Issue with "Pin_bus_params -r BusParamsBilling"
(Doc ID 2505871.1)
Last updated on NOVEMBER 26, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.17.0 and laterInformation in this document applies to any platform.
Symptoms
The execution of pin_bus_params (with -r BusParamsBilling) command removes important parameters (like general_ledger_reporting) and disables journal posting.
In more detail, when executing the command 'pin_bus_params -r BusParamsBilling bus_params_billing.xml', it creates the file bus_params_billing.xml.out. But, this .out file is not containing the below parameters, even though those parameters are already present in /config/business and also in $PIN_HOME/sys/data/config/bus_params_billing.xml:
general_ledger_reporting - GeneralLedgerReporting - Boolean value enabled/disabled
acct_cycle_delay_period - AcctCycleDelayPeriod - integer
backdating_past_gl_posted_date - BackdatingPastGlPostedDate - Boolean value enabled/disabled
perf_advanced_tuning_settings - PerfAdvancedTuningSettings - integer
refresh_exchange_rate - ExchangeRateRefreshInterval - integer
Moreover, loading back the bus_params_billing.xml.out reports some errors.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |