These fields are populated in the extractor and not stored in any tables. When I try to load setup data I got this message in setup table. 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. 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. 2lis 04 P Arbpl Tables BW Datasources Most important BW Extractors for 2lis 04 P Arbpl Tables # BW DATASOURCE Description. I am trying to extract data from datasource 2lis_02_hdr using lo-cockpit and I have followed the below steps. SAP Tables SAP Table Fields (New) SAP Glossary Search;. 2lis_11_v_itm. Job for collective update stopped (LBWE) 4. Overall Picking/Putaway Status. Check the. Vote up 0 Vote down. I need to enhance the Datasource 2LIS_02_ITM. Both the datasource do not have Material document number (BELNR) field. Step three:. MC11V_0ITMSETUP. BW-BCT-PM (Plant Maintenance). Purchasing Data (Schedule Line Level) NA. The activation of the business function by itself will not enhance the database tables. 2. Step 3: Move BW TRs to BW PRD system. Sep 16, 2009 at 06:26 PM. I tried deleting the setup table (LBWG) and tried again initialization (OLI3BW) but I cant. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 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. However, when I want to re-extract ""Purchasing"" I get a message ""Data source 2LIS_02_HDR contains data still to be transferred"". Delivery date (SCLDT)= 01. I have added field LOEKZ (Deletion indicator) to datasource 2LIS_02_ITM from t-code LBWE and activated. 2LIS_02_ITM. You can capture that without enhancing 2LIS_02_SCL Datasource. SAP Knowledge Base Article - Preview. 94 Views. 5. Data load for :2LIS_02_HDR. You can see the table in the above screen shot. Run DTP with extraction mode “Delta” ( 1 st time it extracts data from setup table). Scenario 2: If 5/10 line items are marked for deletion, Even though I can see their LOEKZ status in EKPO as L,2LIS_02_ITM is being. RSS Feed. When I enhance comm. Hi mates, Im using extractor 2LIS_02_ITM in BW, my field Item Category is empty. I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 . Use. Source System for R/3 Entry*. There is a table that maps movement type to process key. As of SAP enhancement package 6 for SAP ERP 6. using help. In the standard extractor 2LIS_02_ITM the field BADAT is check as Field only known in customer exit. Use. Oct 18, 2007 at 09:39 AM. - Process Key 003:IR. 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. LE key figures for the delivery item: This InfoSource contains information that relates to the delivery item, such as delivery quantity in sales units or delivery quantity in the base unit of measure. 2LIS_13_VDITM: Billing Document Item Data. Tables for 2LIS_02_ITM. We are about to delete setup tables for purchase (02) component and refill the setup tables. When I check in EKPO table, deletion indicator "L" is available for all deleted PO's. and had given the termination time . Unlock users out of R/3. This is how the SAP has defined. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 :. Apparently these two fields are NOT updated in BW from a delta load. 2LIS_02_ITM. Comparing DataSource 2LIS_02_SCL to ME80FN. In 2LIS_11_VAHDR however, the field VDATU contains the sold-to party's Requested Delivery Date. Data Modeling Relevancy Factor: 2. Yes. However, InfoCube for Purchasing ( 0PUR_C01) is already active in the system and delta are being loaded into it on a regular. The InfoSource for the SD sales document Order Item Data (as of 2. after creating two tbls r created which will handle ur delta. 2008. In this extractor we have enhanced "PS_PSP_PNR" (WBS Element) field whose values are being stored in "Account Assignment in Purchasing Document" table. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). But in case of LIS it is specific to the particular application. 04. In RSA3 if we check for that sales doc nos , it is displaying 0 records. 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. This is derived from the statisitcs updating facility maintained for updating the LIS (PURCHIS) tables in R/3. I was successful in extracting data for the 0PUR_C01 cube using the conventional 2LIS_02_S012 datasource. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Item Level) ( 2LIS_02_ITM ). The fields are filled with an. but when I perform initialization of LIS table on R/3 side I make initial load to BW I can see that there is an. An overview of Datasources and the programs filling the relevant setup table (named MC*SETUP). When I check with RSA3 I've got a lot of records. Setup Table 2lis 02 Itm TCodes Most important Transaction Codes for Setup Table 2lis 02 Itm # TCODE Description Application; 1 : SE11: ABAP Dictionary Maintenance Basis - Dictionary Maintenance: 2 : SM30: Call View Maintenance Basis - Table Maintenance Tool: 3 : SE16: Data Browser Basis - Workbench Utilities: 4 : SE38:Run RSA3 on the datasource 2LIS_02_ITM, find the extraction program field ROCANCEL(Indicator: Cancel Data Record) for doc1 are all null for each doc1 item that this field ROCANCEL fails to catch EKPO deletion indicator field LOEKZ value for these two deleted item 1 and item 4 showed in table EKPO with value of 'L' for item 1 and item 4. 3. But in RSA7 , there are 0 recrods . following fields of DataSource 0CUSTOMER_TEXT: Sold-to Party. Issues in Filling Setup table for 2LIS_02_HDR | SAP Community Relevancy Factor: 1. I therefore tried to use the FULL LOAD for those datasources (2LIS_02_HDR, 2LIS_02_ITM und 2LIS_02_SCL). But I do not see any entries in the setup table 'MC02M_0ITMSETUP' after the SETUP run. Jan 29, 2008 at 06:41 PM. 4. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 5 ; SAP enhancement package 1 for SAP NetWeaver 7. DataSource 2LIS_02_HDR contains data still to be transferred. ebeln = xmcekpo-ebeln. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. Table EKKN filed PS_PSP_PNR gives you the WBS element associated with the PO. In LBWQ no entry for MCEX02 exist. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. See SAP Service Marketplace, SAP Note 0448600 for more information on prerequisites. In R/3 my setup tables are filled : MC02M_0ITMSETUP . DATA: l_2lis_02_itm type mc02m_0itm, l_index type sy-tabix, lt_ekko type standard table of ekko, wa_ekko type ekko. Datasource : 2LIS_11_V_ITM. 2LIS_02_ITM - Adding field problem | SAP Community Relevancy Factor: 1. 02. save the package and press create. Read more. Delta & Full extraction to BW for 2LIS_02_ITM. Field in Table of Origin. Upon trying, i have encountered many problems: 1. 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. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. 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. For the calculation of Net GRN I need (Movement Types: 101 GR goods receipt, 102 GR for PO reversal, 122 RE return to vendor and 124 GR rtrn blocked stck). Hi Fabio, No You cannot do a setup for 2LIS_02_ITM only, You can only do a setup for the whole 2LIS_02. 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. 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:. Hi All, Im working with 2lis* extractor from Lo Cockpit, and i have the followings questions: 1)For example, im using 2lis_02_itm extractor: I have filled the setup tables on 09. 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:. I know that For purchase order details we used 2 datasources 1. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL. Maintain Extract Structure MC02M_0ITM. This's also valid to other PUSH datasource. 2LIS_02_ITM - Set up Table. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :. "Document data restriction" when filling setup table. It is from BEDAT from EKKO and EKBE. 2LIS_02_CGR. Former Member. 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. This document has 2 parts. Then relicated the data sources . Newer data is not available when checking the datasources. When I execute the RSA3 for different Datasources I can see data only in. PO Doc no (EBELN), PO Itm. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. (2LIS_02_ITM). 4. MC02M_0ITM. While doing the statistical setup i am using the T. I'm trying to use datasource 2LIS_02_CGR in addition to 2LIS_02_ITM already in use. It was huge reload project for us which continued for a. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_12_VCITM: Delivery. Use. sap and forums i found out that for. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. So , how to know. Wanted to know whether is there any way to find out how many entries are remaining in setup table to be transfered to BW. 0. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. Issue: COMPL_DEL/Complete Delivery Flag was not getting populated for a PO Item where Transfer Process/Process Key =1 even when the Delivery Completed Indicator was marked at Item level in ECC. 2LIS_13_VDKON: Billing Condition Data. LO Cockpit - Basic Question. Transformation * For more information about source system IDs, see SAP HANA-Optimized BI Content. Go to LBWE (LO Cockpit), select DataSource 2LIS_02_SCL, click on Maintenance icon in Structure column, say Continue. FIELD-SYMBOLS : <LS_DATA> TYPE MC02M_0ITM, <LV_KUNNR> TYPE EBAN-KUNNR, . (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. When i. 5B. This is what the procedure i used (please tell me if i did something wrong): 1. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule. 0GN_R3_SSY. Symptom. MC11VA0STH: Extraction MD Order Header Status for DataSource 2LIS_11_VASTH. 3 ; SAP NetWeaver 7. I checked the function module also , but still in process, any suggestions would be greatly appreciated. 0B) - SAP Documentation. 0. 3. FI and COPA is easy to get , the hardest to get at is the LO extractors. EKKO. . But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. Extraction Table PFO_GO_00IV (Portfolio Assignment) - 13 : 2LIS_12_VCITM Delivery Item Data SD - Sales and Distribution: 14 :Use. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 0FI_AP_4. Go inside the class ZCL_DS_2LIS_02_ITM and implement the below code – ATA : LT_DATA TYPE STANDARD TABLE OF MC02M_0ITM. Delete the setup Table using LBWG . always possible to expose a standard SAP DataSource for the ODP-SAP replication by maintaining a corresponding entry in table ROOSATTR in the relevant source system. Why are the setup tables not filled?If additional information is needed for the tables please let me know. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . with SE11 transaction you can see these tables. 1) 1) Create/Find a Full Repair Infopackage in 2LIS_11_VASCL datasource in BW system. what is the reason , pls. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. We currently have delta load happening from the same data source. Datasource For Afko And Afvc Tables BW Datasources. Just as try we deleted Setup table and fill it with PO documents having this issue again but no use. create ur infostructure using MC21 transaction code. 3. Once we execute, it would give us the below screen for confirmation. RSA3 for 2LIS_02_ITM,2LIS_02_SCL , 2LIS_03_BX,. Maintained extract structure for 2LIS_02_ITM (LBWE) 2. 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. TABW is a standard Basic Functions Transparent Table in SAP FI application, which stores Asset transaction types data. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2. I use the standard extractor 2LIS_02_ITM (order positions) with the update mode "Direct Delta" and apanded Z-fields. #. If no data. You will find pool of objects there. I have already maintain datasource 2LIS_02_ITM through LBWE. Go inside the class ZCL_DS_2LIS_02_ITM and implement the below code – ATA : LT_DATA TYPE STANDARD TABLE OF MC02M_0ITM. But this isn't working the way I would expect: the full load contains only those records which are in the setup tables MC02M_0HDRSETUP, etc. Now when I click on Initialization >Fill Setup Tables >Perform Setup Purchasing, i get the following message at the status bar: ". 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. all fields of DataSource 2LIS_12_VCITM. 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. For e. The first extraction of the document itself getting two positive records in the same datapackage. 2001. MC02M_0CGR Storage. Filled with the 2-digit logical original backend system (based on ORGLOGSY ). READ TABLE i_t_ekpo WITH KEY ebeln = xmcekpo-ebeln ebelp = xmcekpo-ebelp. Filled with the 2-digit system ID of the connected source system. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. We do not need the history data for the 2 fields added. ALIEF - Number of Deliveries. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Just ignore those things. Use. With no data in setup tables, rsa7, sm13. Technical Name. SAP BW/4HANA. Delete the setup data (LBWG) 2. 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 :. 123456 20 L. We could able to see the enahnced field data in RSA3 , but after making any change in ME22n its not p. and then go to BW side and replicate the Datasource. I have already done the following steps: 1 - Transaction SBIW: Settings for Application-Specific DataSources (PI) Logistics. Our delta queue for 2LIS_02_ITM and 2LIS_02_SCL was deleted from R3 by mistake. following fields of. MC11VA0STI: Extraction MD Order Item Status for DataSource 2LIS_11_VASTI. Name of Target InfoObject. You can find more information in Special Features When Using PP-PI . I saved and Activated the data source. Purchase Order Tables. I did a setup table fill-up of 2lis_03_bf and I'm seeing missing material documents with movement type 561. we have deleted "02" in T-Code LBWG and filled setup table using Tcode - OLI3BW. 2LIS_02_ITM and 2LIS_02_SCL datasources not only extract PO line items. Compare with setup table records. ) 2LIS_02_ITM. 12. 2LIS_02_xxx extractors. EKKO / EKBE and field is BEDAT ( Purchasing Document Entry Date) 2LIS_02_ITM will take form EKKO,EKPO,EBAN tables and SYDATM means it is system date field. Purchasing Data (Item Level) NA. 100 -> 100 -> 200. 2. 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. When I try to do this in the conventional way (in transaction RSA6, button 'E. that all records from 2LIS_02_ITM are deleted in the START routine. Fill the setup tables with historical data using SBIW to get to the tcode OLI*BW. Purchasing Document Category. 3) Check the Indicate. Hi, Where can i find the t-codes for filling the setup table for all the logistics datasources. SAP BW/4HANA Business Content delivers this field-based DataStore Object (advanced) as. purchasing and inventory ( data sources are EG 2LIS_11_Vaitm, 2LIS_02_ITM, etc. Purchasing Group Tables. Table: EKPO. We have recently activated the 2LIS_02_ITM (Purchasing item extractor) and as part of integration testing, have filled the setup tables and performed a full load. Below is a list of frequently asked questions about Logistic DataSource setup table filling: Setup table (or RSA3 result) is empty even though you executed transaction OLI*BW to fill it. If I missed to search something please provide that. This DSO (advanced) contains delivery related indicators and key figures for purchase order items. 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. All, Can we run a set up table job (LO datasources) (in case of purchasing program RMCENEUA) parallely in (R/3)production environment by checking the block documnet option with different document date in selection ? The reason for this is that if we go with this option we can schedule. When running the setup for application 02 (TR OLI3BW), the table was not filled: running RSA3 with no restrictions did not retrieve any records. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . 2LIS_02_SRV (obsolete) The 2LIS_02_SRV data structure is new for the EHP3 and there are some steps to activating it. Home. Setup: Material Movemts. I then delete the Contents of Setup table for Application '02' - message ""setup tables deleted successfully"". Table Coep BW Extractors in SAP (20 BW Datasources) Login; Become a Premium Member; SAP TCodes;. (2LIS_11_V_ITM) - /IMO/CMSD16 . (Which acts also as delta queue similar to RSA7). 4. I now am trying to get publishing back on track. But for 2lis_02_sgr we are able to get records only for "Pruch Docu Catgory" = F(Purchase Order). Data Source:2LIS_02_ITM, Note: Field LOEKZ of table EKPO is the deletion indicator for an item in P20. 13. 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. no (EBLEP) and delivery schedule line counter (ETENR). BEDAT. Inventory Controlling (application 03): 2LIS_03_BX. but not in. (2LIS_11_V_ITM) - /IMO/CMSD16 . This counter determines the number of deliveries based on the GR document items. TXTMD. When using a Join of 2LIS_03_BF ( for Good Movement (E) from MSEG data ) and 2LIS_06_INV ( for Invoice (Q) from EKBE data ) ; In general the DBMTR is same in MSEG and EKBE, but there are few scenarios when they are. IF i_datasource = '2LIS_02_ITM'. 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. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 5 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 6 :670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL . Block user to modify to modify purchase. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 3. I could not find any Info on this kind of issue in SDN. Login; Become a Premium Member; SAP TCodes; Tables. 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. From. FIELD-SYMBOLS: <LS_DATA> TYPE MC02M_0ITM, <LV_KUNNR> TYPE EBAN-KUNNR,. you can store the all the Purchase Orders in one InfoProvider ( restricting on doc. EKKO - Header. No. It is actually a calculated result (rounding) in 2LIS_02_SCL and 2LIS_02_ITM. The migration of DataSource 0FI_AP_3. 0. Transformation Rule. To stop the access from outside we use t-code SM01 to. Purchase Info Record Tables. on BW side make sure Delta mechanism and init load is deleted. Udo. By debugging function module MCEX02_PREPARE_INFO it was found that the field UPDACT in table TMCEXACT. SAP Table Field : BUDAT - Posting Date Top 200 SAP Tables containing the field/column BUDAT. (2LIS_11_V_ITM) - /IMO/SD_IS16 . 0. Recommence extraction into BW from the modified R/3. 01. 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. RemoteCube-Compatible. Consider Process Key 2 for GR amount and Process Key 3 for Invoice Amount. WITH KEY supkz = '2'. Like I activated the datasources in LBWE than I intialised all datasources. g. 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. from the standard tables using a Business content Data Source the Data should be Extracted to BW system. 2LIS_11_VAKON: Order Condition Data. Technical name: 2LIS_02_HDR . Thanks for the quick response. If you followed below steps, no chance to miss single reocrd. Where in BW should be stored the data about secondary costs on purchase (acquisition) which evaluate the real price of goods?. The DSO provides insight into the delivery service of vendors by exploring. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. (2LIS_11_VAHDR). I am tyring to fill the setup tables for application 2LIS_02_* using tcode OLI3BW , but it is taking a lot of time to fill the data even if i enter selection document date for one year every time, i want to fill the setup tables separately for each data source. Follow the below steps to get the lost delta, will be useful for any loads. When does it happen that 2LIS_02_ITM does not add. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. About this page This is a preview of a SAP. 3. Hi All, I had to add a field from table EKPO to 2lis_02_itm datasource, I did the append structure to MC02M_0ITM straight away and filled in the exit. Currently i need direct t-codes to. All 3 2lis_02_itm, hdr and scl were enhanced to add additional fields. This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). LOEKZ is only an indicator/flag. 02. Application DataSource 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. This DataStore Object (DSO) contains the invoice verification data on a granular level. Purchasing. I know the history has it but, I want to know what is the source for BUDAT in 2LIS_02_ITM. SD: Delivery Header Data (2LIS_12_VCHDR) - /IMO/CMSD20 . The system therefore only executes a delta update for this DataSource if. READ TABLE lt_ekko into wa_ekkoTable YBWMAPPING is used by the class YCL_BW_MAPPING. Hi, I am using 2lis_02_itm and 2lis_02_hdr. SAP. PO Cancellation of data record Entry. I am also planning to enhance these extractors for few additional fields which are not extracted by these standard extractors. Delta queue maintenance. 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. 0LOG_SYS_BE. 5. 1. Enhancement of 2LIS_02_ITM from structure RM06E. Step 2 Create Target table where you want to persist the data. Quantity ordered (SCLQTY) = 20. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17. Targets are going to be different for delta and full. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. MM-PUR: Purchase Order Delivery (Items) - /IMO/PUR_D21. 2008 i have executed Initial Load from BI. setup table are built sucessful and he collects data (setuolog) But the extractor checker doesn't work he collects 0 data.