Matching Demands

Every (confirmed) demand schedule line creates a so-called Due Delivery (DD). These Due Deliveries are the basis for the subsequent shipping processes. An ASN can be booked only if a valid DD can be matched.

A demand message in SupplyOn SCM is displayed as

• Delivery Instructions
• Orders
• Scheduling Agreement
• Scheduling Response and
• VMI Material demand

Your customer may request a confirmation for all or for some demand messages, before you are able to send a delivery instruction.

A Due Delivery consists of:

• Customer org code
• Customer plant
• Unloading Point
• Supplier Number
• Order number
• Order position
• Material number
• Delivery Date
• Required Quantity

The shipping notification data must be clearly assigned to the due delivery data. Different delivery addresses can be combined and sent in one xml file.

SupplyOn SCM provides a template for the xml-file. To obtain a valid template create an ASN and send it to your customer.

Watch the tutorial or read the pdf in the media library on how to create an ASN.

Important notes:

• Each customer plant can have a different setting for shipping notifications.
• The information which fields the customer has specified as mandatory fields can either be obtained directly from your customer or you can create a shipping notification in SupplyOn SCM. All fields marked in yellow have been defined as mandatory fields by your customer.
• Create a shipping notification (ASN) in SupplyOn SCM and validate it.
• Download the shipping notification (ASN) in xml format.
• How do I get an xml template?
  In addition, download the xml example in xsd format. Open both files with a text editor. The xsd file serves as a reference for the maximum number of files you can transfer. In the following we will explain how an xml can look like using packaging examples.
• In chapters 2.1 to 2.2 we explain the structure which is repeated in all examples.
• We will not explain all possible combinations. Let's take one example:
• A material can have as mandatory field the serial number, batch number and the production date.

Select the ASN in status ‘Sent’, open the drop down menu of ‘Download’ and select

• ‘Selected ASN Messages’ and afterwards
• ‘Template XML File’

Xml Format Description and structure

In order to guarantee an error-free upload, we advise you to adhere to the following format / structure. Ensure that the xml file is always in UTF-8 format to ensure that special characters (e.g. äöü) are processed correctly.

The customer can define packaging rules.

1. No packing data
2. One level packing data
   • inner and outer packing are the same, i.e. you send your goods in a box
3. Two level packing data
   • inner and outer packing are different, i.e. you pack your goods in a box and stack the boxes on a pallet
     • homogenous pallet
     • mixed pallet

Note: These affect the structure of the ASN.

The structure in detail of the ASN xml File:

Shipping Notification full structure

1.   Header
   1.    Addresses
      1.  Address
2.   Material Positions
   1.  Material Position
      1.  Single Packs
         1. Single Pack
3. Handling Unit Items
   1. Handling Unit
4. Single Pack Positions
   1. Single Pack
5. Handling Unit Positions
   1. Handling Unit

Here we explain the parts of the structure that are needed in all use cases explained in the diagram