Publishing messages

Release Management sends BODs to the ION Connector Service. To complete the new plan, the ION Connector Service uses the ION Messaging Service to publish the PlanningSchedule, ShipmentSchedule and SequenceSchedule BODs to ION. The information is used to create and update the corresponding plans in the target ERP system. The new single plan and the combined plan receive the processing status Current Plan. After the BODs are published, the current single plan and the combined plan are replaced by the newly built plans.

The processing status of the old revisions of the single plan and the combined plan are set to Historic Plan.

If single and combined plan are created for the first time, the status of the corresponding contract line is set to Active.

The cumulative quantities are updated or created with the new data. If the new plan includes shipments, the shipments receive the status Confirmed with the specified date and quantity.

Inclusion of Backorder and Immediate Requirement Types in BODs sent to ERP

When Release Management publishes any plan with a requirement type of Backorder or Immediate, the requirement type must be published In the outbound PlanningSchedule and ShipmentSchedule BODs.

In the outbound schedules, these are the corresponding xpaths:
  • SyncPlanningSchedule/DataArea/PlanningSchedule/PlanningScheduleLine/PlanningScheduleDetail/PlanTypeCode
  • SyncShipmentSchedule/DataArea/ShipmentSchedule/ShipmentScheduleLine/LineType

Inclusion of Backorder and Immediate Requirement Types in BODs sent from ERP

The Backorder and Immediate requirement types are also supported in procurement transactions from the ERP, specifically the SupplierPlanningSchedule and SupplierShipmentSchedule BODs.

These are the corresponding xpaths:
  • SupplierPlanningSchedule/SupplierPlanningScheduleLine/SupplierPlanningScheduleDetail/PlanTypeCode
  • SupplierShipmentSchedule/SupplierShipmentScheduleLine/LineType