Subscription Contract not replicating to FICA and CC

[former_member655345]

Hi All,

We are implementing BRIM scenario using S/4 HANA customer management and SAP CC/CI part.We have created subscription products ,subscription order and subscription contract from S4CRM.

But Subscription contract is not getting replicated to FICA and CC and .We can see in the fkkcc_pc_mon subscription contract with the error .

Diagnosis

Master data object was successfully created or changed in Contract Accounts Receivable and Payable. However, the change was not distributed to SAP Convergent Charging.

Procedure

Distribute the change of the master data object to SAP Convergent Charging.

Does anyone guide us what could be the potential issue.

Regards

Nikhil

[anilm1]

Dear Nikhil

We are facing similar issue. If you could able to resolve the issue, would you please help us.

thanks in advance

BR

Anil

[francois_thimon]

Hi Nikhil,

If you're still getting the same issue, you should check the CC updater's trace file. It will tell you whether CC rejected the creation for some reason.
If this is not explicit enough, you may also enable the WS debug traces in the CC updater and reproduce the issue to generate detailed new logs.

Best regards.

François
SAP Convergent Charging Support

[anilm1]

Hello Fransis,

We are also facing similar issue. Can you please help to understand how to execute the said step in CC.

Thanks

Anil

[francois_thimon]

Hi Anil,

Normally, CC receives SOAP queries from S/4 HANA and, based upon them, creates the contracts in its own database.
If the creation doesn't happen as expected, it most likely indicates that the queries were not sent at all, or invalid for some reason.
First of all, you should check the results in S/4 HANA to see if any error response was sent back from CC. If a further investigation is necessary, you need to:
1. First, enable the WS debug traces in the CC updater.
For this, please set LS_TRC_DOMAIN to WS and then LS_TRC_SEVERITY to DEBUG, using the following procedure:
https://help.sap.com/viewer/4c9aeffd94de48f8ba0253b7e1e6e50f/5.0.6/en-US/78aa35dea7c84af086c61f982ad...
2. Reproduce the whole scenario in order to generate the actual traces in the CC updater.
3. Restore your usual log levels, using the same procedure.
4. Retrieve the CC updater's last trace file (its name is similar to updater#n_LDF2.x.trc). The default location is /usr/sap/<SID>/CCU<nn>/work/log/.

This TRC file contains all SOAP dumps and will tell you whether CC actually received any queries from CRM at all, and whether they were successfully processed or not.
If you need further help with this, you can open a BCP incident and send us the trace files.

Best regards.

François
SAP Convergent Charging Support

[anilm1]

Thanks a lot francois.thimon