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

Similar Messages

  • 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.

  • 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 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.

  • 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

  • Could not determine recipients for message type HRMD_B

    Hi,
    I am getting below Error in SRM when transferring Org Structure data from HCM system to SRM system in a Idoc. I am using Message type HRMD_ABA and not HRMD_B. I didn't maintain Distribution model for HRMD_B. But in my IDOC status I am seeing below error message for Message type HRMD_ABA Inbound to SRM.
    Only I am seeing HRMD_B message type in transactions WE81 and WE82.
    Any idea? I appreciate your help.
    Could not determine recipients for message type HRMD_B
    Message no. B1003
    Diagnosis
    An IDoc of message type HRMD_B 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.
    Thanks,
    Shears

    Hi Shears
    Did you find soulution to your issue ??
    thanks
    Anup

  • 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

  • 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

  • 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.

  • 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

  • Could not determine recipients for message type BUPA_INBOUND_MAIN_SAVE_M

    We are upgrading CRM from 4.0 to 7.0
    While synchronizing a business partner from CRM to ECC, the IDOC control Data section shows no information on the "Receiver Information" Section.It also provides error as "Could not determine recipients for message type BUPA_INBOUND_MAIN_SAVE_M" with error No 29, Outbound Error in ALE.
    The Message Type (BUPA_INBOUND_MAIN_SAVE_M) and the Basic Type (BUPA_INBOUND_MAIN_SAVE_M03) was not used in the CRM 4.0 and not sure the reason it apprears now in the IDOC.
    The relevant BDOC is not created/shown in transaction SMW01.
    We have verified WE20,21, BD64 in ECC
    Any advice is greatly appreciated.
    Regards
    Dhina

    Hi,
    Please check below note if it helpful to you in resolving the issue.
    Note 1447734 - Enhancement of message type BUPA_INBOUND_MAIN_SAVE_M
    Thanks,
    George

  • USER EXIT for Message Type PCROLL

    Hello Gurus ,
    My requirement is that i need to convert few fields for Message Type PCROLL (Basic type GLDCMT01)  before sending it to other system by ALE . Can somebody help me out which user exit should be used .
    Many thanks for your help in advance .
    Regards,
    NK

    For future reference in case anyone is trying to do this, we were not able to find a suitable user exit to enhance BENEFIT3 IDoc, so we put in an OSS note and received the following response:
    "...currently there is no user exit/Badi in SAP Benefits Administration
    to enhance IDoc BENEFIT3. Such functionality is indeed missing in the
    system, which means that you will need to submit a development
    request to enhance the system in this respect in a future release."
    Anke

  • Object type not maintained for message type

    Hi,
    I am working on chnage pointers for Vendor classification data. when I execute the program RBDMIDOC (BD21) I get the error Object type LIFNR not maintained for Message type.
    If anyone has worked on change pointers, please guide me in solving this error.
    Thanks
    Hari

    Hi
    Which msg type u r using there.
    Regads,
    Prasad.

Maybe you are looking for