Grouping of Component Requirements
Use
For components that are set in the material or product master so that they can be grouped, the SAP APO calculates the total dependent requirements per period from the results of the component variant matrix. The periods are freely definable. This has the advantage that it is not necessary to generate a procurement element for each individual dependent requirement. It is only necessary to generate one procurement element for the dependent requirements that fall within a certain period. This considerably reduces the volume of data.
Integration
The SAP APO calculates the total dependent requirements of a component for freely definable periods. If you continue planning for these components in the DI system, the periods within a day are grouped into days when these grouped requirements are transferred.
Example
Production is executed on a two-shift basis. You have set shifts as the periods for grouping in the SAP APO. The SAP APO calculates a total for shift 1 and 2. When the requirements are transferred to the DI system (during the planning run), the system displays the total for shift 1 and 2, because the DI system can only calculate on a daily basis.
Prerequisites
In Customizing for Production Planning and Detailed Scheduling, you have maintained one or more period profiles in the IMG activity
Maintain Period Profile for Grouping of Component Requirements.
If you create various period profiles, you can group the various components according to different rules. It can be useful, for example, to set a daily grouping for components that are to be planned further in the DI system and, in contrast, in the short term to set hourly grouping for APO components.In the product masters for the components, you have selected
Always coll. requirements
and assigned a period profile.
Features
In the first step, the matrix copies the exact requirements dates for the components .
The system then determines the periods for grouping a component using the period profile in the product master. The period profile is not dependent on the location or the factory calendar. The system uses the assignment in the product master to determine the necessary line resources, and thereby the valid shift sequence for the resources, as well as the factory calendar. The system uses the entries for the period profile, the shift sequence and the factory calendar to determine the periods in which the dependent requirements are to be grouped.
For example, you can use a period profile to determine that the dependent requirements are to be grouped monthly in the long-term horizon, weekly in the mid-term horizon and daily or by shift in the short-term horizon. In addition, you can define user-specific periods within a shift. For example, each hour should be the start of a new period, in which case the dependent requirements are grouped on an hourly basis.
In the last step, the system generates all requirements for a component that fall within a period and groups these together. Planning continues on the basis of the total requirement.
Example
The requirements dates for the component A, which is required 2 days after the planning day (= today), are 6.00 am, 6.10 am, 6.20 am, 6.30 am and so on. The requirements quantity for each order is to be 1 piece.In the period profile, you have defined that the requirements are to be grouped on an hourly basis, that means, the system determines the time period from 6.00 am to 6.59 am as period 1 for the following day. The system groups the requirements that lie within this period and calculates a total requirement of 6 pieces.