Mass Accounts’ Bill Cycle Update
Oracle Revenue Management and Billing provides the ability to update the bill cycle of multiple accounts at once through the Upload Request feature. The C1-BillCycleUpdateUplReq business object enables you to create an upload request for mass accounts’ bill cycle update.
You need to create an upload request type for the C1-BillCycleUpdateUplReq business object. You can then upload a mass accounts’ bill cycle update file in the CSV format using the respective upload request type. The mass accounts’ bill cycle update file should contain records with the following information – account identifier details or account ID and bill cycle. For more information, see Mass Accounts’ Bill Cycle Update CSV Format.
On uploading a mass accounts’ bill cycle update 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 account ID or account identifier type and account identifier is specified in the record.
-
Bill cycle is specified in the record.
If the account ID is not specified in the record, the system derives the account ID using the respective account identifier type and account identifier combination. If the system could not derive the account ID using the account identifier type and account identifier 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.
If the bill cycle is missing in any record of the file, the system will not allow you to create an upload request.
The system does not allow you to upload a file which exceeds 700 KB. Therefore, you must ensure that the file size is within the maximum limit.
On clicking the Validate button, the system validates the following:
-
The account ID given in the record is valid.
-
The bill cycle given in the record is valid.
-
The given bill cycle is associated to the division of the account.
-
The two or more records with the same account ID do not exist in the upload request.
If the account ID is invalid, the system derives the account ID using the respective account identifier type and account identifier combination. If the system could not derive the account ID using the account identifier type and account identifier combination, the status of the record is changed to Invalid.
If duplicate records exist in the upload request, the system validates and changes the status of one record to Valid and the status of the remaining records to Invalid.
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 updates the bill cycle of the respective account.
Once the account is successfully updated, the status of the record is changed to Processed. However, if any error occurs while updating the account, the status of the record is changed to Error. Finally, the status of the upload request is changed to Processed.
The system updates the account using the entity business object specified in the respective upload request type.
This feature is tested and certified for both the financial services and health insurance domains.
