This extractor also brings data from Goods receipts and Invoice Receipts which typically come from EKBE table. Transaction LBWQ in ECC: MCEX02. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. 2LIS_03_UM: Revaluations MM - Materials Management: 6. 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. This DSO is filled by the InfoSource MM-PUR: Purchase Data Item Level (2LIS_02_ITM) (/IMO/PUR_IS11) to provide general information on the principal agreement. 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. It is field-based and contains all. However, if I use MIGO to do a goods receipt on the already initialize-loaded PO's, no delta for 2LIS_02_SCL is. Below is a list of frequently asked questions about Logistic DataSource setup table filling: Setup table (or RSA3 result) is empty even though you executed transaction OLI*BW to fill it. Monica. 2) can i map 0CPPVLC (BWGEO), instead of 0ORDER_val (BWEFFWR) in the transformation and in routine b/w data source and cube. DBWMNG - Delta for Purchase Order Quantity/Goods Receipt Quantity in Base Unit of Measure. The ODS which in our system has the 0PROCESSKEY as one of the key fields. MC02M_0SGR Storage. clear wa_package. Hit enter to search. 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. Comparing DataSource 2LIS_02_SGR to ME80FN. 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. We are using two PO extrctors 2LIS_02_ITM & 2LIS_02_SCL to load data, both are working fine. My question is if anyone of you have come across this issue? If yes how was it resolved. 1)2LIS_03_BX : BWMNG,BWAPPLNM, BSTAUS ,BSTTYP. Based on DataSource: 2LIS_02_SCN. But it is fetching 0 data with green status. LIS_ITM is meant for item level information e. Make sure at least one of the below data sources belonging to purchasing application is activated in transaction LBWE, 2lis_02_acc / 2lis_02_hdr / 2lis_02_itm / 2lis_02_scl. This DataSource provides information about the distribution of goods receipt quantities to the confirmation quantities. Francisco Milán Campos. <i>Note : I do no selection in my infopackage. Enter t-code : RSA9. Please help. Released . so i think i have to use Schedule Line Counter (ETENR) to take the. AFS 3. The additional field is not filled when you check the delivered data on BW side. Solution : Prerequisite: Make sure all your datasources are active in LBWE. there is a routine for the PO open quantity 0BO_QTY as follows: RESULT = COMM_STRUCTURE-cpquaou * COMM_STRUCTURE-numerator / COMM_STRUCTURE-denomintr. I used the datasource 2LIS_02_SCL to get the purchase data . From the business content, in the update rule: 2LIS_02_SCL -> 0PUR_DS03. 2LIS_02_SCL extractor does not always fetch data from EKET table. Why are the setup tables not filled?The data is not updated into the upur_c01 cube . doc / . 2. 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. In datasource 2LIS_02_SCL, there is only fields BWMNG - that represents quantity, BWGEO and BWGEO that represent values. MC02M_OSCL. The information under these fields are dependent from the information of field BWVORG (BW transaction key). Depending on the process key field BWVORG, the data may be coming from EKET or EKBE. 5. MCBO -Transaction key active or not. Choose New Data Connection. From this data source data is storing in two data targets 1. The Field (CHARG) not hidden. 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. Hello everybody, I am using datasource 2LIS_02_SCL to extract data into BW. i. - Process Key 002:GR. 2lis_02_scl and 2lis_02_itm - SAP Q&A Relevancy Factor: 1. 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. 3. Available from OLTP Release. When you use service-based invoice verification (EKPO-LEBRE) the extractor 2lis_02_scl. 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. The Select Data Source page appears. Use. 但是系统字段：交货单号（ ekbe-belnr ），参考凭证号（ekbe-xblnr ）没有。如果不做增强， 在其它数据源上是否有这二个字段？我找了采购，销售的都没有这二个字段，可能我还没有找对，麻烦各位高人帮指点。 谢谢. O Qty is 50 its getting clubbed as 250 in the Cube it has an direct delta FYI, Could you guys throw some light. SAP Community Network Wiki - SAP NetWeaver Business Warehouse - BW Setup Tables List. VRTKZ – Distribution Indicator for Multiple Account. 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). MM. The field 2lis_02_ITM-AKTWE give the good GR Quantity for services but do. 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. SCL_BEDAT is obviously updated in the extractor with field EKET-ETBDT which is the so called "Order Date". The data of this extractor needs to be used to measure a supplier service sevel based upon single schedule lines. Something likes: 2010/11/01 ZNB F 4500000030 610. AFS 3. On RSA 3 when i check out the extraction for the PO, i find that there are 2 extra (-)negative records (ROCANCEL='R') for the. and he has managed to laod data using full upload without. Visit SAP Support Portal's SAP Notes and KBA Search. Comparing DataSource 2LIS_02_SCL to ME80FN. Choose. "MCEX_UPDATE_02_V1" "(FORM)", or declared in the procedure's RAISING clause. LBWE u2013 activate in option 02 your datasource, follow the right sequence. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. Can you please guide me through! Thanks, Ram. I will analyse notes 459517, 728687, 722339 y 869628. I had a requirement to make two Purchasing DSOs (2LIS_02_ITM & 2LIS_02_SCL based) write-optimized. By default, either of these does not capture changes to a transaction field in VL32N > Item > foreign trade/customs tab > Invoice accomp. (BANFN) and. I am using standard extractor 2LIS_13_VDITM and 2LIS_02_SCL. 5. datasource 2lis_02_scl. Please share your ideas on this data source setup. if the update does not go through for whaterever reason, the complete transaction is rolled back. We implemented 0PUR_C01 (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. Go to. WKURS – Exchange Rate. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. When i extract a Invoice receipt in delta : (0processkey = 3). Data sources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. InfoSource. 2LIS_02_HDR EKKO, EKBE,T001, EKPA. calculation logic for field BWMNG in 2lis_02_scl - SAP Q&A Relevancy Factor: 1. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 2LIS_13_VDKON:. Tables for 2LIS_02_ITM. The following jobs move the data from the outbound queue to BW. Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. KNTTP – Account Assignment Category The account assignment category determines the account assignment data for an item, such as cost center and account number. 2. 26. 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. Specifically I am looking at the BWVORG field. I don' t understand because there are many records in EKPO and EKET for STO (document range. if anyone knows tcodes for runinng the set uptable to each data source separatley. Some are transparent, some are reference, but there are one or two that stand out here. 2LIS_02_CGR: Produced Activity: Delivery of Confirmations: MM - Materials Management: 2LIS_03_BF: Goods Movements From Inventory Management: MM - Materials. When i investigated using RSA3 extraction for 2LIS_02_SCL and singled out the problamatic PO i found that. e: if ELIKZ = X , delivery completed else it is an open PO. It appears that many of the key figures are updated based on logic relating to the BW Processing Key. With this setting I have to take downtime in R/3. Check details in below T codes: BF11- check box required for BW. 2867285-2LIS_02_SCL : extracts more schedule lines than table EKET. . I can create correctly the init update but I have problems with the. Delete the setup data (LBWG) 2. For more information, refer to the. Best Answer. 2LIS_02_CGR Produced Activity: Delivery of Confirmations MM - Materials Management: 27 : 0CO_OM_WBS_4 wbs element s: Statistical key figuresSAP Help, Wiki, Q&A and other resources for 2LIS_02_HDR Click here for the full list of resources and help pages, only the first few are posted below . 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. TRAN . To have an understanding about BW DataSource 2LIS_02_SCL for deletion and un-deletion a Purchase Order Item. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. Requires; Object Type. A problem or project situation that affects project goals. 2016-01-05 02:11:43 Received: 2LIS_02_SCL, Id: 17, rows: 50275, Total rows: 218842. No. The keys of this DSO are PO Number, PO Item and Schedule Line number. ALIEF - Number of Deliveries. Please also specify what is the way to find out it. I am still finding out which of these extractor needs to be modified. Use. Genrally BWMNG is mapped with 0CPQUAOU. 2. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. The Info Package which indicates that an x amount of records were transferred but not received, got a timeout and was restarted just to bring in zero records in the delta. InfoSources 2LIS_12_VCHDR , 2LIS_12_VCITM , and 2LIS_12. As when we pull BUDAT(posting date) in 2lis_02_scl it depends on the transaction key. 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. Available from OLTP Release. I am unable to figure out why this fields is not populated. If any entries are available then trigger the equivalent Info. if you put EKET then it brings up. Both the datasource do not have Material document number (BELNR) field. ANLH: Main Asset Number. 2LIS_02_SCL not extracting field EKPO-LOEKZ. You can use this InfoSource to evaluate delivery services. process key for infosource 2LIS_02_SCL. Visit SAP Support Portal's SAP Notes and KBA Search. That is the way SAP provides extractor fields. 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. 2lis_02_cgr . But when we have an Invoice Receipt the 2lis_02_scl puts WEMNG and WERT field blank while REMNG and REWRT are populated correctly. AFS Grid Value. I has chosen required request and has pressed button. 2lis_02_scn. LBWE u2013 activate in option 02 your datasource, follow the right sequence. includes tables like ekko/ekpo/ekbe etc. 24. Among the fields that were appended are fields EKKO-BUKRS and EKPO-LOEKZ. 1) these extractors don't appear to have the same data. 2. i. Features of Extractor. I used rsa3 to validate these 2 fields against EKET table, the Received Qty is not correct. J_3ASIZE. 0. This InfoSource contains the quantity that was delivered for each schedule line in a delivery item. 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. Has searched many threads from the forum but unable to find perfect solution. 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. BW SD MM FI 数据源. Note that if you change a purchasing document, the. 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. Your LIS_SCl will contain the schedule line information that is if somebody wants schedule date wise e. We are doing a delta update. 2016-01-05 02:12:26 NOT all Rows are received yet: 2LIS_02_SCL. 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. Record count in RSA3 and PSA is different. I have already maintain datasource 2LIS_02_ITM through LBWE. If you choose the Delivery Schedule Lines view in the transaction ME80FN, you can compare the data in the DataSource fields with the original document data in SAP R/3, such as: · Purchasing Document Number (EBELN) · Item Number of Purchasing Document (EBELP) · Item delivery date (SCLDT)Technical name: 2LIS_02_SCL. SAP. 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. So 2LIS_02_SCL gives more informations. Once I do that, I am able to extract data for an info source 2LIS_02_SCL. ATTR . MM Data Sources Tables Purchasing. This counter determines the number of deliveries based on the GR document items. I have a problem with 2LIS_13_VDITM delta. - Cross company order -. 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. Vendor. Bei Einkaufsbelegen, die in einer anderen als der Hauswährung angelegt wurden oder zu denen Belege wie z. 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. Technical name: 2LIS_02_SGR. 2LIS_02_SCL that the process key for corresponding transcation be '05' or '06'. LE key figures for the delivery item: This InfoSource contains information that relates to the delivery item, such as delivery quantity in sales units or delivery quantity in the base unit of measure. check step by step. Likewise proceed with all the extractor. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW >. PSA in BW. When I extaract data, I get 2 records. I need to load data into purchasing data cube (0PUR_C01) from two standard data sources: 2LIS_02_ITM and 2LIS_02_SCL. the situation is that when I run delta it fetches 0 records. I never used 2LIS_02_SGR, but following the documentation it gives returns data related for goods receipt. Load data InfoPackage 2LIS_02_SGR_INIT_R3. 2lis_45* oliabw rmceneub Document update is where the transaction (documents) are updated in the application tables. We had at this point realised there is no Delta on the Purchase cube(New). 2) Include these fields in the Extract structure in LBWE (Maintain Extract structure) 3) Implement the User exit called: LEINS001 - Statistics update - purchasing documents. This field determines whether these values are from a purchasing order, goods receipt or an invoice. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . I am extracting data from 2LIS_02_SCL. 2013 through transaction code SMQ1. An issue may result in changes to scope, budget, timeline, or resources. 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. enabled:true in the Search box and press Enter. e. 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. To confirm the delta queue, Check the SMQ1 transaction code if any Queue Name start with MCEX** or Destination BWCLNT*** (i. However in the S/4HANA system, table KONV is obsolete and replaced by table. and enhanced the datasources ITM and SCL adding one Char in RSAP0001 using user exist EXIT_SAPLRSAP_001 . Load data InfoPackage 2LIS_02_ITM_INIT_R3. As you are aware that some fields of the standard extractors gets derived via Calulation (SAP derived logic ) . 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’. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. ) 2LIS_02_SCL & 2. If successful, 3. I created a PO with Qty 100 on 03/28/2007 and perfroemd GR on the same day for Qty of 25. 2lis_02_itm . 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). Thanks and regards. BUT. This counter determines the number of deliveries based on the GR document items. 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. ENDLOOP. Q3: I just want to confirm that if I go with 2LIS_02_S011, these steps are not necessary. Apparently these two fields are NOT updated in BW from a delta load. Vote up 2 Vote down. I also know that my InfoSources for this data are 2LIS_02_HDR, 2LIS_02_ITM, and 2LIS_02_SCL. for Infosource 2lis_02_scl - 10 : MCEKET: Purchasing Document Delivery Schedule MM - Purchasing Information System: Structure 11 : MC02M_0SCLSETUP: Storage BW Setup for MC02M_OSCL Logistics - Logistics Information System (LIS) Transparent Table 12 : TMCLVBW: Transaction Key for SAP BWWe consider to use 2LIS_02_SCL to extract schedule line data but after examining the data we got, a confused result occurs. Transactional Data. Purchasing 2LIS_02_SCN MC02M_0SCNSETUP BW-Rebuild for. here give the PO numbers, specify a name for the job run and execute. 2LIS_02_SCL returns data for the purchase order on header item and schedule line level. 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. here give the PO numbers, specify a name for the job run and execute. The EKET (Purchasing Schedule Line) table doesn't have this. But in BI 7. We created an ODS object for purchasing schedule line items where my key fields are PO Doc#, PO Item#, PO Schedule Line # and Fiscal year variant. 2016-01-05 02:11:55 NOT all Rows are received yet: 2LIS_02_SCL. Now we realize that processkeys 010 are missing but 2LIS_02_ITM catches these. To prevent the exception, note the following: A dataset can only be imported to a target area with the same structure . 0B (2LIS_02_SCL) and Offsetting Confirmation and Goods Receipt (2LIS_02_SGR). Once the setup table filling is done. I have loaded data into 0PUR_DS03 from datasource 2LIS_02_SCL , I have done the Initiail load successfully and also the delta load successfully (receive the new data into 0PUR_DS03) >> It's OK. Controlling 2LIS_03_BF MC03BF0SETUP. Allocation – Confirmation with Schedule Line. 2. 2LIS_02_SCL Issue. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. (table EKPA). 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). Marco. 0AF_CGR10. However, when. check in start routine/update/end routine for any filters. Hi All, Can you please share your experience on the 2LIS_02_ACC data source setup. BNKA: Master Records of banks. Problem with MCEX_UPDATE_02 COLL. 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). A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!Activate data source of Appl. Extraction job in R3 is unable to extract any data, so it . And below I am giving the job log details of ODS activation. g. ) 2LIS_02_ITM. 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. Setting the Layout. J_3AKVGR10. I have some strange problem in R/3. They also extract GR and IR. 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. am working on a new report based on a view which. We discovered for once GR 2LIS_02_SCL always presents 2 lines with almost same data execpt field ROCANCEL equals 'X'. ALIEF - Number of Deliveries. not ectract the good Invoice receipt quantity. 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. Hi, I have activated and loaded data in datasource 2lis_02_scl. 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. From ITM all fields available are needed and from SCL requisitioner (AFNAM), purchase reg. - 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. I am activating structure. failing. 2LIS_03_UM. we have problems with extractor 2lis_02_scl in delta data extraction. 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. 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. In particular every time I schedule the job for. I am still finding out which of these extractor needs to be modified. Fill the set up tables. BWA / BIA. Demo - Generate and Extract delta data . Visit SAP Support Portal's SAP Notes and KBA Search. Fill the set up tables. To ingest data from an SAP S/4HANA data source, perform the following procedure. fields in 2LIS_02_SCL. Deletion indicator not appearing in 2lis_02* extractor . 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 7 : 2LIS_13_VDITM Billing Document Item Data SD - Sales and Distribution: 8 :Hi SAP USER. ekpo -meins . Similarly Now Check for the Data Source 2LIS_02_ITM Now Check for the Data Source 2LIS_02_SCL Go to Tcode SM13 (update Request) Go to ME21N (creating Purchase Order) Go to SMQ1 (Queue Status). ekko -waers . When a purchase order item confirmed, even though this filed is not changed. I created an ODS object with the following fields as a key. 1. 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. Help. 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. Load data InfoPackage. Then use the function Activate and Schedule to start the process chain according to your scheduling options. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/PUR_IS12. When we do the reconciliation with MC$4, some. 2LIS_02_ITM EKKO, EKBE,T001, T001W, EKPO, TMCLVBW, T027C, ESSR, T147K,. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) ( 2LIS_02_SCL ). It is actually a calculated result (rounding) in 2LIS_02_SCL and 2LIS_02_ITM. 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. 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 :. 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_acc 中找到了交货单，没有记录，所以认为不是在这个数据源。 2lis_06_inv 有reference 这个字段，但内容值对不上。Purchasing (application 02): 2LIS_02_ITM. but do not understand the delta behavior. 2LIS_02_SCL. 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 7. You will find that value of "LOEKZ" of. 2LIS_02_SCL - What is the Source table field for REWRT (Invoice Value in Local Currency) 203 Views. The following has all been done. This InfoSource contains the structure to provide purchase accounting data on item level into the EDW Core Layer. I made my changes in the development environment and transported them to QA. Lost while creating the. WKURS - Währungskurs. BW SD MM FI 常用 数据源. g. I am facing following problem with above extractor. 1) what are the difference b/t them. Unfortunately data doesn't. . 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. Please do advise on the below questions. SAP Knowledge Base Article - Preview. The Posting date (BUDAT) from the 2LIS_02_SCL is being assigned to 0CALDAY with the rule type specified as Time Characteristic. Use. The information in this field indicates the difference between the purchase order quantity and the goods receipt quantity in the base unit of measure. Former Member. values. As you konw, When R/3 system doesn't make any transaction data, we can fill the setup table. 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. 0SUP_PLANT (Supplying Plant) - populated from Structure Field Name. Line 40 had been entered. ME23n – PO Qty. 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;. 0.