For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. result =. This DataSource provides the BW with data from the Sales area and supplies the InfoSource 2AF_SD_SHP_1 with data. Also can i avoid using 2LIS_03_BF for GR's by enhancing 2LIS_02_SCL with MBLNR(GR doc no) from EKBE. You may choose to manage your own preferences. Steps: 1. then check in data target. Now, the 2LIS_02_SCL becomes zero by default. 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;. 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. We have a standard datsource 2LIS_02_SCL for loading the Issued quantity WAMNG against PO. e 04/21 I did delta update. in both the bw systems. actually my purchase relevant data are as follows: 21 reordes of order item ,78 reocords of order. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2LIS_02_ITM EKKO, EKBE,T001, T001W, EKPO, TMCLVBW, T027C, ESSR, T147K,. Fill the set up tables. 1) what are the difference b/t them. Comment . Now we realize that processkeys 010 are missing but 2LIS_02_ITM catches these. 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. We are using two PO extrctors 2LIS_02_ITM & 2LIS_02_SCL to load data, both are working fine. Rechnungen in einer anderen Währung gebucht wurden, gibt der Inhalt dieses Feldes. 以下是SAP ECC中各主要数据源与描述. BNKA: Master Records of banks. SCL_BEDAT is obviously updated in the extractor with field EKET-ETBDT which is the so called "Order Date". 02 in LBWE. Data Modeling. Since I know I am working with Purchasing data those are my obvious choices. I'm trying to reconcile a record produced by the 2LIS_02_SCL datasource back to the base R/3 tables. MC02M_0ITM: Extraction Purchasing (Item) for DataSource 2LIS_02_ITM. X 2010/11/01 ZNB F. g. The Posting date (BUDAT) from the 2LIS_02_SCL is being assigned to 0CALDAY with the rule type specified as Time Characteristic. 2016-01-05 02:11:46 rqState 9: Reported complete by SAP, id: 17. 2) can i map 0CPPVLC (BWGEO), instead of 0ORDER_val (BWEFFWR) in the transformation and in routine b/w data source and cube. Go to Maintainance. 2LIS_02_SCL. 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. Thank you all four you responses. 1) these extractors don't appear to have the same data. 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 :. KEKO: Product Costing Header Data. 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. Purchasing 2LIS_02_SGR MC02M_0SGRSETUP BW-Rebuild for. do not extract the good Invoice receipt quantity for each purchase order. Once I do that, I am able to extract data for an info source 2LIS_02_SCL. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 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. The counted number depends on how often a material appears in a GR document. However after full loading, you notice that more schedule line records are extracted by Datasource 2LIS_02_SCL. As when we pull BUDAT(posting date) in 2lis_02_scl it depends on the transaction key. 2LIS_02_SCL. I needed to analyse contents PSA of the table of a Datasource "2LIS_02_SCL". 2016-01-05 04:11:47 NOT all Rows are received yet: 2LIS_02_SCL. 2. Save BW. PO delivery schedule lines are first consolidated in an ODS through data from the InfoSources Purchasing Data (Document Schedule Line Level) as of 2. Problem: Setup tables are not getting populated for 2lis_02_hdr, 2lis_02_item. enabled:true in the Search box and press Enter. Inconsistent Delivery Date in BW after extraction using datasource 2LIS_02_SCL from ECC table EKET Delivery date EINDT in DataSource 2LIS_02_SCL does not match ECC data. Determine Industry Sector. I tried to install it separately from BI Content but could not find transformation or transfer rule related to Cube 0PUR_C01. In our case, the filling setup table, it took normally over 1 days. Vendor Supply Information. 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. 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. You will find that value of "LOEKZ" of. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. missing, lost, loss, 2lis, queue, delta, aim, aimd, abr, addd, newd, 2lis_02_acc, 2lis_02_cgr, 2lis_02_hdr, 2lis_02_itm, 2lis_02_scl, 2lis_02_scn, 2lis_02_sgr, 2lis. Company code. This DataSource provides information about the distribution of goods receipt quantities to the confirmation quantities. Type of DataSource. It's almost impossible to get the chance ( when korea plant rest, another plant still running. Reorganization for. Please share your ideas on this data source setup. Status . About this page This is a preview of a SAP Knowledge Base Article. if anyone knows tcodes for runinng the set uptable to each data source separatley. 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. Symptom. Key Fields for DSO using 2lis_02_SCL and 2lis_02_ITM. I have a question. - Process Key 001:PO. ALIEF - Number of Deliveries. Choosing any numbers 1 – 6 will populate the corresponding EXPO KZWI 1 – 6 fields. 2016-01-05 02:12:26 NOT all Rows are received yet: 2LIS_02_SCL. Check the PO in ME23n for Order qty. before image; #; . 1)2LIS_03_BX : BWMNG,BWAPPLNM, BSTAUS ,BSTTYP. 6. Technical name: 2LIS_02_SGR. WKURS - Währungskurs. In datasource 2LIS_02_SCL, there is only fields BWMNG - that represents quantity, BWGEO and BWGEO that represent values. Customer Group 10. 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. in 2lis_02_scl and 2lis_02_itm Data Sources. I know that For purchase order details we used 2 datasources 1. Help needed, with detailed step would. InfoSource: /IMO/PUR_IS12. 1. Setting the Layout. J_3ABWEL_COLOR. I'd like to extract Stock Transfer Orders (MM documents) by using DS 2LIS_02_SCL. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. Our users are complaining, because they expect it to match up. 中都找不到，在提取结构中也没有发现。 在2lis_02_acc 中找到了交货单，没有记录，所以认为不是在这个数据源。 2lis_06_inv 有reference 这个字段，但内容值对不上。Purchasing (application 02): 2LIS_02_ITM. The data records for. Step 2 : Activate and transfer the Application Component Hierarchy(One Time Activity in the project). BW/BI Accelarator is a tool that improves the performance of BW 7. Technical Data. Bei Einkaufsbelegen, die in einer anderen als der Hauswährung angelegt wurden oder zu denen Belege wie z. The subtotal amounts are extracted in PO currency. RSS Feed. SAP Community Network Wiki - SAP NetWeaver Business Warehouse - BW Setup Tables List. LIS_ITM is meant for item level information e. 2LIS_02_CGR: Produced Activity: Delivery of Confirmations: MM - Materials Management: 2LIS_03_BF: Goods Movements From Inventory Management: MM - Materials. 2867285-2LIS_02_SCL : extracts more schedule lines than table EKET. goods tab > invoice number field. 2LIS_02_SCL transformation 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’. We are executing a delta load from datasource 2LIS_02_SCL and it is. 1) what are the difference b/t them. As per the BI content online documentation for an info source 2LIS_02_SCL, Set up table for purchasing application needs to be recreated. Namely Purchasing Document Header EKKO and Purchasing Document Item EKPO. When you use service-based invoice verification (EKPO-LEBRE) the extractor 2lis_02_scl. 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. BW SD MM FI 常用 数据源. I have a question. RemoteCube Compatibility. Hi, I have activated and loaded data in datasource 2lis_02_scl. If the target area is longer or shorter . Likewise proceed with all the extractor. 2lis_02_sgr. 以下是SAP ECC中各主要数据源与描述. Use. Step one: stop all postings in connected ERP system. png. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 7. 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. This counter determines the number of deliveries based on the GR document items. For one PO (Purchasing Order) there're 1 record in schedule line table EKET. MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. RSS Feed. There r 2 ways to get this data. Then save, check and activate the process chain and provide information, where applicable, about which server the process chain should be scheduled on. 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. 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. BW SD MM FI 常用 数据源. Comp. Due to some reason we have to fill up set up table for Purchasing (2LIS_02_ITM and 2LIS_02_SCL) again: These tasks have to been done: 1. For e. It mentions BWVORG assumes a value based on the "purchase item type, processed document and purchasing order 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 :. LIS_ITM is meant for item level information e. Transactional Data. Step 1: Get the name of tables affected by the lost delta data source. Here is a list of the values that process key - BWVORG can assume, according with the purchasing item type, processed document and purchasing order type: 1 - For non return items: a) Document type: Purchasing order. MC02M_OSCL. 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). 2LIS_03_UM: Revaluations MM - Materials Management: 6. 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). Technical Data. VRTKZ – Distribution Indicator for Multiple Account. I now am trying to get publishing back on track. 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. I add the following fields REMNG /REWRT/ WEMNG /WEWRT in the LO cockpit. 2. The 2 datasource aren't loading the same information. They are then using the Exchange rate from the PO Header. 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. ME23n – PO Qty. When i am extracting same datasource in source system and able to see data. Use. We are using two PO extrctors 2LIS_02_ITM & 2LIS_02_SCL to load data, both are working fine. 172 Views. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 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). Choose New Data Connection. The counted number depends on how often a material appears in a GR document. This DataSource provides information about the header data of a purchasing document, such as vendor, purchasing organization, order currency, and so on. RSA3. But still the data source 2LIS_02_SRV will not be visible in LBWE, but is activated & will be visible in RSA3. Transactional Data. 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. Please help me. Delta Update. (BANFN) and. MM Data Sources Tables Purchasing. . 2lis_03_bx. But in BI 7. 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. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. Purchsing Data Extraction through EKBEH table. Visit SAP Support Portal's SAP Notes and KBA Search. Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. 0AF_DEPTM. The outbound queue is filled for the following queues in the. I initiated on 04/14 and after a week i. Please help. Has searched many threads from the forum but unable to find perfect solution. To prevent the exception, note the following: A dataset can only be imported to a target area with the same structure . We discovered for once GR 2LIS_02_SCL always presents 2 lines with almost same data execpt field ROCANCEL equals 'X'. x queries on InfoCubes. I created an ODS object with the following fields as a key. Here for this Info cube from another 2lis_02_itm datasource also data is coming. I have compared BW data with SAP R/3 using tcode ME80FN and data seems to be consistent. We have historical data for 2LIS_02_SCL loaded in PSA. Visit SAP Support Portal's SAP Notes and KBA Search. and choose the industry sector "Standard (Core)". Hit enter to search. Fill the set up tables. I made my changes in the development environment and transported them to QA. in 2lis_02_scl and 2lis_02_itm Data Sources. 2. Locate your Extractor (Datasource). eg: and comm_structure-cppvlc <> 0. 2LIS_02_SCL Issue. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. = I've been running a FULL Load from this data source with no problems. However, if I use MIGO to do a goods receipt on the already initialize-loaded PO's, no delta for 2LIS_02_SCL is. This is basically information relating to the delivery completed indicator, open quantity and planned delivery date or requested. Same problem i got for Cube 0PUR_C01, for same datasource only i. The process chain supports SAP R/3 standard systems as of Release 4. 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 7. The counted number depends on how often a material appears in a GR document. J_3AKVGR10. Customer-Defined DataSource ® L. This DataSource provides the BW with data from the Sales area and supplies the InfoSource 2AF_SD_SHP_1 with data. 2lis_02_s012. 2LIS_02_SCL . 方便各位开发顾问查询. This extractor was enhanced via an append structure and ABAP in the user exit. 0FIPMATNR_ATTR . Dear Gurus, I have a requirement to extract Invoice Recipt Document number & Invoice date for every purchase order into BW. collective update this end with a dump with the message MESSAGE_TYPE_X. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL. I enhanced scheduled qty (MCEKET-MENGE) and Received Qty (MCEKET-WEMNG) to 2lis_02_scl. One system it is showing 42 Records Transferred and 8 Added Record in DSO level, and another system is showing 14. Data sources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. Francisco Milán Campos. Record count in RSA3 and PSA is different. includes tables like ekko/ekpo/ekbe etc. In the transformation start routine, I could see alogic which is barring some records to DSO. Some are transparent, some are reference, but there are one or two that stand out here. - 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. Kindly provide a solution for the below problem whcih i am facing with 2lis_02_itm and scl data sources. 2) Now you can selectively fill the setup tables for purchasing related datasources by the T-code OLI3BW. Visit SAP Support Portal's SAP Notes and KBA Search. It will send a change like below: Record Mode; EVERS; QTY. MM. I have to use two info sources called 2LIS_02_SCL and 2LIS_02_SGR in order to populate data in the cube. 0 Flow or 3. Apparently these two fields are NOT updated in BW from a delta load. This InfoSource contains the quantity that was delivered for each schedule line in a delivery item. 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. I have a problem with 2LIS_13_VDITM delta. For more information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Line 30 had been entered and totally delivered. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. Once the setup table filling is done. The 2LIS_02_SCL init. FIP Material Number 0SR_VE_INT_IV . 2LIS_02_SCL that the process key for corresponding transcation be '05' or '06'. As much as I understand the key fields which I should be using are EBELN Purchasing Doc. Why are the setup tables not filled?The data is not updated into the upur_c01 cube . Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04. load brings in goods receipt history and a starting GR $-value if quantities are partially received (0CPPVLC/0CPPVOC), and the 2LIS_02_SGR init. apart from process key is there any. Here Loekz field related data is completely not fetching from the above data sources partial data is able to get. 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. 3: Open delivery quantity/value: 2LIS_12_VCSCL gives the delivery quantity. To have an understanding about BW DataSource 2LIS_02_SCL for deletion and un-deletion a Purchase Order Item. 2. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. Technical name: 2LIS_02_SCN. so i think i have to use Schedule Line Counter (ETENR) to take the. when i check in rsa3 the data is correct. infoobject are overwritten in the ODS. DataSource: 2LIS_02_SCL. 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. Activate ODS data 0PUR_DS03. , EBELP Item and ETENR Schedule Line. By default, either of these does not capture changes to a transaction field in VL32N > Item > foreign trade/customs tab > Invoice accomp. 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 currently have an issue with Received Qty of DataSource 2LIS_02_SCL. 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. In R/3- Enhance the SCL extractor by adding the ZZ. Transfer struct. datasource 2lis_02_scl. failing. It would be fine if 2LIS_02_SGR provided the amounts (a left outer join of the. Is there any standard solution to extract. doc / . If successful, 3. We now decided to load Purchase (Old), Purchase (New) and Article Logistics cubes using 2LIS_02_SCL with the same Info Package. Method . I look at SE11 for ' MC02M_0HDRSETUP ' and table contents gives 0 records. Difference Between 2lis_02_itm & 2lis_02_scl. But when we have an Invoice Receipt the 2lis_02_scl puts WEMNG and WERT field blank while REMNG and REWRT are populated correctly. there is a routine for the PO open quantity 0BO_QTY as follows: RESULT = COMM_STRUCTURE-cpquaou * COMM_STRUCTURE-numerator / COMM_STRUCTURE-denomintr. We implemented 0PUR_C01 (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. Then try to load the Setup Tables again with Transaction OLI3BW or navigate from Transaction SBIW >. I have enhanced the extract structure of 2LIS_02_SCL (MC02M_0SCL) to include a field from the standard pool in transaction LBWE. Ramarao. I am facing following problem with above extractor. here give the PO numbers, specify a name for the job run and execute. 2LIS_02_HDR EKKO, EKBE,T001, EKPA. "MCEX_UPDATE_02_V1" "(FORM)", or declared in the procedure's RAISING clause. A total of 9 records are dropped while extraction from R3 to BI. But these datasource read data from EKKO,. 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. Then save the PO. - Data Source: 2LIS_11_VASTH. Now the problem is, I could see FEW records getting posted twice (duplicated) in PSA. but do not understand the delta behavior. Application Component. After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. 0. O Qty is 50 its getting clubbed as 250 in the Cube it has an direct delta FYI, Could you guys throw some light. 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. From this data source data is storing in two data targets 1. However in the S/4HANA system, table KONV is obsolete and replaced by table. - Stock transport order - BWVORG = 011. However, when. (table EKPA). Help. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. WKURS – Exchange Rate 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. Please suggest me the ideal way to complete this task. Hi All. 0A. My client here does not use schedule lines. 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 :. Load data InfoPackage 2LIS_02_SGR_INIT_R3. 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. Thanks and regards. In transactions "RSA1" has gone to a bookmark "DataSources", has selected a datasource "2LIS_02_SCL" and has chosen from the contextual menu "Manage". What i knew is, this type of data we will get from 'Purchasing Data (Schedule Line Level). This how 2LIS_03_BF /UM. <Delete> Go to edit mode of a PO, select an item and click "Delete". J_3AKVGR10. 5B. SAP. Comparing DataSource 2LIS_02_SCL to ME80FN. I have some strange problem in R/3. It is field-based and contains all. A drop down list on “Su Tot” reveals a list of assignment options. e: if ELIKZ = X , delivery completed else it is an open PO. We went to the Infopackage scheduler and by mistake deleted the Initialisation assuming we need a new Initialisation. 2LIS_02_SCL Issue. From the business content, in the update rule: 2LIS_02_SCL -> 0PUR_DS03. 5. Delete the setup data (LBWG) 2. th einfo object may be the same but there is a big diffrence . For example, by comparing the planned and actual goods issue dates, you can determine which quantities were delivered on time. 'MATERIAL_ATTR,MAT_SALES_ATTR,2LIS_02_SCL,2LIS_03_BF,2LIS_11_VAITM,2LIS_11_VASCL,2LIS_13_VDITM. and enhanced the datasources ITM and SCL adding one Char in RSAP0001 using user exist EXIT_SAPLRSAP_001 . We have extracted purchasing data using 2LIS_02_SCL and 2LIS_02_ITM datasources. The Field (CHARG) not hidden. Change PO Qty For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. you can get the records by running the extraction of 2LIS_02_SCL in RSA3. 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. So 2LIS_02_SCL gives more informations. ie: EUR, JPY, USD,INR and all other country currencies. 2LIS_02_SCL extractor does not always fetch data from EKET table. The field we enhanced is EKPO-EVERS. Both the datasource do not have Material document number (BELNR) field. This's also valid to other PUSH datasource. Hi, It is calculated through Function module. Please do advise on the below questions. From ITM all fields available are needed and from SCL requisitioner (AFNAM), purchase reg. Vote up 0 Vote down. 2) Now you can selectively fill the setup tables for purchasing related datasources by the T-code OLI3BW. It contained the delta queues as. Online Help Keyboard Shortcuts Feed Builder What’s newEXTACTOR 2LIS_02_SCL DELTA ERROR REMNG REWRT /WEMNG /WEWRT. 5. If any entries are available then trigger the equivalent Info. Some key figures in the data source need to be updated in an additive process. 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. In datasource 2LIS_02_SCL, there is only fields BWMNG - that represents quantity, BWGEO and BWGEO that represent values. x flow. The same field BUDAT is being assigned to 0FISCPER with rule type Time Characteristic as well. Thanks, John. 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. Open View Browser app from the search results. The extractor works correctly till the good Receipt and fills WEMNG and WEWRT fields correctly. MCEX03. 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. 0. Let’s check the delta flow – Example with Purchase order 4500000001; Purchase Order Quantity in Target table – using data preview; Purchase Order – 4500000001. When I extaract data, I get 2 records. Comparing DataSource 2LIS_02_SCN to ME80FN.