Logistics Information System in External Services - ERP SCM - SCN Wiki

Registration. ERP SCM … ERP Supply Chain Management ERP Materials Management Service Procurement External Services. Logistic Information System. Information systems are flexible tools for collectiong, aggregating and evaluating data from the operative application. In addition, you can use this data as the basis for planning. You can therefore use the information systems for controling, monitoring, and planning purposes. There are two processes in LIS: Online : This process occurs every time that a purchasing document (purchase order, service entry sheet or invoice receipt) is created or changed. The document information is processes in LIS. Reconstruction : In this process a reconstruction of the statistical information structure is performed. The document and the information structure selection are made in transaction OLI3. LIS for External Services. LIS for services are totally integrated in the purchasing module. The function group "EINS" handles the statistic information system. MM-SRV-BW Transactions OLIX: Copy/Delete versions in Information Structures OMO2 MC26 OLI3. Customizing. Updating Rules in LIS. Type of updating Rules. The update type determines how the data to be updated is linked to the data that has already been updated in the information structure. There are three updating types: Cumulative updating: "A" the new values are always added to or subtracted from the old values Counter: "C" is a special form of cumulative updating. Data Transfer Only: "B" the new value will overwrite the already updated value. The old value in the information structure is deleted and replaced by the new value. Event - The event determines which activity in the operative application is to trigger the update of this key figure. In external services we use the events MA, MB and MC. Customizing: Activate Update. Period unit of the update updating on a daily basis updating on a weekly basis updating on a monthly basis updating on the basis of posting period Type of updating Synchronous update (V1 update) - This statistics update is carried out at the same time as the document update Asynchronous update (V2 update) - The document update and the statistics update take place separately so that if the statistics update is terminated, this does not affect the update of the documents that are available in the operative allication. Asynchnous Updating (V3 Update) - The statistic update is made separately from the document update. The difference between V2 and V3 updates is the time schedule. With V3 update active, the update can be executed at a later time. Customizing: Transaction OMO2. Updating the info structures in purchasing. Customizing: Info Structures Update. Customizing: Updating Rules MC26. Information Structure. Information structures are database tables where the collected data in LIS is stored. There are several info-structures. The customer is allowed to create their own structure. In services we work with the following tables: S011: This is the " Purchasing Group" table which forms the data for the purchasing gorup analysis. S012: This is the "Purchasing" table which forms the data for the vendor analysis. S174: This is the "Service" table which forms the data for the services analysis. Communication Tables. T_* internal tables: The information from the database tables (EKKO, EKPO, EKET, ESLL and EKBE) are passed to the following communication tables: T_EKKO, T_EKPO, T_EKET, T_ESLL and T_EKBE. XMC* internal tables: XMCEKKO: The purchasing document header information is collected in this table. XMCEKPO: The item position information is saved in this table. XMCEKET: The delivery schedule information is stored in this table. BEDAT: Purchasing document date. In some Info-Structures, this field is used to determinate the updating period. See in transaction MC26. XMCESLL: The service information is saved in this table. Every XMC* internal table has an important field called SUPKZ. This field is the statistic update indicator. SUPKZ = '1' means that the sentence contains the information "before" the changes. SUPKZ = '2' means that the sentence contains the information "after" the changes. Notes: The XMC* tables are based on the information from the respective T_* tables. The XMC* tables gets normally two sentences (old and new sentence) when the purchase document is updated. Setup of Statistical data. It reads the purchasing documents and triggers the statistical update of these documents in accordance with the selection on screen. Both archived and actual documents are processed. MCES: Service Analysis for purchasing values in Info Structure S174. MCER: Service analysis for purchasing quantity in Info Structure S174. MC$4: Vendor Analysis with the information from Info Structure S011. MCE8: Service Analysis with the information from Info Structure S174. Important Subroutines in External Services. DIEN_BEREITSTELLEN: The data from service purchase order is determined in this subroutine. BLANKET_BEREITSTELLEN: The information from Limit purchase oder is processed in this subroutine. LIS_DIEN_BEST: It appends old and new sentences in the XMCESLL table. LIS_DIEN_EKBE: Here the communication tables are filled. LIS_DIEN_EKBE_E: The XMCESLL table is appended when GR-based IV is used. LIS_DIEN_EKBE_L: The XMCESLL table is appended when Service based IV is used. LIS_VERTEILUNG_DIEN: The values of GR and/or IR are updated in the XMCEKET table. Update Reports. Report for statistics update in LIS RMCSS174: The info-structure S174 is updated. RMCSS011: The info-structure S011 is updated. RMCSS012: The info-structure S012 is updated. Important Notes. 64636 : Statistical Setup 615786: LIS BW: Wrong BW/statistic data with mov. type 103 600527: Error in statistics updating in service 602618: LIS BW: Wrong goods receipt values in statistics 613338: LIS BW: duplicate entries in XMCEKET. Debugging Steps. Online Process. Reconstruction Process. Interface to Plug In System. Online process: Breakpoint. LIS_VERBUCHUNG in statement: IF flg_bw NE space. Here you can check whether the communication tables are correctly filled. MCEX_UPDATE_CALL: In this function module the information from the communication tables are passed the the Plug In system. Reconstruction process: Breakpoint LIS_VERBUCHUNG_NEW in statement: IF mccontrol-modus EQ con_modus_newbw According with the Plug In release the following function modules are called here: MCEX_UPDATE_CALL_02 MCEX_UPDATE_02. Interface to Plug In System. You can find further documentation in customizing and also in SAPNet alias: MMINT-> Purchasing -> Info Pool for MM Purchasing -> Knowledge Data Base /Components -> MM-PUR-GF-LIS.