Automatic creation of sales orders from delivery scheduled lines

Purpose and Benefits

This agent helps both buyers and sellers gain early visibility into planned sales orders, typically 7 to 14 days in advance. The time frame is configurable by using the rule SAFE_DAYS_TO_FULFILL_AN_ORDER. This view helps sellers to understand the on-hand demand. This view also enables proactive manual adjustments to order lines based on current requirements. Typical adjustments are increasing or reducing quantities of an order line, or canceling order lines. These adjustments help to prevent late-stage disruptions such as shipping cancellations or product returns, minimizing operational losses.

Agent execution and processing logic

This agent is designed to run daily, ideally during early morning hours, to help ensure the timely creation of sales orders that are based on delivery-scheduled lines. Since the minimum granularity for automatic order delivery is one day, daily execution provides a way for the agent to generate sales orders each day as planned in the delivery-scheduled lines. Whenever the agent runs, it considers all available delivery-scheduled lines with an OrderDate on or before the current date, within the defined window. The SAFE_DAYS_TO_CREATE_ORDER_FOR_MISSED_DSL rule defines the window. The default is three days. The agent ignores any delivery-scheduled lines that are outside of the window range.

When creating a sales order, the system uses the DefaultFromContractOrderTemplate and DefaultFromContractOrderLineTemplate templates defined under the Order Fulfillment process type. These two templates determine which entities and corresponding attributes from the contract order and contract order lines are copied to the generated sales order and sales order lines. You can customize these templates to control which entities and attributes are included in or excluded from the sales order creation process.

The OMPCreateOrderFromDeliveryScheduledLinesAgent agent can also invoke the YFSBeforeCreateOrderUE user exit during automatic sales order creation from a contract. This invocation of user exit provides you a place holder to modify or override any attribute on the sales order before it is created.

This agent is a non-enterprise agent that when triggered, processes all contract orders with unconsumed delivery-scheduled lines across the system. It can be auto-triggered, with early morning execution recommended for optimal performance.

Order grouping logic

The yfs.contract.create.automatic.orders.by.shipto configuration property defines how delivery schedule lines are grouped when creating sales orders.

By default, the yfs.contract.create.automatic.orders.by.shipto is set to N.

Validations

To help ensure accurate order creation, the agent performs several validations on delivery-scheduled lines. Quantity validations make sure that the delivery-scheduled line quantities do not exceed the remaining contract order line quantity. For example, an account manager creates manual sales orders or changes the contract order lines. If the scheduled quantity exceeds the remaining contract order line quantity, the delivery-scheduled line is marked as closed and excluded from processing. This type of validation check prevents over-ordering and maintains contract integrity.

In addition to quantity checks, contract relevance checks verify whether the contract line, contract tenure, or contract order are still valid. Delivery-scheduled lines that are tied to outdated or canceled contract orders are marked as closed. For example, modifications are made to close a contract order, reduce the tenure, or cancel a contract order line. If the agent performs a check and determines that the contract line that corresponds to the delivery-scheduled line is not relevant, mark the contract order as closed to avoid processing outdated or invalid data.

Related information

For detailed configuration and implementation information for the OMPCreateOrderFromDeliveryScheduledLinesAgent agent, see Create order from delivery scheduled lines.