Show TOC

Background documentationPrerequisite: Clean Up Total Requirements

 

Before activating the business function, you have to make sure that you have no total requirements in your system. Proceed as described below to deal with your total customer requirements and your total dependent requirements.

Procedure

Procedure for dealing with total customer requirements

Originally, there were two alternative ways of transferring customer requirements from Sales and Distribution (SD) to Material Requirements Planning (MRP): Individual requirements and total requirements. Individual requirements are stored in table VBBE, whereas total requirements are stored in table VBBS. Table VBBS stores the total demand for a material, plant, and requirement date. This causes a massive amount of data to be loaded, stored, and aggregated on the database at the same time which, on the one hand, speeds up the demand reading process. However, on the other hand, the data involved is locked for further processing; different sales orders requiring the same material at the same date cannot be posted in parallel, for example. When using an in-memory database such as SAP HANA to execute your planning run, however, total requirements are no longer necessary. Your customer demand is aggregated individually at runtime — without having a negative impact on the performance of your MRP.

  1. Check whether you have total customer requirements in the system. Use the data browser (transaction SE16) for table VBBS and check the number of entries in that table.

    • If there are no entries in table VBBS, you have no total customer requirements and therefore you do not have a problem. In this case, proceed with step 7.

    • If you have entries in this table, you have total customer requirements and you should proceed with step 2.

  2. Check whether you can safely use individual customer requirements. For example, check whether you have custom reports that evaluate table VBBS. These reports should read table VBBE instead.

  3. Check the ATP (Available-to-Promise) checking group in Customizing. The ATP checking group defines whether total or individual requirements are created for sales orders.

    • In Customizing for Sales and Distribution, under Start of the navigation path Basic Functions Next navigation step Availability Check And Transfer of Requirements Next navigation step Availability Check Next navigation step Availability Check with ATP Logic or Against Planning Next navigation step Define Checking Groups End of the navigation path, determine the ATP checking groups with total requirements; an ATP checking group with “B” (Totals records per day) in column TotalSales or TotDlvReqs creates total requirements. If no checking group exists with this entry, the entries you found in table VBBS are meaningless. In this case, proceed with step 7.

    • If such a checking group exists, either delete the ATP checking groups that create total requirements or change their TotalSales and TotDlvReqs attributes in Customizing from “B” (Totals records per day) to “A” (Single records). This prevents the usage of incorrect ATP checking groups in future. Proceed with step 4.

  4. Create and execute the ABAP report Z_MATERIALS_W_COLLECTIVE_REQS (transaction SE38) to determine which materials use the ATP checking group that creates total customer requirements. This report finds all the materials with the ATP checking group “01” that creates total requirements. Note that if you have different checking groups that create total requirements, you have to adjust the ABAP report accordingly:

    Syntax Syntax

    1. data:
  ls_marc type marc.

select matnr werks from marc into (ls_marc-matnr, ls_marc-werks) where mtvfp = '01'.
  write: / ls_marc-matnr, ls_marc-werks.
ENDSELECT.
    End of the code.

    • If the system does not find any materials, your VBBS records are meaningless. In this case, proceed with step 7.

    • If the system finds materials for which the ATP checking group is “01”, proceed with step 5.

  5. For every material found by the report in step 4, open the MRP 3 View of the Material Master in change mode and select an ATP checking group that creates individual requirements.

  6. For each material, execute report SDRQCR21, “Recovery of Sales and Delivery Requirements” to recreate the customer requirements

  7. Check whether you have implemented any of the methods of the BAdI MD_CHANGE_MRP_DATA. If you have and if the BAdI only adds data to MRP evaluations such as MD04, re-implement your BAdI implementations in BAdI MD_ADD_ELEMENTS.

    Note Note

    The BAdI MD_ADD_ELEMENTS is processed in MRP evaluations such as MD04 or MD07 and is processed in the classic MRP transactions MD01 or MD02. MRP Live (transaction MD01N) does not process BAdIs for materials that are planned in HANA completely. Materials that require changes of the planning logic in BAdIs should be planned using classic MRP. The classic MRP run is performed by the classic MRP transactions such as MD01 or MD02 or if you have set the Plan in Classic MRP indicator for the material in the report Include Material in Classic MRP (transaction MD_MRP_FORCE_CLASSIC). Check which materials require the processing of a BAdI during the MRP run and set the Plan in Classic MRP indicator for these materials.

    End of the note.

Procedure for dealing with total dependent requirements

  1. Now check whether you have a problem with total dependent requirements. Use the data browser (transaction SE16) for table RQIT and check the number of entries in that table.

    • If there are no entries in table RQIT, you have no total dependent requirements and therefore you do not have a problem. In this case, proceed with step 5.

    • If entries exist in this table, you have total dependent requirements and you should proceed with step 2.

  2. Create a planning file entry for every material in table RQID (transaction MD20) and set the Net change planning and the Re-explode BOM indicators

  3. If you work with repetitive manufacturing, you have to check and, if necessary, switch off the Aggregate reqmts indicator in the repetitive manufacturing profiles in Customizing for Production. In combination with the collective requirements indicator in the material master, this indicator determines whether dependent requirements are grouped to collective requirements on a daily basis.

    In Customizing for Production, under Start of the navigation path Repetitive Manufacturing Next navigation step Control Data Next navigation step Define Repetitive Manufacturing Profiles End of the navigation path, check the Control data 2 tab for each profile to see whether the Aggregate reqmts checkbox is selected. Remove the selection, if necessary.

  4. Execute an MRP run which re-explodes all BOMs for the affected materials and creates individual dependent requirements.

  5. Create number range PP for planned orders, purchase requisitions, and reservations.