plan.autoFenceOperations setting in parameters and per operation #480
-
|
I would like to clarify the explanation for Release Fence on the following link. The plan.autoFenceOperations in parameters setting is the default value for each operation if I endable the FENCE in the constraint planning. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
These are 2 different things: The plan.autoFenceOperations is to let the solver know how long it can wait for existing confirmed supply before proposing another replenishment. Example: You have a PO due in 10 days. If plan.autoFenceOperations is 14, the solver will not propose another PO and wait for that one (provided its quantity covers the need). If plan.autoFenceOperations is 7, then another PO will be proposed. The fence constraint is to respect the release fence field at operation level (operation + item supplier + item distribution). The solver will not propose any PO/MO/DO within the release fence. There is no default parameter for the release fence, it has to be set for each record of operation/item supplier/item distribution. |
Beta Was this translation helpful? Give feedback.
These are 2 different things:
The plan.autoFenceOperations is to let the solver know how long it can wait for existing confirmed supply before proposing another replenishment. Example: You have a PO due in 10 days. If plan.autoFenceOperations is 14, the solver will not propose another PO and wait for that one (provided its quantity covers the need). If plan.autoFenceOperations is 7, then another PO will be proposed.
The fence constraint is to respect the release fence field at operation level (operation + item supplier + item distribution). The solver will not propose any PO/MO/DO within the release fence. There is no default parameter for the release fence, it has to be set for each reco…