Hierarchy
MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net⤷
PM-WOC-MO (Application Component) Maintenance Orders⤷
/MRSS/SGE (Package) Multiresource Planning: Scheduling Engine
IMG Activity
| ID | /MRSS/BUND0110 | Set Up Bundle Groups |
| Transaction Code | /MRSS/92000341 | (empty) |
| Created on | 20130104 | |
| Customizing Attributes | /MRSS/BUND0110 | Set Up Bundle Groups |
| Customizing Activity | /MRSS/BUND0110 | Set Up Bundle Groups |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /MRSS/BUND0110 |
Use
In this Customizing activity, you set up bundle groups. By creating bundle groups you specify which types of demands and demand items can be bundled in the planning board.
Based on the settings you make in this Customizing activity, the system filters the demands and demand items according to the following criteria:
- Planning node
- Abstract order type (for example, PM order type or CRM transaction type)
- Abstract item type (for example, PM control key or CRM item type)
- CRM service product
- PM activity type
- Bundle group ID
You can only bundle demand types that have been assigned the same bundle group ID.
Requirements
Standard settings
Make sure to perform this Customizing activity in each system individually (development, quality, production system).
Activities
Create entries by specifying at least a bundle group ID. You can be more specific, for example, by specifying the order and item type. You can also enter an asterisk <*> in these fields. In that case, the system permits all order or item types to be bundled.
Example
You create 4 bundle groups by making entries as follows:
Planning Node Order Type Item Type PM Activity Type CRM Servi.Product Group ID
50001855 PM01 PM01 CIM 1
50001855 PM01 PM01 Maintenance 1
50001855 PM01 PM01 Service Order 2
50001855 PM01 PM01 Emergency Order 2
50001856 PM01 PM01 Turbine Warning 2
50001856 PM01 PM01 Emergency Order 2
50001856 PRODUCT1 3
50001856 PRODUCT2 3
50001856 PRODUCT3 4
The planning node structure is as follows:
Planning Node Description
50001855 Germany
50001856 Region North
50001857 Region South
In this example, for demands belonging to planning node 50001855, the PM activity types CIM and Maintenance can be bundled since they have been assigned the same bundle group ID 1.
Other PM activity types like Service Order cannot be bundled with the previous ones. Instead you can bundle activity types Service Order and Emergency Order since they have been assigned the same bundle group ID 2.
You can also bundle demands that belong to different planning nodes. For example, for demands that belong to planning node 50001856, the PM activity types Emergency Order and Turbine Warning are assigned bundle group ID 2. Therefore, those demands can be bundled with service orders and emergency orders that belong to planning node 50001855.
Since there is no explicit entry for planning node 50001857, the system inherits the settings from the upper level, that is, from the superordinate planning node 50001855. Therefore, all parameters that are entered for planning node 50001855 are also valid for planning node 50001857.
Similarly, for CRM orders in planning node 50001856, the demands with product IDs PRODUCT1 and PRODUCT2 can be bundled since they have been assigned bundle group ID 3. PRODUCT3 cannot be included in this bundle since it has been assigned bundle group ID 4.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | /MRSS/BUND0110 | 0 | /MRSS/WFF0000002 | SAP Multiresource Scheduling |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| /MRSS/V_BUND_GRP | V - View | SM30 |
History
| Last changed by/on | SAP | 20130524 |
| SAP Release Created in | 800 |
