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. This field is not present in the source structure 2LIS_02_ITM. When I try to do this in the conventional way (in transaction RSA6, button 'E. This is available in SBIW. Ship-to Party. 3. Important Key Figures: ROCANCEL. Sales Document Item Data (2LIS_11_VAITM) - /IMO/CMSD11. 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. 2. SAP Tables SAP Table Fields (New) SAP Glossary Search; SAP FMs; SAP ABAP Reports; SAP BW Datasources;. create ur infostructure using MC21 transaction code. 2lis 02 Itm Database Tables in SAP (23 Tables) MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/PUR_IS11. Transaction LBWQ in ECC: MCEX02. 2LIS_18_I0CAUSE: Full & Delta: Customer Service: 2LIS_18_I0ACTY: Full & Delta Financial Accounting and Controlling. However, when I want to re-extract ""Purchasing"" I get a message ""Data source 2LIS_02_HDR contains data still to be transferred"". Prerequisites. I'm using OLIG and OLIGBW to fill setup tables but there are certain. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2LIS_11_VAKON: Order Condition Data. Transformation Rule. RSA3 for 2LIS_02_ITM,2LIS_02_SCL , 2LIS_03_BX,. g. what is the reason , pls. With this process chain, the initial data set is updated (initialization of the delta process) in the data targets affected (InfoArea. Datasource Jest Table BW Extractors in SAP (25 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. no (EBELP). 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. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 0B) ( 2LIS_11_VAITM ), is used to update the Media Product Sales (M/PS) data targets, for which the SD order document is used as the basis. When I loaded to BW , 2LIS_02_ITM transferred some records but added 0 Records. Invoice Verification. the situation is that when I run delta it fetches 0 records. Purchasing Document Category. So this thing need to be keep in mind while reconciling with ECC table specially for purchasing data. 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. I checked in RSA3 and the set up tables all the above datasources have records. 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),. EKKO - Header. Click ‘Yes’ to proceed further. Maintain Extract Structure MC02M_0ITM. create your update rules using MC24. Comparing DataSource 2LIS_02_SCL to ME80FN. 2lis 04 P Arbpl Tables BW Datasources Most important BW Extractors for 2lis 04 P Arbpl Tables # BW DATASOURCE Description. MC11VA0STH: Extraction MD Order Header Status for DataSource 2LIS_11_VASTH. 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 :. PO. Follow RSS Feed HI Experts, i am abaper. OLI1BW INVCO Stat. SAP BW/4HANA. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . Purchasing 2LIS_02_ITM MC02M_0ITMSETUP. SAP R/3 Enterprise. 2LIS_02_ITM - Adding field problem | SAP Community Relevancy Factor: 1. e. Maintain enhancement in LEINS001. I'm trying to design a dataflow from a SAP ECC 2lis_02_itm delta extractor to sql server table (odp extractor -->sql -->map_cdc_operation --> sql table. When is it necessary to reload the setup table? For Example. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 :. . RemoteCube-Compatible. When I execute the RSA3 for different Datasources I can see data only in. 0B, InfoSource 2LIS_04_P_MATNR replaces InfoSource 2LIS_04_S280. I have gone through many threads with similar subject but dint got proper solution for this. Step two: Delete delta entries in RSA7. 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. BEDAT. There I see data only for some extractors (2LIS_46_SCL and 2LIS_46_ITM) : see attached picture issue-gtm-01. 2166572-What tables are read for datasource 2LIS_06_INV and basic logic. And after the setup table is filled, data in 2LIS_02_SRV gets duplicated. SAP Table Field : ERNAM - Created by Top 200 SAP Tables containing the field/column ERNAM. Use. MC02M_0ITMSETUP if it have any records" Customized BADI Name – ZPP_DS_2LIS_02_ITM. 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. Data load for :2LIS_02_HDR. The modeling property Inbound table as extended table has been turned on. cat = F ) . 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. 0. Follow. The fields are filled with an. Customized BADI Name – ZPP_DS_2LIS_02_ITM. On top of this, setup table was filled, but I see no data for 2lis_02_itm. I then delete the Contents of Setup table for Application '02' - message ""setup tables deleted successfully"". You should find table names here. SAP Knowledge Base Article - Preview. I've done all the "tasks" for setup tables, but i don't have 0PROCESSKEY. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_CGR: Produced Activity: Delivery of Confirmations: MM - Materials Management: 2LIS_02_SCN: Produced Activity: Confirmation of Schedule Lines: MM - Materials Management:. Is it the right method or should it have been add. Due to a company migration, We are using a program to delete line items of a PO. 0B) - SAP Documentation. Fill setup table. "Document data restriction" when filling setup table. excuse me for this message, but I have a problem and I think you could help me. ALIEF - Number of Deliveries. 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:. Implemented class Name – ZCL_DS_2LIS_02_ITM. Sap Supply Chain Management Tables in SAP. 2LIS_02_ITM: DS only for Direct Access, 2181511: 0MM_PUR_PO_SCL: 2LIS_02_SCL: DS only for Direct Access, 2181511: 0MM_PUR_PO_SCN: 2LIS_02_SCN. In LBWQ no entry for MCEX02 exist. SETUP tables not filling for 2LIS_02_ITM. I have added field LOEKZ (Deletion indicator) to datasource 2LIS_02_ITM from t-code LBWE and activated. using help. SAP Tables SAP Table Fields (New) SAP Glossary Search. But <u>it's work with a FULL infopackage</u>. This means the persistence of data for this. Extraction Table PFO_GO_00IV (Portfolio Assignment) - 13 : 2LIS_12_VCITM Delivery Item Data SD - Sales and Distribution: 14 :Use. Use. We are analbe to get the records for "Pruch Docu Catgory" = L(Scheduling Agreement). 4 ; SAP NetWeaver 7. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 - SAP Help Portal Relevancy Factor: 10. Purchasing Data (Item Level) NA. We currently have delta load happening from the same data source. 0LOG_SYS_BE. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 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. g. There is a table that maps movement type to process key. Jun 15, 2007 at 04:37 PM. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. Functional Area:. The DSO provides insight into the delivery service of vendors by exploring. Best Answer. Purchase Info Record Tables. 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. I have also deleted the setup tables and filled them again. Transa ctional. 5. Issues in Filling Setup table for 2LIS_02_HDR | SAP Community Relevancy Factor: 1. also check in BD87. Field PSTYP. I have pasted the eror message below for reference. 100 -> 100 -> 200. For information, I had the same problem with 2LIS_02_ITM. I have a problem with the delta. 5. But when the user changes only the account assignment of an outline agreement , without changing any other fields (e. But in RSA7 , there are 0 recrods . Source System for R/3 Entry*. my question is what transaction code can I see this field in BW Table. MCEX03. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. I did a setup table fill-up of 2lis_03_bf and I'm seeing missing material documents with movement type 561. I am trying to fill up the SETUP tables. 2lis_11_v_ssl. of entries in Set up tables. The EKPO table (Purchasing Document Item). It was huge reload project for us which continued for a. Login; Become a Premium Member; SAP TCodes; Tables. You think 2LIS_06_INV extracts too many records either in the INIT, Delta or Full loads. request - The Setup-tables are populated in a separate IMG-process (tcode: SBIW): "Data Transfer to the SAP Business Information Warehouse -> Settings for Application-Specific DataSources (PI) -> Logistics -> Managing. MC11V_0ITM: Extraction SD Sales BW: Document Item Allocation for DataSource 2LIS_11_V_ITM. 4. i need to get the data from different tables. We can replace the contents of internal dd_belnr through flat file upload. Runn full load. with SE11 transaction you can see these tables. 2LIS_02_CGR 2LIS_02_SGR 2LIS_02_SCN. The EKPO table ( Purchasing. 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. Follow the below steps to get the lost delta, will be useful for any loads. 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. 1. My data flow is direct load to Info cube using 2lis_02_ITM and SCL datasources. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. KNTTP – Account Assignment Category. 339 Views. Figure 7: BW Control Table – Fields . However, when we do delta-load, none of the account. I'm using OLIG and OLIGBW to fill setup tables but there are certain documents/contracts I can. (2LIS_11_V_ITM) - /IMO/CMSD16 . How can I find which tables in R/3 are the source tables for this and that extractor (e. BW: Transaction Key in 2LIS_02_ITM. I have an issue with Purchasing data source: 2LIS_02_ITM. In the second InfoProvider, you can. Date of Purchasing Document. 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). Delivery date (SCLDT)= 01. Cannot see the data for datasrc 2lis_02_scl in RSA3. Data Source:2LIS_02_ITM. Even I have tried again by deleting the setup tables & then fileed it but syill cant see data only in 2lis_02_sclI am loading 0PUR_O01 from 2LIS_02_ITM/SGR/CGR and SCN. Delete the setup Table using LBWG . 2LIS_02_ITM Purchasing Data (Item Level) MM - Materials Management: 14 : 2LIS_05_QE2 Inspection Result: Quantitative Data QM - Quality Management: 15 :Transformation. 2LIS_13_VDKON: Billing Condition Data. An overview of Datasources and the programs filling the relevant setup table (named MC*SETUP). 2lis_11_v_itm. 2LIS_13_VDITM: Billing Document Item Data. During the initial load, everything comes along fine all the way to PSA. LFA1 NAME1. Technically, during the full load, these items should be extracted with a recordmode = R. 0. Dear All, It would be really helpful to know the used tables for datasource 2LIS_02_ITM. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Clear "LBWQ" 04. 2. 0OPS_12_ITM. It looks to me, that it provides information about, whether it is a invoice, GR, and so on. Environment. 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. Step 4) Choose the datasource 2LIS_02_ITM, which is purchasing data at Item level. The activation of the business function by itself will not enhance the database tables. 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. EKBE is a standard Purchasing Transparent Table in SAP MM application, which stores History per Purchasing Document data. Thank you all for your replies. DataStore object (advanced): SD: Billing Document Item Data (2LIS_13_VDITM) - /IMO/CMSD31. then go to T- Code OLI9BW. Go to RSA2, enter DataSource name 2LIS_02_ITM,. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . KONV KSCHL. After that, AWS Supply Chain automatically creates the Amazon S3 paths and ingests data from the SAP source tables. Delete data "LBWG" 05. If a data inbound layer persistence and/or a corporate memory persistence is used, the transformation from this DataStore. LOOP AT c_t_data into l_2lis_02_itm. Technical name: 2LIS_12_VCITM. On 09. Use corresponding exit FM as template and copy the import, Export, Table, Exception. 2LIS_02_ITM : MC02M_0ITMSETUP : Storage BW Setup for MC02M_OITM : Purchasing :. but when I perform initialization of LIS table on R/3 side I make initial load to BW I can see that there is an. The 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. A goods movement is posted with the following information: Posting date (BUDAT) = 05. When I check in EKPO table, deletion indicator "L" is available for all deleted PO's. That means setup process wasn't happen correctly. 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. 0. I now am trying to get publishing back on track. Thanks for the quick response. Wanted to know whether is there any way to find out how many entries are remaining in setup table to be transfered to BW. 192 Views. Most important Database Tables for 2lis 02 Itm Data Source Tab # TABLE Description Application Table Type; 1 : MARA: General Material data: Logistics - Material Master: Transparent Table 2 : MARC: Plant data for Material Logistics - Material Master: Transparent Table 3 : VBAK: Sales Document: Header data: SD - Sales:Table of Contents SAP BW/4HANA Content Add-On. Please note , Everything is fine with setup table data , update rule ( Overwrite mode) and other BW part. 0. 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. 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. It s failing for only 2LIS_02_ITM only. Datasource is in active mode. Dear All, I have activated BI Contents: 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_HCL. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). The account assignment category determines the account assignment data for an item, such as cost center and account number. Sep 16, 2009 at 06:26 PM. Select the Data Source ( 2LIS_02_ITM ) 3. When I check with RSA3 I've got a lot of records. Hi, Where can i find the t-codes for filling the setup table for all the logistics datasources. Transaction Data. 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 :. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. I have already done the following steps: 1 - Transaction SBIW: Settings for Application-Specific DataSources (PI) Logistics. Step one: stop all postings in connected ERP system. This is derived from the statisitcs updating facility maintained for updating the LIS (PURCHIS) tables in R/3. Newer data is not available when checking the datasources. This document has 2 parts. Clear setup tables in LBWG. SAP BW/4HANA. I have already maintain datasource 2LIS_02_ITM through LBWE. Whereas 2LIS_02_SGR transferred and added records. 3. Setup: Material Movemts. Jan 29, 2008 at 06:41 PM. Like I activated the datasources in LBWE than I intialised all datasources. Delta queue maintenance. For e. Sap Tcode Ksbt Tables in SAP. Create column table “02_ITM” as (select * from “INF627126″. Go inside the class ZCL_DS_2LIS_02_ITM and implement the below code – ATA : LT_DATA TYPE STANDARD TABLE OF MC02M_0ITM. Hi Fabio, No You cannot do a setup for 2LIS_02_ITM only, You can only do a setup for the whole 2LIS_02. Recently, I need Batch data for reporting related to Purchasing , fortunately there is field CHARG (Batch) in 2LIS_02_ITM. 3. Description. All 3 2lis_02_itm, hdr and scl were enhanced to add additional fields. 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. I am trying to find the procedure / sequence in to carry out in. 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. The counted number depends on how often a material appears in a GR document. I know that For purchase order details we used 2 datasources 1. EKKO. CM SD: Sales-Shipping Allocation Item Data (2LIS_11_V_ITM) - /IM: CM SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD: CM SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD1:. There will be no impact on existing processes. But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. LBWE transaction - inactivate update, deleted setup tables in application component 02(MM) and also deleted any delta queue in /nrso2. 01. It contains the complete history of the loaded data. BSTYP. 3. The DSO is directly supplied from the Info/DataSource 2LIS_06_INV. To stop the access from outside we use t-code SM01 to. We need the data for the two new fields going forward. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. When I try to load setup data I got this message in setup table. But this isn't working the way I would expect: the full load contains only those records which are in the setup tables MC02M_0HDRSETUP, etc. However I observed a different behaviour in case of POs with an Invoicing Plan ( mostly framework POs) E. 2LIS_02_ITM. 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. Use. Then I. But you need to find the filed (AEDAT) belongs to which table. Source System for R/3 Entity*. SAP. Scenario 1: All the line items associated are marked for deletion,Then 2LIS_02_ITM--> LOEKZ being extracted as L,No issues here. Name of Target InfoObject. 2lis 02 Itm # TABLE Description Application Table Type; 1 : EKPO: Purchasing Document Item MM - Purchasing: Transparent Table 2 : EKKO: Purchasing Document Header MM - Purchasing: Transparent Table 3 : EBAN: Purchase Requisition MM - Purchasing:Issue: Even when Deletion Indicator is marked for a PO Item in P20, the same is not reflected in BW via delta/full repair loads. Once we get the above screen, we could specify the component (02, 11, etc…) and click on execute button. 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. 01. Sap Mm Contract Tables in SAP. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). 2lis_11_vascl. IF i_datasource = '2LIS_02_ITM'. 2LIS_03_BF, 2LIS_03_BX, 2LIS_03_UM)?. choose your characteristics and key figures. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. News & Insights. 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. DATA: l_2lis_02_itm type mc02m_0itm, l_index type sy-tabix, lt_ekko type standard table of ekko, wa_ekko type ekko. TABW is a standard Basic Functions Transparent Table in SAP FI application, which stores Asset transaction types data. Purchase Requisition Tables. 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. 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). READ TABLE lt_ekko into wa_ekkoTable YBWMAPPING is used by the class YCL_BW_MAPPING. Note: As an alternative you can also use DHCDCVCDSEXTRE in SE16 which contains more or less the same information. This DSO (advanced) contains delivery related indicators and key figures for purchase order items. then data inconsistency will be happen. 123456 20 L. Go to t-code ODQMON (in ECC). Append MCEKPO. I have enhanced the datasource(2lis_02_itm) for the Tolerance fields. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 0FI_AP_4. 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. The Problem is, that the setup tables are not getting poulated. g quantities),. Thank you all four you responses. 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. KNTTP – Account Assignment Category. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . I have been using DataSource: 2LIS_02_ITM for couple of months and I have loaded data into (Full and Deltas). Locate your Extractor (Datasource). If you choose the Header/Item Data view in the transaction ME80FN, you can compare the data in the following DataSource fields with the original document data in the ERP system: MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11. In rsa3 and in set up tables I see data fro 2LIS_02_ITM AND 2LIS_02_SCL. Custom Duty 14% JCDB . 2008 i have executed Initial Load from BI. Available as of Plug-In Release. see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Purchasing. Go to LBWE (LO Cockpit), select DataSource 2LIS_02_SCL, click on Maintenance icon in Structure column, say Continue. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :. 11. The outbound queue is filled for the following queues in the. Transformation * For more information about source system IDs, see SAP HANA-Optimized BI Content. Transformation. and added a Z-field (ZZEKKOL) for this field. better till first info provider DSO. When running the setup for application 02 (TR OLI3BW), the table was not filled: running RSA3 with no restrictions did not retrieve any records. These Z-Fields are in the database table EKPO. If they don't solve delta queue I'll report to SAP. Base Tables . Figure 8: BW Control Table – Entry Help/Check . 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. 3. I need to enhance the Datasource 2LIS_02_ITM. Table of Contents SAP BW/4HANA Content Add-On. Note: This step is used when we need to add additional fields, to push into BW. 04. MM-PUR: Purchase Order Delivery (Items) - /IMO/PUR_D21. You can look at the includes with *TOP* eg INCLUDE mcex02top. Product. Table of Origin. The first extraction of the document itself getting two positive records in the same datapackage. 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. SAP delivers the following example BEx queries on top of MultiProviders Sales Overview. Delta.