SAP Note 1516684 MKPF fields added to MSEG - Performanceoptimization Note Language: English Version: 20 Validity: Valid Since 26.06.2012 Summary Symptom Applications and reports that read material documents have a very long runtime and sometimes terminate with the short dump "TIME_OUT". Other terms MSEG, MKPF, SELECT, JOIN, PERFORMANCE Reason and Prerequisites There is a large number of MM documents in your system. The SELECT statement on the header and item table is very demanding on system performance. Solution ********************************************************************* For more detailed information about implementing the redesign, read FAQ note 1598760 and the information document "MB51_Redesign_Q3_2011.pdf" attached to it. ********************************************************************* This note adds fields from the table MKPF to the table MSEG. The fields from MKPF are now held redundantly in the table MSEG. This enables large gains for the performance of all applications that read material documents. This note supplies the fields for the enhancement of the table MSEG. In addition, a correction is included that updates the new fields of the table MSEG in the same way as the fields in the table MKPF. To fill the existing document items in the table MSEG with the fields from MKPF, a conversion tool is contained in the attachment of this note. Carry out the following steps in the following order: #1. Table changes Use transaction SE11 to add the following fields with the specified data types to the end of all fields of the table MSEG (before the append structures): Data field VGART_MKPF BUDAT_MKPF CPUDT_MKPF CPUTM_MKPF USNAM_MKPF XBLNR_MKPF TCODE2_MKPF Data type VGART BUDAT CPUDT CPUTM USNAM XBLNR TCODE Important: NEVER set the INIT indicator. Save and activate your change. 23.10.2012 Page 1 of 6 You can do this using the report ZMST_FILL_MSEG_FROM_MKPF. Carry out a a database conversion.SAP Note 1516684 MKPF fields added to MSEG . you should execute this report in the background only. Insert the report ZMST_FILL_MSEG_FROM_MKPF from the attachment of this note in your system. If you want. #2. To benefit from the design change. BUDAT_MKPF. MJAHR. Short Description: "Inventory Management: General Control Table" Delivery Class S Display/Maintenance Allowed Data class APPL0 Size category 0 Add the following fields: Field Data element MANDT MANDT ACTION CHAR50 STATUS CHAR1 ENTRY_DATE DATUM ENTRY_TIME UZEIT USERNAME UNAME REPID REPID SAPINT CHAR1 Select MANDT and ACTION as key fields (Key). You also have the option of creating the following index at database level: MSEG~TMP: MANDT. #3.2012 Page 2 of 6 . Use transaction SNOTE to implement the attached correction instructions (step #1 is required for this). How the report works: This report will cause an extremely long runtime. you can then set "Block size" to 23. [Select Material documents for processing] Material Document Year Plant Movement type Block size Number of runs per block size Here you can choose to carry out the conversion for individual documents by entering the material documents in the "Material Document" selection parameter or you can carry it out for a whole material document year in the "Year" field. you can also carry out the conversion for a certain number of document items.10. Therefore. #4.Performance optimization Create the database table MMIM_CONTROL_LOG in the package MB. MBLNR This accelerates the conversion and it can be deleted again after the conversion. the data from MKPF must be filled for the existing documents in MSEG. [Run in update mode] Update MSEG If you want to carry out the conversion. If. You should schedule this only in the background. If all document items have been converted. the system displays the number of the individual documents only. you can plan the jobs as follows: Plant (range) 0001 -> 0050 for Year (MJAHR) 2010 and 2011 individually Plant (range) 0051 -> 0100 for Year (MJAHR) 2010 and 2011 individually In this example. and not about the converted items. "Set conversion complete" This function sets a switch in the client. for example. you must execute the report in update MSEG mode. It displays the number of document items that are still to be converted. "Regenerate MB51" This function must be executed after the conversion is completed.000. for example. the conversion is carried out completely. [Choose mode] "Process material documents" In this mode. If all document items have been converted. you have the option of starting several parallel jobs for the report covering different fiscal years (MJAHR) and.2012 Page 3 of 6 .10. you run 4 parallel jobs to reduce the total run time for the conversion. "Show number of converted documents" This function displays the number of document items that were already converted. the number of document items is not specified. "Show documents to be converted" You can view the status of the conversion using this function. The new logic in transaction MB51 is activated as a result. the system issues a log that contains information about the converted material documents. 23. you are only told that all items have been converted. the MSEG conversion is carried out if the checkbox "Update MSEG" is set.SAP Note 1516684 MKPF fields added to MSEG . the number of document items is not specified.Performance optimization 1. but not the number of items. After the job is finished.000. you are only told that all items have been converted. Transaction MB51 (in accordance with Note 1550000) can then be used with optimized functions. This is about the number of material documents (that is. different plants. you have 100 plants (001 -> 0100) in your system and material documents for the fiscal years 2010 and 2011. If you have many documents in your system. for example. For performance reasons. The function "Number of runs per Block size" specifies how often the number that was specified in "Block size" is to be processed. headers). SAPKH60020 | | Release 602 Until SAPKH60210 | | Release 603 Until SAPKH60309 | | Release 604 SAPKH60401 . Create the database table MMIM_CONTROL_LOG in the package MB. 2. | -----------------------------------------------------------------------|VALID FOR | |Software Component SAP_APPL SAP Application | | Release 500 From SAPKH50001 | | Release 600 SAPKH60001 .SAP Note 1516684 MKPF fields added to MSEG . Implement the report ZMST_FILL_MSEG_FROM_MKPF from the attachment of this 23.Performance optimization -----------------------------------------------------------------------|Manual Pre-Implement.2012 Page 4 of 6 . Use transaction SE11 to add the following fields with the specified data types to the end of all fields of the table MSEG (before the append structures): Data field VGART_MKPF BUDAT_MKPF CPUDT_MKPF CPUTM_MKPF USNAM_MKPF XBLNR_MKPF TCODE2_MKPF Data type VGART BUDAT CPUDT CPUTM USNAM XBLNR TCODE Important: NEVER set the INIT indicator.10. Short Description: "Inventory Management: General Control Table" Delivery Class S Display/Maintenance Allowed Data class APPL0 Size category 0 Add the following fields: Field Data element MANDT MANDT ACTION CHAR50 STATUS CHAR1 ENTRY_DATE DATUM ENTRY_TIME UZEIT USERNAME UNAME REPID REPID SAPINT CHAR1 3. Save and activate your change.SAPKH60410 | | Release 605 Until SAPKH60506 | | Release 606 Until SAPKH60601 | -----------------------------------------------------------------------1. 10. BUDAT_MKPF. SOBKZ.SAP Note 1516684 MKPF fields added to MSEG . BWART. SOBKZ MSEG~M1: MANDT. LGORT. SOBKZ Add BUDAT_MKPF to the index MSEG~M: MANDT. SOBKZ MSEG~M2: MANDT. BWART. Create the following database indexes: o o o MSEG~BUD: MANDT. LGORT.2012 08:06:57 German Correction with high priority Program error MM-IM-GF-PERF Performance Secondary Components: MM-IM-GF-MB MB_CREATE_GOODS_MOVEMENT Valid Releases Software Component Release SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL 600 602 603 604 605 606 From Release 600 602 603 604 605 606 To Release 600 602 603 604 605 606 and Subsequent Support Packages Support Packages SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL SAP_APPL 23. BWART. MATNR. MATNR. 4. BWART. BUDAT_MKPF Header Data Release Status: Released on: Master Language: Priority: Category: Primary Component: Released for Customer 04. MATNR.Performance optimization note in your system. WERKS.09. BUDAT_MKPF. LGORT. WERKS.2012 Release 600 602 603 604 605 606 Package Name SAPKH60021 SAPKH60211 SAPKH60310 SAPKH60411 SAPKH60507 SAPKH60602 Page 5 of 6 . WERKS. WERKS. LGORT. BUDAT_MKPF. MATNR. 10.Side-Effects The following SAP Notes correct this SAP Note / patch: SAP Note Version Version SAP Note Version Reason from to Solution 1516684 1679885 1 1516684 1685136 3 Support Package Correction Instructions Correcti on Instruct ions 1008552 Valid from Valid to Software Component Typ e *) Reference Correction 600 606 SAP_APPL C EBSK093117 Last Changed 21.Performance optimization Related Notes Number 1756236 1679885 1638997 1598760 1567602 1558298 1550000 Short Text MBGR: Redesign of selection for performance optimization MB02: Changes in field XBLNR not updated in MSEG Performance: CKMDUVMAT selection with new fields in MSEG FAQ: MSEG extension and MB51/MB5B redesign DB dependent steps to support the redesign of MB51 MB5B: Redesign of selection for performance optimization MB51: Redesign of selection for performance optimization Attachments File Type TXT File Name Language Size ZMST_FILL_MSEG_FROM_MKPF.03.SAP Note 1516684 MKPF fields added to MSEG . A Postprocessing. M Undefined Work 23.2012 07:05:29 1422497 500 500 SAP_APPL C Y54K919442 10.01.2012 07:02:28 *) C Correction.2012 Page 6 of 6 .txt E 22 KB Symptoms . B Preprocessing.