Create Child Despatch Orders

For context, see Parent and Child Despatch Orders, Aggregated Parent Despatch Orders (APDOs) and Consignment Parent Despatch Orders (CPDOs).

The PDO and all of its child despatch orders (CDOs) must belong to the same contract. However, each CDO can have different specifications, required quantity, planned despatch date, and so on. Each CDO can be loaded in one or many despatches, and can have its own set of samples.

For APDOs, invoicing is either by APDO or by CDO. See Configuration for Aggregated Parent Despatch Orders.

For CPDOs, both the CPDO and the CDOs can be invoiced; however, only the CDOs can have payable invoice installments. See Configuration for Consignment Parent Despatch Orders.

CDOs cannot be created for:

• Linked despatch orders
• APDOs that have already been added to a despatch
• DOs in a trade between a sales DO and a purchase DO

Note: The business rules for APDOs and their CDOs, and for CPDOs and their CDOs are quite different from the rules for Split Parent Despatch Orders (SPDOs). The CDOs of an SPDO are created via the SPDO, and may come from different contracts; or the CDOs are created by MineMarket for cumulative pricing.

Security Note: You need the Allow the user to maintain despatch orders security right in the Contracts domain security rights group for this activity.

Activity Steps

1. Open the Sales Contract or Purchase Contract.
2. Select the Despatch Orders node for the contract product.

   Note: You can also create CDOs via the Despatch Orders tab on the node for the quota.

3. To apply a date range to the search, check Include Date Range and select the Start Date and End Date.
4. Enter a Search Name if required.
5. Click Search.
6. Right-click the despatch order that will become the APDO or CPDO and select Create Child Despatch Orders from the menu.

   The Create Child Despatch Orders screen displays.

7. Complete the following fields as required.
   • Start Date—Planned despatch date for the first CDO. If the offset is zero days, this date applies to all CDOs.
   • Number of Despatch Orders—Number of CDOs to create at once.
   • Offset—Period of time between the CDO dates.
   • Offset Unit—Select from Days, Weeks and Months.
   • Quantity—Amount of material to be despatched in each CDO.
   • Unit—Unit of measure for the quantity. Select from the Mass units defined in the Unit Conversion Editor.
   • Quota—Select from the quotas in the contract product if creating CDOs from the Despatch Orders node. Set to the current quota if creating CDOs from a Quota node.
   • Planned Loading Location—Select from the locations defined on the Supply Chain panel of the Solution Explorer. Default: The Contractual Source of the quota, if specified.
   • Planned Unloading Location—Default: The Contractual Destination of the quota, if specified.
   • Package Type—Select from the package types defined on the Supply Chain panel of the Solution Explorer. For package types with limited Allowed Products, only the package types that are applicable to the contract product display.
   • Ignore For Hedging—Whether to ignore the CDOs for hedging. If checked, the CDOs will not be displayed when searching for DOs to hedge.
   • Nominated Product—If Allowed Nominations are specified for the contract product, select from the contract product and allowed nominations. If Allowed Nominations are not specified for the contract product, the nominated product can only be the product of the contract product.
8. Click Create.

   A message displays the status of the CDO creation.

9. Click OK.
10. Close the Create Child Despatch Orders screen.
11. If the PDO is to be an APDO, see Configure Invoicing for an Aggregated Parent Despatch Order and its Child Despatch Orders.
12. If the PDO is to be a CPDO, see Configure a Consignment Parent Despatch Order.
13. Click Save.

    Note: If the Despatch Order status definition exists, the CDOs are assigned the initial status. This status definition controls whether the CDOs are editable and selectable. See Status Definitions.