You use this program to capture and maintain resource structures (i.e. to indicate the relationship between the resource parent assigned to a stock item and its components).
Field | Description |
---|---|
Change Resource | |
Change Resource | Select this to indicate a different resource parent item for which you want to maintain the structure. |
Save | Select this to save your changes. |
Resource parent | Indicate the resource parent code for which you want to maintain the structure. |
Once you have entered a valid parent resource, the component resources for the parent are displayed in an editable listview. You use this listview to maintain the details for resource parents.
Field | Description |
---|---|
Resource | Indicate the component resource code. |
Description | This indicates the description held against the resource component and is displayed for information purposes. |
Uom | This indicates the unit of measure for the resource component and is displayed for information purposes. |
Quantity per |
Indicate the quantity of the resource component required for each resource parent code. The number of decimals that can be entered here is determined by the option: Number of decimals in resource quantity per (Requirements Planning Setup). |
Offset days |
Indicate the number of days before or after the due date of the finished product that the component is required. A positive value indicates the number of days before the due date, while a negative value indicates the number of days after the due date of the finished product that the component is required. |
Indicating the relationship between the resource parent assigned to a stock item and its components involves the activity of creating a bill of resources for critical constraints to test the feasibility of the MPS (or the direct product demand that exists at this planning level, if you are not using an MPS).
For example, perhaps you want to ensure that you have enough capital and storage space to manufacture different types of bicycles stated on the MPS. You would create a resource code and attach these two constraints as resource components, with a quantity of the dollars required to make one bicycle and the quantity of space needed to store a finished bike until sold.
You enter the resource parent code and then add each resource component relationship, which includes the quantity per and the offset days. You use the offset days to indicate the number of days before or after the due date of the finished product that the component is required.
When you run the Resource Explosion program, the structure you created is exploded to obtain the load profile for the MPS (or the direct product demand that exists at this planning level, if you are not using an MPS).