2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. 2LIS_13_VDKON: Billing Condition Data. 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. some sales document nos missed in bw. 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:. and enhanced the datasources ITM and SCL adding one Char in. Field in Table of Origin. a few weeks ago delta in BW stopped working. 94 Views. 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: Sales-Shipping Allocation Item Data: SD - Sales and Distribution: 2LIS_11_VASCL: Sales Document Schedule Line: SD - Sales and Distribution:. where ebeln = c_t_data-ebeln. Sales Document Item Data (2LIS_11_VAITM) - /IMO/CMSD11. 01. There is a requirement to load full load to BW system from 2LIS_02_ITM data source. 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. For purchasing datasources 2lis_02_itm and 2lis_02_sgr . 2lis 03 Bf Table BW Extractors in SAP (29 BW Datasources) Login; Become a Premium Member; Transaction Codes; Tables. "2LIS_02_SCN MM MC02M_0SCN Achieved Performance: Confirmation of. "Image/data in this KBA is from SAP internal systems. Tables for 2LIS_02_ITM. cat = F ) . We appended cost center and cost element to this extractor using FUNCTION EXIT_SAPLEINS_001. 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. The process chain supports SAP R/3 standard systems as of Release 4. ) 2LIS_02_SCL & 2. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. ) 2LIS_02_ITM. Thank-You. 100 -> 100 -> 200. VRTKZ – Distribution Indicator for Multiple Account Assignment Table of Origin. Description. Here are the 25 most used bw_datasources in SAP Bw datasource Description Functional Area 2LIS_03_BF Goods Movements From Inventory MM - Materials Management Management 2LIS_02_ITM Purchasing Data (Item Level) MM - Materials Management 2LIS_03_BX Stock. Type of DataSource. Append MCEKPO. As of SAP enhancement package 6 for SAP ERP 6. Hi, Logistics application ""02 : Purchasing"" (HDR, ITM and SCL) is activated. Purchasing (application 02): 2LIS_02_ITM. Purchase Invoice Tables. Step 5) Choose the datasource 2LIS_02_ITM and go to the Datasource tab and click Change the datasource as shown in screenshot. MC02M_0ACC. 0. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Step 4) Choose the datasource 2LIS_02_ITM, which is purchasing data at Item level. Dear All, It would be really helpful to know the used tables for datasource 2LIS_02_ITM. Ship-to Party. This is derived from the statisitcs updating facility maintained for updating the LIS (PURCHIS) tables in R/3. , Z1, and we try to add this new field into the LO Cookpit datasource 2LIS_02_ITM. Once we get the above screen, we could specify the component (02, 11, etc…) and click on execute button. 02. Then use the function Activate and Schedule to start the process chain according to your scheduling options. 2lis_02_itm Structure is active. Consider Process Key 2 for GR amount and Process Key 3 for Invoice Amount. RSS Feed. You get this message , when you execute MCB_ " View/table V_TMCLBW can only be displayed and maintained with restrictions" 2. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . Purchasing Organization Tables. 3. 2LIS_02_ITM : MC02M_0ITMSETUP : Storage BW Setup for MC02M_OITM : Purchasing :. Use. Filled with the 2-digit system ID of the connected source system. ECC -> SE11 -> ROOSOURCE -> Both "GENDELTAFD" and "GENDELTATP" are empty too. after this load you can run deltas. When I check in EKPO table, deletion indicator "L" is available for all deleted PO's. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. Create column table “02_ITM” as (select * from “INF627126″. Locate your Extractor (Datasource). EKKO. When i. 2LIS_02_HDR. Purchasing. Table of Contents SAP BW/4HANA Content Add-On. 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. You have to enhance the data source if the field is not available to you. Step one: stop all postings in connected ERP system. Select the Data Source ( 2LIS_02_ITM ) 3. This counter determines the number of deliveries based on the GR document items. In RSA7 i purged or deleted the records and entry for this datasource. Check the data in T- Code RSA3. This DataStore Object (DSO) contains the invoice verification data on a granular level. no (EBLEP) and delivery schedule line counter (ETENR). It is located under materials management --> Purchasing. # Table. There are multiple ways of creating a column table. 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. Run the collective run, so all the data is sent into the delta queues. Purchasing Document Category. To reach the customising node use transaction OMGO. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17. transfered datasource 2LIS_02_ITM using tcode RSA5. etc. we have deleted "02" in T-Code LBWG and filled setup table using Tcode - OLI3BW. The system therefore only executes a delta update for this DataSource if. I checked in RSA3 and the set up tables all the above datasources have records. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. LIS uses transparent tables. Sep 25, 2008 at 11:16 AM. g quantities),. If you followed below steps, no chance to miss single reocrd. But these datasource read data from EKKO, EKPO & EKBE table and material document number field is availble in EKBE. Because when you fill any Purchasing DataSource (i. 2. The fields concerned are located in one of the Purchase Order screens (ME21). The issue is when I ONLY change the. 2016 at 02:59 PM GTM 2LIS_46_ITM extraction. Please also specify what is the way to find out it. For more information on this topic, refer to the. Why are the setup tables not filled?If additional information is needed for the tables please let me know. Newer data is not available when checking the datasources. In debug mode search for below string and add breakpoint there. Hi everyone, We are implementing the purchasing solution for the first time at the client. 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. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. 1. I have gone through many threads with similar subject but dint got proper solution for this. RSS Feed. OLI1BW INVCO Stat. Media-Specific Adjustments to the InfoSource Order Item Data (as of 2. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . Relevancy Factor: 1. The DSO provides insight into the delivery service of vendors by exploring. All 3 2lis_02_itm, hdr and scl were enhanced to add additional fields. but not in. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. if anyone knows tcodes for runinng the set uptable to each data source separatley. When I try to do this in the conventional way (in transaction RSA6, button 'E. 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. Delta & Full extraction to BW for 2LIS_02_ITM. my question is what transaction code can I see this field in BW Table. For the calculation of Net GRN I need (Movement Types: 101 GR goods receipt, 102 GR for PO reversal, 122 RE return to vendor and 124 GR rtrn blocked stck). Delete the setup Table using LBWG . LOOP AT c_t_data into l_2lis_02_itm. so the standard. 0B, InfoSource 2LIS_04_P_MATNR replaces InfoSource 2LIS_04_S280. But when the user changes only the account assignment of an outline agreement , without changing any other fields (e. Purpose. Fill setup table. First part explains about the activation of the data source 2lis_02_SRV & second part explains about enhancing it for adding the services line items to be made available for extraction. That means setup process wasn't happen correctly. "Document data restriction" when filling setup table. Transaction Data. and Yes,I have DELETED setup tables data prior to running the Setup process. Deleted the set up tables and ran OLI3BW and filled the set up tables. e 4. The system therefore only executes a delta update for this DataSource if. 0) Basis - BW Service API: VBDATA: Update data: Basis - Client/Server Technology: BW Datasources related to RMBWV302 BW DATASOURCE Description Application ;. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) -. But in case of LIS it is specific to the particular application. we have the V3 update job, running every 15 minutes. Can see Queue 2LIS_11_VAHDR. Maintain Extract Structure MC02M_0ITM. In ekpo screenshot you can find final Invoice flag is set (EKPO-EREKZ) for all the PO line. I also have checked that: 1. A goods movement is posted with the following information: Posting date (BUDAT) = 05. I'm using OLIG and OLIGBW to fill setup tables but there are certain documents/contracts I can. Step 2 Create Target table where you want to persist the data. Important Key Figures: ROCANCEL. In RSA3 if we check for that sales doc nos , it is displaying 0 records. In rsa3 and in set up tables I see data fro 2LIS_02_ITM AND 2LIS_02_SCL. Hi, when you delete the setup table for 2LIS_02_ITM, it will show that still data exist for other DS. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. Then save, check and activate the process chain and provide information, where applicable, about which server the process chain should be scheduled on. I use the standard extractor 2LIS_02_ITM (order positions) with the update mode "Direct Delta" and apanded Z-fields. MC11VA0STH: Extraction MD Order Header Status for DataSource 2LIS_11_VASTH. We deleted init and reinitialised with no success. Use. I checked the function module also , but still in process, any suggestions would be greatly appreciated. In the ERP system, this information is contained in the following tables:. Sap Tables in SAP. 12. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. EKKO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Header data. 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 :. Description: Sales-Shipping Allocation Item Data. 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. I executed infopackage full load for such sales documents, but 0records are received. I tried deleting the setup table (LBWG) and tried again initialization (OLI3BW) but I cant. Follow. 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. So I did the following steps : 1. after creating two tbls r created which will handle ur delta. 2LIS_02_ITM Not Updating Setup Tables In Initialization Summary. Product. Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04. BW . ECC -> RSA2 -> Generic Delta -> field name is empty. This gives me a message 'Date fields for info structure S032 are not. Issue: COMPL_DEL/Complete Delivery Flag was not getting populated for a PO Item where Transfer Process/Process Key =1 even when the Delivery Completed Indicator was marked at Item level in ECC. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). Clear "LBWQ" 04. 02. Hi All, When a PO is posted the vaules are being picked by the 2LIS_02_ITM extractor. SAP Tables SAP Table Fields (New) SAP Glossary Search. I have a problem with 2LIS_13_VDITM delta. But I do not see any entries in the setup table 'MC02M_0ITMSETUP' after the SETUP run. Test using RODPS_REPL_TEST , SUM = 0 in the result. At present delta loads are running through that extractor. - Process Key 002:GR. Import the table definition from the Metadata Repository in the Data store Explorer and use it as source in a data flow. Purchase Order Tables. no (EBELP). Features of Extractor This DataSource provides information about: the header data of a purchasing document, such as vendor, purchasing organization, order currency, and so on the item data. 3. Settings: Purchasing. This is to keep data that is depending on each other consistent. KNTTP – Account Assignment Category. The corporate memory is filled independently of the EDW core layer’s update. Home. Run DTP with extraction mode “Delta” ( 1 st time it extracts data from setup table). 3. 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. KONV KSCHL. Determine Industry Sector. 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. Then went to BW , installed the cube , update rules and the infosources. 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. Source table: EKET (Scheduling Agreement Delivery Schedule Lines) Extract structure: MC02M_0SCL. Goto LBWE transaction in R/3. Yes. I'm trying to use datasource 2LIS_02_CGR in addition to 2LIS_02_ITM already in use. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) (2LIS_02_SCL). 0. FI and COPA is easy to get , the hardest to get at is the LO extractors. Technical Name. In the second InfoProvider, you can. 2LIS_02_ITM is a purchasing extractor, mkpf et mseg are inventory table. Use. Add a Comment. I am able to see the newly added field in the structure, However when I test the datasourcein RSA3. At the same time, they are also updated in the ODQDATA table. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. g. AND ebelp = mc02m_0itm-ebelp. BW-BCT-PM (Plant Maintenance). I am using 2lis_02_itm and 2lis_02_hdr. Datasource Jest Table BW Extractors in SAP (25 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. Check the source system connectivity. Technical Name of Target InfoObject. After all the fixes were done we can think (did the same kind of fix for all 3), 2lis_02_itm refuse to send us any delta records. 0GN_R3_SSY. Delete data "LBWG" 05. SAP. It is mapped to BW fields 0DEL_FLAG and 0ITEM_DEL via direct assignment. I have added field LOEKZ (Deletion indicator) to datasource 2LIS_02_ITM from t-code LBWE and activated. Purchasing Document Category. Press F8 and program will stop at this step. or alternatively you can build your own custom extractor using purchasing tables EKKO,. Implemented class Name – ZCL_DS_2LIS_02_ITM. 14. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. LBWE-- >Purchasing >Extract structures ---->2LIS_02_HDR/SCL/ITM (DATA SOURCES),when i click on the in-active tab to make change and activate i get a alert as the DATA SOURCE doesn't exist. png. I then delete the Contents of Setup table for Application '02' - message ""setup tables deleted successfully"". Mvke Table BW Extractors in SAP (16 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. Figure 9: BW Control Table – Foreign. AWS Documentation AWS Supply Chain User. 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. 2LIS_02_xxx extractors. 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 . I know the history has it but, I want to know what is the source for BUDAT in 2LIS_02_ITM. SCL dS will trigger delta with GR and IR. 2LIS_02_* Problem - Setup Tables empty | SCN Relevancy Factor: 1. 5. 2. Release Strategy Tables. I created the setup tables via "Purchasing - Perform Setup", but only 3 setup tables were filled. 2LIS_03_BF, 2LIS_03_BX, 2LIS_03_UM)?. 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. MC02M_0ITM: Extraction Purchasing (Item) for DataSource 2LIS_02_ITM. 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 :. Vote up 2 Vote down. For all purchasing data you should use Extractors 2LIS_02_ITM, 2LIS_02_HDR and 2LIS_02_SCL . 0. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. you can store the all the Purchase Orders in one InfoProvider ( restricting on doc. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. We are analbe to get the records for "Pruch Docu Catgory" = L(Scheduling Agreement). Delete content of ODS/CUBE. Customized BADI Name – ZPP_DS_2LIS_02_ITM. . I therefore tried to use the FULL LOAD for those datasources (2LIS_02_HDR, 2LIS_02_ITM und 2LIS_02_SCL). PO Cancellation of data record Entry. Product. Purchasing 2LIS_02_CGR MC02M_0CGRSETUP BW-Rebuild for. RSS Feed. Delivery date (SCLDT)= 01. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). When is it necessary to reload the setup table? For Example. Login; Become a Premium Member; SAP TCodes; SAP Tables; SAP Table Fields; SAP Glossary Search; SAP FMs;. EKKO - Header. In EHP 3 the tables are already delivered to the customer enhanced, the activation will only. setup table are built sucessful and he collects data (setuolog) But the extractor checker doesn't work he collects 0 data. DATA: l_2lis_02_itm type mc02m_0itm, l_index type sy-tabix, lt_ekko type standard table of ekko, wa_ekko type ekko. Step 1: Move ECC TR to ECC- PRD system. Table of Contents SAP BW/4HANA Content Add-On. SAP delivers the following example BEx queries on top of MultiProviders Sales Overview. This means the persistence of data for this. We do not have down time. Data source. see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. MM - Materials Management: 10 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 11 : 2LIS_13_VDITM: Billing. For all LO datasources logic is written in function module MCEX_BW_LO_API. . 2LIS_02_SRV(obsolete) BW-BCT-PA - Personnel Management . Table of Origin. If you have a look at the code, for example sel 'MC02M_0ITM' mc02m_0itm_tab mc02m_0itmsetup, and double click on mc02m_0itm_tab,it will take you to another screen. I have already maintain datasource 2LIS_02_ITM through LBWE. MSEG MENGE. This is what the procedure i used (please tell me if i did something wrong): 1. 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. 2008. 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. Issues in Filling Setup table for 2LIS_02_HDR | SAP Community Relevancy Factor: 1. LBWE transaction - inactivate update, deleted setup tables in application component 02(MM) and also deleted any delta queue in /nrso2. MC11VA0STI: Extraction MD Order Item Status for DataSource 2LIS_11_VASTI. Invoice Verification. also full update of 2LIS_13_VDITM featches only records that have been uploaded with initial load. Go to t-code ODQMON (in ECC). 2LIS_02_ITM, 2LIS_02_HDR, 2LIS_* , KBA , BC-BW , BW Service API , BW-BCT-MM. 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. Source Tables (Function Module): MCEX_BW_LO_API (Function Module) SAP Help, Wiki, Q&A and other resources for 2LIS_03_BF. ODP Semantics. 2lis_11_vascl. we have datas (ekko,ekpo) 2. Status record it will be having different statuses like idoc created,idoc posted etc. 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. 13. Root Cause: If a PO Item in P20 is. Clear "RSA7" 03. PO Deletion Indicator. In this extractor we have enhanced "PS_PSP_PNR" (WBS Element) field whose values are being stored in "Account Assignment in Purchasing Document" table. Presss F5 and get inside the form “select_option_fill”. SAP BW/4HANA Business Content delivers. Note: As an alternative you can also use DHCDCVCDSEXTRE in SE16 which contains more or less the same information. If no data. I'm using OLIG and OLIGBW to fill setup tables but there are certain. Table Header for SAP BW OLTP Sources (Relevant From 2. LOOP AT c_t_data INTO mc02m_0itm. 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. ZBW_ 2LIS_02_HDR; ZBW_ 2LIS_02_ITM . Due to a company migration, We are using a program to delete line items of a PO. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. The start routine for the updates ensures that only orders and free-of-charge orders are updated in the DataStore object. But now I have a requirement to calculate Net GRN. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2LIS_02_ITM - Set up Table. My plan is to perform below steps. Table: EKPO. We do not need the history data for the 2 fields added. Copy & paste to SE37 eg for 2LIS_02_ITM , extractor MCEX_BW_LO_API is used. 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. 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. 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)). When running the setup for application 02 (TR OLI3BW), the table was not filled: running RSA3 with no restrictions did not retrieve any records. Overall Picking/Putaway Status. better till first info provider DSO. (Account Level) (2LIS_02_ACC). Quantity ordered (SCLQTY) = 20. so I add field CHARG into that datasource. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :Note. The fields are filled with an. These many numbers (Po and Line item) will not be extracted by the std extractor i,e, 2LIS_02_ITM, since those POs are not real PO. 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. 2LIS_11_V_ITM. Run info pack with init without data transfer.