Procedure to Load data using Setup Table

Procedure to
load data using Setup Table

Summary

The objective of the document is to give information to load data using setup tables when delta is still enabled. The information below is available in SCN in different forums. I have tried to collate that and give some more information in my personal experience in one single document.

Introduction

Setup tables are nothing but tables which are directly linked to application tables. SAP doesn’t allow direct access to application tables and hence to extract data from those tables, we have setup table as an interface between them and the extractor.

Load from setup table is used to initialize delta loads, which means this is always a full load from the application tables, based on the selection provided while
running setup job. Once the load from setup table is completed, we could normally load deltas through delta queue.

Business Scenario

We have various scenarios to load historical data to newly developed info-provider or existing info-provider with few enhancements. In these scenarios, we may need the help of setup tables to load data and this is a part of LO Extraction scenario.

Business users want a new report based on purchasing which cannot be achieved using a standard info-cube based on the requirement. Hence we have developed a new Info cube which needs to have data from 2LIS_02_SCL and 2LIS_02_SCL (which is already delta enabled).

In the above scenario, if the business doesn’t require history data, then there is no challenge since we could add the new info-cube in the existing delta info-packages.

If the business requires history data, then we need to load history data using setup table and then add the same info-cube in existing delta loads.

Procedure to fill setup table and load data to BI

We need to keep in mind that the setup table is not filled always. If we have a scenario to load full/Init, we need to fill the corresponding setup tables by scheduling setup runs (BGD jobs).

Before proceeding to fill the setup tables, we should make sure that they are empty

Below is the procedure to delete setup tables. The procedure to delete setup table for all components is same and the deletion is component dependent, not
datasource wise. Hence if we our requirement is to load data from HDR datasource, we need to fill the whole component which includes HDR information also.

Transaction code to delete setup table is LBWG

Once we get the above screen, we could specify the component (02, 11, etc…) and click on execute button.

Once we execute, it would give us the below screen for confirmation. Click ‘Yes’ to proceed further.

(We are not going to delete any data from application tables. We are deleting the setup table before filling it up, just to avoid duplicate data)

Once the setup table is deleted, the below message will appear in the bottom of the screen

Now we are done with the deletion of setup table and we are fine to proceed further to
fill it back

Deletion activity is very simple with one transaction for all components. But in order to fill the setup tables, we have the following transaction codes for
individual components.

We could also achieve the above through the transaction code SBIW in the following path.

Settings for Application-Specific Data Sources –> Logistics –> Managing Extract Structures –> Initialization –> Filling in the Setup Table –> Choose the component to fill

Loading data to BI

Once the required history data is available in setup table, we could start loading it to BI. Before triggering the info-package, we need to change the settings in info-package to load it as Repair-Full request.

Below are the steps to convert an info-package with full load to a repair full load

Open the info-package

Menu –> Scheduler –> Click ‘Repair Full Request’ as below

Below screen will appear in which we need to check the option ‘Indicate Request as Repair Request’

The purpose of changing the full load to repair-full load is because we wouldn’t be able to run delta after a full load. Hence the load should be a repair-full
load.

There is also an option to change a full load request into repair full request after loading using the program ‘RSSM_SET_REPAIR_FULL_FLAG’

Once the full loads are completed, we need to run the above program which will give us the below screen

We need to fill the above information and execute. All full requests in the info-provider will be converted into Repair-Full request. After which, we could do delta loading without any issues.

Points to remember

• The setup table deletion and filling up activity should be preferably done in non-business hours
• Before starting the activities, it is suggested to lock the business users, so that delta will not be lost
• It is not mandatory to stop V3 jobs, since the setup table concept runs entirely a different path and it will not disturb delta. But still, we should run V3 jobs manually until and make sure delta loads to BI picks ‘0’ data.
• When we run setup table filling jobs, it is always recommended to fill it for selective regions or periods. We can never predict on how much data is available in application tables. If we don’t specify any selections, it will take days to complete the job.

Naming Convention of setup tables

Setup table name will be extract structure name followed by SETUP.

It starts with ‘MC’ followed by application component ’01’/’02’ etc. and then last digits of the Data source name and then followed by SETUP. We can also derive it with the name of communication structure in LBWE followed by ‘SETUP’

Below is the list of setup table names for the application 02 – Purchasing.

With the use of these tables, we could make sure that the data is deleted/ filled after the corresponding jobs

Important Transaction Codes

NPRT – Log for Setup Table jobs

LBWG – To delete setup table based on
components