ALE with BAPI; No recipient found for message type

We have to send sales activities from an ECC-system to CRM and tried to do this with message type SFADPSA and Idoc SFADPSA01.
When adding this message type to the distribution model (transaction BD64) we got the SAP-message to use a BAPI instead: IF1037SR with method RECEIVEPARTNERSALESACTIVITY. So we did.
To trigger the Idoc, we customized an output type, with transmission medium ALE, program RSNASTED and processing ALE_PROCESSING.
When processing the output type we get an error B1 129: "No recipient found for message type SFADPSA in the ALE model".
Analysing the error I found out following: during processing (RSNASTED, ALE_PROCESSING) function module MMODEL_INT_VALID_GET is called. This FM only looks into table TBD05, in which no entry for message type SFADPSA is found.
However, also function module BMODEL_INT_VALID_GET exist, searching table TBD06.
This table does contain an entry for the above BAPI and method and would not lead to an error message.
Obviously this last FM should be called, but this never happened...
Has anyone a clue?
Do we use the correct processing code?
Another message type to use could be SFADSACTIVITY, but this message type has no Idoc type assigned.

Hello Wolf,
This error message come while determing the distribution channel.
This error come from one of below includes. Can you please put a break point and swich update debugging on and check whether the program is populating reuqired parameters to determine the distribution model. by doing this you can understand what is going wrong....
LBDMOU17
PCHEAF01
PCITEF01
RBDSECOP
RBDSEGLM
if you are not able to check this let us know..
Regards
Naresh

Similar Messages

Too many recipients found for message type in the ALE model

Hello Friends,
Please help me in solving this error. I have a Outbound sales order confirmation ORDRSP .
In the distribution model i have defined the sender receiver and message type clearly...
But in va01 after creating sales order extras ->Output->Hearder --->Edit
Output type-- BA00
medium --ALE
Dispatch time : Send Immediately
I am getting a error -
Too many recipients found for message type ORDRSP in the ALE model
Message no. B1130
Diagnosis
In the ALE distribution customer model several recipient systems for IDOCs with message type ORDRSP and filter object type 'KUNNR' with value '100' have been modeled from this system, but only one recipient system is allowed.
Procedure
Please change the ALE distribution customer model so that it allows only one recipient system for the message from this system.
Please help me in solving this error.
Regards,
jeevan

Hi Jeevan,
In BD64, the said problem occurs, since the message type ORDRSP will be configured to different Logical System.
Since you are creating sales orders & Output type, system doesnt knows, to which Logical system, it has to be sent since the Message type exists more than once.
select Your respective Logical System where the Outbound Sales Order Confirmation ORDRSP has been created.
Under the node ORDRSP, add the filter group for Customer.
Double click the Filter group and add the respective Customer No.s to whom the Order confirmation needs to be sent.
Then create Sales Order Confirmation & Output type. Data will be passed(IDoc) to the respective Customer(where the customer no.) exist in the filter.
Hope it solves your Issues.
Regards,
Anbalagan.

Too many recipients found for message type ORDERS in the ALE model

Hi all ,
please help me to solve this issue .
i done with ale settings .
orders message type is used in 2 different model view for 2 different systems
when i create po it is giving error in output "Too many recipients found for message type ORDERS in the ALE model"
how can i rectify this error.
Thanks

> orders message type is used in 2 different model view for 2 different systems
do both of them carter diffrent needs or is it the same idoc which is being sent to diffrent systems?
if yes, then use a single model view with noth receiver systems defined in it.
if not, i would suggest, copying the standard idoc and create a zidoc and then use different ones for diffrent receivers....
or u can use diff versions of the orders message type...
say orders05 for one.... receiver and orders02 for another one....
hope this helps!!
Cheers!!
Sidharth

ALE settings error "Too many recipients found for message type" urgent

Hi all ,
please help me to solve this issue !!!!!!!!
i done with ale settings .
in the bd64 , orders message type is used in 2 different model view for 2 different systems
when i create po it is giving error in output "Too many recipients found for message type ORDERS in the ALE model"
how can i rectify this error.
Thanks

Hi,
Try to redefine your distribution model to have both receivers of your message type ORDERS in one "model view".
Regards,
Jakub

Too many recipients found for message type (Distribution model)

Hi,
I wanna send Dilvery note using message type DESADV from a SAP system to another non-SAP System.
I have Created port partner profile and distribution model.
But the Problem is the same message type DESADV is used to send Dilvery from SAP System to another SAP Client.
Idoc getting failed and throwing error stating Too many recipients found for message type DESADV in the ALE model .
I am sure we can create the more than one recipients for same message types. I have done it some time back. Any help highly appreciated.
Regards
Raj

