IDOC - BPM - IDOC Error --no sender or receiver interface definition found

I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
I have read instructions on weblogs:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
<Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
</Trace>
Thanks,
Sergio

Rajeev,
The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
Below is some trace information in the Receiver Determination.
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - IP_GeneralLedger</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
Thanks,
Sergio

Similar Messages

No sender or receiver interface definition found

Hi,
I have designed an JDBC to R3 scenario.
In the XI system SXMB_MONI the message was processed successully on the outbound side.
On the R3 side. in SXMB_MONI => Trace there is a message like
no sender or receiver interface definition found
What could be the problem. I have checked the IR and ID settings.
Everything seems to be OK. Is there a problem with the Queues.
Please suggest.
Thanks
Kumar

Hi,
We have encountered same error in one of our scenarios. When we restarted these messages they were successfully processed. This could be probably because of the cache update failure at that particular instance when the message was posted.
Restarting the message through SXMB_MONI could probably solve the problem sometimes.
Regards
Sai

Code to retrive the sender and receiver interface names using custome adapter module

Hello Team,
I want to develop an custom adapter module which could retrieve the names of the sender and receiver interfaces of the scenario and for that i am trying to use com.sap.aii.af.service.administration.api.monitoring.ProcessContextFactory.ParamSet but i don't know whether this API will support or not and also i don't know how to develop the code using this API so please suggest me some code for it so that i could retrieve the names.
Thanks you all in advance.
Regards,
Avinash.

Hi,
Just ASMA setting will do the needful. Are you planning to rename your target file name. If yes then only you will require UDF.
Update: Since your directory name will be taken from source file name then you have to use mapping for this, else it will not be possible.
I don't know if creating a new module for this will help you solve the issue, but in that case rather creating adapter module, mapping will be easier.
Regards,
Sarvesh
Edited by: Sarvesh Singh on Dec 7, 2009 3:04 PM

IDOC Error - Copy Sender from Payload: Sender Is Missing in Payload

Hi,
I have following scenario.
SOAP adapter ---> PI -
> IDOC Receiver -
> ECC
THe IDOC has a required node that is disabled and IDOC revicer communication channel has checkd following options.
Apply control record value from pay load
Take Sender from Payload
The soap message is mapped to IDOC structure. While testing I received following error.
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Copy Sender from Payload: Sender Is Missing in Payload</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: Copy Sender from Payload: Sender Is Missing in Payload</SAP:Stack>
If you have seen similar error and please let me know how to trobleshoot. I appreciate your help.
Thank you,
Balaji

Thank you for the response. I can enable EDI_DC40 segment and map required following values.
· SNDPRN
· SNDPRT
· SNDPFC
· RCVPRN
· RCVPRT
However as we move transports to different environemnts the above values changes and I can't hard code in the mapping.
My questions is how can I map these values such that when transport moves across different environemtns the mapping valaues are still good. Please let me know.
Dont enable EDI_DC40 and dont select take sender ,receiver from pay load option,apply control record values from pay load.
this case IDoc adapter reads values from configuration time andno problem after trasporting to quality or prod.
Regards,
Raj

Display sender and receiver interfaces in CCMS

Hello CCMS Specialists,
I've a question regarding CCMS and SNMP TRAPS.
In my case I'm sending the alerts to a Third Party application via SNMP TRAPS. In CCMS I don't get the information about a specific Interface and therefore I can't send it to a third party application.
My question is: is it possibile or how to send the information from an interface (sender and receiver information) via CCMS to our Third Party application?
For example, if there has been an Internal HTTP error. We don't get the details about the interface. Hoe could we display those information as well?
Kind Regards,
Kamran

hi,
And also check spro -
> financial accounting -
> financial accounting global settings -
> correspondence -
> define correspondance check the variant bcause all are standard variants so the one which we require need 2 make changes......... create our variant..
if useful assign points....
regards,
santosh kumar

Modify the ASMA without defining the Sender and Receiver Interface

