Mass Contract Rider Update

Oracle Revenue Management and Billing provides the ability to update the contract rider information of multiple contracts at once through the Upload Request feature. The C1-ContractRiderUpdateUplReq business object enables you to create an upload request for mass contract rider update.

You need to create an upload request type for the C1-ContractRiderUpdateUplReq business object. You can then upload a mass contract rider update file in the CSV format using the respective upload request type. The mass contract rider update file should contain records with the following information – Contract ID or account details and contract type, start end, end date, and bill factor. Note that you can only specify a bill factor where the Contract Rider Applicability option is selected. For more information, see Mass Contract Rider Update CSV Format.

On uploading a mass contract rider 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 contract ID or account details and contract type are specified in the record.

• Either the account ID or account identifier type and account identifier is specified in the record.

• Start date and bill factor are 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:

• The account ID given in the record is valid.

• The contract ID given in the record is valid.

• The contract type given in the record is valid.

• The bill factor given in the record is valid.

• If both the account ID and contract ID are given in the record, the contract belongs to the account.

• The contract type is defined for the division to which the account belongs.

• The Contract Rider Applicability flag of the bill factor is set to Y.

• The two or more records with the same contract ID or account ID and contract type combination 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 checks whether the contract ID is specified in the record. If so, it updates the contract rider information of the respective contract. However, if the contract ID is not specified in the record, the system derives the active contracts of the account which are created using the given contract type. For each such derived contract, the system updates the contract rider information. However, if there are no active contracts of the respective contract type for the account, the status of the record is changed to Error.

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