Hierarchy
ECC-DIMP (Software Component) DIMP⤷
IS-A-S2L (Application Component) Production Supply⤷
DI_S2L (Package) Production Supply
IMG Activity
| ID | S2P_GROUP_PLNG_ITEMS | BAdI: Grouping Planning Elements |
| Transaction Code | S_KA5_12001166 | IMG Activity: S2P_GROUP_PLNG_ITEMS |
| Created on | 20020607 | |
| Customizing Attributes | S2P_GROUP_PLNG_ITEMS | BAdI: Grouping Planning Elements |
| Customizing Activity | S2P_GROUP_PLNG_ITEMS | BAdI: Grouping Planning Elements |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | S2L_GROUP_PLNG_ITEMS |
Use
In the supply-to-production table, in the list of planning elements, you can use the pushbutton Group Planning Elements to group planning elements of the same type (for example, APO requirements). This means you can improve the clarity of the table at planning element level. This function only affects the display of the planning elements and does not affect the missing parts calculation.
Using the Business Add-In (BAdI) S2L_GROUP_PLNG_ITEMS you can define your own logic for grouping planning elements.
Requirements
Standard settings
The standard logic groups all consecutive planning elements of the same type (with the exception of replenishment proposals).
Activities
Create an implementation of the Business Add-In and implement the two interface methods IF_EX_S2L_GROUP_PLNG_ITEMS~CHECK_MERGABILITY and IF_EX_S2L_GROUP_PLNG_ITEMS~MERGE. Create a forward declaration for the type pool S2L to enable access to the fixed values listed below.
Method CHECK_MERGABILITY
Using the details data of the current planning element (Import-Parameter: CURRENT_ITEM_DETAILS) and the preceding planning elements (import parameter: PREVIOUS_ITEM_DETAILS), you can determine whether and how a planning element is to be grouped with its predecessor. The method is only accessed if it is basically possible to group the planning element with its predecessor. The predecessor planning element may already contain several grouped planning elements.
You can transfer the following fixed values to the export parameter MERGE.
- S2L_NO_MERGE
Planning element should not be grouped with predecessor. - S2L_STANDARD_MERGE
Planning element is grouped according to standard logic. - S2L_CUSTOM_MERGE
Planning element is grouped according to user-specific logic (MethodeMERGE).
Method MERGE
You can access this method if method CHECK_MERGABILITY provides the fixed value S2L_CUSTOM_MERGE . You can group the current planning element (import parameters: CURRENT_ITEM_DETAILS) with its predecessor (changing parameters: PREVIOUS_ITEM_DETAILS) taking your own user-specific logic into account.
Example
You only want special planning element types (for example, requirements) to be grouped (see example implementation).
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20030120 |
| SAP Release Created in | 471 |
