2867285-2LIS_02_SCL : extracts more schedule lines than table EKET. 2LIS_02_SCL. 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. Situation 2. 2. RSS Feed. I add the following fields REMNG /REWRT/ WEMNG /WEWRT in the LO cockpit. 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. With this setting I have to take downtime in R/3. Rechnungen in einer anderen Währung gebucht wurden, gibt der Inhalt dieses Feldes. as the data in that dataset. - Normal purchasing order - BWVORG = 001. Type of DataSource. ENDLOOP. We are doing a delta update. Once the setup table filling is done. Hi i need to enhance the extractor 2LIS_02_SCL with MKPF-BLDAT or EKBE-BLDAT, but i don't know how to add this field, because the Purchasing Document (EBELN) and EBELP aren't unique key to enter in this table (they could have more material document with different BLDAT). Fill the set up tables. when checked the data by RSA3 , I found the system generated mass data(2400 records) . 2LIS_02_SCL : Purchasing data schedule line level 2LIS_02_SCN : Produced Activity : confirmation of schedule Lines 2LIS_02_HDR : Produced Activity : Delivery of schedule lines 2LIS_02_HDR : Produced Activity : Delivery Confirmation Purchasing Standard Info Cube and DSO Info cube 0PUR_C01 Purchasing Data. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_CGR:. 2LIS_02_ITM EKKO, EKBE,T001, T001W, EKPO, TMCLVBW, T027C, ESSR, T147K,. 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. AFS 3. Logistic Data sources with tables. LBWE u2013 activate in option 02 your datasource, follow the right sequence. Fields BWGEO, BWGEOO, BWGVP, BWGVO, BWNETWR, BWMNG, etc. Go to Maintainance. 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). Use. Extraction job in R3 is unable to extract any data, so it . 0A. Transaction LBWQ in ECC: MCEX02. Explanation of Note 578471 - Deleted positions in BW and statistics . I am using 2LIS_02_SCL for to fill the data into 0PUR_C01 cube. In R/3- Enhance the SCL extractor by adding the ZZ. I found the some information on this data source from the business content as follows. 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 7. For e. BW SD MM FI 数据源. 2lis_02_s012. The field 2lis_02_ITM-AKTWE give the good GR Quantity for services but do. You may choose to manage your own preferences. As you konw, When R/3 system doesn't make any transaction data, we can fill the setup table. I am loading the data form the 2LIS_02_SCL datasource to the DSO in BI. So every day I would have request with delta data. Billing Document Item Data SD -Sales and Distribution. 2lis_02_itm . 2lis_02_hdr. Use. But in BI 7. I am using standard extractor 2LIS_13_VDITM and 2LIS_02_SCL. 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). , EBELP Item and ETENR Schedule Line. Open View Browser app from the search results. 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_s011. 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). Apparently these two fields are NOT updated in BW from a delta load. They also extract GR and IR. check in start routine/update/end routine for any filters. Use. 2LIS_02_HDR Purchasing data (Header Level) MM - Materials Management: 18 : 2LIS_12_VCITM Delivery Item data: SD - Sales and Distribution: 19 : 0HR_PY_1Comparing DataSource 2LIS_02_SCN to ME80FN. BW SD MM FI 常用 数据源. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. Kindly let me know why i am not able to fetch data. Hi, I think this depends on what logic u have written in your start routine. Hi Fabio, No You cannot do a setup for 2LIS_02_ITM only, You can only do a setup for the whole 2LIS_02. Delivery Item . you can get the records by running the extraction of 2LIS_02_SCL in RSA3. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. and he has managed to laod data using full upload without. Has searched many threads from the forum but unable to find perfect solution. My client here does not use schedule lines. Data Modeling. The account assignment category determines the account assignment data for an item, such as cost center and account number. 2LIS_02_SCL. "Document data restriction" when filling setup table. Technical name: 2LIS_02_SCL. check step by step. If the target area is longer or shorter . The three others (2LIS_46_HED ; 2LIS_46_CFM ; 2LIS_46_GTM) are not showing any data : see attached picture issue. 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. 0B (2LIS_02_SCL) and Offsetting Confirmation and Goods Receipt (2LIS_02_SGR). Can you please guide me through! Thanks, Ram. Note: As an alternative you can also use DHCDCVCDSEXTRE in SE16 which contains more or less the same information. Step three:. We are getting '0' instead of the correct quantity, but when we do full load at the end of the month we get. The other datasource 2LIS_02_SGR is loading the Schedule Line with Goods Receipt from SAP tables EKET, EKBE and EKPO. Step two: Delete delta entries in RSA7. I need to add some Z custom fields in BW datasource 2LIS_02_ITM which we are doingby appending in structure MC02M_0ITM. 但是系统字段：交货单号（ ekbe-belnr ），参考凭证号（ekbe-xblnr ）没有。如果不做增强， 在其它数据源上是否有这二个字段？我找了采购，销售的都没有这二个字段，可能我还没有找对，麻烦各位高人帮指点。 谢谢. Technical name: 2LIS_12_VCITM. 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. Company code. There is a standard SAP DSO 0PUR_DS03 which is getting data from 2LIS_02_SCL. Visit. Thanks, Bobby. Transfer struct. The 2LIS_02_SCL init. 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. Vote up 0 Vote down. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. Check details in below T codes: BF11- check box required for BW. And below I am giving the job log details of ODS activation. Customer-Defined DataSource ® L. Record count in RSA3 and PSA is different. 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. 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. I'd like to extract Stock Transfer Orders (MM documents) by using DS 2LIS_02_SCL. Inventory Controlling (application 03): 2LIS_03_BX. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . Kindly suggest any Solution. 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. It mentions BWVORG assumes a value based on the "purchase item type, processed document and purchasing order type". DataSource: 2LIS_02_SCL. One or more purchasing documents or items are not extracted either by a full load or a delta loads using some of the following DataSources: 2LIS_02_ACC, 2LIS_02_CGR, 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL, 2LIS_02_SCN, 2LIS_02_SGR. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. In the transformation start routine, I could see alogic which is barring some records to DSO. e. I have some strange problem in R/3. This how 2LIS_03_BF /UM. Bei Einkaufsbelegen, die in einer anderen als der Hauswährung angelegt wurden oder zu denen Belege wie z. Sep 26, 2012 at 05:47 AM. 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 :. 0AF_COLOR. my problem is i cannot include process key as a. 1 - System standard fields. Thanks for the advice. Determine Industry Sector. MC11V_0SCL: Extraction SD Sales BW: Allocation Schedule Line for DataSource 2LIS_11_V_SCL. When i have GR reversal , Movement Type 102. I needed to analyse contents PSA of the table of a Datasource "2LIS_02_SCL". Now we realize that processkeys 010 are missing but 2LIS_02_ITM catches these. The following has all been done. It's almost impossible to get the chance ( when korea plant rest, another plant still running. 6. RSA3. The field we enhanced is EKPO-EVERS. 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). When i execute the extractor in RSA3 the data is populated, If any standard field is changed then it is. J_3ABWEL_COLOR. 26. I have done with Initialization of 2LIS_02_SCL and now trying to run delta for 2LIS_02_SCL. Among the ORECRODMODE and STORNO, which is better option to be mapped with the. This may lead to the following: The system does not perform…The data sources 2lis_02_itm ,2lis_02_scl etc will have these tabels data . Expand in hierarchy structure node Logistics application – 12: LE Shipping BW – Extract structures. not ectract the good Invoice receipt quantity. I need to load data into purchasing data cube (0PUR_C01) from two standard data sources: 2LIS_02_ITM and 2LIS_02_SCL. You will find pool of objects there. Feb 04, 2011 at 01:37 AM. DataSource . - Cross company order -. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. We went to the Infopackage scheduler and by mistake deleted the Initialisation assuming we need a new Initialisation. When you use service-based invoice verification (EKPO-LEBRE) the extractor 2lis_02_scl. Thaning you. Sent Job ABORTED update to SAP. <Delete> Go to edit mode of a PO, select an item and click "Delete". Purchsing Data Extraction through EKBEH table. We are using two PO extrctors 2LIS_02_ITM & 2LIS_02_SCL to load data, both are working fine. enabled:true in the Search box and press Enter. Block user to modify to modify purchase. Comparing DataSource 2LIS_02_SCL to ME80FN. 2lis_02_scl. "MCEX_UPDATE_02_V1" "(FORM)", or declared in the procedure's RAISING clause. 2LIS_02_SCL Issue. The field 2lis_02_ITM-AKTWE give the good GR Quantity for services but do. - Data Source: 2LIS_11_VASTH. Due to failre in purchase related datasource. Setting the Layout. As when we pull BUDAT(posting date) in 2lis_02_scl it depends on the transaction key. The Posting date (BUDAT) from the 2LIS_02_SCL is being assigned to 0CALDAY with the rule type specified as Time Characteristic. 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”. ALIEF - Number of Deliveries. 1. SAP automatically put that field under the structure <b>MC02M_2SCL</b> Extraction Purchasing (Schedule Line): Item Data, and it has. ie: EUR, JPY, USD,INR and all other country currencies. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 : 2LIS_03_UM Revaluations MM - Materials Management: 21 : 2LIS_02_HDR Purchasing Data (Header Level) MM - Materials Management: 22 : 2LIS_13_VDKON Billing Document Condition SD - Sales and Distribution: 23 :2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 3 : 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 :. For more information, refer to the. Search for additional results. 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. 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 more information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 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. there is a routine for the PO open quantity 0BO_QTY as follows: RESULT = COMM_STRUCTURE-cpquaou * COMM_STRUCTURE-numerator / COMM_STRUCTURE-denomintr. 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. 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. 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. No. This update is normally a synchronous update, i. Comment . Delete content of ODS/CUBE. 2016-01-05 04:11:47 NOT all Rows are received yet: 2LIS_02_SCL. 2LIS_02_SCL EKKO, EKBE,T001, T001W, EKET, EKPA. Your LIS_SCl will contain the schedule line information that is if somebody wants schedule date wise e. 2. 6. In 2LIS_02_SCL i have 0CPPVLC (BWGEO), 0CPPVOC (BWGEOO), 0ORDER_val (BWEFFWR). 2) can i map 0CPPVLC (BWGEO), instead of 0ORDER_val (BWEFFWR) in the transformation and in routine b/w data source and cube. ekpo -meins . However, I found 2LIS_02_SCL. 2lis_02_scn. However, before replicating to the BW on HANA system connected, I checked data in S4 via RSA3. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. Ensure that this counter only counts. Load data InfoPackage 2LIS_02_SGR_INIT_R3. Vote up 2 Vote down. For more information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2016-01-05 04:11:48 Err Id: 17. Please suggest me the ideal way to complete this task. 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;. 2) Now you can selectively fill the setup tables for purchasing related datasources by the T-code OLI3BW. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Visit SAP Support Portal's SAP Notes and KBA Search. 0. Ramarao. dataextraction. It appears that many of the key figures are updated based on logic relating to the BW Processing Key. 2lis_02_itm uses EKKO and EKPO tables etc. Save BW. SAP Community Network Wiki - SAP NetWeaver Business Warehouse - Step by Step Enhance your Datasource. field in the view because it doesn't exist as a field. There I see data only for some extractors (2LIS_46_SCL and 2LIS_46_ITM) : see attached picture issue-gtm-01. g. 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. And one question concerning purchase data. 2LIS_02_SRV . Problem: We are using the 2LIS_02_SCL to get our purchasing order data. But it is fetching 0 data with green status. There is no other common key between MC02M_SCL and EKBE. In particular every time I schedule the job for. . Hi All. 'MATERIAL_ATTR,MAT_SALES_ATTR,2LIS_02_SCL,2LIS_03_BF,2LIS_11_VAITM,2LIS_11_VASCL,2LIS_13_VDITM. "Image/data in this KBA is from SAP internal systems. PSA in BW. I have to use two info sources called 2LIS_02_SCL and 2LIS_02_SGR in order to populate data in the cube. 2LIS_02_SCL transformation logic. Application Component. By default, this object is created according to the DataStore Object (advanced) template Data acquisition layer (including corporate memory). also full update of 2LIS_13_VDITM featches only records that have been uploaded with initial load. A drop down list on “Su Tot” reveals a list of assignment options. if anyone knows tcodes for runinng the set uptable to each data source separatley. When a purchase order item confirmed, even though this filed is not changed. 5. The EKET (Purchasing Schedule Line) table doesn't have this. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Thanks and regards. We have a standard datsource 2LIS_02_SCL for loading the Issued quantity WAMNG against PO. Help. J_3ASIZE. 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. Lost while creating the. 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. The outbound queue is filled for the following queues in the. 2lis_03_bf . Comparing DataSource 2LIS_02_SGR to ME80FN. 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. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 2LIS_13_VDKON:. and choose the industry sector "Standard (Core)". In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. 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. 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. Now, all the extractor must be zero (0). Complete customizing, LBWE setup and Delta initialisation was performed the. 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. I have some strange problem in R/3. do not extract the good Invoice receipt quantity for each purchase order. Line 30 had been entered and totally delivered. 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. 02 in LBWE. This is regarding finding out the Extractor Logic (Fuction module ABAP logic ) for few of the standard extaractors fields in sap ecc side. 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. I have enhanced the extract structure of 2LIS_02_SCL (MC02M_0SCL) to include a field from the standard pool in transaction LBWE. 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. actually my purchase relevant data are as follows: 21 reordes of order item ,78 reocords of order. Type of DataSource. when i check in rsa3 the data is correct. The counted number depends on how often a material appears in a GR document. x flow. i need to. Step 2 Goto LBWE transaction in R/3. in 2lis_02_scl and 2lis_02_itm Data Sources. 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. so i think i have to use Schedule Line Counter (ETENR) to take the. Or if you are looking for OSS NOte # 353042. Available from OLTP Release. ANLA, ANLB, ANLC : Segment Assets Masters. Technical Data. DELETE TABLE SOURCE_PACKAGE from wa_package. Hi Amit, Refresh your BI system first and you will find your Datasource replicate the Datasource, soon after you replicate it will take to you to BI Content there you have to active the related objects as desired for 2lis_02_SCL,then your Datasource is replicated successfully and it will appear in u201CDu201D Version. Technical Data. One system it is showing 42 Records Transferred and 8 Added Record in DSO level, and another system is showing 14. We are using two PO extrctors 2LIS_02_ITM & 2LIS_02_SCL to load data, both are working fine. Once I do that, I am able to extract data for an info source 2LIS_02_SCL. MM. Load data InfoPackage 2LIS_02_ITM_INIT_R3. Datasource 2LIS_02_ITM (Purchasing data (item level)) with delta type D (push): As this is delta type PUSH, the delta data records from the application are posted to the delta queue before they are extracted from ODQ as part of the delta update. The logic says: umren EQ 0. DataSource 2LIS_03_BF contains data still to be transferred. As much as I understand the key fields which I should be using are EBELN Purchasing Doc. Type . Use. 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. 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. We implemented 0PUR_C01 (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. In the SAP S/4HANA Cloud system, choose the App Finder and search for the View Browser app. 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. 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_OSCL. Please also specify what is the way to find out it. i did the setup using one purchase order no(of course I deleted the setup table before did it). Key Fields for DSO using 2lis_02_SCL and 2lis_02_ITM. Note that if you change a purchasing document, the. LBWE-- >Purchasing >Extract structures ---->2LIS_02_HDR/SCL/ITM (DATA SOURCES),when i click on the in-active tab to make change and activate i get a alert as the DATA SOURCE doesn't exist. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/PUR_IS12. goods tab > invoice number field. 2LIS_03_BF. By default, either of these does not capture changes to a transaction field in VL32N > Item > foreign trade/customs tab > Invoice accomp. 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. 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. e 04/21 I did delta update. I am extracting data from 2LIS_02_SCL. 2LIS_02_SCL. 0AF_GRDVAL. LO Data Sources With Tables - Free download as Word Doc (. KNTTP – Account Assignment Category The account assignment category determines the account assignment data for an item, such as cost center and account number. in any of the tables. 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. Let’s check the delta flow – Example with Purchase order 4500000001; Purchase Order Quantity in Target table – using data preview; Purchase Order – 4500000001. 24. 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. WKURS – Exchange Rate. Demo - Generate and Extract delta data . 0A. 2LIS_02_ITM and 2LIS_02_SCL. 2LIS_02_SCL EKKO, EKBE,T001, T001W, EKET, EKPA. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 5. However after full loading, you notice that more schedule line records are extracted by Datasource 2LIS_02_SCL. Once the setup table filling is done. So 2LIS_02_SCL gives more informations. If the information relates to a goods receipt or an invoice, the field is filled with the. The same field BUDAT is being assigned to 0FISCPER with rule type Time Characteristic as well. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . We have a standard datsource 2LIS_02_SCL for loading the Issued quantity WAMNG against PO. I created a PO with Qty 100 on 03/28/2007 and perfroemd GR on the same day for Qty of 25. Change the PO Qty from 32 to 40 and save the same. Situation: In the business content the update rule of 0PO_QTY is referencing the time characteristic 0SCHED_DATE for 0CALDAY. ATTR . ie: EUR, JPY, USD,INR and all other country currencies. 2LIS_02_SCL Issue. 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). - 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 . In the S/4HANA on-premise edition of SAP Commercial Project Management, the business object 'issue' is referred to as 'issue activity'. Dear All, When I am populating 0PUR_C01 using the InfoSource (2LIS_02_SCL) I am getting multiple entries like if I have one material record for an relevant P. 2lis_45* oliabw rmceneub Document update is where the transaction (documents) are updated in the application tables. your BW System name). If the DataSources are from the LO cockpit, this push takes place either with a direct delta. As you are aware that some fields of the standard extractors gets derived via Calulation (SAP derived logic ) . Tables for 2LIS_02_ITM. BW/BI Accelarator is a tool that improves the performance of BW 7. Data sources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. In the migrated Transformation between InfoSource 2LIS_02_ITM and DSO ZPUR_O01 (Position) I have two rule groups. 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). My predecessor actually changed the standard definition of this. 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.