Use. DataStore object (advanced): SD: Delivery Item Data (2LIS_12_VCITM) - /IMO/CMSD21. MC02M_0CGRSETUP. But I can say as numeric pointer ,backend data source is using primary key (VBELN) or combination of primary key (VBELN-POSNR) from VBAP table. It's the pre-processing of Archive ( Archive Object is MM_EKKO ). 2LIS_03_BF, 2LIS_03_BX, 2LIS_03_UM)?. Hi We are using the following logic to enhance 2lis_02_itm with different fields from diff tables. Every works ok when executing setup of statistical tables. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. I did a setup table fill-up of 2lis_03_bf and I'm seeing missing material documents with movement type 561. Go to LBWE (LO Cockpit), select DataSource 2LIS_02_SCL, click on Maintenance icon in Structure column, say Continue. 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. Follow RSS Feed HI Experts, i am abaper. The EKPO table ( Purchasing. Due to some loads failed, we are doing re-init the loads. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. But these datasource read data from EKKO, EKPO & EKBE table and material document number field is availble in EKBE. ex: 2LIS_13_VDITM. 2LIS_02_ITM - Adding field problem | SAP Community Relevancy Factor: 1. Fill the Set up Tables with Data Tcode : SBIW (to fill setup tables) Expand Settings for Application Specific Data Sources (PI) ----> Expand. All 3 2lis_02_itm, hdr and scl were enhanced to add additional fields. READ TABLE xmcekkn. 1) 1) Create/Find a Full Repair Infopackage in 2LIS_11_VASCL datasource in BW system. , Z1, and we try to add this new field into the LO Cookpit datasource 2LIS_02_ITM. - Process Key 001:PO. KNTTP – Account Assignment Category. BW-Rebuild for MC02M_0CGR Storage. To reach the customising node use transaction OMGO. RSS Feed. 3. You get this message , when you execute MCB_ " View/table V_TMCLBW can only be displayed and maintained with restrictions" 2. The counted number depends on how often a material appears in a GR document. 02 Purchasing 2LIS_02_ACC MC02M_0ACCSETUP Folder: BW Setup for. Because when you fill any Purchasing DataSource (i. 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. 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. Currently i need direct t-codes to. 0. Tables for 2LIS_02_ITM. As of SAP enhancement package 6 for SAP ERP 6. SD Sales Orders. SD-DLV: Sales Document: Order Delivery (2LIS_11_V_SSL) - /IMO/SD_IS17. 123456 10 L. following fields of DataSource 0CUSTOMER_TEXT: Sold-to Party. then go to T- Code OLI9BW. 0GN_R3_SSY. When i. 2. We've created a new field called, e. Set Up Table 2lis 02 Itm Tables Most important Database Tables for Set Up Table 2lis 02 Itm # TABLE Description Application Table Type; 1 : MARA: General Material Data Logistics - Material Master: Transparent Table 2 : VBAK: Sales Document: Header Data SD - Sales: Transparent Table 3 : BSEG: Accounting Document SegmentWhen answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Transaction code to delete setup table is LBWG. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. * For more information about source system IDs, see SAP HANA-Optimized BI Content. KNTTP – Account Assignment Category. The records have the deletion indicator LOEKZ set to L in EKPO and are correctly getting updated with Recordmode 'R' and negative keyfigures in the PSA of datasource 2LIS_02_ITM. see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. select * into table lt_ekko from ekko for all entries in c_t_data. Datasource is in active mode. Go to Maintainance. SAP. g. Pls reply needed urgent,i'm. 2LIS_45_LST: Agency document: Remuneration list: IS - 2LIS_45_HDR: Agency document header data: IS - 2LIS_03_BF: Goods Movements From Inventory Management: MM - Materials Management: 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_11_VAITM: Sales Document Item Data: SD - Sales and Distribution:. Date of Purchasing Document. FIELD-SYMBOLS: <LS_DATA> TYPE MC02M_0ITM, <LV_KUNNR> TYPE EBAN-KUNNR,. The EKPO table (Purchasing Document Item). GR or IR level changes won't trigger any deltas for ITM Datasorce. Create column table “02_ITM” as (select * from “INF627126″. For item 20, LOEKZ = L (Deletion indicator). But this isn't working the way I would expect: the full load contains only those records which are in the setup tables MC02M_0HDRSETUP, etc. EKKO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Header data. MM-PUR: Purchase Order Delivery (Items) - /IMO/PUR_D21. Step 1: Get the name of tables affected by the lost delta data source. 4. This. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. KOSTK. I am using 2lis_02_itm and 2lis_02_hdr. Go to OLI*BW and fill set up tables. Sep 16, 2009 at 06:26 PM. About this page This is a preview of a SAP. If no data inbound. For POC we have used Virtual table as template and used the SQL console to create table. Delete Delta Queue (RSA7) for 2LIS_02_ITM and 2LIS_02_SCL. There will be no impact on existing processes. This InfoSource provides the transaction data from the production process, with reference to the order header and item. we have done initialisation and filled setup tables. WHEN '2LIS_02_ITM'. Best Answer. I have been using DataSource: 2LIS_02_ITM for couple of months and I have loaded data into (Full and Deltas). excuse me for this message, but I have a problem and I think you could help me. Purchase Invoice Tables. Purchasing. Run the collective run, so all the data is sent into the delta queues. the situation is that when I run delta it fetches 0 records. 0. 2. Run the collective run so all the data are sent into the delta queue. The purchase order exists in APO in the form of an order. 3. Vendor Master Data Tables : LFA1: Vendor master data general section LFB1 : Vendor Master Company Code. My data flow is direct load to Info cube using 2lis_02_ITM and SCL datasources. 2lis_11_vascl. With this handy table you can find the status of your current job or previous initialization jobs through SM37. Field in Table of Origin. Maintain Extract Structure MC02M_0ITM. 0. The account assignment category determines the account assignment data for an item, such as cost center and account number. "Document data restriction" when filling setup table. Available as of OLTP Release. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. we have deleted "02" in T-Code LBWG and filled setup table using Tcode - OLI3BW. Marco. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. PO. ALIEF - Number of Deliveries. From. And it shows 0 records. They are needed in BW and not in R/3. Thanks and regards. 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. I have enhanced the datasource(2lis_02_itm) for the Tolerance fields. (2LIS_11_V_ITM) - /IMO/CMSD16 . Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. Table of Contents SAP BW/4HANA Content Add-On. SAP delivers the following example BEx queries on top of MultiProviders Sales Overview. but when I perform initialization of LIS table on R/3 side I make initial load to BW I can see that there is an. LOEKZ is only an indicator/flag. In R3, some PO items marked with Final Invoice (EREKZ = X) but the same PO items are not reflected with final Invoice flag via the extractor 2LIS_02_ITM. This is how the SAP has defined. 12. 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. 2LIS_02_ITM. But for 2lis_02_sgr we are able to get records only for "Pruch Docu Catgory" = F(Purchase Order). Setup Table. 5. 2lis 02 Itm Sap Database Tables in SAP (30 Tables) Logistic Cockpit datasources reads from Setup-tables (like MC02M_0ITMSETUP for 2LIS_02_ITM) when you execute Full or Delta-init. Hi All, I had to add a field from table EKPO to 2lis_02_itm datasource, I did the append structure to MC02M_0ITM straight away and filled in the exit. 4. 2. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Replicate the same in BW system. ALIEF - Number of Deliveries. Jan 29, 2008 at 06:41 PM. You can capture that without enhancing 2LIS_02_SCL Datasource. Status record it will be having different statuses like idoc created,idoc posted etc. Clear "RSA7" 03. Then use the function Activate and Schedule to start the process chain according to your scheduling options. I'm having a kind of a business issue when trying to extract data from 2lis_46_itm to BW. For more information on this topic, refer to the. That means setup process wasn't happen correctly. EKKO. 3 ; SAP NetWeaver 7. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data: SD - Sales and Distribution: 2LIS_11_VASCL: Sales Document Schedule Line: SD - Sales and Distribution:. Is it the right method or should it have been add. MC02M_0ITMSETUP if it have any records" Customized BADI Name – ZPP_DS_2LIS_02_ITM. Just as try we deleted Setup table and fill it with PO documents having this issue again but no use. Data load for :2LIS_02_HDR. 0. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. How can I find which tables in R/3 are the source tables for this and that extractor (e. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. So in the PSA,I am getting 2 records for the PO which has. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. Delivery date (SCLDT)= 01. Maintain extract structure and datasource. 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. 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: MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11. Step-4: Creating function modules for each extractor enhancement. Delete the setup data (LBWG) 2. e 4. We are analbe to get the records for "Pruch Docu Catgory" = L(Scheduling Agreement). Processkeys are maintained. 2LIS_02_CGR. 2. Technical name: 2LIS_02_ITM Use In combination with the InfoSources Purchasing Data (Document Header Level) and Purchasing Data (Document Schedule Line Level , the InfoSource Purchasing Data (Document Item Level) supplies the basic data for analyses of purchasing documents. FIELD-SYMBOLS : <LS_DATA> TYPE MC02M_0ITM, <LV_KUNNR> TYPE EBAN-KUNNR, . The DSO is directly supplied from the Info/DataSource 2LIS_06_INV. A New Home in New Year for SAP Community: Exciting times ahead for the SAP Community!We have schedule the job of filling the setup tables today i. Purchasing Group Tables. 2lis_11_v_ssl. It looks to me, that it provides information about, whether it is a invoice, GR, and so on. So we created an append structure to MC02M_0ITM. Use. 4 ; SAP NetWeaver 7. Data Modeling Relevancy Factor: 2. 6C. The process chain supports SAP R/3 standard systems as of Release 4. NO/PO itm no/ schline. 3. to fill the setup table. #. in previous versions of ABAP you could easily get it by searching through the code in the code table for TABLES and you would have got it. 2. - Process Key 002:GR. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. if you put EKET then it brings up. Important Key Figures: ROCANCEL. SAP R/3 Enterprise. 339 Views. Field PSTYP. Use. Hi everyone, We are implementing the purchasing solution for the first time at the client. This is to keep data that is depending on each other consistent. I've done all the "tasks" for setup tables, but i don't have 0PROCESSKEY. Relevancy Factor: 1. Then relicated the data sources . Clear "LBWQ" 04. 14. "Can you please specific Setup table i. READ TABLE i_t_ekpo WITH KEY ebeln = xmcekpo-ebeln ebelp = xmcekpo-ebelp. "2LIS_02_SCN MM MC02M_0SCN Achieved Performance: Confirmation of. But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. As of R/3 Release 4. 2LIS_02_ACC. You can look at the includes with *TOP* eg INCLUDE mcex02top. Total number of tables/structures containing this field is 7006. Inventory Controlling (application 03): 2LIS_03_BX. 0 EHP 3. Use. 0. We appended cost center and cost element to this extractor using FUNCTION EXIT_SAPLEINS_001. LIS uses v1 and v2 update modes only. Step 1: Move ECC TR to ECC- PRD system. Overall Picking/Putaway Status. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. READ TABLE lt_ekko into wa_ekkoTable YBWMAPPING is used by the class YCL_BW_MAPPING. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. hi Check in Base tables 😊. For e. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. We could able to see the enahnced field data in RSA3 , but after making any change in ME22n its not p. The start routine for the updates ensures that only orders and free-of-charge orders are updated in the DataStore object. For purchasing datasources 2lis_02_itm and 2lis_02_sgr . Job for collective update stopped (LBWE) 4. Tables related to 2LIS_13_VDHDR TABLE Description Application ; VBRK: Billing Document: Header Data: SD - Billing: VBRP: Billing Document: Item Data: SD - Billing: VBAP:For the same Datasource 2LIS_02_HDR, when in R/3 production I try to extract data using RSA3, it gives me '0' records. Run info pack with init without data transfer. and do repair Full for whole data. 2LIS_02_ITM: DS only for Direct Access, 2181511: 0MM_PUR_PO_SCL: 2LIS_02_SCL: DS only for Direct Access, 2181511: 0MM_PUR_PO_SCN: 2LIS_02_SCN. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule. Sap Supply Chain Management Tables in SAP. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. If I missed to search something please provide that. We currently have delta load happening from the same data source. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . Runn full load. 2LIS_02_* Problem - Setup Tables empty | SCN Relevancy Factor: 1. Symptom. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. I am trying to fill up the SETUP tables. Vote up 0 Vote down. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 - SAP Help Portal Relevancy Factor: 10. Source Tables (Function Module): MCEX_BW_LO_API (Function Module) SAP Help, Wiki, Q&A and other resources for 2LIS_03_BF. Everything went fine, up to the point wherein i was supposed to perform the [Delete set-up tables / perform extraction] part of the process. In EKET Table the primary key is based on 3 fields. that all records from 2LIS_02_ITM are deleted in the START routine. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . BEDAT. These Z-Fields are in the database table EKPO. The fields are filled with an. Then save, check and activate the process chain and provide information, where applicable, about which server the process chain should be scheduled on. 3. and had given the termination time . 2lis 11 Vaitm Ecc Source Tables BW Datasources Most important BW Extractors for 2lis 11 Vaitm Ecc Source Tables # BW DATASOURCE Description Application; 1 :. Transformation. Issues in Filling Setup table for 2LIS_02_HDR | SAP Community Relevancy Factor: 1. The InfoSource for the SD sales document Order Item Data (as of 2. AND ebelp = mc02m_0itm-ebelp. Follow. (We are not going to delete any data from application tables. We have an infocube up and running in production for couple of years, now have to add 2 fields in the extractor which are part of standard extractor 2lis_02_itm. Figure 8: BW Control Table – Entry Help/Check . Nevertheless, nothing work with. Newer data is not available when checking the datasources. Some of the PO items are marked for deletion in the source system (LOEKZ = L). Hi, Logistics application ""02 : Purchasing"" (HDR, ITM and SCL) is activated. 01. 2lis_02_itm Structure is active. This form assigns the range entered in selection screen to internal table dd_belnr. 12. You can see the table in the above screen shot. 0B, InfoSource 2LIS_04_P_MATNR replaces InfoSource 2LIS_04_S280. 94 Views. 5B. Root Cause: If a PO Item in P20 is. SAP. The following has all been done. 3. Run DTP with extraction mode “Delta” ( 1 st time it extracts data from setup table). 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). When running the setup for application 02 (TR OLI3BW), the table was not filled: running RSA3 with no restrictions did not retrieve any records. Step. The system therefore only executes a delta update for this DataSource if. I have loaded an initial load to my ODS (0BBP_PO) and also setup a delta. Then I. Step 2 Create Target table where you want to persist the data. Press F8 and program will stop at this step. eg: if i do the following action: Fill 1 -> Delete - Fill 2. SAP is redifining the code and changing lots of extractors and are pushing forHi. Step 2: In the table TCDOB put the table name in TABNAME field, you will get some name in OBJECT. Checked data in "RSA3" ex: 200 records. following fields of. Thank-You. During the initial load, everything comes along fine all the way to PSA. Transport the Enhanced Data source to Source SAP system . With this process chain, the initial data set is updated (initialization of the delta process) in the data targets affected (InfoArea. 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. 1. Application; 1 : 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 : 2LIS_11_VAITM: Sales Document Item Data SD - Sales and Distribution: 3 : 0CO_OM_OPA_6:. Purchase Requisition Tables. 2016 at 02:59 PM GTM 2LIS_46_ITM extraction. This document has 2 parts. Deleted the set up tables and ran OLI3BW and filled the set up tables. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_S012: Purchasing: MM - Materials Management:. CM SD: Sales-Shipping Allocation Item Data (2LIS_11_V_ITM) - /IM: CM SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD: CM SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD1:. MC02M_0ITM: Extraction Purchasing (Item) for DataSource 2LIS_02_ITM. Use. save the package and press create. # Table. LIS is customer generated extractors. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. At present delta loads are running through that extractor. Name of Target InfoObject. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. where this is using a standard datasource 2lis_02_ITM and 2LIS_02_SCL and i have acitvated this standard cube 0pur_c01. I have pasted the eror message below for reference. Can somebody please explain this behavior? Regards, AlexSetup Table Structure : MC02M_0(HDR)SETUP Deleting Setup tables : LBWG - Application : 02 Setup Table deletion job name. When using a Join of 2LIS_03_BF ( for Good Movement (E) from MSEG data ) and 2LIS_06_INV ( for Invoice (Q) from EKBE data ) ; In general the DBMTR is same in MSEG and EKBE, but there are few scenarios when they are. However in the S/4HANA system, table KONV is obsolete and replaced by table. I executed infopackage full load for such sales documents, but 0records are received. -----Mensaje original-----De: John Parks via sap-r3-bw [mailto:sap-r3. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) -. Step 5) Choose the datasource 2LIS_02_ITM and go to the Datasource tab and click Change the datasource as shown in screenshot. e. ZBW_ 2LIS_02_HDR; ZBW_ 2LIS_02_ITM . ebeln = xmcekpo-ebeln. all fields of DataSource 2LIS_12_VCITM. I cannot see this same field under the same comm. See SAP Service Marketplace, SAP Note 0448600 for more information on prerequisites. Delivery Item . 2166572-What tables are read for datasource 2LIS_06_INV and basic logic. I have added field BADAT-PR creation date in the extractor structure of 2lis_02_itm. 3. Bobby. Go to RSA2, enter DataSource name 2LIS_02_ITM,. Step 3: Move BW TRs to BW PRD system. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. When testing the data, we noticed that certain PO's that are in the tables EKPO are not showing up in the 2lis_02_ITM PSA. Udo. SCL dS will trigger delta with GR and IR. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Home. I'm trying to use datasource 2LIS_02_CGR in addition to 2LIS_02_ITM already in use. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Item Level) ( 2LIS_02_ITM ). MC02M_0SCLSETUP. BW-BCT-PM (Plant Maintenance). xmcekpo-ZZKUNNR = i_t_ekpo-kunnr. 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. Compare with setup table records. where ebeln = c_t_data-ebeln. You have to enhance the data source if the field is not available to you. LBWE-- >Purchasing >Extract structures ---->2LIS_02_HDR/SCL/ITM (DATA SOURCES),when i click on the in-active tab to make change and activate i get a alert as the DATA SOURCE doesn't exist. Using this approach, the advantages are: The code is limited to few numbers of. Sales Document Item Data (2LIS_11_VAITM) - /IMO/CMSD11. 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. On top of this, setup table was filled, but I see no data for 2lis_02_itm. correct me if iam wrong. 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. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17. They also extract GR and IR. 3. g. Billing Document Item Data SD -Sales and Distribution. Can see Queue 2LIS_11_VAHDR. (2LIS_13_VDITM). I tried deleting the setup table (LBWG) and tried again initialization (OLI3BW) but I cant. Control record it will be having information like Idoc number, message type, idoc type, sender, receiver etc. I created the setup tables via "Purchasing - Perform Setup", but only 3 setup tables were filled. 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. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 5 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 6 :670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL . SETUP tables not filling for 2LIS_02_ITM. RSA3 for 2LIS_02_ITM,2LIS_02_SCL , 2LIS_03_BX, 2LIS_03_UM shows data but it does not get updated to the cube ( 0PUR_C01, 0IC_C03). No. . first run Init without datatransfer. This gives me a message 'Date fields for info structure S032 are not. Former Member. Select display Data Source (Ctr+F2). Oct 18, 2007 at 09:39 AM. I am trying to extract data from datasource 2lis_02_hdr using lo-cockpit and I have followed the below steps. with different condition types fromo KONV table . Our delta queue for 2LIS_02_ITM and 2LIS_02_SCL was deleted from R3 by mistake. I am trying to find the procedure / sequence in to carry out in. Ship-to Party. 10 characters required. Table Header for SAP BW OLTP Sources (Relevant From 2. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL.