I also have checked that: 1. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. we have done initialisation and filled setup tables. BEDAT. I saved and Activated the data source. I am able to see the newly added field in the structure, However when I test the datasourcein RSA3. Purchase Order Tables. SAP BW/4HANA Business Content delivers. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Item Level) ( 2LIS_02_ITM ). In the ECC table EKET these two fields have changed for a given purchase order but the change is not. Total number of tables/structures containing this field is 7006. Source System for R/3 Entry*. Purchase Requisition Tables. Control record it will be having information like Idoc number, message type, idoc type, sender, receiver etc. Technically, during the full load, these items should be extracted with a recordmode = R. Relevancy Factor: 30. 02 Purchasing 2LIS_02_ACC MC02M_0ACCSETUP Folder: BW Setup for. Remove the Field known only in Exit indicator. PO Deletion Indicator. When is it necessary to reload the setup table? For Example. I am also planning to enhance these extractors for few additional fields which are not extracted by these standard extractors. Go to LBWE (LO Cockpit), select DataSource 2LIS_02_SCL, click on Maintenance icon in Structure column, say Continue. 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. If no data inbound. Prerequisites. I need to enhance the Datasource 2LIS_02_ITM. MSEG MENGE. The following jobs move the data from the outbound queue to BW. 2LIS_02_ITM. Thank-You. Field PSTYP. 2. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. 4. Then use the function Activate and Schedule to start the process chain according to your scheduling options. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . Note: Field COMPL_DEL of BW is mapped via direct assignment to ECC field ELIKZ ( Delivery. Name of Target InfoObject. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 3 :. This is available in SBIW. Step 1: Get the name of tables affected by the lost delta 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. This item won't be delete physically. Loaded 0%. Table of Contents SAP BW/4HANA Content Add-On. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. In the second InfoProvider, you can. Source Tables (Function Module): MCEX_BW_LO_API (Function Module) SAP Help, Wiki, Q&A and other resources for 2LIS_03_BF. DATA: l_2lis_02_itm type mc02m_0itm, l_index type sy-tabix, lt_ekko type standard table of ekko, wa_ekko type ekko. I have already done the following steps: 1 - Transaction SBIW: Settings for Application-Specific DataSources (PI) Logistics. 2LIS_02_ITM is a purchasing extractor, mkpf et mseg are inventory table. Go to. Check the source system connectivity. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Copy & paste to SE37 eg for 2LIS_02_ITM , extractor MCEX_BW_LO_API is used. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. I checked the function module also , but still in process, any suggestions would be greatly appreciated. Thank you all four you responses. I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 . With this handy table you can find the status of your current job or previous initialization jobs through SM37. choose your characteristics and key figures. You should find table names here. Application DataSource Setup Table. DataSource 2LIS_02_HDR contains data still to be transferred. ECC -> SE11 -> ROOSOURCE -> Both "GENDELTAFD" and "GENDELTATP" are empty too. Enhancement of 2LIS_02_ITM from structure RM06E. There are multiple ways of creating a column table. How can I find which tables in R/3 are the source tables for this and that extractor (e. 3. These documents are also not getting filled into Setup Table by OLI3BW. But now I have a requirement to calculate Net GRN. 0OPS_12_ITM. Description. When does it happen that 2LIS_02_ITM does not add. eg: if i do the following action: Fill 1 -> Delete - Fill 2. This is how the SAP has defined. 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:. Transformation. MC02M_0SCLSETUP. 3. Follow. 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 :. Compare with setup table records. SAP BW/4HANA Business Content delivers this field-based DataStore Object (advanced) as. Inventory Controlling (application 03): 2LIS_03_BX. Transaction data. But you need to find the filed (AEDAT) belongs to which table. 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 . 2. Purchasing (application 02): 2LIS_02_ITM. Sap Supply Chain Management Tables in SAP. Base Tables . 2LIS_02_HDR purchasing order header level data,2LIS_02_ITM purchasing order item level data,2LIS_02_SCL purchasing order schedule level data. Billing Document Header Data. KNTTP – Account Assignment Category. Transa ctional. Goto LBWE transaction in R/3. 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. MM-PUR: Purchase Order Delivery (Items) - /IMO/PUR_D21. g quantities),. In 2LIS_11_VAHDR however, the field VDATU contains the sold-to party's Requested Delivery Date. Use. 2. When i. Hi everyone, We are implementing the purchasing solution for the first time at the client. But this d/s 2LIS_02_SRV doesnt pick/identify the deleted service entry sheets. etc. Append MCEKPO. Go to RSA6. and enhanced the datasources ITM and SCL adding one Char in. I have loaded an initial load to my ODS (0BBP_PO) and also setup a delta. SAP Knowledge Base Article - Preview. Step two: Delete delta entries in RSA7. I have already maintain datasource 2LIS_02_ITM through LBWE. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. 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:. 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. These fields are populated in the extractor and not stored in any tables. Use SAP BW/4HANA Business Content delivers this field-based DataStore Object (advanced) as a first persistence layer of data replicated into a SAP BW/4HANA data warehouse. Step 2 Create Target table where you want to persist the data. 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. When I check with RSA3 I've got a lot of records. The configuration of the table looks as follows. Scenario 1: All the line items associated are marked for deletion,Then 2LIS_02_ITM--> LOEKZ being extracted as L,No issues here. Datasource Jest Table BW Extractors in SAP (25 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. Code - 'oli2bw'. Datasource : 2LIS_11_V_ITM. Step 1: Move ECC TR to ECC- PRD system. 100 -> 100 -> 200. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. 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. I have a problem with 2LIS_13_VDITM delta. 2008. The system always converts the net price to the local currency and to the base unit of measure. I'm using OLIG and OLIGBW to fill setup tables but there are certain documents/contracts I can. Every works ok when executing setup of statistical tables. Figure 8: BW Control Table – Entry Help/Check . And it shows 0 records. Delivery date (SCLDT)= 01. 163 Views. KONV KSCHL. Field in Table of Origin. 0B) - SAP Documentation. Deleted the Setup tables. The account assignment category determines the account assignment data for an item, such as cost center and account number. The InfoSource for the SD sales document Order Item Data (as of 2. 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. 0) Basis - BW Service API: VBDATA: Update data: Basis - Client/Server Technology: BW Datasources related to RMBWV302 BW DATASOURCE Description Application ;. Bobby. I was successful in extracting data for the 0PUR_C01 cube using the conventional 2LIS_02_S012 datasource. Locate your Extractor (Datasource). MC11V_0SCL: Extraction SD Sales BW: Allocation Schedule Line for. 6C. Delta. Determine Industry Sector. RSS Feed. Purchasing. Not just "LO DataSources" because there are some that don't use this feature. 2. Yes. Name of Target InfoObject. sap and forums i found out that for. 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. MC11VA0STI: Extraction MD Order Item Status for DataSource 2LIS_11_VASTI. Step 4) Choose the datasource 2LIS_02_ITM, which is purchasing data at Item level. Import the table definition from the Metadata Repository in the Data store Explorer and use it as source in a data flow. This DSO (advanced) contains delivery related indicators and key figures for purchase order items. 11. Use. 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:. ZBW_ 2LIS_02_HDR; ZBW_ 2LIS_02_ITM . Former Member. Below is a list of frequently asked questions about Logistic DataSource setup table filling: Setup table (or RSA3 result) is empty even though you executed transaction OLI*BW to fill it. Purchasing. Both the datasource do not have Material document number (BELNR) field. ) 2LIS_02_SCL & 2. 2008 i have executed Initial Load from BI. Purchasing Data (Schedule Line Level) NA. While doing the statistical setup i am using the T. Login; Become a Premium Member; SAP TCodes. LBWE shows both extract structures (MC02M_0CGR and MC02M_0ITM) as active; Both datasources 2LIS_02_CGR and 2LIS_02_ITM are active and shown in RSA2; Delete setup tables for application 02. Here is the code: LOOP AT xmcekpo. 2lis_11_v_itm. Settings: Purchasing. I did a setup table fill-up of 2lis_03_bf and I'm seeing missing material documents with movement type 561. Comparing DataSource 2LIS_02_SCL to ME80FN. SAP. I guess you are talking about the variances that are calculated based on the NO_TIME counter that is filled in during run time. Set up table data will be deleted for whole 'Purchasing' if deleting for '02' even though you want data reload for only Purchasing Item datasource 2lis_02_itm. IF i_datasource = '2LIS_02_ITM'. These infoprovder will not have a field for ktmng rather it will have PO specific fields such as PO no, po qty, PO Agreement no. AND ebelp = mc02m_0itm-ebelp. MCEX03. Table Coep BW Extractors in SAP (20 BW Datasources) Login; Become a Premium Member; SAP TCodes;. Technical name: 2LIS_12_VCITM. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. PO Cancellation of data record Entry. 2LIS_02_SRV(obsolete) BW-BCT-PA - Personnel Management . Follow RSS Feed HI Experts, i am abaper. . Go to RSA2, enter DataSource name 2LIS_02_ITM,. Then went to BW , installed the cube , update rules and the infosources. MC02M_0ITM is a standard Logistics Information System (LIS) Structure in SAP LO application. Follow the below steps to get the lost delta, will be useful for any loads. 2lis 11 Vaitm Tables BW Extractors in SAP (28 BW Datasources) Login; Become a Premium Member; SAP TCodes;. 4. LFA1 NAME1. 12. We are about to delete setup tables for purchase (02) component and refill the setup tables. 2. We do not need the history data for the 2 fields added. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. Then I. Jun 15, 2007 at 04:37 PM. When I check in EKPO table, deletion indicator "L" is available for all deleted PO's. ebeln = xmcekpo-ebeln. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data. excuse me for this message, but I have a problem and I think you could help me. Media-Specific Adjustments to the InfoSource Order Item Data (as of 2. See SAP Service Marketplace, SAP Note 0448600 for more information on prerequisites. 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. 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. (2LIS_02_ITM). Tables for 2LIS_02_ITM. we have the V3 update job, running every 15 minutes. <LV_ADRNR> TYPE EBAN-ADRNR. FIELD-SYMBOLS : <LS_DATA> TYPE MC02M_0ITM, <LV_KUNNR> TYPE EBAN-KUNNR, . I am trying to find the procedure / sequence in to carry out in. But in case of LIS it is specific to the particular application. Dear All, I have activated BI Contents: 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_HCL. LOOP AT c_t_data INTO mc02m_0itm. Also, please make sure that your answer complies with our Rules of Engagement. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. Technical Name of Target InfoObject. (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. 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. MC11V_0ITM: Extraction SD Sales BW: Document Item Allocation for DataSource 2LIS_11_V_ITM. We deleted init and reinitialised with no success. setup table are built sucessful and he collects data (setuolog) But the extractor checker doesn't work he collects 0 data. Maintain extract structure and datasource. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :. The extractor 2lis_02_itm will extract both Purchase Orders and Agreements. eg: if i do the following action: Fill 1 -> Delete - Fill 2. When using a Join of 2LIS_03_BF ( for Good Movement (E) from MSEG data ) and 2LIS_06_INV ( for Invoice (Q) from EKBE data ) ; In general the DBMTR is same in MSEG and EKBE, but there are few scenarios when they are. Unlock users out of R/3. 05. RSA3 for 2LIS_02_ITM,2LIS_02_SCL , 2LIS_03_BX,. Delete the setup data (LBWG) 2. with SE11 transaction you can see these tables. 5 ; SAP enhancement package 1 for SAP NetWeaver 7. 01. 2001. 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. 2LIS_02_ITM, 2LIS_02_HDR, 2LIS_* , KBA , BC-BW , BW Service API , BW-BCT-MM. I executed infopackage full load for such sales documents, but 0records are received. Over the last few days , I had some posts on 2LIS_02_ITM and Process Key activation. But these datasource read data from EKKO, EKPO & EKBE table and material document number field is availble in EKBE. and choose the industry sector "Standard (Core)". Transaction LBWQ in ECC: MCEX02. 2LIS_02_SCL. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW > Settings for. There will be no impact on existing processes. if you put EKET then it brings up. 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. BW Reorganization Store for MC11V_0ITM. 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. Step. 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. Purchasing Document Category. ALIEF - Number of Deliveries. Sep 25, 2008 at 11:16 AM. These fields are populated in the extractor and not stored in any tables. As of R/3 Release 4. Since I know I am working with Purchasing data those are my obvious choices. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. CLEAR LT_DATA. 48. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. I activated 2LIS_02_itm and SCL datasources in LO cockpit but, it is not prompting for a transport request. Environment. 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. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . also check in BD87. Source table: EKET (Scheduling Agreement Delivery Schedule Lines) Extract structure: MC02M_0SCL. of entries in Set up tables. Environment. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL. 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. Presss F5 and get inside the form “select_option_fill”. Targets are going to be different for delta and full. The process chain supports SAP R/3 standard systems as of Release 4. 2LIS_13_VDITM: Billing Document Item Data. MC11VA0STH: Extraction MD Order Header Status for DataSource 2LIS_11_VASTH. So , how to know. Apparently these two fields are NOT updated in BW from a delta load. If a data inbound layer persistence and/or a corporate memory persistence is used, the transformation from this DataStore. Suppose the sale order is 20 qty, there will be couple of records with 20 qty, doubling up the qty. 3. 2. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Customized BADI Name – ZPP_DS_2LIS_02_ITM. PO. PLAF is a standard Master Data Transparent Table in SAP PP application, which stores Planned order data. MC02M_0CGRSETUP. Read more. I have an issue with Purchasing data source: 2LIS_02_ITM. g. You can see the table in the above screen shot. where ebeln = c_t_data-ebeln. Rohan, Looking at EKBE is correct. 2lis_02_itm uses EKKO and EKPO tables etc. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). Run the collective run, so all the data is sent into the delta queues. "Document data restriction" when filling setup table. When we are filling Setup table if anyone access the same setup table from outside. (Account Level) (2LIS_02_ACC). MC02M_0CGR Storage. We need the data for the two new fields going forward. Filled with the 2-digit logical backend system (based on LOGSY) Logical System Backend. Run DTP with extraction mode “Delta” ( 1 st time it extracts data from setup table). Delivery Item . 0. Run the collective run so all the data are sent into the delta queue. Available as of OLTP Release. This is derived from the statisitcs updating facility maintained for updating the LIS (PURCHIS) tables in R/3. Sap Tables in SAP. 0 ; SAP NetWeaver 7. 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. READ TABLE i_t_ekpo WITH KEY ebeln = xmcekpo-ebeln ebelp = xmcekpo-ebelp. MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. This is available in SBIW. I have a problem with the delta. 2LIS_02_ITM Purchasing Data (Item Level) MM - Materials Management: 14 : 2LIS_05_QE2 Inspection Result: Quantitative Data QM - Quality Management: 15 :Transformation. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Source System for R/3 Entity*. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. Now when I click on Initialization >Fill Setup Tables >Perform Setup Purchasing, i get the following message at the status bar: ". 2LIS_03_BX: Stock Initialization for Inventory Management MM - Materials Management: 7 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level). But when the user changes only the account assignment of an outline agreement , without changing any other fields (e. 2lis 02 Itm Database Tables in SAP (23 Tables) MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/PUR_IS11. When I try to do this in the conventional way (in transaction RSA6, button 'E. The activation of the business function by itself will not enhance the database tables. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. With no data in setup tables, rsa7, sm13. 1. Important Key Figures: ROCANCEL. 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),. . "2LIS_02_SCN MM MC02M_0SCN Achieved Performance: Confirmation of. Functional Area:. SAP Table Field : ERNAM - Created by Top 200 SAP Tables containing the field/column ERNAM. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 0FI_AP_4. 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). 2LIS_03_UM. 02. 2lis 03 Bf Table BW Extractors in SAP (29 BW Datasources) Login; Become a Premium Member; Transaction Codes; Tables. 02. 2LIS_11_VAKON: Order Condition Data. Go inside the class ZCL_DS_2LIS_02_ITM and implement the below code – ATA : LT_DATA TYPE STANDARD TABLE OF MC02M_0ITM. 2LIS_02_ITM (Purchasing Document Item Level Data) 2LIS_02_SCL (Purchasing Document Schedule Line Level Data) Step 1 : Log on to Sap R/3 Ecc System. 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. Thanks for the quick response. 9) After zero records repeat the step 6 to 7 for double confirmation to avoid any possible data entries.