OrderLine Addition

In this amendment type, one or more new order lines can be added as part of the amendment request to fulfil the additional products. The plan items corresponding to the newly added order lines are added into the execution plan and the dependencies are updated accordingly. At a high level, there are two main cases.

  1. If an optional child product from a ProductComprisedOf relationship was ordered in the original request and the parent product is then ordered in a new order line in the amendment request, the newly created plan item for parent product will have a dependency on the existing plan item of the child product.

    For example, if B is an optional child product of A, in case of the above mentioned scenario; the newly added plan item for A will have a dependency on the plan item of B which was there in the original plan. This is done regardless of the status of the plan item for child product B.

    This is logical and would have been the case even when both products were ordered in the original request itself. Once the amendment plan is activated, the plan item for the parent product goes into EXECUTION after the plan item for child product is successfully completed. If the plan item for child product was already COMPLETE, the plan item for parent product will go into EXECUTION immediately.

  2. On the other hand, if a parent product from a ProductComprisedOf relationship was ordered in the original request and the child product is then ordered in a new order line in the amendment request, the dependency of the child plan item is added based on the status of the parent plan item, as explained in the following points:
    1. If the parent plan item was PENDING before the amendment, the dependency will be added into the existing parent plan item.
    2. If the parent plan item was SUSPENDED or COMPLETE before the amendment, a REDO plan item will be generated against it. The original parent plan item will be cancelled if it was SUSPENDED. A REDO plan item will be generated based on the EPMR action configurations as mentioned in the following points:
      1. If the value configured in the EPMR characteristic for the corresponding order line action is either RESTART or COMPENSATE_RESTART. E.g. In case of PROVIDE action, the value of EPMR_ACTION_PROVIDE characteristic is referred.
      2. Or the required EPMR characteristic is missing in the product model and the CompensateRestartForNoEPMRChar flag is enabled in AOPD configurations.

      See Execution Plan Modification Rules (EPMR) for details about EPMR actions. The dependency of the child plan item will be added into the newly created REDO plan item for the parent product. Once the amendment plan is activated, the newly added plan item for the child product goes into EXECUTION. After it is successfully completed, the REDO plan item for parent will go into EXECUTION.

Preconditions for OrderLine Addition

Following is the only precondition for the order line addition amendment type.

The lineID, productID, requiredByDate, and UDFs in all the order lines in the amendment request must match with those in the original order request.

Note: Unlike addition, the deletion or removal of an existing order line is not allowed and supported in an amendment request. For cancelling the fulfillment of the product in an order line, the order line action should be changed to CANCEL instead.