Comment . With this setting I have to take downtime in R/3. I never used 2LIS_02_SGR, but following the documentation it gives returns data related for goods receipt. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. SAP. Comp. When checking the OMJJ transaction, the 103 and 104 movement types are marked. Description . Once the setup table filling is done. 1)2LIS_03_BX : BWMNG,BWAPPLNM, BSTAUS ,BSTTYP. RemoteCube Compatibility. <Delete> Go to edit mode of a PO, select an item and click "Delete". Fill the set up tables. 2. I have a question. 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. docx), PDF File (. 2lis_02_scl. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 5. Technical name: 2LIS_12_VCITM. As you konw, When R/3 system doesn't make any transaction data, we can fill the setup table. The incorrect situation consists in the following. e. It appears that many of the key figures are updated based on logic relating to the BW Processing Key. Once the setup table filling is done. 2LIS_02_SCL returns data for the purchase order on header item and schedule line level. The data are transfered correctly (maybe!) from Extraction Queue to Delta Queue (daily, the amount of data is almost 1000 a day). From the business content, in the update rule: 2LIS_02_SCL -> 0PUR_DS03. Record count in RSA3 and PSA is different. Comparing DataSource 2LIS_02_SCL to ME80FN. Open View Browser app from the search results. I am working with 2LIS_02_SCL. At my client we implemented the PO Sch Extrc 2LIS_02_SCL and 2LIS_02_ITM. This how 2LIS_03_BF /UM. When i am trying to join with EKBE from 2LIS_02_SCL data, there is no field in 2LIS_02_SCL to differentiate between 101 and 102 records. 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). Please share your ideas on this data source setup. Based on DataSource: 2LIS_02_SCN. . But for 2LIS_02_SCL, i am not getting either 7. 2LIS_02_SCL . Symptom. Genrally BWMNG is mapped with 0CPQUAOU. When we do the reconciliation with MC$4, some. This is regarding finding out the Extractor Logic (Fuction module ABAP logic ) for few of the standard extaractors fields in sap ecc side. Why? What am i missing out do i need to do any changes before i actiavte the in-active tables in LO-Cockpit. DSO Will Not Activate after Transport with rc=8. Now, all the extractor must be zero (0). there is a routine for the PO open quantity 0BO_QTY as follows: RESULT = COMM_STRUCTURE-cpquaou * COMM_STRUCTURE-numerator / COMM_STRUCTURE-denomintr. InfoSources 2LIS_12_VCHDR , 2LIS_12_VCITM , and 2LIS_12. Also, source field Document date is being assigned to the 0ENTRY_DATE field in the target DSO. 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. If successful, 3. Note that if you change a purchasing document, the. Technical name: 2LIS_02_SCL. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW >. 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. The three others (2LIS_46_HED ; 2LIS_46_CFM ; 2LIS_46_GTM) are not showing any data : see attached picture issue. png. 5. This DSO is filled by InfoSource MM-PUR: Purchase Data Schedule Line Level (2LIS_02_SCL) (/IMO/PUR_IS12) to provide contract and scheduling agreement call-offs. process key for infosource 2LIS_02_SCL. Please do advise on the below questions. goods tab > invoice number field. Choosing any numbers 1 – 6 will populate the corresponding EXPO KZWI 1 – 6 fields. For example, by comparing the planned and actual goods issue dates, you can determine which quantities were delivered on time. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. I can create correctly the init update but I have problems with the. - 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 . Released . 2LIS_02_SCL. 2) can i map 0CPPVLC (BWGEO), instead of 0ORDER_val (BWEFFWR) in the transformation and in routine b/w data source and cube. Thank you all four you responses. We went to the Infopackage scheduler and by mistake deleted the Initialisation assuming we need a new Initialisation. Search for additional results. AFS Elementary Field Color /AFS/BWEL_COLOR. Determine Industry Sector. Then save the PO. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. Customer-Defined DataSource ® L. ATTR . 2lis_02_cgr . Ensure that this counter only counts. th einfo object may be the same but there is a big diffrence . Now when I extract this data in full load in RSA3, I get a total of 19200 records. collective update this end with a dump with the message MESSAGE_TYPE_X. Feb 04, 2011 at 01:37 AM. 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). Hence there are multiple records for one PO item with different 0PROCESSKEY. The extractor works correctly till the good Receipt and fills WEMNG and WEWRT fields correctly. 2867285-2LIS_02_SCL : extracts more schedule lines than table EKET. Technical Name. Name. the situation is that when I run delta it fetches 0 records. Thanks, John. If you click that dropdown you will find the tables for your Datasource. BW SD MM FI 数据源. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 1. 2. 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. I also know that my InfoSources for this data are 2LIS_02_HDR, 2LIS_02_ITM, and 2LIS_02_SCL. Please suggest me the ideal way to complete this task. Change the PO Qty from 32 to 40 and save the same. For more information, see the data source documentation. 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. This DataSource provides the BW with data from the Sales area and supplies the InfoSource 2AF_SD_SHP_1 with data. 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. I have some strange problem in R/3. May 21, 2012 at 04:31 AM. O transormation between the Datasource and DSO, ROCANCEL field needs to be mapped to the either the 0RECORDMODE or STORNO to identify the delta records. Please help. Thanks. Hi all! I have to initialize my BW data for the datasources: 2LIS_02_HDR 2LIS_02_ITM 2LIS_02_SCL 2LIS_02_S012 All my key figures are in "summation" mode, that means, no item should be loaded. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. I am unable to figure out why this fields is not populated. 方便各位开发顾问查询. Maintain your data source in LBWE, For this: (I) Inactivate the data source. I have a requirement to enhance the datasource 2LIS_02_SCL with some custom fields, those custom fields were directly appended in the EKET table and these fields were moved to the Right hand side under the maintenance link in LBWE. 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. , EBELP Item and ETENR Schedule Line. Kindly provide a solution for the below problem whcih i am facing with 2lis_02_itm and scl data sources. It returns also data for goods receipt and invoices if they exist. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 2LIS_13_VDKON:. 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. 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). Bei Einkaufsbelegen, die in einer anderen als der Hauswährung angelegt wurden oder zu denen Belege wie z. 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. Process overview . Situation 2. A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!Activate data source of Appl. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. SAP Community Network Wiki - SAP NetWeaver Business Warehouse - BW Setup Tables List. <Delete> Go to edit mode of a PO, select an item and click "Delete". In BW- IF ITM is feeding an ODS already in BW, create an UPDATE rule into the ODS that SCL is feeding data into for that particular field. Can you please guide me through! Thanks, Ram. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. but I need only in USD(US dollers) For these I followed the steps like thisCurrently 0PUR_C01 is coming from DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2LIS_02_HDR EKKO, EKBE,T001, EKPA. However, my delta infopackage is not picking up any new records. In the S/4HANA on-premise edition of SAP Commercial Project Management, the business object 'issue' is referred to as 'issue activity'. In 7. 2LIS_02_SCL not extracting field EKPO-LOEKZ. TBSL: Posting Keys. J_3AKVGR10. Our users are complaining, because they expect it to match up. You will find pool of objects there. After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. This is to keep data that is depending on each other consistent. In the ECC table EKET these two fields have changed for a given purchase order but the change is not added to the delta queue. V . In the above scenario, if the business doesn’t require history data, then there is no challenge since we could add the new info-cube in the existing delta info-packages. The standard purchasing info objects in BW for storing the subtotals are 0SUBTOT_OC1 –. If you select Choose Layout, you have access to all the SAP List Viewers functions. ) 3. I have a problem with Queued Delta Update Method. 2LIS_02_ITM and 2LIS_02_SCL. Hi, I am working on the Procurement area and will be setting up the 2LIS_02 extractors (HDR, ITM, SCL and ACC). 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. If the DataSources are from the LO cockpit, this push takes place either with a direct delta. 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. 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). In datasource 2LIS_02_SCL, there is only fields BWMNG - that represents quantity, BWGEO and BWGEO that represent values. 2LIS_02_SCL. MC02M_OSCL. - Normal purchasing order - BWVORG = 001. RemoteCube Compatibility. ALIEF - Number of Deliveries This counter determines the number of deliveries based on the GR document items. Apart from the sales orders, 2LIS_02_SCL will give the purchase orders based on stock order transfer. We have a standard datsource 2LIS_02_SCL for loading the Issued quantity WAMNG against PO. And below I am giving the job log details of ODS activation. in 2lis_02_scl and 2lis_02_itm Data Sources. The ODS which in our system has the 0PROCESSKEY as one of the key fields. KNTTP – Account Assignment Category The account assignment category determines the account assignment data for an item, such as cost center and account number. Enter the search text @Analytics. 0. Request or instruction from a purchasing organization to a vendor (external supplier) or a plant to deliver a certain quantity of a product or to perform certain services at a certain point in time. I have a problem with 2LIS_13_VDITM delta. Q3: I just want to confirm that if I go with 2LIS_02_S011, these steps are not necessary. Among the fields that were appended are fields EKKO-BUKRS and EKPO-LOEKZ. It would be fine if 2LIS_02_SGR provided the amounts (a left outer join of the. This extractor was enhanced via an append structure and ABAP in the user exit. MM Data Sources Tables Purchasing. 3. fields in 2LIS_02_SCL. I am still finding out which of these extractor needs to be modified. e. Locate your Extractor (Datasource). - IR document number (if there is an invoice referred to this GR) The 2LIS_02_SCL would be fine, but it does not provide the GR and IR numbers I need. 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. Transactional Data. and enhanced the datasources ITM and SCL adding one Char in RSAP0001 using user exist EXIT_SAPLRSAP_001 . I am using 2LIS_02_SCL for to fill the data into 0PUR_C01 cube. you can get the records by running the extraction of 2LIS_02_SCL in RSA3. 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. g for one item 001 u have quantity 90PC. The purchase order exists in APO in the form of an order. Help. If the target area is longer or shorter . Hi, I have activated and loaded data in datasource 2lis_02_scl. Logistic Data sources with tables. for datasources 2lis_02_hdr, 2lis_02_itm, 2lis_02_scl. 方便各位开发顾问查询. Users compare BW report output with SAP R/3 tcodes MCSJ and MC$4. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_CGR:. Save BW. Use. One of my 2LIS_02* extractor data load is failing from past few days and we fixed it by performing Initialization WITHOUT data transfer and deltas are running as expected. than the dataset, see the documentation on the ACCEPTING PADDING andCheck the Records Now Similarly check for 2LIS_02_ITM and 2LIS_02_SCL Now Check in RSA7 (ECC) Check for the Data Source 2LIS_02_HDR. 1. Load data InfoPackage. However after full loading, you notice that more schedule line records are extracted by Datasource 2LIS_02_SCL. 2. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. The Info Package which indicates that an x amount of records were transferred but not received, got a timeout and was restarted just to bring in zero records in the delta. Go to. PO delivery schedule lines are first consolidated in an ODS through data from the InfoSources Purchasing Data (Document Schedule Line Level) as of 2. Step 2 Goto LBWE transaction in R/3. There I see data only for some extractors (2LIS_46_SCL and 2LIS_46_ITM) : see attached picture issue-gtm-01. BW SD MM FI 常用 数据源. By default, either of these does not capture changes to a transaction field in VL32N > Item > foreign trade/customs tab > Invoice accomp. Method . Comparing DataSource 2LIS_02_SCN to ME80FN. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). This DataSource provides information about the header data of a purchasing document, such as vendor, purchasing organization, order currency, and so on. Status . All of my changes propogated; the DSOs are now write-optimized;. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_SGR: Produced Activity: Delivery of Schedule Lines: MM - Materials Management:. Some are transparent, some are reference, but there are one or two that stand out here. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL . So 2LIS_02_SCL gives more informations. MM. Here Loekz field related data is completely not fetching from the above data sources partial data is able to get. This is basically information relating to the delivery completed indicator, open quantity and planned delivery date or requested. Features of Extractor. If you want to update a further key figure from the InfoSource check, the key figure needs to be updated in overwrite or additive mode. AFS Grid Value. I now am trying to get publishing back on track. Unfortunately data doesn't. ZPUR_C01) and modify with any from the header that is needed. Delete the setup data (LBWG) 2. populate Goods Receipt value and Invoice Receipt. 2lis_02_s012. It depends on key mentioned for BWVORG field in transaction - Transaction Key SAP BW. I am using standard extractor 2LIS_13_VDITM and 2LIS_02_SCL. This DSO is filled by the InfoSource MM-PUR: Purchase Data Item Level (2LIS_02_ITM) (/IMO/PUR_IS11) to provide general information on the principal agreement. We are getting '0' instead of the correct quantity, but when we do full load at the end of the month we get. Requires; Object Type. Line 30 had been entered and totally delivered. 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. If successful, 4. I've done all the "tasks" for setup tables, but i don't have 0PROCESSKEY. g for one item 001 u have quantity 90PC. Now the problem is, I could see FEW records getting posted twice (duplicated) in PSA. Then use the function Activate and Schedule to start the process chain according to your scheduling options. I need a Report in Local Currency ie: USD only (US dollers), Here what I am getting in my Report is all different currencies . 2LIS_02_SCL extractor does not always fetch data from EKET table. Please also specify what is the way to find out it. LIS_ITM is meant for item level information e. Here for this Info cube from another 2lis_02_itm datasource also data is coming. Timeout type: TimeoutData, Extractor: 2LIS_02_SCL" On the screenshot from the Publisher below all tasks in the group are from SAP ERP system except SAP Extractor Group_A_002 ZBI_NEW_PILOT DELTA, which. The information in this field indicates the difference between the purchase order quantity and the goods receipt quantity in the base unit of measure. It is field-based and contains all. InfoSource: /IMO/PUR_IS12. 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). not ectract the good Invoice receipt quantity. Available from OLTP Release. MM. They also extract GR and IR. When you use service-based invoice verification (EKPO-LEBRE) the extractor 2lis_02_scl. Where in BW should be stored the data about secondary costs on purchase (acquisition) which evaluate the real price of goods? Thank You very much, AlesakWe recently got a request to setup extractor 2LIS_02_S012, which is setup to populate 0PUR_C01. I am facing following problem with above extractor. 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. I look at SE11 for ' MC02M_0HDRSETUP ' and table contents gives 0 records. I am using Key figure BWGEO BW:CValLocCrcy & BWGEOO BW: CValOrdCrcy with summation. Online Help Keyboard Shortcuts Feed Builder What’s newEXTACTOR 2LIS_02_SCL DELTA ERROR REMNG REWRT /WEMNG /WEWRT. Purchasing Data (Document Schedule Line Level) Technical name: 2LIS_02_SCL. J_3ADEPM. before image; #; . LIS_ITM is meant for item level information e. I would like to hear from you on following issue. Check details in below T codes: BF11- check box required for BW. failing. Extraction job in R3 is unable to extract any data, so it . Strangely when we load data using delta mechanism, we are not getting the correct updated 'issued quantity' . MC11V_0SSL: Extraction MD Sales: Order Delivery for DataSource 2LIS_11_V_SSL. "MCEX_UPDATE_02_V1" "(FORM)", or declared in the procedure's RAISING clause. Assuming, you would like to use the new method, the process would be like this: RSA5 u2013 Source system; activate these datasources 2LIS_02_ITM and 2LIS_02_SCL. dataextraction. AFS 3. Problem: We are using the 2LIS_02_SCL to get our purchasing order data. Because it is possible to post a goods receipt with a posting date (EKBE-BUDAT) that lies before or after the document creation date (EKBE-CPUDT), the creation date of the goods receipt document (GR document) plays an important role in the quantity. Technical Data. BW SD MM FI 常用 数据源. In R/3- Enhance the SCL extractor by adding the ZZ. Also processkey 007 is missing from 2LIS_02_ITM. BW/BI Accelarator is a tool that improves the performance of BW 7. clear wa_package. SAP Knowledge Base Article - Preview. Your LIS_SCl will contain the schedule line information that is if somebody wants schedule date wise e. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. I had a requirement to make two Purchasing DSOs (2LIS_02_ITM & 2LIS_02_SCL based) write-optimized. 2. 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. A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!Hello, gurus. 及其r3数据 源:2lis_02_s012,2lis_02_itm,2lis_02_scl. Step 2: In the table TCDOB put the table name in TABNAME field, you will get some name in OBJECT. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. 2016-01-05 02:11:55 NOT all Rows are received yet: 2LIS_02_SCL. This DataSource provides the BW with data from the Sales area and supplies the InfoSource 2AF_SD_SHP_1 with data. Oct 18, 2007 at 09:39 AM. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL. The following has all been done. I used rsa3 to validate these 2 fields against EKET table, the Received Qty is not correct. 2lis_03_bf . in both the bw systems. 2) Now you can selectively fill the setup tables for purchasing related datasources by the T-code OLI3BW. 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. You have the option to use the old and new method. BUT. Choose New Data Connection. We have extracted purchasing data using 2LIS_02_SCL and 2LIS_02_ITM datasources. Kindly provide a solution for the below problem whcih i am facing with 2lis_02_itm and scl data sources. When I extract this data to PSA ONLY, the count is 19191. The data records for. I am using logistick Cockpit Extraction and in particular 2LIS 02 ITM. 2) Now you can selectively fill the setup tables for purchasing related datasources by the T-code OLI3BW. Apparently these two fields are NOT updated in BW from a delta load. g. 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. If the information relates to a goods receipt or an invoice, the field is filled with the. In the transformation start routine, I could see alogic which is barring some records to DSO. KNTTP – Account Assignment Category The account assignment category determines the account assignment data for an item, such as cost center and account number. I have done with Initialization of 2LIS_02_SCL and now trying to run delta for 2LIS_02_SCL. and choose the industry sector "Standard (Core)". 0SUP_PLANT (Supplying Plant) - populated from Structure Field Name. Follow the below steps to get the lost delta, will be useful for any loads. Likewise proceed with all the extractor. e. The information under these fields are dependent from the information of field BWVORG (BW transaction key). Allocation – Confirmation with Schedule Line. adjusts the quantities to give the true 'open/closed' qty after GR. Once I do that, I am able to extract data for an info source 2LIS_02_SCL. I am enhancing MC02M_SCL structure for purchasing 2lis_02_scl, I added the fields MENGE (quantity) posting date (BUDAT) and transaction value type VGABE. 以下是SAP ECC中各主要数据源与描述. If successful, 5. 2 LIS_02_HDR (Purchasing Document Header Level Data) 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. The requirement of mine is to show the End-User Total Number of PO's ,Open POs and Closed PO's for Current and Previous Months. Best Answer. I add the following fields REMNG /REWRT/ WEMNG /WEWRT in the LO cockpit. To confirm the delta queue, Check the SMQ1 transaction code if any Queue Name start with MCEX** or Destination BWCLNT*** (i. Hi All, Can you please share your experience on the 2LIS_02_ACC data source setup.