Based on the requirement we have to trigger few calculation on contract activation, we are using CC activation one shot rate. The behavior of one time rate is not consistent, if we create contract in past, the charge activates in CC for the replicated contract , but for few of contracts it generates BITs and for few there is no contract. We checked all the logs but did not find any thing. The activation parameters are set as below
Please advice if we need to change any other parameters.
Also, if the CC one shot rate on activation is still a feature in CC 5.0- I mean can we still use one shot on activation, please suggest.
Yes, one-shot events still exist in CC so, if you create your contracts in the past, the next activation should process the one-shot event for their creation, and also the recurring events between the creation date and the current date.
Here, "activation" is the process of listing and computing all due recurring charges (i.e., only for recurring events applicable before the current date).
Sometimes, when the activation doesn't work, it is due to errors in the pricing logic. For example, some users put "No access" components in their recurring charges, and the rating is then aborted (as well as all further charges for the affected contracts, this is why "No access" should not at all be used in recurring charges).
So, first, can you check the logs of the activation process, and see whether CC reported any such errors?
Please also check the "Last activation date" for the affected contracts: it's like a cursor, which is shifted every time the activation completes successfully for a contract. If it doesn't move, it means the activation has not been completed.
Otherwise (if the "Last activation date" has properly been updated), it means the rating has worked, but another error occurred afterwards. In that case, as suggested by Raphael earlier, you can also check your BIT mapping, to see if CC successfully performs the rating but is then unable to send the BIT's to ERP.
It's also possible that the BIT's have properly been sent by CC, but that ERP kept them in the "RAW" state (because the provisioning or the configuration is incorrect).
If you need to check what CC actually sends to ERP, you can activate the "JCO" debug traces in the bulkloader. You'll then see every BIT sent, so as to confirm which contracts are fully activated or not.
SAP Convergent Charging Support