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. ) 2LIS_02_SCL & 2. This form assigns the range entered in selection screen to internal table dd_belnr. <LV_ADRNR> TYPE EBAN-ADRNR. If no data inbound. I have been using DataSource: 2LIS_02_ITM for couple of months and I have loaded data into (Full and Deltas). My plan is to perform below steps. - Process Key 001:PO. 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. MC11V_0ITMSETUP. Date of Purchasing Document. 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. 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 :. SAP Tables SAP Table Fields (New) SAP Glossary Search. 2LIS_02_ITM Purchasing Data (Item Level) MM - Materials Management: 14 : 2LIS_05_QE2 Inspection Result: Quantitative Data QM - Quality Management: 15 :Transformation. It contains the complete history of the loaded data. Thanks for the quick response. Table of Origin. create your update rules using MC24. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. Purchase Order Tables. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . But I can say as numeric pointer ,backend data source is using primary key (VBELN) or combination of primary key (VBELN-POSNR) from VBAP table. Transformation Rule. 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. 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:. The following foreign key relationships have to be maintained. Use. In the second InfoProvider, you can. 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). 2. 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. 2008. RemoteCube-Compatible. (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. For all purchasing data you should use Extractors 2LIS_02_ITM, 2LIS_02_HDR and 2LIS_02_SCL . You should find table names here. or alternatively you can build your own custom extractor using purchasing tables EKKO,. 0. 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. LIS uses v1 and v2 update modes only. Prerequisites. 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. Transaction LBWQ in ECC: MCEX02. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). In combination with the InfoSources Purchasing Data (Document Item Level). 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. You have to enhance the data source if the field is not available to you. 2001. Thanks,-af. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. PO Deletion Indicator. Source System for R/3 Entity*. 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 :. Go to. 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. from the standard tables using a Business content Data Source the Data should be Extracted to BW system. Login; Become a Premium Member; SAP TCodes. There will be no impact on existing processes. In the datasource for Purchasing 2LIS_02_ITM and it is also there in the Schedule line item 2LIS_02_SCL, there is a field called BW: Transaction Key mapped to BWVORG in R/3. Empty BW delta queues on R/3 by extraction to BW. In this extractor we have enhanced "PS_PSP_PNR" (WBS Element) field whose values are being stored in "Account Assignment in Purchasing Document" table. create ur infostructure using MC21 transaction code. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. Media-Specific Adjustments to the InfoSource Order Item Data (as of 2. It's the pre-processing of Archive ( Archive Object is MM_EKKO ). I need to enhance the Datasource 2LIS_02_ITM. 2LIS_02_SRV (obsolete) The 2LIS_02_SRV data structure is new for the EHP3 and there are some steps to activating it. 0. first run Init without datatransfer. Name of Target InfoObject. Purchasing 2LIS_02_CGR MC02M_0CGRSETUP BW-Rebuild for. Sap Supply Chain Management Tables in SAP. You can find more information in Special Features When Using PP-PI . Follow. Please follow bellow steps: 1. KNTTP – Account Assignment Category. The issue is when I ONLY change the. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :Note. When I try to do this in the conventional way (in transaction RSA6, button 'E. ”VT_2LIS_02_ITM”). MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. T-Code Purpose. If you choose the Delivery Schedule Lines view in the transaction ME80FN, you can compare the data in the DataSource fields with the original document data in SAP R/3, such as: · Purchasing Document Number (EBELN) · Item Number of Purchasing Document (EBELP) · Delivery Date (EINDT)1. Data load for :2LIS_02_HDR. Login; Become a Premium Member; SAP TCodes; Tables. 2LIS_02_SCL. Some of the PO items are marked for deletion in the source system (LOEKZ = L). Delete content of ODS/CUBE. 2lis 11 Vaitm Tables BW Extractors in SAP (28 BW Datasources) Login; Become a Premium Member; SAP TCodes;. 4. FAQ: Setup table filling with 2LIS* extractors. Clear setup tables in LBWG. Important Key Figures: ROCANCEL. News & Insights. 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. Filled with the 2-digit system ID of the connected source system. RSA3 for 2LIS_02_ITM,2LIS_02_SCL , 2LIS_03_BX,. Purchase Requisition Tables. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 :. 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. Sap Tcode Ksbt Tables in SAP. Billing Document Header Data. A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!We have schedule the job of filling the setup tables today i. e 4. Checked data in "RSA3" ex: 200 records. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 - SAP Help Portal Relevancy Factor: 10. Setup: Material Movemts. LOOP AT c_t_data into l_2lis_02_itm. At the same time, they are also updated in the ODQDATA table. also full update of 2LIS_13_VDITM featches only records that have been uploaded with initial load. 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. Code - 'oli2bw'. 123456 30 - 123456 40 - 123456 50 - 2lis_02_itm Setup Table. The system therefore only executes a delta update for this DataSource if. 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. 2001. Issues in Filling Setup table for 2LIS_02_HDR | SAP Community Relevancy Factor: 1. 12. MC11V_0ITM: Extraction SD Sales BW: Document Item Allocation for DataSource 2LIS_11_V_ITM. MC02M_OHDR. 2LIS_02_ITM. Note: As an alternative you can also use DHCDCVCDSEXTRE in SE16 which contains more or less the same information. I guess you are talking about the variances that are calculated based on the NO_TIME counter that is filled in during run time. so I add field CHARG into that datasource. The account. NO/PO itm no/ schline. "Document data restriction" when filling setup table. Application: SD - Sales and Distribution. Run the Delta Info package in BW to update all the data i. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). (2LIS_11_V_ITM) - /IMO/CMSD16 . 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule. 192 Views. I did a setup table fill-up of 2lis_03_bf and I'm seeing missing material documents with movement type 561. I was successful in extracting data for the 0PUR_C01 cube using the conventional 2LIS_02_S012 datasource. SAP BW/4HANA. with SE11 transaction you can see these tables. When I try to do this in the conventional way (in transaction RSA6, button 'E. ex: 2LIS_13_VDITM. we have done initialisation and filled setup tables. This document has 2 parts. Dear All, It would be really helpful to know the used tables for datasource 2LIS_02_ITM. Vote up 0 Vote down. 02. I have gone through many threads with similar subject but dint got proper solution for this. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. In this case use FM EXIT_SAPLRSAP_001 as template. For e. These many numbers (Po and Line item) will not be extracted by the std extractor i,e, 2LIS_02_ITM, since those POs are not real PO. Run DTP with extraction mode “Delta” ( 1 st time it extracts data from setup table). I have enhanced the datasource(2lis_02_itm) for the Tolerance fields. MC02M_0ITM. Billing Document Item Data SD -Sales and Distribution. When I check with RSA3 I've got a lot of records. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. Table of Contents SAP BW/4HANA Content Add-On. Date of Purchasing Document. LBWE transaction - inactivate update, deleted setup tables in application component 02(MM) and also deleted any delta queue in /nrso2. KOSTK. 4. 2. I also know that my InfoSources for this data are 2LIS_02_HDR, 2LIS_02_ITM, and 2LIS_02_SCL. I can see the data for other datasrcs related to purchasing like 2lis_02_itm data in rsa3 . what is the reason , pls. Environment. Hi everyone, We are implementing the purchasing solution for the first time at the client. Then relicated the data sources . VRTKZ – Distribution Indicator for Multiple Account Assignment Table of Origin. Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. I'm having a kind of a business issue when trying to extract data from 2lis_46_itm to BW. SAP BW/4HANA. 2LIS_02_ITM - Adding fields to communication structure - User exit | SAP Community Relevancy Factor: 1. 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:. Then I. 3. WHEN '2LIS_02_ITM'. Then went to BW , installed the cube , update rules and the infosources. Also you can see same in Transaction code ME80FN. 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. There is a requirement to load full load to BW system from 2LIS_02_ITM data source. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_12_VCITM: Delivery. The system therefore only executes a delta update for this DataSource if. In EKET Table the primary key is based on 3 fields. 5. This is to keep data that is depending on each other consistent. 0OPS_12_ITM. following fields of DataSource 0CUSTOMER_TEXT: Sold-to Party. 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. But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. Symptom. iam loding data for purchasing data using 4 data sorses. EKKO. Determine Industry Sector. Why are the setup tables not filled?If additional information is needed for the tables please let me know. are extracting data, the 2 mentioned in the subject line do not extract any data. DataStore object (advanced): SD: Delivery Item Data (2LIS_12_VCITM) - /IMO/CMSD21. ZBW_ 2LIS_02_HDR; ZBW_ 2LIS_02_ITM . You can capture that without enhancing 2LIS_02_SCL Datasource. MM-PUR: Purchase Order Delivery (Items) - /IMO/PUR_D21. If I missed to search something please provide that. For all LO datasources logic is written in function module MCEX_BW_LO_API. ) We had a similar scenario where we wanted to refresh entire data for 2LIS_13_VDKON. With no data in setup tables, rsa7, sm13. But these datasource read data from EKKO, EKPO & EKBE table and material document number field is availble in EKBE. I'm trying to use datasource 2LIS_02_CGR in addition to 2LIS_02_ITM already in use. Bobby. Situation 2. When a DTP/TRFN has to be created for a Datasource as source, then the Datasource cannot be added from the value help or manually, if the name of the datasource begins with a number between 1 to 9. Purchasing. Login; Become a Premium Member; SAP TCodes; SAP Tables; SAP Table Fields; SAP Glossary Search; SAP FMs;. Source System for R/3 Entry*. Delta Process: Delta Queue based. Use. For information, I had the same problem with 2LIS_02_ITM. The EKPO table ( Purchasing. 2lis_02_itm uses EKKO and EKPO tables etc. It is located under materials management --> Purchasing. after this load you can run deltas. 2016 at 02:59 PM GTM 2LIS_46_ITM extraction. RSS Feed. Data Modeling Relevancy Factor: 2. Purchasing Data (Item Level) NA. I tried deleting the setup table (LBWG) and tried again initialization (OLI3BW) but I cant. Hi, Logistics application ""02 : Purchasing"" (HDR, ITM and SCL) is activated. SD - Sales and Distribution: 3 : 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 : 2LIS_12_VCITM: Delivery Item Data SD - Sales and Distribution: 5 : 2LIS_01_S001: Customer SD - Sales and. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . Attributes; Attributes. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. 2LIS_11_V_ITM. I am trying to find the procedure / sequence in to carry out in. Follow RSS Feed HI Experts, i am abaper. 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. We've created a new field called, e. Thank-You. Go to RSA6. 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. 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. 2lis 02 Itm Tables Most important Database Tables for 1. Implemented class Name – ZCL_DS_2LIS_02_ITM. Use. 5. If they don't solve delta queue I'll report to SAP. g. Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. Go inside the class ZCL_DS_2LIS_02_ITM and implement the below code – ATA : LT_DATA TYPE STANDARD TABLE OF MC02M_0ITM. Transa ctional. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. BSART. Clear "RSA7" 03. Please provide a distinct answer and use the comment option for clarifying purposes. Settings: Purchasing. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. Delivery time (SCLTM) = 12:00:00. Ship-to Party. I have added field LOEKZ (Deletion indicator) to datasource 2LIS_02_ITM from t-code LBWE and activated. Symptom. save the package and press create. 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. EKKO. Purchase Info Record Tables. we have datas (ekko,ekpo) 2. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data. TXTMD. 02:PURCHASING. 100 -> 100 -> 200. (2LIS_11_V_ITM) - /IMO/CMSD16 . Purchase Requisition Tables. 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. then data inconsistency will be happen. 1. Hi, Where can i find the t-codes for filling the setup table for all the logistics datasources. Data Source:2LIS_02_ITM, Note: Field LOEKZ of table EKPO is the deletion indicator for an item in P20. Thanks and regards. 2166572-What tables are read for datasource 2LIS_06_INV and basic logic. Application Component. I checked in RSA3 and the set up tables all the above datasources have records. SAP Tables SAP Table Fields (New) SAP Glossary Search;. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 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". Z2LIS_02_ ITM_SRV. It is mapped to BW fields 0DEL_FLAG and 0ITEM_DEL via direct assignment. (2LIS_13_VDITM). In R/3 my setup tables are filled : MC02M_0ITMSETUP . Vote up 2 Vote down. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. some sales document nos missed in bw. Home. , Z1, and we try to add this new field into the LO Cookpit datasource 2LIS_02_ITM. The DSO is directly supplied from the Info/DataSource 2LIS_06_INV. Functional Area:. - Process Key 003:IR. These documents are also not getting filled into Setup Table by OLI3BW. 100 -> 100 -> 200. 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. 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. So , how to know. 0. 0B) - SAP Documentation. 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 . In EKET Table the data is like. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17. You get this message , when you execute MCB_ " View/table V_TMCLBW can only be displayed and maintained with restrictions" 2. EKKO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Header data. 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_CGR 2LIS_02_SGR 2LIS_02_SCN. 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 how the SAP has defined. Like I activated the datasources in LBWE than I intialised all datasources. MC02M_0CGRSETUP. Job for collective update stopped (LBWE) 4. In EHP 3 the tables are already delivered to the customer enhanced, the activation will only. Transaction data. BW: Transaction Key in 2LIS_02_ITM. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 6 : 2LIS_11_VAITM: Sales Document Item Data SD - Sales and Distribution: 7 :2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_HDR:. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. Scenario 2: If 5/10 line items are marked for deletion, Even though I can see their LOEKZ status in EKPO as L,2LIS_02_ITM is being. DATA: l_2lis_02_itm type mc02m_0itm, l_index type sy-tabix, lt_ekko type standard table of ekko, wa_ekko type ekko. Home. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. These Z-Fields are in the database table EKPO. However I observed a different behaviour in case of POs with an Invoicing Plan ( mostly framework POs) E. that all records from 2LIS_02_ITM are deleted in the START routine. Press F8 and program will stop at this step. 2. The modeling property Inbound table as extended table has been turned on. Transaction Data. 1. EKBE is a standard Purchasing Transparent Table in SAP MM application, which stores History per Purchasing Document data. SAP Knowledge Base Article - Preview. Purchasing Document Category. RSS Feed. Then save, check and activate the process chain and provide information, where applicable, about which server the process chain should be scheduled on. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Suppose the sale order is 20 qty, there will be couple of records with 20 qty, doubling up the qty. When I enhance comm. 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. 3. g. In LBWQ no entry for MCEX02 exist. With this handy table you can find the status of your current job or previous initialization jobs through SM37. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. We appended cost center and cost element to this extractor using FUNCTION EXIT_SAPLEINS_001. Check the. I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 . 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. When testing the data, we noticed that certain PO's that are in the tables EKPO are not showing up in the 2lis_02_ITM PSA. (2LIS_02_ITM). * For more information about source system IDs, see SAP HANA-Optimized BI Content. 3. The Setup Tables are the objects from which the Business Warehouse system is going to extract data for Full loads and Initialization on LO Cockpit DataSources. KNTTP – Account Assignment Category. That means setup process wasn't happen correctly. LO Cockpit - Basic Question. 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. structure in LBWE for 2LIS_02_SCL. All 3 2lis_02_itm, hdr and scl were enhanced to add additional fields. The details are as below:2LIS_11_VAITM Data Source is not fetching data | SCN. Step two: Delete delta entries in RSA7. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :.