Message Type problem - ALE

Hello All,
I have a ALE requirement to transfer material.
This I am doing in development client i.e. same server in different clients.
After this is successful I have to do it with different servers.
In SALE all the settings are complete. Remote login is also complete.
Even partner rofile is also generated.
But when I say Distribute model view it is giving me following error :
<b>Model view MV01 has not been updated                   
Rreason: Distribution model is currently being processed</b>
Kindly suggest why this error is comming.
Dilip

Hello,
       The senario is like this in same server one client is having all data & other client is just a client copy without data only config setting.
         I have created new model view & tried but getting same error.
When I say generate IT IS SAYING
<b>
System LOG210 as a partner type already exists                   
System LOG505 as a partner type already exists                   
Port A000000018 with RFC destination LOG210 already exists       
Outbound parameters for message type MATMAS MATMAS05 already exist
Outbound parameters for message type SYNCH SYNCHRON already exist
</b>
Dilip

Similar Messages

  • Inbound IDOC error :51 Passed with out Message Type to ALE Layer

    Hi,
    I am struct wtih the inbound IDOC scenario ..XI able to send IDOC but at ECC side it is in 51 red status and the error message is
    "IDOC passed without Message type to ALE Layer"
    Do I need to pass these segment values in Message Mapping? I didnt mapped any MESTYP,SNDPOR,SNDPRT and so on.. disabled these fields...
    Could any one light on this issue?
    Thanks
    Rajeev

    >
    rajeev raj wrote:
    > Hi,
    >
    > I am passing values in MM as below:
    >
    > <?xml version="1.0" encoding="UTF-8"?>
    > <ZPORDCR01>
    > <IDOC BEGIN="Constant">
    > <EDI_DC40 SEMENT="Constant">
    > <TABNAM>Constant</TABNAM>
    > <DIRECT>Constant</DIRECT>
    > <IDOCTYP>ZOrders</IDOCTYP>
    > <CIMTYP>Constant</CIMTYP>
    > <MESTYP>Z_Orders</MESTYP>
    > <SNDPOR>B0009</SNDPOR>
    > <SNDPRT>LS</SNDPRT>
    > <SNDPFC>LS</SNDPFC>
    > <SNDPRN>PD_100</SNDPRN>
    > <RCVPOR>DEV</RCVPOR>
    > <RCVPRT>LS</RCVPRT>
    > <RCVPRN>Dev10</RCVPRN>
    > <REFINT>GB</REFINT>
    > <REFGRP>MTI</REFGRP>
    > <REFMES></REFMES>
    > <ARCKEY>20090909</ARCKEY>
    > </EDI_DC40>
    > <E1PORDCR SEGMENT="Constant">
    >
    > I am forwarding these values in MM... IDOC is successfully reaching in ECC but with 51 error in red... Logical system, post and message types are avaliable in Control record of the IDOC which received wiht errors in ECC.
    >
    > Thnaks
    > Rajeev
    Fill the TABNAME as EDI_DC40 and Direct as 2 (represents the inbound direction) and resend the idoc and check
    Rajesh

  • Tcode to send custom data using custom message type in ALE

    I have ceated custom message type and i want to send data to say system B.I wanted to know Tcode to send custom data using custom message type in ALE.
      for example:
    material data...message type = matmas....tcode = BD10.
    like this.
      i hope you have got my question.
    plz guide me?
       regards
         mallikarjun mangalore

    Hi,
    Sending data through ALE is not a single-step process. Take a look at http://www.sapgenie.com/ale/. The paper at http://www.sapgenie.com/sapgenie/docs/ale_whitepaper.doc is a wonderful resource for the ALE process.
    Regards

  • Need of message type in ALE-IDOC

    Hi,
    Please tell me need of message type  in ALE_IDOC and its functioning.Also why it is required.Let me know its exact role.
    Thanks.

    Hi,
    Message types (required for sending the data across participating systems)relate to the structure of the data called an IDOC (Intermediate Document).Message types provide the format of the data, which can be exchanged betweenSAP and non-SAP systems. ALE supports over 200 message types in R/3.
    Also check the below links
    http://www.thespot4sap.com/Articles/SAP_ALE_Introduction.asp
    http://www.sap-img.com/basis/types-of-idocs-use-in-ale-configuration.htm
    Thank U,
    Jay....

  • Message types for ALE distribution

    Hi,
    I am working on SRM 7.0. I need to copy the org structure from one client to another. For that I am using the ALE distribution model. Can anyone please let me know all the message types reqired for transferring the org structure.
    Thanks,
    Bhakti

    Hi Masa,
    Thanks alot for your help. The document is quite helpful if the org structure had to be mapped from HR. But, the org structure is to be mapped from another existing ERP. Kindly suggest if there is any document for such a transfer.
    Also, I have found another way to transport the org structure. Hopefully that should work. Once I am done testing for the same, I will notify.
    Thanks,
    Bhakti

  • Message type to ALE T880

    Hi All,
    I have a requirement to ALE the table T880 changes (Global Company Data (for KONS Ledger). Can anybody help me identify if there is any standard message type to handle this requirement. I tried creating a custom view and sending idocs. The data is not getting populated correctly in target systems. The fields are getting shifted by one segment when populating in the target systems eg- Name 1 is being populated to Name 2 field and the same for all the following fields.
    Any help is much appreciated.
    Regards,
    Chandra Kumar
    Edited by: Chandra Meda on Sep 3, 2009 11:00 AM

    >
    Chandra Meda wrote:
    > ...I tried creating a custom view and sending idocs...
    I don't understand what you exactly did (what message type did you use?), but I feel that you tried to update kind of directly (even though you used idoc technology) the table in the target system, you should neither do that, nor try (instead, use BDC, etc., and all other technologies you probably know, amongst them is also idoc of course if there is a standard one ).

  • Can we assign same  basic type to  different message type in ALE

    Hi Expert
       can we assign same idoc type to different message type?

    Hi,
    Yes you can assign the one idoc type to multiple message type. Message type nothing but it represents the kind of data we transfer.But idoc type is the format in which we transfer data. As an example in Messager types "ORDERS" and "ORDRSP"  both indicates the order related data, and in both case idoc type can be ORDERS01, ORDERS02.............
    Thanks,
    Asit Purbey.
    Edited by: Asit Purbey on Oct 12, 2009 3:07 PM

  • Regarding Message Type in ALE

    hi guys,
    i was involved in Master data distribution using Message Types MATMAS, DEBMAS and CREMAS but never created a customer specific Message Type that is why, i just want to know in what cases do we have to create our own message type's using we31, we30 and we81 and we82.
    can any one out here help me out by sharing giving some real time scenario's in what cases do we exactly have to create our own message type.
    thanks
    Pavan

    Hi Pavan,
    There is no hard and fast rule that you use standard or custom message types...
    SAP has provided messages for almost all scenarios. If you don't have enough fields in standard messgae type, you can enhance it to accumulate your requirement.
    But if the organization has completetly custom defined system (involving many Z-tables) , we create custom message types...
    As far as my knowledge, we should try to go ahead with standard message types by suppressing unnecessary segments and enhancing existing segments just to avoid Z-objects.
    Regards,
    Audy

  • Problem in Output Message types in PO

    Hi Experts,
    I created a PO of type (ZRTS) and i assigend message type as ALE its working fine and idoc genereted.
    but when i am usign some other PO type its not working .
    Here the Partner is same (VN-Vendor)
    Pls help me ..

    If you have created conditin record for all the document type in MN04 then it should work becuase doc type has nothing to do for printing config.
    this is basically a condition record.
    check your condition record

  • To know the programme for message type

    Hi experts,
    This is Venkat, I want to know how to know the programme for master type message types in ALE/ IDOC like for customer master -
    SAPLVV01
    Thanks in advance
    Regds
    Venkat

    Any body   have any solution ?
    Message was edited by:
            agrud agrud

  • When to add message type to distribution model

    hi
    i am bit confused on when to add a custom/std message type to distribution model. what are the conditions. is that always necessary to add the message type to distribution model.
    thanks

    [http://sap.ittoolbox.com/groups/technical-functional/sap-interfaces/add-message-type-in-ale-distribution-model-1192885]
    [http://docs.sun.com/app/docs/doc/820-5014/ggcpd?a=view]
    [http://publib.boulder.ibm.com/infocenter/wtxdoc/v8r2m0/index.jsp?topic=/com.ibm.websphere.dtx.packsapxi.doc/tasks/t_pack_sapxi_Create_a_Destination_Model_BD64.htm]

  • ALE distribution model - one message type to more than one recipient

    Hello colleagues,
    currently I'm working on an integration project between one SAP system and an e-shop system. The communication is established through IDOCs ( both inbound and outbound ). There is another system ( POS ) which is already integrated
    with SAP via IDOCs also.
       Now I'm facing the following problem regarding distribution of transactional IDOCs ( orders, deliveries, etc. ): when assigning one message type ( for example DESADV - Delivery: Shipping notification ) to more than one external system in ALE distribution model I receive a message alerting that one message type can be send to only one recipient.
    The distribution model is as follows:
    Model Views
       SAP to POS
          SAPDEV ( the SAP system )
             POS ( the external POS system )
                DESADV
       SAP to E-SHOP
          SAPDEV ( the SAP system )
             E-SHOP ( the external e-shop system )
                DESADV
       Well, the system message is clear and I did the obvious: create a complete copy to the original message type and than assign it to the E-SHOP system ( the original message type is already used in integration between SAP and POS ).
    As you can see I have found a workaround already but I think that it comes natural to SAP to communicate with other systems and to exchange same kind of documents to those systems and I can't believe that there isn't a standard solution for situation like this.
    FYI I'm working on SAP ECC 6.0
    Thanks in advance.
    Wish you nice day and successful week ,
    Vladimir

    I believe when ePrint server has received the email, it made the necessary settings and configured the job for printing and then it went for "Reply All" option. So here it cannot send the print job to your personal email ID and the error came up.
    The only option I can think of is add the printer email ID to your email contact list and give it a name like MyPrinter so you can remember easily , just like email contacts are added in Outlook.
    Mark this post as answered so that others can find it useful.
    Say "Thanks" by clicking the Kudos Star in the post that helped you.
    Please mark the post that solves your problem as "Accepted Solution"

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

  • ALE - error in custom  message type creation

    HAI friends,
    I am new to ALE IDOC, i am creating custom message type for custom table . i created segment, idoc, message type and executed  outbound program . in outbound client, status is dispatch ok. so problem in outbound.
    my problem is in inbound . i created one function module idoc_input_zmsg. In test tool for idoc processing ie. TCODE WE19, i clicked my segment and then i clicked the inbound function module button . In function module text box my own function module idoc_input_zmsg is available. but when i click ok button, i am getting the following error.
    "INTERFACE FOR FUNCTION IDOC_INPUT_ZMSG IS INCORRECT".
    PLS HELP ME . THANKS IN ADVANCE.
    WITH REGARDS,
    SENTHIL KUMAR.R

    All the IDOC processings FMs should have similar interface like this.
    *"  IMPORTING
    *"     VALUE(INPUT_METHOD) LIKE  BDWFAP_PAR-INPUTMETHD
    *"     VALUE(MASS_PROCESSING) LIKE  BDWFAP_PAR-MASS_PROC
    *"  EXPORTING
    *"     VALUE(WORKFLOW_RESULT) LIKE  BDWFAP_PAR-RESULT
    *"     VALUE(APPLICATION_VARIABLE) LIKE  BDWFAP_PAR-APPL_VAR
    *"     VALUE(IN_UPDATE_TASK) LIKE  BDWFAP_PAR-UPDATETASK
    *"     VALUE(CALL_TRANSACTION_DONE) LIKE  BDWFAP_PAR-CALLTRANS
    *"  TABLES
    *"      IDOC_CONTRL STRUCTURE  EDIDC
    *"      IDOC_DATA STRUCTURE  EDIDD
    *"      IDOC_STATUS STRUCTURE  BDIDOCSTAT
    *"      RETURN_VARIABLES STRUCTURE  BDWFRETVAR
    *"      SERIALIZATION_INFO STRUCTURE  BDI_SER
    *"  EXCEPTIONS
    *"      WRONG_FUNCTION_CALLED
    Check if you have different one. Even if the name of variables is not as above you may get the error message .
    Cheers

Maybe you are looking for