Now we realize that processkeys 010 are missing but 2LIS_02_ITM catches these. oss note 353042-Howto: Activate transaction key (PROCESSKEY) may also useful. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL . 2lis_02_itm . In the datasource for Purchasing 2LIS_02_ITM and it is also there in the Schedule line item 2LIS_02_SCL, there is a field called BW: Transaction Key mapped to BWVORG in R/3. 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. apart from process key is there any. Activate ODS data 0PUR_DS03. I have created a DSO based on the schedule lines standard extractor 2LIS_02_SCL. <Delete> Go to edit mode of a PO, select an item and click "Delete". Enter the search text @Analytics. Load data InfoPackage 2LIS_02_SCL_INIT_R3. 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. In 7. If successful, 6. The process chain supports SAP R/3 standard systems as of Release 4. 2) can i map 0CPPVLC (BWGEO), instead of 0ORDER_val (BWEFFWR) in the transformation and in routine b/w data source and cube. 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. Based on DataSource: 2LIS_02_SCN. 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. 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. Users compare BW report output with SAP R/3 tcodes MCSJ and MC$4. . BW SD MM FI 数据源. 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. 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. Logic of Datasource 0INFO_REC_ATTR . It appears that many of the key figures are updated based on logic relating to the BW Processing Key. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 2LIS_13_VDKON:. 2LIS_02_ITM and 2LIS_02_SCL. Sep 26, 2012 at 05:47 AM. Hi, I think this depends on what logic u have written in your start routine. InfoSources 2LIS_12_VCHDR , 2LIS_12_VCITM , and 2LIS_12. If any entries are available then trigger the equivalent Info. am working on a new report based on a view which. Purchase related data source 2lis_02_scl datasource chain is failuring from last 5 days due to incorrect data loaded in PSA on 7/04/2012. ALIEF - Number of Deliveries. Department. I am unable to figure out why this fields is not populated. Among the ORECRODMODE and STORNO, which is better option to be mapped with the. BUDAT – Posting Date. 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. Not all fields in the ITM extractor is availavble in the SCL extractor. Why? What am i missing out do i need to do any changes before i actiavte the in-active tables in LO-Cockpit. MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. SAP Community Network Wiki - SAP NetWeaver Business Warehouse - BW Setup Tables List. 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. And below I am giving the job log details of ODS activation. Comp. If they don't solve delta queue I'll report to SAP. when i check in rsa3 the data is correct. AFS 3. 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. The IP for Purchasing (2LIS_02_SCL) started the job in ERP and the job did finish, but BW never received the message that the ERP job has been successful. I have thought to create a new ODS to upload information from this DS 2LIS_02_SCL, and fill data in two steps: Infopackage A: Full Update. Help. 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). After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. 2LIS_02_SCL . MCSJ and MC$4 uses info structure S502 and S012 respectively. 2867285-2LIS_02_SCL : extracts more schedule lines than table EKET. In 2LIS_02_SCL i have 0CPPVLC (BWGEO), 0CPPVOC (BWGEOO), 0ORDER_val (BWEFFWR). You will find that value of "LOEKZ" of. 2. Some are transparent, some are reference, but there are one or two that stand out here. 2016-01-05 02:12:26 NOT all Rows are received yet: 2LIS_02_SCL. I don' t understand because there are many records in EKPO and EKET for STO (document range. 1. RemoteCube Compatibility. This update is normally a synchronous update, i. 2LIS_03_UM: Revaluations MM - Materials Management: 6. Name. you can get the records by running the extraction of 2LIS_02_SCL in RSA3. Comparing DataSource 2LIS_02_SGR to ME80FN. actually my purchase relevant data are as follows: 21 reordes of order item ,78 reocords of order. 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. We are doing a delta update. In the SAP S/4HANA Cloud system, choose the App Finder and search for the View Browser app. 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. 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. 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). The problem is that instead of sending over the Doc Value Amounts found in the EKBE table, SAP is doing a calculation based on the the local currency. 2. BUT. I have reviewed SAP note 684465 with the list of values BWVORG for purchasing. However, when. SAP Community Network Wiki - SAP NetWeaver Business Warehouse - Step by Step Enhance your Datasource. 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). For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. LO Data Sources With Tables - Free download as Word Doc (. (II) Click on the maintanence tab, pull the fields from communication structure to extract structure based on reporting requirement. 1. Step 001 started (program RSODSACT1, variant &0000000060772, user ID U6X9539) Activation is running: Data target ZP2_PSCL, from 1,572,117 to 1,572,117. WKURS - Währungskurs. I have done with Initialization of 2LIS_02_SCL and now trying to run delta for 2LIS_02_SCL. infoobject are overwritten in the ODS. 03 Inventory. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. I created a PO with Qty 100 on 03/28/2007 and perfroemd GR on the same day for Qty of 25. This counter determines the number of deliveries based on the GR document items. It would be fine if 2LIS_02_SGR provided the amounts (a left outer join of the. Note that if you change a purchasing document, the. Click more to access the full version on SAP for Me (Login required). The logic says: umren EQ 0. Is processkey a standard across a module eg: MM and SD. But it is fetching 0 data with green status. here give the PO numbers, specify a name for the job run and execute. in both the bw systems. load brings in goods receipt history and a starting GR $-value if quantities are partially received (0CPPVLC/0CPPVOC), and the 2LIS_02_SGR init. Follow. It will send a change like below: Record Mode; EVERS; QTY. RSS Feed. Job started. This field determines whether these values are from a purchasing order, goods receipt or an invoice. V . If successful, 4. 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. The Posting date (BUDAT) from the 2LIS_02_SCL is being assigned to 0CALDAY with the rule type specified as Time Characteristic. Sent Job ABORTED update to SAP. 但是系统字段：交货单号（ ekbe-belnr ），参考凭证号（ekbe-xblnr ）没有。如果不做增强， 在其它数据源上是否有这二个字段？我找了采购，销售的都没有这二个字段，可能我还没有找对，麻烦各位高人帮指点。 谢谢. ZPUR_C01) and modify with any from the header that is needed. eg: and comm_structure-cppvlc <> 0. 0AF_COLOR. - Data Source: 2LIS_11_VASTH. 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. 2lis_02_hdr. We are using two PO extrctors 2LIS_02_ITM & 2LIS_02_SCL to load data, both are working fine. I am using Key figure BWGEO BW:CValLocCrcy & BWGEOO BW: CValOrdCrcy with summation. In particular every time I schedule the job for. Use. Now when I extract this data in full load in RSA3, I get a total of 19200 records. as the data in that dataset. Purchsing Data Extraction through EKBEH table. I'm very familiar with delta loading process (and complete setup) for the logistics datasources like 2LIS_02_HDR, 2LIS_02_ITM and 2LIS_02_SCL. 2lis_02_scl and 2lis_02_itm - SAP Q&A Relevancy Factor: 1. 2LIS_02_SCL. Situation: In the business content the update rule of 0PO_QTY is referencing the time characteristic 0SCHED_DATE for 0CALDAY. 及其r3数据 源:2lis_02_s012,2lis_02_itm,2lis_02_scl. I've done all the "tasks" for setup tables, but i don't have 0PROCESSKEY. Sep 16, 2009 at 06:26 PM. Change PO Qty For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. In the migrated Transformation between InfoSource 2LIS_02_ITM and DSO ZPUR_O01 (Position) I have two rule groups. Change the Standard variant to Released Views variant. 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. Below is the logic. Fields BWGEO, BWGEOO, BWGVP, BWGVO, BWNETWR, BWMNG, etc. Step one: stop all postings in connected ERP system. Locate your Extractor (Datasource). I look at SE11 for ' MC02M_0HDRSETUP ' and table contents gives 0 records. I am currently have an issue with Received Qty of DataSource 2LIS_02_SCL. not ectract the good Invoice receipt quantity. Vendor. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) (2LIS_02_SCL). The purchase order exists in APO in the form of an order. I made my changes in the development environment and transported them to QA. Here Loekz field related data is completely not fetching from the above data sources partial data is able to get. When i have GR reversal , Movement Type 102. Demo - Generate and Extract delta data . Please also specify what is the way to find out it. By default, either of these does not capture changes to a transaction field in VL32N > Item > foreign trade/customs tab > Invoice accomp. clear wa_package. 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”. Allocation – Confirmation with Schedule Line. Data Modeling. The 2LIS_02_SGR provides the GR document number and 2LIS_06_INV the IR document number. B. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. Features of Extractor. In the S/4HANA on-premise edition of SAP Commercial Project Management, the business object 'issue' is referred to as 'issue activity'. I have compared BW data with SAP R/3 using tcode ME80FN and data seems to be consistent. Why are the setup tables not filled?The data is not updated into the upur_c01 cube . Line 30 had been entered and totally delivered. It looks to me, that it provides information about, whether it. Hi, I have activated and loaded data in datasource 2lis_02_scl. LBWE u2013 activate in option 02 your datasource, follow the right sequence. In 2LIS_02_SCL i have 0CPPVLC (BWGEO), 0CPPVOC (BWGEOO), 0ORDER_val (BWEFFWR). I used rsa3 to validate these 2 fields against EKET table, the Received Qty is not correct. 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. I am using 2LIS_02_SCL for to fill the data into 0PUR_C01 cube. Your LIS_SCl will contain the schedule line information that is if somebody wants schedule date wise e. <i>Note : I do no selection in my infopackage. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . But when we have an Invoice Receipt the 2lis_02_scl puts WEMNG and WERT field blank while REMNG and REWRT are populated correctly. 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. 5. MM. check in start routine/update/end routine for any filters. Hi All. The counted number depends on how often a material appears in a GR document. 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 7. 2LIS_02_SCL. Reason: In customizing cockpit, tcode LBWE, the following EVENTS can be found for application 02: 02: Purchasing -> extract structure MC02M_0SCL . WKURS – Exchange Rate. You will find pool of objects there. Please suggest me the ideal way to complete this task. BW/BI Accelarator is a tool that improves the performance of BW 7. Transactional Data. 172 Views. If you wish to use the new extraction method, you must make certain settings in Customizing for the OLTP system. When i am extracting same datasource in source system and able to see data. Visit. I am using standard extractor 2LIS_13_VDITM and 2LIS_02_SCL. However, my delta infopackage is not picking up any new records. Controlling 2LIS_03_BF MC03BF0SETUP. Hello everybody, I am using datasource 2LIS_02_SCL to extract data into BW. Due to failre in purchase related datasource. The field 2lis_02_ITM-AKTWE give the good GR Quantity for services but do. 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. 3: Open delivery quantity/value: 2LIS_12_VCSCL gives the delivery quantity. Kindly provide a solution for the below problem whcih i am facing with 2lis_02_itm and scl data sources. This data source is used often. InfoSource: /IMO/PUR_IS12. This InfoSource contains the quantity that was delivered for each schedule line in a delivery item. Application Component. "Hi, we need to track the modifiations of the PARVW (Role Partner) when it is changed in a Purchasing document. We have extracted purchasing data using 2LIS_02_SCL and 2LIS_02_ITM datasources. so I add field CHARG into that datasource. We are getting '0' instead of the correct quantity, but when we do full load at the end of the month we get. When a purchase order item confirmed, even though this filed is not changed. docx), PDF File (. 2. According to my Knowledge, by help of BW: Transaction Key (0PROCESSKEY) we can differ PO's. Explanation of Note 578471 - Deleted positions in BW and statistics . The same field BUDAT is being assigned to 0FISCPER with rule type Time Characteristic as well. J_3AKVGR10. 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. Note: As an alternative you can also use DHCDCVCDSEXTRE in SE16 which contains more or less the same information. On the AWS Supply Chain dashboard, on the left navigation pane, choose Data Lake and then choose Connections. 2LIS_02_SCL. When I extaract data, I get 2 records. Specifically I am looking at the BWVORG field. MCEX03. This extractor also brings data from Goods receipts and Invoice Receipts which typically come from EKBE table. "MCEX_UPDATE_02_V1" "(FORM)", or declared in the procedure's RAISING clause. - Process Key 002:GR. As you are aware that some fields of the standard extractors gets derived via Calulation (SAP derived logic ) . 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. g for one item 001 u have quantity 90PC. we have problems with extractor 2lis_02_scl in delta data extraction. 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. 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. 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. However in the S/4HANA system, table KONV is obsolete and replaced by table. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 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. In datasource 2LIS_02_SCL, there is only fields BWMNG - that represents quantity, BWGEO and BWGEO that represent values. The following has all been done. 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. 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. RSA3. 2) Now you can selectively fill the setup tables for purchasing related datasources by the T-code OLI3BW. In our case, the filling setup table, it took normally over 1 days. ) 2LIS_02_ITM. I activated 2LIS_02_itm and SCL datasources in LO cockpit but, it is not prompting for a transport request. ME23n – PO Qty. ekko -waers . Please help me. The values can be seen in EKPO table but I am not sure this would be the source for extractor 2LIS_02_ITM becuase, when I run setup table or extract. <Delete> Go to edit mode of a PO, select an item and click "Delete". Technical Data. 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. 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_SGR: Produced Activity: Delivery of Schedule Lines: MM - Materials Management:. Transfer struct. Block user to modify to modify purchase. 2860804-2LIS_02* Datasource : custom program / transaction cannot generate delta record. 2lis_03_bx. For e. Change the PO Qty from 32 to 40 and save the same. V . 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 any of the tables. Logistic Data sources with tables. 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. In datasource 2LIS_02_SCL, there is only fields BWMNG - that represents quantity, BWGEO and BWGEO that represent values. Once the setup table filling is done. failing. 5. Search for additional results. We had at this point realised there is no Delta on the Purchase cube(New). Now, the 2LIS_02_SCL becomes zero by default. I have enhanced the extract structure of 2LIS_02_SCL (MC02M_0SCL) to include a field from the standard pool in transaction LBWE. 2lis_02_s012. DataSource 2LIS_03_BF contains data still to be transferred. When i investigated using RSA3 extraction for 2LIS_02_SCL and singled out the problamatic PO i found that. Inventory Controlling (application 03): 2LIS_03_BX. 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. I'm want to use some 2LIS_02* extractors (2LIS_02_HDR, 2LIS_02_ITM and 2LIS_02_SCL) to cubes 0PUR_C01 and 0PUR_C04. For more information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. adjusts the quantities to give the true 'open/closed' qty after GR. Transactional Data. I have a 5 records in PSA for a purchase order where total. But for 2LIS_02_SCL, i am not getting either 7. if anyone knows tcodes for runinng the set uptable to each data source separatley. Relevancy Factor: 2. when checked the data by RSA3 , I found the system generated mass data(2400 records) . Ramarao. 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. BNKA: Master Records of banks. Has searched many threads from the forum but unable to find perfect solution. Application Component. May 21, 2012 at 04:31 AM. ALIEF - Number of Deliveries. When I extract this data to PSA ONLY, the count is 19191. 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 :. 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. When we do the reconciliation with MC$4, some. The data are transfered correctly (maybe!) from Extraction Queue to Delta Queue (daily, the amount of data is almost 1000 a day). I would like to hear from you on following issue. 0. 2LIS_02_CGR: Produced Activity: Delivery of Confirmations: MM - Materials Management: 2LIS_03_BF: Goods Movements From Inventory Management: MM - Materials. 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. I am facing following problem with above extractor. By default, either of these does not capture changes to a transaction field in VL32N > Item > foreign trade/customs tab > Invoice accomp. In transactions "RSA1" has gone to a bookmark "DataSources", has selected a datasource "2LIS_02_SCL" and has chosen from the contextual menu "Manage". The keys of this DSO are PO Number, PO Item and Schedule Line number. Record count in RSA3 and PSA is different. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 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. 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). Tables for 2LIS_02_ITM. We discovered for once GR 2LIS_02_SCL always presents 2 lines with almost same data execpt field ROCANCEL equals 'X'. 5. You may choose to manage your own preferences. I'm having an issue with extractor 2LIS_02_SCL whereby the quantity field WEMNG is populated incorrectly after perform initialization, below are the activities being done so far: 4) LBWE activate datasource and included field MCEKET WEMNG (Received) After performing these steps, in RSA3, the qty display in field WEMNG doesn't match. Expand in hierarchy structure node Logistics application – 12: LE Shipping BW – Extract structures. Delivery Item . Load data InfoPackage 2LIS_02_ITM_INIT_R3. 2LIS_02_SCL extractor does not always fetch data from EKET table. Available from OLTP Release. 2016-01-05 04:11:48 Err Id: 17. result =. 3. 12. Lost while creating the. A drop down list on “Su Tot” reveals a list of assignment options. Therefore, the values for PO Qty, GR Qty and Invoice Qty (and their corresponding value KF's) appear to be. When i execute the extractor in RSA3 the data is populated, If any standard field is changed then it is. I am still finding out which of these extractor needs to be modified. I never used 2LIS_02_SGR, but following the documentation it gives returns data related for goods receipt. - Cross company order -. It is field-based and contains all. Purchasing 2LIS_02_SCN MC02M_0SCNSETUP BW-Rebuild for. 1)2LIS_03_BX : BWMNG,BWAPPLNM, BSTAUS ,BSTTYP. Keyfigures 0ORDER_VAl and 0INVCD_AMNT are in Addition mode. 1 Answer. 0A. Bei Einkaufsbelegen, die in einer anderen als der Hauswährung angelegt wurden oder zu denen Belege wie z. Hi All, Can you please share your experience on the 2LIS_02_ACC data source setup. During the initial load, everything comes along fine all the way to PSA. J_3AKVGR10. and 2LIS 02 SCL for loading business content Infocube 0PUR_C01. To confirm the delta queue, Check the SMQ1 transaction code if any Queue Name start with MCEX** or Destination BWCLNT*** (i. 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. 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 . An issue may result in changes to scope, budget, timeline, or resources. Apparently these two fields are NOT updated in BW from a delta load. 2016-01-05 02:11:46 rqState 9: Reported complete by SAP, id: 17. RUN Init. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. g. 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. I now am trying to get publishing back on track. 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. 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. 0AF_CGR10. I'm doing the data model design for procurement and i'm intending to use standard cube 0PUR_C01, but instead of using the standard flow (directly from DS to Cube) i was wondering to load the data firstly to one DSO (with all the detail) and next to the cube. Problem with MCEX_UPDATE_02 COLL. you can get the records by running the extraction of 2LIS_02_SCL in RSA3. 2lis_02_cgr . Comparing DataSource. 1 - System standard fields. The counted number depends on how often a material appears in a GR document. From ITM all fields available are needed and from SCL requisitioner (AFNAM), purchase reg. I have some strange problem in R/3. <b>Table Field</b> eket -menge .