This message pops up when SAP can't identify how to distribute the IDoc based on the settings in BD64. Take a look at the settings there, most likely you'll need to add a filter.
The big ALE/EDI/IDoc book suggests that the same IDoc may be distributed to 2 different systems but specific details are not clear. It seems that one system should be configured first (it does mention a need to use a filter) and then somehow menu Edit -> Model View -> Distribute should be used.
I've never done it myself though and have only run into that error when I missed some filter settings in BD64. Hope this helps.

Problem with BPM: no receive step found for message ....

Hello,
I have the follwing problem with a BPM ina PI 7.3 system.
I created a BPM for the following 'process':
We will receive an IDOC from SAP ECC, then call a synchronous webservice and finally send the result back to ECC.
I created my BPM.
Now when I send the IDOC, the interface is triggered but it gets stuck in the queue with message 'No receive step found for message ...'. I get this message when I go to Tx SMQ2 and try to simulate the message
I have already refreshed the CPA cache without result however.
in SXI_CACHE I can find my IP* and the status = '0' ( So i guess this is OK )
I do not use correlations in my BPM.
In my configuration I can find my sender agreement and interface determination towards the service (abstract) which is defined in the receive step of the BPM.
Does anybody have any ideas what can be wrong ?
Thanks,
Erwin
Edited by: Erwin Van Lysebetten on Oct 27, 2011 10:37 AM

Hi Erwin, delete Integration Process in the Directory Integration and import it again.

Error in ALE service 29 Could not determine recipients for message type MAT

Hi Experts,
While transferring the material using ALE am getting error 29 ie 'Error in ALE service' and message is 'Could not determine recipients for message type MATFET'.
Also i ve recieved the materials with the proper status al the end am getting the above error.
Kindly help me out.
Thanks in advance.

Hi ,
Status 29 means " partner profile not found " . Please check if the recieving partner is configured properly in WE20 in sender system.
Also make sure that the Port and RFC definations are also completed. If the IDoc is manually triggered then please make sure that control record parameters of the idoc are properly filled - if we miss the details ( like wrong port given , wrong basic type for message type - or extended message type ) then also the idoc will fail in status 29 even though the partner profile is properly configured .
Since your idoc is getting generated i think no issues with BD64 since already interested recipeints were populated in control record of idoc.
Regards
Vikas Chaudhary

LSMW: ALE/IDOC, getting the Create a partner profile for message type

Hi Gurus,
In my current project, i need to upload the employee data using the ALE/IDOC method with the LSMW
when i'm generating the idoc in the 13th step, its posing the information message stating that:
Create a partner profile for message type 'ZEMP_MSG'
In partner profile i already assigned the message type .
How to solve this issue, <inappropriate urgency removed by moderator>
Thnks&regards,
sree
Edited by: Thomas Zloch on May 13, 2011 9:55 AM

This forum's aim is not only to search for information and ask the members questions, but also to share knowledge. When you have asked a question and found a solution, do share with the rest.

ALE for message type BATMAS

Hello
I am trying to generate IDocs for a copy of the message type BATMAS and have added some custom fields to this new custom message type..
1. I have created BD52 entries for this new custom message . But starngely the IDoc created is for message type BATMAS instead of the new custom message type in WE02. I am executing BD21 for the new custom message type . I have checked BD64 and partner profile settings for the new custom msg type. I have activated change pointers for this new message type in BD50 and BD61.
2. I added a new field MCHA LVORM to the fields in BD52 . But the IDoc is not genearted whenever we change deletion indicator(IDoc).. Its creating the IDocs for changing all the other already existing fields.
I'd appreciate any suggestions/help.
Thanks
V

Hi Ravi;
Just so I understand you, an IDOC was successfully created in ECC and sent to an outbound system. Your outbound system, in this case is PI, which is acting as middleware for your ALE. Now you have an error in PI and you can't get it sent to EREC.
I know people don't like getting questions answered with other questions, but why are you using PI in this scenario? Every ALE scenario I've utilized uses HRMD_ABA directly from ECC to the target system (not with a middleware piece included). In WE20, what would be the harm in changing your receiver port to your actual EREC system? Do you have some kind of business logic being executed in PI converting IDOC field values?
If you think you must use PI, then in sxmb_moni, it would be interesting to know the error message for the IDOC there. However, I think it's entirely likely you don't need to use PI at all and could just use a direct RFC between ECC and EREC.
Good luck,
Chris

MissingResourceException: No localizer class found for message id

