I've done all the "tasks" for setup tables, but i don't have 0PROCESSKEY. . With this process chain, the initial data set is updated (initialization of the delta process) in the data targets affected (InfoArea. Product. - Process Key 001:PO. When I try to load setup data I got this message in setup table. The records have the deletion indicator LOEKZ set to L in EKPO and are correctly getting updated with Recordmode 'R' and negative keyfigures in the PSA of datasource 2LIS_02_ITM. Deleted the set up tables and ran OLI3BW and filled the set up tables. 3. But for 2lis_02_sgr we are able to get records only for "Pruch Docu Catgory" = F(Purchase Order). 6940 Views. Suppose the sale order is 20 qty, there will be couple of records with 20 qty, doubling up the qty. Table of Contents SAP BW/4HANA Content Add-On. We could able to see the enahnced field data in RSA3 , but after making any change in ME22n its not p. Yes. etc. In EHP 3 the tables are already delivered to the customer enhanced, the activation will only. 2LIS_02_ITM Not Updating Setup Tables In Initialization Summary. EKPO - Item. Then I will build a ODS on top of these extractors. e 4. In combination with the InfoSources Purchasing Data (Document Item Level). Available as of OLTP Release. Symptom. sap and forums i found out that for. Replicate the datasource 2LIS_02_ITM and reinit and load data. I checked the function module also , but still in process, any suggestions would be greatly appreciated. Hi, when you delete the setup table for 2LIS_02_ITM, it will show that still data exist for other DS. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 :. How can I find which tables in R/3 are the source tables for this and that extractor (e. WITH KEY supkz = '2'. 2LIS_02_ITM and 2LIS_02_SCL datasources not only extract PO line items. When I try to do this in the conventional way (in transaction RSA6, button 'E. We are using the BW DataSource 2LIS_02_SCL from the LO Cockpit and have added these two fields from the Customizing cockpit (LBWE): WAMNG WEMNG. 2lis 02 Itm # TABLE Description Application Table Type; 1 : EKPO: Purchasing Document Item MM - Purchasing: Transparent Table 2 : EKKO: Purchasing Document Header MM - Purchasing: Transparent Table 3 : EBAN: Purchase Requisition MM - Purchasing:Issue: Even when Deletion Indicator is marked for a PO Item in P20, the same is not reflected in BW via delta/full repair loads. 2016 at 02:59 PM GTM 2LIS_46_ITM extraction. Header/Item Data (data from the tables EKKO and EKPO) Delivery Schedule Lines (data from the table EKET) Purchase Order History (data from the table EKBE) You can check the data from the DataSource 2LIS_02_ITM with the Header/Item Data view. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. From. In RSA3 if we check for that sales doc nos , it is displaying 0 records. 2LIS_02_HDR purchasing order header level data,2LIS_02_ITM purchasing order item level data,2LIS_02_SCL purchasing order schedule level data. When I enhance comm. Figure 9: BW Control Table – Foreign. Delete the setup data (LBWG) 2. 2LIS_02_SCL. correct me if iam wrong. Here is the code: LOOP AT xmcekpo. For information, I had the same problem with 2LIS_02_ITM. Thanks and regards. With this handy table you can find the status of your current job or previous initialization jobs through SM37. SAP delivers the following example BEx queries on top of MultiProviders Sales Overview. I have already maintain datasource 2LIS_02_ITM through LBWE. FI and COPA is easy to get , the hardest to get at is the LO extractors. Purchasing 2LIS_02_HDR MC02M_0HDRSETUP Storage BW Setup for. I am able to see the newly added field in the structure, However when I test the datasourcein RSA3. MC11VA0STH: Extraction MD Order Header Status for DataSource 2LIS_11_VASTH. (Which acts also as delta queue similar to RSA7). Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. Total number of tables/structures containing this field is 4948. 13. Pls clarify if both delta and full load can happen in parallel for the same data source?Vbak Table Data Source BW Datasources. Scenario 1: All the line items associated are marked for deletion,Then 2LIS_02_ITM--> LOEKZ being extracted as L,No issues here. Fill the setup tables with historical data using SBIW to get to the tcode OLI*BW. Setup Table. The process chain supports SAP R/3 standard systems as of Release 4. 01. As of SAP enhancement package 6 for SAP ERP 6. The DSO is directly supplied from the Info/DataSource 2LIS_06_INV. CLEAR LT_DATA. I have an issue with Purchasing data source: 2LIS_02_ITM. But now I have a requirement to calculate Net GRN. Upon trying, i have encountered many problems: 1. 2LIS_02_ITM. 2. SAP Tables SAP Table Fields (New) SAP Glossary Search; SAP FMs; SAP ABAP Reports; SAP BW Datasources;. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. 3. 3. 123456 20 L. 2LIS_02_xxx extractors. You get this message , when you execute MCB_ " View/table V_TMCLBW can only be displayed and maintained with restrictions" 2. Purchasing document 4500000001, Item 0010, has the following schedule lines: Schedule line number (SCLNR) = 1. Maintained extract structure for 2LIS_02_ITM (LBWE) 2. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 . Comparing DataSource 2LIS_02_SCL to ME80FN. Set up table data will be deleted for whole 'Purchasing' if deleting for '02' even though you want data reload for only Purchasing Item datasource 2lis_02_itm. Bobby. READ TABLE xmcekkn. Transaction LBWQ in ECC: MCEX02. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. Then I. Follow. I have checked unhide in rsa6, but still its not displaying any values. transfered datasource 2LIS_02_ITM using tcode RSA5. BW: Transaction Key in 2LIS_02_ITM. For purchasing datasources 2lis_02_itm and 2lis_02_sgr . When is it necessary to reload the setup table? For Example. Clear setup tables in LBWG. Login; Become a Premium Member; SAP TCodes. I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 . IF i_datasource = '2LIS_02_ITM'. Add a Comment. We deleted init and reinitialised with no success. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2LIS_02_ITM Purchasing Data (Item Level) MM - Materials Management: 14 : 2LIS_05_QE2 Inspection Result: Quantitative Data QM - Quality Management: 15 :Transformation. (We are not going to delete any data from application tables. This is derived from the statisitcs updating facility maintained for updating the LIS (PURCHIS) tables in R/3. cat = F ) . I am using 2lis_02_itm and 2lis_02_hdr. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. Data source. MCEX03. Go to OLI*BW and fill set up tables. 2166572-What tables are read for datasource 2LIS_06_INV and basic logic. 01. Transa ctional. we have deleted "02" in T-Code LBWG and filled setup table using Tcode - OLI3BW. You can look at the includes with *TOP* eg INCLUDE mcex02top. Follow. Comparing DataSource 2LIS_02_SGR to ME80FN. 05. 0B) - SAP Documentation. Scheduling Agreement Tables. SAP Table Field : BUDAT - Posting Date Top 200 SAP Tables containing the field/column BUDAT. 04. Purchasing Document Category. It was huge reload project for us which continued for a. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL. 0. no (EBELP). However, InfoCube for Purchasing ( 0PUR_C01) is already active in the system and delta are being loaded into it on a regular. Test using RODPS_REPL_TEST , SUM = 0 in the result. Now when I click on Initialization >Fill Setup Tables >Perform Setup Purchasing, i get the following message at the status bar: ". Read more. 2008 i have executed Initial Load from BI. 2lis 13 Vditm Tables Most important Database Tables for 2lis 13 Vditm # TABLE Description Application Table Type; 1 : VBRP: Billing Document: Item Data SD - Billing: Transparent Table 2 : VBRK: Billing Document: Header Data SD - Billing: Transparent Table 3 : MC13VD0ITM:table names anywhere. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. This DSO contains delivery related indicators and key figures for purchase order items. Check the. Hi Kumar: Maybe you're not able to fill the Setup Tables because the Extract Structures for Purchasing are inactive, you can activate them in Transaction LBWE. They are needed in BW and not in R/3. Select the Data Source ( 2LIS_02_ITM ) 3. 339 Views. 4. 2lis_11_vascl. I am trying to extract data from datasource 2lis_02_hdr using lo-cockpit and I have followed the below steps. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. SAP BW/4HANA. I know that For purchase order details we used 2 datasources 1. This counter determines the number of deliveries based on the GR document items. Tables related to 2LIS_06_INV TABLE Description Application ; RSEG: Document Item: Incoming Invoice: MM - Invoice Verification: RBKP:MM-PUR: Purchase Order Delivery (Items) - /IMO/D_PUR21. Two lines are extracted. Tables for 2LIS_02_ITM. 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. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. In this extractor we have enhanced "PS_PSP_PNR" (WBS Element) field whose values are being stored in "Account Assignment in Purchasing Document" table. Implemented class Name – ZCL_DS_2LIS_02_ITM. You think 2LIS_06_INV extracts too many records either in the INIT, Delta or Full loads. Description: Sales-Shipping Allocation Item Data. But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. Invoice Verification. 100 -> 100 -> 200. 2. Delta & Full extraction to BW for 2LIS_02_ITM. MC02M_0ITMSETUP if it have any records" Customized BADI Name – ZPP_DS_2LIS_02_ITM. The first extraction of the document itself getting two positive records in the same datapackage. 2lis_11_vahdr & 2lis_11_vaitm we have to use tcode OLI7BW. SAP R/3 Enterprise all versions Keywords. the situation is that when I run delta it fetches 0 records. . Recently, I need Batch data for reporting related to Purchasing , fortunately there is field CHARG (Batch) in 2LIS_02_ITM. Datasource : 2LIS_11_V_ITM. MC11VA0STI: Extraction MD Order Item Status for DataSource 2LIS_11_VASTI. how does 2lis_02_itm gets data from ekpo pstyp, what tcode can I see the entry? is it also in VA03? the Item Category from that transaction is from VBAP. KONV KBETR. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW > Settings for. 2. Step three:. 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. Cannot see the data for datasrc 2lis_02_scl in RSA3. At present delta loads are running through that extractor. and choose the industry sector "Standard (Core)". Use corresponding exit FM as template and copy the import, Export, Table, Exception. Over the last few days , I had some posts on 2LIS_02_ITM and Process Key activation. This's also valid to other PUSH datasource. Or if you are looking for OSS NOte #. Thanks for the quick response. See SAP Service Marketplace, SAP Note 0448600 for more information on prerequisites. These documents are also not getting filled into Setup Table by OLI3BW. An overview of Datasources and the programs filling the relevant setup table (named MC*SETUP). We have data sources 2LIS_02_ITM, 2LIS_02_CGR, 2LIS_02_SCR and 2LIS_02_SGR activated and up and running delta properly. If no data. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). I executed infopackage full load for such sales documents, but 0records are received. 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. The DSO provides insight into the delivery service of vendors by exploring. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. However, when I want to re-extract ""Purchasing"" I get a message ""Data source 2LIS_02_HDR contains data still to be transferred"". ) 2LIS_02_ITM. Jun 15, 2007 at 04:37 PM. 3. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :Note. We have an issue with the delta's for the 2LIS_11_V_ITM, which is extracting duplicate values. e. Technical name: 2LIS_12_VCITM. DATA: l_2lis_02_itm type mc02m_0itm, l_index type sy-tabix, lt_ekko type standard table of ekko, wa_ekko type ekko. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. LBWE shows both extract structures (MC02M_0CGR and MC02M_0ITM) as active; Both datasources 2LIS_02_CGR and 2LIS_02_ITM are active and shown in RSA2; Delete setup tables for application 02. Source System for R/3 Entry*. It is from BEDAT from EKKO and EKBE. Symptom. Purchasing Data (Item Level) NA. During the initial load, everything comes along fine all the way to PSA. also check in BD87. In this case use FM EXIT_SAPLRSAP_001 as template. When I check in EKPO table, deletion indicator "L" is available for all deleted PO's. Technical name: 2LIS_02_HDR . There is a table that maps movement type to process key. following fields of DataSource 0CUSTOMER_TEXT: Sold-to Party. we have done initialisation and filled setup tables. The three others (2LIS_46_HED ; 2LIS_46_CFM ; 2LIS_46_GTM) are not showing any data : see attached picture issue. 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)). Consider Process Key 2 for GR amount and Process Key 3 for Invoice Amount. So , how to know. Transaction code to delete setup table is LBWG. After that, AWS Supply Chain automatically creates the Amazon S3 paths and ingests data from the SAP source tables. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. News & Insights. 2LIS_02_SRV(obsolete) BW-BCT-PA - Personnel Management . Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. Nevertheless, nothing work with. in previous versions of ABAP you could easily get it by searching through the code in the code table for TABLES and you would have got it. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. Table Coep BW Extractors in SAP (20 BW Datasources) Login; Become a Premium Member; SAP TCodes;. g. Datasource Type: Transaction Data Extractor. Purchase Requisition Tables. Source System for R/3 Entity*. Login; Become a Premium Member; SAP TCodes; Tables. Block user to modify to modify purchase. MC02M_0CGRSETUP. Hi all, 1. and Yes,I have DELETED setup tables data prior to running the Setup process. Delete the setup Table using LBWG . Use. The InfoSource for the SD sales document Order Item Data (as of 2. 2) From the Scheduler dropdown, select the Repair Full Request Option. 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. 100 -> 100 -> 200. I'm trying to design a dataflow from a SAP ECC 2lis_02_itm delta extractor to sql server table (odp extractor -->sql -->map_cdc_operation --> sql table. I also have checked that: 1. Type of DataSource. Go to t-code ODQMON (in ECC). after this load you can run deltas. Diagnostics. RSS Feed. The purchase order exists in APO in the form of an order. EKKO - Header. LO Cockpit - Basic Question. Runn full load. 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. Vote up 0 Vote down. are extracting data, the 2 mentioned in the subject line do not extract any data. 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:. This InfoSource contains the structure to provide purchase data on item level into the EDW Core Layer. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. In LBWQ no entry for MCEX02 exist. Is there any particular reason? I looked up the configuration of the movement types by going into. 2LIS_02_HDR Purchasing data (Header Level) MM - Materials Management: 16 :2lis 13 Vditm Base Tables BW Datasources Most important BW Extractors for 2lis 13 Vditm Base Tables # BW DATASOURCE Description Application; 1 :. Transaction Data. 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. when I used INIT or DELTA infopackage. OLI1BW INVCO Stat. By debugging function module MCEX02_PREPARE_INFO it was found that the field UPDACT in table TMCEXACT. Hi all, I ran OLI3BW to fill the set-up tables and tried with RSA3 (no selections) and it returned 0 records for 2LIS_02_CGR, 2lis_02_scn and 2lis_02_cgr. READ TABLE i_t_ekpo WITH KEY ebeln = xmcekpo-ebeln ebelp = xmcekpo-ebelp. About this page This is a preview of a SAP. The configuration of the table looks as follows. Thank you all four you responses. 3. 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. SAP. In the ERP system, this information is contained in the following tables:. g. Table of Contents SAP BW/4HANA Content Add-On. Both the datasource do not have Material document number (BELNR) field. 0. WHEN '2LIS_02_ITM'. Delta queue maintenance. (2LIS_13_VDITM). PO. after creating two tbls r created which will handle ur delta. . We are using this 2lis_02-srv d/s for loading services orders (service entry sheet), in this d/s there will be multiple service entry sheets for a purchase order, sometimes in R/3 some service entry sheets may be deleted within the PO. 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. SAP Knowledge Base Article - Preview. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) (2LIS_02_SCL). LO-IO. e, 2lis_02_itm, or 2lis_02_hdr), both the header and the item gets filled up. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. First part explains about the activation of the data source 2lis_02_SRV & second part explains about enhancing it for adding the services line items to be made available for extraction. Go to RSA6. (2LIS_11_V_ITM) - /IMO/SD_IS16 . Filled with the 2-digit system ID of the connected source system. Purchasing 2LIS_02_CGR MC02M_0CGRSETUP BW-Rebuild for. This is available in SBIW. The modeling property Inbound table as extended table has been turned on. some sales document nos missed in bw. "Document data restriction" when filling setup table. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Since I know I am working with Purchasing data those are my obvious choices. This is available in SBIW. eg: if i do the following action: Fill 1 -> Delete - Fill 2. Application DataSource Setup Table. Then save, check and activate the process chain and provide information, where applicable, about which server the process chain should be scheduled on. 0. ex: 2LIS_13_VDITM. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_CGR: Produced Activity: Delivery of Confirmations: MM - Materials Management: 2LIS_02_SCN: Produced Activity: Confirmation of Schedule Lines: MM - Materials Management:. 11. LBWE-- >Purchasing >Extract structures ---->2LIS_02_HDR/SCL/ITM (DATA SOURCES),when i click on the in-active tab to make change and activate i get a alert as the DATA SOURCE doesn't exist. 3. 163 Views. Recommence extraction into BW from the modified R/3. EKKO. So we created an append structure to MC02M_0ITM. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . Purchasing Document Category. Total number of tables/structures containing this field is 7006. That means setup process wasn't happen correctly. However in the S/4HANA system, table KONV is obsolete and replaced by table. Former Member. 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:. RSS Feed. Transformation Rule. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. When we are filling Setup table if anyone access the same setup table from outside. The data is not updated into the upur_c01 cube . I then delete the Contents of Setup table for Application '02' - message ""setup tables deleted successfully"". Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. I have read that it is necessary to delete the setup tables before reloading the setup tables to make sure that there is no duplicate data, however I have different question. 2LIS_02_SCL. KNTTP – Account Assignment Category. Purchasing Organization Tables. Name of Target InfoObject. You can see a relationship between this tables in the web site and click on the link "SAP MM, SD, FI, PS, PP, PM, HR, System Tables". Important Key Figures: ROCANCEL. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. VRTKZ – Distribution Indicator for Multiple Account Assignment Table of Origin. My plan is to perform below steps. Jan 29, 2008 at 06:41 PM. This is how the SAP has defined. The start routine for the updates ensures that only orders and free-of-charge orders are updated in the DataStore object. and enhanced the datasources ITM and SCL adding one Char in. Just as try we deleted Setup table and fill it with PO documents having this issue again but no use. Transformation * For more information about source system IDs, see SAP HANA-Optimized BI Content. and had given the termination time . READ TABLE lt_ekko into wa_ekkoTable YBWMAPPING is used by the class YCL_BW_MAPPING. Where in BW should be stored the data about secondary costs on purchase (acquisition) which evaluate the real price of goods?. I have loaded an initial load to my ODS (0BBP_PO) and also setup a delta. The account. Datasource Jest Table BW Extractors in SAP (25 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. Relevancy Factor: 1. 123456 30 - 123456 40 - 123456 50 - 2lis_02_itm Setup Table. see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. When running the setup for application 02 (TR OLI3BW), the table was not filled: running RSA3 with no restrictions did not retrieve any records. Vote up 2 Vote down. 2LIS_02_ACC. We are analbe to get the records for "Pruch Docu Catgory" = L(Scheduling Agreement). Clear "LBWQ" 04. I'm trying to use datasource 2LIS_02_CGR in addition to 2LIS_02_ITM already in use. In EKET Table the data is like. Run info pack with init without data transfer. Application; 1 : 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 : 2LIS_11_VAITM: Sales Document Item Data SD - Sales and Distribution: 3 : 0CO_OM_OPA_6:. But this d/s 2LIS_02_SRV doesnt pick/identify the deleted service entry sheets. I can see the data for other datasrcs related to purchasing like 2lis_02_itm data in rsa3 . Datasource 2LIS_02_ITM (Purchasing data (item level)) with delta type D (push): As this is delta type PUSH, the delta data records from the application are posted to the delta queue before they are extracted from ODQ as part of the delta update. Delete data "LBWG" 05. When looking in the EKPO table, you'll get an 'X' in the Elikz field when completed, however in the extractor you do not have simply one row with the most recent value, you'll have. I did a setup table fill-up of 2lis_03_bf and I'm seeing missing material documents with movement type 561. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. Hi, Where can i find the t-codes for filling the setup table for all the logistics datasources. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . Direct Access Enabled. Purchasing (application 02): 2LIS_02_ITM. PO Doc no (EBELN), PO Itm. setup table are built sucessful and he collects data (setuolog) But the extractor checker doesn't work he collects 0 data. Delta Process: Delta Queue based. MC02M_OHDR. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources.