InfoSource. The information under these fields are dependent from the information of field BWVORG (BW transaction key). 02 in LBWE. Determine Industry Sector. It contained the delta queues as. BWEFFWR blank for 2lis_02_scl. Released . goods tab > invoice number field. Comparing DataSource. infoobject are overwritten in the ODS. Help. ekbe -wrbtr . . The counted number depends on how often a material appears in a GR document. We are doing a delta update. And one question concerning purchase data. When i have GR reversal , Movement Type 102. You will find that value of "LOEKZ" of. Comparing DataSource. Allocation - Schedule Line with Goods Receipt. 2LIS_03_BF. RSS Feed. 0AF_CGR10. Go to Maintainance. V . 2) can i map 0CPPVLC (BWGEO), instead of 0ORDER_val (BWEFFWR) in the transformation and in routine b/w data source and cube. DSO Will Not Activate after Transport with rc=8. Settings: Purchasing. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. I'm very familiar with delta loading process (and complete setup) for the logistics datasources like 2LIS_02_HDR, 2LIS_02_ITM and 2LIS_02_SCL. in both the bw systems. The keys of this DSO are PO Number, PO Item and Schedule Line number. 2lis_02_s011. The other datasource 2LIS_02_SGR is loading the Schedule Line with Goods Receipt from SAP tables EKET, EKBE and EKPO. 但是系统字段：交货单号（ ekbe-belnr ），参考凭证号（ekbe-xblnr ）没有。如果不做增强， 在其它数据源上是否有这二个字段？我找了采购，销售的都没有这二个字段，可能我还没有找对，麻烦各位高人帮指点。 谢谢. Feb 04, 2011 at 01:37 AM. 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). Our users are complaining, because they expect it to match up. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. BUDAT – Posting Date. Step three:. 2. Step 001 started (program RSODSACT1, variant &0000000060772, user ID U6X9539) Activation is running: Data target ZP2_PSCL, from 1,572,117 to 1,572,117. The process chain supports SAP R/3 standard systems as of Release 4. The subtotal amounts are extracted in PO currency. DataSource 2LIS_02_SCL returns value zero for enhanced field MENGE (Scheduled Qty) for some records. Explanation of Note 578471 - Deleted positions in BW and statistics . 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. So 2LIS_02_SCL gives more informations. 2. This how 2LIS_03_BF /UM. In the SAP S/4HANA Cloud system, choose the App Finder and search for the View Browser app. Attached is the flow i installed. 2lis_02_scl and 2lis_02_itm - SAP Q&A Relevancy Factor: 1. Type of DataSource. Specifically I am looking at the BWVORG field. <i>Note : I do no selection in my infopackage. Overlapping check with archived data areas for InfoProvider ZP2_PSCL. If any entries are available then trigger the equivalent Info. Records Transferred and 8 Added Record in. g. Difference Between 2lis_02_itm & 2lis_02_scl. includes tables like ekko/ekpo/ekbe etc. Search for additional results. Is processkey a standard across a module eg: MM and SD. To have an understanding about BW DataSource 2LIS_02_SCL for deletion and un-deletion a Purchase Order Item. Comparing DataSource 2LIS_02_SCL to ME80FN. 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. Best Answer. This extractor was enhanced via an append structure and ABAP in the user exit. Deletion indicator not appearing in 2lis_02* extractor . 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. 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. 2LIS_02_SCL. 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 :. Job for collective update stopped (LBWE) 4. However, my delta infopackage is not picking up any new records. i. Save BW. Delete the setup data (LBWG) 2. 2LIS_13_VDITM. Also processkey 007 is missing from 2LIS_02_ITM. 2016-01-05 04:11:47 NOT all Rows are received yet: 2LIS_02_SCL. The extractor 2lis_02_scl is based in the tables EKET, EKKO and EKPO is possible to add a field from other table? I tryied to enhancement the extractor but is not possible. 1. If you wish to use the new extraction method, you must make certain settings in Customizing for the OLTP system. Kindly provide a solution for the below problem whcih i am facing with 2lis_02_itm and scl data sources. 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. RSS Feed. collective update this end with a dump with the message MESSAGE_TYPE_X. The data are transfered correctly (maybe!) from Extraction Queue to Delta Queue (daily, the amount of data is almost 1000 a day). 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). All the Key figures in datasource are getting populated , but BWEFFWR (order value) is not getting populated. I am working with 2LIS_02_SCL. There is a standard SAP DSO 0PUR_DS03 which is getting data from 2LIS_02_SCL. Line 40 had been entered. We make use of extractor 2LIS_02_SCL. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. MM. Hope it helps. 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. The counted number depends on how often a material appears in a GR document. 5. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. AFS 3. Thanks for the advice. Released . TBSL: Posting Keys. Data sources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. DataSource 2LIS_02_SCL was enhanced by field WAMNG (PO item issued queantity), but it is not updated by delta load (value of the field is 0). DBWMNG - Delta for Purchase Order Quantity/Goods Receipt Quantity in Base Unit of Measure. J_3ASIZE. Enter t-code : RSA9. When i investigated using RSA3 extraction for 2LIS_02_SCL and singled out the problamatic PO i found that. Technical Data. When i execute the extractor in RSA3 the data is populated, If any standard field is changed then it is. 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. O I am getting 5 Line entries of this material Hence if the original P. BW SD MM FI 常用 数据源. This DataSource provides the BW with data from the Sales area and supplies the InfoSource 2AF_SD_SHP_1 with data. Problem: We are using the 2LIS_02_SCL to get our purchasing order data. 0SUP_PLANT (Supplying Plant) - populated from Structure Field Name. 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. As when we pull BUDAT(posting date) in 2lis_02_scl it depends on the transaction key. 2lis_02_itm . "6. I never used 2LIS_02_SGR, but following the documentation it gives returns data related for goods receipt. - Cross company order -. 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. Open View Browser app from the search results. If successful, 4. This is regarding finding out the Extractor Logic (Fuction module ABAP logic ) for few of the standard extaractors fields in sap ecc side. Make sure at least one of the below data sources belonging to purchasing application is activated in transaction LBWE, 2lis_02_acc / 2lis_02_hdr / 2lis_02_itm / 2lis_02_scl. Extraction job in R3 is unable to extract any data, so it . Step 1: Get the name of tables affected by the lost delta data source. If the target area is longer or shorter . If they don't solve delta queue I'll report to SAP. KNTTP – Account Assignment Category The account assignment category determines the account assignment data for an item, such as cost center and account number. Load data InfoPackage. Comparing DataSource 2LIS_02_SCN to ME80FN. Change the Standard variant to Released Views variant. 0 there is a data source called 2LIS_06_Inv which provides data from all these data sources. This counter determines the number of deliveries based on the GR document items. 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. You can use this InfoSource to evaluate delivery services. cpquaou is mapped to BWMNG which is the PO quantity "not the OPEN PO. Is 0PUR_C01 is the correct cube to get Outstanding PO? or there is some other process involved? Anything we missed out? How are the filtering/restrictions should be done to get all the Incomplete POs? Many thanks, VinceLBWQ entires not loaded to RSA7 after RMBWV302 run - 2LIS_02_SCL ok to ITM. 2) can i map 0CPPVLC (BWGEO), instead of 0ORDER_val (BWEFFWR) in the transformation and in routine b/w data source and cube. RemoteCube Compatibility. Hi, It is calculated through Function module. I need to load data into purchasing data cube (0PUR_C01) from two standard data sources: 2LIS_02_ITM and 2LIS_02_SCL. Marco. Q3: I just want to confirm that if I go with 2LIS_02_S011, these steps are not necessary. 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. ODQMON – 2lis_02_itm – Init with data transfer. 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. apart from process key is there any. Hi, I am working on the Procurement area and will be setting up the 2LIS_02 extractors (HDR, ITM, SCL and ACC). I am using the datasource 2LIS_02_SCL for Purchasing reports and this extractor has the 'Delivery Completed Indicator'[ELIKZ] which is mapped to 0COMPL_DEL in BW. delta upload. the situation is that when I run delta it fetches 0 records. if you put EKET then it brings up. The three others (2LIS_46_HED ; 2LIS_46_CFM ; 2LIS_46_GTM) are not showing any data : see attached picture issue. 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. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). From the business content, in the update rule: 2LIS_02_SCL -> 0PUR_DS03. During the initial load, everything comes along fine all the way to PSA. 以下是SAP ECC中各主要数据源与描述. in 2lis_02_scl and 2lis_02_itm Data Sources. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW >. The field is BADAT [Requisition (Request) Date]. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). if anyone knows tcodes for runinng the set uptable to each data source separatley. then check in data target. txt) or read online for free. ) 3. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 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. 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). 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. 2016-01-05 04:11:48 Err Id: 17. . missing, lost, loss, 2lis, queue, delta, aim, aimd, abr, addd, newd, 2lis_02_acc, 2lis_02_cgr, 2lis_02_hdr, 2lis_02_itm, 2lis_02_scl, 2lis_02_scn, 2lis_02_sgr, 2lis. 2) Now you can selectively fill the setup tables for purchasing related datasources by the T-code OLI3BW. for datasources 2lis_02_hdr, 2lis_02_itm, 2lis_02_scl. You will find pool of objects there. 2016-01-05 02:12:26 NOT all Rows are received yet: 2LIS_02_SCL. Hi, I have activated and loaded data in datasource 2lis_02_scl. Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04. Some key figures in the data source need to be updated in an additive process. 2LIS_02_SCL. 0 Flow or 3. 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 7. 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. 2LIS_02_SCL and _ITM Purchasing Cube 0PUR_C01. check in start routine/update/end routine for any filters. is cancelled. VRTKZ – Distribution Indicator for Multiple Account. In the transfer rule, there is a coding to check on process key in 2LIS_02_SCL. load brings in goods receipt history and a starting GR $-value if quantities are partially received (0CPPVLC/0CPPVOC), and the 2LIS_02_SGR init. Demo - Generate and Extract delta data . 2LIS_03_UM. I have thought to create a new ODS to upload information from this DS 2LIS_02_SCL, and fill data in two steps: Infopackage A: Full Update. Udo. your BW System name). I don' t understand because there are many records in EKPO and EKET for STO (document range. 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. dataextraction. Please share your ideas on this data source setup. This field determines whether these values are from a purchasing order, goods receipt or an invoice. I will analyse notes 459517, 728687, 722339 y 869628. This InfoSource contains the quantity that was delivered for each schedule line in a delivery item. This DataSource provides information about the header data of a purchasing document, such as vendor, purchasing organization, order currency, and so on. Please find the below extractors and its fields . We deleted the inbound queues for 11. when checked the data by RSA3 , I found the system generated mass data(2400 records) . Status . We are getting '0' instead of the correct quantity, but when we do full load at the end of the month we get. Technical Name. 2LIS_02_ITM and 2LIS_02_SCL. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL . J_3ADEPM. Technically, it is always possible to expose a standard SAP DataSource for the ODP-SAP replication by maintaining a corresponding entry in table ROOSATTR in the relevant source system with OLTPSOURCE = <Technical Name of DataSource> and EXPOSE_EXTERNAL = ‘X’. 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). DataSource 2LIS_03_BF contains data still to be transferred. "Hi, we need to track the modifiations of the PARVW (Role Partner) when it is changed in a Purchasing document. Vendor Supply Information. e. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. (table EKPA). Symptom. 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. Is there any standard solution to extract. here give the PO numbers, specify a name for the job run and execute. 2LIS_02_HDR EKKO, EKBE,T001, EKPA. Thanks, Bobby. Expand in hierarchy structure node Logistics application – 12: LE Shipping BW – Extract structures. 2LIS_02_ITM (Field CHARG is BLANK in RSA3) Recently, I need Batch data for reporting related to Purchasing , fortunately there is field CHARG (Batch) in 2LIS_02_ITM. 0A. 2LIS_02_CGR: Produced Activity: Delivery of Confirmations: MM - Materials Management: 2LIS_03_BF: Goods Movements From Inventory Management: MM - Materials. WKURS - Währungskurs. SAP. For one PO (Purchasing Order) there're 1 record in schedule line table EKET. MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. For e. On this way you could also enable ODP extraction for obsolete SAP standard. 1) these extractors don't appear to have the same data. HI, Which source field in 2LIS_02_SCL give me GR Receipt date in 2LIS_02_SCL Purchasing Data (Schedule Line Level) (SAP Library - Procurement) THANKS2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_S012: Purchasing: MM - Materials Management: 2LIS_02_SGR:. The additional field is not filled when you check the delivered data on BW side. The 2 datasource aren't loading the same information. We have attached 3 source systems to our BW and 2 of them are working absolutely without problems. ie: EUR, JPY, USD,INR and all other country currencies. It enables quick access to any data with a low amount of administrative effort and is especially useful for sophisticated scenarios with unpredictable query types, high data volume and high frequency of queries. MC02M_0ITM: Extraction Purchasing (Item) for DataSource 2LIS_02_ITM. BW SD MM FI 数据源. 1) Add the custom fields to the Communication structure (MCEKET - for Schedule lines) using the APPEND Structure in SE11. Some are transparent, some are reference, but there are one or two that stand out here. 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. Load data InfoPackage 2LIS_02_CGR_INIT_R3. Use. 及其r3数据 源:2lis_02_s012,2lis_02_itm,2lis_02_scl. 2LIS_02_SCL returns data for the purchase order on header item and schedule line level. Hi, I think this depends on what logic u have written in your start routine. 1) what are the difference b/t them. If successful, 3. if the update does not go through for whaterever reason, the complete transaction is rolled back. We are getting '0' instead of the correct quantity, but when we do full load at the end of the month we get. 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'd like to extract Stock Transfer Orders (MM documents) by using DS 2LIS_02_SCL. i need to. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data: SD - Sales and Distribution: 2LIS_11_VASCL: Sales Document Schedule Line: SD - Sales and Distribution: Tables related to 2LIS_13_VDITM TABLE Description Application ; VBRP:The key column for BW is “Sub tot”. Kindly provide a solution for the below problem whcih i am facing with 2lis_02_itm and scl data sources. In fact, 2LIS_02_CGR is loading Confirmation with Goods Receipt from SAP tables EKBE, EKES, EKBE and EKPO. Infopackage B: Delta Update – using the same that I used for IC 0PUR_C01. as the data in that dataset. Vendor. 2lis_03_bx. docx), PDF File (. For more information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. In datasource 2LIS_02_SCL, there is only fields BWMNG - that represents quantity, BWGEO and BWGEO that represent values. I am still finding out which of these extractor needs to be modified. Thanks and regards. Something likes: 2010/11/01 ZNB F 4500000030 610. For e. 2LIS_02_SRV . I have enhanced the extract structure of 2LIS_02_SCL (MC02M_0SCL) to include a field from the standard pool in transaction LBWE. not ectract the good Invoice receipt quantity. Once I do that, I am able to extract data for an info source 2LIS_02_SCL. Problem: Setup tables are not getting populated for 2lis_02_hdr, 2lis_02_item. Monica. I used the datasource 2LIS_02_SCL to get the purchase data . SAP Library - ProcurementIn case of LO Extractors, (2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL in my case), if we have to do full upload, do we still need to run the setup in R/3. Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. Help needed, with detailed step would. Use. The purchase order exists in APO in the form of an order. 0AF_GRDVAL. We have a standard datsource 2LIS_02_SCL for loading the Issued quantity WAMNG against PO. result =. MC02M_0SCN Storage. I'm trying to reconcile a record produced by the 2LIS_02_SCL datasource back to the base R/3 tables. I need a Report in Local Currency ie: USD only (US dollers), Here what I am getting in my Report is all different currencies . Search for additional results. As much as I understand the key fields which I should be using are EBELN Purchasing Doc. Affected REMOTE SUBSCRIPTIONS: SUB_VT_2LIS_03_BF, SUB_VT_2LIS_13_VDITM, SUB_VT_2LIS_02_ITM, SUB_VT_2LIS_13_VDHDR, SUB_VT_2LIS_02_SCL, SUB_VT_2LIS_12_VCITM, SUB_VT_1_CO_PA_CHEMICALS, SUB_VT_2LIS_11_VAKON, SUB_VT_2LIS_11_VAITM, SUB_VT_2LIS_11_VAHDR,. J_3ABWEL_COLOR. KNTTP – Account Assignment Category. Load data InfoPackage 2LIS_02_SGR_INIT_R3. We are doing a delta update. BW SD MM FI 数据源. Lost while creating the. My question is: can we delete/fill setup table without any impact on Delta load? we have a Process Chain that every day load 2LIS data from R3 to BW so our idea is to. On the AWS Supply Chain dashboard, on the left navigation pane, choose Data Lake and then choose Connections. 2LIS_02_CGR Produced Activity: Delivery of Confirmations MM - Materials Management: 27 : 0CO_OM_WBS_4 wbs element s: Statistical key figuresSAP Help, Wiki, Q&A and other resources for 2LIS_02_HDR Click here for the full list of resources and help pages, only the first few are posted below . Inventory Controlling (application 03): 2LIS_03_BX. BW SD MM FI 常用 数据源. 2LIS_02_SCL. J_3ADEPM. This's also valid to other PUSH datasource. First time in the Initial update and seond time in the delta update. ) 2LIS_02_ITM. 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. Description . Visit SAP Support Portal's SAP Notes and KBA Search. Visit. 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. MC11V_0SSL: Extraction MD Sales: Order Delivery for DataSource 2LIS_11_V_SSL. FIP Material Number 0SR_VE_INT_IV . Line 10 and 20 had been deleted. Rechnungen in einer anderen Währung gebucht wurden, gibt der Inhalt dieses Feldes. 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. Available from OLTP Release. Extractor 2LIS_02_SCL --> behaviour when ELIKZ is set. "Image/data in this KBA is from SAP internal systems. SAP automatically put that field under the structure <b>MC02M_2SCL</b> Extraction Purchasing (Schedule Line): Item Data, and it has. The field 2lis_02_ITM-AKTWE give the good GR Quantity for services but do. 1 Answer. Use. My client here does not use schedule lines. 0B (2LIS_02_SCL) and Offsetting Confirmation and Goods Receipt (2LIS_02_SGR). Here Loekz field related data is completely not fetching from the above data sources partial data is able to get. Use. 2LIS_02_HDR EKKO, EKBE,T001, EKPA. Why are the setup tables not filled?Our delta queue for 2LIS_02_ITM and 2LIS_02_SCL was deleted from R3 by mistake. 2lis_02_scn. here give the PO numbers, specify a name for the job run and execute. Situation 2. Thanks, John. Hello everybody, I am using datasource 2LIS_02_SCL to extract data into BW. Sep 16, 2009 at 06:26 PM. Key Fields for DSO using 2lis_02_SCL and 2lis_02_ITM. So every day I would have request with delta data. 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. e. Schedule Line Level: DataSource 2LIS_02_SCL -> InfoSource 2LIS_02_SCL -> DSO ZPUR_O02 (Schedule Line Level) -> InfoCube ZPUR_C01. By default, either of these does not capture changes to a transaction field in VL32N > Item > foreign trade/customs tab > Invoice accomp. Step 2 Goto LBWE transaction in R/3. and enhanced the datasources ITM and SCL adding one Char in RSAP0001 using user exist EXIT_SAPLRSAP_001 . and he has managed to laod data using full upload without. Other terms2LIS_02_ITM, 2LIS_02_SCL, RSA3, RSA7, delta queue, delta initialization,ME21N, MIGO, MIRO, OLI3BW, RMCENEUA.