Mass Adjustment Creation

Oracle Revenue Management and Billing provides the ability to create multiple adjustments at once through the Upload Request feature. The system allows you to create an adjustment for each adjustment data record through an adjustment upload request. The C1-ADJUPLD business object enables you to create an upload request for mass adjustment creation.

Note: At present, you can only create new adjustments and not update existing adjustments through the Upload Request feature.

You need to create an adjustment upload request type using the C1-AdjRequestType business object where the upload request business object is set to C1-ADJUPLD. You can then upload a mass adjustment creation file in the CSV format using the respective adjustment upload request type. The mass adjustment creation file should contain records with the following information – account details, match type, match value, adjustment type, adjustment amount, adjustment currency, comments, bill ID, arrears date, and characteristics. For more information, see Mass Adjustment Creation CSV Format.

Note: You can specify maximum 5 characteristics in the adjustment data record.

On uploading a mass adjustment creation file, the system validates each adjustment data record in the CSV file. 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.

  • The match type, match value, adjustment type, adjustment amount, and currency are specified in the record.

  • The account ID given in the record is valid.

  • An account with the given account identifier type and account identifier combination exists in the system.

  • The adjustment type, currency code, and match type given in the record are valid.

  • The characteristic type given in the record is valid and its characteristic entity is set to Adjustment and is associated with the adjustment type.

  • The adhoc characteristic values are validated as per the validations defined in the respective algorithm.

  • The predefined characteristic value is already defined for the characteristic type.

  • The foreign key reference characteristic value is valid.

  • The bill ID given in the record is valid.

  • The contract type or contract ID given in the record is valid.

  • The contract is not in the Canceled status.

  • An active contract of the specified contract type exists for the account.

  • The amount matches the decimal positions of the respective currency.

  • The adjustment type is included in the adjustment type profile which is associated with the contract type.

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 or if any of the above validations fail, the system does not allow you to create an adjustment upload request.

Note: The system does not allow you to upload a file which exceeds the maximum file size limit (in kilobytes) specified in the respective adjustment upload request type. Therefore, you must ensure that the file size is within the maximum limit.

If all the adjustment data records are successfully validated, the system creates an adjustment upload request in the Pending status. You have an option to cancel an adjustment upload request if incorrect data is uploaded through the adjustment data file. If the approval process is not configured for the respective adjustment upload request type, you can click the Create Adjustment button to create the adjustments. The status of the adjustment upload request is then changed to Creating Adjustment.

However, if the approval process is configured for the respective adjustment upload request type, you can click the Submit for Approval button to submit the adjustment upload request for approval. The approver can either approve or reject the adjustment upload request based on the observations. On approving an adjustment upload request, the status of the adjustment upload request is changed to Approved. However, on rejecting an adjustment upload request, the status of the adjustment upload request is changed to Rejected.

Once the status of the adjustment upload request is changed to Creating Adjustment or Approved, the system checks whether the adjustment 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 records in the adjustment data file does not exceed the online record process limit specified in the C1-UPLDEFEVL algorithm (attached to the Defer Algorithm field in the respective adjustment upload request type), the system creates adjustments in the real time (i.e., immediately) and changes the status of the adjustment upload request to Completed. However, if the number of records in the adjustment data file exceeds the online record process limit, the status of the adjustment upload request is changed to Deferred. The system then changes the status of the adjustment upload request from Deferred to Creating Adjustment when the C1-UPLRQ batch is executed.

Once the adjustments are successfully created for an adjustment upload request, the adjustment information string appears corresponding to each adjustment data record in the Adjustment Data Records zone.

Note: This feature is tested and certified for both the financial services and health insurance domains.