Hold Request Lifecycle

While creating a hold request, you need to specify the hold request type using which you want to create the hold request. It is the hold request type which helps the system to determine the following:

• The hold request business object using which a hold request should be created through the hold request type.

• The processes which can be kept on hold for different entities through the respective hold requests.

• Whether approval process is required while activating and/or releasing the respective hold requests.

• Whether partial hold is allowed when a bill is kept on hold through the respective hold requests.

Once a hold request is created, you can add more processes and entities before activating the hold request. You can then click the Submit button to activate the hold request. On activating a hold request, the system checks whether the number of entities added in the hold request exceeds the defer processing count. If the number of entities added in the hold request does not exceed the defer processing count, the status of the hold request is changed to Active and the respective processes are kept on hold for the selected entities. However, if the number of entities added in the hold request exceeds the defer processing count, the system changes the status of the hold request to Deferred Processing. On executing the C1-HLDRQ batch, the status of the hold request is changed to Active.

You can optionally configure the approval process, if required, while activating the hold request. If the activation approval process is configured in the respective hold request type, the status of the hold request is changed to Activation Approval In Progress. The approver can review, and accordingly approve or reject the hold activation request based on the observations. In addition, the approver can request the submitter to resubmit the hold activation request for approval after making the necessary changes to it. On approving the hold activation request, the status of the hold request is changed to Active and the respective processes are kept on hold for the selected entities.

Note that all the selected processes of the entities may not be kept on hold on activating a hold request. Only when the entity date falls within the process date range and the process start date is earlier than the system date or batch business date, the system keeps the process of the respective entity on hold. You need to then execute the C1-HLMON batch at regular intervals. It will hold a process of an entity when the following conditions are met:

• Entity date falls within the process date range

• Process start date is earlier than the batch business date

The system enables you to manually release a hold request from the user interface. On manually releasing a hold request from the user interface, the system sets the hold request, hold entities, and hold processes end dates to the system date. In addition, the status of the hold request is changed to Released and the respective processes kept on hold are released for the selected entities. You can optionally configure the approval process, if required, while releasing the hold request. If the release approval process is configured in the respective hold request type, the status of the hold request is changed to Release Approval in Progress. The approver can review, and accordingly approve the hold release request based on the observations. In addition, the approver can request the submitter to resubmit the hold release request for approval after making the necessary changes to it. On approving the hold release request, the status of the hold request is changed to Released and the respective processes kept on hold are released for the selected entities.

The system also automatically releases a hold request. On executing the C1-HLMON batch, it checks whether any active hold request’s end date is earlier than the batch business date. If so, the status of the hold request is changed to Released and the respective processes kept on hold are released for the selected entities. In addition, the release status reason is stamped corresponding to the hold request. The hold request, hold entity, and the hold process end dates are updated to the batch business date. Note that the entity and process end dates are updated only when their start date is not a future date.

A hold request goes through various statuses in its lifecycle. Note that lifecycle of a hold request is driven by the business object using which the hold request is created. A hold request business object named C1-HoldRequest is shipped with the product. The hold request feature explained in this document is articulated based on the lifecycle and logic defined in the C1-HoldRequest business object.

For more information on how to setup the hold request feature, see Prerequisites.

Related Topics