This activity allows you to modify the planning hierarchy details for the selected planning group. You can select the planning group for which the details are to be modified. You can modify the validity dates and change the status of the planning group in the header.
The planning group or the item retrieved for the selected planning group and the warehouse of the item or planning group can also modified in the multiline. You have the option of deleting the planning hierarchy details of the planning group. You can delete the planning group or item details by selecting the records in the multiline and initiate the delete operation. The system updates the login and system date as a part of modification details.
Select the “Edit Planning Hierarchy” link under the “Supply Chain Model“ business component.
The “Edit Planning Hierarchy” page appears.
Modify the following, if required:
Plg. Group |
The code identifying the planning group for which hierarchy has to be defined. If the planning group is specified, then the hierarchy should have been already defined for the planning group and old valid from combination. |
Press <Enter> key. |
|
The system ensures that the planning group should not be left blank. The planning group must exist in the "Create Planning Group" activity and should be in “Active” status. In case if planning hierarchy exists for the planning group, then the system retrieves the corresponding planning group details in the header and multiline. The system checks the uniqueness of both the planning group and valid from in the header. If valid from is entered, then the system retrieves the planning hierarchy that is valid for the given date, else if valid from is left blank then the system retrieves the existing planning hierarchy for the current date. Otherwise, the system retrieves the last valid planning hierarchy. |
|
Help facility available. |
The system displays the following:
Desc. |
The description of the planning group |
Modify the following, if required:
Status |
Use the drop-down list box to select the status of the planning hierarchy. You can select from “Active”, “Draft” or “Inactive”. The system displays “Active” by default on launch of the page. |
Valid From |
The date from which the hierarchy is valid for the planning group under the plant and warehouse. The system retrieves the planning hierarchy for the planning group entered, which is valid for the given valid from date. If none exists, the system displays an error message. If this field is not specified, then the system sets it as low date. |
Valid To |
The date till which the hierarchy is valid for the planning group under the plant and warehouse. If valid to field is not specified, then the system sets it as high date. If specified, it should be greater than the valid from date. |
Maintained By |
Use the drop-down list box to select the “Maintained By” control units for which the login user has “All” access permission. The system displays “First Value” by default on launch of the page. |
Modify the following in the multiline, if required:
Plg. Group |
The code identifying the planning group in the hierarchy defined for a planning group. |
Help facility available. |
|
Item Code |
The code identifying the item in the hierarchy defined for a planning group. |
Press <Enter> key. |
|
The system ensures that the item Code should not be blank. If an item code is specified, it should be valid for the login Business Unit. If the item does not have variants attached to it, then the system retrieves the item type, description from the Item Planning Parameters screen and the warehouse from the Item-Warehouse Planning Parameters screen. The system sets the standard warehouse as the default warehouse of the default item Organization Unit. If it is not marked, then the system defaults to the first Organization Unit, else none is marked. If the item has only one variant attached to it, then the system retrieves the variant and item type, description from the Item Planning Parameters screen and the warehouse from the Item-Warehouse Planning Parameters screen. The system sets the standard warehouse as the default warehouse of the default item Organization Unit. If it is not marked, then the system defaults to the first Organization Unit, else none is marked. If a variant is specified, It should have been attached to the item code. The system retrieves the item type, description from the Item Planning Parameters screen and the warehouse from the Item-Warehouse Planning Parameters screen. The system sets the standard warehouse as the default warehouse of the default item Organization Unit. If it is not marked, then the system defaults to the first Organization Unit, else none is marked. |
|
Help facility available. |
|
Variant Code |
The code or number identifying the variant of the item in the hierarchy to be defined for a planning group. |
Press <Enter> key. |
|
If a variant is specified, It should have been attached to the item code. If not attached to the item, the system displays an error message else it retrieves the item type and the item variant description from the Item Planning Parameters screen. |
The system displays the following:
Desc. |
The description in the combination of item/item variant. |
Item Type |
The type of the item. The system retrieves the values from “Item Administration” business component. |
Modify the following in the multiline, if required:
Warehouse Code |
The code or number identifying the warehouse of the item that forms a part of planning hierarchy. Mandatory. |
Help facility available. |
Note: If the item code is specified in the multiline, then the warehouse should not be blank. If the warehouse is specified, it should be valid for the item and variant combination.
The system checks whether the warehouse from the “Storage Administration” business component is in “Active” status. If not in active status, then the system displays an error message.
Check the box in the “Select” column of the multiline to mark the details.
Click the “Delete” pushbutton to delete the selected details in the multiline.
The system deletes the rows marked for deletion from the planning hierarchy defined.
Check the box in the “Select” column of the multiline to select the planning hierarchy for modifying its details.
Click the “Edit Planning Hierarchy” pushbutton to create planning hierarchy.
The system ensures that at least one record exists in the multiline before defining the hierarchy. For each row in the multiline, either planning group or item code can be entered. The system ensures that the planning group in header and multiline does not repeat and the item (if specified) and warehouse combination does not repeat in the hierarchy being created. The planning group (if specified) should not repeat in the hierarchy being created.
The system checks whether the item is to be linked to multiple planning groups. If it is not to be linked, then the planning group in the multiline should not be a part of another active planning hierarchy of a different planning group in the header and the planning group should not repeat in the hierarchy being created.
Note: The planning group/item/variant can be part of hierarchy of the parent-planning group more than once if the valid dates do not overlap.
The system saves the planning hierarchy details for the planning group based on planning group or item or warehouse.
Note: The user can only modify the multi-line details in Edit planning hierarchy or change the valid from or valid to date in the header.
The planning group in the header cannot be changed and is enabled only for fetching the details. The system saves the modified Valid From or Valid To fields of the header and inserts the rows modified, or row deleted as marked.
The system updates the login ID of the user to the “Edited By” and the system date to the “Edited Date” field.
The system displays the following:
Created By |
The login ID of the user who created the planning hierarchy. |
Created Date |
The date on which the planning hierarchy was created. |
Edited By |
The login ID of the user who modified the planning hierarchy. |
Edited Date |
The date on which the planning hierarchy was modified. |