Logs Lord of PI.
Recently, we were working on CIDX scenarios on SAP PI 7.31 (AEX).
Most of them were, IDOC to/from CIDX scenarios, where one of the system was ECC and other one was CIDX compliant system.
Let me take example of one recent scenario : CIDX to IDOC.
Brief info on how CIDX message finds SAP PI sender agreement:
The CIDX adapter determines the communication component for an incoming CIDX action message based on selected header fields of the RNIF 1.1 protocol service header. The adapter then constructs the name of the communication component.
For E.g. Name of communication component:CIDX<Transaction code>_<Version>_<Role>
For CIDX action message to reach to SAP PI server, the CIDX message header should have appropriate values to determine PI objects(sender agreement) run time.
In our scenario, CIDX complaint system was sending CIDX action messages to SAP PI and they were not recieved in SAP PI and nowhere the error information was visible in SAP PI – monitoring tool, communication channel. At sender system(CIDX compliant) was receiving 500 error. SAP PI team is always gets blamed as usual 🙂 .
Then tadaaaaaaaa……… logs(NWA->TroubleShooting->Logs and Traces->Logviewer->Select Developer trace) came to rescue and found the below information:
It is clear that there is mismatch between CIDX message header and configuration in CIDX sender adapter and after proper CIDX message header message got received in SAP PI.
I know that logs are not new to people and there are already blogs on logs 🙂 , but I thought to write blog on this as we do not use logs extensively but scenarios like this require only logs for further troubleshooting.
More info on CIDX:
Hope this helps to people working on B2B adapters.