Upload Request

Oracle Revenue Management and Billing provides a generic upload feature that allows you to upload data to create or update multiple entities through an upload request. At present, the system supports only Comma-Separated Values (CSV) format and therefore you can upload the data only using the CSV file. Note that, at a time, a CSV file can have data to create or update a particular type of entities in the system. In other words, you cannot upload data for multiple types of entities (such as, hold request and billable charge) through a single CSV file.

Through an upload request, you can not only create or update the business object based entities but can also create or update the service-driven entities. If the lifecycle is defined for the entity business object, the status of entity is updated accordingly when the upload request is processed. If the approval process is configured for the upload request business object, the system will submit the upload request for approval before creating or updating the entities in the system. Similarly, if the approval process is configured for the entity business object, the system will submit the entity for approval once it is created using the uploaded data.

At present, the system allows you to upload data for creating the following entities - Billable Charges (for both the financial services and health insurance domains), Hold Requests, Refund Requests, Write Off Requests, Bill Group Sort Records, and Bill Group Derivation and Pricing Parameters Records. It also allows you to upload data for updating the following entities:

• Contract rider details of a contract

• Bill cycle of an account

In addition, you can reinstate multiple fully insured group policies and cancel payment tenders through the Upload Request feature.

While uploading a CSV file, you need to specify distinct upload request type using which you want to create the upload request. For more information, see Upload Request Type. An upload request goes through various statuses in its lifecycle. Note that lifecycle of an upload request is driven by the business object using which the upload request is created. We have shipped the following upload request business objects:

• Bill Cycle Update Upload (i.e., C1-BillCycleUpdateUplReq)

• Bill Group Derivation & Pricing Parameter (i.e., C1-BillLevelUploadRequest)

• Bill Group Sorting Upload Request (i.e., C1-BillGrpSortUploadRequest)

• Billable Charge Upload (i.e., C1-BillableChargeUploadRequest)

• Billable Charge Upload for Fully Insured (i.e., C1-BillableChargeUploadFI)

• Contract Rider Upload (i.e., C1-ContractRiderUpdateUplReq)

• Hold Request Upload (i.e., C1-HoldUploadRequest)

• Refund Request Upload (i.e., C1-RefundUploadRequest)

• Reinstatement Upload Request (i.e., C1-ReinstatementUploadRequest)

• Tender Cancelation Upload Request (i.e., C1-TndrCnclUploadRequest)

• Write Off Request Upload (i.e., C1-WriteOffUploadRequest)

Each upload request feature explained in this document is articulated based on the lifecycle and logic defined in the respective business object.

Related Topics

Parent Topic: Oracle Revenue Management and Billing Generic Business Processes