Error: 0 communication IDoc(s) generated for message type

what is this??..wher i need to screw this error.

Hi Priyank,
Just cross check with this weblog:
ALE configuration for pushing idocs from SAP to XI
Regards,
Sachin

Similar Messages

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

Error - Could not determine recipients for message type ACP JMM

Hi Guru's
I am facing a problem while doing goods receipt(migo), "Could not determine recipients for message type ACPJMM".
Right answer will be rewarded
Regards

hi
If you want to deactivate this goto SM30, enter the table TRWCA, deactivate the component
RWEX - Idoc Output, External Accounting.
this should solve your problem.
refer following links
Message type ACPJMM
Message no. B1003""Could not determine recipients for message type ACPJMM""
MIGO and MIRO Problum
regards
kunal
Edited by: kunal ingale on Sep 2, 2008 11:46 AM

IDoc parallel posting for message type of DESADV

The DESADV (Delivery Advice) logic is complex and it takes long time than expected. We want to improve its performance by posting DESADV IDocs in parallel.
Currently, the "Input type" of DESADV's function module is 1, which means parallel run is not enabled. (In tcode BD51). In addition, DESADV is configed as "Immediately" instead of "collected run". We will trigger DESADV every 30 mins, about 500-1000 IDocs will be created automatically and then be posted.
I want to know:
Is it possible to enable DESADV IDocs posting in parallel, how?
Dialog or background is recommended, especially from workload/performance point of view?
Any other concern? such as will data duplicated posting or data lose?
In BD20 (or program RBDAPP01), I noticed there was "Parallel Proc." option which can be selected. Can I just simply change the message type to "collected run" and schedule another background to post those IDocs in parallel?
Any comments is appreciated.
TIA
James

no answer

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

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.

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

Error MSG : Create a partner profile for message type 'MATMAS'

Getting Error MSG : Create a partner profile for message type 'MATMAS'
While running LSMW Idoc generation process

See the below link and it has all screen shots how to configure ALE like partner profile,logical systems,RFC
http://searchsap.techtarget.com/general/0,295582,sid21_gci1130337,00.html

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.

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

Can not generate one xsd file for message type in xi

Dear Experts.
I am not able to generate one XSD file from message type from XI 3.0, When i select message type and go to XSD tab then click on export xsd to file, it is generating two xsd files MainSchema.xsd, Schema1.xsd into one zip file, but i need only one xsd file to import it into MDM.
Could you please help
Thanks and Regards.
Sravya.
The following are the two files. MainSchema.xsd, Schema1.xsd .

Hi Harsha,
Thanks lot for the immediate response. Appreciate it.
Now I am able to generate the one xsd with your inputs , but i am not able to load it into mdm with out any changes in the generated XSD from Message Type. the below is only the original root tag, where modification required.
Original Element : MDM_CUST_MASTER_FILE_REQUEST_MT
==============
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:abc.com:MDM_Customer_Master_ECC" targetNamespace="urn:abc.com:MDM_Customer_Master_ECC">
<xsd:element name="MDM_CUST_MASTER_FILE_REQUEST_MT" type="MDM_CUST_MASTER_FILE_REQUEST_DT" />
etc.
Case :.When i modify the above element as below with out xmlns, targetNamespace
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="MDM_CUST_MASTER_FILE_REQUEST_MT" type="MDM_CUST_MASTER_FILE_REQUEST_DT" />
I can import xsd into mdm with the above modification.
The generated XML out put File from mdm is having message type tag like below
?xml version="1.0" encoding="UTF-8"?>
<MDM_CUST_MASTER_FILE_REQUEST_MT>
<CUSTOMER> </customer> ...
note: no namespace for message type
Result:
1.When i send this xml file into XI it is failing in message mapping because it doesn't have namespace attached to it and failing in message mapping.
Finally i need your help to generate the xsd or data file like below to avoid mapping problem in xi.
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MDM_CUST_MASTER_FILE_REQUEST_MT xmlns:ns0=urn:abc.com:MDM_Customer_Master_ECC>
Appreciate your help.
Thanks and Regards.
Sravya.

1 request Idocs created for message type MATMAS

Hi Experts
I have done necessary config.
I have attempted BD10 and BD11.
I have got message that "1 request Idocs created for message type MATMAS"
But iam unable to find the material in target system.
Please suggest what need to be done.
regards
ramSiva

Marias,
And in PI, after having changed the password (why not), have you unlock this user account ? in SU01 of PI, you have a lock button.
if you did it, and changed also the password, as explained, you have perhaps another (or several) program like a RFC destination which uses another password, and so after some exchanges... with a bad/old password, you have your message "too many...", and then the user is again locked...
If you change the password in PI, you should change it in all application which uses this user. I hope you have not the same user from ECC to PI, than from a third-party to PI...
that's why: the use of such technical users have to be referenced in a doc. By this way, if password has to modifiy, we know where we have to update it (mainly in different RFC destination).
Mickael
Edited by: Mickael Huchet on Dec 5, 2011 5:33 PM

Create a partner profile for message type - 'CRMXIF_ORDER_SAVE_M'

Hi
I am trying to create IDOC generateion through LSMW.
i AM GETTING THE MESSAGEcreate a partner profile for message type - 'CRMXIF_ORDER_SAVE_M'
How do I create this profile??????

Hi,
Execute transaction BD64.
Identify you distribution Model,
Select the leaf node, and from menu select
Environment->Generate Partner Profile
Here in you specify 'Output mode' and 'Processing Mode'.
Click on Execute.
Check if any error occurs (Marked with Red color).
Try creating the IDOCs
Best Regards,
Pratik Patel
Reward with points if it is of any help to you!

ALE Distribution for Message Type FIDCC2

Dear all,
I would like to confirm my steps below in setting up the ALE distribution of message type FIDCC2, to ensure that I did not do anyhting that impact other company code that already live in the system :-
1. Use tcode OB87 to add the Global Company Code, XBJ01.
2. Use tcode OBV7 to link a dummy (non-existence in sending system)
Chart of Account to the Global Company code XBJ01.
3. Use tcode OBB5 to assign the Global Company Code, XBJ01, setup in step 1. to the an existing company code BJ01.
4. Use tcode BD64 to setup a distribution with message type FIDCC2, and
filter with value XBJ01.
5. Create an FI document using tcode FB01 with company code BJ01.
6. IDOC is created successfully with message type FIDCC2.
Is there above steps correct? As there are times I receive an error message when trying to do a PGI with company code other than BJ01 "F1302 No cross-system company code is defined for company code TR01".
Another question is, with setting up of FIDCC2 with ALE distribution, any transaction in SAP that will generate a FI document will have IDOC created, right?
Thank you.
Best Regards
Chee Hean

I don't know if you still have this problem but my team and I faced a similar issue in production. Due to a project we're handling, a tool that we are executing requested us to create a Distribution Model based on FIDCC2. This stuck hundreds of thousands of FI Document. Actually, for any FI document the system generated an FIDCC2 and it's not possible to reuse those IDocs because the FIDCC2 Message Type has a structure completely different from FIDCMT (the original message that the system should generate). We identified all the IDoc that should be generated and re-create the Idocs in the target system and the Idocs we posted correctly. We change the FIDCC2 IDocs status to 62 or 32 (depending if inbound system or outbound system). I recommend to investigate about this message type before use it. This Message Type is stronger than any other message type so it must be filter perfectly otherwise, for sure, problems will appear.
Regards,
Hugo

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

Error: 0 communication IDoc(s) generated for message type

Similar Messages

Maybe you are looking for