First part explains about the activation of the data source 2lis_02_SRV & second part explains about enhancing it for adding the services line items to be made available for extraction. KONV KBETR. I'm using OLIG and OLIGBW to fill setup tables but there are certain documents/contracts I can. TABW is a standard Basic Functions Transparent Table in SAP FI application, which stores Asset transaction types data. The DataStore Object already exists in Business Content and contains the following new fields necessary for RMA Cost Allocation: A key figure provided from DataSource. Figure 8: BW Control Table – Entry Help/Check . We have data sources 2LIS_02_ITM, 2LIS_02_CGR, 2LIS_02_SCR and 2LIS_02_SGR activated and up and running delta properly. Why? What am i missing out do i need to do any changes before i actiavte the in-active tables in LO-Cockpit. I can then reference the InfoSources in question since I know HDR data will come ! from EKKO and ITM data will come from EKPO. Nevertheless, nothing work with. Table of Contents SAP BW/4HANA Content Add-On. 0OPS_12_ITM. As of SAP enhancement package 6 for SAP ERP 6. WHEN '2LIS_02_ITM'. 2. When we are filling Setup table if anyone access the same setup table from outside. In rsa3 and in set up tables I see data fro 2LIS_02_ITM AND 2LIS_02_SCL. I am trying to simulate the exact extraction of 2LIS_03_BF and 2LIS_03_UM just to make sure the. READ TABLE i_t_ekpo WITH KEY ebeln = xmcekpo-ebeln ebelp = xmcekpo-ebelp. However, InfoCube for Purchasing ( 0PUR_C01) is already active in the system and delta are being loaded into it on a regular. Purchasing 2LIS_02_HDR MC02M_0HDRSETUP Storage BW Setup for. LFA1 NAME1. Step 2: In the table TCDOB put the table name in TABNAME field, you will get some name in OBJECT. 1. We are analbe to get the records for "Pruch Docu Catgory" = L(Scheduling Agreement). Go to Maintainance. In the ECC table EKET these two fields have changed for a given purchase order but the change is not. all fields of DataSource 2LIS_12_VCITM. I am trying to find the procedure / sequence in to carry out in. EKKO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Header data. KNTTP – Account Assignment Category. 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. These fields are populated in the extractor and not stored in any tables. Prerequisites. Figure 7: BW Control Table – Fields . BSART. Then use the function Activate and Schedule to start the process chain according to your scheduling options. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. # Table. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Purchasing (application 02): 2LIS_02_ITM. From what I read, i think i'm missing the following steps, from which I need more detail:EKBE table has Purchase Order History data and MSEG has Document Segment: Material data in it. 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. Customized BADI Name – ZPP_DS_2LIS_02_ITM. Creating an infopackage using the "full update" option: to do this I activated the extract structure MC02M_0ITM, i. The data is not updated into the upur_c01 cube . But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. This item won't be delete physically. Wanted to know whether is there any way to find out how many entries are remaining in setup table to be transfered to BW. Clear setup tables in LBWG. ) 2LIS_02_SCL & 2. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 4 :. SAP delivers the following example BEx queries on top of MultiProviders Sales Overview. run delta loads asusal. I have a problem with 2LIS_13_VDITM delta. Test using RODPS_REPL_TEST , SUM = 0 in the result. 2LIS_11_V_ITM Sales-Shipping Allocation Item Data SD - Sales and Distribution: 15 :. At the same time, they are also updated in the ODQDATA table. we have datas (ekko,ekpo) 2. Data Source:2LIS_02_ITM, Note: Field LOEKZ of table EKPO is the deletion indicator for an item in P20. 2LIS_13_VDKON: Billing Condition Data. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data (Schedule Line Level) MM - Materials Management: 2LIS_02_CGR: Produced Activity: Delivery of Confirmations: MM - Materials Management: 2LIS_02_SCN: Produced Activity: Confirmation of Schedule Lines: MM - Materials Management:. Total number of tables/structures containing this field is 4948. Suppose the sale order is 20 qty, there will be couple of records with 20 qty, doubling up the qty. Delta & Full extraction to BW for 2LIS_02_ITM. The details are as below:2LIS_11_VAITM Data Source is not fetching data | SCN. 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. 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 the name of the structure 5) Enter the NEW field starting with "ZXXXXX" 6) Save it 7) Go to Cmod and then create a project 8) The assign components as EXIT_SAPLRSAP_002 (for. Check the. RSS Feed. 2LIS_02_ITM Not Updating Setup Tables In Initialization Summary. 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) · Delivery Date (EINDT)1. This InfoSource provides the transaction data from the production process, with reference to the order header and item. SYDAT is Item created on - EKPO-AEDAT. The account assignment category determines the account assignment data for an item, such as cost center and account number. I tried deleting the setup table (LBWG) and tried again initialization (OLI3BW) but I cant. I use the standard extractor 2LIS_02_ITM (order positions) with the update mode "Direct Delta" and apanded Z-fields. We deleted init and reinitialised with no success. so the standard. Is there anyway I can get this field populated without writing code for it? "Field BADAT in 2lis_02_itm not displaying values - SAP Q&A"SAP NetWeaver 7. We appended cost center and cost element to this extractor using FUNCTION EXIT_SAPLEINS_001. 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). Step 5) Choose the datasource 2LIS_02_ITM and go to the Datasource tab and click Change the datasource as shown in screenshot. * For more information about source system IDs, see SAP HANA-Optimized BI Content. Filled with the 2-digit logical original backend system (based on ORGLOGSY ). For POC we have used Virtual table as template and used the SQL console to create table. 2010 1:00 AM. LO-IO. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. 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. 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:. We need the data for the two new fields going forward. 94 Views. 2. 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). I have checked unhide in rsa6, but still its not displaying any values. g. 3. 0. Datasource is in active mode. Hi, Where can i find the t-codes for filling the setup table for all the logistics datasources. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). Transformation * For more information about source system IDs, see SAP HANA-Optimized BI Content. This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). Unlock users out of R/3. -----Mensaje original-----De: John Parks via sap-r3-bw [mailto:sap-r3. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Once we get the above screen, we could specify the component (02, 11, etc…) and click on execute button. PO Doc no (EBELN), PO Itm. Runn full load. 2LIS_02_HDR : Purchasing data header level 2LIS_02_ITM : Purchasing data item data 2LIS_02_SCL : Purchasing data schedule line level 2LIS_02_SCN : Produced Activity : confirmation of schedule Lines. SD Sales Orders. some sales document nos missed in bw. Go to. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . with SE11 transaction you can see these tables. The DSO provides insight into the delivery service of vendors by exploring deviations across the. setup table are built sucessful and he collects data (setuolog) But the extractor checker doesn't work he collects 0 data. Press F8 and program will stop at this step. (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. 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. Hi Can anybody tell me the table name for the datasource 2LIS_02_SCL. Purchase Info Record Tables. 2lis_02_itm Structure is active. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data. SAP BW/4HANA. All, Can we run a set up table job (LO datasources) (in case of purchasing program RMCENEUA) parallely in (R/3)production environment by checking the block documnet option with different document date in selection ? The reason for this is that if we go with this option we can schedule. We've created a new field called, e. If you click that dropdown you will find the tables for your Datasource. 2016 at 02:59 PM GTM 2LIS_46_ITM extraction. That means that you can use this DataSource both for data replication in a BW system (SAP Business. (2LIS_13_VDITM). MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 . The Field (CHARG) not hidden. Login; Become a Premium Member; SAP TCodes. Hi Fabio, No You cannot do a setup for 2LIS_02_ITM only, You can only do a setup for the whole 2LIS_02. Run the collective run so all the data are sent into the delta queue. 2LIS_02_ITM - Set up Table. S012 is a standard Data Collection Transparent Table in SAP Logistics application, which stores Purchasing data. first run Init without datatransfer. MC02M_0CGR Storage. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Technical Name of Target InfoObject. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 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. Processkeys are maintained. My data flow is direct load to Info cube using 2lis_02_ITM and SCL datasources. Step 4) Choose the datasource 2LIS_02_ITM, which is purchasing data at Item level. Relevancy Factor: 6. 02 Purchasing 2LIS_02_ACC MC02M_0ACCSETUP Folder: BW Setup for. DataStore object (advanced): SD: Delivery Item Data (2LIS_12_VCITM) - /IMO/CMSD21. Consider Process Key 2 for GR amount and Process Key 3 for Invoice Amount. ) 2LIS_02_ITM. 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. The outbound queue is filled for the following queues in the. Step 4: Delete set up table. 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. There will be no impact on existing processes. Newer data is not available when checking the datasources. 05. You should find table names here. MC11V_0SCL: Extraction SD Sales BW: Allocation Schedule Line for. 100 -> 100 -> 200. Or if you are looking for OSS NOte #. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Remove the Field known only in Exit indicator. 2. This DataStore Object (DSO) contains the invoice verification data on a granular level. I am trying to fill up the SETUP tables. Import the table definition from the Metadata Repository in the Data store Explorer and use it as source in a data flow. Moreover STAPO (Item is statistical) = X, means Item is statistical. 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. eg: if i do the following action: Fill 1 -> Delete - Fill 2. Sap Tables in SAP. READ TABLE xmcekkn. 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. Add a Comment. 2LIS_03_BF. 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. Go to RSA6. The following jobs move the data from the outbound queue to BW. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. This is to keep data that is depending on each other consistent. During the initial load, everything comes along fine all the way to PSA. SAP Knowledge Base Article - Preview. g. SAP BW/4HANA Business Content delivers. When does it happen that 2LIS_02_ITM does not add. correct me if iam wrong. 02:PURCHASING. If no data inbound. Home. 2lis 11 Vaitm Ecc Source Tables BW Datasources Most important BW Extractors for 2lis 11 Vaitm Ecc Source Tables # BW DATASOURCE Description Application; 1 :. Rohan, Looking at EKBE is correct. 04. I'm trying to use datasource 2LIS_02_CGR in addition to 2LIS_02_ITM already in use. For e. Targets are going to be different for delta and full. Technical name: 2LIS_02_HDR . You will find pool of objects there. However, i wanted to try extraction using the newer 2LIS_02_ITM. These documents are also not getting filled into Setup Table by OLI3BW. With this process chain, the initial data set is updated (initialization of the delta process) in the data targets affected (InfoArea. Then I will build a ODS on top of these extractors. Recently, I need Batch data for reporting related to Purchasing , fortunately there is field CHARG (Batch) in 2LIS_02_ITM. SAP Tables SAP Table Fields (New) SAP Glossary Search; SAP FMs; SAP ABAP Reports; SAP BW Datasources;. we have deleted "02" in T-Code LBWG and filled setup table using Tcode - OLI3BW. These Z-Fields are in the database table EKPO. SAP. Delete the setup data (LBWG) 2. 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. hi Check in Base tables 😊. Presss F5 and get inside the form “select_option_fill”. 2LIS_03_BF, 2LIS_03_BX, 2LIS_03_UM)?. Situation 2. We do not need the history data for the 2 fields added. Please follow bellow steps: 1. 2LIS_11_V_ITM. 2lis_11_vakon. 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. Similarly, we can do the same steps (Step1-5). I am trying to extract data from datasource 2lis_02_hdr using lo-cockpit and I have followed the below steps. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. 2LIS_02_SCL Purchasing Data (Schedule Line Level) MM - Materials Management: 20 :After activating Datasources 2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL. Read more. PO. 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. When looking in the EKPO table, you'll get an 'X' in the Elikz field when completed, however in the extractor you do not have simply one row with the most recent value, you'll have. To reach the customising node use transaction OMGO. following fields of. Purchasing Organization Tables. Go to t-code ODQMON (in ECC). when I used INIT or DELTA infopackage. 2LIS_03_BX: Stock Initialization for Inventory Management MM - Materials Management: 7 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level). Empty BW delta queues on R/3 by extraction to BW. or alternatively you can build your own custom extractor using purchasing tables EKKO,. Type of DataSource. BW . 2LIS_02_CGR 2LIS_02_SGR 2LIS_02_SCN. Fill the setup tables with historical data using SBIW to get to the tcode OLI*BW. LOEKZ is only an indicator/flag. You can capture that without enhancing 2LIS_02_SCL Datasource. We can replace the contents of internal dd_belnr through flat file upload. LIS is customer generated extractors. Go inside the class ZCL_DS_2LIS_02_ITM and implement the below code – ATA : LT_DATA TYPE STANDARD TABLE OF MC02M_0ITM. So this thing need to be keep in mind while reconciling with ECC table specially for purchasing data. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. purchasing and inventory ( data sources are EG 2LIS_11_Vaitm, 2LIS_02_ITM, etc. IF i_datasource = '2LIS_02_ITM'. 2008 i have executed Initial Load from BI. Purchase Order Tables. Udo. 4 ; SAP NetWeaver 7. CLEAR LT_DATA. It is located under materials management --> Purchasing. Important Key Figures: ROCANCEL. Read more. For information, I had the same problem with 2LIS_02_ITM. 0. Urgent help required. Oct 18, 2007 at 09:39 AM. We currently have delta load happening from the same data source. Vendor Master Data Tables : LFA1: Vendor master data general section LFB1 : Vendor Master Company Code. Copy & paste to SE37 eg for 2LIS_02_ITM , extractor MCEX_BW_LO_API is used. 48. but not in. Code - 'oli2bw'. (2LIS_11_V_ITM) - /IMO/CMSD16 . MC02M_0CGRSETUP. so I add field CHARG into that datasource. 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:. Clear "RSA7" 03. I have an issue with Purchasing data source: 2LIS_02_ITM. 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. This field is not present in the source structure 2LIS_02_ITM. 63 Views. Determine Industry Sector. Datasource Jest Table BW Extractors in SAP (25 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. Two lines are extracted. They are needed in BW and not in R/3. Scheduling Agreement Tables. You think 2LIS_06_INV extracts too many records either in the INIT, Delta or Full loads. SAP R/3 Enterprise. To stop the access from outside we use t-code SM01 to. Scenario 1: All the line items associated are marked for deletion,Then 2LIS_02_ITM--> LOEKZ being extracted as L,No issues here. (2LIS_11_V_ITM) - /IMO/CMSD16 . eg: if i do the following action: Fill 1 -> Delete - Fill 2. Quantity ordered (SCLQTY) = 20. Scenario 2: If 5/10 line items are marked for deletion, Even though I can see their LOEKZ status in EKPO as L,2LIS_02_ITM is being. Fill setup table. Delete content of ODS/CUBE. I have been using DataSource: 2LIS_02_ITM for couple of months and I have loaded data into (Full and Deltas). 2LIS_02_SRV(obsolete) BW-BCT-PA - Personnel Management . Thank you all four you responses. 2LIS_02_ITM : MC02M_0ITMSETUP : Storage BW Setup for MC02M_OITM : Purchasing :. Run the Delta Info package in BW to update all the data i. Extraction Table PFO_GO_00IV (Portfolio Assignment) - 13 : 2LIS_12_VCITM Delivery Item Data SD - Sales and Distribution: 14 :Use. I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 . Transformation Rule. The three others (2LIS_46_HED ; 2LIS_46_CFM ; 2LIS_46_GTM) are not showing any data : see attached picture issue. 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. It is from BEDAT from EKKO and EKBE. However, when we do delta-load, none of the account. Sap Supply Chain Management Tables in SAP. Step-4: Creating function modules for each extractor enhancement. TXTMD1. 2. When I execute the RSA3 for different Datasources I can see data only in. 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. PO Deletion Indicator. Fill the Set up Tables with Data Tcode : SBIW (to fill setup tables) Expand Settings for Application Specific Data Sources (PI) ----> Expand. In EHP 3 the tables are already delivered to the customer enhanced, the activation will only. The fields concerned are located in one of the Purchase Order screens (ME21). ex: 2LIS_13_VDITM. 0. I now am trying to get publishing back on track. Transaction LBWQ in ECC: MCEX02. LBWE transaction - inactivate update, deleted setup tables in application component 02(MM) and also deleted any delta queue in /nrso2. we have done initialisation and filled setup tables. BW-BCT-PM (Plant Maintenance). Is there any particular reason? I looked up the configuration of the movement types by going into. There is a table that maps movement type to process key. Tables for 2LIS_02_ITM. 2LIS_02_* Problem - Setup Tables empty | SCN Relevancy Factor: 1. 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. BEDAT. 2LIS_02_SRV (obsolete) The 2LIS_02_SRV data structure is new for the EHP3 and there are some steps to activating it. SD: Delivery Header Data (2LIS_12_VCHDR) - /IMO/CMSD20 . choose your characteristics and key figures. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . We are using this 2lis_02-srv d/s for loading services orders (service entry sheet), in this d/s there will be multiple service entry sheets for a purchase order, sometimes in R/3 some service entry sheets may be deleted within the PO. to fill the setup table. 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. Select display Data Source (Ctr+F2). After that, AWS Supply Chain automatically creates the Amazon S3 paths and ingests data from the SAP source tables. The EKPO table (Purchasing Document Item). By debugging function module MCEX02_PREPARE_INFO it was found that the field UPDACT in table TMCEXACT. I also have checked that: 1. 2lis 02 Itm Tables Most important Database Tables for 1. 192 Views. I am using 2lis_02_itm and 2lis_02_hdr. LIS uses transparent tables. The DSO is directly supplied from the Info/DataSource 2LIS_06_INV. I checked in RSA3 and the set up tables all the above datasources have records. But you need to find the filed (AEDAT) belongs to which table. When I try to do this in the conventional way (in transaction RSA6, button 'E. 2. So , how to know. 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. Delete Set up table -> Statistical setup -> Schedule job in LBWE -> Load to BW. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . I checked in RSA7 - all 5 DataSources are there.