ALE/Idocs Distribution Model

Hi
I am facing one problem in distribution model. Im trying to send idocs from one system to another. The distribution model has been created and been distributed to the other system. so no error comes in the source system. Even the idocs are generated without error.
Now in the receiving system,
1) after the distribution model is created in this system by distribution option from the source system and when i try to generate the partner profile in this system. It gives the error that " No messages have been defined for the selection conditions in the model". Though everything is created here.
2) the idocs reaches in this system but in error state. Again the error says partner not found.
Now am not able to understand how to rectify this problem. when the model is distributed why this partner is not being created automatically.
can anybody help???
regds
sanjeev

This is the error that comes when I run the FM (FM is active) contrary to the error:
Runtime Errors         CALL_FUNCTION_NOT_ACTIVE
Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          20.11.2007 12:13:39
Short text
     The function module is not active or contains no code.
What happened?
     The function module "ZIDOC_INPUT_ZADR_MESSAGETYPE" is called, but
     cannot be found in its function group.
     Error in the ABAP Application Program
     The current ABAP program "ZIDOC_INPUT_ZADR_MESSAGETYPE==FT" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
      not caught in
     procedure "FUNCTION_CALL" "(FORM)", nor was it propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The program "ZIDOC_INPUT_ZADR_MESSAGETYPE==FT" contains the CALL FUNCTION
      statement.
     The name of the function module to be called is "ZIDOC_INPUT_ZADR_MESSAGETYPE".
   but "ZIDOC_INPUT_ZADR_MESSAGETYPE" cannot be found in its function group.
   Possible reasons:
   a) The function module "ZIDOC_INPUT_ZADR_MESSAGETYPE" has not been activated.
    Therefore,
      it cannot be found at runtime.
   b) The Function Library contains an incorrect entry for
    "ZIDOC_INPUT_ZADR_MESSAGETYPE".
   c) The function module contains no code, even FUNCTION ... ENDFUNCTION
      is missing.
Missing RAISING Clause in Interface
    Program                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Include                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Row                                     69
    Module type                             (FORM)
    Module Name                             FUNCTION_CALL
Trigger Location of Exception
    Program                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Include                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Row                                     93
    Module type                             (FORM)
    Module Name                             FUNCTION_CALL
Source Code Extract
Line  SourceCde
   63 *
   64 DATA: OTHERS(1).
   65 *
   66 FORM EXISTENCE_CHECK CHANGING VARIA.
   67   VARIA = 1.
   68 ENDFORM.
   69 FORM FUNCTION_CALL.
   70   CLEAR %_OWORKFLOW_RESULT.
   71   CLEAR %_OAPPLICATION_VARIABLE.
   72   CLEAR %_OIN_UPDATE_TASK.
   73   CLEAR %_OCALL_TRANSACTION_DONE.
   74   CLEAR %_OIDOC_CONTRL.
   75 %_OIDOC_CONTRL = %_IIDOC_CONTRL.
   76   CLEAR %_OIDOC_DATA.
   77 %_OIDOC_DATA = %_IIDOC_DATA.
   78   CLEAR %_OIDOC_STATUS.
   79 %_OIDOC_STATUS = %_IIDOC_STATUS.
   80   CLEAR %_ORETURN_VARIABLES.
   81 %_ORETURN_VARIABLES = %_IRETURN_VARIABLES.
   82   CLEAR %_OSERIALIZATION_INFO.
   83 %_OSERIALIZATION_INFO = %_ISERIALIZATION_INFO.
   84 *  TRANSAKTION = 'Repo', PROGRAM = REPORT
   85   IF ATRA = '1'.
   86     SET RUN TIME ANALYZER ON %_INTERNAL.
   87   ENDIF.
   88 IF DESTI IS INITIAL.
   89 IF DEBUG = '1'. BREAK-POINT AT NEXT APPLICATION STATEMENT.
   90 ENDIF.
   91 DEBUG = SPACE.
   92 GET RUN TIME FIELD TIME1.
