No service for system in Integration Directory

[Former Member]

Hi,

i already checked SDN and OSS Note 940313.

We want to send IDoc from System to XI. Therefore sender gets "No service for system SAPPSI, client 010 in Integration Directory"

Thats because IDoc-Adapteris not able to identify SAPPSI.

Well this Port does exist in IDX1.

In Integration Directory the Adapter-specifc identifier shows "PSI" and client "010".

So everything seems to work fine! Even the RFC-Destination has no errors!

The IDoc contains "SAPPSI" and the client "010" in the right fields, but we have no idea what causes the problem!

Does somebody can provide me with ideas on how to solve this issue?!

br

[GabrielSagaya]

Try following things

1. As already told by other members, Verify the logical business system in SLD.

To verify --- Go to SLD home page ---> Technical Landscape --> Select Web AS ABAP --> Select the technical system --> Clients ---> Click on the client you used as Business system --> Here look for the logical system is defined or not.

2. Open ID---> Click on Objects --> Service Without party/Party > Double click on business system>On the tright side--> Service --> Adapter specific Identifiers ---> Check IDoc Adpater, Logical System.

3. Refresh the full CPA Cache (userid must be XIDIRUSER/PIDIRUSER)

http://<hostname>:50000/CPACache/refresh?mode=full

[Former Member]

Hi to all.

Because i already did everything you mentioned i am kind of desperate.

Question concerning Sender-Information in IDoc-header.

There is send <SNDPOR>SAPPSI</SNDPOR>.

This port reference the one in IDX1?!

I am asking because we have a testsystem also sending IDoc's where everything works out. System is called ASI so the port is SAPASI. As i mentioned, this works!!!

In ID the Business Systems are called ASICLNT010 and PSICLNT010. The adapter specific Identifiers are saying:

For PSI

R/3 System ID: PSI

Client: 010

For ASI

R/3 System ID: ASI

Client: 010

So what the hell is the problem?!

br - thx to all!

[prateek]

Have u created WebAS ABAP BS and TS for ur sender R3 system?

Regards,

Prateek

[Former Member]

Yes i did. Otherwise i won't be able to import Business System in ID.

Did i understand you right?!

In BS the logical system name is as given in previous post!

br

[Former Member]

Hi,

Have you gone through it.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344...

In your ID do this, Environment ---> Clear SLD Data Cache

Also refresh the cache, if not done it before.

Regards,

Sarvesh

Edited by: Sarvesh Singh on May 9, 2008 6:45 PM

[Former Member]

Hi, we solved the issue.

Port SAPPSI called the right RFC-Destination, but the "URL" inside the destination pointed to another XI System.

That's all - what a dumb fault!

br - thx to all your help!

[GabrielSagaya]

This problem is due to incorrect RFC setup in SM59.

Recheck the RFC connection for both XI and SAPPSI

Also check if your Logical System Name is correctly maintained in the SLD

/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system

[Former Member]

Check in R/3 system client 010 by tocde BD54 if logical system name matches with which you have in the SLD.