Hi All,
I am developing a scenario where I am picking files from NFS and putting in FTP.
For this I am using only the ID and no IR content.
So far so good.
But Now we have a requirement to dynamically extract the target folder names from the File name.
e.g
Sourc File: ABC_FN_PQR
Folder name shouild be FN
For this the solution would be UDF.
But now my question is that where do i put this UDF as there is no IR at all.
Please suggest.
regards,
Piyush

Hi,
Just ASMA setting will do the needful. Are you planning to rename your target file name. If yes then only you will require UDF.
Update: Since your directory name will be taken from source file name then you have to use mapping for this, else it will not be possible.
I don't know if creating a new module for this will help you solve the issue, but in that case rather creating adapter module, mapping will be easier.
Regards,
Sarvesh
Edited by: Sarvesh Singh on Dec 7, 2009 3:04 PM

RFC to BPM - Error in receiver interface

Hi everybody,
I have created the scenario below.
i imported the ZStart_Job rfc from R/3
i created the MI_Start_Abs (abstract and async) - message type is same from ZStart_Job
i created the BPM_Job where the send interface is MI_Start_Abs.
i configured the sender and receiver agrameent, receiver and interface determination and others.
i actived everything.
When i execute the "call function ZStart_Job", the execution dosent return error in Message Monitoring, but appears one green flag with hit "Scheduled".
In XML body show the error below
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
Can anybody help me?

Guys,
I used the Configuration Wizard for create configuration again.
But occurs the same error below
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
PLEASE, can anybody helpe me?

No Sender or Receiver Info found

Hi,
We are getting an error message " no sender or receiver interface definition found" while trying to send the messages from XI to ECC.
From ECC we are able to send the message to XI through PROXY. But not able to receive the messages from XI to ECC. In the SXMB_MONI transaction it displays the below error.
No implementing class registered for the interface (ABAP interface, request message , )
Thanks,
CS.

where do you see the error message mentioned? in Pi system?.
what is the scenario you are trying to configure?

Regarding idocs error handling

HI . i want to learn idoc error handling on sap xi side because my current project is in PRODUCTION They implemented lot of idocs so is there any documents(guides ) regarding error handling of idocs for both sender and receiver side.

Hi
Please refer File to IDOC Scenario..
the 2nd post (Troubleshooting IDOC scenario) from Swarup Sawant , you will get a very good understanding
as lots of reference links are attached with different scenarios.
Regards,
Srinivas

Error 388 while sending or receiving fax, HP Officejet 6260

My unit is always giving this error while sending or receiving a fax. I have tried searching and found out its a line noise problem but when I connected a telephone set to that line it was all clear. No noise during calls.

Hi sixline,
HP has a page on faxing with VoIP services - it has instructions on how to reduce the transmissions speed
http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c00302247
Three other things to check:
1) Is the phone line plugged into "line 1" or the "ext" port on the OfficeJet? I've mixed the two up before. It should be plugged into "line 1"
2) Do you have internet service through DSL or Cable internet? If it's through DSL, you may need a filter on the line. If you get your phone through a Cable provider, then what looks like a regular phone line may actually be a VoIP phone. See page 56 on this document http://h10032.www1.hp.com/ctg/Manual/c00238458.pdf for information on the DSL filter.
3) Are you using the fax on some sort of corporate PBX system? If so, see page 57 on the document from #2.
I do NOT work for HP
I do NOT work for HP

BPM for error handling and acknowledgements

Hi,
Can any one tell me how to handle BPM for error handling and acknowledgements in one scenario.
Please send me the link if you have other wise give me the solution on the same.
Thanks,
Nagesh

