My client here does not use schedule lines. I am using standard extractor 2LIS_13_VDITM and 2LIS_02_SCL. When i am extracting same datasource in source system and able to see data. 0A. Then use the function Activate and Schedule to start the process chain according to your scheduling options. ekpo -meins . I have done with Initialization of 2LIS_02_SCL and now trying to run delta for 2LIS_02_SCL. 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. am working on a new report based on a view which. ALIEF - Number of Deliveries. 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. You can check the data from the DataSource 2LIS_02_SCL in last two views mentioned. 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. i. 2LIS_02_SCL transformation logic. However, when. Other terms2LIS_02_ITM, 2LIS_02_SCL, RSA3, RSA7, delta queue, delta initialization,ME21N, MIGO, MIRO, OLI3BW, RMCENEUA. The counted number depends on how often a material appears in a GR document. 0. But it is fetching 0 data with green status. This is basically information relating to the delivery completed indicator, open quantity and planned delivery date or requested. Use. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . TBSL: Posting Keys. 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. Comparing DataSource 2LIS_02_SCN to ME80FN. Job started. Please find the below extractors and its fields . adjusts the quantities to give the true 'open/closed' qty after GR. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL . The data are transfered correctly (maybe!) from Extraction Queue to Delta Queue (daily, the amount of data is almost 1000 a day). What i knew is, this type of data we will get from 'Purchasing Data (Schedule Line Level). we have problems with extractor 2lis_02_scl in delta data extraction. It's almost impossible to fill the setup table. Released . Problem: We are using the 2LIS_02_SCL to get our purchasing order data. you can get the records by running the extraction of 2LIS_02_SCL in RSA3. DataSource 2LIS_02_SCL returns value zero for enhanced field MENGE (Scheduled Qty) for some records. J_3ADEPM. 2LIS_02_SGR Produced Activity: Delivery of Schedule Lines MM - Materials Management: 16 : 0MATERIAL_ATTR Material Number Logistics - Logistics - General: 17 :I am using standard extractor 2LIS_13_VDITM and 2LIS_02_SCL. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management:. where this is using a standard datasource 2LIS_02_ITM and 2LIS_02_scl and i have acitvated this standard cube 0pur_c01. Status . If the information relates to a goods receipt or an invoice, the field is filled with the. 2lis_02_s012. I have succeed to get some key figures like PO Quantity, GR Quantity and Invoice Receipt Quantity according to the Process Key value. Step one: stop all postings in connected ERP system. Data Modeling. From the business content, in the update rule: 2LIS_02_SCL -> 0PUR_DS03. InfoSources 2LIS_12_VCHDR , 2LIS_12_VCITM , and 2LIS_12. Department. If successful, 4. before image; #; . doc / . I will analyse notes 459517, 728687, 722339 y 869628. In the migrated Transformation between InfoSource 2LIS_02_ITM and DSO ZPUR_O01 (Position) I have two rule groups. This DataSource provides information about the distribution of goods receipt quantities to the confirmation quantities. here give the PO numbers, specify a name for the job run and execute. 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). 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. e 04/21 I did delta update. We are using two PO extrctors 2LIS_02_ITM & 2LIS_02_SCL to load data, both are working fine. 1. Why? What am i missing out do i need to do any changes before i actiavte the in-active tables in LO-Cockpit. Comparing DataSource. Is processkey a standard across a module eg: MM and SD. 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. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) (2LIS_02_SCL). In transactions "RSA1" has gone to a bookmark "DataSources", has selected a datasource "2LIS_02_SCL" and has chosen from the contextual menu "Manage". This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) ( 2LIS_02_SCL ). The information in this field indicates the difference between the purchase order quantity and the goods receipt quantity in the base unit of measure. ie: EUR, JPY, USD,INR and all other country currencies. Thaning you. Controlling 2LIS_03_BF MC03BF0SETUP. That is the way SAP provides extractor fields. Purchasing 2LIS_02_SCN MC02M_0SCNSETUP BW-Rebuild for. 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. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. 2LIS_02_SCL. I have already maintain datasource 2LIS_02_ITM through LBWE. 26. 2LIS_02_SCL enhancement - SAP Q&A Relevancy Factor: 1. so i think i have to use Schedule Line Counter (ETENR) to take the. 2013 through transaction code SMQ1. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. I need a Report in Local Currency ie: USD only (US dollers), Here what I am getting in my Report is all different currencies . The system only calculates this delta if a purchase order item is completed. Based on DataSource: 2LIS_02_SCN. Purchasing Data (Document Schedule Line Level) Technical name: 2LIS_02_SCL. The field is BADAT [Requisition (Request) Date]. This's also valid to other PUSH datasource. i did the setup using one purchase order no(of course I deleted the setup table before did it). RSS Feed. 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. "6. Based on DataSource: 2LIS_02_SGR. Not able to load delta for 2LIS_02_SCL. - Cross company order -. Please help. = I've been running a FULL Load from this data source with no problems. The additional field is not filled when you check the delivered data on BW side. The field 2lis_02_ITM-AKTWE give the good GR Quantity for services but do. This InfoSource contains the structure to provide purchase accounting data on item level into the EDW Core Layer. 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. LBWE u2013 activate in option 02 your datasource, follow the right sequence. It depends on key mentioned for BWVORG field in transaction - Transaction Key SAP BW. (II) Click on the maintanence tab, pull the fields from communication structure to extract structure based on reporting requirement. We are getting '0' instead of the correct quantity, but when we do full load at the end of the month we get. All of my changes propogated; the DSOs are now write-optimized;. 2LIS_02_SCL. 2LIS_02_SCL datasource will give the GR values from EKBE table by considering the purchase documents from EKKO table for respective vendor. Go to. 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:. for datasources 2lis_02_hdr, 2lis_02_itm, 2lis_02_scl. Step 2 : Activate and transfer the Application Component Hierarchy(One Time Activity in the project). field in the view because it doesn't exist as a field. Choose. I look at SE11 for ' MC02M_0HDRSETUP ' and table contents gives 0 records. Can you please guide me through! Thanks, Ram. Technical Data. Features of Extractor. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. 0. Block user to modify to modify purchase. When I extract this data to PSA ONLY, the count is 19191. Locate your Extractor (Datasource). 1 - System standard fields. Apparently these two fields are NOT updated in BW from a delta load. Symptom. Enter t-code : RSA9. 0AF_CGR10. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 : 0CO_OM_OPA_6: Orders: Actual Costs Using Delta Extraction CO - Overhead Cost Orders: 3 :. SAP. The counted number depends on how often a material appears in a GR document. 2LIS_02_SCL and _ITM Purchasing Cube 0PUR_C01. SAP Knowledge Base Article - Preview. I know that For purchase order details we used 2 datasources 1. do not extract the good Invoice receipt quantity for each purchase order. From what I read, i think i'm missing the following steps, from which I need more detail:Hi all!! Im using the extractor 2lis_02_scl and now the customer want to add a field that is in the table EKBE, the field is CPUDT. The field we enhanced is EKPO-EVERS. The following has all been done. I am working with 2LIS_02_SCL. Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. We are executing a delta load from datasource 2LIS_02_SCL and it is. Depending on the process key field BWVORG, the data may be coming from EKET or EKBE. Please help me. Pls reply needed urgent,i'm. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW >. g we have in Item 001 quanity 90PC, in Schedule line it will be schedule line wise that is. I have loaded data into customize infocube from datasource 2LIS_02_SGR (This customize infocube have to use full update mode for. 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. 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. Hi, I was loading 2LIS_02_SCL - PO Schedule Line into BW - I was able to add = an extra field to the Extract Structure though the Customizing Cockpit. Then save the PO. The data records for. If the DataSources are from the LO cockpit, this push takes place either with a direct delta. The information under these fields are dependent from the information of field BWVORG (BW transaction key). 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). in 2lis_02_scl and 2lis_02_itm Data Sources. In datasource 2LIS_02_SCL, there is only fields BWMNG - that represents quantity, BWGEO and BWGEO that represent values. Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. 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’. "Hi, we need to track the modifiations of the PARVW (Role Partner) when it is changed in a Purchasing document. 2LIS_02_SRV . To prevent the exception, note the following: A dataset can only be imported to a target area with the same structure . Namely Purchasing Document Header EKKO and Purchasing Document Item EKPO. Extraction job in R3 is unable to extract any data, so it . Transfer struct. 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. 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. This could be a viable solution? Do you have any document in order to configurate it? I tested it in RSA3 but no data retreived. 1) what are the difference b/t them. Please help me. 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. Explanation of Note 578471 - Deleted positions in BW and statistics . 2LIS_02_SCL Issue. Purchsing Data Extraction through EKBEH table. Step three:. Problem with MCEX_UPDATE_02 COLL. 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. But i want know like, how we can show the Open PO Value & Open PO Qty in the BI report level. Sent Job ABORTED update to SAP. In fact, 2LIS_02_CGR is loading Confirmation with Goods Receipt from SAP tables EKBE, EKES, EKBE and EKPO. B. J_3AKVGR10. 2LIS_03_UM. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. The issue is related to the extraction. i need to. Marco. docx), PDF File (. Comment . When you use service-based invoice verification (EKPO-LEBRE) the extractor 2lis_02_scl. We are using two PO extrctors 2LIS_02_ITM & 2LIS_02_SCL to load data, both are working fine. 4: Open GI quantity/value: 2LIS_12_VCSCL also gives the goods movement status, which can be used to calculate the open goods issue quantity from the. A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!Hello, gurus. SCL_BEDAT is obviously updated in the extractor with field EKET-ETBDT which is the so called "Order Date". For e. We discovered for once GR 2LIS_02_SCL always presents 2 lines with almost same data execpt field ROCANCEL equals 'X'. Apart from the sales orders, 2LIS_02_SCL will give the purchase orders based on stock order transfer. Open View Browser app from the search results. failing. For more information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Technical name: 2LIS_02_SCN. Load data InfoPackage 2LIS_02_SGR_INIT_R3. Please do advise on the below questions. - Process Key 003:IR. I am trying to work with the standard Purchasing queries based on 0PUR_C01. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. SAP automatically put that field under the structure <b>MC02M_2SCL</b> Extraction Purchasing (Schedule Line): Item Data, and it has. Demo - Generate and Extract delta data . 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. Our users are complaining, because they expect it to match up. 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. Comparing DataSource. 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. The account assignment category determines the account assignment data for an item, such as cost center and account number. Udo. We deleted the inbound queues for 11. Available from OLTP Release. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. 5. The outbound queue is filled for the following queues in the. First activate the data source in RSA5 and check it in RSA6 (active data sources are available here). Type . It appears that many of the key figures are updated based on logic relating to the BW Processing Key. KNTTP – Account Assignment Category The account assignment category determines the account assignment data for an item, such as cost center and account number. check step by step. 2LIS_02_SCL. A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!Activate data source of Appl. Process overview . The counted number depends on how often a material appears in a GR document. 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. MCBO -Transaction key active or not. 0AF_GRDVAL. . SAP BW Datasource : 2LIS_02_SCL - Purchasing Data (Schedule Line Level). Industry key is also set and application component is also populating. 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. Here for this Info cube from another 2lis_02_itm datasource also data is coming. 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. This extractor also brings data from Goods receipts and Invoice Receipts which typically come from EKBE table. Transaction event type has the values 1 to 8, I am comparing the keys EBELN and EBELP from structure. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . Load data InfoPackage 2LIS_02_SCL_INIT_R3. At my client we implemented the PO Sch Extrc 2LIS_02_SCL and 2LIS_02_ITM. Expand in hierarchy structure node Logistics application – 12: LE Shipping BW – Extract structures. Change PO Qty For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. You may choose to manage your own preferences. goods tab > invoice number field. From ITM all fields available are needed and from SCL requisitioner (AFNAM), purchase reg. We implemented 0PUR_C01 (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. LO Data Sources With Tables - Free download as Word Doc (. 2016-01-05 04:11:47 NOT all Rows are received yet: 2LIS_02_SCL. We now decided to load Purchase (Old), Purchase (New) and Article Logistics cubes using 2LIS_02_SCL with the same Info Package. values. I enhanced scheduled qty (MCEKET-MENGE) and Received Qty (MCEKET-WEMNG) to 2lis_02_scl. Now we realize that processkeys 010 are missing but 2LIS_02_ITM catches these. Here Loekz field related data is completely not fetching from the above data sources partial data is able to get. 2. 方便各位开发顾问查询. 5. Now when I extract this data in full load in RSA3, I get a total of 19200 records. Activate ODS data 0PUR_DS03. I have to use two info sources called 2LIS_02_SCL and 2LIS_02_SGR in order to populate data in the cube. there will be a second record in 2LIS_02_SCL. and 2LIS 02 SCL for loading business content Infocube 0PUR_C01. From this data source data is storing in two data targets 1. Once I do that, I am able to extract data for an info source 2LIS_02_SCL. 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. This is regarding finding out the Extractor Logic (Fuction module ABAP logic ) for few of the standard extaractors fields in sap ecc side. Load data InfoPackage 2LIS_02_CGR_INIT_R3. Line 30 had been entered and totally delivered. This field determines whether these values are from a purchasing order, goods receipt or. 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. 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. 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). here give the PO numbers, specify a name for the job run and execute. 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. in both the bw systems. goods tab > invoice number field. collective update this end with a dump with the message MESSAGE_TYPE_X. 0FIPMATNR_ATTR . We have a standard datsource 2LIS_02_SCL for loading the Issued quantity WAMNG against PO. I understand the for new methos DS (2LIS_02_ITM and 2LIS_02_SCL), there is a activation, deleting od setup tables, ect process associated. Sep 16, 2009 at 06:26 PM. I activated 2LIS_02_itm and SCL datasources in LO cockpit but, it is not prompting for a transport request. 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. The 2LIS_02_SGR provides the GR document number and 2LIS_06_INV the IR document number. 2016-01-05 04:11:48 Err Id: 17. V . An issue may result in changes to scope, budget, timeline, or resources. 2LIS_02_ITM and 2LIS_02_SCL. Use. includes tables like ekko/ekpo/ekbe etc. MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. Thanks. I created a PO with Qty 100 on 03/28/2007 and perfroemd GR on the same day for Qty of 25. Visit. RemoteCube Compatibility. Delta Update. 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. 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. I initiated on 04/14 and after a week i. The following jobs move the data from the outbound queue to BW. Application Component. Logistic Data sources with tables. In the transfer rule, there is a coding to check on process key in 2LIS_02_SCL. Your LIS_SCl will contain the schedule line information that is if somebody wants schedule date wise e. Note 886716 - Deleted item not reversed in BWPurchasing 2LIS_02_SCL MC02M_0SCLSETUP Storage BW Setup for. 2016-01-05 02:11:55 NOT all Rows are received yet: 2LIS_02_SCL. Change the PO Qty from 32 to 40 and save the same. MC02M_0ITM: Extraction Purchasing (Item) for DataSource 2LIS_02_ITM. As per the BI content online documentation for an info source 2LIS_02_SCL, Set up table for purchasing application needs to be recreated. For more information, see the data source documentation. I went on with the assumption that SCL will capture all events that ITM captures except for Quotations and Contracts (Which my. Something likes: 2010/11/01 ZNB F 4500000030 610. I am facing following problem with above extractor. The Data Lake page appears. It is field-based and contains all. Please also specify what is the way to find out it. If successful, 5. you can get the records by running the extraction of 2LIS_02_SCL in RSA3. I am using Key figure BWGEO BW:CValLocCrcy & BWGEOO BW: CValOrdCrcy with summation. This DataSource provides the BW with data from the Sales area and supplies the InfoSource 2AF_SD_SHP_1 with data. RUN Init. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 5. Hi, I think this depends on what logic u have written in your start routine. Though the cumulative goods receipt is coming OK in BW, am not able to see any values against vendor returns since update rulesWeitere Informationen finden Sie im SAP-Hinweis 670313: BW: Feld NETPR für Datenquelle 2LIS_02_ITM und 2LIS_02_SCL. "Document data restriction" when filling setup table. Since I know I am working with Purchasing data those are my obvious choices. 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. The 2 datasource aren't loading the same information. Here Loekz field related data is completely not fetching from the above data sources partial data is able to get. Lost while creating the. populate Goods Receipt value and Invoice Receipt. O I am getting 5 Line entries of this material Hence if the original P. This counter determines the number of deliveries based on the GR document items. Dear Gurus, I have a requirement to extract Invoice Recipt Document number & Invoice date for every purchase order into BW. (table EKPA). Line 10 and 20 had been deleted. 2lis_02_scn. 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. When i have GR reversal , Movement Type 102. You can use this InfoSource to evaluate delivery services. 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). Infopackage B: Delta Update – using the same that I used for IC 0PUR_C01. i. 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. In our case, the filling setup table, it took normally over 1 days. Vendor. This DataSource provides the BW with data from the Sales area and supplies the InfoSource 2AF_SD_SHP_1 with data. RemoteCube Compatibility. DSO. 1. 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. Some are transparent, some are reference, but there are one or two that stand out here. VRTKZ – Distribution Indicator for Multiple Account.