Since collaboration between a customer and a supplier can potentially go through several rounds of negotiations, both parties can use the same BOD to communicate their current demand or supply schedule in response to what they received from the other party. Either party can indicate detailed exception descriptions along with reason code and action code to the other party why the original demand/supply requirements need to be adjusted using the optional Data Type PlanningScheduleException.

The purpose of the ChangePlanningSchedule is to enable a business applications module to request this Planning Schedule information be acted upon by another business application. The response to this BOD is AcknowledgePlanningSchedule.