You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Important Key Figures: ROCANCEL. Transaction data. Add a Comment. 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. However I observed a different behaviour in case of POs with an Invoicing Plan ( mostly framework POs) E. 2LIS_02_ITM Not Updating Setup Tables In Initialization Summary. Because when you fill any Purchasing DataSource (i. Thank-You. SAP Tables SAP Table Fields (New) SAP Glossary Search. ALIEF - Number of Deliveries. Gross Price P001 / P000 / PB00 / PBXX . Urgent help required. 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. READ TABLE lt_ekko into wa_ekkoTable YBWMAPPING is used by the class YCL_BW_MAPPING. #. Purchasing 2LIS_02_HDR MC02M_0HDRSETUP Storage BW Setup for. Thank you all four you responses. Purchasing document 4500000001, Item 0010, has the following schedule lines: Schedule line number (SCLNR) = 1. Now when I click on Initialization >Fill Setup Tables >Perform Setup Purchasing, i get the following message at the status bar: ". 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. I cannot see this same field under the same comm. 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: Full & Delta: Inventory Management: Material Management: 2LIS_03_BF: Full & Delta: Production Planning: Production Planning: 2LIS_04_P_MATNR: Full & Delta: Sales:. The issue is when I ONLY change the. When I try to load setup data I got this message in setup table. 05. 02. we have the V3 update job, running every 15 minutes. From what I read, i think i'm missing the following steps, from which I need more detail:EKBE table has Purchase Order History data and MSEG has Document Segment: Material data in it. I can then reference the InfoSources in question since I know HDR data will come ! from EKKO and ITM data will come from EKPO. "2LIS_02_SCN MM MC02M_0SCN Achieved Performance: Confirmation of. We are analbe to get the records for "Pruch Docu Catgory" = L(Scheduling Agreement). Issues in Filling Setup table for 2LIS_02_HDR | SAP Community Relevancy Factor: 1. Situation 2. Transformation * For more information about source system IDs, see SAP HANA-Optimized BI Content. - Process Key 002:GR. g. Select the Data Source ( 2LIS_02_ITM ) 3. This gives me a message 'Date fields for info structure S032 are not. Data source. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. Base Tables . There is a table that maps movement type to process key. (Account Level) (2LIS_02_ACC). It would be really helpful to know the used tables for datasource 2LIS_02_ITM. Currently I'm trying to figure out what the logic is behind determining the most recent 'Delivery Completed Indicator' (2LIS_02_ITM-ELIKZ) value ('True' or 'False). Root Cause: If a PO Item in P20 is. We have data sources 2LIS_02_ITM, 2LIS_02_CGR, 2LIS_02_SCR and 2LIS_02_SGR activated and up and running delta properly. When running the setup for application 02 (TR OLI3BW), the table was not filled: running RSA3 with no restrictions did not retrieve any records. In this extractor we have enhanced "PS_PSP_PNR" (WBS Element) field whose values are being stored in "Account Assignment in Purchasing Document" table. Moreover STAPO (Item is statistical) = X, means Item is statistical. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. Field PSTYP. SAP R/3 Enterprise. We have an issue with the delta's for the 2LIS_11_V_ITM, which is extracting duplicate values. 0B) ( 2LIS_11_VAITM ), is used to update the Media Product Sales (M/PS) data targets, for which the SD order document is used as the basis. where ebeln = c_t_data-ebeln. Data load for :2LIS_02_HDR. While doing the statistical setup i am using the T. Scheduling Agreement Tables. Fill the Set up Tables with Data Tcode : SBIW (to fill setup tables) Expand Settings for Application Specific Data Sources (PI) ----> Expand. enhancing through function module in 2lis_02_itm. This table stores the mapping rules. (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. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). I have added field LOEKZ (Deletion indicator) to datasource 2LIS_02_ITM from t-code LBWE and activated. PO Deletion Indicator. Transaction Data. . Delta queue maintenance. Please note , Everything is fine with setup table data , update rule ( Overwrite mode) and other BW part. Relevancy Factor: 6. The three others (2LIS_46_HED ; 2LIS_46_CFM ; 2LIS_46_GTM) are not showing any data : see attached picture issue. Figure 8: BW Control Table – Entry Help/Check . Transa ctional. Some of the PO items are marked for deletion in the source system (LOEKZ = L). For e. The modeling property Inbound table as extended table has been turned on. No. Former Member. we have done initialisation and filled setup tables. Runn full load. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_12_VCITM: Delivery. Table of Contents SAP BW/4HANA Content Add-On. MC02M_0ITM: Extraction Purchasing (Item) for DataSource 2LIS_02_ITM. RSS Feed. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. To stop the access from outside we use t-code SM01 to. then go to T- Code OLI9BW. Former Member. 5B. 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. 4. I checked in RSA7 - all 5 DataSources are there. 2LIS_02_SRV(obsolete) BW-BCT-PA - Personnel Management . 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. 2lis 04 P Arbpl Tables BW Datasources Most important BW Extractors for 2lis 04 P Arbpl Tables # BW DATASOURCE Description. Name of Target InfoObject. SAP delivers the following example BEx queries on top of MultiProviders Sales Overview. with different condition types fromo KONV table . Go to RSA6. If they don't solve delta queue I'll report to SAP. So I did the following steps : 1. I have a problem with the delta. Transformation. The system therefore only executes a delta update for this DataSource if. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. 5. With no data in setup tables, rsa7, sm13. MC02M_0ITM. It is located under materials management --> Purchasing. but not in. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 . EKKO. All 3 2lis_02_itm, hdr and scl were enhanced to add additional fields. Functional Area:. Hi all, 1. These indicators and key figures are based on the associated confirmation and goods receipt documents. Purchasing Data (Schedule Line Level) NA. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 0. IF i_datasource = '2LIS_02_ITM'. SCL dS will trigger delta with GR and IR. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. DataStore object (advanced): SD: Delivery Item Data (2LIS_12_VCITM) - /IMO/CMSD21. Replicate the same in BW system. With no data in setup tables, rsa7, sm13. we have datas (ekko,ekpo) 2. if you put EKET then it brings up. Application: SD - Sales and Distribution. 12. ECC -> SE11 -> ROOSOURCE -> Both "GENDELTAFD" and "GENDELTATP" are empty too. Read more. BSART. LOOP AT c_t_data INTO mc02m_0itm. 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. In the standard extractor 2LIS_02_ITM the field BADAT is check as Field only known in customer exit. And after the setup table is filled, data in 2LIS_02_SRV gets duplicated. There is a requirement to load full load to BW system from 2LIS_02_ITM data source. Ship-to Party. Info Record Tables. 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. SAP BW Datasource : 2LIS_02_SCL - Purchasing Data (Schedule Line Level). For information, I had the same problem with 2LIS_02_ITM. 2LIS_02_CGR 2LIS_02_SGR 2LIS_02_SCN. Field in Table of Origin. 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. BW-BCT-PM (Plant Maintenance). 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. 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. 04. Please provide a distinct answer and use the comment option for clarifying purposes. Run the collective run, so all the data is sent into the delta queues. MC11V_0ITM: Extraction SD Sales BW: Document Item Allocation for DataSource 2LIS_11_V_ITM. KNTTP – Account Assignment Category. The Problem is, that the setup tables are not getting poulated. Determine Industry Sector. How can I find which tables in R/3 are the source tables for this and that extractor (e. I'm using OLIG and OLIGBW to fill setup tables but there are certain. Wanted to know whether is there any way to find out how many entries are remaining in setup table to be transfered to BW. 11. Before fill setup I have done pre requisites as follow, 01. Is there any particular reason? I looked up the configuration of the movement types by going into. Customer-Defined DataSource Logistics Management of Extract Structures Initialization Fill Recompiled Tables Application-Specific Recompilation Purchasing – Carry Out Recompilation. 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. 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 . are extracting data, the 2 mentioned in the subject line do not extract any data. I checked the function module also , but still in process, any suggestions would be greatly appreciated. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. The DSO provides insight into the delivery service of vendors by exploring. 2LIS_13_VDKON: Billing Condition Data. Source table: EKET (Scheduling Agreement Delivery Schedule Lines) Extract structure: MC02M_0SCL. Hi, Where can i find the t-codes for filling the setup table for all the logistics datasources. Login; Become a Premium Member; SAP TCodes. Code - 'oli2bw'. Sales Document Item Data (2LIS_11_VAITM) - /IMO/CMSD11. 1) 1) Create/Find a Full Repair Infopackage in 2LIS_11_VASCL datasource in BW system. Step 2 Create Target table where you want to persist the data. 2LIS_02_ITM: DS only for Direct Access, 2181511: 0MM_PUR_PO_SCL: 2LIS_02_SCL: DS only for Direct Access, 2181511: 0MM_PUR_PO_SCN: 2LIS_02_SCN. transfered datasource 2LIS_02_ITM using tcode RSA5. Filled with the 2-digit logical backend system (based on LOGSY) Logical System Backend. 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. now i want to fill setup tables for below datasources, can you suggest what are tcodes to fill up setup tables for below datasources. 0OPS_12_ITM. 0) Basis - BW Service API: VBDATA: Update data: Basis - Client/Server Technology: BW Datasources related to RMBWV302 BW DATASOURCE Description Application ;. that all records from 2LIS_02_ITM are deleted in the START routine. From. The DSO is directly supplied from the Info/DataSource 2LIS_06_INV. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. 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. Source System for R/3 Entry*. SAP BW/4HANA. To reach the customising node use transaction OMGO. The fields concerned are located in one of the Purchase Order screens (ME21). Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. "Document data restriction" when filling setup table. By debugging function module MCEX02_PREPARE_INFO it was found that the field UPDACT in table TMCEXACT. Data Source:2LIS_02_ITM. MC11V_0ITMSETUP. The following foreign key relationships have to be maintained. 2008 i have executed Initial Load from BI. SAP. Purchasing. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . Login; Become a Premium Member; SAP TCodes; Tables. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . The system always converts the net price to the local currency and to the base unit of measure. 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. The 2lis_02_itm documentation says that the field NETWR (Net PO value) is picked up directly from table field EKPO-NETWR. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 3) Check the Indicate. 2lis 11 Vaitm Ecc Source Tables BW Datasources Most important BW Extractors for 2lis 11 Vaitm Ecc Source Tables # BW DATASOURCE Description Application; 1 :. Fill setup table. 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. Application; 1 : 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 : 2LIS_11_VAITM: Sales Document Item Data SD - Sales and Distribution: 3 : 0CO_OM_OPA_6:. 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:. Delete content of ODS/CUBE. 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. where this is using a standard datasource 2lis_02_ITM and 2LIS_02_SCL and i have acitvated this standard cube 0pur_c01. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). after creating two tbls r created which will handle ur delta. In my example, I focus on an potential alternative to the classic LIS DataSource 2LIS_02_ITM (MM Purchase Order Items): C_PurchaseOrderItemDEX is a released delta-enabled CDS extractor. Then I. You can see a relationship between this tables in the web site and click on the link "SAP MM, SD, FI, PS, PP, PM, HR, System Tables". If I missed to search something please provide that. cat = F ) . Vote up 2 Vote down. e. . When I execute the RSA3 for different Datasources I can see data only in. I have been using DataSource: 2LIS_02_ITM for couple of months and I have loaded data into (Full and Deltas). Also you can see same in Transaction code ME80FN. With this process chain, the initial data set is updated (initialization of the delta process) in the data targets affected (InfoArea. Step 4: Delete set up table. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) (2LIS_02_SCL). Figure 7: BW Control Table – Fields . Follow RSS Feed HI Experts, i am abaper. This means the persistence of data for this. 2. In EKET Table the primary key is based on 3 fields. Go inside the class ZCL_DS_2LIS_02_ITM and implement the below code – ATA : LT_DATA TYPE STANDARD TABLE OF MC02M_0ITM. This document has 2 parts. ebeln = xmcekpo-ebeln. Comparing DataSource 2LIS_02_SGR to ME80FN. Home. I saved and Activated the data source. 2. 2LIS_02_CGR. Check the source system connectivity. A goods movement is posted with the following information: Posting date (BUDAT) = 05. See SAP Service Marketplace, SAP Note 0448600 for more information on prerequisites. to fill the setup table. OLI1BW INVCO Stat. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . Bobby. Use. correct me if iam wrong. I'm want to use some 2LIS_02* extractors (2LIS_02_HDR, 2LIS_02_ITM and 2LIS_02_SCL) to cubes 0PUR_C01 and 0PUR_C04. Just ignore those things. Datasource Type: Transaction Data Extractor. This counter determines the number of deliveries based on the GR document items. Processkeys are maintained. 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. LO-IO. 2. sap and forums i found out that for. These fields are populated in the extractor and not stored in any tables. Hi All, When a PO is posted the vaules are being picked by the 2LIS_02_ITM extractor. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Step 5) Choose the datasource 2LIS_02_ITM and go to the Datasource tab and click Change the datasource as shown in screenshot. Go to LBWE (LO Cockpit), select DataSource 2LIS_02_SCL, click on Maintenance icon in Structure column, say Continue. i need to get the data from different tables. Whereas 2LIS_02_SGR transferred and added records. select * into table lt_ekko from ekko for all entries in c_t_data. Vote up 0 Vote down. Whenever setup table is deleted for application 02, all records for data sources 2LIS_02_HDR, 2LIS_02_ITM & 2LIS_02_SCL becomes zero in RSA3, but 2LIS_02_SRV will contain data. I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 . PO Item Deletion Indicator (LOEKZ) 123456 10 L. You have to enhance the data source if the field is not available to you. Compare with setup table records. 2. Why are the setup tables not filled?If additional information is needed for the tables please let me know. Source Tables (Function Module): MCEX_BW_LO_API (Function Module) SAP Help, Wiki, Q&A and other resources for 2LIS_03_BF. KONV KBETR. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. the situation is that when I run delta it fetches 0 records. These Z-Fields are in the database table EKPO. Hi everyone, We are implementing the purchasing solution for the first time at the client. The data is not updated into the upur_c01 cube . Maintain enhancement in LEINS001. Use. Clear "RSA7" 03. This form assigns the range entered in selection screen to internal table dd_belnr. The fields are filled with an. 3. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17. Use. Sep 25, 2008 at 11:16 AM. "Image/data in this KBA is from SAP internal systems. That means setup process wasn't happen correctly. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. Technical name: 2LIS_02_ITM Use In combination with the InfoSources Purchasing Data (Document Header Level) and Purchasing Data (Document Schedule Line Level , the InfoSource Purchasing Data (Document Item Level) supplies the basic data for analyses of purchasing documents. 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. Go to OLI*BW and fill set up tables. The new DataStore object of Invoice Verification (0LIV_DS01) is supplied with data by the new DataSource 2LIS_06_INV, whereas previously the relevant invoice verification data was only supplied by the three DataSources of Purchasing 2LIS_02_HDR (purchasing data (header level)), 2LIS_02_ITM (purchasing data (item level)), and 2LIS_02_SCL. I am trying to fill up the SETUP tables. These documents are also not getting filled into Setup Table by OLI3BW. 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. Transport the Enhanced Data source to Source SAP system . 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. 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_HDR purchasing order header level data,2LIS_02_ITM purchasing order item level data,2LIS_02_SCL purchasing order schedule level data. Scenario 1: All the line items associated are marked for deletion,Then 2LIS_02_ITM--> LOEKZ being extracted as L,No issues here. 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. Direct Access Enabled. Vendor Master Data Tables : LFA1: Vendor master data general section LFB1 : Vendor Master Company Code. 2. ERROR MESSAGE DUMP for DBIF_RSQL_INVALID_CURSOR ***** Runtime Errors. You can capture that without enhancing 2LIS_02_SCL Datasource. 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. We do not need the history data for the 2 fields added. Pls reply needed urgent,i'm. Table of Origin. 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 :. This is how the SAP has defined. 2lis_11_vakon. 3. ) 2LIS_02_ITM. With this handy table you can find the status of your current job or previous initialization jobs through SM37. Field in Table of Origin. Purchasing (application 02): 2LIS_02_ITM. Use. Purchasing. Best Answer. 4. The DSO provides insight into the delivery service of vendors by exploring deviations across the. 02. WITH KEY supkz = '2'. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. So this thing need to be keep in mind while reconciling with ECC table specially for purchasing data. This item won't be delete physically. RSS Feed. Purchase Invoice Tables. Hi all, I ran OLI3BW to fill the set-up tables and tried with RSA3 (no selections) and it returned 0 records for 2LIS_02_CGR, 2lis_02_scn and 2lis_02_cgr. 0. (2LIS_11_V_ITM) - /IMO/SD_IS16 . But you need to find the filed (AEDAT) belongs to which table. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. -----Mensaje original-----De: John Parks via sap-r3-bw [mailto:sap-r3. Where in BW should be stored the data about secondary costs on purchase (acquisition) which evaluate the real price of goods?. But this d/s 2LIS_02_SRV doesnt pick/identify the deleted service entry sheets. 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. choose your characteristics and key figures. so the standard. Thanks and regards. Thanks for the quick response. As of R/3 Release 4. I was successful in extracting data for the 0PUR_C01 cube using the conventional 2LIS_02_S012 datasource. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Item Level) ( 2LIS_02_ITM ). AWS Documentation AWS Supply Chain User. and had given the termination time . The EKPO table ( Purchasing. Billing Document Header Data. from the standard tables using a Business content Data Source the Data should be Extracted to BW system. 2lis 13 Vditm Tables Most important Database Tables for 2lis 13 Vditm # TABLE Description Application Table Type; 1 : VBRP: Billing Document: Item Data SD - Billing: Transparent Table 2 : VBRK: Billing Document: Header Data SD - Billing: Transparent Table 3 : MC13VD0ITM:table names anywhere. About this page This is a preview of a SAP. Locate your Extractor (Datasource). following fields of DataSource 0CUSTOMER_TEXT: Sold-to Party. An overview of Datasources and the programs filling the relevant setup table (named MC*SETUP). 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. 5 ; SAP enhancement package 1 for SAP NetWeaver 7. ) 2LIS_02_SCL & 2. This is derived from the statisitcs updating facility maintained for updating the LIS (PURCHIS) tables in R/3. 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. no (EBELP). Purchasing 2LIS_02_ITM MC02M_0ITMSETUP. Copy & paste to SE37 eg for 2LIS_02_ITM , extractor MCEX_BW_LO_API is used.