Mass Bill Group Derivation and Pricing Parameters Record Creation

Oracle Revenue Management and Billing provides the ability to add bill group derivation and pricing parameters records for multiple bill groups at once through the Upload Request feature. The system allows you to create bill group derivation and pricing parameters records for multiple bill groups of a single parent customer at a time through an upload request. The specified bill groups (i.e., child persons whose person type is set to Bill Group) should be related to the parent customer using the relationship type that is specified in the Person Relationship Type option type of the C1-ASOBLLNG feature configuration. The C1-BillLevelUploadRequest business object enables you to create an upload request for mass bill group derivation and pricing parameters record creation.

You need to create an upload request type for the C1-BillLevelUploadRequest business object. You can then upload a mass bill group derivation and pricing parameters record creation file in the CSV format using the respective upload request type. The mass bill group derivation and pricing parameters record creation file should contain records with the following information – bill group ID or bill group identifier type and bill group identifier, sort ID, source system, bill level 1 (i.e., parameter 1), bill level 2 (i.e., parameter 2), bill level 3 (i.e., parameter 3), bill level 4 (i.e., parameter 4), and effective date. For more information, see Mass Bill Group Derivation and Pricing Parameters Record Creation CSV Format.

While uploading a mass bill group derivation and pricing parameters record creation file, you need to specify the parent customer whose bill groups' derivation and pricing parameters records you want to create. On uploading a mass bill group derivation and pricing parameters record creation 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 bill group (i.e., person) ID or bill group (i.e., person) identifier type and bill group (i.e., person) identifier is specified in the record.

• Sort ID, source system, bill level 1 (i.e., parameter 1), and effective date are specified in the record.

If the bill group ID is not specified in the record, the system derives the bill group ID using the respective bill group identifier type and bill group identifier combination. If the system could not derive the bill group ID using the bill group identifier type and bill group 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 checks whether the upload request must be validated in the real time (i.e., immediately) or in the deferred mode (i.e., in the background). If the total number of records in the upload request does not exceed the online record validate limit, the system validates the following in the real time:

• The bill group (i.e., person) ID given in the record is valid.

• The parent customer's person type is set to Parent Customer in the system.

• The bill group identifier type is available when the bill group identifier is specified in the record and vice versa.

• The bill group is the child person of the parent customer.

• The bill group's person type is set to Bill Group in the system.

• The relationship between the bill group and parent customer is effective on the system date.

• The bill group is related to the parent customer using the relationship type that is specified in the Person Relationship Type option type of the C1-ASOBLLNG feature configuration.

• The source system exists in the extendable lookup that is specified in the Source System Extendable Lookup parameter of the C1-BLVLVALID algorithm.

• The bill group sort record with the bill group ID and sort ID combination already exists in the system.

• The effective date specified in the record is within the date range of the bill group sort record.

• A duplicate record with the source system, parameter 1, parameter 2, parameter 3, parameter 4, and effective date combination does not exist for the bill group in the C1_​BILL_​LVL table.

• The two or more records with the same source system, parameter 1, parameter 2, parameter 3, parameter 4, and effective date combination do not exist for the same bill group 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.

However, if the total number of records in the upload request exceeds the online record validate limit, the system changes the status of the upload request to Deferred Validation. The system then validates the records and changes the status of the upload request from Deferred Validation to Validated when the C1-UPLRQ batch is executed.

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 with a unique combination of the source system, parameter 1, parameter 2, parameter 3, parameter 4, and effective date, this algorithm creates one bill group derivation and pricing parameters record for the bill group ID and sort ID combination. The status of the bill group derivation and pricing parameters record is set to Active.

Once the bill group derivation and pricing parameters record is successfully created, the status of the record is changed to Processed. However, if any error occurs while creating the bill group derivation and pricing parameters record, the status of the record is changed to Error. Finally, the status of the upload request is changed to Processed.