5B. Table of Origin. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Z2LIS_02_ ITM_SRV. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. When is it necessary to reload the setup table? For Example. It is actually a calculated result (rounding) in 2LIS_02_SCL and 2LIS_02_ITM. However, when I want to re-extract ""Purchasing"" I get a message ""Data source 2LIS_02_HDR contains data still to be transferred"". e, 2lis_02_itm, or 2lis_02_hdr), both the header and the item gets filled up. Table: EKPO. Marco. But <u>it's work with a FULL infopackage</u>. Apply the changes / Transport. 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. 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. png. excuse me for this message, but I have a problem and I think you could help me. Rohan, Looking at EKBE is correct. 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. I checked the function module also , but still in process, any suggestions would be greatly appreciated. 3. 2lis 02 Itm Tables Most important Database Tables for 1. Wanted to know whether is there any way to find out how many entries are remaining in setup table to be transfered to BW. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. Overall Picking/Putaway Status. 3 ; SAP NetWeaver 7. 100 -> 100 -> 200. Hi Fabio, No You cannot do a setup for 2LIS_02_ITM only, You can only do a setup for the whole 2LIS_02. Also, please make sure that your answer complies with our Rules of Engagement. If a data inbound layer persistence and/or a corporate memory persistence is used, the transformation from this DataStore. Product. Technical Name of Target InfoObject. Thanks and regards. TXTMD1. SAP R/3 Enterprise all versions Keywords. I have gone through many threads with similar subject but dint got proper solution for this. For purchasing datasources 2lis_02_itm and 2lis_02_sgr . In the ECC table EKET these two fields have changed for a given purchase order but the change is not. Consider Process Key 2 for GR amount and Process Key 3 for Invoice Amount. Test using RODPS_REPL_TEST , SUM = 0 in the result. Run DTP with extraction mode โDeltaโ ( 1 st time it extracts data from setup table). I'm trying to use datasource 2LIS_02_CGR in addition to 2LIS_02_ITM already in use. PO Cancellation of data record Entry. The DSO provides insight into the delivery service of vendors by exploring deviations across the. SAP R/3 Enterprise all versions Keywords. Available as of Plug-In Release. But when the user changes only the account assignment of an outline agreement , without changing any other fields (e. The details are as below:2LIS_11_VAITM Data Source is not fetching data | SCN. Relevancy Factor: 1. 0B) - SAP Documentation. Then went to BW , installed the cube , update rules and the infosources. 2) From the Scheduler dropdown, select the Repair Full Request Option. One or more purchasing documents or items are not extracted either by a full load or a delta loads using some of the following DataSources: 2LIS_02_ACC, 2LIS_02_CGR, 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL, 2LIS_02_SCN, 2LIS_02_SGR. But this d/s 2LIS_02_SRV doesnt pick/identify the deleted service entry sheets. MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. Targets are going to be different for delta and full. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. then go to T- Code OLI9BW. RSS Feed. 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. (2LIS_13_VDITM). It is from BEDAT from EKKO and EKBE. Is there any particular reason? I looked up the configuration of the movement types by going into. request - The Setup-tables are populated in a separate IMG-process (tcode: SBIW): "Data Transfer to the SAP Business Information Warehouse -> Settings for Application-Specific DataSources (PI) -> Logistics -> Managing. The 2lis_02_itm documentation says that the field NETWR (Net PO value) is picked up directly from table field EKPO-NETWR. 11. 2LIS_02_ITM: DS only for Direct Access, 2181511: 0MM_PUR_PO_SCL: 2LIS_02_SCL: DS only for Direct Access, 2181511: 0MM_PUR_PO_SCN: 2LIS_02_SCN. Dear All, I have activated BI Contents: 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_HCL. 2001. I filled the setup table in the development system and did an Initialize with data transfer. Determine Industry Sector. 2008 i have executed Initial Load from BI. EKKO. 02. 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. 0. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. Purchasing Organization Tables. Use. Type of DataSource. 6C. Delivery Item . Like I activated the datasources in LBWE than I intialised all datasources. hi Check in Base tables ๐. In R/3 my setup tables are filled : MC02M_0ITMSETUP . I have already maintain datasource 2LIS_02_ITM through LBWE. I can see the data for other datasrcs related to purchasing like 2lis_02_itm data in rsa3 . The following jobs move the data from the outbound queue to BW. And after the setup table is filled, data in 2LIS_02_SRV gets duplicated. Control record it will be having information like Idoc number, message type, idoc type, sender, receiver etc. Field in Table of Origin. a few weeks ago delta in BW stopped working. There is a requirement to load full load to BW system from 2LIS_02_ITM data source. In LBWE, its showing that LOEKZ is taken from EKPO. 2lis_11_v_itm. 2LIS_02_ITM. 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. Product. also full update of 2LIS_13_VDITM featches only records that have been uploaded with initial load. The system therefore only executes a delta update for this DataSource if. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. and do repair Full for whole data. For more information on this topic, refer to the. Sap Tables in SAP. I need to enhance the Datasource 2LIS_02_ITM. I use the standard extractor 2LIS_02_ITM (order positions) with the update mode "Direct Delta" and apanded Z-fields. 2LIS_02_SRV(obsolete) BW-BCT-PA - Personnel Management . The start routine for the updates ensures that only orders and free-of-charge orders are updated in the DataStore object. Technical name: 2LIS_02_HDR . You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. (2LIS_11_V_ITM) - /IMO/CMSD16 . Goto LBWE transaction in R/3. You get this message , when you execute MCB_ " View/table V_TMCLBW can only be displayed and maintained with restrictions" 2. Situation 2. Clear setup tables in LBWG. Source Tables (Function Module): MCEX_BW_LO_API (Function Module) SAP Help, Wiki, Q&A and other resources for 2LIS_03_BF. Press F8 and program will stop at this step. However, InfoCube for Purchasing ( 0PUR_C01) is already active in the system and delta are being loaded into it on a regular. where this is using a standard datasource 2lis_02_ITM and 2LIS_02_SCL and i have acitvated this standard cube 0pur_c01. They are needed in BW and not in R/3. 100 -> 100 -> 200. 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. Purchasing 2LIS_02_CGR MC02M_0CGRSETUP BW-Rebuild for. 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. I've done all the "tasks" for setup tables, but i don't have 0PROCESSKEY. Tables for 2LIS_02_ITM. 04. Then I will build a ODS on top of these extractors. This is available in SBIW. l_index = sy-tabix. ) 2LIS_02_ITM. now i want to fill setup tables for below datasources, can you suggest what are tcodes to fill up setup tables for below datasources. RSEG is a standard Invoice Verification Transparent Table in SAP MM application, which stores Document Item: Incoming Invoice data. SAP delivers the following example BEx queries on top of MultiProviders Sales Overview. e. 2LIS_03_BF. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). 2. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL. 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:. Technical Name of Target InfoObject. MC11V_0SCL: Extraction SD Sales BW: Allocation Schedule Line for. Ship-to Party. with SE11 transaction you can see these tables. Folder: BW Setup for MC02M_0ACC. Delta queue maintenance. FAQ: Setup table filling with 2LIS* extractors. It was huge reload project for us which continued for a. Before fill setup I have done pre requisites as follow, 01. Data load for :2LIS_02_HDR. Login; Become a Premium Member; SAP TCodes; SAP Tables; SAP Table Fields; SAP Glossary Search; SAP FMs;. Step 3: Move BW TRs to BW PRD system. Even I have tried again by deleting the setup tables & then fileed it but syill cant see data only in 2lis_02_sclI am loading 0PUR_O01 from 2LIS_02_ITM/SGR/CGR and SCN. Sap Supply Chain Management Tables in SAP. This is available in SBIW. after this load you can run deltas. Purchasing Data (Schedule Line Level) NA. Transformation. You should find table names here. READ TABLE xmcekkn. 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. Purchasing. This DSO contains delivery related indicators and key figures for purchase order items. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. I have been using DataSource: 2LIS_02_ITM for couple of months and I have loaded data into (Full and Deltas). I am able to see the newly added field in the structure, However when I test the datasourcein RSA3. 2LIS_11_VAKON: Order Condition Data. Figure 8: BW Control Table โ Entry Help/Check . Use corresponding exit FM as template and copy the import, Export, Table, Exception. Not just "LO DataSources" because there are some that don't use this feature. 2LIS_02_HDR -> Purchasing Header Tables: EKKO PO Data (Header) (EBELN, BSTYP, BSART) EKPA- Partner Roles 2LIS_02_ITM -> Purchasing Item Tables: EKKO PO Data (Header) (EBELN, BSTYP, BSART) EKPO PO Data (Item) (EBELN, EBELP, MATNR) 2LIS_02_SCL > Purchasing Schedule Line Tables: EKKO PO Data. SYDAT is Item created on - EKPO-AEDAT. EKAB is a standard Purchasing Transparent Table in SAP MM application, which stores Release Documentation data. 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. SAP Table Field : ERNAM - Created by Top 200 SAP Tables containing the field/column ERNAM. 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. Best Answer. 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:. Maintain Extract Structure MC02M_0ITM. and enhanced the datasources ITM and SCL adding one Char in. "2LIS_02_SCN MM MC02M_0SCN Achieved Performance: Confirmation of. Step three:. 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. Setup Table. Thanks,-af. 3. This. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 :. iam loding data for purchasing data using 4 data sorses. 0. 2LIS_02_ITM - Adding field problem | SAP Community Relevancy Factor: 1. Invoice Verification. Datasource Jest Table BW Extractors in SAP (25 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. xmcekpo-ZZKUNNR = i_t_ekpo-kunnr. g If a PO item has qty 10 and Price 5 , then the field ekpo-netwr is 50 ( = 10 * 5) Now if this PO item has 3 invoices. but not in. KOSTK. "Document data restriction" when filling setup table. Just as try we deleted Setup table and fill it with PO documents having this issue again but no use. Purchasing 2LIS_02_HDR MC02M_0HDRSETUP Storage BW Setup for. I have loaded an initial load to my ODS (0BBP_PO) and also setup a delta. Table Coep BW Extractors in SAP (20 BW Datasources) Login; Become a Premium Member; SAP TCodes;. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. These infoprovder will not have a field for ktmng rather it will have PO specific fields such as PO no, po qty, PO Agreement no. DataStore object (advanced): SD: Billing Document Item Data (2LIS_13_VDITM) - /IMO/CMSD31. The InfoSource for the SD sales document Order Item Data (as of 2. Data Source:2LIS_02_ITM, Note: Field LOEKZ of table EKPO is the deletion indicator for an item in P20. Data Source:2LIS_02_ITM. RSS Feed. or alternatively you can build your own custom extractor using purchasing tables EKKO,. 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)). 2LIS_02_HDR Purchasing Data (Header Level) MM - Materials Management: 13 :Structure of 2LIS_02_ITM (MCEKPO) The issue i am facing is EKKOL (Condition Group with Vendor) is a standard field of table EKPO. BW-BCT-PM (Plant Maintenance). Description: Sales-Shipping Allocation Item Data. 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. The outbound queue is filled for the following queues in the. When I try to do this in the conventional way (in transaction RSA6, button 'E. Please provide step by step guidance for how to load data to 2LIS_02_HDR? I have tried to search on SCN but could not get any helpful document. 4. Please note , Everything is fine with setup table data , update rule ( Overwrite mode) and other BW part. 14. The counted number depends on how often a material appears in a GR document. select * into table lt_ekko from ekko for all entries in c_t_data. After that, AWS Supply Chain automatically creates the Amazon S3 paths and ingests data from the SAP source tables. Filled with the 2-digit logical backend system (based on LOGSY) Logical System Backend. 123456 30 - 123456 40 - 123456 50 - 2lis_02_itm Setup Table. and Yes,I have DELETED setup tables data prior to running the Setup process. RSS Feed. 2LIS_02_ITM - Set up Table. ECC -> RSA2 -> Generic Delta -> field name is empty. When I try to load setup data I got this message in setup table. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. LOOP AT c_t_data INTO mc02m_0itm. , Z1, and we try to add this new field into the LO Cookpit datasource 2LIS_02_ITM. BEDAT. So this thing need to be keep in mind while reconciling with ECC table specially for purchasing data. READ TABLE lt_ekko into wa_ekkoTable YBWMAPPING is used by the class YCL_BW_MAPPING. SAP Tables SAP Table Fields (New) SAP Glossary Search;. In the second InfoProvider, you can. e. 4 ; SAP NetWeaver 7. That means that you can use this DataSource both for data replication in a BW system (SAP Business. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_04_P_COMP: Component View from PP/PP-PI: PP - Production Planning and Control:I will analyse notes 459517, 728687, 722339 y 869628. 2LIS_02_ITM. 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. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Unlock users out of R/3. Two lines are extracted. There is a table that maps movement type to process key. SAP. Delete the setup data (LBWG) 2. <LV_ADRNR> TYPE EBAN-ADRNR. Settings: Purchasing. Select the Data Source ( 2LIS_02_ITM ) 3. Replicate the datasource 2LIS_02_ITM and reinit and load data. Symptom. PO Doc no (EBELN), PO Itm. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. A goods movement is posted with the following information: Posting date (BUDAT) = 05. If you click that dropdown you will find the tables for your Datasource. Step 4) Choose the datasource 2LIS_02_ITM, which is purchasing data at Item level. Hi, I am using 2lis_02_itm and 2lis_02_hdr. LO-IO. FIELD-SYMBOLS: <LS_DATA> TYPE MC02M_0ITM, <LV_KUNNR> TYPE EBAN-KUNNR,. 3. after creating two tbls r created which will handle ur delta. I cannot see this same field under the same comm. In EKET Table the data is like. PLAF is a standard Master Data Transparent Table in SAP PP application, which stores Planned order data. Use. OLI1BW INVCO Stat. Transaction Data. Locate your Extractor (Datasource). BEDAT. Transport the Enhanced Data source to Source SAP system . Vote up 0 Vote down. 2lis_11_vahdr & 2lis_11_vaitm we have to use tcode OLI7BW. Go to. 5. enhancing through function module in 2lis_02_itm. Then I. LIS uses transparent tables. 12. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17. Hi We are using the following logic to enhance 2lis_02_itm with different fields from diff tables. SD Sales Orders. If no data inbound. Every works ok when executing setup of statistical tables. 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. 2. also check in BD87. Description. SD - Sales and Distribution: 3 : 2LIS_02_ITM: Purchasing data (Item Level) MM - Materials Management: 4 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 5 :. SAP BW/4HANA Business Content delivers. Use SAP BW/4HANA Business Content delivers this field-based DataStore Object (advanced) as a first persistence layer of data replicated into a SAP BW/4HANA data warehouse. 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. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 0LOG_SYS_BE. some sales document nos missed in bw. T-Code Purpose. 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. 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_12_VCITM: Delivery. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. LOOP AT c_t_data into l_2lis_02_itm. We are trying to implement Purchasing Information, Purchasing Data Item Level (2LIS_02_ITM), Purchasing Data Header Level (2LIS_02_HDR), Purchasing Data Schedule Line (2LIS_02_SCL), we have activated the extract structure, filled the set-up table and tried to look into the setup table but it does not show any records (even RSA3 do not show),. Table of Contents SAP BW/4HANA Content Add-On. Field in Table of Origin. Select display Data Source (Ctr+F2). 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. 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. - Process Key 003:IR. Go to Maintainance. (2LIS_11_V_ITM) - /IMO/SD_IS16 . that all records from 2LIS_02_ITM are deleted in the START routine. The modeling property Inbound table as extended table has been turned on. There will be no impact on existing processes. . Delta Process: Delta Queue based. Use. 3) Check the Indicate. Source System for R/3 Entry*. EKBE is a standard Purchasing Transparent Table in SAP MM application, which stores History per Purchasing Document data. 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. 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. I now am trying to get publishing back on track. MC02M_0CGRSETUP. 0. News & Insights. "Image/data in this KBA is from SAP internal systems. 5. ODP Semantics. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 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. choose your characteristics and key figures. MC02M_0CGR Storage. Follow. Set Up Table 2lis 02 Itm Tables Most important Database Tables for Set Up Table 2lis 02 Itm # TABLE Description Application Table Type; 1 : MARA: General Material Data Logistics - Material Master: Transparent Table 2 : VBAK: Sales Document: Header Data SD - Sales: Transparent Table 3 : BSEG: Accounting Document SegmentWhen answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. With this handy table you can find the status of your current job or previous initialization jobs through SM37. 2. When I try to do this in the conventional way (in transaction RSA6, button 'E. all fields of DataSource 2LIS_12_VCITM. SD-DLV: Sales Document: Order Delivery (2LIS_11_V_SSL) - /IMO/SD_IS17. 0. As of R/3 Release 4. They also extract GR and IR. But in case of LIS it is specific to the particular application. with different condition types fromo KONV table . In combination with the InfoSources Purchasing Data (Document Item Level). Sap Mm Contract Tables in SAP. Code - 'oli2bw'. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. By debugging function module MCEX02_PREPARE_INFO it was found that the field UPDACT in table TMCEXACT. FI and COPA is easy to get , the hardest to get at is the LO extractors. Mapped to InfoObject. 2016 at 02:59 PM GTM 2LIS_46_ITM extraction. Both the datasource do not have Material document number (BELNR) field. SETUP tables not filling for 2LIS_02_ITM. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. And after the setup table is filled, data in 2LIS_02_SRV gets duplicated. of entries in Set up tables. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. It's the pre-processing of Archive ( Archive Object is MM_EKKO ). We are about to delete setup tables for purchase (02) component and refill the setup tables. These Z-Fields are in the database table EKPO. There is a table that maps movement type to process key.