No service for system SAPXXX, client in Integration Directory

[Former Member]

Hi,

A Third Party system is sending IDOC to SAP PI over TCP/IP. But when message is sent the Third Party application receive a error message "No service for system SAPXXX, client in Integration Directory"

Some investigation already done is:

1) The logical system name in SLD and in Adapter specfic is same

2) The following IDOC control details is populated by Third party application SNDPOR / SNDPRT /SNDPRN / MESTYP /IDOCTYP

Could any one let me know what could be the probable reason.

Thanks

Praveen

[Former Member · Accepted solution]

the Error is sloved by Analysing Error from the T-Code SM21.

"should Populate the SNDPOR Value with Logical System Name which wwe maintained in SLD"

Following is the Information extracted from SM21

"No service for system &1, client &2 in Integration Directory

&CAUSE&

Unable to determine the service for system &1, client &2.

&SYSTEM_RESPONSE&

You tried to determine a service for system &1, client &2.

The system ID is taken from the sender port of the IDoc control record,

which must have the form 'SAP' + system ID. In the case of external

systems, in the sender port field you must enter the logical system

that is assigned to the service in the Integration Directory.

&WHAT_TO_DO&

Maintain a service in the Integration Directory for system &1,

client &2.

"

Edited by: praveen kalwa on Jul 6, 2010 4:34 PM

Edited by: praveen kalwa on Jul 6, 2010 4:35 PM

[Former Member · Accepted solution]

HI Praveen,

I have a similar scenario and similar issue, and I am doing what ever you have said but still I am getting this

Transaction IDX1: Port &1, client &2, RFC destination &3 contain error

&CAUSE&

Transaction IDX1: Port &1, client &2, RFC destination &3 contain error

&SYSTEM_RESPONSE&

You tried to fetch the metadata for the current IDoc from the referenc

system, using RFC.

In doing so, an error occurred that was caused by one of the following

1. You have not yet assigned a port/client to the RFC destination.

2. You have not yet created the RFC destination or it contains errors.

3. The target system is unable to receive.

&WHAT_TO_DO&

1. Check your RFC destination in transaction SM58.

2. Check your assignment of port and client to the RFC destination in

transaction IDX1.

I have defined metadata in IDX2 and created port as well, is there anything specific that needs to be done.

If you could reply to this asap, that would be a great help.

Cheers

Abhi

[Former Member]

Why is third party system sending IDOC to PI? Is it not an ECC system? Are you using WSDL created based on IDOC structure?

Confirm this.

I am assuming you are sending from an ECC system. In which case check the following.

1. Go to SLD and check if the business system has been assigned with proper technical system. If it is not created push it to SLD (pushing works better than manual creation) else if the TS is correctly assigned to BS, then go to step 2

2. Go to Business system in ID and click on adapter specific identifiers and check if your BS shows up the logical system and SID, client correctly for the TS. If its not assigned, in edit mode, click on the button to compare SLD entries.

Venkat.

[Former Member]

Hi Venkat,

The 3rd Party system not an ECC system but can send and Accepts the IDOC Over TCP/IP to PI.

I have Cheekd your 2 Points and it is Fine.

Please let me know if you have any Solution.

Regards,

Praveen K

[Former Member]

Hi

But when message is sent the Third Party application receive a error message "No service
 for system SAPXXX, client in Integration Directory"

Please check your configuration in integration directory,do a test configuration.

Is your third party system a sap system? what is your target system?

Please check if partner profile,port and RFC destination are working fine when tested.

regards,

Srinivas

[Former Member]

Hi srinivas,

My Configuration isCorrect and working fine.

My 3rd Party system is a NON-SAP system sending IDOC to SAP PI.

Regards,

Praveen K

[Former Member]

Hi Praveen,

the third party system may be sending you the IDOC xml and in PI your are mapping it to IDOC and posting it in the SAP system.

In this case we need to create a logical system in SAP for the identification of the third party and in the business service which

we create for the 3rd party , in adapter attributes mention the logical system created in ECC earlier otherwise you will get ALE errors..

Regard,

Srinvas

[Former Member]

Hi ,

The Scenario is 3rd Party(IDOC)--->SAP PI --->3rd Party (SOAP).

There is no ECC in the Landscape.

regards,

Praveen K

[Former Member]

Dear,

Have you filled Logical System Name in the SLD and then imported it in the adapter specific identifiers?

If this is correct,

Cache may be the reason for this :

Refresh Cache SXI_CACHE.

RegardsDragon