Constraints for generating nonreferenced purchase schedule linesThe following constraints can prevent Enterprise Planning to generate or update nonreferenced purchase schedule lines:
Frozen zone settings Frozen periods, which you can specify in the Items - Purchase Business Partner (tdipu0110m000), Purchase Contract Line Logistic Data (tdpur3102m000), and Purchase Contract Line Logistic Detail Line (tdpur3102m100) sessions, can prevent schedule lines to be generated or updated. The following frozen time zones are available:
Note
Generation horizon of the patterns In Enterprise Planning, requirements are grouped based on the delivery moments generated in the Generate Planned Delivery Moments (tdipu0225m000) session. In the Generate Planned Delivery Moments (tdipu0225m000) session, you must define a horizon end date. The horizon end date is the date until which the delivery moments are stored in the Planned Delivery Moments (Receipt Based) (tdipu0126m000) session and the Planned Delivery Moments (Shipment Based) (tdipu0125m000) session, from which they can be called on by Enterprise Planning for lead time offsetting. Because delivery moments are not calculated for the period after the horizon end date, Enterprise Planning cannot find valid delivery moment for this period. As a result, for the period after the horizon end date, Enterprise Planning is free to plan its own delivery moments. Expiry date of the contract If requirements fall after the contract's expiry date, valid business partners can no longer be found. As a result, Enterprise Planning generates planned purchase orders without a supplier. In this case, LN sends a signal to Enterprise Planning that a planned purchase order is generated instead of a schedule line. Firm Planned status of the schedule line If you click Firm Planned in the Purchase Schedule Lines (tdpur3111m000) session, a schedule line is made Firm Planned. As a result, the schedule line cannot be changed during the next run of Enterprise Planning. Example
| |||||||||||||