Support for Capturing Additional Attributes at Ship-To Address Level in B2B Contract Recurrence Plans

The current B2B Contract Orders module supports automatic creation of sales orders based on recurrence plans and delivery schedules. As previously proposed (https://watsonsupplychain.ideas.ibm.com/ideas/OH-I-288), there is a need to support additional business-specific attributes within recurrence plans and delivery schedules so that they flow into generated sales orders.

However, in many real-world B2B scenarios, additional information is not always tied to the recurrence plan or delivery schedule itself. Instead, such information may vary based on the Ship-To address, even when the same recurrence plan is used.

Business Scenario

A single recurrence plan may be used to generate orders for multiple Ship-To addresses under the same customer account.

While:

• Frequency

• Product

• Contract pricing

may remain the same,

Delivery-related instructions and operational attributes can differ by Ship-To location, for example:

• Special delivery instructions (e.g., “Deliver only between 8 AM – 11 AM”)

• gate entry details

• Required Level of Service (e.g., Next Day vs Standard)

• Mandatory pallet type

Today, there is no mechanism to capture and persist such additional attributes at the Ship-To level within the recurrence context and have them automatically flow into the generated sales orders.

Note: There is another request logged (https://watsonsupplychain.ideas.ibm.com/ideas/OH-I-304) to generate orders grouped including ship to address along with contract & order date. The current idea here is linked to this specific request.