Mass Bill Cycle Rule Characteristic Creation or Modification
Oracle Revenue Management and Billing enables you to create or update bill cycle rule characteristic of multiple accounts at once through the Upload Request feature. The C1-BillCycleRuleCharUpdUplReq business object enables you to create an upload request for mass bill cycle rule characteristic creation or modification.
You need to create an upload request type for the C1-BillCycleRuleCharUpdUplReq business object. You can then upload a mass bill cycle rule characteristic creation or modification file in the CSV format using the respective upload request type. The mass bill cycle rule characteristic creation or modification file should contain records with the following information – account identifier details or account ID and characteristic value with its effective date. For more information, see Mass Bill Cycle Rule Characteristic Creation or Modification CSV Format.
On uploading a mass bill cycle rule characteristic creation or modification 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.
-
Effective date and bill cycle rule code 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.
On clicking the Validate button, the system validates the following:
-
Whether the account ID given in the record is valid.
-
Whether the bill cycle rule code is a valid billing preference.
-
Whether the two or more records with the same account ID and effective date combination does 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 derives the characteristic type specified in the Bill Cycle Rule Code option type of the C1-ASOBLLNG feature configuration. For each valid record, the system checks whether a billing preference characteristic with the derived characteristic type and effective date combination is already defined for the account. If so, the system updates the existing billing preference characteristic value of the account. However, if a billing preference characteristic with the derived characteristic type and effective date combination does not exist for the account, the system creates the billing preference characteristic for the account.
The system creates or updates the billing preference characteristic of the account using the entity business object specified in the respective upload request type.
The system derives the bill cycle from the Bill Cycle attribute of the billing preference when the respective characteristic is effective for the account. The derived bill cycle is then stamped against the account.
Once the billing preference characteristic is successfully created or updated for the account, the status of the data record is changed to Processed. However, if any error occurs while creating or updating the billing preference characteristic for the account, the status of the data record is changed to Error. Finally, the status of the upload request is changed to Processed.