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. 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. g. Available as of OLTP Release. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 7 :. SCL dS will trigger delta with GR and IR. DataStore object (advanced): SD: Delivery Item Data (2LIS_12_VCITM) - /IMO/CMSD21. The following foreign key relationships have to be maintained. They are needed in BW and not in R/3. SAP Table Field : BUDAT - Posting Date Top 200 SAP Tables containing the field/column BUDAT. I have already done the following steps: 1 - Transaction SBIW: Settings for Application-Specific DataSources (PI) Logistics. Technical name: 2LIS_02_HDR . Datasource For Afko And Afvc Tables BW Datasources. I have pasted the eror message below for reference. Extraction Table PFO_GO_00IV (Portfolio Assignment) - 13 : 2LIS_12_VCITM Delivery Item Data SD - Sales and Distribution: 14 :Use. e 4. The details are as below:2LIS_11_VAITM Data Source is not fetching data | SCN. where this is using a standard datasource 2lis_02_ITM and 2LIS_02_SCL and i have acitvated this standard cube 0pur_c01. Run info pack with init without data transfer. -----Mensaje original-----De: John Parks via sap-r3-bw [mailto:sap-r3. 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. after creating two tbls r created which will handle ur delta. 1) Go to the RSA6 (Find ur datasource 2LIS_02_ITM double click on it ) 2) Double click on the extract structure 3) You will see extract structuter then you can see the append structure at the top left click onit 4) Give the name of the structure 5) Enter the NEW field starting with "ZXXXXX" 6) Save it 7) Go to Cmod and then create a project 8) The assign components as EXIT_SAPLRSAP_002 (for. I also have checked that: 1. Upon trying, i have encountered many problems: 1. Purchasing Group Tables. MC11VA0STH: Extraction MD Order Header Status for DataSource 2LIS_11_VASTH. (2LIS_02_ITM). Root Cause: If a PO Item in P20 is. 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. That means that you can use this DataSource both for data replication in a BW system (SAP Business. 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. Maintain Extract Structure MC02M_0ITM. I am using the 2LIS_02_ITM extractor. 123456 30 - 123456 40 - 123456 50 - EKPO table r/3. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. Even I have tried again by deleting the setup tables & then fileed it but syill cant see data only in 2lis_02_sclI am loading 0PUR_O01 from 2LIS_02_ITM/SGR/CGR and SCN. 0. Transport the Enhanced Data source to Source SAP system . 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. SD: Delivery Header Data (2LIS_12_VCHDR) - /IMO/CMSD20 . Please provide a distinct answer and use the comment option for clarifying purposes. I'm using OLIG and OLIGBW to fill setup tables but there are certain documents/contracts I can. 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:. TXTMD. I have added field LOEKZ (Deletion indicator) to datasource 2LIS_02_ITM from t-code LBWE and activated. Francisco Milán Campos. 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. Hi Fabio, No You cannot do a setup for 2LIS_02_ITM only, You can only do a setup for the whole 2LIS_02. When is it necessary to reload the setup table? For Example. RSS Feed. 2LIS_02_SRV (obsolete) The 2LIS_02_SRV data structure is new for the EHP3 and there are some steps to activating it. 4. CLEAR LT_DATA. RSS Feed. In LBWE, it says EKKO-SYDAT but it is from EKPO (*) 2LIS_02_ACC. Transaction Data. 2lis_11_vascl. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Remove the Field known only in Exit indicator. 3. then go to T- Code OLI9BW. create ur infostructure using MC21 transaction code. 63 Views. Mapped to InfoObject. Setup Table 2lis 02 Itm TCodes Most important Transaction Codes for Setup Table 2lis 02 Itm # TCODE Description Application; 1 : SE11: ABAP Dictionary Maintenance Basis - Dictionary Maintenance: 2 : SM30: Call View Maintenance Basis - Table Maintenance Tool: 3 : SE16: Data Browser Basis - Workbench Utilities: 4 : SE38:Run RSA3 on the datasource 2LIS_02_ITM, find the extraction program field ROCANCEL(Indicator: Cancel Data Record) for doc1 are all null for each doc1 item that this field ROCANCEL fails to catch EKPO deletion indicator field LOEKZ value for these two deleted item 1 and item 4 showed in table EKPO with value of 'L' for item 1 and item 4. Step three:. 3) Check the Indicate. ECC -> SE11 -> ROOSOURCE -> Both "GENDELTAFD" and "GENDELTATP" are empty too. Hi everyone, We are implementing the purchasing solution for the first time at the client. Sales Document Item Data (2LIS_11_VAITM) - /IMO/CMSD11. I have read that it is necessary to delete the setup tables before reloading the setup tables to make sure that there is no duplicate data, however I have different question. Can see Queue 2LIS_11_VAHDR. ex: 2LIS_13_VDITM. Two lines are extracted. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 0FI_AP_4. 2LIS_02_ITM : MC02M_0ITMSETUP : Storage BW Setup for MC02M_OITM : Purchasing :. 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. Currently i need direct t-codes to. Symptom. 1. Sap Tcode Ksbt Tables in SAP. PLAF is a standard Master Data Transparent Table in SAP PP application, which stores Planned order data. In EKET Table the data is like. My data flow is direct load to Info cube using 2lis_02_ITM and SCL datasources. Where in BW should be stored the data about secondary costs on purchase (acquisition) which evaluate the real price of goods?. Sep 16, 2009 at 06:26 PM. We could able to see the enahnced field data in RSA3 , but after making any change in ME22n its not p. In LBWE, its showing that LOEKZ is taken from EKPO. I wonder why the same is not getting extracted when I check in RSA3 for Data Source 2LIS_02_ITM. Delete the setup Table using LBWG . Hi mates, Im using extractor 2LIS_02_ITM in BW, my field Item Category is empty. Filled with the 2-digit logical backend system (based on LOGSY) Logical System Backend. Available as of Plug-In Release. 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. * For more information about source system IDs, see SAP HANA-Optimized BI Content. Purchasing Organization Tables. There is a requirement to load full load to BW system from 2LIS_02_ITM data source. I was successful in extracting data for the 0PUR_C01 cube using the conventional 2LIS_02_S012 datasource. 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. and enhanced the datasources ITM and SCL adding one Char in. I have also deleted the setup tables and filled them again. 3. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. Marco. FAQ: Setup table filling with 2LIS* extractors. You should find table names here. Data Source:2LIS_02_ITM, Note: Field LOEKZ of table EKPO is the deletion indicator for an item in P20. Settings: Purchasing. PO Deletion Indicator. I use the standard extractor 2LIS_02_ITM (order positions) with the update mode "Direct Delta" and apanded Z-fields. There I see data only for some extractors (2LIS_46_SCL and 2LIS_46_ITM) : see attached picture issue-gtm-01. By debugging function module MCEX02_PREPARE_INFO it was found that the field UPDACT in table TMCEXACT. KNTTP – Account Assignment Category. Follow. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Read more. Step 1: Get the name of tables affected by the lost delta data source. Description: Sales-Shipping Allocation Item Data. Thank-You. 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. Thanks for the quick response. Select the Data Source ( 2LIS_02_ITM ) 3. Data Source 2LIS_02_SRV used for extraction of (Services Procurement) service line data to BW is made available with ECC 6. 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)). 2lis_11_v_ssl. You get this message , when you execute MCB_ " View/table V_TMCLBW can only be displayed and maintained with restrictions" 2. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. and added a Z-field (ZZEKKOL) for this field. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Item Level) ( 2LIS_02_ITM ). Compare with setup table records. 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. The system therefore only executes a delta update for this DataSource if. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . MC02M_0CGR Storage. (Which acts also as delta queue similar to RSA7). MC02M_0ITM is a standard Logistics Information System (LIS) Structure in SAP LO application. Data Modeling Relevancy Factor: 2. select * into table lt_ekko from ekko for all entries in c_t_data. However, when I want to re-extract ""Purchasing"" I get a message ""Data source 2LIS_02_HDR contains data still to be transferred"". Step 1: Move ECC TR to ECC- PRD system. Step 4: Delete set up table. For more information on this topic, refer to the. Login; Become a Premium Member; SAP TCodes; Tables. 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. ERROR MESSAGE DUMP for DBIF_RSQL_INVALID_CURSOR ***** Runtime Errors. The system therefore only executes a delta update for this DataSource if. I did a setup table fill-up of 2lis_03_bf and I'm seeing missing material documents with movement type 561. Purchasing 2LIS_02_ITM MC02M_0ITMSETUP. It is from BEDAT from EKKO and EKBE. MC11VA0STI: Extraction MD Order Item Status for DataSource 2LIS_11_VASTI. Everything went fine, up to the point wherein i was supposed to perform the [Delete set-up tables / perform extraction] part of the process. Relevancy Factor: 1. 2LIS_02_xxx extractors. ) 2LIS_02_SCL & 2. I can see the data for other datasrcs related to purchasing like 2lis_02_itm data in rsa3 . Table of Origin. 2LIS_03_UM. are extracting data, the 2 mentioned in the subject line do not extract any data. Purchasing document 4500000001, Item 0010, has the following schedule lines: Schedule line number (SCLNR) = 1. WITH KEY supkz = '2'. - Process Key 003:IR. Diagnostics. Moreover STAPO (Item is statistical) = X, means Item is statistical. In the second InfoProvider, you can. We do not have down time. Then use the function Activate and Schedule to start the process chain according to your scheduling options. Go to. If I missed to search something please provide that. 2. Relevancy Factor: 6. Delta Process: Delta Queue based. These fields are populated in the extractor and not stored in any tables. Once we execute, it would give us the below screen for confirmation. Step 3: Move BW TRs to BW PRD system. LFA1 NAME1. 2LIS_11_V_ITM. Folder: BW Setup for MC02M_0ACC. 1. ebeln = xmcekpo-ebeln. 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_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 :. I created the setup tables via "Purchasing - Perform Setup", but only 3 setup tables were filled. 2lis_13_vdkon. what is the reason , pls. Former Member. Similarly, we can do the same steps (Step1-5). As of SAP enhancement package 6 for SAP ERP 6. There is a table that maps movement type to process key. Bobby. I have already maintain datasource 2LIS_02_ITM through LBWE. However, InfoCube for Purchasing ( 0PUR_C01) is already active in the system and delta are being loaded into it on a regular. Run the Delta Info package in BW to update all the data i. That means setup process wasn't happen correctly. or alternatively you can build your own custom extractor using purchasing tables EKKO,. Is there any particular reason? I looked up the configuration of the movement types by going into. Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. SAP R/3 Enterprise all versions Keywords. 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. AND ebelp = mc02m_0itm-ebelp. The records have the deletion indicator LOEKZ set to L in EKPO and are correctly getting updated with Recordmode 'R' and negative keyfigures in the PSA of datasource 2LIS_02_ITM. I tried deleting the setup table (LBWG) and tried again initialization (OLI3BW) but I cant. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. 0. 2LIS_02_ITM. then data inconsistency will be happen. 123456 10 L. . 123456 20 L. If a data inbound layer persistence and/or a corporate memory persistence is used, the transformation from this DataStore. This is how the SAP has defined. Table of Contents SAP BW/4HANA Content Add-On. 2LIS_02_CGR 2LIS_02_SGR 2LIS_02_SCN. Purchasing Data (Schedule Line Level) NA. 2LIS_02_SRV(obsolete) BW-BCT-PA - Personnel Management . All the data is updated to standard table like VBAK , VBRK, LIKP. 2. Copy & paste to SE37 eg for 2LIS_02_ITM , extractor MCEX_BW_LO_API is used. Item 20 is deleted. The account. I have a problem with the delta. The 2lis_02_itm documentation says that the field NETWR (Net PO value) is picked up directly from table field EKPO-NETWR. 0. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. (We are not going to delete any data from application tables. 4. Datasource Jest Table BW Extractors in SAP (25 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. Field PSTYP. MM - Materials Management: 10 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 11 : 2LIS_13_VDITM: Billing. The DSO provides insight into the delivery service of vendors by exploring. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. 94 Views. The account assignment category determines the account assignment data for an item, such as cost center and account number. iam loding data for purchasing data using 4 data sorses. 4. Clear "LBWQ" 04. This InfoSource contains the structure to provide purchase data on item level into the EDW Core Layer. 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. Wanted to know whether is there any way to find out how many entries are remaining in setup table to be transfered to BW. # Table. SD Sales Orders. . A goods movement is posted with the following information: Posting date (BUDAT) = 05. 48. Situation 2. But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. no (EBLEP) and delivery schedule line counter (ETENR). 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:. It contains the complete history of the loaded data. 2lis_02_itm Structure is active. 100 -> 100 -> 200. Purchasing Document Category. 2lis_11_vakon. Hi, when you delete the setup table for 2LIS_02_ITM, it will show that still data exist for other DS. i need to get the data from different tables. Code - 'oli2bw'. FI and COPA is easy to get , the hardest to get at is the LO extractors. During the initial load, everything comes along fine all the way to PSA. Deleted the Setup tables. An overview of Datasources and the programs filling the relevant setup table (named MC*SETUP). 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_11_VAHDR:. 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. It is located under materials management --> Purchasing. from the standard tables using a Business content Data Source the Data should be Extracted to BW system. Transformation * For more information about source system IDs, see SAP HANA-Optimized BI Content. Why? What am i missing out do i need to do any changes before i actiavte the in-active tables in LO-Cockpit. Hello, while testing extraction of 2LIS_02_ITM and 2LIS_02_SCL (rsa3), the system tells me ""0 data records selected"" even when I did everything before correctly: - LBWE - activation and set of direct delta - set application active indicator - customize industry sector - deleting setup tables - creating the statistics from the historical data. 2lis 11 Vaitm Ecc Source Tables BW Datasources Most important BW Extractors for 2lis 11 Vaitm Ecc Source Tables # BW DATASOURCE Description Application; 1 :. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. PO Cancellation of data record Entry. These fields are populated in the extractor and not stored in any tables. 0. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) -. In ekpo screenshot you can find final Invoice flag is set (EKPO-EREKZ) for all the PO line. Technical name: 2LIS_12_VCITM. Use. Hi All, Im working with 2lis* extractor from Lo Cockpit, and i have the followings questions: 1)For example, im using 2lis_02_itm extractor: I have filled the setup tables on 09. Hi We are using the following logic to enhance 2lis_02_itm with different fields from diff tables. 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. Prerequisites. 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. 0. Vote up 2 Vote down. They also extract GR and IR. Sap Supply Chain Management Tables in SAP. Or if you are looking for OSS NOte #. Rohan, Looking at EKBE is correct. 123456 30 - 123456 40 - 123456 50 - 2lis_02_itm Setup Table. 2LIS_02_ITM - Set up Table. Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. In the ECC table EKET these two fields have changed for a given purchase order but the change is not. Environment. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). 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 ). I can then reference the InfoSources in question since I know HDR data will come ! from EKKO and ITM data will come from EKPO. 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. Is it the right method or should it have been add. SAP. Datasource is in active mode. The data is not updated into the upur_c01 cube . But when the user changes only the account assignment of an outline agreement , without changing any other fields (e. (2LIS_11_V_ITM) - /IMO/CMSD16 . However, when we do delta-load, none of the account. All, Can we run a set up table job (LO datasources) (in case of purchasing program RMCENEUA) parallely in (R/3)production environment by checking the block documnet option with different document date in selection ? The reason for this is that if we go with this option we can schedule. 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. MCEX03. LIS uses v1 and v2 update modes only. Release Strategy Tables. This. Here is the code: LOOP AT xmcekpo. (Account Level) (2LIS_02_ACC). On top of this, setup table was filled, but I see no data for 2lis_02_itm. This DataSource replaces DataSource 0FI_AP_3 (Accounts Payable: Line Items) and uses the same extraction structure. DataStore object (advanced): SD: Billing Document Item Data (2LIS_13_VDITM) - /IMO/CMSD31. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. Apparently these two fields are NOT updated in BW from a delta load. we have the V3 update job, running every 15 minutes. RSA3 for 2LIS_02_ITM,2LIS_02_SCL , 2LIS_03_BX, 2LIS_03_UM shows data but it does not get updated to the cube ( 0PUR_C01, 0IC_C03). Use. 2016 at 02:59 PM GTM 2LIS_46_ITM extraction. Login; Become a Premium Member; SAP TCodes; Tables. #. There is a table that maps movement type to process key. If you followed below steps, no chance to miss single reocrd. 2LIS_02_ITM - Adding field problem | SAP Community Relevancy Factor: 1. On 09. "Image/data in this KBA is from SAP internal systems. SAP Knowledge Base Article - Preview. enhancing through function module in 2lis_02_itm. Status record it will be having different statuses like idoc created,idoc posted etc. Use. Yes. 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. with SE11 transaction you can see these tables. If they don't solve delta queue I'll report to SAP. EKKO - Header. So we created an append structure to MC02M_0ITM. Delivery Item . Vendor Master Data Tables : LFA1: Vendor master data general section LFB1 : Vendor Master Company Code. Purchasing. This is to keep data that is depending on each other consistent. 339 Views. I chkd EKKO and EKPO and EKPA , from where it is extracted, but dont find BUDAT in these tables. No. In RSA7 i purged or deleted the records and entry for this datasource. 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. This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). 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. But these datasource read data from EKKO, EKPO & EKBE table and material document number field is availble in EKBE. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW > Settings for. I have loaded an initial load to my ODS (0BBP_PO) and also setup a delta. my question is what transaction code can I see this field in BW Table. Source System for R/3 Entry*. Date of Purchasing Document. This DSO (advanced) contains delivery related indicators and key figures for purchase order items. Transaction data. For item 20, LOEKZ = L (Deletion indicator). 04. 3. BEDAT. Data load for :2LIS_02_HDR. 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. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: Glossary/Terms related to ERNAM ProfileWhen extracting from a single table, do that in a standard data flow. 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_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. Test using RODPS_REPL_TEST , SUM = 0 in the result. But <u>it's work with a FULL infopackage</u>. Gross Price P001 / P000 / PB00 / PBXX . In LBWQ no entry for MCEX02 exist. Implemented class Name – ZCL_DS_2LIS_02_ITM. Name of Target InfoObject.