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. 2) From the Scheduler dropdown, select the Repair Full Request Option. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. For information, I had the same problem with 2LIS_02_ITM. 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. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. Thanks for the quick response. This is available in SBIW. It was huge reload project for us which continued for a. 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. RSA3 for 2LIS_02_ITM,2LIS_02_SCL , 2LIS_03_BX,. Run the collective run, so all the data is sent into the delta queues. If no data. 2LIS_02_SRV (obsolete) The 2LIS_02_SRV data structure is new for the EHP3 and there are some steps to activating it. (2LIS_02_ITM). you can store the all the Purchase Orders in one InfoProvider ( restricting on doc. The counted number depends on how often a material appears in a GR document. If you click that dropdown you will find the tables for your Datasource. 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. so I add field CHARG into that datasource. WHEN '2LIS_02_ITM'. png. and Yes,I have DELETED setup tables data prior to running the Setup process. Step-4: Creating function modules for each extractor enhancement. This DSO (advanced) contains delivery related indicators and key figures for purchase order items. We have an infocube up and running in production for couple of years, now have to add 2 fields in the extractor which are part of standard extractor 2lis_02_itm. RSS Feed. Creating an infopackage using the "full update" option: to do this I activated the extract structure MC02M_0ITM, i. This counter determines the number of deliveries based on the GR document items. no (EBLEP) and delivery schedule line counter (ETENR). Both the datasource do not have Material document number (BELNR) field. But in RSA7 , there are 0 recrods . EKES is a standard Purchasing Transparent Table in SAP MM application, which stores Vendor Confirmations data. Comparing DataSource 2LIS_02_SCL to ME80FN. RSS Feed. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 3 :. It s failing for only 2LIS_02_ITM only. However, when we do delta-load, none of the account. I can see the data for other datasrcs related to purchasing like 2lis_02_itm data in rsa3 . 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. 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. 3. 0. After all the fixes were done we can think (did the same kind of fix for all 3), 2lis_02_itm refuse to send us any delta records. Maintained extract structure for 2LIS_02_ITM (LBWE) 2. This table stores the mapping rules. Thanks for the quick response. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. MSEG MENGE. Rohan, Looking at EKBE is correct. Relevancy Factor: 6. ) 2LIS_02_ITM. Not just "LO DataSources" because there are some that don't use this feature. Please note , Everything is fine with setup table data , update rule ( Overwrite mode) and other BW part. Environment. 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 :. RSS Feed. I know the history has it but, I want to know what is the source for BUDAT in 2LIS_02_ITM. we have the V3 update job, running every 15 minutes. Select display Data Source (Ctr+F2). Customer-Defined DataSource Logistics Management of Extract Structures Initialization Fill Recompiled Tables Application-Specific Recompilation Purchasing – Carry Out Recompilation. 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. 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. In the ECC table EKET these two fields have changed for a given purchase order but the change is not. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17. Total number of tables/structures containing this field is 7006. For all LO datasources logic is written in function module MCEX_BW_LO_API. We could able to see the enahnced field data in RSA3 , but after making any change in ME22n its not p. 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. 0. If a data inbound layer persistence and/or a corporate memory persistence is used, the transformation from this DataStore object (advanced) to the InfoSource directly assigns the fields of the DataStore object to the InfoSource. The modeling property Inbound table as extended table has been turned on. See SAP Service Marketplace, SAP Note 0448600 for more information on prerequisites. the situation is that when I run delta it fetches 0 records. and then go to BW side and replicate the Datasource. 2LIS_03_UM. Presss F5 and get inside the form “select_option_fill”. About this page This is a preview of a SAP. When I try to do this in the conventional way (in transaction RSA6, button 'E. Import the table definition from the Metadata Repository in the Data store Explorer and use it as source in a data flow. 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. Read more. 100 -> 100 -> 200. Extraction Table PFO_GO_00IV (Portfolio Assignment) - 13 : 2LIS_12_VCITM Delivery Item Data SD - Sales and Distribution: 14 :Use. BW-Rebuild for MC02M_0CGR Storage. EKKO. To reach the customising node use transaction OMGO. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. Issues in Filling Setup table for 2LIS_02_HDR | SAP Community Relevancy Factor: 1. The account assignment category determines the account assignment data for an item, such as cost center and account number. 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". This DataSource extracts Accounts Payable Accounting line items from tables BSIK (open items) and BSAK (cleared items) in the R/3 source system. For purchasing datasources 2lis_02_itm and 2lis_02_sgr . MC02M_OHDR. 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:. g quantities),. SD: Delivery Header Data (2LIS_12_VCHDR) - /IMO/CMSD20 . AWS Documentation AWS Supply Chain User. 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. Description: Sales-Shipping Allocation Item Data. Maintain Extract Structure MC02M_0ITM. SYDAT is Item created on - EKPO-AEDAT. We appended cost center and cost element to this extractor using FUNCTION EXIT_SAPLEINS_001. SAP R/3 Enterprise. I have loaded an initial load to my ODS (0BBP_PO) and also setup a delta. I'm using OLIG and OLIGBW to fill setup tables but there are certain. These documents are also not getting filled into Setup Table by OLI3BW. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Then I. 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:. Thanks,-af. all fields of DataSource 2LIS_12_VCITM. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW > Settings for. 0B) ( 2LIS_11_VAITM ), is used to update the Media Product Sales (M/PS) data targets, for which the SD order document is used as the basis. Read more. Relevancy Factor: 30. then data inconsistency will be happen. We can replace the contents of internal dd_belnr through flat file upload. choose your characteristics and key figures. SD Sales Orders. DATA SOURCE NAMING CONVENTIONS : 11 ----- 2LIS_11_VAHDR / 2LIS_11_VAITM / 2LIS_11_VASCL 2LIS ----- Standard refer for every LO Data Source. Sap Mm Contract Tables in SAP. 2LIS_02_ITM - Set up Table. MM - Materials Management: 10 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 11 : 2LIS_13_VDITM: Billing. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . Purchase Order Tables. . Use. I know that For purchase order details we used 2 datasources 1. This is what the procedure i used (please tell me if i did something wrong): 1. 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. You should find table names here. Use. Check the data in T- Code RSA3. PO Cancellation of data record Entry. . 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. 02. better till first info provider DSO. Using this approach, the advantages are: The code is limited to few numbers of. where ebeln = c_t_data-ebeln. Inventory Controlling (application 03): 2LIS_03_BX. Two lines are extracted. I am also planning to enhance these extractors for few additional fields which are not extracted by these standard extractors. I have also deleted the setup tables and filled them again. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. following fields of. This form assigns the range entered in selection screen to internal table dd_belnr. So in the PSA,I am getting 2 records for the PO which has. Before fill setup I have done pre requisites as follow, 01. Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. In combination with the InfoSources Purchasing Data (Document Item Level). Use. 3. 3. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). Mvke Table BW Extractors in SAP (16 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. Also, please make sure that your answer complies with our Rules of Engagement. That means that you can use this DataSource both for data replication in a BW system (SAP Business. Customized BADI Name – ZPP_DS_2LIS_02_ITM. EKAB is a standard Purchasing Transparent Table in SAP MM application, which stores Release Documentation data. (2lis_02_scn,2lis_02_cgr, 2LIS_02_SGR,2lis_02_itm) when i run the statistical setup by using OLI3BW i am geting data of ITM AND SGR data sorses into setup tables, but i am not getting data of remaining data sorses , data is present in the tables of that data sorses. I therefore tried to use the FULL LOAD for those datasources (2LIS_02_HDR, 2LIS_02_ITM und 2LIS_02_SCL). 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. This InfoSource contains the structure to provide purchase data on item level into the EDW Core Layer. Step two: Delete delta entries in RSA7. I am trying to fill up the SETUP tables. CM SD: Sales-Shipping Allocation Item Data (2LIS_11_V_ITM) - /IM: CM SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD: CM SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD1:. eg: if i do the following action: Fill 1 -> Delete - Fill 2. With no data in setup tables, rsa7, sm13. 2LIS_11_VAKON: Order Condition Data. Source table: EKET (Scheduling Agreement Delivery Schedule Lines) Extract structure: MC02M_0SCL. Step 2: Replicate datasources in BW -PRD. 1. Z2LIS_02_ ITM_SRV. Table of Contents SAP BW/4HANA Content Add-On. e. Every works ok when executing setup of statistical tables. I'm using OLIG and OLIGBW to fill setup tables but there are certain documents/contracts I can. Pls clarify if both delta and full load can happen in parallel for the same data source?Vbak Table Data Source BW Datasources. 2. DataStore object (advanced): SD: Billing Document Item Data (2LIS_13_VDITM) - /IMO/CMSD31. While doing the statistical setup i am using the T. Situation 2. of entries in Set up tables. (Which acts also as delta queue similar to RSA7). Click ‘Yes’ to proceed further. Datasource is in active mode. Settings: Purchasing. 05. . This gives me a message 'Date fields for info structure S032 are not. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. When does it happen that 2LIS_02_ITM does not add. Figure 7: BW Control Table – Fields . 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. RSA3 for 2LIS_02_ITM,2LIS_02_SCL , 2LIS_03_BX, 2LIS_03_UM shows data but it does not get updated to the cube ( 0PUR_C01, 0IC_C03). 2LIS_02_ITM, 2LIS_02_HDR, 2LIS_* , KBA , BC-BW , BW Service API , BW-BCT-MM. The configuration of the table looks as follows. The data is not updated into the upur_c01 cube . You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Currently i need direct t-codes to. BSART. Determine Industry Sector. Create column table “02_ITM” as (select * from “INF627126″. and added the fields in ODS( Key Purchasing Document and Document Item) I did the testing , and found that the fields are not correctly populated in BW. Application Component. In EKET Table the primary key is based on 3 fields. Table EKKN filed PS_PSP_PNR gives you the WBS element associated with the PO. 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. 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. TABW is a standard Basic Functions Transparent Table in SAP FI application, which stores Asset transaction types data. 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. Pls reply needed urgent,i'm. then go to T- Code OLI9BW. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. 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. SAP BW Datasource : 2LIS_02_SCL - Purchasing Data (Schedule Line Level). I'm want to use some 2LIS_02* extractors (2LIS_02_HDR, 2LIS_02_ITM and 2LIS_02_SCL) to cubes 0PUR_C01 and 0PUR_C04. Data Source:2LIS_02_ITM. I saved and Activated the data source. 0. 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 Data Schedule Lines (2LIS_02_SCL) -. 12. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: Glossary/Terms related to ERNAM ProfileWhen extracting from a single table, do that in a standard data flow. Because when you fill any Purchasing DataSource (i. MC02M_0CGR Storage. that all records from 2LIS_02_ITM are deleted in the START routine. News & Insights. (2LIS_11_V_ITM) - /IMO/CMSD16 . 2001. In ekpo screenshot you can find final Invoice flag is set (EKPO-EREKZ) for all the PO line. SAP delivers the following example BEx queries on top of MultiProviders Sales Overview. I wonder why the same is not getting extracted when I check in RSA3 for Data Source 2LIS_02_ITM. 2LIS_02_HDR purchasing order header level data,2LIS_02_ITM purchasing order item level data,2LIS_02_SCL purchasing order schedule level data. Home. Filled with the 2-digit logical backend system (based on LOGSY) Logical System Backend. If no data inbound. 3) Check the Indicate. Replicate the same in BW system. 799 Views. Thank-You. save the package and press create. also check in BD87. SAP Tables SAP Table Fields (New) SAP Glossary Search. Setup Table. 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. Table of Contents SAP BW/4HANA Content Add-On. Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. g. Why are the setup tables not filled?If additional information is needed for the tables please let me know. BW Reorganization Store for MC11V_0ITM. ODP Semantics. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 . 2lis_02_itm uses EKKO and EKPO tables etc. Just as try we deleted Setup table and fill it with PO documents having this issue again but no use. 2LIS_02_ITM : MC02M_0ITMSETUP : Storage BW Setup for MC02M_OITM : Purchasing :. 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. now i want to fill setup tables for below datasources, can you suggest what are tcodes to fill up setup tables for below datasources. such as material, purchase order quantity, order unit, net price, and so on Show TOC MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/PUR_IS11 InfoSource: /IMO/PUR_IS11 This InfoSource contains the structure to provide purchase data on item level into the EDW Core Layer. Jun 15, 2007 at 04:37 PM. That means setup process wasn't happen correctly. Hi We are using the following logic to enhance 2lis_02_itm with different fields from diff tables. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Item Level) ( 2LIS_02_ITM ). MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 - SAP Help Portal Relevancy Factor: 10. 1) 1) Create/Find a Full Repair Infopackage in 2LIS_11_VASCL datasource in BW system. Fill setup table. (2LIS_11_V_ITM) - /IMO/CMSD16 . Former Member. 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. Purchasing. Recommence extraction into BW from the modified R/3. 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. These indicators and key figures are based on the associated confirmation and goods receipt documents. Code - 'oli2bw'. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 2. Unlock users out of R/3. Is it possible to get this PO Delivery date in to our data source 2lis_02_itm which has PO Doc no (EBELN) and PO item. Follow. In the second InfoProvider, you can. i need to get the data from different tables. In this extractor we have enhanced "PS_PSP_PNR" (WBS Element) field whose values are being stored in "Account Assignment in Purchasing Document" table. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . EKBE is a standard Purchasing Transparent Table in SAP MM application, which stores History per Purchasing Document data. 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. 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. Name of Target InfoObject. (2LIS_11_VAHDR). We have data sources 2LIS_02_ITM, 2LIS_02_CGR, 2LIS_02_SCR and 2LIS_02_SGR activated and up and running delta properly. Maintain enhancement in LEINS001. This is derived from the statisitcs updating facility maintained for updating the LIS (PURCHIS) tables in R/3. LIS is customer generated extractors. 2016 at 02:59 PM GTM 2LIS_46_ITM extraction. MC11VA0STH: Extraction MD Order Header Status for DataSource 2LIS_11_VASTH. LO Cockpit - Basic Question. FI and COPA is easy to get , the hardest to get at is the LO extractors. but not in. I am trying to extract data from datasource 2lis_02_hdr using lo-cockpit and I have followed the below steps. I have already maintain datasource 2LIS_02_ITM through LBWE. , Z1, and we try to add this new field into the LO Cookpit datasource 2LIS_02_ITM. I have already done the following steps: 1 - Transaction SBIW: Settings for Application-Specific DataSources (PI) Logistics. 5. 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 . etc. 339 Views. This InfoSource provides the transaction data from the production process, with reference to the order header and item. Setup: Material Movemts. Step 2: In the table TCDOB put the table name in TABNAME field, you will get some name in OBJECT. FIELD-SYMBOLS: <LS_DATA> TYPE MC02M_0ITM, <LV_KUNNR> TYPE EBAN-KUNNR,. Note: Field COMPL_DEL of BW is mapped via direct assignment to ECC field ELIKZ ( Delivery. Source System for R/3 Entry*. The fields concerned are located in one of the Purchase Order screens (ME21). Symptom. Table of Contents SAP BW/4HANA Content Add-On. I have pasted the eror message below for reference. The following has all been done. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. This document has 2 parts. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. These documents are also not getting filled into Setup Table by OLI3BW. But <u>it's work with a FULL infopackage</u>. The account. "2LIS_02_SCN MM MC02M_0SCN Achieved Performance: Confirmation of. MC02M_0SCLSETUP. when I used INIT or DELTA infopackage. Once we execute, it would give us the below screen for confirmation. In EHP 3 the tables are already delivered to the customer enhanced, the activation will only. Direct Access Enabled. 2LIS_02_SRV(obsolete) BW-BCT-PA - Personnel Management . ECC -> SE11 -> ROOSOURCE -> Both "GENDELTAFD" and "GENDELTATP" are empty too. SCL dS will trigger delta with GR and IR. cat = F ) . These fields are populated in the extractor and not stored in any tables. 01. no (EBELP). Purchasing (application 02): 2LIS_02_ITM. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :Note. 2. 2LIS_02_SCL. If I missed to search something please provide that. I have checked unhide in rsa6, but still its not displaying any values. Everything went fine, up to the point wherein i was supposed to perform the [Delete set-up tables / perform extraction] part of the process. Purchase Invoice Tables. A goods movement is posted with the following information: Posting date (BUDAT) = 05. 63 Views. 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:. I am trying to extract data from the EKKO and EKPO tables using the purchasing extractors 2lis_02_itm and 2lis_02_hdr. If you choose the Header/Item Data view in the transaction ME80FN, you can compare the data in the following DataSource fields with the original document data in the ERP system: MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. with different condition types fromo KONV table . Sap Tcode Ksbt Tables in SAP. Field VDATU has the same name as Update Date for Statistics Update for DataSources 2LIS_11_VAITM and 2LIS_11_VASCL. 2LIS_02_ITM - Adding field problem | SAP Community Relevancy Factor: 1. 2. As of R/3 Release 4. The issue is when I ONLY change the. So this thing need to be keep in mind while reconciling with ECC table specially for purchasing data. Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04.