2lis_02_scl. Then save the PO. 2lis_02_scl

 
 Then save the PO2lis_02_scl  Hi All, Can you please share your experience on the 2LIS_02_ACC data source setup

7. It's almost impossible to fill the setup table. MM-PUR: Purchase Data Account Level (2LIS_02_ACC) - /IMO/PUR_IS13. The information in this field indicates the difference between the purchase order quantity and the goods receipt quantity in the base unit of measure. 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. my problem is i cannot include process key as a. Genrally BWMNG is mapped with 0CPQUAOU. so I add field CHARG into that datasource. 26. Here for this Info cube from another 2lis_02_itm datasource also data is coming. and enhanced the datasources ITM and SCL adding one Char in RSAP0001 using user exist EXIT_SAPLRSAP_001 . Step two: Delete delta entries in RSA7. 2lis_02_sgr. Comparing DataSource 2LIS_02_SCN to ME80FN. 2. 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. 2LIS_02_ITM EKKO, EKBE,T001, T001W, EKPO, TMCLVBW, T027C, ESSR, T147K,. 2016-01-05 02:11:55 NOT all Rows are received yet: 2LIS_02_SCL. <Delete> Go to edit mode of a PO, select an item and click "Delete". Company code. 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. J_3ABWEL_COLOR. I enhanced scheduled qty (MCEKET-MENGE) and Received Qty (MCEKET-WEMNG) to 2lis_02_scl. What i knew is, this type of data we will get from 'Purchasing Data (Schedule Line Level). pdf), Text File (. there is a possibility the records containing this date might be getting filtered based on some difefrent field filter. Comparing DataSource. enabled:true in the Search box and press Enter. "MCEX_UPDATE_02_V1" "(FORM)", or declared in the procedure's RAISING clause. Sent Job ABORTED update to SAP. MCBO -Transaction key active or not. I have some strange problem in R/3. LO Data Sources With Tables - Free download as Word Doc (. We have attached 3 source systems to our BW and 2 of them are working absolutely without problems. SAP automatically put that field under the structure <b>MC02M_2SCL</b> Extraction Purchasing (Schedule Line): Item Data, and it has. g for one item 001 u have quantity 90PC. then check in data target. 1. 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. Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. Tables for 2LIS_02_ITM. Best Answer. for datasources 2lis_02_hdr, 2lis_02_itm, 2lis_02_scl. All of my changes propogated; the DSOs are now write-optimized;. I am still finding out which of these extractor needs to be modified. I can create correctly the init update but I have problems with the. I have to use two info sources called 2LIS_02_SCL and 2LIS_02_SGR in order to populate data in the cube. It mentions BWVORG assumes a value based on the "purchase item type, processed document and purchasing order type". BW/BI Accelarator is a tool that improves the performance of BW 7. By default, this object is created according to the DataStore Object (advanced) template Data acquisition layer (including corporate memory). We had at this point realised there is no Delta on the Purchase cube(New). 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management:. 2LIS_02_SCL . But i want know like, how we can show the Open PO Value & Open PO Qty in the BI report level. Setting the Layout. 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. When I extract this data to PSA ONLY, the count is 19191. I am trying to work with the standard Purchasing queries based on 0PUR_C01. For more information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. LIS_ITM is meant for item level information e. BNKA: Master Records of banks. 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. Logic of Datasource 0INFO_REC_ATTR . 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. 2LIS_02_SCL. For more information, see the data source documentation. result =. J_3ADEPM. My client here does not use schedule lines. I have a 5 records in PSA for a purchase order where total. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. It will send a change like below: Record Mode; EVERS; QTY. Udo. 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). Choose New Data Connection. am working on a new report based on a view which. SAP Knowledge Base Article - Preview. if you put EKET then it brings up. My predecessor actually changed the standard definition of this. we are actually facing an issue with the standard extractor 2LIS_02_SCL - schedule line Level of purchase orders. Reorganization for. There r 2 ways to get this data. I am using 2LIS_02_SCL for to fill the data into 0PUR_C01 cube. RSS Feed. It contained the delta queues as. No. Depending on the process key field BWVORG, the data may be coming from EKET or EKBE. BW SD MM FI 数据源. 以下是SAP ECC中各主要数据源与描述. When i execute the extractor in RSA3 the data is populated, If any standard field is changed then it is. I am currently have an issue with Received Qty of DataSource 2LIS_02_SCL. As per the BI content online documentation for an info source 2LIS_02_SCL, Set up table for purchasing application needs to be recreated. I am working with 2LIS_02_SCL. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL . Users compare BW report output with SAP R/3 tcodes MCSJ and MC$4. As much as I understand the key fields which I should be using are EBELN Purchasing Doc. I have reviewed SAP note 684465 with the list of values BWVORG for purchasing. ALIEF - Number of Deliveries. here give the PO numbers, specify a name for the job run and execute. 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. g for one item 001 u have quantity 90PC. It appears that many of the key figures are updated based on logic relating to the BW Processing Key. You will find that value of "LOEKZ" of. 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. Billing Document Item Data SD -Sales and Distribution. We now decided to load Purchase (Old), Purchase (New) and Article Logistics cubes using 2LIS_02_SCL with the same Info Package. 1) Go to the RSA6 (Find ur datasource 2LIS_02_ITM double click on it ) 2) Double click on the extract structure 3) You will see extract structuter then you can see the append structure at the top left click onit 4) Give. Use. 2. This's also valid to other PUSH datasource. From ITM all fields available are needed and from SCL requisitioner (AFNAM), purchase reg. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Please help me. 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. On the AWS Supply Chain dashboard, on the left navigation pane, choose Data Lake and then choose Connections. You have the option to use the old and new method. Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04. e. Allocation - Schedule Line with Goods Receipt. Note 886716 - Deleted item not reversed in BW2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 5. 1 Answer. Choosing any numbers 1 – 6 will populate the corresponding EXPO KZWI 1 – 6 fields. Now, all the extractor must be zero (0). If successful, 4. 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. 2. ANLH: Main Asset Number. 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. I am facing following problem with above extractor. your BW System name). in any of the tables. Check the PO in ME23n for Order qty. I am extracting purchasing data into BW using datasource 2LIS_02_SCL into ODS 0PUR_DS03. I have a problem with 2LIS_13_VDITM delta. DSO. I tried pulling the data from R/3. Note that if you change a purchasing document, the. BW SD MM FI 常用 数据源. I'm doing the data model design for procurement and i'm intending to use standard cube 0PUR_C01, but instead of using the standard flow (directly from DS to Cube) i was wondering to load the data firstly to one DSO (with all the detail) and next to the cube. I have already maintain datasource 2LIS_02_ITM through LBWE. FIP Material Number 0SR_VE_INT_IV . 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. Is processkey a standard across a module eg: MM and SD. Hi Fabio, No You cannot do a setup for 2LIS_02_ITM only, You can only do a setup for the whole 2LIS_02. Once I do that, I am able to extract data for an info source 2LIS_02_SCL. But the extractors 2lis_02_scl and 2lis_02_hdr don't load the PARVW field; and when the PARVW field is changed in a Purchasing document, the modification date is not updated. ekpo -meins . Comparing DataSource 2LIS_02_SGR to ME80FN. 2LIS_02_HDR EKKO, EKBE,T001, EKPA. 2LIS_02_ITM and 2LIS_02_SCL datasources not only extract PO line items. docx), PDF File (. Features of Extractor. 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”. Then save, check and activate the process chain and provide information, where applicable, about which server the process chain should be scheduled on. e 04/21 I did delta update. - Process Key 003:IR. ODQMON – 2lis_02_itm – Init with data transfer. I have loaded data into customize infocube from datasource 2LIS_02_SGR (This customize infocube have to use full update mode for. MC02M_0ITM: Extraction Purchasing (Item) for DataSource 2LIS_02_ITM. 2LIS_02_SCL enhancement - SAP Q&A Relevancy Factor: 1. 1) what are the difference b/t them. The Select Data Source page appears. SAP Community Network Wiki - SAP NetWeaver Business Warehouse - Step by Step Enhance your Datasource. 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. 0B (2LIS_02_SCL) and Offsetting Confirmation and Goods Receipt (2LIS_02_SGR). For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. PSA in BW. This field determines whether these values are from a purchasing order, goods receipt or an invoice. 0. The information under these fields are dependent from the information of field BWVORG (BW transaction key). MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. 0AF_COLOR. 2LIS_03_BF: Goods Movements From Inventory Management: MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: Messages related to MCBO MESSAGE Description;. Comp. I have to use two info sources called 2LIS_02_SCL and 2LIS_02_SGR in order to populate data in the cube. When a purchase order item confirmed, even though this filed is not changed. in 2lis_02_scl and 2lis_02_itm Data Sources. Your LIS_SCl will contain the schedule line information that is if somebody wants schedule date wise e. ALIEF - Number of Deliveries. BW SD MM FI 数据源. 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. LBWE u2013 activate in option 02 your datasource, follow the right sequence. failing. 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 7. Delete the setup data (LBWG) 2. The subtotal amounts are extracted in PO currency. By default, either of these does not capture changes to a transaction field in VL32N > Item > foreign trade/customs tab > Invoice accomp. Step 2 : Activate and transfer the Application Component Hierarchy(One Time Activity in the project). values. Thanks, Bobby. 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. 2LIS_02_SCL. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. Line 40 had been entered. Description . 2LIS_02_SCL: Purchasing data (Schedule Line Level) MM - Materials Management: 5 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 6 :. Open View Browser app from the search results. After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. 方便各位开发顾问查询. Determine Industry Sector. 2lis_02_scl and 2lis_02_itm - SAP Q&A Relevancy Factor: 1. Now the problem is, I could see FEW records getting posted twice (duplicated) in PSA. WKURS – Exchange Rate. "6. I created a PO with Qty 100 on 03/28/2007 and perfroemd GR on the same day for Qty of 25. Data sources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. This DataSource provides the BW with data from the Sales area and supplies the InfoSource 2AF_SD_SHP_1 with data. But it is fetching 0 data with green status. 及其r3数据 源:2lis_02_s012,2lis_02_itm,2lis_02_scl. in both the bw systems. 2) can i map 0CPPVLC (BWGEO), instead of 0ORDER_val (BWEFFWR) in the transformation and in routine b/w data source and cube. Vendor. Check details in below T codes: BF11- check box required for BW. The additional field is not filled when you check the delivered data on BW side. e. ZPUR_C01) and modify with any from the header that is needed. 172 Views. However, if I use MIGO to do a goods receipt on the already initialize-loaded PO's, no delta for 2LIS_02_SCL is. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW >. This InfoSource contains the quantity that was delivered for each schedule line in a delivery item. When you use service-based invoice verification (EKPO-LEBRE) the extractor 2lis_02_scl. They also extract GR and IR. In particular every time I schedule the job for. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 5. Is there any standard solution to extract. Some are transparent, some are reference, but there are one or two that stand out here. Hit enter to search. Line 30 had been entered and totally delivered. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. 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. From the business content, in the update rule: 2LIS_02_SCL -> 0PUR_DS03. Thank you all four you responses. (BANFN) and. First time in the Initial update and seond time in the delta update. Use. 1)2LIS_03_BX : BWMNG,BWAPPLNM, BSTAUS ,BSTTYP. This doubt came to my mind because, in the past LIS extractors were used in this project 2LIS_02_S012 ( not by me but my predecessor). Comparing DataSource 2LIS_02_SCL to ME80FN. I am using Key figure BWGEO BW:CValLocCrcy & BWGEOO BW: CValOrdCrcy with summation. (table EKPA). Ensure that this counter only counts. The counted number depends on how often a material appears in a GR document. 2lis_03_bf . 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management:. My question is if anyone of you have come across this issue? If yes how was it resolved. so i think i have to use Schedule Line Counter (ETENR) to take the. Visit SAP Support Portal's SAP Notes and KBA Search. I made my changes in the development environment and transported them to QA. BUT. 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. Need advise to build a standard DSO over 2LIS_02_SCL extractor to capture PO details with PO, GR, IR amount and quantity with delta load. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) ( 2LIS_02_SCL ). g. I never used 2LIS_02_SGR, but following the documentation it gives returns data related for goods receipt. 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. The 2LIS_02_SGR provides the GR document number and 2LIS_06_INV the IR document number. This extractor also brings data from Goods receipts and Invoice Receipts which typically come from EKBE table. It depends on key mentioned for BWVORG field in transaction - Transaction Key SAP BW. 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. Has searched many threads from the forum but unable to find perfect solution. - Data Source: 2LIS_11_VASTH. Let’s check the delta flow – Example with Purchase order 4500000001; Purchase Order Quantity in Target table – using data preview; Purchase Order – 4500000001. I have done with Initialization of 2LIS_02_SCL and now trying to run delta for 2LIS_02_SCL. You may choose to manage your own preferences. RSS Feed. I have compared BW data with SAP R/3 using tcode ME80FN and data seems to be consistent. 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. Thanks. Click more to access the full version on SAP for Me (Login required). 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. i. Rechnungen in einer anderen Währung gebucht wurden, gibt der Inhalt dieses Feldes. - Cross company order -. The counted number depends on how often a material appears in a GR document. 2LIS_13_VDITM. 2lis_02_hdr. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_SGR: Produced Activity: Delivery of Schedule Lines: MM - Materials Management:. g. KNTTP – Account Assignment Category The account assignment category determines the account assignment data for an item, such as cost center and account number. This DataSource provides information about the header data of a purchasing document, such as vendor, purchasing organization, order currency, and so on. MM. 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 :. However, my delta infopackage is not picking up any new records. I am trying to fill up the SETUP tables. Situation 2. SAP BW Datasource : 2LIS_02_SCL - Purchasing Data (Schedule Line Level). 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 :. When we do the reconciliation with MC$4, some. The Data Lake page appears. You will find pool of objects there. Now we realize that processkeys 010 are missing but 2LIS_02_ITM catches these. 1. Extraction job in R3 is unable to extract any data, so it . We went to the Infopackage scheduler and by mistake deleted the Initialisation assuming we need a new Initialisation. This counter determines the number of deliveries based on the GR document items. You can use this InfoSource to evaluate delivery services. InfoSources 2LIS_12_VCHDR , 2LIS_12_VCITM , and 2LIS_12. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 : 2LIS_11_VAITM: Sales Document Item Data SD - Sales and Distribution: 5 : 0FI_GL_4: General Ledger: Line Items with Delta Extraction FI - General Ledger Accounting: 6 : 2LIS_03_BX: Stock Initialization for Inventory Management MM - Materials. Block user to modify to modify purchase. Step one: stop all postings in connected ERP system. before image; #; . 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. Follow the below steps to get the lost delta, will be useful for any loads. Transaction event type has the values 1 to 8, I am comparing the keys EBELN and EBELP from structure. Here when we are loading one single purchasing doument from the Datasource ( 2LIS_02_SCL ) to DSO level by using DTP,we found the difference. Maintain your data source in LBWE, For this: (I) Inactivate the data source. Technical name: 2LIS_02_SCL. V . ATTR . I had a requirement to make two Purchasing DSOs (2LIS_02_ITM & 2LIS_02_SCL based) write-optimized. 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. 2LIS_02_ITM and 2LIS_02_SCL. Load data InfoPackage 2LIS_02_CGR_INIT_R3. Allocation – Confirmation with Schedule Line. ie: EUR, JPY, USD,INR and all other country currencies. Job started. 'MATERIAL_ATTR,MAT_SALES_ATTR,2LIS_02_SCL,2LIS_03_BF,2LIS_11_VAITM,2LIS_11_VASCL,2LIS_13_VDITM. MC02M_OSCL. However in the S/4HANA system, table KONV is obsolete and replaced by table. ) 2LIS_02_SCL & 2. Please help me. Enter the search text @Analytics. field in the view because it doesn't exist as a field. On this way you could also enable ODP extraction for obsolete SAP standard. 以下是SAP ECC中各主要数据源与描述. It looks to me, that it provides information about, whether it. Follow. The issue is related to the extraction. With this setting I have to take downtime in R/3. In the migrated Transformation between InfoSource 2LIS_02_ITM and DSO ZPUR_O01 (Position) I have two rule groups. 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. - 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. Technical name: 2LIS_12_VCITM. infoobject are overwritten in the ODS. Visit SAP Support Portal's SAP Notes and KBA Search. = I've been running a FULL Load from this data source with no problems. SAP Knowledge Base Article - Preview. SCL_BEDAT is obviously updated in the extractor with field EKET-ETBDT which is the so called "Order Date". Once the setup table filling is done. when checked the data by RSA3 , I found the system generated mass data(2400 records) . Overlapping check with archived data areas for InfoProvider ZP2_PSCL. there will be a second record in 2LIS_02_SCL. For e. 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). 2) Include these fields in the Extract structure in LBWE (Maintain Extract structure) 3) Implement the User exit called: LEINS001 - Statistics update - purchasing documents. Use. For more information, refer to the. 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. Sep 16, 2009 at 06:26 PM. Since I know I am working with Purchasing data those are my obvious choices. Lost while creating the. Step 2 Goto LBWE transaction in R/3. 2lis_02_scn. 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. 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. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. g. 2LIS_13_VDKON: Billing Condition Data; Supply Chain Management: 2LIS_02_HDR: Purchasing Data Header; 2LIS_02_ITM: Purchasing Data Item; 2LIS_02_SCL: Purchasing Data Schedule Line; 2LIS_02_ACC: Purchasing Data Accounting; 2LIS_02_SCN: Purchasing Data Confirmation of Schedule Lines; 2LIS_02_SGN: Purchasing Data Delivery of Schedule Lines Technical name: 2LIS_02_SCL Use 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. J_3ASIZE. Please share your ideas on this data source setup. MM Data Sources Tables Purchasing. 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). Namely Purchasing Document Header EKKO and Purchasing Document Item EKPO. As per the BI content online documentation for an info source 2LIS_02_SCL, Set up table for purchasing application needs to be recreated. . Fill the set up tables. txt) or read online for free. The other datasource 2LIS_02_SGR is loading the Schedule Line with Goods Receipt from SAP tables EKET, EKBE and EKPO. We deleted the inbound queues for 11. Change the Standard variant to Released Views variant. If successful, 5. If any entries are available then trigger the equivalent Info. Problem: Setup tables are not getting populated for 2lis_02_hdr, 2lis_02_item. This data source is used often. To ingest data from an SAP S/4HANA data source, perform the following procedure. X 2010/11/01 ZNB F. If successful, 3. When you use service-based invoice verification (EKPO-LEBRE) the extractor 2lis_02_scl. First activate the data source in RSA5 and check it in RSA6 (active data sources are available here). To prevent the exception, note the following: A dataset can only be imported to a target area with the same structure . 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. and choose the industry sector "Standard (Core)". However, when. Line 10 and 20 had been deleted. 2. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL.