A user can now create multi-purpose resources that can be used to constrain production, purchasing and stock transfer quantities simultaneously. Additionally, a new resource period type is introduced as an attribute on the resource for all resource types to enable time aggregated resource consumption per resource.
- Model constraints on an aggregated level
- Support additional use cases such as:
- Use multi-purpose resource as a production resource to have multiple production resources with different period types
- Use of a multi-purpose resource as an aggregated constraint
- New resource type multi-purpose resource with flexible source of supply assignment possibilities
- Model all existing resources on an aggregated level
- Flexible period type for all resources
This feature is available only in planning areas based on the flexible sample planning area SAP7F.
If you would like to start using multi-purpose resources, but you have already created the RESOURCELOCATION virtual master data in your planning area, you need to adjust the configuration.
Planning Level DAYPDSRES has to updated accoring to the following:
- In the Planning Areas app, remove all references to the RESOURCELOCATION virtual master data from the Source column for all attributes of the Location master data, but keep this value for at least one attribute which is not relevant for multi-purpose resources, for example, WORKCENTER. See the screenshot to the right.
- Save your changes. The Source Assignment for Attributes field must be now visible and set to User-Defined
The planning area has to be reactivated.
A new resource type is available (type = 4, multi-purpose resource), which can be used as a production and a transportation resource at the same time.
The following resource attributes are available:
- Required: Resource ID, Resource Type, Capacity Consumption Policy (only E - consumption at end is supported), Bucket UoM, Display Bucket UoM, Resource Time Zone
- Optional: Resource Description, Default Capacity, Resource Period Type, Marked for Deletion
- The rest of the attributes must be empty.
The new resource type can be maintained with CI-DS and data integration for the RESOURCE master data.
New attribute Resource Period Type can be used to define the period type of the resource on the resource level. It enables different period types per resource. The period type defines how the defined resource capacity is considered and consumed. The attribute can be used for the new multi-purpose resources and for the existing production and transportation resources as well.
Allowed values: empty (default), D (Day), W (Week), TW (Technical Week), M (Month), Q (Quarter), Y (Year), where the ID is fix, the description is translatable. The default value means that the Resource Period Type setting is read from the Settings for Order-based Planning.
If the period type is not valid due to the time profile setup (the used period type does not exist in the time profile) the master data can be saved, but the default value (Settings for Order-based Planing) is used during the planning run.
Multi-purpose resources can be assigned to any type of source of supply freely: production, external procurement or internal stock transfer.
The assignment can be maintained with CI-DS and data integration for the PDSRES and TLANERESOURCE master data.
Optionally, the resource assignment can be maintained via the Rule-based Master Data Maintenance on an aggregated level (e.g. prudct family). See the next section in this document for en example.
The screenshots show an example where the multi-purpose is used for constraining both production and procurement simultaneously. The production data structure is constrained by both a production and a multi-purpose resource.
- Any resources can be set up as aggregated constraints via the Manage Rules for Master Data Maintenance app. In this section, we will look at an example with multi-purpose resources as aggregated constraints, but the same approach can be used to configure aggregated production resources and aggregated transportation resources.
- There are various use cases for rule-based master data maintenance, including assigning resources to source of supply on an aggregated level. The tool has been delivered with release 2211.
- On the next slides, we provide a step by step setup for multi-purpose resources as aggregated constraints for production and procurement in a factory. Some finished products are produced (Phone A and Phone B), some are procured (Phone C and Phone D). All products belong to the PHONE product group.
Maintain a new resource that serves as an aggregated constraints.
This example has a resource created in the Manage Master Data app:
- Resource Type = 4 (Multi-purpose Resource)
- Period Type = Week (time aggregated consideration and consumption of resource capacity)
- Capacity Consumption Policy = E (as this resource will be used for production and procurement, only consumption at end is allowed)
This new simple master data type defines the aggregated level. In this example, the aggregated constraint is relevant at product group level.
Two rules are required: one for PDS resource assignments and another one for transportation resource assignments. The rules are configured in the Manage Rules for Master Data Maintenance app.
Execute application job Rule-Based Master Data Maintenance with each previously created rules.
All products that belong to product group PHONE have now a multi-purpose resource constraint. Please note that the component materials (product group COMP) are not constrained by this aggregated constraint in same factory.
Existing consumption key figures can be used to display the consumption of multi-purpose resources in the planning views in Planner Workspaces or in the Excel add-in.
Similarly to production and transportation resources, Fiori app displays the consumption details for multi-purpose resources on both Supply and Resource Usage tabs.
When a multi-purpose constraint inhibits the on-time fulfillment of a demand, a resource gating factor is displayed in the View Gating Factors, View Confirmations and in the Order Network.
Existing global Capacity constraint switch is valid for all resources including multi-purpose resource.
New rule-based section Multi-Purpose Capacity Rule enables rule-based inactivation of multi-purpose resources.
Additionally, attribute Resource Period Type is now available for all Capacity Rules.
- App Supply Chain Dependencies doesn't show supply chain networks connected by multi-purpose resources
- No minimum constraints are available
- Further aggregated constraints, for example inventory constraints are not supported