”VT_2LIS_02_ITM”). MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 . 3. Field in Table of Origin. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. This document has 2 parts. also full update of 2LIS_13_VDITM featches only records that have been uploaded with initial load. now i want to fill setup tables for below datasources, can you suggest what are tcodes to fill up setup tables for below datasources. then data inconsistency will be happen. 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. In the second InfoProvider, you can. Read more. Inside LBWE, click the Maintenance button for this 2LIS_02_ITM, the left frame is "Selection criteria" and the right frame is "Pool", but we don't know on how to locate our new field Z1 from this Structure Maintenance window. Then save, check and activate the process chain and provide information, where applicable, about which server the process chain should be scheduled on. -----Mensaje original-----De: John Parks via sap-r3-bw [mailto:sap-r3. MC02M_0ITM. Quantity ordered (SCLQTY) = 20. EKKO. Purchasing. 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. Table of Contents SAP BW/4HANA Content Add-On. 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. Import the table definition from the Metadata Repository in the Data store Explorer and use it as source in a data flow. No. 02 Purchasing 2LIS_02_ACC MC02M_0ACCSETUP Folder: BW Setup for. 01. It s failing for only 2LIS_02_ITM only. We do not need the history data for the 2 fields added. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . Dear All, It would be really helpful to know the used tables for datasource 2LIS_02_ITM. LOOP AT c_t_data INTO mc02m_0itm. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_04_P_COMP: Component View from PP/PP-PI: PP - Production Planning and Control:I will analyse notes 459517, 728687, 722339 y 869628. Is it the right method or should it have been add. 799 Views. Hi, Where can i find the t-codes for filling the setup table for all the logistics datasources. I therefore tried to use the FULL LOAD for those datasources (2LIS_02_HDR, 2LIS_02_ITM und 2LIS_02_SCL). You should find table names here. structure in LBWE for 2LIS_02_SCL. Delivery time (SCLTM) = 12:00:00. 2. LOOP AT c_t_data into l_2lis_02_itm. Deleted the Setup tables. Go to RSA2, enter DataSource name 2LIS_02_ITM,. LIS is customer generated extractors. IF i_datasource = '2LIS_02_ITM'. This is how the SAP has defined. Pls reply needed urgent,i'm. The data is not updated into the upur_c01 cube . You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. . SD: Delivery Header Data (2LIS_12_VCHDR) - /IMO/CMSD20 . Extraction Table PFO_GO_00IV (Portfolio Assignment) - 13 : 2LIS_12_VCITM Delivery Item Data SD - Sales and Distribution: 14 :Use. 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. RSS Feed. This is what the procedure i used (please tell me if i did something wrong): 1. Tables for 2LIS_02_ITM. WHEN '2LIS_02_ITM'. no (EBLEP) and delivery schedule line counter (ETENR). 5. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. Locate your Extractor (Datasource). 0GN_R3_SSY. Fill setup table. Just as try we deleted Setup table and fill it with PO documents having this issue again but no use. Hi All, When a PO is posted the vaules are being picked by the 2LIS_02_ITM extractor. 3) Check the Indicate. Data load for :2LIS_02_HDR. MC11V_0ITM: Extraction SD Sales BW: Document Item Allocation for DataSource 2LIS_11_V_ITM. 0. Figure 8: BW Control Table – Entry Help/Check . 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. LBWE transaction - inactivate update, deleted setup tables in application component 02(MM) and also deleted any delta queue in /nrso2. Check the data in T- Code RSA3. Step 4: Delete set up table. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Fill the Set up Tables with Data Tcode : SBIW (to fill setup tables) Expand Settings for Application Specific Data Sources (PI) ----> Expand. Maintain extract structure and datasource. Suppose the sale order is 20 qty, there will be couple of records with 20 qty, doubling up the qty. 0OPS_12_ITM. BW . click the Filter combo to see the base tables, select MCEKKO MEMORY from the right and transfer it to the right section, click Continue, next click Yes. In EKET Table the primary key is based on 3 fields. what is the reason , pls. All the data is updated to standard table like VBAK , VBRK, LIKP. when I used INIT or DELTA infopackage. 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. g. "Can you please specific Setup table i. Go to LBWE (LO Cockpit), select DataSource 2LIS_02_SCL, click on Maintenance icon in Structure column, say Continue. To stop the access from outside we use t-code SM01 to. We are using the BW DataSource 2LIS_02_SCL from the LO Cockpit and have added these two fields from the Customizing cockpit (LBWE): WAMNG WEMNG. 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. This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). However, i wanted to try extraction using the newer 2LIS_02_ITM. I could not find any Info on this kind of issue in SDN. Transaction code to delete setup table is LBWG. 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. and then go to BW side and replicate the Datasource. Our delta queue for 2LIS_02_ITM and 2LIS_02_SCL was deleted from R3 by mistake. Technical Name of Target InfoObject. Due to a company migration, We are using a program to delete line items of a PO. Two lines are extracted. "2LIS_02_SCN MM MC02M_0SCN Achieved Performance: Confirmation of. Use. Afterwards, you find no delta data is generated for 2LIS_02_HDR, 2LIS_02_ITM and other 02 Datasources. 3. you can store the all the Purchase Orders in one InfoProvider ( restricting on doc. In ekpo screenshot you can find final Invoice flag is set (EKPO-EREKZ) for all the PO line. Field PSTYP. The 2lis_02_itm documentation says that the field NETWR (Net PO value) is picked up directly from table field EKPO-NETWR. Table of Contents SAP BW/4HANA Content Add-On. T-Code Purpose. Why? What am i missing out do i need to do any changes before i actiavte the in-active tables in LO-Cockpit. When I check in EKPO table, deletion indicator "L" is available for all deleted PO's. Is it possible to get this PO Delivery date in to our data source 2lis_02_itm which has PO Doc no (EBELN) and PO item. But I do not see any entries in the setup table 'MC02M_0ITMSETUP' after the SETUP run. 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). For all LO datasources logic is written in function module MCEX_BW_LO_API. Run the collective run, so all the data is sent into the delta queues. g. g. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_11_VAHDR:. I know that For purchase order details we used 2 datasources 1. KNTTP – Account Assignment Category. I created the setup tables via "Purchasing - Perform Setup", but only 3 setup tables were filled. 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. Login; Become a Premium Member; SAP TCodes; Tables. 12. DataStore object (advanced): SD: Billing Document Item Data (2LIS_13_VDITM) - /IMO/CMSD31. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). 9) After zero records repeat the step 6 to 7 for double confirmation to avoid any possible data entries. Step-4: Creating function modules for each extractor enhancement. ) 2LIS_02_SCL & 2. For more information on this topic, refer to the. 01. 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:. 0B) ( 2LIS_11_VAITM ), is used to update the Media Product Sales (M/PS) data targets, for which the SD order document is used as the basis. We have an issue with the delta's for the 2LIS_11_V_ITM, which is extracting duplicate values. Step 2: In the table TCDOB put the table name in TABNAME field, you will get some name in OBJECT. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). 2LIS_02_xxx extractors. Mapped to InfoObject. 2lis_11_v_ssl. Data Source:2LIS_02_ITM. 2LIS_02_ITM. Data Source:2LIS_02_ITM, Note: Field LOEKZ of table EKPO is the deletion indicator for an item in P20. Sales Document Item Data (2LIS_11_VAITM) - /IMO/CMSD11. 1 ; SAP NetWeaver 7. e. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. News & Insights. This DataStore Object (DSO) contains the invoice verification data on a granular level. Note: As an alternative you can also use DHCDCVCDSEXTRE in SE16 which contains more or less the same information. 11. Currently I'm trying to figure out what the logic is behind determining the most recent 'Delivery Completed Indicator' (2LIS_02_ITM-ELIKZ) value ('True' or 'False). Data Modeling Relevancy Factor: 2. (2LIS_02_ITM). ebeln = xmcekpo-ebeln. There is a table that maps movement type to process key. Application DataSource Setup Table. SAP. At present delta loads are running through that extractor. Former Member. Use. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 0FI_AP_4. Field VDATU has the same name as Update Date for Statistics Update for DataSources 2LIS_11_VAITM and 2LIS_11_VASCL. Delete content of ODS/CUBE. 2. My data flow is direct load to Info cube using 2lis_02_ITM and SCL datasources. That means setup process wasn't happen correctly. Vendor Master Data Tables : LFA1: Vendor master data general section LFB1 : Vendor Master Company Code. We have data sources 2LIS_02_ITM, 2LIS_02_CGR, 2LIS_02_SCR and 2LIS_02_SGR activated and up and running delta properly. Invoice Verification. But in case of LIS it is specific to the particular application. EKKO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Header data. The process chain supports SAP R/3 standard systems as of Release 4. Or if you are looking for OSS NOte #. Go to Maintainance. TABW is a standard Basic Functions Transparent Table in SAP FI application, which stores Asset transaction types data. The counted number depends on how often a material appears in a GR document. 2LIS_03_BX: Stock Initialization for Inventory Management MM - Materials Management: 7 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level). Settings: Purchasing. (We are not going to delete any data from application tables. 1. 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. Targets are going to be different for delta and full. This field is not present in the source structure 2LIS_02_ITM. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. choose your characteristics and key figures. a few weeks ago delta in BW stopped working. 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. I filled the setup table in the development system and did an Initialize with data transfer. The fields are filled with an. Relevancy Factor: 6. I activated 2LIS_02_itm and SCL datasources in LO cockpit but, it is not prompting for a transport request. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . png. 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. sap and forums i found out that for. Datasource Type: Transaction Data Extractor. In this case use FM EXIT_SAPLRSAP_001 as template. 2LIS_02_SCL. (2lis_02_scn,2lis_02_cgr, 2LIS_02_SGR,2lis_02_itm) when i run the statistical setup by using OLI3BW i am geting data of ITM AND SGR data sorses into setup tables, but i am not getting data of remaining data sorses , data is present in the tables of that data sorses. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Note: This step is used when we need to add additional fields, to push into BW. Empty BW delta queues on R/3 by extraction to BW. Setup Table 2lis 02 Itm TCodes Most important Transaction Codes for Setup Table 2lis 02 Itm # TCODE Description Application; 1 : SE11: ABAP Dictionary Maintenance Basis - Dictionary Maintenance: 2 : SM30: Call View Maintenance Basis - Table Maintenance Tool: 3 : SE16: Data Browser Basis - Workbench Utilities: 4 : SE38:Run RSA3 on the datasource 2LIS_02_ITM, find the extraction program field ROCANCEL(Indicator: Cancel Data Record) for doc1 are all null for each doc1 item that this field ROCANCEL fails to catch EKPO deletion indicator field LOEKZ value for these two deleted item 1 and item 4 showed in table EKPO with value of 'L' for item 1 and item 4. VRTKZ – Distribution Indicator for Multiple Account Assignment Table of Origin. etc. (Account Level) (2LIS_02_ACC). BSTYP. We are about to delete setup tables for purchase (02) component and refill the setup tables. 2LIS_02_ITM: Full & Delta: Inventory Management: Material Management: 2LIS_03_BF: Full & Delta: Production Planning: Production Planning: 2LIS_04_P_MATNR: Full & Delta: Sales:. create your update rules using MC24. I'm using OLIG and OLIGBW to fill setup tables but there are certain. purchasing and inventory ( data sources are EG 2LIS_11_Vaitm, 2LIS_02_ITM, etc. These fields are populated in the extractor and not stored in any tables. READ TABLE i_t_ekpo WITH KEY ebeln = xmcekpo-ebeln ebelp = xmcekpo-ebelp. MC11VA0STH: Extraction MD Order Header Status for DataSource 2LIS_11_VASTH. Goto LBWE transaction in R/3. iam loding data for purchasing data using 4 data sorses. g. I wonder why the same is not getting extracted when I check in RSA3 for Data Source 2LIS_02_ITM. This is available in SBIW. In RSA7 i purged or deleted the records and entry for this datasource. READ TABLE lt_ekko into wa_ekkoTable YBWMAPPING is used by the class YCL_BW_MAPPING. 0. DataStore object (advanced): SD: Delivery Item Data (2LIS_12_VCITM) - /IMO/CMSD21. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. 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 :. MC11V_0ITMSETUP. AWS Documentation AWS Supply Chain User. I have a problem with the delta. There are multiple ways of creating a column table. After all the fixes were done we can think (did the same kind of fix for all 3), 2lis_02_itm refuse to send us any delta records. Presss F5 and get inside the form “select_option_fill”. Available as of OLTP Release. 2016 at 02:59 PM GTM 2LIS_46_ITM extraction. 2. my question is what transaction code can I see this field in BW Table. We deleted init and reinitialised with no success. on BW side make sure Delta mechanism and init load is deleted. 2lis_02_itm Structure is active. This is derived from the statisitcs updating facility maintained for updating the LIS (PURCHIS) tables in R/3. These infoprovder will not have a field for ktmng rather it will have PO specific fields such as PO no, po qty, PO Agreement no. The account. 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. Datasource : 2LIS_11_V_ITM. In RSA3 if we check for that sales doc nos , it is displaying 0 records. TXTMD1. Scenario 1: All the line items associated are marked for deletion,Then 2LIS_02_ITM--> LOEKZ being extracted as L,No issues here. 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. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 1. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :. RSS Feed. Code - 'oli2bw'. EKKO - Header. I guess you are talking about the variances that are calculated based on the NO_TIME counter that is filled in during run time. I am using the 2LIS_02_ITM extractor. 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). 0. 5B. I executed infopackage full load for such sales documents, but 0records are received. I have checked unhide in rsa6, but still its not displaying any values. 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. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. Best Answer. And it shows 0 records. Because when you fill any Purchasing DataSource (i. 63 Views. 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. SAP. This counter determines the number of deliveries based on the GR document items. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. They are needed in BW and not in R/3. 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. Table Header for SAP BW OLTP Sources (Relevant From 2. SAP Table Field : ERNAM - Created by Top 200 SAP Tables containing the field/column ERNAM. Consider Process Key 2 for GR amount and Process Key 3 for Invoice Amount. Using this approach, the advantages are: The code is limited to few numbers of. Sap Tables in SAP. Delta queue maintenance. Read more. LIS uses transparent tables. 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:. Figure 9: BW Control Table – Foreign. SAP R/3 Enterprise all versions Keywords. These indicators and key figures are based on the associated confirmation and goods receipt documents. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. Prerequisites. the situation is that when I run delta it fetches 0 records. Technical name: 2LIS_02_HDR . MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. Follow. Delete Set up table -> Statistical setup -> Schedule job in LBWE -> Load to BW. The configuration of the table looks as follows. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) -. SAP R/3 Enterprise. Data Source 2LIS_02_SRV used for extraction of (Services Procurement) service line data to BW is made available with ECC 6. Go to OLI*BW and fill set up tables. There will be no impact on existing processes. Table: EKPO. Billing Document Item Data SD -Sales and Distribution. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. The Field (CHARG) not hidden. 3. 2. The modeling property Inbound table as extended table has been turned on. Custom Duty 14% JCDB . You have to enhance the data source if the field is not available to you. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 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. 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. . 2LIS_02_ITM. 2LIS_02_HDR Purchasing Data (Header Level) MM - Materials Management: 13 :Structure of 2LIS_02_ITM (MCEKPO) The issue i am facing is EKKOL (Condition Group with Vendor) is a standard field of table EKPO. While doing the statistical setup i am using the T. Like I activated the datasources in LBWE than I intialised all datasources. but not in. 2LIS_02_ITM - Adding field problem | SAP Community Relevancy Factor: 1. ALIEF - Number of Deliveries. Processkeys are maintained. . and enhanced the datasources ITM and SCL adding one Char in. In the ERP system, this information is contained in the following tables:. we have datas (ekko,ekpo) 2. Bobby. Purchasing (application 02): 2LIS_02_ITM. KNTTP – Account Assignment Category. Ship-to Party. The start routine for the updates ensures that only orders and free-of-charge orders are updated in the DataStore object. However, InfoCube for Purchasing ( 0PUR_C01) is already active in the system and delta are being loaded into it on a regular. Step 3: Move BW TRs to BW PRD system. MC02M_0CGRSETUP. I've done all the "tasks" for setup tables, but i don't have 0PROCESSKEY. 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. This InfoSource contains the structure to provide purchase data on item level into the EDW Core Layer. The Setup Tables are the objects from which the Business Warehouse system is going to extract data for Full loads and Initialization on LO Cockpit DataSources. 6940 Views. With this process chain, the initial data set is updated (initialization of the delta process) in the data targets affected (InfoArea. Date of Purchasing Document. Here is the code: LOOP AT xmcekpo. (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. EKPO - Item. Hi, Logistics application ""02 : Purchasing"" (HDR, ITM and SCL) is activated. Total number of tables/structures containing this field is 4948. Below is a list of frequently asked questions about Logistic DataSource setup table filling: Setup table (or RSA3 result) is empty even though you executed transaction OLI*BW to fill it. And after the setup table is filled, data in 2LIS_02_SRV gets duplicated. DATA: l_2lis_02_itm type mc02m_0itm, l_index type sy-tabix, lt_ekko type standard table of ekko, wa_ekko type ekko. 123456 30 - 123456 40 - 123456 50 - 2lis_02_itm Setup Table. 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. - Process Key 003:IR. correct me if iam wrong. Just ignore those things. Click ‘Yes’ to proceed further. The extractor 2lis_02_itm will extract both Purchase Orders and Agreements. Implemented class Name – ZCL_DS_2LIS_02_ITM. save the package and press create. Purchase Order Tables. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data. SAP Tables SAP Table Fields (New) SAP Glossary Search; SAP FMs; SAP ABAP Reports; SAP BW Datasources;. I chkd EKKO and EKPO and EKPA , from where it is extracted, but dont find BUDAT in these tables. 2LIS_02_SRV (obsolete) The 2LIS_02_SRV data structure is new for the EHP3 and there are some steps to activating it. Urgent help required. Then use the function Activate and Schedule to start the process chain according to your scheduling options. 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. READ TABLE xmcekkn. see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Mvke Table BW Extractors in SAP (16 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. Append MCEKPO. Technical Name of Target InfoObject. 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. Run the collective run so all the data are sent into the delta queue. Then I. if anyone knows tcodes for runinng the set uptable to each data source separatley. NOTE : Data extraction is working for all 02 transaction data like 2LIS_02_SCL , 2LIS_02_S012. You can see the table in the above screen shot. 2. I have added field LOEKZ (Deletion indicator) to datasource 2LIS_02_ITM from t-code LBWE and activated. ) 2LIS_02_ITM. The account assignment category determines the account assignment data for an item, such as cost center and account number. 05. 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. If a data inbound layer persistence and/or a corporate memory persistence is used, the transformation from this DataStore. Datasource Jest Table BW Extractors in SAP (25 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Use. Replicate the datasource 2LIS_02_ITM and reinit and load data. Vote up 0 Vote down.