Hi !
Just check out these links This might help you.
Usually Application Level Acknowledgement is considered during Sync communication. If you are using RFC, you can make use of Sync communication. So you can handle it without bpm, provided your both sender and receiver are sync interfaces.
To know about Ack-
http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
you can not dirrectly access the content of the ACK, however the BPM shows different behaviours based on the ACK status. E.g. if the ACK contains a success message the BPM will continue in its normal process, if the ACK contains a permanent error, it will either stop or go through an exception branch (provided such a branch has been defined). Have a look at the documentation: http://help.sap.com/saphelp_nw04/helpdata/en/43/65ce41ae343e2be10000000a1553f6/content.htm It doesnt"t state the above mentioned behaviour in detail but says that you need to define an exception branch.
The trickiest part is always to find out, when you will get a transient vs. as permanent error ack. If you are using ACKs with Proxies refer also to this link http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm and this http://help.sap.com/saphelp_nw04/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm
The following link has entire configuration of Receiver XI Adapter (including acknowledgements)
http://help.sap.com/saphelp_nw04/helpdata/en/f4/0a1640a991c742e10000000a1550b0/content.htm
 eror handling in BPM.

1. CCMS monitoring
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/42fb24ff-0a01-0010-d48d-ed27a70205a8
2. BPM Monitoring
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
3. Monitoring XML Messages http://help.sap.com/saphelp_nw04/helpdata/en/41/b715045ffc11d5b3ea0050da403d6a/frameset.htm
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
monitoring BPm https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
Reconciliation of Messages in BPM - /people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
Also see the below BPM related links
check list for BPM https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3bf550d4-0201-0010-b2ae-8569d193124e
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/62/dcef46dae42142911c8f14ca7a7c39/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/de/766840bf0cbf49e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cb/15163ff8519a06e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
Many other examples can be found under the following link at help.sap.com
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
And some weblogs
https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm *****
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
/people/michal.krawczyk2/blog/2005/06/11/xi-how-to-retrieve-messageid-from-a-bpm
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
/people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
/people/michal.krawczyk2/blog/2005/09/04/xi-do-you-realy-enjoy-clicking-and-waiting-while-tracing-bpm-steps *****
/people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements *****
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
/people/kannan.kailas/blog/2005/12/07/posting-multiple-idocs-with-acknowledgement
Also have a look at these seminars,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/daea5871-0701-0010-12aa-c3a0c6d54e02
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/e8515171-0701-0010-be98-e37bec4706cc
Thanks !!!
Regards
Abhishek Agrahari
Questions are welcome here!!
Also mark helpful answers by rewarding points

Error in BPM: "no interface action for sender or receiver found"

hello,
i configured a interface scenario SOAP - PI - Idoc using a BPM sync/async bridge.
i followed the document
when i try to call interface with my soap client i have the follow error in SXMB_MONI:
Timeout condition of pipeline reached
if i check the detail in trace i can found the follow message:
<Trace level="1" type="T">select interface SI_MATREQ_ABS</Trace>
<Trace level="1" type="T">select interface namespace http://pmf/orders</Trace>
<Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
in BPM monitor i cannot see any interesting logs for determine the problem.
I clear cache many time and reimported Integration Process more time.
Have u some suggestion?
thanks in advance

Hi,
Check whether this thread help you or not....
SXMB_MONI: no interface action for sender or receiver found
Regds,
Pinangshuk.

How can I design a BPM with mulitiple IDOC types as sender

Hi Experts,
I am using PI 7.1
I have a senario that I have to design a BPM in such a way that I will get different IDOC types as sender while the receive step has to trigger the the respective IDOC types at run time.
For example: when matmas is the IDOC the BPM instance have to trigger only the respective Abstract interface at runtime.
In my senario I have 5 IDOC TYPES which should pick the related one using a single Abstract Interface in the same design( one BPM ).
Is this possible. Please suggest me how can I do this if possible.
Regards
Shankar.

Hi,
you could work with multiple receive steps that triggering the process.
Similar to the example pattern in SAP Basis BpmPatternSerializeMultipleTrigger
http://help.sap.com/saphelp_nw04/helpdata/en/77/0737133012b24b9d0a12c6df2b1054/frameset.htm
In the fork step you could set the number of required branches to 1 that means only one receiving IDoc is required to leave the fork step.
Regards
Patrick

Idoc Error: Could not find code page for receiving system

