Sort Profile
The sort profile determines the sequence in which the system should link the requirement elements with the receipt elements using fixed pegging.
· In the sort profile, you specify the criteria that are used to sort the requirements. The system uses the sort profile to prioritize the requirements and by doing so, to determine the sequence in which these requirements are assigned. The sort profile is used to sort both the independent and the dependent requirements. You can define, for example, that sales orders have a higher priority. By doing this, you can ensure that the existing receipt elements are assigned to the sales orders first.
· You only use the sort profile in the settings for the heuristic Creation of Fixed Pegging Relationships if you want to create fixed pegging relationships on the basis of user-defined settings.
The sort criteria are sorted in the sort profile in order of importance. You can specify for each criteria whether the values should be sorted in ascending order, descending order or in a special order.
As a default, the sort profile SAP_FIXED_PEGGING is proposed for the creation of fixed pegging relationships. However, in Customizing for Production Planning and Detailed Scheduling under Heuristics, you can create your own sort profile and define a special sorting. See also: Define Sort Profile.

In the sort profile SAP_FIXED_PEGGING, the special sorting for the sort criteria ATP category has not yet been maintained, because the special sorting in SAP APO is valid for all applications. If you have already defined a special sorting for ATP, then this special sorting is also valid for the sort profile that you use for creating fixed pegging relationships and vice versa.
The settings for the sort profile SAP_FIXED_PEGGING are as follows:
Priority (Order of Precedence) |
Sort Criteria |
Sorting |
1 |
ATP category |
Special sorting (not maintained yet) |
2 |
Confirmed quantity |
Descending |
3 |
Desired quantity |
Descending |
4 |
Delivery priority |
Ascending |
5 |
Material availability date/Requirement date |
Ascending |
The way the system sorts the requirements depends on the Pass On Independent Requirements Information indicator:
If you have not set the indicator, the system carries out sorting for each sort criteria according to the sort profile. For example, if you have selected ATP Category as the sort criteria and have filtered out sales orders, planned independent requirements and dependent requirements, the system first sorts all sales orders, then all planned independent requirements and then all dependent requirements according to the settings in the sort profile.
In the following example, the sort profile SAP_FIXED_PEGGING is used:
In the filter, the ATP categories for sales order, planned independent requirement and dependent requirement were selected.
Requirements Product A |
Requirement Date |
Planned independent requirements |
9.18.2004 |
Planned independent requirements |
9.24.2004 |
Sales order |
9.20.2004 |
Sales order |
9.252004 |
Requirements Component B |
Requirement Date |
Dep. req. 1 |
9.15.2004 |
Dep. req. 2 |
9.20.2004 |
Sort result for product A
The system first sorts the independent requirements according to ATP category. Within an ATP category, the system then sorts according to requirement date. The independent requirements then have the following order of precedence:
Level of Priority |
Requirement |
Requirement Date |
1 |
Sales order |
9.20.2004 |
2 |
Sales order |
9.25.2004 |
3 |
Planned independent requirements |
9.18.2004 |
4 |
Planned independent requirements |
9.24.2004 |
This is the sequence is which the system assigns the requirements to the receipt elements and then creates fixed pegging relationships.
Sort result for product B
The dependent requirements for product B are sorted according to requirement date:
Level of Priority |
Requirement |
Requirement Date |
1 |
Dep. req. 1 |
9.15.2004 |
2 |
Dep. req. 2 |
9.20.2004 |
If you have set the indicator Pass On Independent Requirements Information, the system passes on the sort criteria of the independent requirements:
Before the requirements for which the system is to create fixed pegging relationships are sorted, the system determines the pegged independent requirements. The independent requirements information, such as ATP category and delivery priority, is passed on to the dependent requirement, in accordance with the criteria in the sort profile. The dependent requirements are then sorted on the basis of the criteria that have been passed on.
Example for Passing On Sort Criteria
Dependent requirement 1 from September 15th, 2004 is caused by a planned order that is linked to a sales order by fixed pegging. The category BM (sales orders) and the earliest requirements date of the requirements (09.15.2004) is passed on to the dependent requirement. Dependent requirement 2 is caused by a planned order that is linked to a planned independent requirement by fixed pegging. Therefore the category FA (planned order) is passed on to dependent requirement 2. This leads to the sequence: Dependent requirement 1, followed by dependent requirement 2.