Order Amendment

Order Amendment allows the order, that is currently being fulfilled, to be modified for different parameters such as action, requiredByDate, and UDFs in the existing order lines. It also allows adding a new order line in the request. The parameters and their reason for change are mentioned as follows:

  • The parameter values passed in the original request was incorrect. The corrected values can be passed by sending an amendment request.
  • The parameter values require a modification as per the change request from the end user. For example, the bandwidth of a product named Internet Bundle is passed as a UDF named Bandwidth in the order line. The bandwidth in the original order was 1 Mbps. When the order was being fulfilled, the customer requested the bandwidth to be updated to 2 Mbps. This is done by sending an amendment request by changing the value of the UDF named Bandwidth to 2 Mbps.
  • An additional product required fulfillment while the current one is being fulfilled.

An order can be amended when it is in one of the following states:

START If the order is amended in these states then it is called a pre-plan development amendment, because the execution plan has not yet been created. In this scenario, the execution plan generated for the amendment request will be considered and executed.
SUBMITTED
FEASIBILITY
OPD
PREQUALIFICATIONFAILED
EXECUTION If the order is amended in these states it is post-plan development amendment, because the execution plan was already created and had begun execution. In this scenario, the existing plan requires modification and merging with the plan that has been generated as per the amendment request. Post-plan development amendment is the most frequently used amendment.
SUSPENDED
ERROR_HANDLER

An order cannot be amended when it is in either of the FINAL states:

  • COMPLETE
  • CANCELLED
  • WITHDRAWN