O Qty is 50 its getting clubbed as 250 in the Cube it has an direct delta FYI, Could you guys throw some light. BUT. It returns also data for goods receipt and invoices if they exist. Ensure that this counter only counts. populate Goods Receipt value and Invoice Receipt. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management:. Hello everybody, I am using datasource 2LIS_02_SCL to extract data into BW. 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. Other terms2LIS_02_ITM, 2LIS_02_SCL, RSA3, RSA7, delta queue, delta initialization,ME21N, MIGO, MIRO, OLI3BW, RMCENEUA. 2lis_02_itm . However, I found 2LIS_02_SCL. Locate your Extractor (Datasource). You will find that value of "LOEKZ" of. 2LIS_02_SCL enhancement - SAP Q&A Relevancy Factor: 1. I went on with the assumption that SCL will capture all events that ITM captures except for Quotations and Contracts (Which my. Please do advise on the below questions. 6. 1. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL. Type . 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 :. 0SUP_PLANT (Supplying Plant) - populated from Structure Field Name. For more information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. i did the setup using one purchase order no(of course I deleted the setup table before did it). Search for additional results. 2lis_02_s012. in 2lis_02_scl and 2lis_02_itm Data Sources. Complete customizing, LBWE setup and Delta initialisation was performed the. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). J_3AKVGR10. Not able to load delta for 2LIS_02_SCL. No. 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. This DataSource provides information about the header data of a purchasing document, such as vendor, purchasing organization, order currency, and so on. Billing Document Item Data SD -Sales and Distribution. Here Loekz field related data is completely not fetching from the above data sources partial data is able to get. All of my changes propogated; the DSOs are now write-optimized;. If the target area is longer or shorter . The data are transfered correctly (maybe!) from Extraction Queue to Delta Queue (daily, the amount of data is almost 1000 a day). 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. Use. In datasource 2LIS_02_SCL, there is only fields BWMNG - that represents quantity, BWGEO and BWGEO that represent values. X 2010/11/01 ZNB F. 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. InfoSource. Is there any standard solution to extract. V . 2LIS_02_SCL. One system it is showing 42 Records Transferred and 8 Added Record in DSO level, and another system is showing 14. Allocation – Confirmation with Schedule Line. I have enhanced the extract structure of 2LIS_02_SCL (MC02M_0SCL) to include a field from the standard pool in transaction LBWE. Apart from the sales orders, 2LIS_02_SCL will give the purchase orders based on stock order transfer. 2LIS_02_SCL. 2LIS_02_HDR EKKO, EKBE,T001, EKPA. 2lis_02_s011. 2lis_02_itm uses EKKO and EKPO tables etc. I tried pulling the data from R/3. g we have in Item 001 quanity 90PC, in Schedule line it will be schedule line wise that is. Same problem i got for Cube 0PUR_C01, for same datasource only i. ALIEF - Number of Deliveries. of DataSources 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_03_BF, 2LIS_03_UM, 2LIS_40_REVAL are not filled. Hi All. Difference Between 2lis_02_itm & 2lis_02_scl. Kindly provide a solution for the below problem whcih i am facing with 2lis_02_itm and scl data sources. Job for collective update stopped (LBWE) 4. About this page This is a preview of a SAP Knowledge Base Article. . RemoteCube Compatibility. Enter t-code : RSA9. 0A. We are executing a delta load from datasource 2LIS_02_SCL and it is. There r 2 ways to get this data. I now am trying to get publishing back on track. Follow. 0AF_COLOR. 2LIS_02_ITM and 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. Load data InfoPackage 2LIS_02_ITM_INIT_R3. Expand in hierarchy structure node Logistics application – 12: LE Shipping BW – Extract structures. Vote up 0 Vote down. so i think i have to use Schedule Line Counter (ETENR) to take the. If the DataSources are from the LO cockpit, this push takes place either with a direct delta. 1 Answer. Key Fields for DSO using 2lis_02_SCL and 2lis_02_ITM. The new DataStore object of Invoice Verification (0LIV_DS01) is supplied with data by the new DataSource 2LIS_06_INV, whereas previously the relevant invoice verification data was only supplied by the three DataSources of Purchasing 2LIS_02_HDR (purchasing data (header level)), 2LIS_02_ITM (purchasing data (item level)), and 2LIS_02_SCL. 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. Thaning you. We make use of extractor 2LIS_02_SCL. 2) can i map 0CPPVLC (BWGEO), instead of 0ORDER_val (BWEFFWR) in the transformation and in routine b/w data source and cube. 5. If the information in this field relates to an event in the purchase order, the field is filled with the posting date of the purchase order. Please help me. MM. DSO. <Delete> Go to edit mode of a PO, select an item and click "Delete". It is field-based and contains all. This extractor was enhanced via an append structure and ABAP in the user exit. The incorrect situation consists in the following. PO delivery schedule lines are first consolidated in an ODS through data from the InfoSources Purchasing Data (Document Schedule Line Level) as of 2. Info cube 2. 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. 2LIS_02_SCL transformation logic. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) ( 2LIS_02_SCL ). 2LIS_02_HDR EKKO, EKBE,T001, EKPA. I know that For purchase order details we used 2 datasources 1. (II) Click on the maintanence tab, pull the fields from communication structure to extract structure based on reporting requirement. The system always converts the net price to the local currency and to the base unit of measure. 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. 2) Now you can selectively fill the setup tables for purchasing related datasources by the T-code OLI3BW. If you select Choose Layout, you have access to all the SAP List Viewers functions. Follow RSS Feed Hi all, What is the source table field name for REWRT (Invoice Value in Local Currency) in DataSource 2LIS_02_SCL, I mean how REWRT is populated. 2LIS_02_SCL - What is the Source table field for REWRT (Invoice Value in Local Currency) 203 Views. To have an understanding about BW DataSource 2LIS_02_SCL for deletion and un-deletion a Purchase Order Item. . SAP Community Network Wiki - SAP NetWeaver Business Warehouse - BW Setup Tables List. In particular every time I schedule the job for. BW SD MM FI 常用 数据源. do not extract the good Invoice receipt quantity for each purchase order. oss note 353042-Howto: Activate transaction key (PROCESSKEY) may also useful. LIS_ITM is meant for item level information e. 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. Also can i avoid using 2LIS_03_BF for GR's by enhancing 2LIS_02_SCL with MBLNR(GR doc no) from EKBE. 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. VRTKZ – Distribution Indicator for Multiple Account. MM-PUR: Purchase Data Account Level (2LIS_02_ACC) - /IMO/PUR_IS13. adjusts the quantities to give the true 'open/closed' qty after GR. Now we realize that processkeys 010 are missing but 2LIS_02_ITM catches these. We have attached 3 source systems to our BW and 2 of them are working absolutely without problems. Specifically I am looking at the BWVORG field. As per the BI content online documentation for an info source 2LIS_02_SCL, Set up table for purchasing application needs to be recreated. Demo - Generate and Extract delta data . Line 40 had been entered. This extractor also brings data from Goods receipts and Invoice Receipts which typically come from EKBE table. BW SD MM FI 常用 数据源. From this data source data is storing in two data targets 1. 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). Thanks for the advice. Please share your ideas on this data source setup. For e. The Field (CHARG) not hidden. When I extaract data, I get 2 records. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/PUR_IS12. First time in the Initial update and seond time in the delta update. First activate the data source in RSA5 and check it in RSA6 (active data sources are available here). I am using Key figure BWGEO BW:CValLocCrcy & BWGEOO BW: CValOrdCrcy with summation. i. Step 2 Goto LBWE transaction in R/3. 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. we have problems with extractor 2lis_02_scl in delta data extraction. Type of DataSource. The logic says: umren EQ 0. DataSource: 2LIS_02_SCL. The system only calculates this delta if a purchase order item is completed. Then save, check and activate the process chain and provide information, where applicable, about which server the process chain should be scheduled on. you can get the records by running the extraction of 2LIS_02_SCL in RSA3. Deletion indicator not appearing in 2lis_02* extractor . For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. We discovered for once GR 2LIS_02_SCL always presents 2 lines with almost same data execpt field ROCANCEL equals 'X'. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 2LIS_13_VDKON:. i. The evaluation level relates to the common characteristics in this area, such as material and vendor. 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. SAP Knowledge Base Article - Preview. "Hi, we need to track the modifiations of the PARVW (Role Partner) when it is changed in a Purchasing document. Strangely when we load data using delta mechanism, we are not getting the correct updated 'issued quantity' . Extraction job in R3 is unable to extract any data, so it . Line 30 had been entered and totally delivered. Once I do that, I am able to extract data for an info source 2LIS_02_SCL. FIP Material Number 0SR_VE_INT_IV . Why are the setup tables not filled?Our delta queue for 2LIS_02_ITM and 2LIS_02_SCL was deleted from R3 by mistake. Genrally BWMNG is mapped with 0CPQUAOU. If successful, 4. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. Go to. 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. Description . The outbound queue is filled for the following queues in the. SBIW > Application specific datasources> Logistics > Settings for. Visit SAP Support Portal's SAP Notes and KBA Search. In the transfer rule, there is a coding to check on process key in 2LIS_02_SCL. Use. 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;. ekko -waers . 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. Therefore, the values for PO Qty, GR Qty and Invoice Qty (and their corresponding value KF's) appear to be. There is a standard SAP DSO 0PUR_DS03 which is getting data from 2LIS_02_SCL. What i knew is, this type of data we will get from 'Purchasing Data (Schedule Line Level). Determine Industry Sector. Transfer struct. cpquaou is mapped to BWMNG which is the PO quantity "not the OPEN PO. 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) 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. Why are the setup tables not filled?The data is not updated into the upur_c01 cube . 2. Thanks, Bobby. It mentions BWVORG assumes a value based on the "purchase item type, processed document and purchasing order type". However, InfoCube for Purchasing ( 0PUR_C01) is already active in the system and delta are being loaded into it on a regular. 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. Check the PO in ME23n for Order qty. Technical name: 2LIS_12_VCITM. Some key figures in the data source need to be updated in an additive process. not ectract the good Invoice receipt quantity. Your LIS_SCl will contain the schedule line information that is if somebody wants schedule date wise e. 2lis_02_scl and 2lis_02_itm - SAP Q&A Relevancy Factor: 1. th einfo object may be the same but there is a big diffrence . a few weeks ago delta in BW stopped working. 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. Symptom. 1)2LIS_03_BX : BWMNG,BWAPPLNM, BSTAUS ,BSTTYP. . goods tab > invoice number field. I am using logistick Cockpit Extraction and in particular 2LIS 02 ITM. 2867285-2LIS_02_SCL : extracts more schedule lines than table EKET. Due to failre in purchase related datasource. I can create correctly the init update but I have problems with the. But these datasource read data from EKKO,. Search for additional results. 0 I've activated the extractors 2lis_02_scl and 2lis_02_itm, when I do the initalitation in the setup tables I don't see any record also if in the execution log there are 7230 documents. e. And one question concerning purchase data. e 04/21 I did delta update. goods tab > invoice number field. This is regarding finding out the Extractor Logic (Fuction module ABAP logic ) for few of the standard extaractors fields in sap ecc side. This counter determines the number of deliveries based on the GR document items. During the initial load, everything comes along fine all the way to PSA. Schedule Line Level: DataSource 2LIS_02_SCL -> InfoSource 2LIS_02_SCL -> DSO ZPUR_O02 (Schedule Line Level) -> InfoCube ZPUR_C01. 但是系统字段：交货单号（ ekbe-belnr ），参考凭证号（ekbe-xblnr ）没有。如果不做增强， 在其它数据源上是否有这二个字段？我找了采购，销售的都没有这二个字段，可能我还没有找对，麻烦各位高人帮指点。 谢谢. You will find that value of "LOEKZ" of. The field is BADAT [Requisition (Request) Date]. This DataSource provides the BW with data from the Sales area and supplies the InfoSource 2AF_SD_SHP_1 with data. Sent Job ABORTED update to SAP. SAP BW Datasource : 2LIS_02_SCL - Purchasing Data (Schedule Line Level). 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. 0 Flow or 3. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). 2LIS_03_UM: Revaluations MM - Materials Management: 6. Has searched many threads from the forum but unable to find perfect solution. 02 in LBWE. RSS Feed. 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. Logic of Datasource 0INFO_REC_ATTR . B. 2LIS_02_CGR: Produced Activity: Delivery of Confirmations: MM - Materials Management: 2LIS_03_BF: Goods Movements From Inventory Management: MM - Materials. I needed to analyse contents PSA of the table of a Datasource "2LIS_02_SCL". 24. May 21, 2012 at 04:31 AM. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2lis_02_hdr. MC02M_0SCLSETUP. We are getting '0' instead of the correct quantity, but when we do full load at the end of the month we get. 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). You can use this InfoSource to evaluate delivery services. If successful, 5. I created a PO with Qty 100 on 03/28/2007 and perfroemd GR on the same day for Qty of 25. RSA3. Hi, It is calculated through Function module. Name. Now the problem is, I could see FEW records getting posted twice (duplicated) in PSA. I had a requirement to make two Purchasing DSOs (2LIS_02_ITM & 2LIS_02_SCL based) write-optimized. When checking the OMJJ transaction, the 103 and 104 movement types are marked. 0FIPMATNR_ATTR . g for one item 001 u have quantity 90PC. Tables for 2LIS_02_ITM. Currently, when I load the Setup table for Purchase application, I don't have any record for that kind of purchase order though I have standart PO. in any of the tables. <i>Note : I do no selection in my infopackage. Step 2 : Activate and transfer the Application Component Hierarchy(One Time Activity in the project). 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. 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. ZPUR_C01) and modify with any from the header that is needed. 2LIS_02_SCL not extracting field EKPO-LOEKZ. In the ECC table EKET these two fields have changed for a given purchase order but the change is not added to the delta queue. 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. AFS Grid Value. in 2lis_02_scl and 2lis_02_itm Data Sources. 1 Answer. 2013 through transaction code SMQ1. The standard purchasing info objects in BW for storing the subtotals are 0SUBTOT_OC1 –. 2LIS_02_SCL EKKO, EKBE,T001, T001W, EKET, EKPA. BW SD MM FI 数据源. 0AF_DEPTM. 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. V . Delta Update. BWA / BIA. 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. Thanks and regards. 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). 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. includes tables like ekko/ekpo/ekbe etc. 2. 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). When i have GR reversal , Movement Type 102. Use. <b>Table Field</b> eket -menge . Status . I am working on Purchasing Datasource (2LIS_02_ITM & 2LIS_02_SCL) I came to know that, Open PO’s is identified based on the field EKP0-ELIKZ. It looks to me, that it provides information about, whether it. Type of DataSource. Thank you all four you responses. InfoObject. as the data in that dataset. I need to add some Z custom fields in BW datasource 2LIS_02_ITM which we are doingby appending in structure MC02M_0ITM. No. result =. In R/3- Enhance the SCL extractor by adding the ZZ. ie: EUR, JPY, USD,INR and all other country currencies. Company code. - Normal purchasing order - BWVORG = 001. RUN Init. Note: As an alternative you can also use DHCDCVCDSEXTRE in SE16 which contains more or less the same information. 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). Load data InfoPackage 2LIS_02_SGR_INIT_R3. 1) what are the difference b/t them. 2LIS_02_ITM EKKO, EKBE,T001, T001W, EKPO, TMCLVBW, T027C, ESSR, T147K,. It contained the delta queues as. 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”. In the transformation start routine, I could see alogic which is barring some records to DSO. Extractor 2LIS_02_SCL --> behaviour when ELIKZ is set. "Document data restriction" when filling setup table. 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. and he has managed to laod data using full upload without. I am still finding out which of these extractor needs to be modified. "Image/data in this KBA is from SAP internal systems. J_3ADEPM. Available from OLTP Release. where this is using a standard datasource 2LIS_02_ITM and 2LIS_02_scl and i have acitvated this standard cube 0pur_c01. And below I am giving the job log details of ODS activation. - Process Key 003:IR. Depending on the process key field BWVORG, the data may be coming from EKET or EKBE. "MCEX_UPDATE_02_V1" "(FORM)", or declared in the procedure's RAISING clause. 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. Explanation of Note 578471 - Deleted positions in BW and statistics . 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. Among the fields that were appended are fields EKKO-BUKRS and EKPO-LOEKZ. I am loading the data form the 2LIS_02_SCL datasource to the DSO in BI. 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. 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. The information in this field indicates the difference between the purchase order quantity and the goods receipt quantity in the base unit of measure. 3. Record count in RSA3 and PSA is different. Department. As much as I understand the key fields which I should be using are EBELN Purchasing Doc. you can get the records by running the extraction of 2LIS_02_SCL in RSA3. 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. Has searched many threads from the forum but unable to find perfect solution. - 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 . infoobject are overwritten in the ODS. Pls reply needed urgent,i'm. However, my delta infopackage is not picking up any new records. ekbe -wrbtr . But i want know like, how we can show the Open PO Value & Open PO Qty in the BI report level. Or if you are looking for OSS NOte # 353042. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. but do not understand the delta behavior. ANLH: Main Asset Number. 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 . 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. Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04. Your LIS_SCl will contain the schedule line information that is if somebody wants schedule date wise e. 2LIS_02_SCL. I created an ODS object with the following fields as a key. 2lis_03_bx. I have compared BW data with SAP R/3 using tcode ME80FN and data seems to be consistent. As when we pull BUDAT(posting date) in 2lis_02_scl it depends on the transaction key. 2LIS_02_SCL Issue. MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. 2LIS_02_SCL EKKO, EKBE,T001, T001W, EKET, EKPA. I made my changes in the development environment and transported them to QA. We are doing a delta update. Settings: Purchasing. Marco. This InfoSource contains the quantity that was delivered for each schedule line in a delivery item. Attached is the flow i installed. ie: EUR, JPY, USD,INR and all other country currencies. 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. Inventory Controlling (application 03): 2LIS_03_BX. Search for additional results. RemoteCube Compatibility. However after full loading, you notice. This update is normally a synchronous update, i. apart from process key is there any. Application Component. 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.