2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. Release Strategy Tables. 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. BW: Transaction Key in 2LIS_02_ITM. 2LIS_02_ITM, 2LIS_02_HDR, 2LIS_* , KBA , BC-BW , BW Service API , BW-BCT-MM. SAP R/3 Enterprise all versions Keywords. 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. Login; Become a Premium Member; SAP TCodes; Tables. I am using the 2LIS_02_ITM extractor. SETUP tables not filling for 2LIS_02_ITM. The following jobs move the data from the outbound queue to BW. Use. Available as of OLTP Release. However in the S/4HANA system, table KONV is obsolete and replaced by table. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 0GN_R3_SSY. 2LIS_02_ITM - Adding fields to communication structure - User exit | SAP Community Relevancy Factor: 1. Functional Area:. Hi All, When a PO is posted the vaules are being picked by the 2LIS_02_ITM extractor. better till first info provider DSO. -----Mensaje original-----De: John Parks via sap-r3-bw [mailto:sap-r3. after this load you can run deltas. To reach the customising node use transaction OMGO. RemoteCube-Compatible. This process chain activates and for the first time fills all data targets for the scenario Delivery Service Purchasing (InfoArea 0MMPUR_DLV, display component Process Chains Delivery Service MM (0MM_DLV)). 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. Or if you are looking for OSS NOte #. SAP delivers the following example BEx queries on top of MultiProviders Sales Overview. RSS Feed. I have read that it is necessary to delete the setup tables before reloading the setup tables to make sure that there is no duplicate data, however I have different question. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . Loaded 0%. 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. By debugging function module MCEX02_PREPARE_INFO it was found that the field UPDACT in table TMCEXACT. 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. Purchase Invoice Tables. Presss F5 and get inside the form “select_option_fill”. READ TABLE i_t_ekpo WITH KEY ebeln = xmcekpo-ebeln ebelp = xmcekpo-ebelp. 5. of entries in Set up tables. 1. But you need to find the filed (AEDAT) belongs to which table. 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. if anyone knows tcodes for runinng the set uptable to each data source separatley. 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. This InfoSource provides the transaction data from the production process, with reference to the order header and item. Source Tables (Function Module): MCEX_BW_LO_API (Function Module) SAP Help, Wiki, Q&A and other resources for 2LIS_03_BF. Runn full load. There I see data only for some extractors (2LIS_46_SCL and 2LIS_46_ITM) : see attached picture issue-gtm-01. MC02M_0SGR: Produced Activity: Delivery of Schedule Lines Maintenance for Data Source 2LIS_02_SGR 8 31 139,142. Code - 'oli2bw'. 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. BEDAT. 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. create ur infostructure using MC21 transaction code. 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. also full update of 2LIS_13_VDITM featches only records that have been uploaded with initial load. If you followed below steps, no chance to miss single reocrd. 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:. In the ERP system, this information is contained in the following tables:. Table of Contents SAP BW/4HANA Content Add-On. # Table. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :. run delta loads asusal. Once we get the above screen, we could specify the component (02, 11, etc…) and click on execute button. png. I created the setup tables via "Purchasing - Perform Setup", but only 3 setup tables were filled. This is how the SAP has defined. we have done initialisation and filled setup tables. The configuration of the table looks as follows. Hi Can anybody tell me the table name for the datasource 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:. You have to enhance the data source if the field is not available to you. Whereas 2LIS_02_SGR transferred and added records. Read more. -----Mensaje original-----De: John Parks via sap-r3-bw [mailto:sap-r3. so the standard. transfered datasource 2LIS_02_ITM using tcode RSA5. Checked data in "RSA3" ex: 200 records. In RSA7 i purged or deleted the records and entry for this datasource. Transformation * For more information about source system IDs, see SAP HANA-Optimized BI Content. following fields of DataSource 0CUSTOMER_TEXT: Sold-to Party. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. The EKPO table ( Purchasing. I have gone through many threads with similar subject but dint got proper solution for this. When i. The purchase order exists in APO in the form of an order. This DataSource extracts Accounts Payable Accounting line items from tables BSIK (open items) and BSAK (cleared items) in the R/3 source system. 2LIS_11_V_SSL: Sales Document: Order Delivery. Symptom. In debug mode search for below string and add breakpoint there. BSART. ECC -> RSA2 -> Generic Delta -> field name is empty. I'm using OLIG and OLIGBW to fill setup tables but there are certain. Field in Table of Origin. Filled with the 2-digit logical backend system (based on LOGSY) Logical System Backend. I could not find any Info on this kind of issue in SDN. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. ECC -> SE11 -> ROOSOURCE -> Both "GENDELTAFD" and "GENDELTATP" are empty too. Purchasing Group Tables. I have already done the following steps: 1 - Transaction SBIW: Settings for Application-Specific DataSources (PI) Logistics. But these datasource read data from EKKO, EKPO & EKBE table and material document number field is availble in EKBE. Prerequisites. Then I. AND ebelp = mc02m_0itm-ebelp. 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. PO Doc no (EBELN), PO Itm. Processkeys are maintained. 5B. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_40_REVAL: Revaluation at Retail: IS - Retail: 2LIS_11_VAITM: Sales Document Item Data:1. RSS Feed. Why? What am i missing out do i need to do any changes before i actiavte the in-active tables in LO-Cockpit. using help. However I observed a different behaviour in case of POs with an Invoicing Plan ( mostly framework POs) E. 04. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. and Yes,I have DELETED setup tables data prior to running the Setup process. 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. In ekpo screenshot you can find final Invoice flag is set (EKPO-EREKZ) for all the PO line. But for 2lis_02_sgr we are able to get records only for "Pruch Docu Catgory" = F(Purchase Order). Sap Supply Chain Management Tables in SAP. We have recently activated the 2LIS_02_ITM (Purchasing item extractor) and as part of integration testing, have filled the setup tables and performed a full load. I have been using DataSource: 2LIS_02_ITM for couple of months and I have loaded data into (Full and Deltas). The account assignment category determines the account assignment data for an item, such as cost center and account number. 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. (Account Level) (2LIS_02_ACC). 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. 01. MC11V_0ITM: Extraction SD Sales BW: Document Item Allocation for DataSource 2LIS_11_V_ITM. "Document data restriction" when filling setup table. If no data inbound. But this d/s 2LIS_02_SRV doesnt pick/identify the deleted service entry sheets. 3. 163 Views. BW . The system therefore only executes a delta update for this DataSource if. e. SAP Table Field : BUDAT - Posting Date Top 200 SAP Tables containing the field/column BUDAT. When I check with RSA3 I've got a lot of records. The issue is when I ONLY change the. SYDAT is Item created on - EKPO-AEDAT. As of SAP enhancement package 6 for SAP ERP 6. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . Customer-Defined DataSource Logistics Management of Extract Structures Initialization Fill Recompiled Tables Application-Specific Recompilation Purchasing – Carry Out Recompilation. Transaction data. Former Member. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. ) 2LIS_02_SCL & 2. 3. SD-DLV: Sales Document: Order Delivery (2LIS_11_V_SSL) - /IMO/SD_IS17. (2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL in my case), if we have to do full upload, do we still need to run the setup in R/3. eg: if i do the following action: Fill 1 -> Delete - Fill 2. Where in BW should be stored the data about secondary costs on purchase (acquisition) which evaluate the real price of goods?. MM-PUR: Purchase Order Delivery (Items) - /IMO/PUR_D21. In LBWQ no entry for MCEX02 exist. etc. 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. During the initial load, everything comes along fine all the way to PSA. Purpose. 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. 2. To stop the access from outside we use t-code SM01 to. Maintain extract structure and datasource. 2. There is a table that maps movement type to process key. These documents are also not getting filled into Setup Table by OLI3BW. 5. MC02M_0CGRSETUP. 2LIS_02_ACC. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). Hi We are using the following logic to enhance 2lis_02_itm with different fields from diff tables. When is it necessary to reload the setup table? For Example. Dear All, I have activated BI Contents: 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_HCL. Select the Data Source ( 2LIS_02_ITM ) 3. 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:. We could able to see the enahnced field data in RSA3 , but after making any change in ME22n its not p. When running the setup for application 02 (TR OLI3BW), the table was not filled: running RSA3 with no restrictions did not retrieve any records. 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. Click ‘Yes’ to proceed further. and enhanced the datasources ITM and SCL adding one Char in. We've created a new field called, e. So I did the following steps : 1. Status record it will be having different statuses like idoc created,idoc posted etc. 2LIS_02_HDR purchasing order header level data,2LIS_02_ITM purchasing order item level data,2LIS_02_SCL purchasing order schedule level data. SAP BW Datasource : 2LIS_02_SCL - Purchasing Data (Schedule Line Level). I need to enhance the Datasource 2LIS_02_ITM. Purchasing Data (Schedule Line Level) NA. 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. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL. In the standard extractor 2LIS_02_ITM the field BADAT is check as Field only known in customer exit. Product. I cannot see this same field under the same comm. Mapped to InfoObject. Then I will build a ODS on top of these extractors. 2LIS_18_I0CAUSE: Full & Delta: Customer Service: 2LIS_18_I0ACTY: Full & Delta Financial Accounting and Controlling. Using this approach, the advantages are: The code is limited to few numbers of. Purchase Order Tables. 2. And after the setup table is filled, data in 2LIS_02_SRV gets duplicated. Delete data "LBWG" 05. or alternatively you can build your own custom extractor using purchasing tables EKKO,. The fields concerned are located in one of the Purchase Order screens (ME21). 63 Views. This counter determines the number of deliveries based on the GR document items. Follow. Moreover STAPO (Item is statistical) = X, means Item is statistical. Symptom. For more information on this topic, refer to the. 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, 1. We are using the BW DataSource 2LIS_02_SCL from the LO Cockpit and have added these two fields from the Customizing cockpit (LBWE): WAMNG WEMNG. Application DataSource Setup Table. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. correct me if iam wrong. MC11V_0ITMSETUP. Consider Process Key 2 for GR amount and Process Key 3 for Invoice Amount. Important Key Figures: ROCANCEL. 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". 2lis_02_itm Structure is active. Environment. 2LIS_02_ITM. Append MCEKPO. now i want to fill setup tables for below datasources, can you suggest what are tcodes to fill up setup tables for below datasources. Please note , Everything is fine with setup table data , update rule ( Overwrite mode) and other BW part. 01. EKKO. I'm using OLIG and OLIGBW to fill setup tables but there are certain documents/contracts I can. How can I find which tables in R/3 are the source tables for this and that extractor (e. This DataSource replaces DataSource 0FI_AP_3 (Accounts Payable: Line Items) and uses the same extraction structure. e, 2lis_02_itm, or 2lis_02_hdr), both the header and the item gets filled up. READ TABLE lt_ekko into wa_ekkoTable YBWMAPPING is used by the class YCL_BW_MAPPING. 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. Root Cause: If a PO Item in P20 is. hi Check in Base tables 😊. But I do not see any entries in the setup table 'MC02M_0ITMSETUP' after the SETUP run. Go to LBWE (LO Cockpit), select DataSource 2LIS_02_SCL, click on Maintenance icon in Structure column, say Continue. ALIEF - Number of Deliveries. BEDAT. Block user to modify to modify purchase. 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. FI and COPA is easy to get , the hardest to get at is the LO extractors. g. 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. And it shows 0 records. structure MCEKKO with field UNSEZ (on the EKKO table), I can see it in LBWE on the right for selection on the 2LIS_02_ITM datasource. ) We had a similar scenario where we wanted to refresh entire data for 2LIS_13_VDKON. The details are as below:2LIS_11_VAITM Data Source is not fetching data | SCN. 02:PURCHASING. LO Cockpit - Basic Question. Clear setup tables in LBWG. MC02M_0SCLSETUP. Data source. 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 :. This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). With no data in setup tables, rsa7, sm13. sap and forums i found out that for. (2LIS_11_V_ITM) - /IMO/CMSD16 . on BW side make sure Delta mechanism and init load is deleted. The migration of DataSource 0FI_AP_3. This is to keep data that is depending on each other consistent. 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. Clear "RSA7" 03. Add a Comment. 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. Go to RSA6. what is the reason , pls. Type of DataSource. 2LIS_03_UM. This DSO contains delivery related indicators and key figures for purchase order items. 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. Note: As an alternative you can also use DHCDCVCDSEXTRE in SE16 which contains more or less the same information. EKPO - Item. This is available in SBIW. . 3. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. but not in. 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. Step two: Delete delta entries in RSA7. So in the PSA,I am getting 2 records for the PO which has. Base Tables . VRTKZ – Distribution Indicator for Multiple Account Assignment Table of Origin. 2. my question is what transaction code can I see this field in BW Table. I have a problem with 2LIS_13_VDITM delta. I know that For purchase order details we used 2 datasources 1. 0) Basis - BW Service API: VBDATA: Update data: Basis - Client/Server Technology: BW Datasources related to RMBWV302 BW DATASOURCE Description Application ;. 2LIS_02_HDR Purchasing data (Header Level) MM - Materials Management: 16 :2lis 13 Vditm Base Tables BW Datasources Most important BW Extractors for 2lis 13 Vditm Base Tables # BW DATASOURCE Description Application; 1 :. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 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. g If a PO item has qty 10 and Price 5 , then the field ekpo-netwr is 50 ( = 10 * 5) Now if this PO item has 3 invoices. 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). News & Insights. 3 ; SAP NetWeaver 7. The system therefore only executes a delta update for this DataSource if. so I add field CHARG into that datasource. This InfoSource contains the structure to provide purchase data on item level into the EDW Core Layer. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Copy & paste to SE37 eg for 2LIS_02_ITM , extractor MCEX_BW_LO_API is used. you can store the all the Purchase Orders in one InfoProvider ( restricting on doc. 11. the situation is that when I run delta it fetches 0 records. First part explains about the activation of the data source 2lis_02_SRV & second part explains about enhancing it for adding the services line items to be made available for extraction. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. FIELD-SYMBOLS : <LS_DATA> TYPE MC02M_0ITM, <LV_KUNNR> TYPE EBAN-KUNNR, . Figure 9: BW Control Table – Foreign. Maintain Extract Structure MC02M_0ITM. No. 0B) - SAP Documentation. But when the user changes only the account assignment of an outline agreement , without changing any other fields (e. 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. This DataStore Object (DSO) contains the invoice verification data on a granular level. 2lis 11 Vaitm Tables BW Extractors in SAP (28 BW Datasources) Login; Become a Premium Member; SAP TCodes;. ”VT_2LIS_02_ITM”). 0. Transport the Enhanced Data source to Source SAP system . 9) After zero records repeat the step 6 to 7 for double confirmation to avoid any possible data entries. Use. When I check in EKPO table, deletion indicator "L" is available for all deleted PO's. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . 3. There is a requirement to load full load to BW system from 2LIS_02_ITM data source. So , how to know. Purchasing document 4500000001, Item 0010, has the following schedule lines: Schedule line number (SCLNR) = 1. 2LIS_13_VDITM: Billing Document Item Data. Field PSTYP. Then use the function Activate and Schedule to start the process chain according to your scheduling options. 2lis 02 Itm Sap Database Tables in SAP (30 Tables) Logistic Cockpit datasources reads from Setup-tables (like MC02M_0ITMSETUP for 2LIS_02_ITM) when you execute Full or Delta-init. The start routine for the updates ensures that only orders and free-of-charge orders are updated in the DataStore object. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 7 :. I have added field LOEKZ (Deletion indicator) to datasource 2LIS_02_ITM from t-code LBWE and activated. 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 added field BADAT-PR creation date in the extractor structure of 2lis_02_itm. e 4. and then go to BW side and replicate the Datasource. 2LIS_02_ITM. Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04. 0. Sap Tcode Ksbt Tables in SAP. Purchasing 2LIS_02_CGR MC02M_0CGRSETUP BW-Rebuild for. In this case use FM EXIT_SAPLRSAP_001 as template. If no data. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. I can then reference the InfoSources in question since I know HDR data will come ! from EKKO and ITM data will come from EKPO. 2. excuse me for this message, but I have a problem and I think you could help me. NO/PO itm no/ schline. I use the standard extractor 2LIS_02_ITM (order positions) with the update mode "Direct Delta" and apanded Z-fields. This field is not present in the source structure 2LIS_02_ITM. 2lis 03 Bf Table BW Extractors in SAP (29 BW Datasources) Login; Become a Premium Member; Transaction Codes; Tables. Total number of tables/structures containing this field is 4948. Purchase Info Record Tables. 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. 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. 2001. 2lis 11 Vaitm Ecc Source Tables BW Datasources Most important BW Extractors for 2lis 11 Vaitm Ecc Source Tables # BW DATASOURCE Description Application; 1 :. Is there anyway I can get this field populated without writing code for it? "Field BADAT in 2lis_02_itm not displaying values - SAP Q&A"SAP NetWeaver 7. with different condition types fromo KONV table . 04. This means the persistence of data for this. Best Answer. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data: SD - Sales and Distribution: 2LIS_11_VASCL: Sales Document Schedule Line: SD - Sales and Distribution:. 0 EHP 3.