hi,
I am facing the following error while processing Idocs.
ERROR: Could not find code page for receiving system
Diagnosis
For the logical destination BWFIN, you want to determine the code page in which the data is sent with RFC. However, this is not currently possible, and the IDoc cannot yet be dispatched.
Can somebody suggest a solution for this. I have verified that the RFC destinations have been created both on the sender and receiver, ports (WE21) have been defined, and partner profiles (WE20) also created. How would I troubleshoot this problem?

Hi,
I did analyse on this issue.It is all because of the Langauge settings in the SM59.This can be done by the BASIS person.The Language field would be empty, but when ever we send the IDoc from the unicode to a non unicode system we have to mention the Langauage used.
If this helps you really award me the points.
~Katty

Error in Sending IDoc to XI

Hi Gurus,
We are not being able to send Idocs from one of our Back-end SAP system. The Idoc status in we05 is successful but it doesn't reach XI. So we checked in SM58 in the Back-end R/3 system and there it shows the error:
No Service For System SAP*** , Client *** in Integration Directory
We tried almost every possible setup
-The System is defined in SLD and has the logical system name.
-The Adapter Specific Identifiers are correct for the corresponding business system in ID
-The RFC destination in R/3 system is defined.
- Read through other similar threads in SDN about the similar problem.
Do anyone have a more definite solution for this particular problem? The other R/3 systems are connected to XI system and all IDocs from those systems are arriving at XI.
Waiting for your valuable advices!
Regards,
Suddha

Hi All,
We had eventually found the solution to this problem we were facing in sending IDoc, though I couldn't manage to update the thread with the solution. I think this would be a very helpful information for those who face similar problems.
Let me describe the scenario first briefly,
We are sending an IDoc (Idoc extension), from SAP system to XI and then send the XML payload as mail attachment to the receiver via receiver mail adapter. Since this is a cross company transaction, hence we have configured the scenario as a B2B in ID, which means we use Parties for both the sender and receiver.
Now in the ID we had done all necessary configurations and used parties and services under Party. For the sender SAP system we assigned a Business System to Sender Partner, configured the Party Alternative Identifiers correctly. The ports were created in IDX1.
On the other hand the SAP system was also configured successfully - including Partner Profile, Distribution List, RFC destinations and ports.
In SLD we created Business System for the SAP system and in ID the Business System under party had the correct logical system name as Adapter Specific Identifiers.
But after all these, the IDoc was not arriving at XI, though in R/3 the status of the IDoc was 03 in we02. When we checked in sm58 in R/3, it showed us the error message that "No Service For System SAP*** , Client *** in Integration Directory".
The cause to this problem was:
We created (assigned from SLD) Business System only under Party (Sender), as this was a B2B scenario, and didn't create (assign) a Business System without Party, as we didn't need one at all in the scenario configuration. And this the reason behind this error. When an Idoc arrives at XI, before the Inbound IDoc adapter converts the IDoc to IDoc XML using IDoc metadata............it checks in Configuarion to see if any Service without Party (Busniess System) is defined for the Sender SAP System and Client (The SNDPOR and MANDT field values from IDoc Control header are taken as the SAP SID and Client). If it finds one it accepts the IDoc and starts the Normalization (Sender Party, Service......in the message header) and IDoc to XML conversion. If it cannot find an Service without Party in ID for sender system, it rejects the Idoc with the error message that we saw in sm58 in backend R/3 system.
In this step the Service under Party doesn't help, because at this point the Inbound IDoc adapter can not deterimine the sender party.
Hence for sending an IDoc from an SAP system to XI, we need to have an Service Without Party in ID, whether or not we require it in our actual Scenario Configuration, which is ofcourse not a case for the Reverse Scenario, ie Sending an IDoc into SAP system from XI.
This is the similar with BC adapter as well. I was already aware about this behaviour of BC adapter from my past experience and this actually helped to troubleshoot this IDoc adapter problem.
This was ofcourse a useful and new learning for me and hope would be helpful to others as well. Let me know if anyone has any doubts on this.
Regards,
Suddha
Edited by: Suddhasatta Guha on Aug 28, 2008 1:03 PM

IDOC - BPM - IDOC Error --no sender or receiver interface definition found

Similar Messages

Maybe you are looking for