2LIS_02_CGR. PLAF is a standard Master Data Transparent Table in SAP PP application, which stores Planned order data. SAP Table Field : ERNAM - Created by Top 200 SAP Tables containing the field/column ERNAM. If you followed below steps, no chance to miss single reocrd. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_11_VAHDR:. Purchasing Data (Schedule Line Level) NA. 123456 10 L. 3. EKPO - Item. 2LIS_02_ITM Not Updating Setup Tables In Initialization Summary. MC02M_0ACCSETUP. 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:. Prerequisites. Run the collective run, so all the data is sent into the delta queues. Table EKKN filed PS_PSP_PNR gives you the WBS element associated with the PO. Some of the PO items are marked for deletion in the source system (LOEKZ = L). Hi mates, Im using extractor 2LIS_02_ITM in BW, my field Item Category is empty. Transa ctional. Important Key Figures: ROCANCEL. Or if you are looking for OSS NOte #. Please provide a distinct answer and use the comment option for clarifying purposes. Purchasing Organization Tables. When I check with RSA3 I've got a lot of records. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 7 :. using help. Delete the setup Table using LBWG . 163 Views. my question is what transaction code can I see this field in BW Table. I'm trying to use datasource 2LIS_02_CGR in addition to 2LIS_02_ITM already in use. In the ERP system, information about the header data of a purchasing document is contained in the EKKO table ( Purchasing Document Header ). also full update of 2LIS_13_VDITM featches only records that have been uploaded with initial load. Billing Document Item Data SD -Sales and Distribution. Relevancy Factor: 1. I have gone through many threads with similar subject but dint got proper solution for this. Field in Table of Origin. You can find more information in Special Features When Using PP-PI . Apparently these two fields are NOT updated in BW from a delta load. VRTKZ – Distribution Indicator for Multiple Account Assignment Table of Origin. Transformation * For more information about source system IDs, see SAP HANA-Optimized BI Content. 4. Overall Picking/Putaway Status. Hi All, When a PO is posted the vaules are being picked by the 2LIS_02_ITM extractor. (2LIS_11_V_ITM) - /IMO/CMSD16 . Go inside the class ZCL_DS_2LIS_02_ITM and implement the below code – ATA : LT_DATA TYPE STANDARD TABLE OF MC02M_0ITM. 0. MC02M_0ITM. You can see the table in the above screen shot. 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. Upon trying, i have encountered many problems: 1. choose your characteristics and key figures. Note that if you change a purchasing document, the system only takes into consideration the data that is relevant for extraction. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. As of SAP enhancement package 6 for SAP ERP 6. no (EBELP). With no data in setup tables, rsa7, sm13. We could able to see the enahnced field data in RSA3 , but after making any change in ME22n its not p. BW-BCT-PM (Plant Maintenance). I'm trying to design a dataflow from a SAP ECC 2lis_02_itm delta extractor to sql server table (odp extractor -->sql -->map_cdc_operation --> sql table. FI and COPA is easy to get , the hardest to get at is the LO extractors. SAP Tables SAP Table Fields (New) SAP Glossary Search;. Purchasing Group Tables. SAP BW Datasource : 2LIS_02_SCL - Purchasing Data (Schedule Line Level). In this case use FM EXIT_SAPLRSAP_001 as template. BW-Rebuild for MC02M_0CGR Storage. Also, please make sure that your answer complies with our Rules of Engagement. 2) From the Scheduler dropdown, select the Repair Full Request Option. GR or IR level changes won't trigger any deltas for ITM Datasorce. 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. We currently have delta load happening from the same data source. 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. 1. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. EKKO / EKBE and field is BEDAT ( Purchasing Document Entry Date) 2LIS_02_ITM will take form EKKO,EKPO,EBAN tables and SYDATM means it is system date field. It would be really helpful to know the used tables for datasource 2LIS_02_ITM. But this d/s 2LIS_02_SRV doesnt pick/identify the deleted service entry sheets. I also have checked that: 1. That means setup process wasn't happen correctly. sap and forums i found out that for. No. Once we execute, it would give us the below screen for confirmation. The DSO provides insight into the delivery service of vendors by exploring. Pls reply needed urgent,i'm. with different condition types fromo KONV table . SAP Tables SAP Table Fields (New) SAP Glossary Search; SAP FMs; SAP ABAP Reports; SAP BW Datasources;. 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. Datasource is in active mode. #. Maintain enhancement in LEINS001. -----Mensaje original-----De: John Parks via sap-r3-bw [mailto:sap-r3. In LBWE, it says EKKO-SYDAT but it is from EKPO (*) 2LIS_02_ACC. Go to RSA6. Just ignore those things. Field NETPR for DataSource 2LIS_02_ITM and 2LIS_02_SCL. create your update rules using MC24. 0. I was successful in extracting data for the 0PUR_C01 cube using the conventional 2LIS_02_S012 datasource. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: Glossary/Terms related to ERNAM ProfileWhen extracting from a single table, do that in a standard data flow. Fill the setup tables with historical data using SBIW to get to the tcode OLI*BW. 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. 2lis_11_v_ssl. Maintain extract structure and datasource. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. In R/3 my setup tables are filled : MC02M_0ITMSETUP . 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. I am using 2lis_02_itm and 2lis_02_hdr. Select display Data Source (Ctr+F2). Relevancy Factor: 6. I did a setup table fill-up of 2lis_03_bf and I'm seeing missing material documents with movement type 561. 2LIS_03_BF. Purchasing Data (Item Level) NA. 1. Francisco Milán Campos. 2LIS_11_V_ITM. You think 2LIS_06_INV extracts too many records either in the INIT, Delta or Full loads. The 2lis_02_itm documentation says that the field NETWR (Net PO value) is picked up directly from table field EKPO-NETWR. Table Header for SAP BW OLTP Sources (Relevant From 2. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing. ALIEF - Number of Deliveries. Locate your Extractor (Datasource). e, 2lis_02_itm, or 2lis_02_hdr), both the header and the item gets filled up. Rohan, Looking at EKBE is correct. The EKPO table ( Purchasing. 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". we have the V3 update job, running every 15 minutes. The DSO is directly supplied from the Info/DataSource 2LIS_06_INV. MC02M_0ITM: Extraction Purchasing (Item) for DataSource 2LIS_02_ITM. * For more information about source system IDs, see SAP HANA-Optimized BI Content. I'm want to use some 2LIS_02* extractors (2LIS_02_HDR, 2LIS_02_ITM and 2LIS_02_SCL) to cubes 0PUR_C01 and 0PUR_C04. Field VDATU has the same name as Update Date for Statistics Update for DataSources 2LIS_11_VAITM and 2LIS_11_VASCL. Why are the setup tables not filled?If additional information is needed for the tables please let me know. 4. Extraction Table PFO_GO_00IV (Portfolio Assignment) - 13 : 2LIS_12_VCITM Delivery Item Data SD - Sales and Distribution: 14 :Use. Just as try we deleted Setup table and fill it with PO documents having this issue again but no use. All 3 2lis_02_itm, hdr and scl were enhanced to add additional fields. This counter determines the number of deliveries based on the GR document items. Then I will build a ODS on top of these extractors. 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:. But the 2lis_02_itm extractor sends no data to bw: Following is done: 1. LO-IO. 11. I have been using DataSource: 2LIS_02_ITM for couple of months and I have loaded data into (Full and Deltas). 0. There are multiple ways of creating a column table. iam loding data for purchasing data using 4 data sorses. Source Tables (Function Module): MCEX_BW_LO_API (Function Module) SAP Help, Wiki, Q&A and other resources for 2LIS_03_BF. I wanted to find out the deletion indicator (field: LOEKZ) value for the deleted PO's in R/3. 04. 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. 670313-BW: field NETPR for data source 2LIS_02_ITM and 2LIS_02_SCL. Thanks,-af. 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 . In 2LIS_11_VAHDR however, the field VDATU contains the sold-to party's Requested Delivery Date. 01. Hi, when you delete the setup table for 2LIS_02_ITM, it will show that still data exist for other DS. 2LIS_03_BX: Stock Initialization for Inventory Management MM - Materials Management: 7 : 2LIS_02_SCL: Purchasing Data (Schedule Line Level). On 09. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17. Recommence extraction into BW from the modified R/3. Then I. 2LIS_02_ACC. 6940 Views. This is available in SBIW. By debugging function module MCEX02_PREPARE_INFO it was found that the field UPDACT in table TMCEXACT. Base Tables . Type of DataSource. This's also valid to other PUSH datasource. Filled with the 2-digit system ID of the connected source system. MC11VA0STI: Extraction MD Order Item Status for DataSource 2LIS_11_VASTI. 0. There is a table that maps movement type to process key. So we created an append structure to MC02M_0ITM. (2LIS_02_ITM). BSART. (2LIS_02_HDR, 2LIS_02_ITM, 2LIS_02_SCL in my case), if we have to do full upload, do we still need to run the setup in R/3. It is mapped to BW fields 0DEL_FLAG and 0ITEM_DEL via direct assignment. From. 3) Check the Indicate. Run the Delta Info package in BW to update all the data i. 2LIS_03_UM. 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 ). Thanks for the quick response. If no data. 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. Hello, I'm trying use the datasource 2LIS_02_ITM but the field BWVORG is comming empty. 01. 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. 3. Go to RSA2, enter DataSource name 2LIS_02_ITM,. Billing Document Header Data. I could not find any Info on this kind of issue in SDN. 02. Custom Duty 14% JCDB . EKES is a standard Purchasing Transparent Table in SAP MM application, which stores Vendor Confirmations data. KONV KBETR. (2LIS_11_V_ITM) - /IMO/CMSD16 . You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. 02 Purchasing 2LIS_02_ACC MC02M_0ACCSETUP Folder: BW Setup for. Technical Name of Target InfoObject. Home. and then go to BW side and replicate the Datasource. Purchase Info Record Tables. EKKO. RSS Feed. 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:. Folder: BW Setup for MC02M_0ACC. The counted number depends on how often a material appears in a GR document. 2LIS_02_ITM : MC02M_0ITMSETUP : Storage BW Setup for MC02M_OITM : Purchasing :. 2LIS_11_VAKON: Order Condition Data. Apply the changes / Transport. Z2LIS_02_ ITM_SRV. Transport the Enhanced Data source to Source SAP system . Source System for R/3 Entry*. 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. Go inside the class ZCL_DS_2LIS_02_ITM and implement the below code – ATA : LT_DATA TYPE STANDARD TABLE OF MC02M_0ITM. Purchasing. In RSA3 the NETPR value is not the same as the NETPR in the EKPO table. The modeling property Inbound table as extended table has been turned on. now i want to fill setup tables for below datasources, can you suggest what are tcodes to fill up setup tables for below datasources. 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. And it shows 0 records. Using this approach, the advantages are: The code is limited to few numbers of. 02. # Table. DATA SOURCE NAMING CONVENTIONS : 11 ----- 2LIS_11_VAHDR / 2LIS_11_VAITM / 2LIS_11_VASCL 2LIS ----- Standard refer for every LO Data Source. 2001. 04. Use. Determine Industry Sector. 0OPS_12_ITM. 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. Home. MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) -. ODP Semantics. However I observed a different behaviour in case of POs with an Invoicing Plan ( mostly framework POs) E. Transaction code to delete setup table is LBWG. I am trying to fill up the SETUP tables. Hi gurus, We Enhanced 2LIS_02_HDR and 2LIS_02_ITM Datasources to include account assignment (Cost center/Order/WBS element/Account). 2. Every works ok when executing setup of statistical tables. cat = F ) . Order Alloctn Item Delta1 updat :2LIS_11_V_ITM : 8) If still Extraction queue (SMQ1 or LBWQ) has entries, repeat the step 6 to 7 until both the extract Queues and delta Queues read ZERO records. Block user to modify to modify purchase. For all purchasing data you should use Extractors 2LIS_02_ITM, 2LIS_02_HDR and 2LIS_02_SCL . Datasource Jest Table BW Extractors in SAP (25 BW Datasources) Login; Become a Premium Member; SAP TCodes; SAP Tables;. Figure 9: BW Control Table – Foreign. The three others (2LIS_46_HED ; 2LIS_46_CFM ; 2LIS_46_GTM) are not showing any data : see attached picture issue. of entries in Set up tables. 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. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . 2LIS_02_ITM, 2LIS_02_HDR, 2LIS_* , KBA , BC-BW , BW Service API , BW-BCT-MM. Append MCEKPO. Purchase Requisition Tables. we have datas (ekko,ekpo) 2. I have a problem with the delta. But for 2lis_02_sgr we are able to get records only for "Pruch Docu Catgory" = F(Purchase Order). PO Deletion Indicator. "Image/data in this KBA is from SAP internal systems. 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. 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. 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. SD: Delivery Header Data (2LIS_12_VCHDR) - /IMO/CMSD20 . Delivery time (SCLTM) = 12:00:00. Login; Become a Premium Member; SAP TCodes. Please provide step by step guidance for how to load data to 2LIS_02_HDR? I have tried to search on SCN but could not get any helpful document. So this thing need to be keep in mind while reconciling with ECC table specially for purchasing data. Step one: stop all postings in connected ERP system. Root Cause: If a PO Item in P20 is. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 2LIS_02_SCL: Purchasing Data. 2LIS_18_I0CAUSE: Full & Delta: Customer Service: 2LIS_18_I0ACTY: Full & Delta Financial Accounting and Controlling. Login; Become a Premium Member; SAP TCodes; Tables. Urgent help required. 2LIS_02_ITM: Purchasing Data (Item Level) MM - Materials Management: 0FI_AP_4. 1. We do not need the history data for the 2 fields added. Presss F5 and get inside the form “select_option_fill”. 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. 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. In EKET Table the data is like. 0 EHP 3. 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. Use. Filled with the 2-digit logical original backend system (based on ORGLOGSY ). ebeln = xmcekpo-ebeln. KNTTP – Account Assignment Category. MM-PUR: Purchase Data Item (2LIS_02_ITM) - /IMO/CMPUR11 . It is from BEDAT from EKKO and EKBE. BW: Transaction Key in 2LIS_02_ITM. g If a PO item has qty 10 and Price 5 , then the field ekpo-netwr is 50 ( = 10 * 5) Now if this PO item has 3 invoices. 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. Delta & Full extraction to BW for 2LIS_02_ITM. Check the data in T- Code RSA3. When we are filling Setup table if anyone access the same setup table from outside. In combination with the InfoSources Purchasing Data (Document Item Level). 2LIS_02_HDR Purchasing data (Header Level) MM - Materials Management: 16 :2lis 13 Vditm Base Tables BW Datasources Most important BW Extractors for 2lis 13 Vditm Base Tables # BW DATASOURCE Description Application; 1 :. 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. We have an issue with the delta's for the 2LIS_11_V_ITM, which is extracting duplicate values. AND ebelp = mc02m_0itm-ebelp. Purchase Requisition Tables. Step two: Delete delta entries in RSA7. SD Sales Orders. Relevancy Factor: 30. that all records from 2LIS_02_ITM are deleted in the START routine. Delete content of ODS/CUBE. Scenario 1: All the line items associated are marked for deletion,Then 2LIS_02_ITM--> LOEKZ being extracted as L,No issues here. 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. setup table are built sucessful and he collects data (setuolog) But the extractor checker doesn't work he collects 0 data. I am trying to extract data from datasource 2lis_02_hdr using lo-cockpit and I have followed the below steps. I did make sure DS,Extract structure are active and also 2LIS_02_ITM is active in RSA7 . Step 1: Move ECC TR to ECC- PRD system. 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. and added the fields in ODS( Key Purchasing Document and Document Item) I did the testing , and found that the fields are not correctly populated in BW. I wonder why the same is not getting extracted when I check in RSA3 for Data Source 2LIS_02_ITM. 2LIS_02_ITM 2LIS_02_HDR 2LIS_02_SCL. Ship-to Party. Transformation Rule. 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. 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. They are needed in BW and not in R/3. Figure 7: BW Control Table – Fields . ZBW_ 2LIS_02_HDR; ZBW_ 2LIS_02_ITM . you can store the all the Purchase Orders in one InfoProvider ( restricting on doc. Setup: Material Movemts. The issue is when I ONLY change the. Table of Contents SAP BW/4HANA Content Add-On. I am able to see the newly added field in the structure, However when I test the datasourcein RSA3. 05. SD: Sales Document Header Status (2LIS_11_VASTH) - /IMO/CMSD18 . after creating two tbls r created which will handle ur delta. I have read that it is necessary to delete the setup tables before reloading the setup tables to make sure that there is no duplicate data, however I have different question. But these datasource read data from EKKO, EKPO & EKBE table and material document number field is availble in EKBE. Technical name: 2LIS_12_VCITM. 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. Transaction data. However, i wanted to try extraction using the newer 2LIS_02_ITM. This is what the procedure i used (please tell me if i did something wrong): 1. 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. 63 Views. Jan 29, 2008 at 06:41 PM. Clear "LBWQ" 04. Hi all, 1. NOTE : Data extraction is working for all 02 transaction data like 2LIS_02_SCL , 2LIS_02_S012. Follow. I'm using OLIG and OLIGBW to fill setup tables but there are certain. SD: Sales Document Order Delivery (2LIS_11_V_SSL) - /IMO/CMSD17 . RSS Feed. 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. SAP. "Document data restriction" when filling setup table. Field in Table of Origin. Note: Field COMPL_DEL of BW is mapped via direct assignment to ECC field ELIKZ ( Delivery. 14. To stop the access from outside we use t-code SM01 to. In EHP 3 the tables are already delivered to the customer enhanced, the activation will only. 2LIS_11_V_ITM: Sales-Shipping Allocation Item Data. We do not have down time. News & Insights.