Upload Request

Oracle Revenue Management and Billing provides a generic upload feature which enables you to upload various types of data. The system enables you to upload data for the following using the Upload Request feature:

• Billable Charge (Adhoc and Regular)

• Hold Request

• Refund Request

• Write Off Request

• Policy Reinstatement

• Bill Group Sort ID

• Derivation and Pricing Parameters for a Bill Group and Sort ID Combination

It also enables you to update the following information:

• Contract rider of a contract

• Bill cycle of an account

While uploading data for the above supported entities, you need to specify the upload request type using which you want to upload the file. It is the upload request type which helps the system to determine:

• Whether the file must be approved by the approver before creating or updating the entities

• Which business object must be used for creating the upload request

• Which business object must be used for creating or updating entities through an upload request

• Which foreign key reference must be used for generating information string for the entity

• A set of fields using which you can search records uploaded through an upload request

You can upload a data file in the CSV format. You cannot upload data for more than one entity type through the same CSV file. For example, you cannot upload data for billable charges and hold requests using a single CSV file. An upload request of the specified upload request type is created when the file is successfully uploaded in the system. You can track a file through an upload request.

Once an upload request is created, the status of the upload request is set to Draft. The status of each record uploaded through an upload request is set to Pending. However, if the mandatory data is not available or data required for deriving mandatory data is incorrect in the record, the status of record is set to Invalid. You can then edit, delete, or validate the upload request. During the validation process, the system and custom validations (if any) are executed. The status of each record is changed to Valid or Invalid depending on whether the record was validated successfully or not.

Once the upload request is validated, you can either cancel or submit the upload request for further processing. On submitting an upload request, the system checks whether the number of valid records in the uploaded file exceed the online record process limit defined in the Defer Upload Request algorithm. If the number of valid records in the uploaded file does not exceed the online record process limit, the system creates or updates the entities in the real time (i.e. immediately). However, if the number of valid records in the uploaded file exceeds the online record process limit, the system creates or updates the entities in the deferred mode (i.e. when the Upload Request Periodic Monitor (C1-UPLRQ) batch is invoked).

You can optionally configure the system to use the approval workflow process for an upload request. If the Approval Required flag is set to Yes in an upload request type, then on submitting the respective upload request, the approval workflow process creates a To Do for the approver to review the upload request. Once the approver approves the upload request, the system checks whether the number of valid records in the uploaded file exceed the online record process limit defined in the Defer Upload Request algorithm. If the number of valid records in the uploaded file does not exceed the online record process limit, the system creates or updates the entities in the real time (i.e. immediately). However, if the number of valid records in the uploaded file exceeds the online record process limit, the system creates or updates the entities in the deferred mode (i.e. when the Upload Request Periodic Monitor (C1-UPLRQ) batch is invoked. However, if the approver rejects the upload request, the status of the upload request is set to Rejected.

During the upload process, an upload request goes through various statuses in its lifecycle. Note that the lifecycle of an upload request is driven by the business object using which the upload request is created. In this release, we have shipped the following upload request business objects:

• Update Bill Cycle Upload Request (C1-BillCycleUpdateUplReq)

• Billable Charge Upload Request (C1-BillableChargeUploadRequest)

• Update Contract Rider Upload Request (C1-ContractRiderUpdateUplReq)

• Hold Request Upload Request (C1-HoldUploadRequest)

• Refund Request Upload Request (C1-RefundUploadRequest)

• Write Off Request Upload Request (C1-WriteOffUploadRequest)

• Reinstatement Upload Request (C1-ReinstatementUploadRequest)

• Bill Group Sorting Upload Request (C1-BillGrpSortUploadRequest)

• Bill Group Derivation and Pricing Parameters Upload Request(C1-BillLevelUploadRequest)

During the upload request process, an upload request creation goes through various statuses in its lifecycle. For more information about the upload request statuses, see Upload Request (Without Approval) Status Transition and Upload Request (With Approval) Status Transition.

For more information on how to setup the upload request process, see Prerequisites.

Related Topics

Parent Topic: Oracle Revenue Management and Billing Generic Business Processes