Maintain extract structure and datasource. 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. Delivery Item . Transformation Rule. So , how to know. Purchasing Data (Item Level) NA. Extraction Table PFO_GO_00IV (Portfolio Assignment) - 13 : 2LIS_12_VCITM Delivery Item Data SD - Sales and Distribution: 14 :Use. 2LIS_11_VAKON: Order Condition Data. This DSO (advanced) contains delivery related indicators and key figures for purchase order items. 3. Hi, I am using 2lis_02_itm and 2lis_02_hdr. no (EBELP). Note: As an alternative you can also use DHCDCVCDSEXTRE in SE16 which contains more or less the same information. But in case of LIS it is specific to the particular application. Datasource : 2LIS_11_V_ITM. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 0. MC02M_0ITM: Extraction Purchasing (Item) for DataSource 2LIS_02_ITM. This. transfered datasource 2LIS_02_ITM using tcode RSA5. BEDAT. . Wanted to know whether is there any way to find out how many entries are remaining in setup table to be transfered to BW. CLEAR LT_DATA. 2LIS_02_ITM Not Updating Setup Tables In Initialization Summary. The DSO is directly supplied from the Info/DataSource 2LIS_06_INV. (2LIS_11_V_ITM) - /IMO/CMSD16 . With this process chain, the initial data set is updated (initialization of the delta process) in the data targets affected (InfoArea. There I see data only for some extractors (2LIS_46_SCL and 2LIS_46_ITM) : see attached picture issue-gtm-01. Technically, during the full load, these items should be extracted with a recordmode = R. Tables for 2LIS_02_ITM. 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:. When I execute the RSA3 for different Datasources I can see data only in. With no data in setup tables, rsa7, sm13. Step 1: Move ECC TR to ECC- PRD system. I am trying to find the procedure / sequence in to carry out in. Because when you fill any Purchasing DataSource (i. Two lines are extracted. enhancing through function module in 2lis_02_itm. At the same time, they are also updated in the ODQDATA table. Purchasing. 5. Delta Process: Delta Queue based. 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. 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. The modeling property Inbound table as extended table has been turned on. Hi All, When a PO is posted the vaules are being picked by the 2LIS_02_ITM extractor. ”VT_2LIS_02_ITM”). On top of this, setup table was filled, but I see no data for 2lis_02_itm. This is available in SBIW. It is actually a calculated result (rounding) in 2LIS_02_SCL and 2LIS_02_ITM. Marco. 04. 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. Transaction Data. Suppose the sale order is 20 qty, there will be couple of records with 20 qty, doubling up the qty. where this is using a standard datasource 2lis_02_ITM and 2LIS_02_SCL and i have acitvated this standard cube 0pur_c01. 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. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. 2LIS_02_ITM and 2LIS_02_SCL datasources not only extract PO line items. 2LIS_02_ITM - Set up Table. The configuration of the table looks as follows. Quantity ordered (SCLQTY) = 20. (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 am using 2lis_02_itm and 2lis_02_hdr. I have already done the following steps: 1 - Transaction SBIW: Settings for Application-Specific DataSources (PI) Logistics. 0B, InfoSource 2LIS_04_P_MATNR replaces InfoSource 2LIS_04_S280. In the standard extractor 2LIS_02_ITM the field BADAT is check as Field only known in customer exit. 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. Go to LBWE (LO Cockpit), select DataSource 2LIS_02_SCL, click on Maintenance icon in Structure column, say Continue. To reach the customising node use transaction OMGO. Select display Data Source (Ctr+F2). These indicators and key figures are based on the associated confirmation and goods receipt documents. Please follow bellow steps: 1. create ur infostructure using MC21 transaction code. click the Filter combo to see the base tables, select MCEKKO MEMORY from the right and transfer it to the right section, click Continue, next click Yes. Check the source system connectivity. RSS Feed. Implemented class Name – ZCL_DS_2LIS_02_ITM. MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. Apply the changes / Transport. This counter determines the number of deliveries based on the GR document items. 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. 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. we have datas (ekko,ekpo) 2. LIS uses v1 and v2 update modes only. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. "2LIS_02_SCN MM MC02M_0SCN Achieved Performance: Confirmation of. 0. 2lis 11 Vaitm Tables BW Extractors in SAP (28 BW Datasources) Login; Become a Premium Member; SAP TCodes;. Folder: BW Setup for MC02M_0ACC. From. Yes. 02. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . But these datasource read data from EKKO, EKPO & EKBE table and material document number field is availble in EKBE. Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04. I have been using DataSource: 2LIS_02_ITM for couple of months and I have loaded data into (Full and Deltas). MC02M_0ACCSETUP. g. Maintain enhancement in LEINS001. LIS is customer generated extractors. Date of Purchasing Document. Comparing DataSource 2LIS_02_SGR to ME80FN. Jun 15, 2007 at 04:37 PM. LO-IO. Clear setup tables in LBWG. Determine Industry Sector. TXTMD. 6C. I was successful in extracting data for the 0PUR_C01 cube using the conventional 2LIS_02_S012 datasource. Purchasing. These Z-Fields are in the database table EKPO. Urgent help required. 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. In this case use FM EXIT_SAPLRSAP_001 as template. When is it necessary to reload the setup table? For Example. 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. Cannot see the data for datasrc 2lis_02_scl in RSA3. We do not need the history data for the 2 fields added. I executed infopackage full load for such sales documents, but 0records are received. Field in Table of Origin. Bobby. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 :. 0B) - SAP Documentation. LFA1 NAME1. #. The details are as below:2LIS_11_VAITM Data Source is not fetching data | SCN. Field in Table of Origin. 63 Views. Scheduling Agreement Tables. SAP delivers the following example BEx queries on top of MultiProviders Sales Overview. Prerequisites. You can look at the includes with *TOP* eg INCLUDE mcex02top. 2. Step. choose your characteristics and key figures. The fields concerned are located in one of the Purchase Order screens (ME21). MC11VA0STI: Extraction MD Order Item Status for DataSource 2LIS_11_VASTI. Inventory Controlling (application 03): 2LIS_03_BX. Transaction LBWQ in ECC: MCEX02. With this handy table you can find the status of your current job or previous initialization jobs through SM37. There is a table that maps movement type to process key. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. 3. Relevancy Factor: 30. I now am trying to get publishing back on track. 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 . so the standard. Purchasing 2LIS_02_CGR MC02M_0CGRSETUP BW-Rebuild for. Purchase Requisition Tables. Step two: Delete delta entries in RSA7. No. 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. But for 2lis_02_sgr we are able to get records only for "Pruch Docu Catgory" = F(Purchase Order). Billing Document Header Data. following fields of. Hi all! I have to initialize my BW data for the datasources: 2LIS_02_HDR 2LIS_02_ITM 2LIS_02_SCL 2LIS_02_S012 All my key figures are in "summation" mode, that means, no item should be loaded. 123456 30 - 123456 40 - 123456 50 - EKPO table r/3. Add a Comment. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. I know that For purchase order details we used 2 datasources 1. 5. you can store the all the Purchase Orders in one InfoProvider ( restricting on doc. From LBWE, I have added additional field from the right side pool of fields of extraction structure of 2LIS_02_ITM to the left, saved the structure. 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. BW-Rebuild for MC02M_0CGR Storage. Step 2: Replicate datasources in BW -PRD. See SAP Service Marketplace, SAP Note 0448600 for more information on prerequisites. These fields are populated in the extractor and not stored in any tables. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. Deleted the set up tables and ran OLI3BW and filled the set up tables. It looks to me, that it provides information about, whether it is a invoice, GR, and so on. In LBWE, its showing that LOEKZ is taken from EKPO. 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. Clear "LBWQ" 04. 2001. KNTTP – Account Assignment Category. In the datasource for Purchasing 2LIS_02_ITM and it is also there in the Schedule line item 2LIS_02_SCL, there is a field called BW: Transaction Key mapped to BWVORG in R/3. Some of the PO items are marked for deletion in the source system (LOEKZ = L). 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. 2. 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 can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. If you followed below steps, no chance to miss single reocrd. 12. Symptom. Customer-Defined DataSource Logistics Management of Extract Structures Initialization Fill Recompiled Tables Application-Specific Recompilation Purchasing – Carry Out Recompilation. Go to t-code ODQMON (in ECC). and enhanced the datasources ITM and SCL adding one Char in. The outbound queue is filled for the following queues in the. It s failing for only 2LIS_02_ITM only. I checked in RSA7 - all 5 DataSources are there. Then use the function Activate and Schedule to start the process chain according to your scheduling options. 2LIS_02_SRV (obsolete) The 2LIS_02_SRV data structure is new for the EHP3 and there are some steps to activating it. You can find more information in Special Features When Using PP-PI . 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. 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_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . Technical Name. Hi, Where can i find the t-codes for filling the setup table for all the logistics datasources. MM - Materials Management: 10 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 11 : 2LIS_13_VDITM: Billing. MC02M_OHDR. I could not find any Info on this kind of issue in SDN. Mapped to InfoObject. PO Cancellation of data record Entry. Vote up 0 Vote down. But this d/s 2LIS_02_SRV doesnt pick/identify the deleted service entry sheets. SAP Table Field : BUDAT - Posting Date Top 200 SAP Tables containing the field/column BUDAT. In rsa3 and in set up tables I see data fro 2LIS_02_ITM AND 2LIS_02_SCL. DataStore object (advanced): SD: Delivery Item Data (2LIS_12_VCITM) - /IMO/CMSD21. BEDAT. The extractor 2lis_02_itm will extract both Purchase Orders and Agreements. Purchasing 2LIS_02_HDR MC02M_0HDRSETUP Storage BW Setup for. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). Use. Copy & paste to SE37 eg for 2LIS_02_ITM , extractor MCEX_BW_LO_API is used. 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. The system therefore only executes a delta update for this DataSource if. Purchasing (application 02): 2LIS_02_ITM. Vote up 2 Vote down. 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. For information, I had the same problem with 2LIS_02_ITM. Deleted the Setup tables. READ TABLE i_t_ekpo WITH KEY ebeln = xmcekpo-ebeln ebelp = xmcekpo-ebelp. All 3 2lis_02_itm, hdr and scl were enhanced to add additional fields. 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 :. Figure 9: BW Control Table – Foreign. e. first run Init without datatransfer. 2LIS_02_ITM Purchasing Data (Item Level) MM - Materials Management: 14 : 2LIS_05_QE2 Inspection Result: Quantitative Data QM - Quality Management: 15 :Transformation. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. 2. This item won't be delete physically. EKAB is a standard Purchasing Transparent Table in SAP MM application, which stores Release Documentation data. ) 2LIS_02_ITM. 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:. But <u>it's work with a FULL infopackage</u>. g quantities),. save the package and press create. 48. The system therefore only executes a delta update for this DataSource if. Step 4) Choose the datasource 2LIS_02_ITM, which is purchasing data at Item level. Field PSTYP. The purchase order exists in APO in the form of an order. This DataStore Object (DSO) contains the invoice verification data on a granular level. You will find pool of objects there. By debugging function module MCEX02_PREPARE_INFO it was found that the field UPDACT in table TMCEXACT. We could able to see the enahnced field data in RSA3 , but after making any change in ME22n its not p. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. Clear "RSA7" 03. The 2lis_02_itm documentation says that the field NETWR (Net PO value) is picked up directly from table field EKPO-NETWR. 1. Situation 2. Use. In 2LIS_11_VAHDR however, the field VDATU contains the sold-to party's Requested Delivery Date. 4. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . You think 2LIS_06_INV extracts too many records either in the INIT, Delta or Full loads. The EKPO table ( Purchasing. Thanks for the quick response. 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. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 6 : 2LIS_11_VAITM: Sales Document Item Data SD - Sales and Distribution: 7 :2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_HDR:. But when the user changes only the account assignment of an outline agreement , without changing any other fields (e. Here is the code: LOOP AT xmcekpo. 0. 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). Press F8 and program will stop at this step. 5B. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 - SAP Help Portal Relevancy Factor: 10. Processkeys are maintained. I tried deleting the setup table (LBWG) and tried again initialization (OLI3BW) but I cant. Jan 29, 2008 at 06:41 PM. Step 2: In the table TCDOB put the table name in TABNAME field, you will get some name in OBJECT. Hi everyone, We are implementing the purchasing solution for the first time at the client. Comparing DataSource 2LIS_02_SCL to ME80FN. 2lis 04 P Arbpl Tables BW Datasources Most important BW Extractors for 2lis 04 P Arbpl Tables # BW DATASOURCE Description. Please note , Everything is fine with setup table data , update rule ( Overwrite mode) and other BW part. BW-BCT-PM (Plant Maintenance). Our delta queue for 2LIS_02_ITM and 2LIS_02_SCL was deleted from R3 by mistake. Thank you all four you responses. LBWE transaction - inactivate update, deleted setup tables in application component 02(MM) and also deleted any delta queue in /nrso2. 2. Follow the below steps to get the lost delta, will be useful for any loads. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 . AWS Documentation AWS Supply Chain User. Info Record Tables. 2. 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. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. BSART. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). 0. - Process Key 003:IR. We've created a new field called, e. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. RSS Feed. 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 :. Available as of Plug-In Release. Currently i need direct t-codes to. We can replace the contents of internal dd_belnr through flat file upload. 0. I have already maintain datasource 2LIS_02_ITM through LBWE. Rohan, Looking at EKBE is correct. 04. Delta queue maintenance. 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. RemoteCube-Compatible. Maintain Extract Structure MC02M_0ITM. 0. Before fill setup I have done pre requisites as follow, 01. Step 4: Delete set up table. In the ERP system, this information is contained in the following tables:. 5. WITH KEY supkz = '2'. Hi, Logistics application ""02 : Purchasing"" (HDR, ITM and SCL) is activated. 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. 0GN_R3_SSY. Product. Figure 8: BW Control Table – Entry Help/Check . Recommence extraction into BW from the modified R/3. 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. I have loaded an initial load to my ODS (0BBP_PO) and also setup a delta. The first extraction of the document itself getting two positive records in the same datapackage. 2001. on BW side make sure Delta mechanism and init load is deleted. and choose the industry sector "Standard (Core)". Note: Field COMPL_DEL of BW is mapped via direct assignment to ECC field ELIKZ ( Delivery. SAP BW Datasource : 2LIS_02_SCL - Purchasing Data (Schedule Line Level). Data source. Former Member. These fields are populated in the extractor and not stored in any tables. Udo. ebeln = xmcekpo-ebeln. 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. Sap Mm Contract Tables in SAP. Similarly, we can do the same steps (Step1-5). The Field (CHARG) not hidden. 01. I did a setup table fill-up of 2lis_03_bf and I'm seeing missing material documents with movement type 561. Step 2 Create Target table where you want to persist the data. Checked data in "RSA3" ex: 200 records. 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. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Environment. This is how the SAP has defined. Environment. 2. Use. I am trying to extract data from the EKKO and EKPO tables using the purchasing extractors 2lis_02_itm and 2lis_02_hdr. all fields of DataSource 2LIS_12_VCITM. 2LIS_02_ITM is a purchasing extractor, mkpf et mseg are inventory table. ) 2LIS_02_SCL & 2. For all LO datasources logic is written in function module MCEX_BW_LO_API. sap and forums i found out that for. 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.