Application: SD - Sales and Distribution. 2. 10 characters required. Custom Duty 14% JCDB . 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. 2LIS_02_* Problem - Setup Tables empty | SCN Relevancy Factor: 1. 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. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . This DSO (advanced) contains delivery related indicators and key figures for purchase order items. Check the data in T- Code RSA3. 2LIS_02_ITM is a purchasing extractor, mkpf et mseg are inventory table. This gives me a message 'Date fields for info structure S032 are not. 4. Just as try we deleted Setup table and fill it with PO documents having this issue again but no use. For further information, see SAP Note 670313: BW: Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. Remove the Field known only in Exit indicator. There is a requirement to load full load to BW system from 2LIS_02_ITM data source. But in RSA7 , there are 0 recrods . Follow the below steps to get the lost delta, will be useful for any loads. 2LIS_03_BX: Stock Initialization for Inventory Management MM - Materials Management: 7 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level). and Yes,I have DELETED setup tables data prior to running the Setup process. following fields of. Figure 9: BW Control Table – Foreign. When we are filling Setup table if anyone access the same setup table from outside. how does 2lis_02_itm gets data from ekpo pstyp, what tcode can I see the entry? is it also in VA03? the Item Category from that transaction is from VBAP. "Can you please specific Setup table i. DataSource 2LIS_02_HDR contains data still to be transferred. These documents are also not getting filled into Setup Table by OLI3BW. Source table: EKET (Scheduling Agreement Delivery Schedule Lines) Extract structure: MC02M_0SCL. Purchasing document 4500000001, Item 0010, has the following schedule lines: Schedule line number (SCLNR) = 1. Step 2: Replicate datasources in BW -PRD. Loaded 0%. Maintain extract structure and datasource. Then I ran the init load and for 2LIS_02_ITM I got 432 records as transferred and 0 as added and for 2LIS_02_SCL I got 326 as transferred and 0 as added . We do not need the history data for the 2 fields added. This counter determines the number of deliveries based on the GR document items. It s failing for only 2LIS_02_ITM only. Table Coep BW Extractors in SAP (20 BW Datasources) Login; Become a Premium Member; SAP TCodes;. In ekpo screenshot you can find final Invoice flag is set (EKPO-EREKZ) for all the PO line. 2LIS_02_SCL. I have checked unhide in rsa6, but still its not displaying any values. Scheduling Agreement Tables. Former Member. Posted by spicehead-klj5bhfd on Mar 8th, 2004 at 11:20 AM. The extractor 2lis_02_itm will extract both Purchase Orders and Agreements. Vote up 0 Vote down. This is what the procedure i used (please tell me if i did something wrong): 1. of entries in Set up tables. 1) 1) Create/Find a Full Repair Infopackage in 2LIS_11_VASCL datasource in BW system. Fill the Set up Tables with Data Tcode : SBIW (to fill setup tables) Expand Settings for Application Specific Data Sources (PI) ----> Expand. Just ignore those things. I know that For purchase order details we used 2 datasources 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. Data load for :2LIS_02_HDR. In this extractor we have enhanced "PS_PSP_PNR" (WBS Element) field whose values are being stored in "Account Assignment in Purchasing Document" table. Table of Contents SAP BW/4HANA Content Add-On. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. e, 2lis_02_itm, or 2lis_02_hdr), both the header and the item gets filled up. Is there any particular reason? I looked up the configuration of the movement types by going into. The data is not updated into the upur_c01 cube . 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. Over the last few days , I had some posts on 2LIS_02_ITM and Process Key activation. To stop the access from outside we use t-code SM01 to. You can see a relationship between this tables in the web site and click on the link "SAP MM, SD, FI, PS, PP, PM, HR, System Tables". Data Modeling Relevancy Factor: 2. 3. Deleted the set up tables and ran OLI3BW and filled the set up tables. 2LIS_02_ITM Purchasing Data (Item Level) MM - Materials Management: 14 : 2LIS_05_QE2 Inspection Result: Quantitative Data QM - Quality Management: 15 :Transformation. Field VDATU has the same name as Update Date for Statistics Update for DataSources 2LIS_11_VAITM and 2LIS_11_VASCL. EKPO is a standard Purchasing Transparent Table in SAP MM application, which stores Purchasing Document Item data. There will be no impact on existing processes. Technical Name of Target InfoObject. 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. You will find pool of objects there. Append MCEKPO. with different condition types fromo KONV table . BEDAT. Description. 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. TXTMD. I now am trying to get publishing back on track. PO Item Deletion Indicator (LOEKZ) 123456 10 L. Jan 29, 2008 at 06:41 PM. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. Targets are going to be different for delta and full. I have an issue with Purchasing data source: 2LIS_02_ITM. ex: 2LIS_13_VDITM. LFA1 NAME1. Date of Purchasing Document. Implemented class Name – ZCL_DS_2LIS_02_ITM. LO Cockpit - Basic Question. 2LIS_02_ITM and 2LIS_02_SCL datasources not only extract PO line items. - Process Key 003:IR. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. g. The fields concerned are located in one of the Purchase Order screens (ME21). Delivery time (SCLTM) = 12:00:00. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2 : 2LIS_03_BF: Goods Movements From Inventory Management MM - Materials Management: 3 :. Pls reply needed urgent,i'm. 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. Determine Industry Sector. ) 2LIS_02_SCL & 2. About this page This is a preview of a SAP. Vote up 0 Vote down. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. Go to t-code ODQMON (in ECC). 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 0FI_AP_4. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_11_VAHDR:. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Purchasing Data (Item Level) ( 2LIS_02_ITM ). We are trying to implement Purchasing Information, Purchasing Data Item Level (2LIS_02_ITM), Purchasing Data Header Level (2LIS_02_HDR), Purchasing Data Schedule Line (2LIS_02_SCL), we have activated the extract structure, filled the set-up table and tried to look into the setup table but it does not show any records (even RSA3 do not show),. I'm trying to use datasource 2LIS_02_CGR in addition to 2LIS_02_ITM already in use. Then relicated the data sources . Everything went fine, up to the point wherein i was supposed to perform the [Delete set-up tables / perform extraction] part of the process. 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. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . EKES is a standard Purchasing Transparent Table in SAP MM application, which stores Vendor Confirmations data. KONV KBETR. Transport the Enhanced Data source to Source SAP system . We deleted init and reinitialised with no success. Follow. I have already maintain datasource 2LIS_02_ITM through LBWE. . Hi Experts, I need to append additional fields to the extract structure of DataSource 2LIS_02_ITM. 02:PURCHASING. Purchasing 2LIS_02_HDR MC02M_0HDRSETUP Storage BW Setup for. Step 2 Create Target table where you want to persist the data. And after the setup table is filled, data in 2LIS_02_SRV gets duplicated. Sap Tcode Ksbt Tables in SAP. Step-4: Creating function modules for each extractor enhancement. etc. This DataStore object (advanced) serves as the staging and corporate memory DSO for the DataSource Delivery Item Data (2LIS_12_VCITM). Dear All, It would be really helpful to know the used tables for datasource 2LIS_02_ITM. RSA3 for 2LIS_02_ITM,2LIS_02_SCL , 2LIS_03_BX,. Go to RSA2, enter DataSource name 2LIS_02_ITM,. 12. IF i_datasource = '2LIS_02_ITM'. Moreover STAPO (Item is statistical) = X, means Item is statistical. 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. Because when you fill any Purchasing DataSource (i. Clear setup tables in LBWG. We appended cost center and cost element to this extractor using FUNCTION EXIT_SAPLEINS_001. "2LIS_02_SCN MM MC02M_0SCN Achieved Performance: Confirmation of. I use the standard extractor 2LIS_02_ITM (order positions) with the update mode "Direct Delta" and apanded Z-fields. and then go to BW side and replicate the Datasource. Direct Access Enabled. - Process Key 001:PO. 05. 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. Step 4) Choose the datasource 2LIS_02_ITM, which is purchasing data at Item level. To reach the customising node use transaction OMGO. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) - /IMO/CMPUR12. Important Key Figures: ROCANCEL. But for 2lis_02_sgr we are able to get records only for "Pruch Docu Catgory" = F(Purchase Order). request - The Setup-tables are populated in a separate IMG-process (tcode: SBIW): "Data Transfer to the SAP Business Information Warehouse -> Settings for Application-Specific DataSources (PI) -> Logistics -> Managing. 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. Please provide a distinct answer and use the comment option for clarifying purposes. The EKPO table ( Purchasing. Maintained extract structure for 2LIS_02_ITM (LBWE) 2. The counted number depends on how often a material appears in a GR document. Delete data "LBWG" 05. some sales document nos missed in bw. 2. This means the persistence of data for this. I am using the 2LIS_02_ITM extractor. 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. Filled with the 2-digit system ID of the connected source system. Go to OLI*BW and fill set up tables. 1. 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. 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR, OLI3BW, RSA3, BSTYP , KBA , BW-BCT-MM-PUR , BW only - Purchase , Problem . Also you can see same in Transaction code ME80FN. 2lis 11 Vaitm Tables BW Extractors in SAP (28 BW Datasources) Login; Become a Premium Member; SAP TCodes;. So in the PSA,I am getting 2 records for the PO which has. 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. A goods movement is posted with the following information: Posting date (BUDAT) = 05. xmcekpo-ZZKUNNR = i_t_ekpo-kunnr. In EHP 3 the tables are already delivered to the customer enhanced, the activation will only. Use. Environment. 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. The first extraction of the document itself getting two positive records in the same datapackage. Item 20 is deleted. with SE11 transaction you can see these tables. Once we get the above screen, we could specify the component (02, 11, etc…) and click on execute button. 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:. I have gone through many threads with similar subject but dint got proper solution for this. 4. I am also planning to enhance these extractors for few additional fields which are not extracted by these standard extractors. 2LIS_11_V_ITM. better till first info provider DSO. Delivery date (SCLDT)= 01. BSART. 0B) - SAP Documentation. I saved and Activated the data source. MM-PUR: Purchase Order Delivery (Items) - /IMO/PUR_D21. NO/PO itm no/ schline. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). Invoice Verification. Transformation Rule. Purchasing 2LIS_02_ITM MC02M_0ITMSETUP. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) -. 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. the situation is that when I run delta it fetches 0 records. transfered datasource 2LIS_02_ITM using tcode RSA5. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. In R/3 my setup tables are filled : MC02M_0ITMSETUP . Technical Name. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 2LIS_02_xxx extractors. 4. 3. Purchasing Data (Schedule Line Level) NA. Follow. The modeling property Inbound table as extended table has been turned on. SD Sales Orders. Now when I click on Initialization >Fill Setup Tables >Perform Setup Purchasing, i get the following message at the status bar: ". (Purchasing Data) cube filled with 2LIS_02_ITM and 2LIS_02_SCL extractor. Delta & Full extraction to BW for 2LIS_02_ITM. 3. Delta. SAP Tables SAP Table Fields (New) SAP Glossary Search. Release Strategy Tables. 2lis 04 P Arbpl Tables BW Datasources Most important BW Extractors for 2lis 04 P Arbpl Tables # BW DATASOURCE Description. I can then reference the InfoSources in question since I know HDR data will come ! from EKKO and ITM data will come from EKPO. 2010 1:00 AM. . Attributes; Attributes. LOOP AT c_t_data into l_2lis_02_itm. Purchasing. eg: if i do the following action: Fill 1 -> Delete - Fill 2. 2. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 2LIS_02_ITM. Best Answer. Comparing DataSource 2LIS_02_SCL to ME80FN. now i want to fill setup tables for below datasources, can you suggest what are tcodes to fill up setup tables for below datasources. When I try to load setup data I got this message in setup table. While doing the statistical setup i am using the T. 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. . Field in Table of Origin. ALIEF - Number of Deliveries. But in case of LIS it is specific to the particular application. OLI1BW INVCO Stat. (2LIS_11_V_ITM) - /IMO/CMSD16 . If you need a field that can take over the Update Date for Statistics Update function, proceed as described in SAP Note. 0. 2. 2LIS_02_CGR. For information, I had the same problem with 2LIS_02_ITM. 3) Check the Indicate. Here is the code: LOOP AT xmcekpo. 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. Due to some loads failed, we are doing re-init the loads. 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 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. Table of Contents SAP BW/4HANA Content Add-On. SAP BW/4HANA. If you click that dropdown you will find the tables for your Datasource. 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. I checked in RSA3 and the set up tables all the above datasources have records. 2) From the Scheduler dropdown, select the Repair Full Request Option. Jun 15, 2007 at 04:37 PM. "MC02M_0ITM and MC02M_0SCL are automatically placed into a transport request by SAP when you activate the data sources. Bobby. Relevancy Factor: 30. However I observed a different behaviour in case of POs with an Invoicing Plan ( mostly framework POs) E. what is the reason , pls. Total number of tables/structures containing this field is 7006. 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. This InfoSource contains the structure to provide purchase data on item level into the EDW Core Layer. #. MC11VA0STH: Extraction MD Order Header Status for DataSource 2LIS_11_VASTH. RSS Feed. The following jobs move the data from the outbound queue to BW. This field is not present in the source structure 2LIS_02_ITM. Delivery Item . Select the Data Source ( 2LIS_02_ITM ) 3. I chkd EKKO and EKPO and EKPA , from where it is extracted, but dont find BUDAT in these tables. I can see the data for other datasrcs related to purchasing like 2lis_02_itm data in rsa3 . On top of this, setup table was filled, but I see no data for 2lis_02_itm. MC02M_0ACCSETUP. MC02M_0ITMSETUP if it have any records" Customized BADI Name – ZPP_DS_2LIS_02_ITM. Oct 18, 2007 at 09:39 AM. For all purchasing data you should use Extractors 2LIS_02_ITM, 2LIS_02_HDR and 2LIS_02_SCL . There is a table that maps movement type to process key. we have datas (ekko,ekpo) 2. The DataStore object integrates data on orders and free-of-charge orders on the basis of the order items (2LIS_11_VAITM) and aggregated information on order delivery schedule lines ( 2LIS_11_V_SSL ). I have a problem with the delta. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. MC02M_0SGR: Produced Activity: Delivery of Schedule Lines Maintenance for Data Source 2LIS_02_SGR 8 31 139,142. My plan is to perform below steps. RSS Feed. 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. Run the collective run so all the data are sent into the delta queue. 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. Presss F5 and get inside the form “select_option_fill”. SAP R/3 Enterprise. 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. hi Check in Base tables 😊. 2lis 11 Vaitm Tables BW Extractors in SAP (28 BW Datasources) Login; Become a Premium Member; SAP TCodes;. This DSO contains delivery related indicators and key figures for purchase order items. Francisco Milán Campos. Comparing DataSource 2LIS_02_SGR to ME80FN. 6C. Vote up 2 Vote down. Deleted the Setup tables. The corporate memory is filled independently of the EDW core layer’s update. Purchasing (application 02): 2LIS_02_ITM. Enhancement of 2LIS_02_ITM from structure RM06E. The fields are filled with an. If they don't solve delta queue I'll report to SAP. This is how the SAP has defined. 123456 20 L. This DataSource extracts Accounts Payable Accounting line items from tables BSIK (open items) and BSAK (cleared items) in the R/3 source system. 4 ; SAP NetWeaver 7. MC02M_0CGRSETUP. 11. When i try with 2LIS_02_ITM ,2lis_02_scl and 2lis_02_hdr ,R3 returns correctly my records from the set-up table . Symptom. 2lis_11_vahdr & 2lis_11_vaitm we have to use tcode OLI7BW. - Process Key 002:GR. I have been using DataSource: 2LIS_02_ITM for couple of months and I have loaded data into (Full and Deltas). . Sales Document Item Data (2LIS_11_VAITM) - /IMO/CMSD11. Transformation * For more information about source system IDs, see SAP HANA-Optimized BI Content. Datasource : 2LIS_11_V_ITM. 2LIS_02_ITM. Table of Contents SAP BW/4HANA Content Add-On. 0B, InfoSource 2LIS_04_P_MATNR replaces InfoSource 2LIS_04_S280. The outbound queue is filled for the following queues in the. This's also valid to other PUSH datasource. then go to T- Code OLI9BW. It was huge reload project for us which continued for a. Type of DataSource. Due to a company migration, We are using a program to delete line items of a PO. At the same time, they are also updated in the ODQDATA table. MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data Source2LIS_02_SCN. Billing Document Header Data. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. Some of the PO items are marked for deletion in the source system (LOEKZ = L). Not just "LO DataSources" because there are some that don't use this feature. following fields of DataSource 0CUSTOMER_TEXT: Sold-to Party. 2lis_11_vascl. I am trying to find the procedure / sequence in to carry out in. PO Doc no (EBELN), PO Itm. Use. setup table are built sucessful and he collects data (setuolog) But the extractor checker doesn't work he collects 0 data. Copy & paste to SE37 eg for 2LIS_02_ITM , extractor MCEX_BW_LO_API is used. 48. The following foreign key relationships have to be maintained. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. Compare with setup table records. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. choose your characteristics and key figures. Field PSTYP. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. 2lis 02 Itm Database Tables in SAP (23 Tables) MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/PUR_IS11. In LBWE, its showing that LOEKZ is taken from EKPO. 2LIS_02_ACC. The configuration of the table looks as follows. Then save, check and activate the process chain and provide information, where applicable, about which server the process chain should be scheduled on. 2lis 03 Bf Table BW Extractors in SAP (29 BW Datasources) Login; Become a Premium Member; Transaction Codes; Tables. Upon trying, i have encountered many problems: 1.