Hi Sunny,
When it comes to diagnosing charging operations and billable/consumption item generations, Convergent Charging doesn't have any feature to debug one contract in particular, but you can still use any combination of the following features to achieve a comparable result.
- get JCo traces: in the bulkloader, enable the "JCO" tracing domain (and the "DEBUG" level) to see what BITs are actually sent to CI.
- get charging request traces: in the dispatcher and/or the rater, enable the "WS" and/or "MSG" tracing domains (and the "DEBUG" level) to dump every WS request and/or charging request processed.
- enable the "tracing passport": if you are using the SOAP WS interface, you can set a special HTTP header in a request to enable the "tracing passport"; this will activate debug traces in all the instances, only for that particular request, so you can "follow" it through it the system.
- debug the pricing logic: in Core tool, use the "Trial run" to execute a pricing logic step by step in a manually defined context (i.e. the property values will be manually set, not taken from an actual contract).
Depending upon your needs, you may also decide to change your pricing logic temporarily, in order to send property values in notifications or user alerts (so as to read them outside of CC), or you can set your bulkloader to archive the billable item files, so as to let you verify them after the rating.
Feel free to ask for more guidance if needed.
Best regards.
François Thimon
SAP Convergent Charging Support
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.