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. 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). This is what the procedure i used (please tell me if i did something wrong): 1. 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 :. For information, I had the same problem with 2LIS_02_ITM. Then went to BW , installed the cube , update rules and the infosources. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. We need to extract fields RM06E-LTEX1 (long text) and RM06E-KZLTX (More Text Exists which is a flag) from R/3 into BW however RM06E is a structure in R/3. 163 Views. so the standard. Table EKKN filed PS_PSP_PNR gives you the WBS element associated with the PO. 123456 20 L. Transaction LBWQ in ECC: MCEX02. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :Note. When running the setup for application 02 (TR OLI3BW), the table was not filled: running RSA3 with no restrictions did not retrieve any records. I activated 2LIS_02_itm and SCL datasources in LO cockpit but, it is not prompting for a transport request. Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. . For all purchasing data you should use Extractors 2LIS_02_ITM, 2LIS_02_HDR and 2LIS_02_SCL . Maintain Extract Structure MC02M_0ITM. We have an issue with the delta's for the 2LIS_11_V_ITM, which is extracting duplicate values. I have already maintain datasource 2LIS_02_ITM through LBWE. (2LIS_02_ITM). Available as of Plug-In Release. Figure 9: BW Control Table – Foreign. (2LIS_11_V_ITM) - /IMO/CMSD16 . Some of the PO items are marked for deletion in the source system (LOEKZ = L). When is it necessary to reload the setup table? For Example. MC02M_0ITMSETUP if it have any records" Customized BADI Name – ZPP_DS_2LIS_02_ITM. Step two: Delete delta entries in RSA7. 2016 at 02:59 PM GTM 2LIS_46_ITM extraction. Step 1: Move ECC TR to ECC- PRD system. Table Coep BW Extractors in SAP (20 BW Datasources) Login; Become a Premium Member; SAP TCodes;. Purchasing document 4500000001, Item 0010, has the following schedule lines: Schedule line number (SCLNR) = 1. Vendor Master Data Tables : LFA1: Vendor master data general section LFB1 : Vendor Master Company Code. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. and then go to BW side and replicate the Datasource. Delta Process: Delta Queue based. Add a Comment. 0. But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. Transaction data. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. 339 Views. 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 ). 123456 30 - 123456 40 - 123456 50 - EKPO table r/3. Technically, during the full load, these items should be extracted with a recordmode = R. I guess you are talking about the variances that are calculated based on the NO_TIME counter that is filled in during run time. LOOP AT c_t_data into l_2lis_02_itm. FAQ: Setup table filling with 2LIS* extractors. With no data in setup tables, rsa7, sm13. 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. We are analbe to get the records for "Pruch Docu Catgory" = L(Scheduling Agreement). You think 2LIS_06_INV extracts too many records either in the INIT, Delta or Full loads. Due to a company migration, We are using a program to delete line items of a PO. PO Deletion Indicator. then data inconsistency will be happen. 4. Billing Document Item Data SD -Sales and Distribution. Then I ran the init load and for 2LIS_02_ITM I got 432 records as transferred and 0 as added and for 2LIS_02_SCL I got 326 as transferred and 0 as added . KNTTP – Account Assignment Category. Replicate the datasource 2LIS_02_ITM and reinit and load data. SAP BW/4HANA. Pls clarify if both delta and full load can happen in parallel for the same data source?Vbak Table Data Source BW Datasources. I know the history has it but, I want to know what is the source for BUDAT in 2LIS_02_ITM. Quantity ordered (SCLQTY) = 20. 02:PURCHASING. etc. Z2LIS_02_ ITM_SRV. If I missed to search something please provide that. In LBWE, it says EKKO-SYDAT but it is from EKPO (*) 2LIS_02_ACC. Transaction Data. I've done all the "tasks" for setup tables, but i don't have 0PROCESSKEY. 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. I filled the setup table in the development system and did an Initialize with data transfer. 2lis 02 Itm Tables Most important Database Tables for 1. When I try to load setup data I got this message in setup table. Hi, I am using 2lis_02_itm and 2lis_02_hdr. 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. Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. To reach the customising node use transaction OMGO. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. This DataStore Object (DSO) contains the invoice verification data on a granular level. Clear "RSA7" 03. SAP. after creating two tbls r created which will handle ur delta. 12. If you need a field that can take over the Update Date for Statistics Update function, proceed as described in SAP Note. But for 2lis_02_sgr we are able to get records only for "Pruch Docu Catgory" = F(Purchase Order). 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. eg: if i do the following action: Fill 1 -> Delete - Fill 2. Figure 7: BW Control Table – Fields . 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 7 :. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 :. Sep 16, 2009 at 06:26 PM. where ebeln = c_t_data-ebeln. ODP Semantics. Francisco Milán Campos. But in case of LIS it is specific to the particular application. KONV KSCHL. Purchasing (application 02): 2LIS_02_ITM. Technical name: 2LIS_02_HDR . 1. Step 4: Delete set up table. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. That means that you can use this DataSource both for data replication in a BW system (SAP Business. Runn full load. 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. 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. OLI1BW INVCO Stat. Hi We are using the following logic to enhance 2lis_02_itm with different fields from diff tables. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. Delete the setup data (LBWG) 2. SD Sales Orders. 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. 0 (SAP_APPL 606), business function Sales and Distribution, Analytics 01 (LOG_SD_ANALYTICS_01), this DataSource also contains an ODP extractor for Operational Data Provisioning (ODP). Use. With this process chain, the initial data set is updated (initialization of the delta process) in the data targets affected (InfoArea. Using this approach, the advantages are: The code is limited to few numbers of. WHEN '2LIS_02_ITM'. 3. Product. (Account Level) (2LIS_02_ACC). A goods movement is posted with the following information: Posting date (BUDAT) = 05. ERROR MESSAGE DUMP for DBIF_RSQL_INVALID_CURSOR ***** Runtime Errors. to fill the setup table. Checked data in "RSA3" ex: 200 records. FI and COPA is easy to get , the hardest to get at is the LO extractors. also check in BD87. 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. following fields of. Maintain extract structure and datasource. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. SAP BW/4HANA Business Content delivers. With this handy table you can find the status of your current job or previous initialization jobs through SM37. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. MC02M_0ITM. Due to some loads failed, we are doing re-init the loads. Former Member. 3. Control record it will be having information like Idoc number, message type, idoc type, sender, receiver etc. * For more information about source system IDs, see SAP HANA-Optimized BI Content. if anyone knows tcodes for runinng the set uptable to each data source separatley. (2LIS_11_V_ITM) - /IMO/CMSD16 . SAP Table Field : BUDAT - Posting Date Top 200 SAP Tables containing the field/column BUDAT. 2LIS_02_ITM and 2LIS_02_SCL datasources not only extract PO line items. But these datasource read data from EKKO, EKPO & EKBE table and material document number field is availble in EKBE. 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. and choose the industry sector "Standard (Core)". Name of Target InfoObject. It s failing for only 2LIS_02_ITM only. 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. LO Cockpit - Basic Question. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 . 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. It is located under materials management --> Purchasing. 2. This document has 2 parts. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. Recently, I need Batch data for reporting related to Purchasing , fortunately there is field CHARG (Batch) in 2LIS_02_ITM. Transaction code to delete setup table is LBWG. Date of Purchasing Document. Thank-You. Suppose the sale order is 20 qty, there will be couple of records with 20 qty, doubling up the qty. first run Init without datatransfer. I'm trying to use datasource 2LIS_02_CGR in addition to 2LIS_02_ITM already in use. Step. In EKET Table the data is like. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 - SAP Help Portal Relevancy Factor: 10. Step 2 Create Target table where you want to persist the data. Select the Data Source ( 2LIS_02_ITM ) 3. BW Reorganization Store for MC11V_0ITM. Purchase Info Record Tables. SAP R/3 Enterprise all versions Keywords. some sales document nos missed in bw. DataSource 2LIS_02_HDR contains data still to be transferred. Dear All, I have activated BI Contents: 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_HCL. Step 3: Move BW TRs to BW PRD system. 11. An overview of Datasources and the programs filling the relevant setup table (named MC*SETUP). Settings: Purchasing. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. (2LIS_11_VAHDR). TXTMD. BW: Transaction Key in 2LIS_02_ITM. 0. 1. Maintain enhancement in LEINS001. Implemented class Name – ZCL_DS_2LIS_02_ITM. This counter determines the number of deliveries based on the GR document items. MC02M_0ACCSETUP. 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. Item 20 is deleted. Clear setup tables in LBWG. Hi all! I have to initialize my BW data for the datasources: 2LIS_02_HDR 2LIS_02_ITM 2LIS_02_SCL 2LIS_02_S012 All my key figures are in "summation" mode, that means, no item should be loaded. ) 2LIS_02_SCL & 2. 10 characters required. 2LIS_03_BF. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. and had given the termination time . When does it happen that 2LIS_02_ITM does not add. Tables related to 2LIS_13_VDHDR TABLE Description Application ; VBRK: Billing Document: Header Data: SD - Billing: VBRP: Billing Document: Item Data: SD - Billing: VBAP:For the same Datasource 2LIS_02_HDR, when in R/3 production I try to extract data using RSA3, it gives me '0' records. Available as of OLTP Release. 2LIS_02_ITM Purchasing Data (Item Level) MM - Materials Management: 14 : 2LIS_05_QE2 Inspection Result: Quantitative Data QM - Quality Management: 15 :Transformation. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. We are trying to implement Purchasing Information, Purchasing Data Item Level (2LIS_02_ITM), Purchasing Data Header Level (2LIS_02_HDR), Purchasing Data Schedule Line (2LIS_02_SCL), we have activated the extract structure, filled the set-up table and tried to look into the setup table but it does not show any records (even RSA3 do not show),. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. We are using this 2lis_02-srv d/s for loading services orders (service entry sheet), in this d/s there will be multiple service entry sheets for a purchase order, sometimes in R/3 some service entry sheets may be deleted within the PO. Just as try we deleted Setup table and fill it with PO documents having this issue again but no use. 12. The extractor 2lis_02_itm will extract both Purchase Orders and Agreements. 2001. "Image/data in this KBA is from SAP internal systems. 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). Run info pack with init without data transfer. There are multiple ways of creating a column table. Issues in Filling Setup table for 2LIS_02_HDR | SAP Community Relevancy Factor: 1. 0. my question is what transaction code can I see this field in BW Table. 2lis 11 Vaitm Ecc Source Tables BW Datasources Most important BW Extractors for 2lis 11 Vaitm Ecc Source Tables # BW DATASOURCE Description Application; 1 :. 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. There is a table that maps movement type to process key. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Table of Contents SAP BW/4HANA Content Add-On. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . RSS Feed. -----Mensaje original-----De: John Parks via sap-r3-bw [mailto:sap-r3. The activation of the business function by itself will not enhance the database tables. Please note , Everything is fine with setup table data , update rule ( Overwrite mode) and other BW part. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data. Hi, Where can i find the t-codes for filling the setup table for all the logistics datasources. 2lis 11 Vaitm Tables BW Extractors in SAP (28 BW Datasources) Login; Become a Premium Member; SAP TCodes;. Note: Field COMPL_DEL of BW is mapped via direct assignment to ECC field ELIKZ ( Delivery. About this page This is a preview of a SAP. These indicators and key figures are based on the associated confirmation and goods receipt documents. The Field (CHARG) not hidden. 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. 2166572-What tables are read for datasource 2LIS_06_INV and basic logic. Login; Become a Premium Member; SAP TCodes; Tables. 2lis_02_itm uses EKKO and EKPO tables etc. SETUP tables not filling for 2LIS_02_ITM. I use the standard extractor 2LIS_02_ITM (order positions) with the update mode "Direct Delta" and apanded Z-fields. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). Datasource : 2LIS_11_V_ITM. The modeling property Inbound table as extended table has been turned on. Oct 18, 2007 at 09:39 AM. 2LIS_11_VAKON: Order Condition Data. MC02M_0CGR Storage. 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 have also deleted the setup tables and filled them again. Media-Specific Adjustments to the InfoSource Order Item Data (as of 2. 05. Go to OLI*BW and fill set up tables. i need to get the data from different tables. 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. I now am trying to get publishing back on track. Hi, Logistics application ""02 : Purchasing"" (HDR, ITM and SCL) is activated. Use. Similarly, we can do the same steps (Step1-5). You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 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. VRTKZ – Distribution Indicator for Multiple Account Assignment Table of Origin. READ TABLE lt_ekko into wa_ekkoTable YBWMAPPING is used by the class YCL_BW_MAPPING. Then use the function Activate and Schedule to start the process chain according to your scheduling options. Environment. Follow RSS Feed HI Experts, i am abaper. Purchasing. Why are the setup tables not filled?If additional information is needed for the tables please let me know. MM - Materials Management: 10 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 11 : 2LIS_13_VDITM: Billing. Upon trying, i have encountered many problems: 1. transfered datasource 2LIS_02_ITM using tcode RSA5. 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. PO Item Deletion Indicator (LOEKZ) 123456 10 L. Technical Name of Target InfoObject. I have pasted the eror message below for reference. Purchase Requisition Tables. We have an infocube up and running in production for couple of years, now have to add 2 fields in the extractor which are part of standard extractor 2lis_02_itm. 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. how does 2lis_02_itm gets data from ekpo pstyp, what tcode can I see the entry? is it also in VA03? the Item Category from that transaction is from VBAP. (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. I have added field BADAT-PR creation date in the extractor structure of 2lis_02_itm. 2. We need the data for the two new fields going forward. Purchasing. Hi Kumar: Maybe you're not able to fill the Setup Tables because the Extract Structures for Purchasing are inactive, you can activate them in Transaction LBWE. 3. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . News & Insights. structure in LBWE for 2LIS_02_SCL. 0B, InfoSource 2LIS_04_P_MATNR replaces InfoSource 2LIS_04_S280. PO. In 2LIS_11_VAHDR however, the field VDATU contains the sold-to party's Requested Delivery Date. 2. we have deleted "02" in T-Code LBWG and filled setup table using Tcode - OLI3BW. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :. then go to T- Code OLI9BW. we have done initialisation and filled setup tables. 2LIS_02_* Problem - Setup Tables empty | SCN Relevancy Factor: 1. DATA SOURCE NAMING CONVENTIONS : 11 ----- 2LIS_11_VAHDR / 2LIS_11_VAITM / 2LIS_11_VASCL 2LIS ----- Standard refer for every LO Data Source. We've created a new field called, e. select * into table lt_ekko from ekko for all entries in c_t_data. 2LIS_02_ITM is a purchasing extractor, mkpf et mseg are inventory table. Pls reply needed urgent,i'm. Test using RODPS_REPL_TEST , SUM = 0 in the result. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. 3. For purchasing datasources 2lis_02_itm and 2lis_02_sgr . Code - 'oli2bw'. On 09. ALIEF - Number of Deliveries. We have data sources 2LIS_02_ITM, 2LIS_02_CGR, 2LIS_02_SCR and 2LIS_02_SGR activated and up and running delta properly. 5. Go to t-code ODQMON (in ECC). Tables for 2LIS_02_ITM. 3. Environment. 9) After zero records repeat the step 6 to 7 for double confirmation to avoid any possible data entries. I executed infopackage full load for such sales documents, but 0records are received. 1 ; SAP NetWeaver 7. When i. 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. Delivery time (SCLTM) = 12:00:00. MC02M_0SGR: Produced Activity: Delivery of Schedule Lines Maintenance for Data Source 2LIS_02_SGR 8 31 139,142. Read more. 02. It is from BEDAT from EKKO and EKBE. and added the fields in ODS( Key Purchasing Document and Document Item) I did the testing , and found that the fields are not correctly populated in BW. . In LBWE, its showing that LOEKZ is taken from EKPO. The counted number depends on how often a material appears in a GR document. 2LIS_02_HDR. When I enhance comm. Purchasing 2LIS_02_HDR MC02M_0HDRSETUP Storage BW Setup for. ZBW_ 2LIS_02_HDR; ZBW_ 2LIS_02_ITM . 02 Purchasing 2LIS_02_ACC MC02M_0ACCSETUP Folder: BW Setup for. We do not have down time. Dear All, It would be really helpful to know the used tables for datasource 2LIS_02_ITM. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . Total number of tables/structures containing this field is 4948. Check the source system connectivity. SAP delivers the following example BEx queries on top of MultiProviders Sales Overview. Hi everyone, We are implementing the purchasing solution for the first time at the client. Recommence extraction into BW from the modified R/3. - Process Key 002:GR. Thank you all four you responses. Purchasing Group Tables. are extracting data, the 2 mentioned in the subject line do not extract any data. ) 2LIS_02_ITM. We currently have delta load happening from the same data source. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. (We are not going to delete any data from application tables. Remove the Field known only in Exit indicator. The fields concerned are located in one of the Purchase Order screens (ME21). I have an issue with Purchasing data source: 2LIS_02_ITM. Use corresponding exit FM as template and copy the import, Export, Table, Exception. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. 100 -> 100 -> 200. 2LIS_02_ITM, 2LIS_02_HDR, 2LIS_* , KBA , BC-BW , BW Service API , BW-BCT-MM. the situation is that when I run delta it fetches 0 records. EKKO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Header data. 01. 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. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. 2lis 03 Bf Table BW Extractors in SAP (29 BW Datasources) Login; Become a Premium Member; Transaction Codes; Tables. or alternatively you can build your own custom extractor using purchasing tables EKKO,. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. We are about to delete setup tables for purchase (02) component and refill the setup tables. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. I chkd EKKO and EKPO and EKPA , from where it is extracted, but dont find BUDAT in these tables. Delete content of ODS/CUBE. g. Data Modeling Relevancy Factor: 2. MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. I'm having a kind of a business issue when trying to extract data from 2lis_46_itm to BW. Source System for R/3 Entity*. Info Record Tables. Now when I click on Initialization >Fill Setup Tables >Perform Setup Purchasing, i get the following message at the status bar: ". 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. Delete the setup Table using LBWG . However I observed a different behaviour in case of POs with an Invoicing Plan ( mostly framework POs) E. Yes. 3. To stop the access from outside we use t-code SM01 to. . Datasource Jest Table BW Extractors in SAP (25 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. This DSO contains delivery related indicators and key figures for purchase order items.