Releasing a Hold Request
Prerequisites
To release a hold request, you should have:
-
Reasons defined for the Released status of the C1-HoldRequest business object in the Status Reason screen
Procedure
To release a hold request:
- Search for the hold request in the Hold Request screen.
-
In the Search Results section, click
the link in the Hold Request Information column
corresponding to the hold request that you want to release.
The Hold Request screen appears.
- Ensure that the Main tab is selected.
-
Click the Release button in the Hold Request zone.
The Release Reason window appears. It contains the following fields:
Field Name Field Description Mandatory (Yes or No) Release Reason Used to indicate the reason why you want to release the hold request. Note: The list includes only those reasons which are defined for the Released status of the C1-HoldRequest business object through the Status Reason screen.Yes Comments Used to specify additional information while releasing the hold request. Note: You can resize the text box depending on your requirement by clicking the Resize Handle () icon at the bottom right corner of the text box.
No Note: The Release button appears when the hold request is in the Active status. - Select the reason for releasing the hold request from the Release Reason list.
- Enter the comments (if any) while releasing the hold request in the respective field.
-
Click Save.
The system behaves in the following manner:
If... Then... The Release Approval option is selected in the respective hold request type The status of the hold request is changed to Release Approval in Progress. A To Do is created using the To Do type (i.e., C1-HLDAP) specified in the Release Approval To Do Type field of the respective hold request type and then assigned to the users with the role specified in the Release Approval To Do Role field of the respective hold request type. In addition, a log entry is created for the hold request when the To Do is created for the approver. The Release Approval option is not selected in the respective hold request type The status of the hold request is changed to Released. If the hold entity end date and hold process end date is earlier than the system date, the system sets the hold entity end date and hold process end date to the system date. It also sets the hold request end date to the system date. In addition, the alert end date on the respective account is set to the system date. On releasing a hold request, the system checks whether the number of entities added (either manually or via filter criteria) 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 system does the following (in the online mode):
If… Then… The hold request is created for an account, the auto pay process is on hold, and the entity end date in the hold request is earlier than or equal to the system date The defer auto pay until date is set to the system date for the respective account. In addition, the automatic payment details of the debit bills (if any) for the respective account are updated in the CI_BILL_ACH table. Note: The defer auto pay date then appears corresponding to the account in the Hold Entities zone of the Hold Request screen. In addition, it appears in the Defer Auto Pay Date field on the Auto Pay tab of the Account screen.The hold request is created for an account, the bill generation process is on hold, and the entity end date in the hold request is earlier than or equal to the system date The bill after date is cleared for the respective account. This will enable the business to bill the account immediately on the same day when the hold is released. Note: The bill after date is cleared corresponding to the account in the Hold Entities zone of the Hold Request screen. In addition, it is cleared from the Bill On or After Date field on the Main tab of the Account screen.The hold request is created for an account, the overdue process is on hold, and the entity end date in the hold request is earlier than or equal to the system date The postpone credit review until date is set to the system date for the respective account. Note: The postpone credit review until date then appears corresponding to the account in the Hold Entities zone of the Hold Request screen. In addition, it appears in the Postpone Credit Review Until field on the C & C tab of the Account screen.The hold request is created for an account, the delinquency process is on hold, and the entity end date in the hold request is earlier than or equal to the system date The postpone credit review until date is set to the system date for the respective account. Note: The postpone credit review until date then appears corresponding to the account in the Hold Entities zone of the Hold Request screen. In addition, it appears in the Postpone Credit Review Until field on the C & C tab of the Account screen.The hold request is created for an account, the refund process is on hold, and the entity end date in the hold request is earlier than or equal to the system date The hold refund until date is set to the system date for the respective account. In addition, the status of the refund request (if any) for the respective accounts is changed from Hold to its previous status. Note: The hold refund until date then appears corresponding to the account in the Hold Entities zone of the Hold Request screen.The hold request is created for a person, the bill generation process is on hold, and the entity end date in the hold request is earlier than or equal to the batch business date The bill after date is cleared either for all the accounts in the person’s hierarchy or only for the persons’ immediate accounts depending on whether the Hierarchy option is selected or not. Note that the system considers only the child persons and not the grandchild persons from the person’s hierarchy and then derives the accounts where the child person is the main customer. Note:In this scenario, the bill after date is always cleared in the deferred mode when the C1-HLMON batch is executed.
The bill after date is cleared from the Bill On or After Date field on the Main tab of the Account screen.
The hold request is created for a person, the delinquency process is on hold, and the entity end date in the hold request is earlier than or equal to the batch business date The postpone credit review until date is set to the system date for the respective person and its immediate accounts (where the person is the main customer). If the Hierarchy option is selected for the person, the system sets the postpone credit review until date for the person, its immediate accounts, its child persons, and for the child persons’ accounts. Note that the system considers only the child persons and not the grandchild persons from the person’s hierarchy and then derives the accounts where the child person is the main customer. Note:In this scenario, the postpone credit review until date is always set in the deferred mode when the C1-HLMON batch is executed.
The postpone credit review until date then appears corresponding to the person in the Hold Entities zone of the Hold Request screen. In addition, the postpone credit review until date of the account appears in the Postpone Credit Review Until field on the C & C tab of the Account screen.
Note: The above dates are updated to the system date only when the entity end date or respective process end date is not earlier than the system date.However, if the number of entities added in the hold request exceeds the defer processing count, a log entry is created indicating that the hold request is manually released but the release process (i.e. system behavior mentioned in the above table) would be completed when the C1-HLMON batch is executed.
Related Topics
For more information on... | See... |
---|---|
How to search for a hold request | Searching for a Hold Request |
Hold Request screen | Hold Request (Used for Viewing) |
Hold Request zone | Hold Request |