2. Delete Set up table -> Statistical setup -> Schedule job in LBWE -> Load to BW. Hi All, Im working with 2lis* extractor from Lo Cockpit, and i have the followings questions: 1)For example, im using 2lis_02_itm extractor: I have filled the setup tables on 09. The issue is when I ONLY change the. MC02M_OHDR. LIS uses v1 and v2 update modes only. READ TABLE xmcekkn. 2lis 02 Itm Tables Tables Most important Database Tables for 2lis 02 Itm Tables # TABLE Description Application Table Type; 1 : EKPO: Purchasing Document Item MM - Purchasing: Transparent Table 2 : EKKO: Purchasing Document Header MM - Purchasing: Transparent Table 3 : MSEG: Document Segment: MaterialRequest or instruction from a purchasing organization to a vendor (external supplier) or a plant to deliver a certain quantity of a product or to perform certain services at a certain point in time. MC11VA0STH: Extraction MD Order Header Status for DataSource 2LIS_11_VASTH. 2LIS_11_VAHDR: Sales Document Header Data SD - Sales and Distribution: 3 : 2LIS_13_VDITM: Billing Document Item Data SD - Sales and Distribution: 4 : 2LIS_11_VASCL: Sales Document Schedule Line SD - Sales and Distribution: 5 : 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 6 :. We appended cost center and cost element to this extractor using FUNCTION EXIT_SAPLEINS_001. Whenever setup table is deleted for application 02, all records for data sources 2LIS_02_HDR, 2LIS_02_ITM & 2LIS_02_SCL becomes zero in RSA3, but 2LIS_02_SRV will contain data. 4. VRTKZ – Distribution Indicator for Multiple Account Assignment Table of Origin. Delivery Item . Consider Process Key 2 for GR amount and Process Key 3 for Invoice Amount. 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. Upon trying, i have encountered many problems: 1. In combination with the InfoSources Purchasing Data (Document Item Level). Purchasing. 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. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). first run Init without datatransfer. 01. 2 ; SAP NetWeaver 7. SETUP tables not filling for 2LIS_02_ITM. 4. 2LIS_02_ITM, 2LIS_02_HDR, 2LIS_* , KBA , BC-BW , BW Service API , BW-BCT-MM. The counted number depends on how often a material appears in a GR document. structure in LBWE for 2LIS_02_SCL. EKPO - Item. MC11VA0STI: Extraction MD Order Item Status for DataSource 2LIS_11_VASTI. Purchasing 2LIS_02_CGR MC02M_0CGRSETUP BW-Rebuild for. after creating two tbls r created which will handle ur delta. and added a Z-field (ZZEKKOL) for this field. LOOP AT c_t_data INTO mc02m_0itm. Go to Maintainance. Go to LBWE (LO Cockpit), select DataSource 2LIS_02_SCL, click on Maintenance icon in Structure column, say Continue. This means the persistence of data for this. Now I am doing it to extract the purchasing group relevant dataand filling up the Cube PUR_C04. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. and do repair Full for whole data. Apparently these two fields are NOT updated in BW from a delta load. Purchase Requisition Tables. Suppose the sale order is 20 qty, there will be couple of records with 20 qty, doubling up the qty. So we created an append structure to MC02M_0ITM. 2lis 02 Itm Tables Most important Database Tables for 1. Data Source:2LIS_02_ITM. g If a PO item has qty 10 and Price 5 , then the field ekpo-netwr is 50 ( = 10 * 5) Now if this PO item has 3 invoices. KONV KSCHL. Z2LIS_02_ ITM_SRV. For all LO datasources logic is written in function module MCEX_BW_LO_API. Because when you fill any Purchasing DataSource (i. #. Click on save ---> Again Click on Inactive Click on Continue and Again Click on Continue Now You can see the Data Source in Active (Job Control) * Repeat the same steps for 2LIS_02_ITM and 2LIS_02_SCL 3. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 0FI_AP_4. save the package and press create. RSS Feed. Why? What am i missing out do i need to do any changes before i actiavte the in-active tables in LO-Cockpit. 63 Views. Product. 2LIS_02_HDR: Purchasing Data (Header Level) MM - Materials Management: 11 :However, before replicating to the BW on HANA system connected, I checked data in S4 via RSA3. Diagnostics. Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. 2. 2lis_11_vakon. I also have checked that: 1. For all purchasing data you should use Extractors 2LIS_02_ITM, 2LIS_02_HDR and 2LIS_02_SCL . 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. . 2LIS_02_ITM and 2LIS_02_SCL datasources not only extract PO line items. 2LIS_02_ITM Not Updating Setup Tables In Initialization Summary. I use the standard extractor 2LIS_02_ITM (order positions) with the update mode "Direct Delta" and apanded Z-fields. Go to t-code ODQMON (in ECC). We deleted init and reinitialised with no success. I am also planning to enhance these extractors for few additional fields which are not extracted by these standard extractors. If a data inbound layer persistence and/or a corporate memory persistence is used, the transformation from this DataStore. This counter determines the number of deliveries based on the GR document items. Use corresponding exit FM as template and copy the import, Export, Table, Exception. The following is the list of frequently asked questions about LO Data Extraction (logistics datasource) in a S/4HANA system: In the ERP system, 2LIS_11_VAKON (Sales Document Condition) & 2LIS_13_VDKON (Billing Document Condition) is used to fetch data from table KONV. g. # Table. This field is not present in the source structure 2LIS_02_ITM. Set up table data will be deleted for whole 'Purchasing' if deleting for '02' even though you want data reload for only Purchasing Item datasource 2lis_02_itm. 01. When I check in EKPO table, deletion indicator "L" is available for all deleted PO's. Use. In RSA3 if we check for that sales doc nos , it is displaying 0 records. Initialize Delta Process, selection criteria, filtered out, RSA7, delta queue, table ROOSPRMSF, BUDAT, logistics data source, 2LIS_02_ITM, 2LIS_02_HDR, 2LIS_* , KBA , BC-BW , BW Service API , BW-BCT-MM-PUR , BW only - Purchase , How To. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data: SD - Sales and Distribution: 2LIS_11_VASCL: Sales Document Schedule Line: SD - Sales and Distribution:. 2LIS_11_VAKON: Order Condition Data. Unlock users out of R/3. RSS Feed. But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. I filled the setup table in the development system and did an Initialize with data transfer. READ TABLE i_t_ekpo WITH KEY ebeln = xmcekpo-ebeln ebelp = xmcekpo-ebelp. As of R/3 Release 4. but not in. Date of Purchasing Document. the situation is that when I run delta it fetches 0 records. Table EKKN filed PS_PSP_PNR gives you the WBS element associated with the PO. (2LIS_11_V_ITM) - /IMO/CMSD16 . This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Schedule Line Level) (2LIS_02_SCL). Use. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. I checked in RSA7 - all 5 DataSources are there. Info Record Tables. ex: 2LIS_13_VDITM. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. The account. DATA SOURCE NAMING CONVENTIONS : 11 ----- 2LIS_11_VAHDR / 2LIS_11_VAITM / 2LIS_11_VASCL 2LIS ----- Standard refer for every LO Data Source. That means setup process wasn't happen correctly. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. Transaction LBWQ in ECC: MCEX02. Root Cause: If a PO Item in P20 is. 2LIS_02_HDR -> Purchasing Header Tables: EKKO PO Data (Header) (EBELN, BSTYP, BSART) EKPA- Partner Roles 2LIS_02_ITM -> Purchasing Item Tables: EKKO PO Data (Header) (EBELN, BSTYP, BSART) EKPO PO Data (Item) (EBELN, EBELP, MATNR) 2LIS_02_SCL > Purchasing Schedule Line Tables: EKKO PO Data. 2LIS_02_CGR 2LIS_02_SGR 2LIS_02_SCN. Due to some loads failed, we are doing re-init the loads. The system therefore only executes a delta update for this DataSource if. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. From. 5B. 1. 0. 0GN_R3_SSY. 05. This DataSource extracts Accounts Payable Accounting line items from tables BSIK (open items) and BSAK (cleared items) in the R/3 source system. If no data. I have already maintain datasource 2LIS_02_ITM through LBWE. 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. Run the collective run so all the data are sent into the delta queue. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 3. Purchasing Group Tables. EKKO / EKBE and field is BEDAT ( Purchasing Document Entry Date) 2LIS_02_ITM will take form EKKO,EKPO,EBAN tables and SYDATM means it is system date field. You can capture that without enhancing 2LIS_02_SCL Datasource. - Process Key 003:IR. Figure 7: BW Control Table – Fields . then go to T- Code OLI9BW. 0B) - SAP Documentation. Empty BW delta queues on R/3 by extraction to BW. Delete content of ODS/CUBE. 94 Views. Purchase Requisition Tables. If I missed to search something please provide that. These many numbers (Po and Line item) will not be extracted by the std extractor i,e, 2LIS_02_ITM, since those POs are not real PO. I am using the 2LIS_02_ITM extractor. Check the data in T- Code RSA3. MC02M_0CGR Storage. Gross Price P001 / P000 / PB00 / PBXX . I activated 2LIS_02_itm and SCL datasources in LO cockpit but, it is not prompting for a transport request. The activation of the business function by itself will not enhance the database tables. SAP Tables SAP Table Fields (New) SAP Glossary Search. When I try to load setup data I got this message in setup table. Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. I am tyring to fill the setup tables for application 2LIS_02_* using tcode OLI3BW , but it is taking a lot of time to fill the data even if i enter selection document date for one year every time, i want to fill the setup tables separately for each data source. It contains the complete history of the loaded data. 11. EKBE is a standard Purchasing Transparent Table in SAP MM application, which stores History per Purchasing Document data. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_40_REVAL: Revaluation at Retail: IS - Retail: 2LIS_11_VAITM: Sales Document Item Data:1. that all records from 2LIS_02_ITM are deleted in the START routine. It is actually a calculated result (rounding) in 2LIS_02_SCL and 2LIS_02_ITM. In ekpo screenshot you can find final Invoice flag is set (EKPO-EREKZ) for all the PO line. Sap Tcode Ksbt Tables in SAP. iam loding data for purchasing data using 4 data sorses. Purchase Order Tables. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data. IF i_datasource = '2LIS_02_ITM'. "2LIS_02_SCN MM MC02M_0SCN Achieved Performance: Confirmation of. (2LIS_13_VDITM). However I observed a different behaviour in case of POs with an Invoicing Plan ( mostly framework POs) E. Datasource Type: Transaction Data Extractor. Run info pack with init without data transfer. PO Item Deletion Indicator (LOEKZ) 123456 10 L. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17. When I enhance comm. BW . If you click that dropdown you will find the tables for your Datasource. eg: if i do the following action: Fill 1 -> Delete - Fill 2. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. Figure 8: BW Control Table – Entry Help/Check . 2. It's the pre-processing of Archive ( Archive Object is MM_EKKO ). TXTMD1. It is located under materials management --> Purchasing. Setup: Material Movemts. KONV KBETR. Step one: stop all postings in connected ERP system. You should find table names here. e. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :. Mapped to InfoObject. All the data is updated to standard table like VBAK , VBRK, LIKP. 192 Views. Test using RODPS_REPL_TEST , SUM = 0 in the result. For e. But this d/s 2LIS_02_SRV doesnt pick/identify the deleted service entry sheets. 3. MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL. 4. I'm using OLIG and OLIGBW to fill setup tables but there are certain documents/contracts I can. no (EBLEP) and delivery schedule line counter (ETENR). Also, please make sure that your answer complies with our Rules of Engagement. Go to RSA6. Hello, while testing extraction of 2LIS_02_ITM and 2LIS_02_SCL (rsa3), the system tells me ""0 data records selected"" even when I did everything before correctly: - LBWE - activation and set of direct delta - set application active indicator - customize industry sector - deleting setup tables - creating the statistics from the historical data. Sap Tables in SAP. ODP Semantics. SAP R/3 Enterprise. This counter determines the number of deliveries based on the GR document items. Issue: COMPL_DEL/Complete Delivery Flag was not getting populated for a PO Item where Transfer Process/Process Key =1 even when the Delivery Completed Indicator was marked at Item level in ECC. While doing the statistical setup i am using the T. This is what the procedure i used (please tell me if i did something wrong): 1. SAP. BEDAT. 2001. 2LIS_02_SCL. from the standard tables using a Business content Data Source the Data should be Extracted to BW system. Ship-to Party. Invoice Verification. Please follow bellow steps: 1. 123456 30 - 123456 40 - 123456 50 - 2lis_02_itm Setup Table. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 . When I try to do this in the conventional way (in transaction RSA6, button 'E. We've created a new field called, e. Creating an infopackage using the "full update" option: to do this I activated the extract structure MC02M_0ITM, i. The details are as below:2LIS_11_VAITM Data Source is not fetching data | SCN. There is a table that maps movement type to process key. They are needed in BW and not in R/3. When a DTP/TRFN has to be created for a Datasource as source, then the Datasource cannot be added from the value help or manually, if the name of the datasource begins with a number between 1 to 9. where this is using a standard datasource 2lis_02_ITM and 2LIS_02_SCL and i have acitvated this standard cube 0pur_c01. Delete the setup Table using LBWG . The EKPO table ( Purchasing. ) We had a similar scenario where we wanted to refresh entire data for 2LIS_13_VDKON. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 :. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :. enhancing through function module in 2lis_02_itm. Direct Access Enabled. SAP BW/4HANA Business Content delivers. The first extraction of the document itself getting two positive records in the same datapackage. Import the table definition from the Metadata Repository in the Data store Explorer and use it as source in a data flow. 2lis 13 Vditm Tables Most important Database Tables for 2lis 13 Vditm # TABLE Description Application Table Type; 1 : VBRP: Billing Document: Item Data SD - Billing: Transparent Table 2 : VBRK: Billing Document: Header Data SD - Billing: Transparent Table 3 : MC13VD0ITM:table names anywhere. On 09. Customized BADI Name – ZPP_DS_2LIS_02_ITM. I am trying to find the procedure / sequence in to carry out in. Symptom. 12. Table: EKPO. ECC -> RSA2 -> Generic Delta -> field name is empty. 2lis_11_vascl. . SAP Tables SAP Table Fields (New) SAP Glossary Search;. Recommence extraction into BW from the modified R/3. On top of this, setup table was filled, but I see no data for 2lis_02_itm. I also know that my InfoSources for this data are 2LIS_02_HDR, 2LIS_02_ITM, and 2LIS_02_SCL. Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. g. Please provide a distinct answer and use the comment option for clarifying purposes. Sales Document Item Data (2LIS_11_VAITM) - /IMO/CMSD11. MC11V_0ITM: Extraction SD Sales BW: Document Item Allocation for DataSource 2LIS_11_V_ITM. 01. RSA3 for 2LIS_02_ITM,2LIS_02_SCL , 2LIS_03_BX,. So this thing need to be keep in mind while reconciling with ECC table specially for purchasing data. Home. I have checked unhide in rsa6, but still its not displaying any values. 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. 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. 2. * For more information about source system IDs, see SAP HANA-Optimized BI Content. structure MCEKKO with field UNSEZ (on the EKKO table), I can see it in LBWE on the right for selection on the 2LIS_02_ITM datasource. 2LIS_03_UM. Follow. 0. We need to extract fields RM06E-LTEX1 (long text) and RM06E-KZLTX (More Text Exists which is a flag) from R/3 into BW however RM06E is a structure in R/3. For more information on this topic, refer to the. setup table are built sucessful and he collects data (setuolog) But the extractor checker doesn't work he collects 0 data. also full update of 2LIS_13_VDITM featches only records that have been uploaded with initial load. Step 1: Move ECC TR to ECC- PRD system. 2LIS_02_HDR Purchasing data (Header Level) MM - Materials Management: 16 :2lis 13 Vditm Base Tables BW Datasources Most important BW Extractors for 2lis 13 Vditm Base Tables # BW DATASOURCE Description Application; 1 :. Description. Read more. When I try to do this in the conventional way (in transaction RSA6, button 'E. so the standard. Delete data "LBWG" 05. 123456 30 - 123456 40 - 123456 50 - EKPO table r/3. 2lis_11_vahdr & 2lis_11_vaitm we have to use tcode OLI7BW. Over the last few days , I had some posts on 2LIS_02_ITM and Process Key activation. . Delta queue maintenance. Transaction code to delete setup table is LBWG. In 2LIS_11_VAHDR however, the field VDATU contains the sold-to party's Requested Delivery Date. The data is not updated into the upur_c01 cube . Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. I am trying to extract data from the EKKO and EKPO tables using the purchasing extractors 2lis_02_itm and 2lis_02_hdr. RSEG is a standard Invoice Verification Transparent Table in SAP MM application, which stores Document Item: Incoming Invoice data. SAP is redifining the code and changing lots of extractors and are pushing forHi. 2lis_02_itm uses EKKO and EKPO tables etc. Datasource For Afko And Afvc Tables BW Datasources. 3) Check the Indicate. RSS Feed. FAQ: Setup table filling with 2LIS* extractors. If you have a look at the code, for example sel 'MC02M_0ITM' mc02m_0itm_tab mc02m_0itmsetup, and double click on mc02m_0itm_tab,it will take you to another screen. we have done initialisation and filled setup tables. Tables for 2LIS_02_ITM. This item won't be delete physically. Runn full load. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. Bobby. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. SD - Sales and Distribution: 3 : 2LIS_02_ITM: Purchasing data (Item Level) MM - Materials Management: 4 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 5 :. For the calculation of Net GRN I need (Movement Types: 101 GR goods receipt, 102 GR for PO reversal, 122 RE return to vendor and 124 GR rtrn blocked stck). At the same time, they are also updated in the ODQDATA table. ECC -> SE11 -> ROOSOURCE -> Both "GENDELTAFD" and "GENDELTATP" are empty too. 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. 0. On DEV ran RSA3 for docs 4500000780 4500000782 0 recs selected 4)Delete set up tables for Purchasing application 02 5)Fill up set up tables date range 9/17/2004 to. With no data in setup tables, rsa7, sm13. KNTTP – Account Assignment Category. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. 2. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 6 : 2LIS_11_VAITM: Sales Document Item Data SD - Sales and Distribution: 7 :2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_HDR:. Run the Delta Info package in BW to update all the data i. EKKO. Purchasing Data (Schedule Line Level) NA. Table of Contents SAP BW/4HANA Content Add-On. 2lis 02 Itm # TABLE Description Application Table Type; 1 : EKPO: Purchasing Document Item MM - Purchasing: Transparent Table 2 : EKKO: Purchasing Document Header MM - Purchasing: Transparent Table 3 : EBAN: Purchase Requisition MM - Purchasing:Issue: Even when Deletion Indicator is marked for a PO Item in P20, the same is not reflected in BW via delta/full repair loads. Hi, Logistics application ""02 : Purchasing"" (HDR, ITM and SCL) is activated. I am trying to extract data from datasource 2lis_02_hdr using lo-cockpit and I have followed the below steps. Quantity ordered (SCLQTY) = 20. The EKPO table (Purchasing Document Item). , Z1, and we try to add this new field into the LO Cookpit datasource 2LIS_02_ITM. Pls clarify if both delta and full load can happen in parallel for the same data source?Vbak Table Data Source BW Datasources. Scheduling Agreement Tables. no (EBELP). 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . Just as try we deleted Setup table and fill it with PO documents having this issue again but no use. Rohan, Looking at EKBE is correct. Similarly, we can do the same steps (Step1-5). Step 4: Delete set up table. We could able to see the enahnced field data in RSA3 , but after making any change in ME22n its not p. 3. see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Nevertheless, nothing work with. Goto LBWE transaction in R/3. LBWE shows both extract structures (MC02M_0CGR and MC02M_0ITM) as active; Both datasources 2LIS_02_CGR and 2LIS_02_ITM are active and shown in RSA2; Delete setup tables for application 02. MC02M_0SCLSETUP. Tables related to 2LIS_06_INV TABLE Description Application ; RSEG: Document Item: Incoming Invoice: MM - Invoice Verification: RBKP:MM-PUR: Purchase Order Delivery (Items) - /IMO/D_PUR21. 0. Select the Data Source ( 2LIS_02_ITM ) 3. In EKET Table the data is like. PLAF is a standard Master Data Transparent Table in SAP PP application, which stores Planned order data. what is the reason , pls. 04. Thank you all for your replies. MCEX03. Targets are going to be different for delta and full. However, InfoCube for Purchasing ( 0PUR_C01) is already active in the system and delta are being loaded into it on a regular. This DataStore Object (DSO) contains the invoice verification data on a granular level. And it shows 0 records. 6940 Views. Also you can see same in Transaction code ME80FN. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. In RSA7 i purged or deleted the records and entry for this datasource. Whenever setup table is deleted for application 02, all records for data sources 2LIS_02_HDR, 2LIS_02_ITM & 2LIS_02_SCL becomes zero in RSA3, but 2LIS_02_SRV will contain data. better till first info provider DSO. Filled with the 2-digit logical backend system (based on LOGSY) Logical System Backend. Purchasing Document Category. Step 1: Get the name of tables affected by the lost delta data source. 2166572-What tables are read for datasource 2LIS_06_INV and basic logic. This DSO contains delivery related indicators and key figures for purchase order items. 2008 i have executed Initial Load from BI. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :Note. I am trying to fill up the SETUP tables. Follow RSS Feed HI Experts, i am abaper. 1. I have added field LOEKZ (Deletion indicator) to datasource 2LIS_02_ITM from t-code LBWE and activated. and added the fields in ODS( Key Purchasing Document and Document Item) I did the testing , and found that the fields are not correctly populated in BW. Purchasing. all fields of DataSource 2LIS_12_VCITM. This is available in SBIW. SAP Knowledge Base Article - Preview. (2LIS_11_V_ITM) - /IMO/SD_IS16 . Due to a company migration, We are using a program to delete line items of a PO. Filled with the 2-digit logical original backend system (based on ORGLOGSY ). I cannot see this same field under the same comm. You think 2LIS_06_INV extracts too many records either in the INIT, Delta or Full loads. Transformation. With no data in setup tables, rsa7, sm13.