Hi, Logistics application ""02 : Purchasing"" (HDR, ITM and SCL) is activated. Source Tables (Function Module): MCEX_BW_LO_API (Function Module) SAP Help, Wiki, Q&A and other resources for 2LIS_03_BF. Yes. BSTYP. Delete content of ODS/CUBE. Step-4: Creating function modules for each extractor enhancement. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). You can see the table in the above screen shot. We've created a new field called, e. This is how the SAP has defined. Click ‘Yes’ to proceed further. The first extraction of the document itself getting two positive records in the same datapackage. create ur infostructure using MC21 transaction code. 4. However, i wanted to try extraction using the newer 2LIS_02_ITM. Purchasing 2LIS_02_CGR MC02M_0CGRSETUP BW-Rebuild for. and had given the termination time . Purchasing (application 02): 2LIS_02_ITM. Add a Comment. As of R/3 Release 4. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . Settings: Purchasing. 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. Purchasing. no (EBELP). 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. But in case of LIS it is specific to the particular application. Use. 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. my question is what transaction code can I see this field in BW Table. I tried deleting the setup table (LBWG) and tried again initialization (OLI3BW) but I cant. 11. MC11V_0ITMSETUP. RSA3 for 2LIS_02_ITM,2LIS_02_SCL , 2LIS_03_BX,. EKES is a standard Purchasing Transparent Table in SAP MM application, which stores Vendor Confirmations data. 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. Thanks and regards. and choose the industry sector "Standard (Core)". Please provide a distinct answer and use the comment option for clarifying purposes. These fields are populated in the extractor and not stored in any tables. It is located under materials management --> Purchasing. We need the data for the two new fields going forward. 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. 2lis 11 Vaitm Ecc Source Tables BW Datasources Most important BW Extractors for 2lis 11 Vaitm Ecc Source Tables # BW DATASOURCE Description Application; 1 :. 48. Attributes; Attributes. Relevancy Factor: 1. RemoteCube Compatible. Quantity ordered (SCLQTY) = 20. I am trying to extract data from datasource 2lis_02_hdr using lo-cockpit and I have followed the below steps. Custom Duty 14% JCDB . 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. In the ERP system, this information is contained in the following tables:. I wonder why the same is not getting extracted when I check in RSA3 for Data Source 2LIS_02_ITM. Transaction Data. As of SAP enhancement package 6 for SAP ERP 6. 2LIS_02_HDR. CLEAR LT_DATA. Figure 9: BW Control Table – Foreign. SAP Tables SAP Table Fields (New) SAP Glossary Search;. 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. Scheduling Agreement Tables. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. We need to extract fields RM06E-LTEX1 (long text) and RM06E-KZLTX (More Text Exists which is a flag) from R/3 into BW however RM06E is a structure in R/3. 2LIS_03_UM. save the package and press create. But this d/s 2LIS_02_SRV doesnt pick/identify the deleted service entry sheets. MM - Materials Management: 10 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 11 : 2LIS_13_VDITM: Billing. Figure 8: BW Control Table – Entry Help/Check . 94 Views. LIS uses v1 and v2 update modes only. 9) After zero records repeat the step 6 to 7 for double confirmation to avoid any possible data entries. Delete the setup data (LBWG) 2. In combination with the InfoSources Purchasing Data (Document Item Level). However, when we do delta-load, none of the account. 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. 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. 2LIS_02_ITM. And after the setup table is filled, data in 2LIS_02_SRV gets duplicated. excuse me for this message, but I have a problem and I think you could help me. I use the standard extractor 2LIS_02_ITM (order positions) with the update mode "Direct Delta" and apanded Z-fields. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data. I've done all the "tasks" for setup tables, but i don't have 0PROCESSKEY. However, InfoCube for Purchasing ( 0PUR_C01) is already active in the system and delta are being loaded into it on a regular. 1. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. but not in. # Table. 0) Basis - BW Service API: VBDATA: Update data: Basis - Client/Server Technology: BW Datasources related to RMBWV302 BW DATASOURCE Description Application ;. 2LIS_13_VDITM: Billing Document Item Data. 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. Use. Not just "LO DataSources" because there are some that don't use this feature. These Z-Fields are in the database table EKPO. Login; Become a Premium Member; SAP TCodes; Tables. Hi all, I ran OLI3BW to fill the set-up tables and tried with RSA3 (no selections) and it returned 0 records for 2LIS_02_CGR, 2lis_02_scn and 2lis_02_cgr. 2LIS_02_SRV (obsolete) The 2LIS_02_SRV data structure is new for the EHP3 and there are some steps to activating it. So we created an append structure to MC02M_0ITM. 04. KNTTP – Account Assignment Category. when I used INIT or DELTA infopackage. But in RSA7 , there are 0 recrods . 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. "Image/data in this KBA is from SAP internal systems. With this handy table you can find the status of your current job or previous initialization jobs through SM37. Purchasing 2LIS_02_HDR MC02M_0HDRSETUP Storage BW Setup for. eg: if i do the following action: Fill 1 -> Delete - Fill 2. if you put EKET then it brings up. #. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 2LIS_02_ITM is a purchasing extractor, mkpf et mseg are inventory table. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 :. Hi We are using the following logic to enhance 2lis_02_itm with different fields from diff tables. Transformation Rule. The 2lis_02_itm documentation says that the field NETWR (Net PO value) is picked up directly from table field EKPO-NETWR. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. Data Source:2LIS_02_ITM. Loaded 0%. Then I. RSS Feed. Datasource Jest Table BW Extractors in SAP (25 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. Sep 25, 2008 at 11:16 AM. Application: SD - Sales and Distribution. Relevancy Factor: 6. 2LIS_02_ITM - Adding field problem | SAP Community Relevancy Factor: 1. Then went to BW , installed the cube , update rules and the infosources. Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. Transaction code to delete setup table is LBWG. Date of Purchasing Document. All 3 2lis_02_itm, hdr and scl were enhanced to add additional fields. 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. I know that For purchase order details we used 2 datasources 1. We do not have down time. Hi, I am using 2lis_02_itm and 2lis_02_hdr. 2LIS_02_ITM (Purchasing Document Item Level Data) 2LIS_02_SCL (Purchasing Document Schedule Line Level Data) Step 1 : Log on to Sap R/3 Ecc System. 2LIS_11_V_SSL: Sales Document: Order Delivery. You have to enhance the data source if the field is not available to you. When I enhance comm. Run the Delta Info package in BW to update all the data i. 2LIS_02_SCL. 2lis_02_itm uses EKKO and EKPO tables etc. Inside LBWE, click the Maintenance button for this 2LIS_02_ITM, the left frame is "Selection criteria" and the right frame is "Pool", but we don't know on how to locate our new field Z1 from this Structure Maintenance window. 3. When running the setup for application 02 (TR OLI3BW), the table was not filled: running RSA3 with no restrictions did not retrieve any records. Please also specify what is the way to find out it. 02. Some of the PO items are marked for deletion in the source system (LOEKZ = L). This is to keep data that is depending on each other consistent. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. Create column table “02_ITM” as (select * from “INF627126″. Run the collective run, so all the data is sent into the delta queues. SYDAT is Item created on - EKPO-AEDAT. Select the Data Source ( 2LIS_02_ITM ) 3. The modeling property Inbound table as extended table has been turned on. Go to LBWE (LO Cockpit), select DataSource 2LIS_02_SCL, click on Maintenance icon in Structure column, say Continue. No. Then relicated the data sources . SD Sales Orders. , Z1, and we try to add this new field into the LO Cookpit datasource 2LIS_02_ITM. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) -. I can then reference the InfoSources in question since I know HDR data will come ! from EKKO and ITM data will come from EKPO. 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. So in the PSA,I am getting 2 records for the PO which has. There I see data only for some extractors (2LIS_46_SCL and 2LIS_46_ITM) : see attached picture issue-gtm-01. Table of Origin. 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. We currently have delta load happening from the same data source. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. The DataStore object integrates data on orders and free-of-charge orders on the basis of the order items (2LIS_11_VAITM) and aggregated information on order delivery schedule lines ( 2LIS_11_V_SSL ). But you need to find the filed (AEDAT) belongs to which table. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. There is a requirement to load full load to BW system from 2LIS_02_ITM data source. Application; 1 : 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 : 2LIS_11_VAITM: Sales Document Item Data SD - Sales and Distribution: 3 : 0CO_OM_OPA_6:. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 . Go inside the class ZCL_DS_2LIS_02_ITM and implement the below code – ATA : LT_DATA TYPE STANDARD TABLE OF MC02M_0ITM. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. IF i_datasource = '2LIS_02_ITM'. SAP Knowledge Base Article - Preview. Data source. g. KNTTP – Account Assignment Category. ) 2LIS_02_SCL & 2. 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. I have been using DataSource: 2LIS_02_ITM for couple of months and I have loaded data into (Full and Deltas). Go to RSA6. I have also deleted the setup tables and filled them again. Bobby. 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),. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. Block user to modify to modify purchase. Purchasing Document Category. Two lines are extracted. 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)). Is there any particular reason? I looked up the configuration of the movement types by going into. now i want to fill setup tables for below datasources, can you suggest what are tcodes to fill up setup tables for below datasources. 2LIS_02_ITM Purchasing Data (Item Level) MM - Materials Management: 14 : 2LIS_05_QE2 Inspection Result: Quantitative Data QM - Quality Management: 15 :Transformation. 2. Apply the changes / Transport. Application Component. These indicators and key figures are based on the associated confirmation and goods receipt documents. Over the last few days , I had some posts on 2LIS_02_ITM and Process Key activation. where this is using a standard datasource 2lis_02_ITM and 2LIS_02_SCL and i have acitvated this standard cube 0pur_c01. with different condition types fromo KONV table . When does it happen that 2LIS_02_ITM does not add. It is from BEDAT from EKKO and EKBE. Symptom. This DataSource replaces DataSource 0FI_AP_3 (Accounts Payable: Line Items) and uses the same extraction structure. When I check with RSA3 I've got a lot of records. 2lis 11 Vaitm Tables BW Extractors in SAP (28 BW Datasources) Login; Become a Premium Member; SAP TCodes;. The DSO is directly supplied from the Info/DataSource 2LIS_06_INV. Field VDATU has the same name as Update Date for Statistics Update for DataSources 2LIS_11_VAITM and 2LIS_11_VASCL. BW-Rebuild for MC02M_0CGR Storage. 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. BW . ECC -> SE11 -> ROOSOURCE -> Both "GENDELTAFD" and "GENDELTATP" are empty too. 12. The EKPO table (Purchasing Document Item). so I add field CHARG into that datasource. When I loaded to BW , 2LIS_02_ITM transferred some records but added 0 Records. Data Source 2LIS_02_SRV used for extraction of (Services Procurement) service line data to BW is made available with ECC 6. SAP BW/4HANA. DataStore object (advanced): SD: Delivery Item Data (2LIS_12_VCITM) - /IMO/CMSD21. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 :. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 3 :. we have the V3 update job, running every 15 minutes. 2LIS_11_VAKON: Order Condition Data. Sap Tables in SAP. MC02M_0SCLSETUP. I also have checked that: 1. If no data. 2lis 03 Bf Table BW Extractors in SAP (29 BW Datasources) Login; Become a Premium Member; Transaction Codes; Tables. with SE11 transaction you can see these tables. Please note , Everything is fine with setup table data , update rule ( Overwrite mode) and other BW part. LIS uses transparent tables. see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Also you can see same in Transaction code ME80FN. Overall Picking/Putaway Status. The following has all been done. 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. Vote up 0 Vote down. Relevancy Factor: 30. I checked the function module also , but still in process, any suggestions would be greatly appreciated. Implemented class Name – ZCL_DS_2LIS_02_ITM. Prerequisites. Step 2: In the table TCDOB put the table name in TABNAME field, you will get some name in OBJECT. or alternatively you can build your own custom extractor using purchasing tables EKKO,. It's the pre-processing of Archive ( Archive Object is MM_EKKO ). For POC we have used Virtual table as template and used the SQL console to create table. 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:. Go to Maintainance. (2LIS_11_V_ITM) - /IMO/CMSD16 . 1 ; SAP NetWeaver 7. The start routine for the updates ensures that only orders and free-of-charge orders are updated in the DataStore object. BEDAT. Former Member. Pls reply needed urgent,i'm. The Problem is, that the setup tables are not getting poulated. However in the S/4HANA system, table KONV is obsolete and replaced by table. I am trying to fill up the SETUP tables. I have pasted the eror message below for reference. Note: As an alternative you can also use DHCDCVCDSEXTRE in SE16 which contains more or less the same information. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. Inventory Controlling (application 03): 2LIS_03_BX. ECC -> RSA2 -> Generic Delta -> field name is empty. How can I find which tables in R/3 are the source tables for this and that extractor (e. 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 11 :However, before replicating to the BW on HANA system connected, I checked data in S4 via RSA3. Follow. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Cannot see the data for datasrc 2lis_02_scl in RSA3. Field PSTYP. 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. 2LIS_02_ITM - Adding fields to communication structure - User exit | SAP Community Relevancy Factor: 1. 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. Fill the setup tables with historical data using SBIW to get to the tcode OLI*BW. Also, please make sure that your answer complies with our Rules of Engagement. Control record it will be having information like Idoc number, message type, idoc type, sender, receiver etc. I also know that my InfoSources for this data are 2LIS_02_HDR, 2LIS_02_ITM, and 2LIS_02_SCL. 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. Vote up 2 Vote down. Sap Supply Chain Management Tables in SAP. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. Similarly, we can do the same steps (Step1-5). Why are the setup tables not filled?If additional information is needed for the tables please let me know. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. In RSA3 if we check for that sales doc nos , it is displaying 0 records. Purchasing 2LIS_02_ITM MC02M_0ITMSETUP. For e. 2LIS_13_VDKON: Billing Condition Data. At the same time, they are also updated in the ODQDATA table. Transformation. In the standard extractor 2LIS_02_ITM the field BADAT is check as Field only known in customer exit. Use. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . 0B, InfoSource 2LIS_04_P_MATNR replaces InfoSource 2LIS_04_S280. 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. ) We had a similar scenario where we wanted to refresh entire data for 2LIS_13_VDKON. LFA1 NAME1. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Sep 16, 2009 at 06:26 PM. from the standard tables using a Business content Data Source the Data should be Extracted to BW system. I have enhanced the datasource(2lis_02_itm) for the Tolerance fields. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. Compare with setup table records. In rsa3 and in set up tables I see data fro 2LIS_02_ITM AND 2LIS_02_SCL. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 0LOG_SYS_BE. I have already maintain datasource 2LIS_02_ITM through LBWE. 2LIS_02_CGR 2LIS_02_SGR 2LIS_02_SCN. then data inconsistency will be happen. Note: Field COMPL_DEL of BW is mapped via direct assignment to ECC field ELIKZ ( Delivery. EKKO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Header data. 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 is redifining the code and changing lots of extractors and are pushing forHi. And it shows 0 records. 2LIS_02_ACC. "Can you please specific Setup table i. They are needed in BW and not in R/3. Locate your Extractor (Datasource). The DataStore Object already exists in Business Content and contains the following new fields necessary for RMA Cost Allocation: A key figure provided from DataSource. 3. MC02M_0ITM. 123456 20 L. SAP Table Field : BUDAT - Posting Date Top 200 SAP Tables containing the field/column BUDAT. Copy & paste to SE37 eg for 2LIS_02_ITM , extractor MCEX_BW_LO_API is used. 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. g. we have datas (ekko,ekpo) 2. BW Reorganization Store for MC11V_0ITM. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. 2lis 04 P Arbpl Tables BW Datasources Most important BW Extractors for 2lis 04 P Arbpl Tables # BW DATASOURCE Description. If you choose the Delivery Schedule Lines view in the transaction ME80FN, you can compare the data in the DataSource fields with the original document data in SAP R/3, such as: · Purchasing Document Number (EBELN) · Item Number of Purchasing Document (EBELP) · Delivery Date (EINDT)1. We appended cost center and cost element to this extractor using FUNCTION EXIT_SAPLEINS_001. 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. I'm using OLIG and OLIGBW to fill setup tables but there are certain documents/contracts I can. Media-Specific Adjustments to the InfoSource Order Item Data (as of 2. I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 . Purchase Order Tables. LOEKZ is only an indicator/flag. If a data inbound layer persistence and/or a corporate memory persistence is used, the transformation from this DataStore. Apparently these two fields are NOT updated in BW from a delta load. 2LIS_18_I0CAUSE: Full & Delta: Customer Service: 2LIS_18_I0ACTY: Full & Delta Financial Accounting and Controlling. MC11VA0STI: Extraction MD Order Item Status for DataSource 2LIS_11_VASTI. 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. For information, I had the same problem with 2LIS_02_ITM. Purchasing Document Category. Deleted the Setup tables. 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:. 2001. Whereas 2LIS_02_SGR transferred and added records. Maintained extract structure for 2LIS_02_ITM (LBWE) 2. Runn full load. EKBE is a standard Purchasing Transparent Table in SAP MM application, which stores History per Purchasing Document data. Table of Contents SAP BW/4HANA Content Add-On. So , how to know. Folder: BW Setup for MC02M_0ACC. and enhanced the datasources ITM and SCL adding one Char in. 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:. 2. g. 01. However I observed a different behaviour in case of POs with an Invoicing Plan ( mostly framework POs) E. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :. This. 3. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule. Hi Fabio, No You cannot do a setup for 2LIS_02_ITM only, You can only do a setup for the whole 2LIS_02. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL. 02. ZBW_ 2LIS_02_HDR; ZBW_ 2LIS_02_ITM . In RSA7 i purged or deleted the records and entry for this datasource. Comparing DataSource 2LIS_02_SCL to ME80FN. 02:PURCHASING. WHEN '2LIS_02_ITM'. Step. In ekpo screenshot you can find final Invoice flag is set (EKPO-EREKZ) for all the PO line. When I execute the RSA3 for different Datasources I can see data only in. 100 -> 100 -> 200. In EKET Table the primary key is based on 3 fields. MC02M_0ITMSETUP if it have any records" Customized BADI Name – ZPP_DS_2LIS_02_ITM. run delta loads asusal. While doing the statistical setup i am using the T. The details are as below:2LIS_11_VAITM Data Source is not fetching data | SCN.