I created a Java Portlet (JSR 168) and am adding it to my portal.
For some reason I keep getting the exception below. Any clues why this happens?
I added the portlet to the portal file by drag and drop.
- vineet
No such portlet with URI RSSPortlet_1.
<[ServletContext(id=7865499,name=SomeWebApp,context-path=/SomeWebApp)] Servlet failed with Exceptionjava.util.MissingResourceException: No localizer class found for message id.
 at weblogic.i18ntools.L10nLookup.getLocalizer(L10nLookup.java:230)
 at weblogic.i18ntools.L10nLookup.getLocalizer(L10nLookup.java:182)
 at weblogic.logging.Loggable.getMessage(Loggable.java:141)
 at weblogic.logging.Loggable.getMessage(Loggable.java:164)
 at com.bea.portlet.container.AppContainer.getPortletStub(AppContainer.java:772)
 at com.bea.portlet.container.AppContainer.getPortletInfo(AppContainer.java:309)
 at com.bea.netuix.servlets.controls.portlet.JavaPortlet.getPortletInfo(JavaPortlet.java:1015)
 at com.bea.netuix.servlets.controls.portlet.JavaPortlet.init(JavaPortlet.java:200)
 at com.bea.netuix.nf.ControlLifecycle$5.visit(ControlLifecycle.java:88)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:298)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:308)
 at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:127)
 at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:204)
 at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:153)
 at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:321)
 at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:184)
 at com.bea.netuix.servlets.manager.PortalServlet.doPost(PortalServlet.java:767)
 at com.bea.netuix.servlets.manager.PortalServlet.doGet(PortalServlet.java:671)
 at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:135)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
 at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
 at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
 at com.company.tools.security.PortalLoginFilter.doFilter(PortalLoginFilter.java:107)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
 at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
>

Fyi, I realize this is an old post, but this problem is usually caused by someone removing a portlet from the portlet.xml file, and the desktop still refers to the portlet. 
Use the DomainAdmin tool to remove the offending "RSSPortlet_1" from the contents of your page/book, that should solve this problem. 
Steve

Distibution Model- Outbound parameters for message type could not be found

Hi SRM Gurus,
Have you ever encountered this error while buidling Distribution model in BD64 -
When I try to generate partner profile, I am getting this error-
Outbound parameters for message type BBPCO BBPCO01 could not be created
Partner not found in partner table
This error is occuring for all message types.
Please let me know the solution if anyone has encountered this error before.
Thanks & Regards
Kapil

Hi
Are you geting this error while generate partner profile?
hope your sender and receiver logical system are correct.double check.
VERSION 3
OUTPUT MODE - tRANSFER idoc immediately option
connectivity between both sytems are ok.
did you save modelview ?
now ports automatically created . check we21 ,we20..
check your sm59 rfc destination? what type connection you made ? hope you maynot do mistake. howevercheck itup.
ask basis consultant assistance why ports anot genrated for backend system after you executed
tbd05 - do yo have entry ?
regards
muthu

Not able to send Email in SOA Suite 12c,getting No matching driver found for delivery type = EMAIL

Hi All,
I am getting following Errror whlie Sending Testing Mail from Human Workflow .
No matching driver found for delivery type = EMAIL
I followed all the steps mentioned in blogs.
Steps that I followed--
1,Downloaded Gmail and Imap Certificate.
2.Imported in Keystore
3.Create a Email driver properties.
Than

Did you resolve this? I am running into the same problem. Not sure if it a configuration issue or an issue with 12c (go figure). I have tried both a blank sender address list and explicitly putting the target address in. Notification mode is set to email. I am using the Notification Test under Human Workflow/Notification Managent. Where else could it be trying to match the driver to EMAIL?
exception.type: ERROR
exception.severity: 2
exception.name: Error status received from UMS.
exception.description: Status detail :
Status type : DELIVERY_TO_DRIVER:FAILURE,
Status Content : No matching driver found for delivery type = EMAIL,
Addressed to : EMAIL:[email protected],
UMS Driver : null,
UMS Message Id : dcb01e3ec0a8456856fe8a439e6ecf3f,
Gateway message Id : null,
Status Received at : Mon Jan 12 00:49:27 EST 2015.
exception.fix: Check status details and fix the underlying reason, which caused error.
>

Message no. B1003""Could not determine recipients for message type ACPJMM""

