It is field-based and contains all. 2LIS_02_SCL : MC02M_0SCLSETUP : Storage BW Setup for MC02M_OSCL : Purchasing : 2LIS_02_SCN : MC02M_0SCNSETUP : BW-Rebuild for MC02M_0SCN Storage : Purchasing : 2LIS_02_SGR : MC02M_0SGRSETUP : BW-Rebuild for MC02M_0SGR Storage : 03: Inventory Controlling : 2LIS_03_BF : MC03BF0SETUP :. SAP Knowledge Base Article - Preview. 2LIS_02_SCL. 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. 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: For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2016-01-05 04:11:48 Err Id: 17. i. A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!Activate data source of Appl. J_3ASIZE. This is to keep data that is depending on each other consistent. Specifically I am looking at the BWVORG field. BW SD MM FI 常用 数据源. Our task is instead of performing Initialization WITH data transfer by deleting data in corresponding data targets, By considering historical data and time it will take to. 0A. Here Loekz field related data is completely not fetching from the above data sources partial data is able to get. MC02M_0SCN Storage. Thanks, Bobby. It contained the delta queues as. The standard purchasing info objects in BW for storing the subtotals are 0SUBTOT_OC1 –. Comparing DataSource 2LIS_02_SCN to ME80FN. It's almost impossible to get the chance ( when korea plant rest, another plant still running. 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) · Item delivery date (SCLDT)Technical name: 2LIS_02_SCL. when checked the data by RSA3 , I found the system generated mass data(2400 records) . adjusts the quantities to give the true 'open/closed' qty after GR. It depends on key mentioned for BWVORG field in transaction - Transaction Key SAP BW. That is the way SAP provides extractor fields. 2LIS_02_SCL datasource will give the GR values from EKBE table by considering the purchase documents from EKKO table for respective vendor. i did the setup using one purchase order no(of course I deleted the setup table before did it). BUT. This field determines whether these values are from a purchasing order, goods receipt or an invoice. Transactional Data. Your LIS_SCl will contain the schedule line information that is if somebody wants schedule date wise e. 2LIS_03_UM: Revaluations MM - Materials Management: 6. Hi All, Can you please share your experience on the 2LIS_02_ACC data source setup. 'MATERIAL_ATTR,MAT_SALES_ATTR,2LIS_02_SCL,2LIS_03_BF,2LIS_11_VAITM,2LIS_11_VASCL,2LIS_13_VDITM. My client here does not use schedule lines. 02 in LBWE. However, I found 2LIS_02_SCL. result =. Help. - Cross company order -. Method . 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. 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. Pls reply needed urgent,i'm. On this way you could also enable ODP extraction for obsolete SAP standard. A total of 9 records are dropped while extraction from R3 to BI. As much as I understand the key fields which I should be using are EBELN Purchasing Doc. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) ( 2LIS_02_SCL ). As I can see, for every Purchase Order Item I get three records: - one record for the last Invoice Receipt (with Posting date of invoice receipt in BUDAT field) - one record for the last Goods Receipt (with Posting date of goods receipt in BUDAT field) - one record for something else. J_3AKVGR10. 103 movement type in 2lis_02-scl. SAP. MC02M_0SGR: Produced Activity: Delivery of Schedule Lines Maintenance for Data Source 2LIS_02_SGR 2LIS_02_SCL, BUDAT, posting date, ELIKZ, delivery completion, DCI, GR, goods receipt, BWVORG , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem About this page This is a preview of a SAP Knowledge Base Article. Industry key is also set and application component is also populating. 1) these extractors don't appear to have the same data. Likewise proceed with all the extractor. DELETE TABLE SOURCE_PACKAGE from wa_package. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. 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: You can check the information about the goods receipt in the Purchase Order History view. Need advise to build a standard DSO over 2LIS_02_SCL extractor to capture PO details with PO, GR, IR amount and quantity with delta load. Now we realize that processkeys 010 are missing but 2LIS_02_ITM catches these. Then save the PO. Extraction job in R3 is unable to extract any data, so it . e. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. ANLH: Main Asset Number. At my client we implemented the PO Sch Extrc 2LIS_02_SCL and 2LIS_02_ITM. Hi, I have activated and loaded data in datasource 2lis_02_scl. g. Step 2 : Activate and transfer the Application Component Hierarchy(One Time Activity in the project). Based on DataSource: 2LIS_02_SGR. SAP. Please suggest me the ideal way to complete this task. ALIEF - Number of Deliveries. I am trying to work with the standard Purchasing queries based on 0PUR_C01. calculation logic for field BWMNG in 2lis_02_scl - SAP Q&A Relevancy Factor: 1. 以下是SAP ECC中各主要数据源与描述. Fields BWGEO, BWGEOO, BWGVP, BWGVO, BWNETWR, BWMNG, etc. It will send a change like below: Record Mode; EVERS; QTY. RSA3. 1. But we realized that process key 7 was not captured by 2lis_02_itm and had to implement 2lis_02_scl to cater this deficiency. Maintain your data source in LBWE, For this: (I) Inactivate the data source. . 2LIS_02_SCL and _ITM Purchasing Cube 0PUR_C01. - Process Key 001:PO. Requires; Object Type. 2. Symptom. Comparing DataSource. Activate ODS data 0PUR_DS03. In my example, I focus on an potential alternative to the classic LIS DataSource 2LIS_02_ITM (MM Purchase Order Items): C_PurchaseOrderItemDEX is a released delta-enabled CDS extractor. Go to. Purchasing 2LIS_02_SCN MC02M_0SCNSETUP BW-Rebuild for. You will find that value of "LOEKZ" of. 2LIS_02_SCL not extracting field EKPO-LOEKZ. 2LIS_02_SCL extractor does not always fetch data from EKET table. RemoteCube Compatibility. From the business content, in the update rule: 2LIS_02_SCL -> 0PUR_DS03. In transactions "RSA1" has gone to a bookmark "DataSources", has selected a datasource "2LIS_02_SCL" and has chosen from the contextual menu "Manage". I tried pulling the data from R/3. Kindly suggest any Solution. O Qty is 50 its getting clubbed as 250 in the Cube it has an direct delta FYI, Could you guys throw some light. Sent Job ABORTED update to SAP. Instead it still comes across with process key '02' which is for standard goods receipt (movement type 101). 2lis_02_scl and 2lis_02_itm - SAP Q&A Relevancy Factor: 1. Use. Please help. Comparing DataSource 2LIS_02_SGR to ME80FN. Key Fields for DSO using 2lis_02_SCL and 2lis_02_ITM. Once the setup table filling is done. Bei Einkaufsbelegen, die in einer anderen als der Hauswährung angelegt wurden oder zu denen Belege wie z. DSO Will Not Activate after Transport with rc=8. Transaction LBWQ in ECC: MCEX02. Here is a list of the values that process key - BWVORG can assume, according with the purchasing item type, processed document and purchasing order type: 1 - For non return items: a) Document type: Purchasing order. For more information, see the data source documentation. Hit enter to search. - Process Key 002:GR. Load data InfoPackage 2LIS_02_CGR_INIT_R3. To ingest data from an SAP S/4HANA data source, perform the following procedure. For e. But for 2LIS_02_SCL, i am not getting either 7. Step one: stop all postings in connected ERP system. FAQ: Setup table filling with 2LIS* extractors. there is a possibility the records containing this date might be getting filtered based on some difefrent field filter. and choose the industry sector "Standard (Core)". 2lis_02_scl. I am extracting purchasing data into BW using datasource 2LIS_02_SCL into ODS 0PUR_DS03. Lost while creating the. Search for additional results. RSS Feed. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. I am activating structure. I am still finding out which of these extractor needs to be modified. TBSL: Posting Keys. Schedule Line Level: DataSource 2LIS_02_SCL -> InfoSource 2LIS_02_SCL -> DSO ZPUR_O02 (Schedule Line Level) -> InfoCube ZPUR_C01. Purchasing 2LIS_02_SGR MC02M_0SGRSETUP BW-Rebuild for. 1)Deleted delta queue for ITM and SCL on DEV 2)Confirmed on BWP that no delta existed for SCL or ITMYou have the option to use the old and new method. This counter determines the number of deliveries based on the GR document items. 0SCHED_DATE is mapped to SCL_BEDAT in the correspondending data source 2LIS_02_SCL. Technical name: 2LIS_12_VCITM. My predecessor actually changed the standard definition of this. We are using two PO extrctors 2LIS_02_ITM & 2LIS_02_SCL to load data, both are working fine. Oct 18, 2007 at 09:39 AM. not ectract the good Invoice receipt quantity. Feb 04, 2011 at 01:37 AM. Please do advise on the below questions. Then save, check and activate the process chain and provide information, where applicable, about which server the process chain should be scheduled on. Thanks, John. The ODS Purchase order schedule lines consolidates data from the InfoSources Purchasing Data Document Schedule Line Level (2LIS_02_SCL) und Offsetting Confirmation and Goods Receipt (2LIS_02_SGR). But these datasource read data from EKKO,. MCBO -Transaction key active or not. Also processkey 007 is missing from 2LIS_02_ITM. (table EKPA). However, my delta infopackage is not picking up any new records. I have succeed to get some key figures like PO Quantity, GR Quantity and Invoice Receipt Quantity according to the Process Key value. You can check the data from the DataSource 2LIS_02_SCL in last two views mentioned. Similarly Now Check for the Data Source 2LIS_02_ITM Now Check for the Data Source 2LIS_02_SCL Go to Tcode SM13 (update Request) Go to ME21N (creating Purchase Order) Go to SMQ1 (Queue Status). Kindly provide a solution for the below problem whcih i am facing with 2lis_02_itm and scl data sources. Vote up 2 Vote down. LBWE-- >Purchasing >Extract structures ---->2LIS_02_HDR/SCL/ITM (DATA SOURCES),when i click on the in-active tab to make change and activate i get a alert as the DATA SOURCE doesn't exist. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 5 : 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 6 :. 1. When i extract a Invoice receipt in delta : (0processkey = 3). I've done all the "tasks" for setup tables, but i don't have 0PROCESSKEY. AFS 3. 2LIS_02_HDR EKKO, EKBE,T001, EKPA. Vote up 0 Vote down. we are actually facing an issue with the standard extractor 2LIS_02_SCL - schedule line Level of purchase orders. But i want know like, how we can show the Open PO Value & Open PO Qty in the BI report level. "Hi, we need to track the modifiations of the PARVW (Role Partner) when it is changed in a Purchasing document. For example, by comparing the planned and actual goods issue dates, you can determine which quantities were delivered on time. Dear All, When I am populating 0PUR_C01 using the InfoSource (2LIS_02_SCL) I am getting multiple entries like if I have one material record for an relevant P. failing. Visit SAP Support Portal's SAP Notes and KBA Search. MC11V_0SSL: Extraction MD Sales: Order Delivery for DataSource 2LIS_11_V_SSL. The EKET (Purchasing Schedule Line) table doesn't have this. As you are aware that some fields of the standard extractors gets derived via Calulation (SAP derived logic ) . When checking the OMJJ transaction, the 103 and 104 movement types are marked. The information under these fields are dependent from the information of field BWVORG (BW transaction key). For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. If the target area is longer or shorter . LIS_ITM is meant for item level information e. From ITM all fields available are needed and from SCL requisitioner (AFNAM), purchase reg. Inconsistent Delivery Date in BW after extraction using datasource 2LIS_02_SCL from ECC table EKET Delivery date EINDT in DataSource 2LIS_02_SCL does not match ECC data. There r 2 ways to get this data. Key Fields;2lis_02_acc, 2lis_02_cgr, 2lis_02_hdr, 2lis_02_itm, 2lis_02_scl, 2lis_02_scn, 2lis_02_sgr, 2lis_03_bf, 2lis_03_bx, 2lis_03_um, 2lis_04_p_arbpl, 2lis_04_p_arbpl_20. What i knew is, this type of data we will get from 'Purchasing Data (Schedule Line Level). 2LIS_02_ITM EKKO, EKBE,T001, T001W, EKPO, TMCLVBW, T027C, ESSR, T147K,. As when we pull BUDAT(posting date) in 2lis_02_scl it depends on the transaction key. Locate your Extractor (Datasource). Check details in below T codes: BF11- check box required for BW. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Q3: I just want to confirm that if I go with 2LIS_02_S011, these steps are not necessary. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 7 : 2LIS_13_VDITM Billing Document Item Data SD - Sales and Distribution: 8 :Hi SAP USER. According to my Knowledge, by help of BW: Transaction Key (0PROCESSKEY) we can differ PO's. 2LIS_02_SCN: Produced Activity: Confirmation of Schedule Lines: MM - Materials Management: 0FI_AP_4: Vendors: Line Items with Delta Extrcation: FI - Accounts Payable:2LIS_02_SCL - Fields for PLIWK (Supplying Plant), PLIEF (Partner Vendor) & PWLIF (Good Supplier) 344 Views. ) 3. Complete customizing, LBWE setup and Delta initialisation was performed the. Genrally BWMNG is mapped with 0CPQUAOU. For more information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. for Infosource 2lis_02_scl - 10 : MCEKET: Purchasing Document Delivery Schedule MM - Purchasing Information System: Structure 11 : MC02M_0SCLSETUP: Storage BW Setup for MC02M_OSCL Logistics - Logistics Information System (LIS) Transparent Table 12 : TMCLVBW: Transaction Key for SAP BWWe consider to use 2LIS_02_SCL to extract schedule line data but after examining the data we got, a confused result occurs. In fact, 2LIS_02_CGR is loading Confirmation with Goods Receipt from SAP tables EKBE, EKES, EKBE and EKPO. KNTTP – Account Assignment Category The account assignment category determines the account assignment data for an item, such as cost center and account number. We are executing a delta load from datasource 2LIS_02_SCL and it is. The incorrect situation consists in the following. The Posting date (BUDAT) from the 2LIS_02_SCL is being assigned to 0CALDAY with the rule type specified as Time Characteristic. Follow RSS Feed Hi all, What is the source table field name for REWRT (Invoice Value in Local Currency) in DataSource 2LIS_02_SCL, I mean how REWRT is populated. 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. BW SD MM FI 常用 数据源. 2LIS_03_BF: Goods Movements From Inventory Management: MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: Messages related to MCBO MESSAGE Description;. Now my user wants to add the following fields to the report. MM. 2LIS_02_ITM: Purchasing data (Item Level) MM - Materials Management: 4 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 5 : 2LIS_02_SCL: Purchasing data (Schedule Line Level) MM - Materials Management: 6 : 0FI_GL_4: General Ledger: Line Items with Delta Extraction FI - General Ledger. Then use the function Activate and Schedule to start the process chain according to your scheduling options. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 : 2LIS_11_VAITM: Sales Document Item Data SD - Sales and Distribution: 5 : 0FI_GL_4: General Ledger: Line Items with Delta Extraction FI - General Ledger Accounting: 6 : 2LIS_03_BX: Stock Initialization for Inventory Management MM - Materials. They also extract GR and IR. The keys of this DSO are PO Number, PO Item and Schedule Line number. 0 there is a data source called 2LIS_06_Inv which provides data from all these data sources. Users compare BW report output with SAP R/3 tcodes MCSJ and MC$4. Data sources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. Search for additional results. This is basically information relating to the delivery completed indicator, open quantity and planned delivery date or requested. 2LIS_02_SCL returns data for the purchase order on header item and schedule line level. SAP Community Network Wiki - SAP NetWeaver Business Warehouse - Step by Step Enhance your Datasource. You will find that value of "LOEKZ" of. ALIEF - Number of Deliveries. 2. This extractor was enhanced via an append structure and ABAP in the user exit. Relevancy Factor: 2. Extractor 2LIS_02_SCL --> behaviour when ELIKZ is set. Is processkey a standard across a module eg: MM and SD. If successful, 6. where this is using a standard datasource 2LIS_02_ITM and 2LIS_02_scl and i have acitvated this standard cube 0pur_c01. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. check in start routine/update/end routine for any filters. About this page This is a preview of a SAP Knowledge Base Article. (BANFN) and. I'm trying to reconcile a record produced by the 2LIS_02_SCL datasource back to the base R/3 tables. Thanks. I am extracting data from 2LIS_02_SCL. FIP Material Number 0SR_VE_INT_IV . I'm want to use some 2LIS_02* extractors (2LIS_02_HDR, 2LIS_02_ITM and 2LIS_02_SCL) to cubes 0PUR_C01 and 0PUR_C04. We are getting '0' instead of the correct quantity, but when we do full load at the end of the month we get. Reorganization for. The problem is that instead of sending over the Doc Value Amounts found in the EKBE table, SAP is doing a calculation based on the the local currency. If successful, 3. clear wa_package. All of my changes propogated; the DSOs are now write-optimized;. here give the PO numbers, specify a name for the job run and execute. BWEFFWR blank for 2lis_02_scl. 2LIS_02_ITM: Purchasing Data (Item Level) 2LIS_02_SCL: Purchasing Data (Schedule Line Level) 2LIS_02_ACC: Purchasing Data (Account Level) SAP delivers sample BEx queries on top of MultiProviders for the following areas: Procurement Value Analysis. Since I know I am working with Purchasing data those are my obvious choices. The 2LIS_02_SGR provides the GR document number and 2LIS_06_INV the IR document number. Once I do that, I am able to extract data for an info source 2LIS_02_SCL. I can create correctly the init update but I have problems with the. fields in 2LIS_02_SCL. As per the solution design, we need to enhance the 2LIS_02_SCL extractor with 3 fields from the EBAN by looking up the purchasing document. Click more to access the full version on SAP for Me (Login required). before image; #; . collective update this end with a dump with the message MESSAGE_TYPE_X. In particular every time I schedule the job for. Among the ORECRODMODE and STORNO, which is better option to be mapped with the. The issue is related to the extraction. Setting the Layout. The Select Data Source page appears. 2) Now you can selectively fill the setup tables for purchasing related datasources by the T-code OLI3BW. Both the datasource do not have Material document number (BELNR) field. This counter determines the number of deliveries based on the GR document items. (II) Click on the maintanence tab, pull the fields from communication structure to extract structure based on reporting requirement. When I check with RSA3 I've got a lot of. Technical Name. Transfer struct. Company code. 2lis_02_scn. I am loading the data form the 2LIS_02_SCL datasource to the DSO in BI. This InfoSource contains the structure to provide purchase accounting data on item level into the EDW Core Layer. delta upload. Deletion indicator not appearing in 2lis_02* extractor . 2LIS_02_SCL Issue. 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. Has searched many threads from the forum but unable to find perfect solution. 0 I've activated the extractors 2lis_02_scl and 2lis_02_itm, when I do the initalitation in the setup tables I don't see any record also if in the execution log there are 7230 documents. Department. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. Currently, when I load the Setup table for Purchase application, I don't have any record for that kind of purchase order though I have standart PO. However, before replicating to the BW on HANA system connected, I checked data in S4 via RSA3. Step 2 Goto LBWE transaction in R/3. V . 2867285-2LIS_02_SCL : extracts more schedule lines than table EKET. DSO. in 2lis_02_scl and 2lis_02_itm Data Sources. eg: and comm_structure-cppvlc <> 0. 2) can i map 0CPPVLC (BWGEO), instead of 0ORDER_val (BWEFFWR) in the transformation and in routine b/w data source and cube. AFS Elementary Field Color /AFS/BWEL_COLOR. The following jobs move the data from the outbound queue to BW. I have some strange problem in R/3. I tried to load 0PUR_C01 with 2LIS_02_SCL ( FULL method ), but in the monitoring I've got 0 record and an <b>Extraction error</b> which deals with data selection. 2lis_02_hdr. Hence there are multiple records for one PO item with different 0PROCESSKEY. They are then using the Exchange rate from the PO Header. The details are as below: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). I'm having an issue with extractor 2LIS_02_SCL whereby the quantity field WEMNG is populated incorrectly after perform initialization, below are the activities being done so far: 4) LBWE activate datasource and included field MCEKET WEMNG (Received) After performing these steps, in RSA3, the qty display in field WEMNG doesn't match. The transport went in with rc=8. Status . Hi, I think this depends on what logic u have written in your start routine. But the extractors 2lis_02_scl and 2lis_02_hdr don't load the PARVW field; and when the PARVW field is changed in a Purchasing document, the modification date is not updated. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. 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. 2LIS_02_SCL enhancement - SAP Q&A Relevancy Factor: 1. The 2 datasource aren't loading the same information. I enhanced scheduled qty (MCEKET-MENGE) and Received Qty (MCEKET-WEMNG) to 2lis_02_scl. This is regarding finding out the Extractor Logic (Fuction module ABAP logic ) for few of the standard extaractors fields in sap ecc side. We are doing a delta update. , EBELP Item and ETENR Schedule Line. 2LIS_02_SRV . but do not understand the delta behavior. Udo. I created an ODS object with the following fields as a key. ANLA, ANLB, ANLC : Segment Assets Masters. 2LIS_02_ITM and 2LIS_02_SCL. This how 2LIS_03_BF /UM. Note that if you change a purchasing document, the. But still the data source 2LIS_02_SRV will not be visible in LBWE, but is activated & will be visible in RSA3. Tables for 2LIS_02_ITM. KNTTP – Account Assignment Category. Sep 26, 2012 at 05:47 AM. Why are the setup tables not filled?Our delta queue for 2LIS_02_ITM and 2LIS_02_SCL was deleted from R3 by mistake. Strangely when we load data using delta mechanism, we are not getting the correct updated 'issued quantity' . BWA / BIA. SAP BW Datasource : 2LIS_02_SCL - Purchasing Data (Schedule Line Level). For example, by comparing the planned and actual goods issue dates, you can determine which quantities were delivered on time. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL. B. Name. enabled:true in the Search box and press Enter. DBWMNG - Delta for Purchase Order Quantity/Goods Receipt Quantity in Base Unit of Measure. cpquaou is mapped to BWMNG which is the PO quantity "not the OPEN PO. SCL_BEDAT is obviously updated in the extractor with field EKET-ETBDT which is the so called "Order Date". To have an understanding about BW DataSource 2LIS_02_SCL for deletion and un-deletion a Purchase Order Item. 1) Add the custom fields to the Communication structure (MCEKET - for Schedule lines) using the APPEND Structure in SE11. I made my changes in the development environment and transported them to QA. The system always converts the net price to the local currency and to the base unit of measure. But in BI 7. 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. You may choose to manage your own preferences. Comparing DataSource 2LIS_02_SCL to ME80FN. goods tab > invoice number field. Hence we have developed a new Info cube which needs to have data from 2LIS_02_SCL and 2LIS_02_SCL (which is already delta enabled). g for one item 001 u have quantity 90PC.