Mass Policy Reinstatement

Oracle Revenue Management and Billing provides the ability to reinstate multiple fully insured group policies at once through the Upload Request feature. The C1-ReinstatementUploadRequest business object enables you to create an upload request for mass policy reinstatement.

You need to create an upload request type for the C1-ReinstatementUploadRequest business object. You can then upload a mass policy reinstatement file in the CSV format using the respective upload request type. The mass policy reinstatement file should contain records with the following information – policy ID or source system and policy number, and reinstatement reason. For more information, see Mass Policy Reinstatement CSV Format.

On uploading a mass policy reinstatement file, the system creates an upload request in the Draft status. The data records are created in the Pending status. The system validates the following for each record:

• Either the policy ID or source system and policy number is specified in the record.

• Reinstatement reason is specified in the record.

If the policy ID is not specified in the record, the system derives the policy ID using the respective source system and policy number combination. If the system could not derive the policy ID using the source system and policy number combination, the status of the record is changed to Invalid. In addition, if any of the above validations fail, the status of the record is changed to Invalid.

On clicking the Validate button, the system validates the following:

• The policy ID given in the record is valid.

• The reinstatement reason is valid for the status specified in the Policy Reinstatement Status for Reason Verification parameter of the C1-REN-VALID algorithm.

• The two or more records with the same policy ID do not exist in the upload request.

If any of above validations fail, the status of the record is changed to Invalid. However, if all the above validations are successful, the status of the record is changed to Valid. Once all the pending records in the upload request are validated, the status of the upload request is changed to Validated.

On clicking the Submit button, the system checks whether the approval is required for the upload request. If the approval is required for the upload request, the status of the upload request is changed to Approval In Progress. However, if the approval is not required for the upload request, the status of the upload request is changed to Submitted.

The approver can either approve or reject the upload request based on the observations. On approving an upload request, the status of the upload request is changed to Approved. However, on rejecting an upload request, the status of the upload request is changed to Rejected.

Once the status of the upload request is changed to Submitted or Approved, the system checks whether the upload request must be processed in the real time (i.e., immediately) or in the deferred mode (i.e., in the background). If the number of valid records in the upload request does not exceed the online record process limit, the system changes the status of the upload request to Processing. However, if the number of valid records in the upload request exceeds the online record process limit, the system changes the status of the upload request to Deferred Processing. The system then changes the status of the upload request from Deferred Processing to Processing when the C1-UPLRQ batch is executed.

Once the status of the upload request is changed to Processing, the system fetches a list of records which are in the Valid status. For each valid record, the system reinstates the respective fully insured group policy and changes its status to Pending Reinstatement.

Once the policy status is successfully updated, the status of the record is changed to Processed. However, if any error occurs while updating the policy status, the status of the record is changed to Error. Finally, the status of the upload request is changed to Processed.