Adhoc Billing Batches not Picking Up the Records when Non-mandatory Soft Parameters are not Passed
(Doc ID 2440020.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Financial Services Revenue Management and Billing - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
In RMB v188.8.131.52.0 against FW v184.108.40.206, it is found that some Adhoc billing batches are not picking up the records when non-mandatory soft parameters are not passed.
Observed that some of the non-mandatory parameters are behaving like mandatory for the below batch programs of On demand Billing process:
1) C1-ODBCH – Billable charge creation
The parameter headerId has given as non-mandatory in the batch control. However when running the batch without providing the header ID, the batch is throwing some exceptions and no records have processed.
2) C1-FABL – Adhoc Bill generation
The parameter fileGroup has given as non-mandatory in the batch control. When running the batch without providing the fileGroup, the bills are not being generated.
3) C1-FCADH – Adhoc Bill Freeze
The parameter fileGroup has given as non-mandatory in the batch control; but when running the batch without providing the fileGroup, the bills are not getting frozen.
There is a query on the validation batch as it is failing when the price item parameters are not provided.
The record validation is failing when the entries are not populated in CI_BCHG_STG_PRI_PARAM table. No price item parameters as per the solution is required and the records to the adhoc staging tables are supposed to be populated by a custom program. But running the validation batch (C1-ODFU), the records are marked as failed with a message. When re validating the records after putting some dummy records to the table CI_BCHG_STG_PRI_PARAM, the records processed successfully.
Also when I tried uploading the records using the file (no price item parameters are provided), it is observed that the similar dummy records are getting inserted in CI_BCHG_STG_PRI_PARAM table.
Since the fields are marked non mandatory, these should not be required.
Otherwise the fields should not be set as non mandatory.
The issue can be reproduced at will with the following steps:
1. Run C1-ODBCH or C1-FABL or C1-FCADH without providing the non mandatory fields in corresponding batch run setup.
The issue has the following business impact:
Due to this issue, users need to provide values that they do not use.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document