SAP PI7.3 IDOC AAE : JCO_ERROR_SYSTEM_FAILURE

[former_member183909]

Hi

I have an inbound IDOC (from PI7.3 into my R/3 system RED) that is failing in the SAP PI and in RWB it can be seen with this error.

Message processing failed. Cause:
javax.resource.spi.EISSystemException: com.sap.conn.jco.JCoException: (104)
JCO_ERROR_SYSTEM_FAILURE: No service for system TRFCSAPPID, client in
Integration Directory (raised by system RED|RHIHSAPDCI01) Message 601 of class
IDOC_ADAPTER type A, Par[1]: TRFCSAPPID

The TRFCSAPPID is the R/3 WE20 TRFC PORT.

The IDOC EDI_DC40 Sender Profile

SNDPOR = TRFCSAPPID

SNDPRT = LS

SNDPRN = WENCO

and Receiver parts

RCVPOR = SAPRED

RCVPRT = LS

RCVPRN = REDCLNT110

(I have created a test IDOC in R/3 via WE19 just to make sure that the IDOC would find the partner profile and process the IDOC - and this had the same settings, SNDPOR etc as above.  That works.)

However when an IDOC is sent from SAP PI7.3 into R/3 it fails with that JcoException.

What is causing that error?

[former_member183909]

Chaps - I have now got this working.  In the end it was the IDOC default destination that was pointing to Client100 and my Business System I was using is Client110.   Once I changed the IDOC default destination it worked.  That Java exception from ECC really threw me.  Thanks for all of your comments.

[Former Member]

Hi Johny,

Good Day!

Refer this link and check your configuration accordingly..

http://scn.sap.com/docs/DOC-31398

Regards,

Hari Suseelan

[former_member183909]

Hi

the IDOC configuration seem to be set up correctly.  The PI JavaIDOCAdapter is running / green and has the DefaultSenderPort = TRFCSAPPID.  The PI inbound Resource Adapter is running / green.   The associated IDOC default destination can reach R/3.

The inbound IDOC SNDPOR is mandatory (not sure why Swathi has in that blog that it is not).. anyway that is set with TRFCSAPPID.

That message says it is raised by my R/3 system so it is connecting (yes ?). 

I am certain that you set the IDOC SNDPOR to the R/3 WE20 TCP/IP port name (in my case TRFCSAPPID). 

What else could that error be?

[Dimitri]

Hi Jonny,

Your receiver idoc communication channel is linked to a Business System or Business Component.

Please have a look at the Adapter-Specific Identifiers. Is that filled in?

Also, did you create a partner profile on your receiving SAP system?

Make sure the Logical System, linked with the Business System or Business Component is the same as the Logical System used in your partner profile.

Kind regards,

Dimitri

[former_member183909]

Hi

yes it is linked to a R/3 Business System (I have used this before successfully to receive in ABAP Proxies - so I know that works).

EDI R/3 set up has been done - and yes with a partner profile.

I am now fairly certain that message I get is from R/3 ABAP message class IDOC_ADAPTER  - and from doing a where used on the message no a601 it is from ABAP LIDOC_ADAPTER_MBF01.

So at least it is getting to R/3 - but failing to marry up the  SNDPOR = TRFCSAPPID  [The TRFCSAPPID is the R/3 WE20 TRFC PORT].

Why is it struggling to do this?

[gagandeep_batra]

Hi Jonny,

As Dimitri said Did you check in Receiver Business System in ID as below:

Regards

Gagan

[former_member183909]

Hi

- yes exactly as I would expect - the R/3 Business System has the Logical System and R3 SystemID/Client as I would expect.

It is getting to R/3 as I have set an external breakpoint on that ABAP include LIDOC_ADAPTER_MBF01 that is throwing the exception.  Debugging it now.

[Former Member]

Hello,

Why don't u use header mapping (disable EDI_DC40 segment in mapping) and post ur idoc in ECC and once it's successfully done then may be u can cross check control record section?

>>I am certain that you set the IDOC SNDPOR to the R/3 WE20 TCP/IP port name (in my case TRFCSAPPID). 

IMO, it's not necessary.

The default sender port name in NWA and TRFC port name in WE21 is not necessarily to be same.

Thanks

Amit Srivastava

[former_member183909]

Hi Amit

Are you suggesting not to provide the  SNDPOR in the IDOC ?  (it is mandatory according to the IDOC structure).

[Former Member]

Hello,

I am suggesting to disable EDI_DC40 segment in mapping (and uncheck  "apply control record from payload" in java idoc receiver channel) and let PI automatically populate control record data from header mapping (open ICO -> Outbound Processing -> Header mapping -> populate sender communication component name)

Make sure that before running ur scenario you have created a partner profile in ECC with the logical system name of Business system/Business Component provided under  "sender communication component".

Thanks

Amit Srivastava

[former_member183909]

Hi

receiver IDOC Comms Channel already had "apply control record from payload" unchecked.  But perhaps because my sender Business Component did not have a logical system set (in it's adapter specific settings) it was still taking it from the mapping.

Anyway I have now set my Business Component to have WENCO and the logical system. And WENCO is my LS logical system partner profile in R/3.

When sending another IDOC It still fails with the same error in R/3 when it tries to get the XI service id.

what should an inbound IDOC contain in;

Partner - SNDPRN - WENCO

Type - SNDPRT - LS

Role -  SNDPRC - blank

Port - SNDPOR   - I have tried SAP+<SID> of my sender integration server

Client - ? - My integration server is a Single Stack JAVA system

[Dimitri]

Hi Jonny,

Check you receiver agreement and try to play around with the header mapping part.

Also, do not provide those fields in your message mapping. Leave them blank or just map a fixed value to it.

Like already stated before, disable segment EDI_DC40

Kind regards,

Dimitri

[Former Member]

Hello,

Ur inbound idoc should contain these details:

Recipient information:

Port: SAP<ECC SID> (SAPRED)

Partner Number (RCVPRN): REDCLNT110

RCVPRT = LS

Sender Information:

  Partner Number (SNDPRN) - WENCO

  Partner Type (SNDPRT) - LS

Sender Port (SNDPOR)   - SAP+ <SID> will do (infact u can use any name)

  Partner Role -  SNDPRC - blank (not required)

  Client - blank (not required)

Thanks

Amit Srivastava

[manigram]

Hi,

Check your idoc configuration in NWA , like destination and JCO Connection.

Regards,

Manigandan