This activity allows you to determine the time fence rules. Tell me more
Select the “Maintain Time Fence” link under the “Supply Chain Model“ business component.
The “Maintain Time Fence” page appears.
Enter the following:
Time Fence Code |
The unique code identifying the time fence defined for the item. Mandatory. The time fence code should not be blank and should exist in the time fence master for the login Business Unit . |
Click the “Get Data” pushbutton to retrieve the time fence details.
The system retrieves the time fence details for the specified time fence code. The system sorts the time fence details according to the time fence (days) in ascending order.
Description |
The description of the time fence. |
Zoom facility available. |
|
Status |
The status of the time fence. You can select from ”Active” or “Inactive” or “Draft". The system displays "Active" by default on launch of the page. |
Demand Time Fence (days) |
The demand time fence for the item. During planning process, only actual demands are considered within the specified time fence (current date + time fence). Forecast demands, if any, will not be considered. You can specify positive and negative values. |
Planning Time Fence (days) |
The planning time fence for the item. During planning process, new receipts are not suggested within the specified time fence (current date + time fence). If this field is specified, it should be greater than or equal to zero. |
Accepted Time Fence (days) |
The accepted time fence for the item. During planning process, if any receipts are pending in "Suggested" status within the specified time fence (current date + time fence), then the system can change status to "Accepted". If this field is specified, it should be greater than or equal to zero. |
Enter the following in the “Time Fence” multiline:
Time Fence (Days) |
The time difference in days from the due date of a work order. If the current date falls within this time fence, then the system can effect automatic amendment of the work order based on the quantity and time changes allowed. If specified for the first row, it should be greater than zero. The system ensures that the specified time fence values cannot be the same. |
Qty %(+) |
The percentage by which the quantity of a work order can be increased by the system corresponding to the time fence defined.. If this field is specified, it should be greater than or equal to zero. |
Qty %(-) |
The percentage by which the quantity of a work order can be decreased by the system corresponding to the time fence defined. If this field is specified, it should be greater than or equal to zero. |
Time In Days (+) |
The time (in number of days) that can be increased by the system from the work order due date corresponding to the time fence defined. If this field is specified, it should be greater than or equal to zero. |
Time In Days (-) |
The time (in number of days) that can be decreased by the system from the work order due date corresponding to the time fence defined. If this field is specified, it should be greater than or equal to zero. |
Check the box in the “Select” column of the multiline to mark the time fence details.
Click the “Delete” pushbutton to delete the selected time fence details in the multiline.
The system updates the time fence by deleting the selected rows in the multiline. If none of the details are specified in the header or multiline then the system deletes the time fence record.
Click the “Edit Time Fence” pushbutton to modify the time fence.
Note: If either “Qty (-)”, “Qty (+)”, “Time in Days (-)” or Time in Days (+)” are left blank, then the system assumes that there are no time fence restrictions on such a parameter.
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 time fence. |
Created Date |
The date on which the time fence was created. |
Edited By |
The login ID of the user who modified the time fence. |
Edited Date |
The date on which the time fence was modified. |