Allow Contract Sales Order Creation Before Contract Start date based on future Requested Delivery Date

As mentioned above the sales order from contract must be created within the active contract order period (also known as contract order tenure) as it is an execution part than a planning part.

But I can provide another option to address the requirement.

When a user creates a sales order from a contract which is yet to start, s/he must provide a date on/after the start date of contract as sales order OrderDate. For a business entity like order, the OrderDate matters more and business operations on order look upon and/or honours OrderDate. Therefore, even though an order entry is made to the system early, for all practical purpose the OrderDate is considered as the date on which the order was taken.

Later at any point of time when anyone looks into the sales orders created from a contract, s/he sees all orders were taken during the tenure of the contract order.

The createOrderFromContract API that creates sales order from contract takes an OrderDate in the input. I don't know whether UI gives a provision to read OrderDate while creating a sales order from Contract.

So, if Rensa still bind to the requirement of creating sales orders early from a contract which is yet to be active, this is the only way we can address it. If this approach is fine, we can verify the current behaviour of both API and UI and make enhancements if needed.

The requested delivery date has NO role to play either in defining a contract order or on deciding when sales orders can be created from a contract order. For a sales order it naturally follows the order date, and users are supposed to give a date after the order date. It is always set manually for the sales orders created from contract manually during the life cycle of the contract order.

The requirement in the OMS application - 'A contract order reaching a confirmed state and also reaching the start date, are the prerequisite for creating orders from contract', aligns with standard business, legal, and operational best practices.

A B2B contract is a legal agreement between two businesses. It protect business interests, establish clear boundaries and expectations, and create a foundation of trust with clients and partners.

A contract order in OMS is a structured agreement that is part of a B2B contract. It is not for deliveries alone. This construct is planned to enhance with B2B contract specific features.

Essentially it is an agreement, and its start date signifies the official beginning of obligations, liability and commitments. Allowing order creation prior to this date undermines contract validity. A contract's effective date is the "go-live" for enforcement. Creating actionable orders beforehand ties, the obligations and liabilities to a period when the contract is not legally active.

Contract terms dictate parameters like price offered for a committed quantity during the tenure of the contract. Processing orders outside this window complicates the framework as it is trying to apply contract terms to a pre-contract action. The current restriction avoids ambiguity in enterprise systems, where the "Order Date" has a larger meaning and it also represents the commitment and allocation of products.

The seller's desire to "create orders early" stems from an operational need like lead time management and may be for creating orders in convenience. I understand sellers often require lead time to allocate inventory, purchase materials, or schedule production so goods can actually deliver on or after the start date.

I would like to reiterate again my point that - the stocking need above is not a ONE-TIME requirement. Seller needs to stock inventory before the order comes. Once the contract officially begins, they can always create orders with requested delivery that is sufficiently far apart. The contract order is OMS allows that.

If the seller needs to queue up work before the contract order officially begins, and if the early order creation is a business need, both parties should formally amend the contract to establish an earlier effective date, shifting the price, legal and financial obligations backward. In fact, if this needed for EVERY NEWLY added contract order then they should create contract orders accordingly at first place.

A contract order reaching in a confirmed state and arriving the start date, are the prerequisite for creating orders from contract. This behaviour cannot be changed.

Therefore, you cannot create sales orders before the contract order start date, manually also. The contract order processing has no intention to check the validity of requested delivery date entered by user on creating order either.

Secondly, what if, user changes the requested delivery date after the order was created. OMS allows to change requested delivery date on an order to any date on or after the order date.

This restriction is only before contract order reaching its start date. Once this date has arrived, users can plan and create orders for future requested delivery dates, in bulk as per their wish, anytime during the life cycle of contract order.

Basically, this requirement 'plan and create orders ahead' is not limited to the short period of any day before contract start date to the contract start date. It is not a one-time requirement. Such requirements can arrive anytime later for any future span of days, and users can create orders in the same bulk pattern without any issues.