We are facing an issue with provider contract activation in SAP CC system. we have verified the fulfillment steps and one thing concerning is the ODI step Activate SAP CC Charging Contract which is set to Irrelevant.
However, we have configured below parameters required for contract activation and also triggering of billable items from CC to S/4 per integration/help guides using admin+ role.
system details: on S/4 2021 (on-prem) and CC on 5.0.6
here are the parameters configured:
1) execute start_contract_activation system parameters for contract activation
2) set the parameter ACTIVATION_SCHEDULER_RECURRENCE
parameter value: 3-9-15-21h/0m ( to run the scheduler recurrence at 3am/9am/3pm/9pm every day )
3) set the parameter POSTPAID_CIT_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY using admin+ role ( command: set POSTPAID_CIT_WRITER_MAX_SIZE_BASED_FILE_ROLLOVER_POLICY to MINUTELY
4) set parameter ACTIVATION_SCHEDULER_ENABLED to true (it's available by default)and restart all the instances of CC server individually
Can you please suggest/guide if we are missing anything?
appreciate your help.
By default, Convergent Charging's activation process is already configured to start automatically, because ACTIVATION_SCHEDULER_ENABLED is already set to "true". You have also set the ACTIVATION_SCHEDULER_RECURRENCE according to your needs. Normally from the parameters that you have set the contract should be activated and the respective charges should be triggered. Nevertheless, there are some additional checks that you might do.
So, when you need to activate a contract immediately, you should rather use the "chargingContractActivate" SOAP method:
This recommended approach will process only the targeted contract, instead of going through the whole database.
Alternatively, you may also target several contracts in one request, using "chargingContractBulkActivate":
This is the first step that you can check if everything is fine in CC and if you do not have any problems. If the last activation date is set then most probably there is an issue with the Activation Call from S/4.
When the rater computes charging results, it temporarily batches them in CSV files, and the bulkloader has to wait for a while before these files become accessible, in order to generate BIT's for CI. If you need the bulkloader to send this data sent to CI sooner, you may indeed change the "XX_FILE_ROLLOVER_POLICY" parameters.
I would also suggest that you check the Rater log files if even after the WS activation the Last Activation Date is not set.
Hope it helps,