Hello, while testing extraction of 2LIS_02_ITM and 2LIS_02_SCL (rsa3), the system tells me ""0 data records selected"" even when I did everything before correctly: - LBWE - activation and set of direct delta - set application active indicator - customize industry sector - deleting setup tables - creating the statistics from the historical data. are extracting data, the 2 mentioned in the subject line do not extract any data. Ship-to Party. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. I also have checked that: 1. KOSTK. 2LIS_02_HDR purchasing order header level data,2LIS_02_ITM purchasing order item level data,2LIS_02_SCL purchasing order schedule level data. 3. About this page This is a preview of a SAP. 2001. 10 characters required. 163 Views. Jan 29, 2008 at 06:41 PM. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . IF i_datasource = '2LIS_02_ITM'. Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. Relevancy Factor: 6. 3. 0) Basis - BW Service API: VBDATA: Update data: Basis - Client/Server Technology: BW Datasources related to RMBWV302 BW DATASOURCE Description Application ;. The migration of DataSource 0FI_AP_3. But I can say as numeric pointer ,backend data source is using primary key (VBELN) or combination of primary key (VBELN-POSNR) from VBAP table. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . I am using the 2LIS_02_ITM extractor. This process chain activates and for the first time fills all data targets for the scenario Delivery Service Purchasing (InfoArea 0MMPUR_DLV, display component Process Chains Delivery Service MM (0MM_DLV)). Use. LOEKZ is only an indicator/flag. I have already done the following steps: 1 - Transaction SBIW: Settings for Application-Specific DataSources (PI) Logistics. Then I will build a ODS on top of these extractors. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). In ekpo screenshot you can find final Invoice flag is set (EKPO-EREKZ) for all the PO line. I cannot see this same field under the same comm. Description. SAP BW/4HANA. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data. Vote up 2 Vote down. Over the last few days , I had some posts on 2LIS_02_ITM and Process Key activation. 2LIS_02_ITM - Adding field problem | SAP Community Relevancy Factor: 1. BW Reorganization Store for MC11V_0ITM. With this process chain, the initial data set is updated (initialization of the delta process) in the data targets affected (InfoArea. etc. we have datas (ekko,ekpo) 2. png. 14. Technical Name of Target InfoObject. 2LIS_02_ITM : MC02M_0ITMSETUP : Storage BW Setup for MC02M_OITM : Purchasing :. I now am trying to get publishing back on track. 02 Purchasing 2LIS_02_ACC MC02M_0ACCSETUP Folder: BW Setup for. It's the pre-processing of Archive ( Archive Object is MM_EKKO ). The process chain supports SAP R/3 standard systems as of Release 4. LO Cockpit - Basic Question. Purchasing Data (Item Level) NA. AWS Documentation AWS Supply Chain User. Delivery time (SCLTM) = 12:00:00. Technical name: 2LIS_02_ITM Use In combination with the InfoSources Purchasing Data (Document Header Level) and Purchasing Data (Document Schedule Line Level , the InfoSource Purchasing Data (Document Item Level) supplies the basic data for analyses of purchasing documents. MC02M_0CGRSETUP. Table EKKN filed PS_PSP_PNR gives you the WBS element associated with the PO. (2LIS_11_VAHDR). -----Mensaje original-----De: John Parks via sap-r3-bw [mailto:sap-r3. Transa ctional. When testing the data, we noticed that certain PO's that are in the tables EKPO are not showing up in the 2lis_02_ITM PSA. KONV KSCHL. It contains the complete history of the loaded data. Quantity ordered (SCLQTY) = 20. setup table are built sucessful and he collects data (setuolog) But the extractor checker doesn't work he collects 0 data. So I did the following steps : 1. Clear "RSA7" 03. For more information on this topic, refer to the. These documents are also not getting filled into Setup Table by OLI3BW. Source System for R/3 Entry*. 192 Views. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Oct 18, 2007 at 09:39 AM. BSART. Once we get the above screen, we could specify the component (02, 11, etc…) and click on execute button. Sap Tables in SAP. 2lis 02 Itm Tables Most important Database Tables for 1. AND ebelp = mc02m_0itm-ebelp. The new DataStore object of Invoice Verification (0LIV_DS01) is supplied with data by the new DataSource 2LIS_06_INV, whereas previously the relevant invoice verification data was only supplied by the three DataSources of Purchasing 2LIS_02_HDR (purchasing data (header level)), 2LIS_02_ITM (purchasing data (item level)), and 2LIS_02_SCL. The DSO is directly supplied from the Info/DataSource 2LIS_06_INV. 63 Views. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. 2LIS_02_HDR. Run the Delta Info package in BW to update all the data i. no (EBLEP) and delivery schedule line counter (ETENR). BEDAT. click the Filter combo to see the base tables, select MCEKKO MEMORY from the right and transfer it to the right section, click Continue, next click Yes. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. In my example, I focus on an potential alternative to the classic LIS DataSource 2LIS_02_ITM (MM Purchase Order Items): C_PurchaseOrderItemDEX is a released delta-enabled CDS extractor. 4. These Z-Fields are in the database table EKPO. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . Apply the changes / Transport. When does it happen that 2LIS_02_ITM does not add. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. also full update of 2LIS_13_VDITM featches only records that have been uploaded with initial load. However in the S/4HANA system, table KONV is obsolete and replaced by table. 2LIS_02_SCL. #. Purchasing Document Category. Field VDATU has the same name as Update Date for Statistics Update for DataSources 2LIS_11_VAITM and 2LIS_11_VASCL. 2LIS_03_BF, 2LIS_03_BX, 2LIS_03_UM)?. 3. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. DataSource 2LIS_02_HDR contains data still to be transferred. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Transport the Enhanced Data source to Source SAP system . 3. 2lis 02 Itm Sap Database Tables in SAP (30 Tables) Logistic Cockpit datasources reads from Setup-tables (like MC02M_0ITMSETUP for 2LIS_02_ITM) when you execute Full or Delta-init. The following is the list of frequently asked questions about LO Data Extraction (logistics datasource) in a S/4HANA system: In the ERP system, 2LIS_11_VAKON (Sales Document Condition) & 2LIS_13_VDKON (Billing Document Condition) is used to fetch data from table KONV. Figure 7: BW Control Table – Fields . BEDAT. 2LIS_02_SRV(obsolete) BW-BCT-PA - Personnel Management . Step. PO Deletion Indicator. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . SD - Sales and Distribution: 3 : 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 : 2LIS_12_VCITM: Delivery Item Data SD - Sales and Distribution: 5 : 2LIS_01_S001: Customer SD - Sales and. This field is not present in the source structure 2LIS_02_ITM. Note: This step is used when we need to add additional fields, to push into BW. You can see the table in the above screen shot. Please also specify what is the way to find out it. Run the collective run, so all the data is sent into the delta queues. SAP R/3 Enterprise. 0OPS_12_ITM. I have added field LOEKZ (Deletion indicator) to datasource 2LIS_02_ITM from t-code LBWE and activated. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Technical Name of Target InfoObject. This is available in SBIW. I executed infopackage full load for such sales documents, but 0records are received. 0. Where in BW should be stored the data about secondary costs on purchase (acquisition) which evaluate the real price of goods?. And it shows 0 records. I filled the setup table in the development system and did an Initialize with data transfer. Targets are going to be different for delta and full. Go to. MC11V_0ITM: Extraction SD Sales BW: Document Item Allocation for DataSource 2LIS_11_V_ITM. Purchasing 2LIS_02_HDR MC02M_0HDRSETUP Storage BW Setup for. following fields of. Datasource Type: Transaction Data Extractor. Use. Media-Specific Adjustments to the InfoSource Order Item Data (as of 2. Issues in Filling Setup table for 2LIS_02_HDR | SAP Community Relevancy Factor: 1. When I loaded to BW , 2LIS_02_ITM transferred some records but added 0 Records. 3. All 3 2lis_02_itm, hdr and scl were enhanced to add additional fields. Table: EKPO. cat = F ) . CLEAR LT_DATA. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . 2LIS_02_ITM - Adding fields to communication structure - User exit | SAP Community Relevancy Factor: 1. The system therefore only executes a delta update for this DataSource if. i need to get the data from different tables. 2lis 02 Itm Database Tables in SAP (23 Tables) MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/PUR_IS11. Please provide a distinct answer and use the comment option for clarifying purposes. . 3. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 3 :. Implemented class Name – ZCL_DS_2LIS_02_ITM. 2lis 11 Vaitm Tables BW Extractors in SAP (28 BW Datasources) Login; Become a Premium Member; SAP TCodes;. I know that For purchase order details we used 2 datasources 1. Go inside the class ZCL_DS_2LIS_02_ITM and implement the below code – ATA : LT_DATA TYPE STANDARD TABLE OF MC02M_0ITM. 2LIS_13_VDITM: Billing Document Item Data. 4. Mvke Table BW Extractors in SAP (16 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. ) 2LIS_02_ITM. 2LIS_11_VAHDR: Sales Document Header Data SD - Sales and Distribution: 3 : 2LIS_13_VDITM: Billing Document Item Data SD - Sales and Distribution: 4 : 2LIS_11_VASCL: Sales Document Schedule Line SD - Sales and Distribution: 5 : 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 6 :. 2. Table of Contents SAP BW/4HANA Content Add-On. Moreover STAPO (Item is statistical) = X, means Item is statistical. From what I read, i think i'm missing the following steps, from which I need more detail:EKBE table has Purchase Order History data and MSEG has Document Segment: Material data in it. RSS Feed. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. T-Code : LBWG Or SBIW -> Settings for Application-Specific Datasources(PI) -> Logistics -> Managing Extract Structures -> Initialization -> Delete the contents of the setup tablesYes you can append the AEDAT filed to 2LIS_02_ITM datasource and need to populate with the data from table by writeing the conde in COMD. If no data. Base Tables . 5B. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_40_REVAL: Revaluation at Retail: IS - Retail: 2LIS_11_VAITM: Sales Document Item Data:1. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). Application Component. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. In R3, some PO items marked with Final Invoice (EREKZ = X) but the same PO items are not reflected with final Invoice flag via the extractor 2LIS_02_ITM. KNTTP – Account Assignment Category. 2lis 03 Bf Table BW Extractors in SAP (29 BW Datasources) Login; Become a Premium Member; Transaction Codes; Tables. We can replace the contents of internal dd_belnr through flat file upload. While doing the statistical setup i am using the T. 2LIS_02_CGR. EKAB is a standard Purchasing Transparent Table in SAP MM application, which stores Release Documentation data. Urgent help required. Purchase Invoice Tables. The extractor 2lis_02_itm will extract both Purchase Orders and Agreements. Fill the setup tables with historical data using SBIW to get to the tcode OLI*BW. Replicate the same in BW system. KONV KBETR. 2LIS_13_VDKON: Billing Condition Data. 2010 1:00 AM. Step 4) Choose the datasource 2LIS_02_ITM, which is purchasing data at Item level. then data inconsistency will be happen. FI and COPA is easy to get , the hardest to get at is the LO extractors. Can see Queue 2LIS_11_VAHDR. 2LIS_02_CGR 2LIS_02_SGR 2LIS_02_SCN. 0B) - SAP Documentation. Also, please make sure that your answer complies with our Rules of Engagement. MC11V_0ITMSETUP. Symptom. Comparing DataSource 2LIS_02_SGR to ME80FN. Use. with SE11 transaction you can see these tables. 1) Go to the RSA6 (Find ur datasource 2LIS_02_ITM double click on it ) 2) Double click on the extract structure 3) You will see extract structuter then you can see the append structure at the top left click onit 4) Give the name of the structure 5) Enter the NEW field starting with "ZXXXXX" 6) Save it 7) Go to Cmod and then create a project 8) The assign components as EXIT_SAPLRSAP_002 (for. Is there anyway I can get this field populated without writing code for it? "Field BADAT in 2lis_02_itm not displaying values - SAP Q&A"SAP NetWeaver 7. These documents are also not getting filled into Setup Table by OLI3BW. 2LIS_02_ITM Not Updating Setup Tables In Initialization Summary. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. Fill setup table. Consider Process Key 2 for GR amount and Process Key 3 for Invoice Amount. sap and forums i found out that for. g. Total number of tables/structures containing this field is 4948. where this is using a standard datasource 2lis_02_ITM and 2LIS_02_SCL and i have acitvated this standard cube 0pur_c01. Step 3: Move BW TRs to BW PRD system. You should find table names here. PO Doc no (EBELN), PO Itm. A goods movement is posted with the following information: Posting date (BUDAT) = 05. Due to some reason we have to fill up set up table for Purchasing (2LIS_02_ITM and 2LIS_02_SCL) again: These tasks have to been done: 1. But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. BW . 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. Then I ran the init load and for 2LIS_02_ITM I got 432 records as transferred and 0 as added and for 2LIS_02_SCL I got 326 as transferred and 0 as added . 02. Application: SD - Sales and Distribution. if you put EKET then it brings up. Marco. It was huge reload project for us which continued for a. Purchasing. e. We've created a new field called, e. Once we execute, it would give us the below screen for confirmation. 4 ; SAP NetWeaver 7. This gives me a message 'Date fields for info structure S032 are not. BEDAT. 2LIS_45_LST: Agency document: Remuneration list: IS - 2LIS_45_HDR: Agency document header data: IS - 2LIS_03_BF: Goods Movements From Inventory Management: MM - Materials Management: 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_11_VAITM: Sales Document Item Data: SD - Sales and Distribution:. MC02M_0ACCSETUP. Dear All, I have activated BI Contents: 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_HCL. A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!We have schedule the job of filling the setup tables today i. READ TABLE xmcekkn. Source System for R/3 Entity*. Filled with the 2-digit system ID of the connected source system. Hi everyone, We are implementing the purchasing solution for the first time at the client. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Go to RSA2, enter DataSource name 2LIS_02_ITM,. RemoteCube Compatible. from the standard tables using a Business content Data Source the Data should be Extracted to BW system. Why? What am i missing out do i need to do any changes before i actiavte the in-active tables in LO-Cockpit. LO-IO. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW > Settings for. Transformation. Is it the right method or should it have been add. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17. 0. LOOP AT c_t_data INTO mc02m_0itm. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. DataStore object (advanced): SD: Billing Document Item Data (2LIS_13_VDITM) - /IMO/CMSD31. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :Note. now i want to fill setup tables for below datasources, can you suggest what are tcodes to fill up setup tables for below datasources. About this page This is a preview of a SAP. 123456 20 L. The InfoSource for the SD sales document Order Item Data (as of 2. This document has 2 parts. MM-PUR: Purchase Order Delivery (Items) - /IMO/PUR_D21. SAP Tables SAP Table Fields (New) SAP Glossary Search;. SAP. MCEX03. 2LIS_45_LST: Agency document: Remuneration list: IS - 2LIS_45_HDR: Agency document header data: IS - 2LIS_03_BF: Goods Movements From Inventory Management: MM - Materials Management: 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_11_VAITM: Sales Document Item Data: SD - Sales and Distribution:. Thank-You. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. The configuration of the table looks as follows. Locate your Extractor (Datasource). Dear All, It would be really helpful to know the used tables for datasource 2LIS_02_ITM. all fields of DataSource 2LIS_12_VCITM. 4. 2LIS_02_HDR : Purchasing data header level 2LIS_02_ITM : Purchasing data item data 2LIS_02_SCL : Purchasing data schedule line level 2LIS_02_SCN : Produced Activity : confirmation of schedule Lines. The first extraction of the document itself getting two positive records in the same datapackage. SAP BW/4HANA. And after the setup table is filled, data in 2LIS_02_SRV gets duplicated. Pls reply needed urgent,i'm. Purchasing. 2. We need the data for the two new fields going forward. 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 11 :However, before replicating to the BW on HANA system connected, I checked data in S4 via RSA3. In LBWE, its showing that LOEKZ is taken from EKPO. These fields are populated in the extractor and not stored in any tables. you can store the all the Purchase Orders in one InfoProvider ( restricting on doc. (We are not going to delete any data from application tables. MC02M_0ITM is a standard Logistics Information System (LIS) Structure in SAP LO application. How can I find which tables in R/3 are the source tables for this and that extractor (e. We need to extract fields RM06E-LTEX1 (long text) and RM06E-KZLTX (More Text Exists which is a flag) from R/3 into BW however RM06E is a structure in R/3. MC02M_0SGR: Produced Activity: Delivery of Schedule Lines Maintenance for Data Source 2LIS_02_SGR 8 31 139,142. 4. The DSO provides insight into the delivery service of vendors by exploring deviations across the. Sep 25, 2008 at 11:16 AM. In the ERP system, this information is contained in the following tables:. I am using 2lis_02_itm and 2lis_02_hdr. 5. Step 2 Create Target table where you want to persist the data. Follow. SYDAT is Item created on - EKPO-AEDAT. (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. RSS Feed. I have an issue with Purchasing data source: 2LIS_02_ITM. For item 20, LOEKZ = L (Deletion indicator). I also know that my InfoSources for this data are 2LIS_02_HDR, 2LIS_02_ITM, and 2LIS_02_SCL. You have to enhance the data source if the field is not available to you. FIELD-SYMBOLS : <LS_DATA> TYPE MC02M_0ITM, <LV_KUNNR> TYPE EBAN-KUNNR, . save the package and press create. and added a Z-field (ZZEKKOL) for this field. what is the reason , pls. All the data is updated to standard table like VBAK , VBRK, LIKP. Most important Database Tables for 2lis 02 Itm Data Source Tab # TABLE Description Application Table Type; 1 : MARA: General Material data: Logistics - Material Master: Transparent Table 2 : MARC: Plant data for Material Logistics - Material Master: Transparent Table 3 : VBAK: Sales Document: Header data: SD - Sales:Table of Contents SAP BW/4HANA Content Add-On. You can capture that without enhancing 2LIS_02_SCL Datasource. 0. Delete content of ODS/CUBE. 339 Views. Hi All, When a PO is posted the vaules are being picked by the 2LIS_02_ITM extractor. Hi mates, Im using extractor 2LIS_02_ITM in BW, my field Item Category is empty. There is a requirement to load full load to BW system from 2LIS_02_ITM data source. Clear setup tables in LBWG. and Yes,I have DELETED setup tables data prior to running the Setup process. I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 . But in case of LIS it is specific to the particular application. I can then reference the InfoSources in question since I know HDR data will come ! from EKKO and ITM data will come from EKPO. This is to keep data that is depending on each other consistent. Jun 15, 2007 at 04:37 PM. Environment. BSTYP. You will find pool of objects there. Features of Extractor This DataSource provides information about: the header data of a purchasing document, such as vendor, purchasing organization, order currency, and so on the item data. 0GN_R3_SSY. Not just "LO DataSources" because there are some that don't use this feature. The values can be seen in EKPO table but I am not sure this would be the source for extractor 2LIS_02_ITM becuase, when I run setup table or extract the data in. WHEN '2LIS_02_ITM'. 0 EHP 3. . "Image/data in this KBA is from SAP internal systems. . When a DTP/TRFN has to be created for a Datasource as source, then the Datasource cannot be added from the value help or manually, if the name of the datasource begins with a number between 1 to 9. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_S012: Purchasing: MM - Materials Management:. Hi, Logistics application ""02 : Purchasing"" (HDR, ITM and SCL) is activated. I therefore tried to use the FULL LOAD for those datasources (2LIS_02_HDR, 2LIS_02_ITM und 2LIS_02_SCL). Whenever setup table is deleted for application 02, all records for data sources 2LIS_02_HDR, 2LIS_02_ITM & 2LIS_02_SCL becomes zero in RSA3, but 2LIS_02_SRV will contain data. Purchasing document 4500000001, Item 0010, has the following schedule lines: Schedule line number (SCLNR) = 1. I saved and Activated the data source. Important Key Figures: ROCANCEL. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) (2LIS_02_SCL). Click on save ---> Again Click on Inactive Click on Continue and Again Click on Continue Now You can see the Data Source in Active (Job Control) * Repeat the same steps for 2LIS_02_ITM and 2LIS_02_SCL 3. 2LIS_02_ITM: Full & Delta: Inventory Management: Material Management: 2LIS_03_BF: Full & Delta: Production Planning: Production Planning: 2LIS_04_P_MATNR: Full & Delta: Sales:. Purpose. Import the table definition from the Metadata Repository in the Data store Explorer and use it as source in a data flow. Available as of Plug-In Release. structure MCEKKO with field UNSEZ (on the EKKO table), I can see it in LBWE on the right for selection on the 2LIS_02_ITM datasource. Use corresponding exit FM as template and copy the import, Export, Table, Exception. However, InfoCube for Purchasing ( 0PUR_C01) is already active in the system and delta are being loaded into it on a regular. Can somebody please explain this behavior? Regards, AlexSetup Table Structure : MC02M_0(HDR)SETUP Deleting Setup tables : LBWG - Application : 02 Setup Table deletion job name. Use. RemoteCube-Compatible. Data load for :2LIS_02_HDR. -----Mensaje original-----De: John Parks via sap-r3-bw [mailto:sap-r3. SD: Delivery Header Data (2LIS_12_VCHDR) - /IMO/CMSD20 . When is it necessary to reload the setup table? For Example. . On DEV ran RSA3 for docs 4500000780 4500000782 0 recs selected 4)Delete set up tables for Purchasing application 02 5)Fill up set up tables date range 9/17/2004 to. They also extract GR and IR. That means that you can use this DataSource both for data replication in a BW system (SAP Business. Login; Become a Premium Member; SAP TCodes; Tables. 100 -> 100 -> 200.