provider contract inconsistency

[Subbareddy2]

Hi Team,

I am getting the" provider contract inconsistent data "while provider contract transfer into CC system. I am not sure where it went wrong, please can help to resolve the issue.

T code-FKKCC_PC_MON

SLG1:

Thanks

Subbareddy

SAP Billing and Revenue Innovation Management, subscription order management SAP Convergent Charging SAP Billing and Revenue Innovation Management SAP Contract Accounts Receivable and Payable 

[francois_thimon]

Hi Subbareddy2,

The error message doesn't come from Convergent Charging.
Still, if you need to analyse what happened within Convergent Charging, you can enable the "WS" debug traces in the updater and then reproduce the scenario.
This can be done using either the Cockpit web UI, or admin+.sh with the two following commands:
set LS_TRC_DOMAIN WS memory updater
set LS_TRC_SEVERITY DEBUG memory updater

Then, you'll see the SOAP dumps in the updater's TRC files, and it'll tell you whether CC faces issues or not.
Can you please try that and let us know the outcome?

Thanks, and best regards.

François
SAP Convergent Charging Support

[Subbareddy2]

Hi François,

I am getting the below Error, but not sure where its went wrong.

Thanks

Subbareddy

[francois_thimon]

Hi Subbareddy,

Sorry for the late answer, I hadn't seen your new message.
The error you're getting is generated by the SOAP WS layer of the updater, in Convergent Charging. More precisely, it's related with the credentials sent by SOM.

To start with, you can already check the updater's logs (updater#x_LDF1*.log) to see if there's a more detailed message at the time of the error.
If you don't find anything relevant, your best bet is to enable the "WS" debug traces (in the CC updater, again), and to reproduce the issue. Normally, you'll then get detailed messages in the TRC file.

Here are already the most probable causes for issues of this kind:
- There's a large mismatch between the clocks of SOM and CC (and SOM writes the time within each query's header). As a precaution against forgery and "replay" attacks, the SOAP server rejects queries with an inconsistent time.
This is explained in detail in SAP note 2428165 ("web service requests rejected").
- Your SOAP client uses the credentials of an "individual" user. Depending on the system configuration of CC, you usually need a "service" user instead.
More details about this are provided in the CC Security guide (you may also have to check the "USER_ISOLATION_ENABLED" system parameter).
- The credentials of your SOAP client are actually wrong or expired.
One way to check that is to try them our in Core tool, or to update them completely.

Feel free to ask for more advice if needed.

Best regards.

François
SAP Convergent Charging Support