2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_SGR: Produced Activity: Delivery of Schedule Lines: MM - Materials Management:. FIP Material Number 0SR_VE_INT_IV . i need to. If successful, 3. Feb 04, 2011 at 01:37 AM. Visit SAP Support Portal's SAP Notes and KBA Search. Strangely when we load data using delta mechanism, we are not getting the correct updated 'issued quantity' . You will find pool of objects there. fields in 2LIS_02_SCL. Purchasing 2LIS_02_SCN MC02M_0SCNSETUP BW-Rebuild for. privacy statement, for purposes that may include site operation, analytics, enhanced user experience, or advertising. If you wish to use the new extraction method, you must make certain settings in Customizing for the OLTP system. I enhanced scheduled qty (MCEKET-MENGE) and Received Qty (MCEKET-WEMNG) to 2lis_02_scl. LO Data Sources With Tables - Free download as Word Doc (. Delete content of ODS/CUBE. Online Help Keyboard Shortcuts Feed Builder What’s newEXTACTOR 2LIS_02_SCL DELTA ERROR REMNG REWRT /WEMNG /WEWRT. Purchase Order Schedule lines (2LIS_02_SCL) Purchase order Allocation Confirmation and Schedule Line (2LIS_02_SCN) Purchase Orders Account level (2LIS_02_ACC) Inventory Management Goods movements (2LIS_03_BF) Inventory Management Revaluations (2LIS_03_UM)The standard content InfoCube 0PUR_C01 is sourced by the 2LIS_02_ITM and 2LIS_02_SCL DataSources. 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. On the AWS Supply Chain dashboard, on the left navigation pane, choose Data Lake and then choose Connections. Follow RSS Feed Hi all, I want to find out the Table Field names for the for the below InfoObjects of DataSource 2LIS_02_SCL (Purchasing Schedule Line Items): 1. One system it is showing 42 Records Transferred and 8 Added Record in DSO level, and another system is showing 14. KNTTP – Account Assignment Category The account assignment category determines the account assignment data for an item, such as cost center and account number. We need to delete and fill setup table for 2LIS_02_SCL because we have changed a rule in Trasformation so we need to reload some data in our ODS (all KF are in Overwrite). 2LIS_02_ITM EKKO, EKBE,T001, T001W, EKPO, TMCLVBW, T027C, ESSR, T147K,. "6. With this setting I have to take downtime in R/3. For one PO (Purchasing Order) there're 1 record in schedule line table EKET. Released . This InfoSource contains the quantity that was delivered for each schedule line in a delivery item. 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. Expand in hierarchy structure node Logistics application – 12: LE Shipping BW – Extract structures. Fill the set up tables. There I see data only for some extractors (2LIS_46_SCL and 2LIS_46_ITM) : see attached picture issue-gtm-01. Comparing DataSource. 7. Please help me. 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. 2LIS_02_SCL datasource will give the GR values from EKBE table by considering the purchase documents from EKKO table for respective vendor. However after full loading, you notice that more schedule line records are extracted by Datasource 2LIS_02_SCL. I am working with 2LIS_02_SCL. e. Hence there are multiple records for one PO item with different 0PROCESSKEY. "MCEX_UPDATE_02_V1" "(FORM)", or declared in the procedure's RAISING clause. Use. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW >. 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. ALIEF - Number of Deliveries. 02 in LBWE. <Delete> Go to edit mode of a PO, select an item and click "Delete". For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 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. It mentions BWVORG assumes a value based on the "purchase item type, processed document and purchasing order type". Reason and PrerequisitesIn the BW customizing is possible to maintain the description of thetransaction key for transferring Logistics movement data to BW system,field BWVORG in purchasing data sources, but. Maintain your data source in LBWE, For this: (I) Inactivate the data source. This extractor was enhanced via an append structure and ABAP in the user exit. 0AF_DEPTM. The additional field is not filled when you check the delivered data on BW side. 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. Setting the Layout. e, 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. Follow. Please do advise on the below questions. doc / . g for one item 001 u have quantity 90PC. We enhanced one filed for 2LIS_02_SCL but it seems it is sending delta for this filed even though there is no change for it in purchasing order. 2) Now you can selectively fill the setup tables for purchasing related datasources by the T-code OLI3BW. I will analyse notes 459517, 728687, 722339 y 869628. Choose. MESSAGE x097(sy), SY097, SY 097, GUID, assigned twice, RSC1_DIAGNOSIS, RSA1QMON, RSA7, double, qRFC, extractors, DataSources, 2LIS_02_ITM, 2LIS_02_SCL, 2LIS_03_BF. 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. . Overlapping check with archived data areas for InfoProvider ZP2_PSCL. 2. ) 2LIS_02_SCL & 2. It will send a change like below: Record Mode; EVERS; QTY. Please find the below extractors and its fields . 2LIS_02_SCL and _ITM Purchasing Cube 0PUR_C01. here give the PO numbers, specify a name for the job run and execute. The Data Lake page appears. It is field-based and contains all. 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. We are executing a delta load from datasource 2LIS_02_SCL and it is. AFS Grid Value. 2) can i map 0CPPVLC (BWGEO), instead of 0ORDER_val (BWEFFWR) in the transformation and in routine b/w data source and cube. includes tables like ekko/ekpo/ekbe etc. Some are transparent, some are reference, but there are one or two that stand out here. SAP Knowledge Base Article - Preview. The information under these fields are dependent from the information of field BWVORG (BW transaction key). in 2lis_02_scl and 2lis_02_itm Data Sources. delta upload. But it is fetching 0 data with green status. The 2LIS_02_SGR provides the GR document number and 2LIS_06_INV the IR document number. - Stock transport order - BWVORG = 011. Thanks, Bobby. Former Member. I can create correctly the init update but I have problems with the. Delivery Item . Kindly provide a solution for the below problem whcih i am facing with 2lis_02_itm and scl data sources. The system only calculates this delta if a purchase order item is completed. 2LIS_02_HDR Purchasing data (Header Level) MM - Materials Management: 18 : 2LIS_12_VCITM Delivery Item data: SD - Sales and Distribution: 19 : 0HR_PY_1Comparing DataSource 2LIS_02_SCN to ME80FN. Application Component. Line 40 had been entered. The counted number depends on how often a material appears in a GR document. This field determines whether these values are from a purchasing order, goods receipt or. The data of this extractor needs to be used to measure a supplier service sevel based upon single schedule lines. Hello everybody, I am using datasource 2LIS_02_SCL to extract data into BW. MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. RemoteCube Compatibility. In combination with the InfoSources Purchasing Data (Document Header Level) and Purchasing Data (Document Item Level), the InfoSource Purchasing Data (Document Schedule Line Level) supplies the basic data for analyses of purchasing documents. My predecessor actually changed the standard definition of this. 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. MC11V_0SCL: Extraction SD Sales BW: Allocation Schedule Line for DataSource 2LIS_11_V_SCL. . 26. Comparing DataSource. Instead it still comes across with process key '02' which is for standard goods receipt (movement type 101). A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!Activate data source of Appl. Why are the setup tables not filled?Our delta queue for 2LIS_02_ITM and 2LIS_02_SCL was deleted from R3 by mistake. Now we realize that processkeys 010 are missing but 2LIS_02_ITM catches these. Go to Maintainance. 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. 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. I have a problem with Queued Delta Update Method. I am currently extracting PO Schedule Line Data from using 2lis_02_scl data source and I see there is a mismatch between ERP and BW regarding the Goods Receipt Quantity (movement type 103 is also included in BW). 2LIS_02_SCL extractor does not always fetch data from EKET table. Search for additional results. For more information, refer to the. Dear Gurus, I have a requirement to extract Invoice Recipt Document number & Invoice date for every purchase order into BW. 2LIS_02_SCN: Produced Activity: Confirmation of Schedule Lines: MM - Materials Management: 2LIS_11_VAITM: Sales Document Item Data: SD - Sales and Distribution:Conventional method: Purchasing (2LIS_02_S012) New method: Purchasing Data (Document Item Level) (2LIS_02_ITM) and Purchasing Data (Document Schedule Line Level) (2LIS_02_SCL) Note. BW SD MM FI 数据源. Reorganization for. Transaction LBWQ in ECC: MCEX02. Then save the PO. 2LIS_02_SCL. Billing Document Item Data SD -Sales and Distribution. 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. We have historical data for 2LIS_02_SCL loaded in PSA. The problem is when user creates PO and that is loaded to BW, the next day he changes the same PO (like G/L account change. So 2LIS_02_SCL gives more informations. 'MATERIAL_ATTR,MAT_SALES_ATTR,2LIS_02_SCL,2LIS_03_BF,2LIS_11_VAITM,2LIS_11_VASCL,2LIS_13_VDITM. 2LIS_02_SCL EKKO, EKBE,T001, T001W, EKET, EKPA. The field we enhanced is EKPO-EVERS. In transactions "RSA1" has gone to a bookmark "DataSources", has selected a datasource "2LIS_02_SCL" and has chosen from the contextual menu "Manage". 方便各位开发顾问查询. MCEX03. A drop down list on “Su Tot” reveals a list of assignment options. If you select Choose Layout, you have access to all the SAP List Viewers functions. not ectract the good Invoice receipt quantity. - Purchase order: which datasource do you recommend to implement? 2LIS_02_SCL, 2LIS_02_ITM? which are the differences?th einfo object may be the same but there is a big diffrence . AFS 3. "Document data restriction" when filling setup table. Purchase related data source 2lis_02_scl datasource chain is failuring from last 5 days due to incorrect data loaded in PSA on 7/04/2012. I have a problem with 2LIS_13_VDITM delta. If the information in this field relates to an event in the purchase order, the field is filled with the posting date of the purchase order. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Follow the below steps to get the lost delta, will be useful for any loads. DELETE TABLE SOURCE_PACKAGE from wa_package. We are using two PO extrctors 2LIS_02_ITM & 2LIS_02_SCL to load data, both are working fine. Step two: Delete delta entries in RSA7. I would like to hear from you on following issue. Released . When I went to look at this, I see that 2LIS_02_S012 is listed as a conventional method and that using 2lis_02_ITM, 02_LIS_02_SCL is the new method. This how 2LIS_03_BF /UM. For purchasing documents that were created in a currency other than the local currency, or to which documents such as invoices were posted in a different currency; The contents of this field specifies the. Reason: In customizing cockpit, tcode LBWE, the following EVENTS can be found for application 02: 02: Purchasing -> extract structure MC02M_0SCL . The field 2lis_02_ITM-AKTWE give the good GR Quantity for services but do. According to my Knowledge, by help of BW: Transaction Key (0PROCESSKEY) we can differ PO's. 2LIS_02_SCL Issue. In 2LIS_02_SCL i have 0CPPVLC (BWGEO), 0CPPVOC (BWGEOO), 0ORDER_val (BWEFFWR). ekpo -meins . I was wondering if I can extract data using datasource 2LIS_02_SCL and keep key figures in overwrite mode so that I don't require. 0B (2LIS_02_SCL) and Offsetting Confirmation and Goods Receipt (2LIS_02_SGR). 2016-01-05 02:12:57 NOT all Rows are received yet: 2LIS_02_SCL I did Enhance 2LIS_02_SCL with Material doc and Item number from EKBE. g we have in Item 001 quanity 90PC, in Schedule line it will be schedule line wise that is. Load data InfoPackage. From this data source data is storing in two data targets 1. Please help me. The problem is when user creates PO and that is loaded to BW, the next day he changes the same PO (like G/L account change. All the Key figures in datasource are getting populated , but BWEFFWR (order value) is not getting populated. You will find that value of "LOEKZ" of. apart from process key is there any. 0 Flow or 3. 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 :. PSA in BW. 0SUP_PLANT (Supplying Plant) - populated from Structure Field Name. However after full loading, you notice. 2LIS_02_SCL. Extractor 2LIS_02_SCL --> behaviour when ELIKZ is set. but I need only in USD(US dollers) For these I followed the steps like thisLBWQ entires not loaded to RSA7 after RMBWV302 run - 2LIS_02_SCL ok to ITM. I tried to install it separately from BI Content but could not find transformation or transfer rule related to Cube 0PUR_C01. Check the PO in ME23n for Order qty. My client here does not use schedule lines. You can check the data from the DataSource 2LIS_02_SCL in last two views mentioned. g for one item 001 u have quantity 90PC. BWEFFWR blank for 2lis_02_scl. FAQ: Setup table filling with 2LIS* extractors. Department. 2016-01-05 02:11:55 NOT all Rows are received yet: 2LIS_02_SCL. There r 2 ways to get this data. I have to use two info sources called 2LIS_02_SCL and 2LIS_02_SGR in order to populate data in the cube. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). - Process Key 001:PO. Open View Browser app from the search results. Hi Fabio, No You cannot do a setup for 2LIS_02_ITM only, You can only do a setup for the whole 2LIS_02. Thanks for the advice. Step 2 : Activate and transfer the Application Component Hierarchy(One Time Activity in the project). Locate your Extractor (Datasource). For e. The following delta update is supported for this DataStore object: - Delta Update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp) - Data Source: 2LIS_11_VAITM. Difference Between 2lis_02_itm & 2lis_02_scl. I need to add some Z custom fields in BW datasource 2LIS_02_ITM which we are doingby appending in structure MC02M_0ITM. 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. Data Modeling. RemoteCube Compatibility. This counter determines the number of deliveries based on the GR document items. so I add field CHARG into that datasource. When I extaract data, I get 2 records. When i investigated using RSA3 extraction for 2LIS_02_SCL and singled out the problamatic PO i found that. The incorrect situation consists in the following. Note 886716 - Deleted item not reversed in BW2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 5. 2) Now you can selectively fill the setup tables for purchasing related datasources by the T-code OLI3BW. and he has managed to laod data using full upload without. When checking the OMJJ transaction, the 103 and 104 movement types are marked. Hi, I think this depends on what logic u have written in your start routine. I have a 5 records in PSA for a purchase order where total. Now my user wants to add the following fields to the report. 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. 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 counted number depends on how often a material appears in a GR document. As per the BI content online documentation for an info source 2LIS_02_SCL, Set up table for purchasing application needs to be recreated. . 3. 2lis_03_bf . For more information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. We have a reporting requirement to merge 2LIS_02_ITM, 2LIS_02_SCL, 2LIS_03_BF and 0FI_GL_4 to report on Purchasing information, which includes POs, GRs, and Invoices. Hi Amit, Refresh your BI system first and you will find your Datasource replicate the Datasource, soon after you replicate it will take to you to BI Content there you have to active the related objects as desired for 2lis_02_SCL,then your Datasource is replicated successfully and it will appear in u201CDu201D Version. AFS 3. It appears that many of the key figures are updated based on logic relating to the BW Processing Key. I have some strange problem in R/3. Is there any standard solution to extract. TRAN . 2LIS_06_INV: Extraction of Invoice Verification Data into BWThis DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) (2LIS_02_SCL). Sep 26, 2012 at 05:47 AM. load brings in goods receipt history and a starting GR $-value if quantities are partially received (0CPPVLC/0CPPVOC), and the 2LIS_02_SGR init. when checked the data by RSA3 , I found the system generated mass data(2400 records) . - Cross company order -. Is there any standard solution to extract. The outbound queue is filled for the following queues in the. I now am trying to get publishing back on track. Kindly suggest any Solution. LIS_ITM is meant for item level information e. SAP. 1. Why are the setup tables not filled?The data is not updated into the upur_c01 cube . 0. Delta Update. To have an understanding about BW DataSource 2LIS_02_SCL for deletion and un-deletion a Purchase Order Item. V . result =. in any of the tables. For example, by comparing the planned and actual goods issue dates, you can determine which quantities were delivered on time. 1 Answer. The following has all been done. Process overview . 2lis_02_cgr . 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. oss note 353042-Howto: Activate transaction key (PROCESSKEY) may also useful. SAP Knowledge Base Article - Preview. Once I do that, I am able to extract data for an info source 2LIS_02_SCL. goods tab > invoice number field. 2lis_02_scl and 2lis_02_itm - SAP Q&A Relevancy Factor: 1. One or more purchasing documents or items are not extracted either by a full load or a delta loads using some of the following DataSources: 2LIS_02_ACC, 2LIS_02_CGR, 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL, 2LIS_02_SCN, 2LIS_02_SGR. This's also valid to other PUSH datasource. This is to keep data that is depending on each other consistent. Ensure that this counter only counts. Hi, I have activated and loaded data in datasource 2lis_02_scl. But when we have an Invoice Receipt the 2lis_02_scl puts WEMNG and WERT field blank while REMNG and REWRT are populated correctly. 1. Hope it helps. 1)2LIS_03_BX : BWMNG,BWAPPLNM, BSTAUS ,BSTTYP. Is processkey a standard across a module eg: MM and SD. I went on with the assumption that SCL will capture all events that ITM captures except for Quotations and Contracts (Which my. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) ( 2LIS_02_SCL ). A problem or project situation that affects project goals. You may choose to manage your own preferences. ALIEF - Number of Deliveries This counter determines the number of deliveries based on the GR document items. I has chosen required request and has pressed button. The other datasource 2LIS_02_SGR is loading the Schedule Line with Goods Receipt from SAP tables EKET, EKBE and EKPO. M3305, M3 305, 2LIS_02_SCL, the article does not exist, 2LIS_03_BF , KBA , BW-BCT-MM-PUR , BW only - Purchase , BW-BCT-MM-IM , BW only - Inventory Management , BW-BCT-LO-LIS , BW only - Logistics Information System , BW-BCT-ISR-LOG , BW only - Logistic , How To 2lis_02_scl. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 7 : 2LIS_11_VAITM: Sales Document Item Data SD - Sales and Distribution: 8 : 0FI_GL_4: General Ledger: Line Items with Delta Extraction FI - General Ledger Accounting: 9 : 2LIS_03_BX: Stock Initialization for Inventory Management MM - Materials. Industry key is also set and application component is also populating. when i check in rsa3 the data is correct. I am activating structure. populate Goods Receipt value and Invoice Receipt. DBWMNG - Delta for Purchase Order Quantity/Goods Receipt Quantity in Base Unit of Measure. 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). We make use of extractor 2LIS_02_SCL. However, InfoCube for Purchasing ( 0PUR_C01) is already active in the system and delta are being loaded into it on a regular. The Select Data Source page appears. Technical Name. here give the PO numbers, specify a name for the job run and execute. is cancelled. KNTTP – Account Assignment Category The account assignment category determines the account assignment data for an item, such as cost center and account number. Application Component. But these datasource read data from EKKO,. Thanks. Why? What am i missing out do i need to do any changes before i actiavte the in-active tables in LO-Cockpit. DSO. Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04. 2lis_02_itm . Status . I created a PO with Qty 100 on 03/28/2007 and perfroemd GR on the same day for Qty of 25. Pls reply needed urgent,i'm. 2. 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. Inventory Controlling (application 03): 2LIS_03_BX. <Delete> Go to edit mode of a PO, select an item and click "Delete". there will be a second record in 2LIS_02_SCL. Enter the search text @Analytics. Technical name: 2LIS_02_SGR. 0 there is a data source called 2LIS_06_Inv which provides data from all these data sources. In the migrated Transformation between InfoSource 2LIS_02_ITM and DSO ZPUR_O01 (Position) I have two rule groups. When we do the reconciliation with MC$4, some. The counted number depends on how often a material appears in a GR document. ENDLOOP. - Process Key 002:GR. For more information, see the data source documentation. In other words, you can change the existing layout (such as add or hide fields and columns, change the sort sequence, add subtotals, set filters), save the. Data sources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. 2) Include these fields in the Extract structure in LBWE (Maintain Extract structure) 3) Implement the User exit called: LEINS001 - Statistics update - purchasing documents. I have a question. If you need reporting characteristics from the Purchase Order header data (2LIS_02_HDR), you can copy the 0PUR_C01 InfoCube into a custom name (e. I used rsa3 to validate these 2 fields against EKET table, the Received Qty is not correct. do not extract the good Invoice receipt quantity for each purchase order. We have a standard datsource 2LIS_02_SCL for loading the Issued quantity WAMNG against PO. MC11V_0SSL: Extraction MD Sales: Order Delivery for DataSource 2LIS_11_V_SSL. No. 2. 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. Load data InfoPackage 2LIS_02_SCL_INIT_R3. Purchasing Data (Document Schedule Line Level) Technical name: 2LIS_02_SCL. In 7. pdf), Text File (. I have loaded data into 0PUR_DS03 from datasource 2LIS_02_SCL , I have done the Initiail load successfully and also the delta load successfully (receive the new data into 0PUR_DS03) >> It's OK. 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 7. RSS Feed. I am using 2LIS_02_SCL for to fill the data into 0PUR_C01 cube. check step by step. I am extracting purchasing data into BW using datasource 2LIS_02_SCL into ODS 0PUR_DS03. 但是系统字段：交货单号（ ekbe-belnr ），参考凭证号（ekbe-xblnr ）没有。如果不做增强， 在其它数据源上是否有这二个字段？我找了采购，销售的都没有这二个字段，可能我还没有找对，麻烦各位高人帮指点。 谢谢. As much as I understand the key fields which I should be using are EBELN Purchasing Doc. Help.