SAP. Click on save ---> Again Click on Inactive Click on Continue and Again Click on Continue Now You can see the Data Source in Active (Job Control) * Repeat the same steps for 2LIS_02_ITM and 2LIS_02_SCL 3. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . In LBWQ no entry for MCEX02 exist. Field in Table of Origin. 3. SAP BW Datasource : 2LIS_02_SCL - Purchasing Data (Schedule Line Level). Relevancy Factor: 6. Data Source:2LIS_02_ITM. 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. PO. 2008 i have executed Initial Load from BI. This DataSource extracts Accounts Payable Accounting line items from tables BSIK (open items) and BSAK (cleared items) in the R/3 source system. better till first info provider DSO. Delete the setup Table using LBWG . 2LIS_02_CGR 2LIS_02_SGR 2LIS_02_SCN. I'm trying to design a dataflow from a SAP ECC 2lis_02_itm delta extractor to sql server table (odp extractor -->sql -->map_cdc_operation --> sql table. When i. 2lis_11_vakon. 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. 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. e. Use. All 3 2lis_02_itm, hdr and scl were enhanced to add additional fields. I filled the setup table in the development system and did an Initialize with data transfer. Run DTP with extraction mode “Delta” ( 1 st time it extracts data from setup table). save the package and press create. Purchasing (application 02): 2LIS_02_ITM. RSEG is a standard Invoice Verification Transparent Table in SAP MM application, which stores Document Item: Incoming Invoice data. Customized BADI Name – ZPP_DS_2LIS_02_ITM. 2) From the Scheduler dropdown, select the Repair Full Request Option. 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:. KONV KBETR. Wanted to know whether is there any way to find out how many entries are remaining in setup table to be transfered to BW. I did a setup table fill-up of 2lis_03_bf and I'm seeing missing material documents with movement type 561. 0. 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. I'm using OLIG and OLIGBW to fill setup tables but there are certain. Step 2 Create Target table where you want to persist the data. Once we get the above screen, we could specify the component (02, 11, etc…) and click on execute button. The Setup Tables are the objects from which the Business Warehouse system is going to extract data for Full loads and Initialization on LO Cockpit DataSources. EKKO. SYDAT is Item created on - EKPO-AEDAT. with SE11 transaction you can see these tables. Similarly, we can do the same steps (Step1-5). 6C. For all purchasing data you should use Extractors 2LIS_02_ITM, 2LIS_02_HDR and 2LIS_02_SCL . Hi mates, Im using extractor 2LIS_02_ITM in BW, my field Item Category is empty. The activation of the business function by itself will not enhance the database tables. Hi everyone, We are implementing the purchasing solution for the first time at the client. This is how the SAP has defined. Use. We have an issue with the delta's for the 2LIS_11_V_ITM, which is extracting duplicate values. They also extract GR and IR. When I execute the RSA3 for different Datasources I can see data only in. Table of Contents SAP BW/4HANA Content Add-On. BW . I am trying to find the procedure / sequence in to carry out 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:. I then delete the Contents of Setup table for Application '02' - message ""setup tables deleted successfully"". I was successful in extracting data for the 0PUR_C01 cube using the conventional 2LIS_02_S012 datasource. Copy & paste to SE37 eg for 2LIS_02_ITM , extractor MCEX_BW_LO_API is used. The system therefore only executes a delta update for this DataSource if. SD: Delivery Header Data (2LIS_12_VCHDR) - /IMO/CMSD20 . Delivery date (SCLDT)= 01. 2. 2lis 02 Itm Sap Database Tables in SAP (30 Tables) Logistic Cockpit datasources reads from Setup-tables (like MC02M_0ITMSETUP for 2LIS_02_ITM) when you execute Full or Delta-init. READ TABLE i_t_ekpo WITH KEY ebeln = xmcekpo-ebeln ebelp = xmcekpo-ebelp. With no data in setup tables, rsa7, sm13. Just ignore those things. if anyone knows tcodes for runinng the set uptable to each data source separatley. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Deleted the set up tables and ran OLI3BW and filled the set up tables. 0LOG_SYS_BE. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. I cannot see this same field under the same comm. Scenario 2: If 5/10 line items are marked for deletion, Even though I can see their LOEKZ status in EKPO as L,2LIS_02_ITM is being. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. 2. If no data. Empty BW delta queues on R/3 by extraction to BW. Every works ok when executing setup of statistical tables. Overall Picking/Putaway Status. g If a PO item has qty 10 and Price 5 , then the field ekpo-netwr is 50 ( = 10 * 5) Now if this PO item has 3 invoices. On 09. (2LIS_11_V_ITM) - /IMO/CMSD16 . I checked in RSA7 - all 5 DataSources are there. Technical Name of Target InfoObject. I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 . 1. Presss F5 and get inside the form “select_option_fill”. Due to some loads failed, we are doing re-init the loads. When is it necessary to reload the setup table? For Example. 2LIS_02_SCL. . The DSO provides insight into the delivery service of vendors by exploring deviations across the. I can then reference the InfoSources in question since I know HDR data will come ! from EKKO and ITM data will come from EKPO. create ur infostructure using MC21 transaction code. 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. KOSTK. 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. BEDAT. I executed infopackage full load for such sales documents, but 0records are received. RemoteCube Compatible. the situation is that when I run delta it fetches 0 records. 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 . 5. Table of Contents SAP BW/4HANA Content Add-On. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 . 2LIS_02_ITM - Adding fields to communication structure - User exit | SAP Community Relevancy Factor: 1. Application DataSource Setup Table. Source Tables (Function Module): MCEX_BW_LO_API (Function Module) SAP Help, Wiki, Q&A and other resources for 2LIS_03_BF. Note: As an alternative you can also use DHCDCVCDSEXTRE in SE16 which contains more or less the same information. We currently have delta load happening from the same data source. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. Use. Some of the PO items are marked for deletion in the source system (LOEKZ = L). 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. after creating two tbls r created which will handle ur delta. WITH KEY supkz = '2'. In the ECC table EKET these two fields have changed for a given purchase order but the change is not. 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. 2LIS_02_xxx extractors. LIS is customer generated extractors. They are needed in BW and not in R/3. For e. Add a Comment. This form assigns the range entered in selection screen to internal table dd_belnr. The following jobs move the data from the outbound queue to BW. Purchase Invoice Tables. 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. Currently i need direct t-codes to. g. EKPO - Item. where this is using a standard datasource 2lis_02_ITM and 2LIS_02_SCL and i have acitvated this standard cube 0pur_c01. 01. Name of Target InfoObject. png. ZBW_ 2LIS_02_HDR; ZBW_ 2LIS_02_ITM . I chkd EKKO and EKPO and EKPA , from where it is extracted, but dont find BUDAT in these tables. ALIEF - Number of Deliveries. 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. The DSO is directly supplied from the Info/DataSource 2LIS_06_INV. Whereas 2LIS_02_SGR transferred and added records. 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. 14. . "Can you please specific Setup table i. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2. 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. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data: SD - Sales and Distribution: 2LIS_11_VASCL: Sales Document Schedule Line: SD - Sales and Distribution:. Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. But I do not see any entries in the setup table 'MC02M_0ITMSETUP' after the SETUP run. It was huge reload project for us which continued for a. Everything went fine, up to the point wherein i was supposed to perform the [Delete set-up tables / perform extraction] part of the process. 2016 at 02:59 PM GTM 2LIS_46_ITM extraction. Hi, Logistics application ""02 : Purchasing"" (HDR, ITM and SCL) is activated. News & Insights. 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. When does it happen that 2LIS_02_ITM does not add. I know the history has it but, I want to know what is the source for BUDAT in 2LIS_02_ITM. 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. 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. An overview of Datasources and the programs filling the relevant setup table (named MC*SETUP). You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. I have an issue with Purchasing data source: 2LIS_02_ITM. The counted number depends on how often a material appears in a GR document. Mvke Table BW Extractors in SAP (16 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. My data flow is direct load to Info cube using 2lis_02_ITM and SCL datasources. In the second InfoProvider, you can. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. 3) Check the Indicate. ex: 2LIS_13_VDITM. Folder: BW Setup for MC02M_0ACC. The extractor 2lis_02_itm will extract both Purchase Orders and Agreements. Figure 8: BW Control Table – Entry Help/Check . Purchasing 2LIS_02_HDR MC02M_0HDRSETUP Storage BW Setup for. MC11V_0SCL: Extraction SD Sales BW: Allocation Schedule Line for. "Document data restriction" when filling setup table. ECC -> SE11 -> ROOSOURCE -> Both "GENDELTAFD" and "GENDELTATP" are empty too. When I try to do this in the conventional way (in transaction RSA6, button 'E. no (EBELP). FI and COPA is easy to get , the hardest to get at is the LO extractors. Why are the setup tables not filled?If additional information is needed for the tables please let me know. After that, AWS Supply Chain automatically creates the Amazon S3 paths and ingests data from the SAP source tables. Hi We are using the following logic to enhance 2lis_02_itm with different fields from diff tables. SAP. BW-Rebuild for MC02M_0CGR Storage. 2LIS_02_SRV(obsolete) BW-BCT-PA - Personnel Management . Control record it will be having information like Idoc number, message type, idoc type, sender, receiver etc. to fill the setup table. For more information on this topic, refer to the. But <u>it's work with a FULL infopackage</u>. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_S012: Purchasing: MM - Materials Management:. Fill the setup tables with historical data using SBIW to get to the tcode OLI*BW. I wonder why the same is not getting extracted when I check in RSA3 for Data Source 2LIS_02_ITM. We could able to see the enahnced field data in RSA3 , but after making any change in ME22n its not p. 2LIS_03_BF. Not just "LO DataSources" because there are some that don't use this feature. Technical Name. I also know that my InfoSources for this data are 2LIS_02_HDR, 2LIS_02_ITM, and 2LIS_02_SCL. This table stores the mapping rules. Follow the below steps to get the lost delta, will be useful for any loads. Filled with the 2-digit logical original backend system (based on ORGLOGSY ). About this page This is a preview of a SAP. It s failing for only 2LIS_02_ITM only. Determine Industry Sector. That means setup process wasn't happen correctly. SAP BW/4HANA Business Content delivers. cat = F ) . These indicators and key figures are based on the associated confirmation and goods receipt documents. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. 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. Follow RSS Feed HI Experts, i am abaper. ”VT_2LIS_02_ITM”). This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). My plan is to perform below steps. where ebeln = c_t_data-ebeln. 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. Date of Purchasing Document. Sep 16, 2009 at 06:26 PM. 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. PO Deletion Indicator. 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:. 2LIS_02_ITM - Adding field problem | SAP Community Relevancy Factor: 1. e 4. Fill setup table. All the data is updated to standard table like VBAK , VBRK, LIKP. Please note , Everything is fine with setup table data , update rule ( Overwrite mode) and other BW part. T-Code Purpose. first run Init without datatransfer. 2lis_11_v_itm. I saved and Activated the data source. 2lis 03 Bf Table BW Extractors in SAP (29 BW Datasources) Login; Become a Premium Member; Transaction Codes; Tables. Append MCEKPO. (Account Level) (2LIS_02_ACC). Application Component. Like I activated the datasources in LBWE than I intialised all datasources. Important Key Figures: ROCANCEL. - Process Key 002:GR. BSTYP. 2LIS_02_ITM is a purchasing extractor, mkpf et mseg are inventory table. 4. and choose the industry sector "Standard (Core)". MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. Type of DataSource. 2LIS_02_ITM Purchasing Data (Item Level) MM - Materials Management: 14 : 2LIS_05_QE2 Inspection Result: Quantitative Data QM - Quality Management: 15 :Transformation. The corporate memory is filled independently of the EDW core layer’s update. ) We had a similar scenario where we wanted to refresh entire data for 2LIS_13_VDKON. Relevancy Factor: 1. (2LIS_11_V_ITM) - /IMO/CMSD16 . Sap Tcode Ksbt Tables in SAP. The three others (2LIS_46_HED ; 2LIS_46_CFM ; 2LIS_46_GTM) are not showing any data : see attached picture issue. (2LIS_02_ITM). 2. The indicator Field known only in Exit is set for the fields in an append structure, meaning that by default, these fields are not passed to the extractor in the field list and the selection table. 2LIS_02_ITM. 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. 2LIS_02_ITM - Set up Table. In this case use FM EXIT_SAPLRSAP_001 as template. 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. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_CGR: Produced Activity: Delivery of Confirmations: MM - Materials Management: 2LIS_02_SCN: Produced Activity: Confirmation of Schedule Lines: MM - Materials Management:. 2LIS_02_ACC. ) 2LIS_02_ITM. 2lis 04 P Arbpl Tables BW Datasources Most important BW Extractors for 2lis 04 P Arbpl Tables # BW DATASOURCE Description. Then I will build a ODS on top of these extractors. eg: if i do the following action: Fill 1 -> Delete - Fill 2. Processkeys are maintained. 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. SAP BW/4HANA. If no data inbound. 3. This means the persistence of data for this. We are analbe to get the records for "Pruch Docu Catgory" = L(Scheduling Agreement). 0. When looking in the EKPO table, you'll get an 'X' in the Elikz field when completed, however in the extractor you do not have simply one row with the most recent value, you'll have. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. so I add field CHARG into that datasource. 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. Apparently these two fields are NOT updated in BW from a delta load. We can replace the contents of internal dd_belnr through flat file upload. 2lis_11_v_ssl. It contains the complete history of the loaded data. 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. In EKET Table the primary key is based on 3 fields. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data. Recommence extraction into BW from the modified R/3. Technically, during the full load, these items should be extracted with a recordmode = R. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. SAP BW/4HANA. Create column table “02_ITM” as (select * from “INF627126″. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 3 :. 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. (2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL in my case), if we have to do full upload, do we still need to run the setup in R/3. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. LO Cockpit - Basic Question. 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 :. These fields are populated in the extractor and not stored in any tables. Source System for R/3 Entity*. 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. FIELD-SYMBOLS: <LS_DATA> TYPE MC02M_0ITM, <LV_KUNNR> TYPE EBAN-KUNNR,. 100 -> 100 -> 200. 799 Views. DataStore object (advanced): SD: Billing Document Item Data (2LIS_13_VDITM) - /IMO/CMSD31. if you put EKET then it brings up. There is a table that maps movement type to process key. 0B, InfoSource 2LIS_04_P_MATNR replaces InfoSource 2LIS_04_S280. Apply the changes / Transport. News & Insights. (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. ) 2LIS_02_SCL & 2. MC02M_0ITM. Purchasing Data (Schedule Line Level) NA. I am using the 2LIS_02_ITM extractor. For information, I had the same problem with 2LIS_02_ITM. Custom Duty 14% JCDB . The modeling property Inbound table as extended table has been turned on. MC11VA0STI: Extraction MD Order Item Status for DataSource 2LIS_11_VASTI. 48. 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. There I see data only for some extractors (2LIS_46_SCL and 2LIS_46_ITM) : see attached picture issue-gtm-01. Hi, I am using 2lis_02_itm and 2lis_02_hdr. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. I am able to see the newly added field in the structure, However when I test the datasourcein RSA3. 2. 2lis 02 Itm Database Tables in SAP (23 Tables) MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/PUR_IS11. EKES is a standard Purchasing Transparent Table in SAP MM application, which stores Vendor Confirmations data. (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. 02 Purchasing 2LIS_02_ACC MC02M_0ACCSETUP Folder: BW Setup for. The system therefore only executes a delta update for this DataSource if. 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. I now am trying to get publishing back on track. select * into table lt_ekko from ekko for all entries in c_t_data. This is available in SBIW. then data inconsistency will be happen. You can see the table in the above screen shot. PO Item Deletion Indicator (LOEKZ) 123456 10 L. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). 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. . Customer-Defined DataSource Logistics Management of Extract Structures Initialization Fill Recompiled Tables Application-Specific Recompilation Purchasing – Carry Out Recompilation. The EKPO table ( Purchasing. These documents are also not getting filled into Setup Table by OLI3BW. g. Media-Specific Adjustments to the InfoSource Order Item Data (as of 2. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 7 :. and do repair Full for whole data. (2LIS_11_V_ITM) - /IMO/SD_IS16 . MC02M_0SCLSETUP. Implemented class Name – ZCL_DS_2LIS_02_ITM. This DSO (advanced) contains delivery related indicators and key figures for purchase order items. Two lines are extracted.