Hi All,
While posting GR in MIGO, an error is showing. I am attaching the error description.
""Could not determine recipients for message type ACPJMM""
Message no. B1003
Diagnosis
An IDoc of message type ACPJMM was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message type or deactivate distribution for these message types.
Yesterday it was not coming and GR was getting posted.. I was doing configurations for CIN and day before yesterday everything was done,all the registers were getting updated. For that I did many customisation in SPRO. I did settings in tax ion goods monement. and in Material master to assign screen sequence for foreign trade data screen. Is any customozation triggerring IDoc? Earlier also this came, that time we got client copy, but the problem is recurring. Its very urgent as we are going to transport SPRO settings to production.
Solutions will be rewarded.
regards
B Shar
Edited by: Ian Wong on Jul 4, 2008 4:48 PM

Hi
If you are not working with ALE & this message comes, then somone has mistakenly activated ALE linkages for IDoc Output in Accounting.
if you want to keep this active & go forward, you need to complete the Distribution model customizng in BD64.
Thanks & Regards
Kishore

Error In MIGO "Could not determine recipients for message type ACPJMM"

Dear all,
At the time of transaction Goods Receipt(MIGO), I am getting the error message "Could not determine recipients for message type ACPJMM".
System Diagnosis is as below
An IDoc of message type ACPJMM was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type
I have check the ALE Settings in we20 and we21
and have assigned the following message types under Logical syste Partner Type
Outbound
ACPJMM
MATMAS
MBGMCR
RSINFO
RSSEND
WHSORD
Inbound
ACPJMM
DEBMAS
FTDABA
FTDACO
FTDACU
INSPECTIONPLAN_CREATE
MATMAS
MBGMCR
RSRQST
WHSCON
I have also created and Assigned a Logical System to the client and have also created a RFC with the same name
I have checked all settings is SALE and they are Fine.
This is a single system
Please help this is really ugrent
Regards
Suhail John

Hi,
Goto table TRWCA (T Code SE30) and deselect all the checked entries.
This should solve your problem.
Regards,
Priyadarshi

Security lending no update types found for prod. type 77B, trans.type 100

Hello
In FTR_CREATE for product type 77B Open-Ended Securities lending I get following error:
No update types found for prod. type 77B, trans. type 100, sec.acct cat.
Message no. TRS0835
how do I solve this?
regards
Arjan
Edited by: Arjan Hogenes on Dec 8, 2009 6:51 PM
I have in customizing in "Update types for position update" for product type 77B, transaction type 100:
Product Type    77B   Open-Ended Securities Lending
Transactn Type 100   Loan
Update Type for Open                      SL1990-
Update Type for Close                     SL1992+
Update Type for Underlying / Exercise     OTC003
Edited by: Arjan Hogenes on Dec 8, 2009 6:55 PM
Edited by: Arjan Hogenes on Dec 8, 2009 6:58 PM

Prasad,
I followed your instructions and changed customization for Update type for Position Update type with standard Update types;
OTC001
OTC002
OTC003
but I still get the same error.
In TRM-Trans Mgr-OTC Derivatives-Transaction Mgt-Update Type-Assign FLows type to Update Types
I have:
6 Derivatives     1990     Securities Lending: Basis Flow     - Outflow     SL1990-     Securities Lending: Basis Flow
6 Derivatives     1991     Sec. Lending: Lending Revenue     + Inflow     SL1991+     Securities Lending: Lending Revenue
6 Derivatives     1992     Sec. Lending: Reverse Posting     + Inflow     SL1992+     Securities Lending: Reverse Posting
6 Derivatives     1993     Securities Lending: Agent Fee     - Outflow     SL1993-     Securities Lending: Agent Fee
6 Derivatives     1994     Sec.Lending: Cash Collateral     + Inflow     SL1994+     Securities Lending: Cash Collateral Inflow
6 Derivatives     1994     Sec.Lending: Cash Collateral     - Outflow     SL1994-     Securities Lending: Cash Collateral Outflow
In TRM-Trans Mgr-Listed Derivatives-Transaction Mgt-Flow Type-Assign FLows type to Transaction Type
I have
77B     Open-Ended Securities Lending     100     Loan     1990
77B     Open-Ended Securities Lending     100     Loan     1991
77B     Open-Ended Securities Lending     100     Loan     1992
77B     Open-Ended Securities Lending     100     Loan     1993
77B     Open-Ended Securities Lending     100     Loan     1994
77B     Open-Ended Securities Lending     100     Loan     1995
Any other suggestion for the error "No update types found for prod. type 77B, trans. type 100, sec.acct cat.
Message no. TRS0835"?
many thanks in advance. I Look forward to your answer!
kr
Arjan

ALE with BAPI; No recipient found for message type

Similar Messages

Maybe you are looking for