MAC-PAC Homecontact ussupport login 
Documentation > MAC-PAC Reference Library > Distribution > Synchro > Key Concepts and Procedures > Delivery Conditions

Delivery Conditions

 

Customer delivery conditions define the splitting rules used in determining the daily delivery schedule of items ordered by period.  The customer can send you a delivery request containing releases by period or delivery request releases by date.  See the Delivery Request Key Concept in this overview for more information about delivery requests and their associated releases.  For releases by period, the system will search for the associated delivery conditions to split and offset the releases.  See the Splitting and Offsetting of delivery request releases Key Concept in this overview for more information.

Splitting rules can be defined at two different levels:

·     Ship-to Customer Level

Splitting rules are defined at this level through the Delivery Conditions Maintenance conversation.  For each day of the week, you can enter a relative quantity, for use in splitting releases by period.  The splitting rules you enter in this conversation apply to all delivery points associated with this bill-to/ship-to customer combination, unless overridden in the specific endorsement.

The system does not automatically apply a splitting rule change to all the attached endorsements.

·     Endorsement Level

You can override the splitting rules assigned to the bill-to/ship-to customer combination by defining specific splitting rules for a specific item/delivery point on the endorsement.  These splitting rules will supersede the splitting rules associated with the customer, and will apply specifically to the item/delivery point.  When no specific splitting rules are defined on the endorsement, the splitting rules associated with the delivery conditions are used.

·     Type of EDI Transmissions

What type of EDI Transmissions, if any, this customer is sending.  This code is set up on Reference File category G28 (Transmission Types).  Currently, Synchro supports only the ODETTE, VDA, and ANSI protocols.  Customer KANBAN supports only the PLUQUO and KANBAN messages.

·     Invoice EDI number

You can compare this invoice EDI number to a mail box where all the EDI messages generated by the same supplier are sent.  Similar to DELINS/VDA Acquisition processing, a third party company can manage this mail box and dispatch the messages to the corresponding customers.  For VDA processing, the system associates the invoice EDI number to the ship-to customer.  Since the VDA standard 4913 does not distinguish between the message sender and the ship-to customer, this value must be identical to the sender EDI number.

·     Purchasing department used to identify the department to invoice.

 

These delivery conditions specify the splitting rules for a normal week.  Each day is associated with a relative quantity showing the allocation of quantities to be shipped daily.  These conditions apply only to delivery request releases by period.  For releases by date, (when the customer has ordered a specific quantity for a one day period) the ordered quantity is delivered.