Customer Fields of BIT class of SAP CI is not reflecting in SAP CC Charged Item Class.

[mohammedhussain]

Hello experts,

We have created the BIT class in SAP CI and activated the interfaces as well. We have created the Charged Item Class through Billable Item Mapping in SAP CC. The concern is I am able to see the standard fields in charged item class but not the ZZ fields.

Note: Billable Item Class is refreshed and bulkloader is restarted in CC.

Best Regards,

Mohammed

[francois_thimon]

Hi Mohammed,

In order to confirm that CI sends the complete BIT class structure to CC, can you please enable the JCo debug traces in the dispatcher?
Then, please reload the BIT class structure again in Core tool (within the BIT mapping editor) and check the dispatcher's traces.

If you have a doubt, you may open a support ticket to send the trace file to us.

Best regards.

François
SAP Convergent Charging Support

[chandru_sdn80]

HI francois.thimon ,

I am sorry, it may be off the topic. Would you pls let me know how to enable the JCo debug traces in the dispatcher?

Thanks

Chandru.R

[mohammedhussain]

Hi Thimon,

Thanks for the reply.

I followed the steps you mentioned. I did check the dispatcher trace file and found the below

Table(s):

Table 'DFIES':

<List of standard charged items along with ZZ fields>

I didn't understand this what does this mean. Please explain it.

Best Regards,

Mohammed

[francois_thimon]

Hi Chandru,

Your question may actually be helpful for others.
To enable debug traces in one or many CC instances, you must:
- first enable the "JCO" tracing domain (which results in disabling all other domains)
- then set the log level (the "severity") to "DEBUG"
For both of these operations, you should specify the involved instances, and make the change only in memory (because debug traces should not be kept permanently enabled).
After having enabled the debug traces, you should immediately reproduce the issue and restore your usual settings, in order to avoid generating unwanted additional traces.

Convergent Charging's Tuning guide gives the detailed procedure:
- for admin+ (console-based interface, installed by default):
https://help.sap.com/viewer/4c9aeffd94de48f8ba0253b7e1e6e50f/2020.2/en-US/78aa35dea7c84af086c61f982a...
- for Cockpit (web GUI, optionally installed):
https://help.sap.com/viewer/4c9aeffd94de48f8ba0253b7e1e6e50f/2020.2/en-US/2a18a0164705428087e03dcdb3...

Best regards.

François
SAP Convergent Charging Support

[francois_thimon]

Hi Mohammed,

When you refresh a BIT class this way, the dispatcher retrieves that class's latest definition from CI, and dumps it in its own TRC file.
So, below the text you've copied, you should see all the class's fields listed in a table (one field per row).
In that list, you can check whether your new field appears or not. If you need help with that, you should open a BCP ticket, where you can safely send your trace files for us to analyse.

Best regards.

François
SAP Convergent Charging Support

[mohammedhussain]

Hi Thimon,

I can see new fields in that list generated in trace file.

Best Regards,

Mohammed

[francois_thimon]

Hi Mohammed,

If the dispatcher shows that it has also received the new field definitions from CI, the class should be properly updated now (using Core tool to refresh a newly modified class is the standard procedure).
So, can you please confirm that all the fields are usable now, when you reproduce the scenario?

Best regards.

François
SAP Convergent Charging Support

[mohammedhussain]

Hi Thimon,

Still I cannot see the customized ZZ fields in Charged Item Class after reproducing the issue. Just to turn all the stones, is JCo settings could be one of the possibility of the issue?

Best Regards,

Mohammed

[francois_thimon]

Hi Mohammed,

This is surprising. Once you have refreshed the class definition from CI, the updater should take it into account.

The objects are not automatically refreshed in Core tool. Can you confirm that you have closed and reopened the Core tool editor where the class fields appear?
Also, to confirm whether Core tool has received the new field definitions, you should open the charge plan (or at least the class mapping), and export it into a file (using File | Export). This will write all the available data in an XML file and show whether Core tool is really aware of the new fields.

To answer your question, the problem doesn't seem to be related with JCo settings at all: as long as CI sends the proper field list to CC, the JCo communication doesn't seem to be at fault.

Best regards.

François
SAP Convergent Charging Support

[mohammedhussain]

Hi Thimon,

Thanks for prompt response. I did refreshed the billable item mapping and restarted the bulkloader as well. Also I have generated multiple Charged Item Classes for same BIT class of CI even though there is no success. Even I exported the class mapping to see the customized ZZ fields but I didn't find any ZZ fields.

Best Regards,

Mohammed

[francois_thimon]

Hi Mohammed,

Currently, the issue is with the updater (or possibly with the dispatcher), because the definition of your objects involves only them. On the other hand, the bulkloader comes into play only after the rating, so restarting it won't help.
Consequently, for now, it may be useful to check the logs and traces of the updater and of the dispatcher, to see if there's a particular error when you refresh the item class from CI (if you need help with this, you'll probably want to open a support ticket, in order to get a secured space to upload your trace/log files).

Best regards.

François
SAP Convergent Charging Support

[mohammedhussain]

Hi Thimon,

I appreciate your help. We found the issue. The issue was in CI side not in CC. ZZ fields in Other Status Group config tab was not maintained for raw bits in CI. Hence the issue.

Best Regards,

Mohammed