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.

Customers can use this PlanningSchedule to communicate demand requirement in three different ways. It can be as specific as the Item level or at the Commodity code level, which is higher than item. Furthermore, it can be required simply by functional specification via feature identifiers and values using the optional component FeatureValues.

The purpose of the ShowPlanningSchedule is to communicate to a business application module or system the sending systems representation of PlanningSchedule information. This request may be used as a response to a GetPlanningSchedule request or as a push notification of an event.