on 04-09-2015 7:27 AM
Hi Rajavadviel,
Have you set a sender agreement with the business system, like sender component, that identifies your sender ECC system?
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rajavadivel,
I confirm what hareesh mentioned above, for more info please check below sap note.
Check question 19 in below SAP Note.
SAP Note 730870 - RFC Adapter
A: The RFC Adapter tries to find a Sender Agreement for this RFC call
but the lookup failes. The values used for this lookup are:
o Sender Party/Sender Service: The values from Party and Service
belonging to the sender channel.
o Sender Interface: The name of the RFC function module.
o Sender Namespace: The fix RFC namespace
urn:sap-com:document:sap:rfc:functions
Receiver Party/Receiver Service: These fields are empty. This will
match the wildcard '*'.
Regards,
Praveen.
Yes. When you import the RFC into ESR, you should see the default namespace "urn:sap-com:document:sap:rfc:functions"
So while you are creating the configuration objects, you should refer(use) the same RFC that you imported into ESR. This way even you configuration objects will carry the default namespace.
How did you create the receiver determination? Did you type the namespace manually?
Didn't you assign the RFC to you sender business system which way you can select the message interface automatically?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.