IDoc status 03 not reaching CPI

[Tasmay]

Hello Gurus,

Need your input

For integration, we have developed an IDoc-based Scenario using CPI as middleware.

On saving Invoice IDoc is getting Triggered and its Status is 03 in WE02

But unfortunately, it's not reached to CPI tenet, but if we do a connection test in SM59 we are able to ping CPI with a successful return Code.

[Ryan-Crosby]

Best to start by double checking that the IDoc port is pointed to the correct SM59 destination and after that you would want to enable a trace of the iFlow with the matching IDoc sender.

[Tasmay]

The Port is correct and Its pointing correct RFC unfortunately we are observing strange behavior as 2 or 3 times only IDoc has reached CPI but that too in an uncertain manner.

Enabling the Trace would only be possible if it's reaching to CPI, but it's not entering the tenet

And even thought IDoc is in 03 state

[Lakshmipathi]

Did you check in SM58 ? What it says under "Status Text" ?

[Tasmay]

Its an HTTP connection to an External server (Type G). We have checked SM58 also but no luck it's empty. And have check immediately after triggering IDoc.

Status is 03 (Data passed to Port ok)

[pranav_malhotra]

Hey Tasmay

Please check if you are using role based authentication then your user is having proper role to send http message like ESBMessaging.send role.

[Tasmay]

Hello Pranav,

Its Certificate based auth. and sometime it enters CPI tenet but most of the time its does not.

[pranav_malhotra]

Is your IDOC contains any other language data than English?

If yes, try to use correct unicode settings in your http destination