Approving a Hold Activation Request

You can view the number of hold requests for which activation is pending for approval from the Hold Request screen. 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 in it.

Note: The system will not allow you to approve, reject, or request to resubmit a hold activation request submitted by you.

To approve a hold activation request, you should have:

  • Activation approval To Do role assigned in the system

Procedure

To approve a hold activation request:

  1. Do either of the following:
    If you want to...Then...
    Review a hold activation request through the Hold Request screen

    1. Search for the hold request with the Activation Approval In Progress status in the Hold Request screen.

      A list of hold requests with the respective status appears in the search results.

    2. In the Search Results section, click the link in the Hold Request Information column corresponding to the hold request which you want to review.
    Review a hold activation request through the To Do List screen

    1. Click the Menu link in the Application toolbar.

      A list appears.

    2. From the Main menu, select To Do and then click To Do List.

      The To Do List screen appears.

    3. Click the Search (The Search Icon) icon corresponding to the To Do Type field.

      The To Do Type for User Search window appears.

    4. Enter C1-HLDAP in the To Do Type field.

    5. Click the Search button corresponding to the To Do Type field.

      The To Do List screen appears.

    6. Select the Open option from the Filter by list to view all unassigned To Dos.

    7. Click the link in the Message column corresponding to the To Do of the hold request that you want to review.
    The Hold Request screen appears.
  2. Review the details in the Hold Request screen.
  3. If the information in the hold request is accurate, click the Approve button in the Hold Request zone.

    The system behaves in the following manner:

    If... Then...
    The number of entities added (either manually or via filter criteria) in the hold request exceeds the defer processing count (defined in the respective hold request type) The status of the hold request is changed to Deferred Processing.
    Note:

    You need to execute the Hold Request Periodic Monitor (C1-HLDRQ) batch. It considers the hold requests which are in the Deferred Processing status and then changes its status to Active.

    Once the hold request is activated, you need to execute the following batches:

    • C1-DELBI - If the bill generation process is kept on hold for an account or person through a hold request, you need to execute the C1-DELBI batch which will delete the pending bills of the respective entities along with their bill segments. For more information about the batch, see Oracle Revenue Management and Billing Batch Guide.

    • C1-HLMON - On executing the C1-HLMON batch, the system will set the bill after date, postpone credit review until date, defer auto pay date, and hold refund until date, if required, for the respective entity.
    The number of entities added (either manually or via filter criteria) in the hold request does not exceed the defer processing count (defined in the respective hold request type) The status of the hold request is changed to Active. In addition, the system does the following (in the online mode):

    • If the start date of the hold request, hold entity, or hold process is earlier than the system date, it sets the respective start date to the system date.

    • If an active overdue process (if any) exists for the account which is kept on hold, it cancels the respective overdue process of the account. The status of the overdue process is changed to Inactive.

    • An alert is created in the dashboard whenever an account is kept on hold through a hold request. Note that the start and end dates of the alert is set to the hold request start and end dates, respectively. The alert appears until the hold request for the account is released.

    Note:

    A warning message appears while activating the hold request if the start date of hold request, hold process, or hold entity is earlier than the system date.

    The system does not allow you to activate a hold request when the hold request end date is earlier than the system date.

    If the bill generation process is kept on hold for an account or person through a hold request, you need to execute the C1-DELBI batch which will delete the pending bills of the respective entities along with their bill segments. For more information about the batch, see Oracle Revenue Management and Billing Batch Guide.
    Note:

    If the Delinquency process is added in the hold request, this algorithm derives the entity level of the hold request. If the entity level is set to Account, it checks whether any individual or group membership is billed to the account. If an individual membership is billed to the account, it determines whether the number of entities in the hold request exceeds the defer processing count and accordingly changes the status of the hold request to either Deferred Processing or Active. However, if a group membership is billed to the account, this algorithm does not use the defer processing count. It directly changes the status of the hold request to Deferred Processing. Similarly, if the entity level is set to Person, it does not use the defer processing count. It directly changes the status of the hold request to Deferred Processing.

    The Approve button appears when the hold request is in the Activation Approval In Progress status and when a user with the activation approval To Do role is reviewing the hold request.

    On approving a hold activation request, the system does the following in the online or deferred (i.e., when the C1-HLMON batch is executed) mode depending on the defer processing count:

    If… Then...
    The hold request is created for an account, the bill generation process is on hold, and the entity start date in the hold request is earlier than or equal to the batch business date The entity end date or process end date whichever is earlier is set as the bill after date for the respective account. In addition, the system creates an entry for the hold request in the CI_​BILL_​DEL_​REQUEST table.
    Note: The bill after date then appears corresponding to the account in the Hold Entities zone of the Hold Request screen. In addition, it appears in 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 start date in the hold request is earlier than or equal to the batch business date The entity end date or process end date whichever is earlier is set as the postpone credit review until 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 start date in the hold request is earlier than or equal to the batch business date The entity end date or process end date whichever is earlier is set as the postpone credit review until 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 auto pay process is on hold, and the entity start date in the hold request is earlier than or equal to the batch business date The entity end date or process end date whichever is earlier is set as the defer auto pay date for the respective account.
    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 refund process is on hold, and the entity start date in the hold request is earlier than or equal to the batch business date The entity end date or process end date whichever is earlier is set as the hold refund until date for the respective account. In addition, the status of the non-final refund request (if any) for the respective account is set to Hold.
    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 an account, the auto pay process is on hold, and the entity end date in the hold request is earlier than the batch business date The automatic payment details of the debit bills (if any) for the respective account are updated in the CI_​BILL_​ACH table.
    The hold request is created for a person, the bill generation process is on hold, and the entity start date in the hold request is earlier than or equal to the batch business date The entity end date or process end date whichever is earlier is set as the bill after date 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. In addition, the system creates an entry for the hold request in the CI_​BILL_​DEL_​REQUEST table.
    Note:

    In this scenario, the bill after date is always set in the deferred mode when the C1-HLMON batch is executed.

    The bill after date then appears in 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 start date in the hold request is earlier than or equal to the batch business date The entity end date or process end date whichever is earlier is set as the postpone credit review until 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:

    If the hold entity end date is not specified, the system will consider the respective process end date while deriving the above dates. If both the hold entity end date and respective process end date are not specified, the system will consider the hold request end date while deriving the above dates.

    The system does not change the start date of the hold request, hold entity, or hold process when it is a future date.

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