Bobby. We are about to delete setup tables for purchase (02) component and refill the setup tables. 3 ; SAP NetWeaver 7. Cannot see the data for datasrc 2lis_02_scl in RSA3. Test using RODPS_REPL_TEST , SUM = 0 in the result. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. # Table. 2LIS_02_ITM - Adding field problem | SAP Community Relevancy Factor: 1. Delivery time (SCLTM) = 12:00:00. Run the collective run, so all the data is sent into the delta queues. 0 (SAP_APPL 606), business function Sales and Distribution, Analytics 01 (LOG_SD_ANALYTICS_01), this DataSource also contains an ODP extractor for Operational Data Provisioning (ODP). Use. MC02M_0SGR: Produced Activity: Delivery of Schedule Lines Maintenance for Data Source 2LIS_02_SGR 8 31 139,142. That means that you can use this DataSource both for data replication in a BW system (SAP Business. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Item Level) ( 2LIS_02_ITM ). g. This DSO contains delivery related indicators and key figures for purchase order items. 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 :. When I enhance comm. These indicators and key figures are based on the associated confirmation and goods receipt documents. Relevancy Factor: 30. Jun 15, 2007 at 04:37 PM. MM - Materials Management: 10 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 11 : 2LIS_13_VDITM: Billing. In the ERP system, this information is contained in the following tables:. The account assignment category determines the account assignment data for an item, such as cost center and account number. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. Step. Follow. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. And after the setup table is filled, data in 2LIS_02_SRV gets duplicated. 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. 2. EKKO. EKKO. MC02M_0ITM is a standard Logistics Information System (LIS) Structure in SAP LO application. Transformation Rule. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . purchasing and inventory ( data sources are EG 2LIS_11_Vaitm, 2LIS_02_ITM, etc. These fields are populated in the extractor and not stored in any tables. excuse me for this message, but I have a problem and I think you could help me. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). Table Coep BW Extractors in SAP (20 BW Datasources) Login; Become a Premium Member; SAP TCodes;. If no data inbound. hi Check in Base tables 😊. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 5 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 6 :670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL . 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. Data Source 2LIS_02_SRV used for extraction of (Services Procurement) service line data to BW is made available with ECC 6. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. 3. Setup Table. BW Reorganization Store for MC11V_0ITM. Presss F5 and get inside the form “select_option_fill”. 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. RSS Feed. 0B, InfoSource 2LIS_04_P_MATNR replaces InfoSource 2LIS_04_S280. Delta. 0GN_R3_SSY. Goto LBWE transaction in R/3. what is the reason , pls. I can then reference the InfoSources in question since I know HDR data will come ! from EKKO and ITM data will come from EKPO. There are multiple ways of creating a column table. My plan is to perform below steps. 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. In 2LIS_11_VAHDR however, the field VDATU contains the sold-to party's Requested Delivery Date. The fields are filled with an. In ekpo screenshot you can find final Invoice flag is set (EKPO-EREKZ) for all the PO line. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule. 13. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. Select the Data Source ( 2LIS_02_ITM ) 3. Follow. Datasource is in active mode. Upon trying, i have encountered many problems: 1. (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. They are needed in BW and not in R/3. SAP BW/4HANA. In debug mode search for below string and add breakpoint there. This counter determines the number of deliveries based on the GR document items. following fields of DataSource 0CUSTOMER_TEXT: Sold-to Party. Order Alloctn Item Delta1 updat :2LIS_11_V_ITM : 8) If still Extraction queue (SMQ1 or LBWQ) has entries, repeat the step 6 to 7 until both the extract Queues and delta Queues read ZERO records. Purchase Requisition Tables. Currently i need direct t-codes to. Deleted the set up tables and ran OLI3BW and filled the set up tables. For e. Processkeys are maintained. SAP BW/4HANA Business Content delivers. 1 ; SAP NetWeaver 7. Clear "RSA7" 03. save the package and press create. But when the user changes only the account assignment of an outline agreement , without changing any other fields (e. On DEV ran RSA3 for docs 4500000780 4500000782 0 recs selected 4)Delete set up tables for Purchasing application 02 5)Fill up set up tables date range 9/17/2004 to. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 - SAP Help Portal Relevancy Factor: 10. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. when I used INIT or DELTA infopackage. ALIEF - Number of Deliveries. 2LIS_02_ACC. 04. Why? What am i missing out do i need to do any changes before i actiavte the in-active tables in LO-Cockpit. On top of this, setup table was filled, but I see no data for 2lis_02_itm. 05. Description. We could able to see the enahnced field data in RSA3 , but after making any change in ME22n its not p. 02:PURCHASING. News & Insights. 2. Read more. 5. READ TABLE i_t_ekpo WITH KEY ebeln = xmcekpo-ebeln ebelp = xmcekpo-ebelp. While doing the statistical setup i am using the T. Ship-to Party. Tables related to 2LIS_13_VDHDR TABLE Description Application ; VBRK: Billing Document: Header Data: SD - Billing: VBRP: Billing Document: Item Data: SD - Billing: VBAP:For the same Datasource 2LIS_02_HDR, when in R/3 production I try to extract data using RSA3, it gives me '0' records. I checked in RSA3 and the set up tables all the above datasources have records. SAP. Initialize Delta Process, selection criteria, filtered out, RSA7, delta queue, table ROOSPRMSF, BUDAT, logistics data source, 2LIS_02_ITM, 2LIS_02_HDR, 2LIS_* , KBA , BC-BW , BW Service API , BW-BCT-MM-PUR , BW only - Purchase , How To. (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. Technical Name of Target InfoObject. 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. 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. Login; Become a Premium Member; SAP TCodes; Tables. 2. But I do not see any entries in the setup table 'MC02M_0ITMSETUP' after the SETUP run. T-Code : LBWG Or SBIW -> Settings for Application-Specific Datasources(PI) -> Logistics -> Managing Extract Structures -> Initialization -> Delete the contents of the setup tablesYes you can append the AEDAT filed to 2LIS_02_ITM datasource and need to populate with the data from table by writeing the conde in COMD. But this d/s 2LIS_02_SRV doesnt pick/identify the deleted service entry sheets. When using a Join of 2LIS_03_BF ( for Good Movement (E) from MSEG data ) and 2LIS_06_INV ( for Invoice (Q) from EKBE data ) ; In general the DBMTR is same in MSEG and EKBE, but there are few scenarios when they are. EKAB is a standard Purchasing Transparent Table in SAP MM application, which stores Release Documentation data. I know the history has it but, I want to know what is the source for BUDAT in 2LIS_02_ITM. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :. Replicate the same in BW system. I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 . Purchase Invoice Tables. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. It s failing for only 2LIS_02_ITM only. 2LIS_13_VDKON: Billing Condition Data. By debugging function module MCEX02_PREPARE_INFO it was found that the field UPDACT in table TMCEXACT. Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04. Hi all, 1. Filled with the 2-digit logical original backend system (based on ORGLOGSY ). No. also full update of 2LIS_13_VDITM featches only records that have been uploaded with initial load. 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),. Technical name: 2LIS_12_VCITM. Read more. 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 also know that my InfoSources for this data are 2LIS_02_HDR, 2LIS_02_ITM, and 2LIS_02_SCL. Table of Contents SAP BW/4HANA Content Add-On. 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 more information on this topic, refer to the. Then save, check and activate the process chain and provide information, where applicable, about which server the process chain should be scheduled on. To stop the access from outside we use t-code SM01 to. In EKET Table the primary key is based on 3 fields. At present delta loads are running through that extractor. Thank you all for your replies. If I missed to search something please provide that. BW-Rebuild for MC02M_0CGR Storage. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Fill setup table. 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. Note: Field COMPL_DEL of BW is mapped via direct assignment to ECC field ELIKZ ( Delivery. Add a Comment. run delta loads asusal. Then I. Sep 16, 2009 at 06:26 PM. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_12_VCITM: Delivery. 12. and added a Z-field (ZZEKKOL) for this field. ALIEF - Number of Deliveries. 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. Follow. ”VT_2LIS_02_ITM”). FAQ: Setup table filling with 2LIS* extractors. News & Insights. 2LIS_18_I0CAUSE: Full & Delta: Customer Service: 2LIS_18_I0ACTY: Full & Delta Financial Accounting and Controlling. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . 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. Step one: stop all postings in connected ERP system. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. and then go to BW side and replicate the Datasource. The 2lis_02_itm documentation says that the field NETWR (Net PO value) is picked up directly from table field EKPO-NETWR. The issue is when I ONLY change the. enhancing through function module in 2lis_02_itm. 1. Comparing DataSource 2LIS_02_SGR to ME80FN. CLEAR LT_DATA. Gross Price P001 / P000 / PB00 / PBXX . Implemented class Name – ZCL_DS_2LIS_02_ITM. T-Code Purpose. correct me if iam wrong. Step 2: Replicate datasources in BW -PRD. KNTTP – Account Assignment Category. Root Cause: If a PO Item in P20 is. MM-PUR: Purchase Order Delivery (Items) - /IMO/PUR_D21. g. Quantity ordered (SCLQTY) = 20. 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. In R/3 my setup tables are filled : MC02M_0ITMSETUP . 2LIS_02_HDR : Purchasing data header level 2LIS_02_ITM : Purchasing data item data 2LIS_02_SCL : Purchasing data schedule line level 2LIS_02_SCN : Produced Activity : confirmation of schedule Lines. see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. ZBW_ 2LIS_02_HDR; ZBW_ 2LIS_02_ITM . Here is the code: LOOP AT xmcekpo. Name of Target InfoObject. 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. 2LIS_02_CGR. 339 Views. Creating an infopackage using the "full update" option: to do this I activated the extract structure MC02M_0ITM, i. 2010 1:00 AM. Jan 29, 2008 at 06:41 PM. xmcekpo-ZZKUNNR = i_t_ekpo-kunnr. then go to T- Code OLI9BW. Please note , Everything is fine with setup table data , update rule ( Overwrite mode) and other BW part. I'm trying to use datasource 2LIS_02_CGR in addition to 2LIS_02_ITM already in use. I am trying to extract data from the EKKO and EKPO tables using the purchasing extractors 2lis_02_itm and 2lis_02_hdr. now i want to fill setup tables for below datasources, can you suggest what are tcodes to fill up setup tables for below datasources. This is to keep data that is depending on each other consistent. Use. 3. I tried deleting the setup table (LBWG) and tried again initialization (OLI3BW) but I cant. RemoteCube-Compatible. IF i_datasource = '2LIS_02_ITM'. Can see Queue 2LIS_11_VAHDR. An overview of Datasources and the programs filling the relevant setup table (named MC*SETUP). 1. 0. This item won't be delete physically. 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. BW-BCT-PM (Plant Maintenance). LBWE transaction - inactivate update, deleted setup tables in application component 02(MM) and also deleted any delta queue in /nrso2. In this case use FM EXIT_SAPLRSAP_001 as template. Both the datasource do not have Material document number (BELNR) field. Relevancy Factor: 1. When i. Invoice Verification. Maintained extract structure for 2LIS_02_ITM (LBWE) 2. BEDAT. In this extractor we have enhanced "PS_PSP_PNR" (WBS Element) field whose values are being stored in "Account Assignment in Purchasing Document" table. Or if you are looking for OSS NOte #. 2lis 02 Itm Tables Most important Database Tables for 1. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 7 :. 02 Purchasing 2LIS_02_ACC MC02M_0ACCSETUP Folder: BW Setup for. ALIEF - Number of Deliveries. and do repair Full for whole data. Delete data "LBWG" 05. Datasource Type: Transaction Data Extractor. - Process Key 001:PO. we have datas (ekko,ekpo) 2. Purchasing Organization Tables. Some of the PO items are marked for deletion in the source system (LOEKZ = L). I activated 2LIS_02_itm and SCL datasources in LO cockpit but, it is not prompting for a transport request. ) We had a similar scenario where we wanted to refresh entire data for 2LIS_13_VDKON. sap and forums i found out that for. I have added field BADAT-PR creation date in the extractor structure of 2lis_02_itm. 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. 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. Step 1: Move ECC TR to ECC- PRD system. This InfoSource contains the structure to provide purchase data on item level into the EDW Core Layer. Scenario 1: All the line items associated are marked for deletion,Then 2LIS_02_ITM--> LOEKZ being extracted as L,No issues here. You can look at the includes with *TOP* eg INCLUDE mcex02top. Sap Tables in SAP. My data flow is direct load to Info cube using 2lis_02_ITM and SCL datasources. Checked data in "RSA3" ex: 200 records. 2lis_11_vahdr & 2lis_11_vaitm we have to use tcode OLI7BW. SAP Knowledge Base Article - Preview. 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. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 0 EHP 3. 0OPS_12_ITM. Date of Purchasing Document. 2. 2008 i have executed Initial Load from BI. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data. 4. Apparently these two fields are NOT updated in BW from a delta load. Implemented class Name – ZCL_DS_2LIS_02_ITM. 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. Available as of OLTP Release. Use. Symptom. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 :. Total number of tables/structures containing this field is 7006. 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. We are using the BW DataSource 2LIS_02_SCL from the LO Cockpit and have added these two fields from the Customizing cockpit (LBWE): WAMNG WEMNG. Transa ctional. all fields of DataSource 2LIS_12_VCITM. Hi, Where can i find the t-codes for filling the setup table for all the logistics datasources. SD - Sales and Distribution: 3 : 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 : 2LIS_12_VCITM: Delivery Item Data SD - Sales and Distribution: 5 : 2LIS_01_S001: Customer SD - Sales and. Maintain extract structure and datasource. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data: SD - Sales and Distribution: 2LIS_11_VASCL: Sales Document Schedule Line: SD - Sales and Distribution:. PLAF is a standard Master Data Transparent Table in SAP PP application, which stores Planned order data. Vendor Master Data Tables : LFA1: Vendor master data general section LFB1 : Vendor Master Company Code. Hi, I am using 2lis_02_itm and 2lis_02_hdr. Purchase Order Tables. 2lis_02_itm uses EKKO and EKPO tables etc. But in RSA7 , there are 0 recrods . SD Sales Orders. I have a problem with the delta. 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. For item 20, LOEKZ = L (Deletion indicator). 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. Click ‘Yes’ to proceed further. ECC -> SE11 -> ROOSOURCE -> Both "GENDELTAFD" and "GENDELTATP" are empty too. e. EKPO - Item. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. This. Step 2: In the table TCDOB put the table name in TABNAME field, you will get some name in OBJECT. During the initial load, everything comes along fine all the way to PSA. When I try to do this in the conventional way (in transaction RSA6, button 'E. I checked the function module also , but still in process, any suggestions would be greatly appreciated. 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. Deleted the Setup tables. In LBWE, it says EKKO-SYDAT but it is from EKPO (*) 2LIS_02_ACC. Technical Name of Target InfoObject. It is mapped to BW fields 0DEL_FLAG and 0ITEM_DEL via direct assignment. I am trying to find the procedure / sequence in to carry out in. We are analbe to get the records for "Pruch Docu Catgory" = L(Scheduling Agreement). create your update rules using MC24. Folder: BW Setup for MC02M_0ACC. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Create column table “02_ITM” as (select * from “INF627126″. SAP R/3 Enterprise. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 :. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. That means setup process wasn't happen correctly. Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. Step-4: Creating function modules for each extractor enhancement. 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. Home. 14. Dear All, I have activated BI Contents: 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_HCL. 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:. We do not need the history data for the 2 fields added. Please provide a distinct answer and use the comment option for clarifying purposes. Marco. 0. Sep 25, 2008 at 11:16 AM. but not in. (2LIS_11_V_ITM) - /IMO/SD_IS16 . Figure 9: BW Control Table – Foreign. I filled the setup table in the development system and did an Initialize with data transfer. Source System for R/3 Entity*. The three others (2LIS_46_HED ; 2LIS_46_CFM ; 2LIS_46_GTM) are not showing any data : see attached picture issue. When I execute the RSA3 for different Datasources I can see data only in. - Process Key 003:IR. FIELD-SYMBOLS: <LS_DATA> TYPE MC02M_0ITM, <LV_KUNNR> TYPE EBAN-KUNNR,. MC02M_0ITMSETUP if it have any records" Customized BADI Name – ZPP_DS_2LIS_02_ITM. You can see the table in the above screen shot. SAP R/3 Enterprise all versions Keywords. , Z1, and we try to add this new field into the LO Cookpit datasource 2LIS_02_ITM. 0. ) 2LIS_02_SCL & 2. As of SAP enhancement package 6 for SAP ERP 6. Hi All, When a PO is posted the vaules are being picked by the 2LIS_02_ITM extractor. These documents are also not getting filled into Setup Table by OLI3BW. using help. Thanks for the quick response. This form assigns the range entered in selection screen to internal table dd_belnr. Purchasing. The configuration of the table looks as follows. This's also valid to other PUSH datasource. Hi We are using the following logic to enhance 2lis_02_itm with different fields from diff tables. There is a table that maps movement type to process key. Item 20 is deleted. I have also deleted the setup tables and filled them again. Transaction Data. . GR or IR level changes won't trigger any deltas for ITM Datasorce. - Process Key 002:GR. 12. In R3, some PO items marked with Final Invoice (EREKZ = X) but the same PO items are not reflected with final Invoice flag via the extractor 2LIS_02_ITM. 2) From the Scheduler dropdown, select the Repair Full Request Option. Datasource For Afko And Afvc Tables BW Datasources. 2lis 02 Itm Tables Tables Most important Database Tables for 2lis 02 Itm Tables # TABLE Description Application Table Type; 1 : EKPO: Purchasing Document Item MM - Purchasing: Transparent Table 2 : EKKO: Purchasing Document Header MM - Purchasing: Transparent Table 3 : MSEG: Document Segment: MaterialRequest or instruction from a purchasing organization to a vendor (external supplier) or a plant to deliver a certain quantity of a product or to perform certain services at a certain point in time. I checked in RSA7 - all 5 DataSources are there. 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. We can replace the contents of internal dd_belnr through flat file upload. Empty BW delta queues on R/3 by extraction to BW.