>>>>> CALL FUNCTION 'ZIDOC_INPUT_ZADR_MESSAGETYPE'
   94 EXPORTING
   95 INPUT_METHOD = %_IINPUT_METHOD
   96 MASS_PROCESSING = %_IMASS_PROCESSING
   97 IMPORTING
   98 WORKFLOW_RESULT = %_OWORKFLOW_RESULT
   99 APPLICATION_VARIABLE = %_OAPPLICATION_VARIABLE
  100 IN_UPDATE_TASK = %_OIN_UPDATE_TASK
  101 CALL_TRANSACTION_DONE = %_OCALL_TRANSACTION_DONE
  102 CHANGING
  103 IDOC_CONTRL = %_OIDOC_CONTRL
  104 IDOC_DATA = %_OIDOC_DATA
  105 IDOC_STATUS = %_OIDOC_STATUS
  106 RETURN_VARIABLES = %_ORETURN_VARIABLES
  107 SERIALIZATION_INFO = %_OSERIALIZATION_INFO
  108 EXCEPTIONS
  109 WRONG_FUNCTION_CALLED = 001
  110 ERROR_MESSAGE = 002
  111 OTHERS = 003.
  112   IF ATRA = '1'.

Similar Messages

  • IDOCs Distribution Model: filter whitout Filter group

    Hi guys!
    In my IDOCs distribution model of IDOCs with Message Type "Z", when i try to add a Filter, in the popup dialog to enter the Filter group i canot see nothing...only a line with a "Dependent on class membership:  Requires classes to be defined in the sending system"
    but not show the expected fields like  Sales organization, or  the Account group
    ¿this is a custonizing problem?
    Best Regards,
    Antonio

    Hi,
    First, create ALE Filter objects via BD95 (if they do not exist yet)
    Secondly, assign ALE Filter objects to your message type for the appropriate segment: BD59
    Then, run bd64 ...
    Regards,
    Jakub

  • Specific IDoc + Distribution Model = pb of filter

    Hi,
    I created a Message Type "ZHRMD_A" and an extension "ZEXT", and I use the standard IDoc type HRMD_A06. Thus my Idoc is: <b>ZRMD_A</b>.HRMD_A06.ZEXT
    All work fine: my ECC send correctly this idoc with the good values...
    But my problem is inside the <b>Distribution Model</b> (BD64): I haven't the line "Data filter active" under my Message Type ZHRMD_A, so <b>I cannot add filter</b> !
    Can I add filter on a specific Message Type?
    if yes, how?
    any idea is welcome.
    Regards
    Mickael

    Hi,
    u can use the tcode- BD56 for segment filtering.Also check for BD95.
    Regards,
    Nagaraj
    Message was edited by:
            nagaraj kumar nishtala

  • Error in IDOC Distribution Model

    HI all ;
    Please Help me in this Issue!!
    am  working with standard IDOC  Using MATMAS (Material Master Transfer)
    LS_800 - Outbound.
    LR_810 - Inbound.
    --> BD54.
    --> SCC4.
    -->SM59.
    -->WE21.
    -->WE20.
    --> WE20 ( in inbound side) Clear Up to this level.
    After that the Problem in Distributing the Model,,,,
    In Bd64 t-code Distribution Model.
    while Generating the Partner Profiles in BD64 ;
    its giving the blank message like below.
    No message has been defined for the selection conditions in the model.
    when we distribute(in BD64) 2 Errors (red) Like Below;
    RFC destination for Syncronous Communication (Message type SYNCH)
    Partner Profile LS LR_810 SYNCH does Not Exits.
    Generate Partner Profile.
    or Specify outbound partner Profile for message type SYNCH
    RFC destination for Syncronous Communication (Message type SYNCH)
    Partner Profile LS LS_810 SYNCH does Not Exits
    Generate Partner Profile.
    or Specify outbound partner Profile for message type SYNCH
    Thannks;
    Upender.

    In Bd64 t-code Distribution Model.
    create the model view ,
    add message type Matmas to it.
    -> select the model view
    ->environment-> generate partner profiles
    In Partner Profiles u hv to maintain the Outbound parameters in Both LS_800 &
    LR_810 .
    in receiver port, double click & make sure that the rfc destination assigned connects successfully..
    Regards.

  • Inbound idoc- distribution model

    Hi,
        Is it mandatory to create distribution model for inbound idoc processing?

    Hi all,
            Mine is inbound scenario.
            Sender is XI system
            Receiver is R/3 system.
            Do i need to maintain distribution model for this?
    1.As per my knowledge, distribution model is only created in outbound scenario? In inbound scenario why distribution model is not created?
    2.On the outbound side, after generating partner profiles we get SYNCH SYNCHRON in outbound partner profile. My question is there any setting to generate partner profiles on inbound side also?
    or else SYNCH SYNCHRON will be for only outboud?
    Please clarify........

  • ALE : Error -- Distribution model is currently being processed

    Dear all,
    I m getting following error during distribute model view....
    Model view MODEL_VIEW has not been updated
    Rreason: Distribution model is currently being processed.
    Thanks in Advance.

    Hi,
    When i genrating partner profile following message i get.
    Partner
    System ERP100                             System ERP100 as a partner type already exists
    System ERP400                             System ERP400 as a partner type already exists
    Port
    System ERP400                             Port A000000017 with RFC destination ERP400 already exists
    Outb. Parameters
    System ERP400                             Outbound parameters for message type MATMAS MATMAS05 already exist
                                               Outbound parameters for message type SYNCH SYNCHRON already exist
    Thanks

  • Idoc : distribution model

    Dear all,
    I m getting following error during distribute model view....
    Model view MODEL1 has not been updated
    Rreason: Distribution model is currently being processed.
    Please help me

    HI,
    The distrobution model is being used by some other application, so please create a new distribution model and try.
    Regards
    Sathish

  • Filters in Idoc distribution Model

    Hi All,
    We are using message type: HRMD_A to distribute HR master data changes to middleware system. Now my requirement is that i should send changes pertaining to US employees alone.
    Do i need to create filter group for  IT0001 in BD64 where i need to maintain set of personnel areas assigned to country grouping: 10 - US. or any other approach. Please let me know. Thanks in advance.

    Hi,
    try to define filters in BD95 tcode and then assign filter to message type in BD59 tcode , then configure the filter in BD64 and then distribute.. see if it works.
    Regards,
    Nagaraj

  • Upgrade impact on ALE, IDOC, RFC & XI

    Hi all
    We are having SAP R/3 4.6c and planning to upgrade ECC 6.0. Please tell me what are impacts on ALE, IDOC, RFC & XI integrations.
    Thanks in Advance.
    Raju

    During Upgrade...
    ALE : ALE Customer Distribution Model ajustments due to changes in underlying structures and fields in Idoc Segments
    We need to adjust the CDM as to adopt these to new ECC6.0 enviroment.
    IDOC : Many of the new IDOCS are not released by SAP hence it happens that these IDOCs get stucked in ALE Communication layer and hence we need to see that IDOC's in use or to be used are released by SAP.
    SAP supports these release issues ...
    Also check the Message Control Settings which needs to be checked and verified during upgrade..
    Interface Mappings : - IDOC to Non SAP systems..Proper rights access should be checked...
    Authorisations, Access rights for Directories ...
    These are the main areas which you should look upon and rest of the things will be known to you once your Business Process testing will start
    Thanks and Regards
    Pushkar Joshi

  • R/3 to XI (Idoc to File): Do we need to maintain distribution model in R/3?

    Hi All,
    I have a very basic question regarding Distribution model.
    My scenario is IDOC-->File ( SAP R/3 --> XI). So all I am trying to do is send the IDOC frrom R/3 to XI. ( Within XI I am going to do an FTP to the 3rd party file server)
    I have created a distribution model, but was wondering if I really need to create one as message is going from R/3 to XI and not from R/3 to another R/3.
    Please help let me know If I need to distribute this model to XI or to SAP production sytem or I do not need to duistribute at all for this scenario.
    Thanks
    Shirin

    Hi,
      if you create partner profiles and port via t.code.
      i hope, it's not required to maintain Distribution model.
      please check the below points.
    Configuration Steps for Idoc to File Scenario.
    This is complete step by step document for configuring the idoc to file scenario along with ALE Settings
    To Configure the IDOC TO FILE SCENARIO, SETTINGS IN SAP-XI
    STEP 1:ALE SETTINGS IN SAP-XI
    We need to do the following settings in XI
    1) Create an RFC Destination to the Sending System in transaction code (SM59)
    a) Choose create
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#
    e) Enter the Gateway host as same details above SID/URL
    f) Gateway service is 3300+system number#
    g) In the Logon /Security tab, enter the client user & Password details of Destination system
    h) Test the connection and remote logon.Both should be succesful
    2) Create Port Using Transaction Code IDX1
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client
    d) Enter the RFC Destination created in SAP R/3 towards other system
    e) Save
    3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1
    SETTINGS IN SAP R/3
    We need to do the following settings in R/3
    Logon to Sap R/3 System
    1) ALE SETTINGS TO POST IDOC OUT OF SAP-R/3 ***********************************************************************
    a) Create RFC Destination using T.code in SM59.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#
    e) Enter the Gateway host as same details above SID/URL
    f) Gateway service is 3300+system number#
    g) In the Logon /Security tab, enter the client user & Password details of Destination system
    h) Test the connection and remote logon.Both must be succesful
    2) Create communication Port for Idoc processing Using Transaction(We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile with Outbound Parameters (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang
    Then Save
    e) Select Partner no. and LS which were create above
    f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
    g) Select Message type
    h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
    I) save
    4) In Transaction SALE, Create Logical System
    a). Go to Basic Settings-> First Define logical systems
    and then assign logical systems
    b) Double click on Define the logical systems
    c) Give data for your Logicaal System and Name
    d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
    e) Assign the logical system name to the client
    5) Create Customer Distribution model in the transaction code BD64
    1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
    2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
    3) Save the Distribution model
    Generate Partner Profiles
    Click on Menu Item u2018Generate Partner Profilesu2019
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
    4) Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> u2018Distributeu2019 to the destination client
    Popup window appears ,press Enter
    You will be intimated about the the Modal View Distributed
    warm regards
    mahesh.

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

  • ALE Distribution Model

    Hi,
    I've created an ALE distribution model to process the interface concerning Set Up HR and Accounting. Initialy we make it all and distribute it to the receiving system (FI) and it seems to be ok. After that the funcional team generate some movements and the IDOC's were generated but they were not sent to the FI system. We've a look at tRFC and an error concerning user or password invalid appears, so i define again the user comunication and after a few adjustments to the model view we distribute it again to the FI system. When i execute it the following message appears : <b>Model view HRFI-CFP has not been updated / Rreason: Distribution model is currently being processed.
    </b>
    Next step we delete the model view and created it again but the same error still remains.
    Can anyone help me ???
    Thanks is advance.
    JMMatos

    Hi
    Distribution Model – A model that describes the ALE message flow between logical systems.
    Applications and the ALE distribution service layer use the model to determine receivers and to control the data distribution. The relationships between logical systems, message types, BAPI’s and filters are defined in the distribution model.
    Ex: The screen shot depicts customer distribution mode ALE_TRNG_Mar07.
    Sender Logical System – EC1CLNT800
    Receiver Logical System  – SALES
    Message Type – CREMAS
    No filter conditions defined.
    This configuration step allows the installation of core ALE features on which data transfer activity will be based.
    In the distribution model you can specify the messages to be sent to a given logical system. You can also define the conditions for the content and dispatch of messages in the filters.
    The distribution model consists of one or more views that you can define
    After creating the distribution model – the model needs to be distributed to the receiver system.
    Partner profiles need to be generated in both sender and receiver systems using transaction BD82 (automatically) or WE20 (manually).

  • Query related to filter group on matnr created in ALE distribution model

    Hi All,
    I have query related to filter group on matnr created in ALE distribution model.
    I have created a filter group on matnr in ALE distribution model and put the value E*  ( purpose is that all the material number started with E should be triggered in case of any changes in the material).But it is not working.
    <b>Can anybody suggest the solution for this i.e how to capture E* value for the material master changes and should trigger idoc using change pointer using BD21.</b>
    Thanks & Regards
    Prabhat

    Unfortunately, you cannot filter using wildcards or exclusions.  You have to explicitly list each allowed value in its entirety.
    In my opinion, the simplest solution would be to copy function MASTERIDOC_CREATE_SMD_MATMAS, modify it to handle your custom filtering and update the message type entry in transaction BD60.

  • How to add BAPI in ALE-distribution model?

    HI all,
    I have to send The post goods issue through ALE-IDOC, this have to create the Goods Receipt in the receiving side.
    I came to know that the message type for this is MBGMCR , when i am trying to add this in the distribution model , it is prompting an error message that this message type belongs to BAPI.
    So , to send the required data , i have to add the BAPI.
    Please help me clearly on how to add this and what are the steps involved in  distributing data through BAPI ?
    Thanks,
    Vamshi

    In we20
    process code will be BAPI and setting will be same as in other process codes
    in bd64 i have example..
    TCode BD64
    Add ADRMAS in Distribution Model u2018TestERDToEXDu2019 as follow:
    Click on u2018Add BAPIu2019 Buton.
    Give Object Name as AddressOrg
    Give Method Name as SaveReplica
    You will get a entry as follows
    Edited by: Madan Gopal Sharma on Jul 1, 2008 9:02 AM
    Edited by: Madan Gopal Sharma on Jul 1, 2008 9:04 AM

  • ALE/distribution model settings

    Hi all,
    We are implementing SAP HR as HR master and need to distribute HR master data to connected systems. We will transfer the data to SAP XI which distribute to connected systems according to the respective requirements.
    We have two interfaces from SAP HR, one for changed data using change pointers in a near real-time fashion and one for complete records in a batch transfer using PFAL.
    We have a quite complex scenario where the changes should be sent to systems A and B, while the batch transfer should be sent to systems C and D. The scheduling of the data transfer has to be done in SAP R/3, since XI only forwards the messages. In order for XI to select the correct pipeline and determine the correct receivers we had to create two different interfaces from SAP HR to XI, based on two different extensions to the HRMD_A06 Idoc.
    These two interfaces are defined in two separate partner profiles in SAP, P1 and P2, each with one of the extensions as the only difference.
    The problem is that real-time idocs should only be sent to P1 and batch idocs should only be sent to P2. In the distribution model you can only define the sender and receiver partner, and the message type. This information is the same for both interfaces, so all idocs that are created, containing either changes using change pointers or batch data using PFAL, are sent to both interfaces.
    Is there a way to filter this, so only the correct idocs are sent to the respective interfaces?
    As it is now, we have the real-time data going to interface intA and intB every time there is a change, and the batch data scheduled every night will also be sent to both intA and intB.
    Any quick help or input to this is highly appreciated.
    Br
    Kenneth

    Hi Kenneth,
    Back again!!!
    Pls check whether i got ur requirement
    Scenario :
    1.) one sending HR system
    2.) one XI system
    3.) four recievieng systems
        A,B for change-pointers
        C,D for batch data.
    Already u have defined the following config in the SAP hr system.
    message type HRMD_A
    idoc type : hrmd_a06
    extension1(for change-pointers) : zext1
    extension2(for bacth) : zext2
    Solution :
    1.) whatever u have done for change-pointers is fine.
    u have activated change-pointers for hrmd_a.
    design a ale model only for change-pointers:
    sending system : HR system
    Recieving system : XI
    partner profile1 :
    mention
    message type : HRMD_A
    idoc type : hrmd_a06
            extension : ext1
    Define port1
    define rfc destination1.
    trigger rbdmidocs for message type HRMD_A to capture change-pointers on timely basis like every 30 minutes.
    BDCP table will be filled and idocs sent to XI for every 30 mins.
    i hope this scenario works successfully for u as required.
    2.) let us discuss abt batch data.
    Define a new message type ZREAL in we81.
    Define a relationship between message type,idoc type and extension.
    message type :ZREAL
    idoc type : hrmd_a06
    extension : ext2
    3.) Define ale model system.
    sending system : HR system
    recieving system : XI
    message type : ZREAL
    no need to define and activate change-pointers for message type ZREAL as it carries out only bacth data.
    4.) partner profile transaction ;
    partner profile1(same partner profile of change-pointers)
    message type will be ZREAL.
    idoc type : hrmd_a06
    extension : ext2
    5.) port1 will be same as change-pointers
    6. rfc destination1 will be same as change-pointers.
    7. schedule PFAL transaction for batch job.
    it will pick up the batch data and send idocs to XI.
    XI system :receiving system:
    u can able to distinguish between batch data and change-pointers data by message type:
    change pointers : hrmd_a
    batch data : zreal
    Only need to perform 2 main steps in we81,we82 for batch data.
    please check the solution and let me know for any concerns.
    Regards,
    Senthil

Maybe you are looking for