MAC-PAC Homecontact ussupport login 
Documentation > MAC-PAC Reference Library > Distribution > Synchro > Key Concepts and Procedures > Synchro Demand > Sources of Demand Issued by Synchro

Sources of Demand Issued by Synchro

 

·     Each offset release constitutes a need for the item positioned in preparation date (planned independent request); this remains true as long as the shipping date of the offset release is not reached, at which time the offset release will become closed.

·     At any time, the left to be shipped field is considered as immediate need.  If this value is negative (delivery advance), it is netted against future release quantities. 

The nature (firm or planned) of the release, as well as the shipper synchronization data play an important role in the MAC-PAC planning functions.

Firm and planned releases are treated similarly to the Order Processing sales orders.  Additionally, Synchro allows the system to propose the planned releases for shipment.  This is done by setting the Ship Planned Schedule flag on the endorsement to Y.  The Ship Planned Schedule flag works through the Master Scheduling, Requirements Planning, Inventory Control, and Just in Time modules as follows:

Master Scheduling:  This module sees planned offset releases regardless of the value of the Planned Schedule flag.

Requirements Planning:  Same as Master Scheduling.

Inventory Control:  The Component Availability/Order Shortage report and the Component Availability Inquiry do not see Planned Offset Releases with a Planned Schedule Flag equal to N.

Just in Time:  Wherever the system displays availability, just in time does not take into account Planned Offset Releases when the Planned Schedule Flag equals N.

The update of the synchronization data modifies the advance/backorder status for an item/delivery point.  These changes are immediately taken into account by the planning modules, either as new "in-shipment" value when the outcome is a backorder, or by reducing (netting) the future releases for that item/delivery point when the outcome is an advance.  Note that when an advance occurs for an item/delivery point, if no future release is yet available, no netting takes place and the planning modules will ignore this "negative" demand.  Any further synchronization changes reset the in-shipment or netted release quantity accordingly.