IDOC Adapter error

[Former Member]

Hi,

We have IDOC Sender & receiver adapter in PI 7.11 to send/rec idoc from ECC. Since few days, i am seeing errors under my ID  in ECC

I checked in SM58 in ECC and i see error " No service for system SAPXXX, client XXX in Integr ation Directory"

This come sunder Function module " IDOC_INBOUND_ASYNCHRONOUS" in SM58 every day. Next day old once are gone & new one comes.

I cheeked the forum and looked at SM21 in PI. I found errors. I am not sure how & when thhis error comes as i checked all RFC, SLD etc..

Also no RFC is under my name still it is coming under my name.. Please advice.

Error in SM21 in PI below

The transaction has been terminated.  This may be caused by a

termination message from the application (MESSAGE Axxx) or by an

error detected by the SAP System due to which it makes no sense to

proceed with the transaction.  The actual reason for the termination

is indicated by the T100 message and the parameters.

Additional documentation for message IDOC_ADAPTER        601

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 recor

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.

&SYS_ADMIN&

[Former Member]

Adapter specific property are good! Also the RFC channel, SLD & SLDCHECK is good! Any more suggestion. Thanks!

[former_member184720]

Did you check the threads which i shared?

control record has incorrect partner number/ IDX1 port issue?

[Former Member]

I ma getting error as like below

No service for system SAPSEP, client 300 in Integr ation Directory

Although my ECC system name is SAPSEQ Client 300. It is showing SAPSEP.. Not sure where it is coming from.

[former_member184720]

Please check the below thread -

[Former Member]

Hello,

If the Adapter Specific Identifiers are ok, and the Business System entry in the SLD is correct,
can you please try refreshing the SLD cache.

Is SLDCHECK successful?
Is transaction SXMB_ADMIN -> Integration Engine Configuration configured correctly in the Business System?

Kind regards

[engswee]

Hi Techie

Have you check the IDoc configurations on the ECC side as well? Did you check the control records of the corresponding IDocs of those SM58 errors? The SAPSEP value might be coming from the IDoc control record.

Was there a refresh of the SEQ system from the SEP system recently?

Rgds

Eng Swee

[Former Member]

Hi,

We have faced the similar error some time back .Check the below.

go to sld -->Business systems-->select your ECC business system and click on Integration tab-->check every thing is fine (client,logical system,technical system ...).

If the above are fine then come to ID and click on your Business system-->adapter specific identifiers-->check is it the same as BS in sld ? If it is not the same then click on  icon at bottom(compare with sld) to reimport .

Regards

Venkat

[Former Member]

I have checked the adapter specific setting and it looks ok.. SLD and BS looks good.. This was running system but suddenly give errors. SID ID all is looking good..

[Former Member]

Hi,

For us problem solved by reimporting content from sld.

Hope you checked the below.

1)type 3 RFC is working at the point of messages struck in sm58 (ECC).check connectivity and authorization checks.

2)Make sure you are using right ports

3)Since IDOC to IDOC hope you are filling control records in mapping then you need to check take from payload option in receiver agreement .

3)Make sure mata data is latest by checking in idx2

Regards

Venkat

[Former Member]

Hello,

Please refer to the steps in note:

940313 :IDoc adapter: Error messages in SM58

Kind regards,

Sarah