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.

Similar Messages

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

  • Why we dont need sender agreement and comm channel in IDOC to file scenario

    Hi,
    there are 2 queries:
    first query :
    Scenario is "Idoc to file transfer"
    why we dont need sender agreement and communication channel for IDOC to file ,while we do need
    both of these for "File to RFC "
    Answer : which i got is because IDOC sits at ABAP stack but same is valid for RFC also.
    Then why For "IDOC to file" we dont need that.
    Second query:
    Also when i did scenario for File1-RFC-File2 scenario using BPM i have created a interface
    between XI-RFC synchronous to send data which we got from file1 in XI to RFC importing parameter
    and getting data from RFC back to File2.
    Here in IDOC to file scenario why we dont need any interfface for IDOC-XI Asynchronous.
    Regards,
    Mayank
    Edited by: mayank verdia on Jan 13, 2009 11:49 AM
    Edited by: mayank verdia on Jan 13, 2009 11:50 AM

    Dear All,
    For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
    For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
    I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
    Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

  • IDOC to File - Clarification needed while using business service.

    Hi all,
    I have 2 scenarios to be implemented in PI..one is IDOC to File and another one File to IDOC.File systems in the above mentioned scenarios are 2 different legacy applications when business is concerned.So i am creating separate business services for the two legacy apps.I have included ECC in SLD and created proper LS name corresponding to that maintained in partner profile in ECC.File to IDOC scenario is working fine.
    In the second scenario (i.e. IDOC to File) also i need to mention adapter-specific identifiers. But since i have already used the R/3 system id and client in the File to IDOC it is throwing an error while trying to activate the buss service.The XML message is failing at Receiver identification step when i have omitted r/3 sys id and client.In the acknowledgement i am getting the message as "Unable to convert the sender service INTEGRATION_SERVER_DEVPI to an ALE logical system"
    I have checked entire SDN but didnt find any solution for the same.
    Is there any work around for this issue?
    Rgds,
    Lekshmi.

    Hi,
      Go through these blogs....
    /people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
    Also chk these threads also.....
    Error: Unable to convert the sender service xxxxx to an ALE logical system
    Unable to convert sender service to an ALE logical system
    Might help you....
    Regds,
    Pinangshuk.

  • IDOC to Flat File and XML ( Need both the Output)

    Hi ,
    My Scenario is IDOC to File .
    I need o/p in 2 format . ie,    1) Flat File 2 ) XML file
    I have a plan to go with Interface determination , 2 IM and what shd be the condition ?
    or Else  2 Receiver detmination  but condition ?
    How to slove this ?
    Need the Output from Idoc in 2 format ( Flat file and XML file )
    Any Blog , Thread ...Tips...etc
    Regards,
    Jude

    Hi Jude,
    Do like this:
    1. Create two inbound Service Interface (with the same target Message Type)
    2. Create separate Operation mapping with the above service interfaces as target (with the same source service interface)
    3. Create Interface Determination and include these two operation mapping (without any condition)
    4. Create 2 receiver agreement (with two separate communication channel) for each of the target service Inetrface. In one channel use content conversion and the other one will give you normal XML output
    Regards
    Suraj

  • IDoc to file. Grouping and generation of files based on condition

    Hi All,
    I am working on a scenario, Idoc to File. I need to create number of files based on  occurrence of a field(vendor) in the idoc. Also the condition is to group by the field(vendor) and create as many files as the number of groups formed.
    For e.g.: In an Idoc if there are ten items present and 3 vendors who are supplying it. <b>The vendor and items can repeat in any order within the same idoc. </b>
    I need to group the items by the vendors and create a file separately for each vendor.  Like :   
    Item         Vendor
    Item1       V1
    Item2         V1
    Item3         V2
    Item4       V2
    Item5        V2
    Item6         V2
    Item1      V2
    Item2         V2
    Item3        V3
    Item6        V3
    What we have to achieve is, to group by the vendors irrespective of the order of the items or number of reoccurrence of the items.  As you see, the Item1 is supplied by both V1 and V2. I need to generate 3 files as follows:
    V1.xml with Item1 and Item2 details.
    V2.xml with Item3, Item4, Item5, Item6, Item1 Item2 details.
    V3.xml with Item3 and Item6 details.
    Can someone please help me with achieving this without using BPM?

    Hi Shashi,
    For this scenario you have to use multimaping without BPM using this blog.
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    And while doing your message mapping you have to use <b>removeContext</b> & <b>SplitByValue</b> (double clike the on splitbyvalue and select <b>value changed</b>) function. This function you have to use with the node in which your Vendor is coming. Example:
    if required to sort the vendor, then first sort the vendor in the below mapping.
    Vendor (NODE) -
    > removeContext -
    > SplitByValue (value Changed) -
    > IDOC.
    By doing this your vendor will be grouped and you will get new IDOC on change of  Vendor.
    Regards,
    Sarvesh

  • Use of Distribution model in Idoc to file

    Hey guys
    just outta curiosity,why do we need to create distribution model for IDOC to file scenario,we can ofcourse do the scenario without creating Distribution model (by using WE19 to send IDOC's).
    is it because for day to day transactions we wont go for WE19(its just for test purposes),we rely on Distribution model?
    also is it job of XI developer to create DM ?
    thanx
    ahmad

    Ahmad,
    BD 64 Distribution model allowed you to automatically create the Logical Systems ( BD54 ) and the partner profiles.
    The steps you create to send an Idoc from your R3 system to XI ,( Bd54, we20 ) etc are all nothing but steps in the Distribution Model Bd 64 to send an Idoc to XI,
    Regards
    Bhavesh

  • Examples needed for Idoc to file and IDOC to web services

    Hi ,
    Could any one of you give some examples which take me through step-by-step in building IDOC-TO-FILE and IDOC-TO-WEB SERVICES?
    Regards,
    XI Developer.

    Hi,
    For IDOC scenario you need to first do the required configuration:
    ALE configuration for pushing idocs from SAP to XI
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    Testing purpose u can use the below method:
    IDOC testing using WE19
    /people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters --> For Idoc sender: IDOC -file
    IDOC configuration:
    Please follow the below process for configuration:
    Pre-requisites for Inbound IDoc to R/3 from PI:
    Configuration required at Xi side:
    Go to IDX1: configure the port.
    Go to IDX2: load the DOC metadata.
    Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
    Configiration required at R3 side:
    Maintain Logical System for PI (SALE transaction):
    Maintain Partner Profile for XI system(WE20):
    Pre-requisites for Outbound IDoc from R/3 to PI:
    Configurations required in R/3:
    Maintain Logical System (SALE)
    Define RFC Destination (SM59) which points to PI system
    Maintain Port (WE21)
    Maintain partner profile. (WE20):
    Maintain Distribution Model (BD64):
    File To IDOC - Part1 (SLD and Design):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    File To IDOC - Part2 (Configuration):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    File To IDOC - Part3 (Steps required in XI and R3):
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    SOAP scenario:
    YOu have to first create the WSDL through ID and import that WSDL in to IR external definition.
    Refer the below thread and pdf:
    How to use SOAP adapter:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
    SAP AII - How to consume and expose webservices  ?
    Thnx
    Chirag
    reward points if it helps.

  • How to do idoc to file cenario?

    Hi,
      how we can do idoc to file cenario in sap-xi,
    pls  explain me?

    Hey,
        For Idoc to File Scenario you need to do ALE settings on R3 side as well XI side.
    refer to the following Steps.
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create two partner profile(one for XI the other for R3).
         Give the outbound or inbound message type based on the direction.
    Step 5)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 6)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    Step 7)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    BD87 to check the status of IDOC.
    In case if not authorized then go to the target system and check in SU53, see for the missing object
    and assign it to the user.
    Once this is done you can import the idoc in Your XI in the Imported Objects.
    Now create the Data type and message type for the receiver file Structure.
    Map the Idoc with the receiver file structure.
    Do your Interface mapping and the required configuration Steps.
    reward points if useful.
    regards,
          Milan

  • Java CAPS SAP IDoc OTD thru IDOC descriptive file needs any sap jars and dd

    Hi All,
    I am doing PoC in Java CAPS using SAP IDoc Descriptive file. As I know for creating SAP IDoc OTD thru it will need certail jar filr and ddls. But creating SAP IDoc ITD thru IDoc descriptive file also we need certain jar files and DLL.
    Please let me know on this.
    Thanks in advance.

    Yes, you will need all of the required SAP JCo jars and DLLs even though you are using the IDoc description file. This link might be useful to you - [Creating a SAP ALE OTDs Wizard|http://docs.sun.com/app/docs/doc/820-4380/dsgn_sap-ale-otd_t?a=view]

  • IDoc Flat File Needed

    Hi Experts.
        I need the Idoc flat file for Delfor01(delivery schedule).
    Advance Thanks.

    Hi Bala,
    Follow the procedure
    IDOC to XML Convertion using ALE Interface
    1) Send an outbound IDOC data(MATMAS) to a flat file(XML) on client1(SENDER).
    - Create File Port (WE21) of XML Type for outbound file.
    - Specify the Physical directory and file under the Outbound File tab
    - Maintain Distribution Model (BD64) for sender ->receiver system.
    - Create Partner Profile (WE20) for logical system.
    - You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
    _ Then you can FTP the file(s) to receiver system.
    2) Upload the flat file as an IDOC on the inbound sytem
    which is Client2(RECIEVER).
    - Create File Port (WE21) for inbound file.
    - Maintain Distribution Model (BD64) for receiver -> sender system.
    - Create Partner Profile (WE20) for logical system.
    - You can use this program RSEINB00 to upload IDoc MATMAS file(s).
    A sample scenario for idoc generation
    Sending System(Outbound ALE Process)
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Create Model View
    Tcode BD82 ? Generate partner Profiles & Create Ports
    Tcode BD64 ? Distribute the Model view
    Message Type MATMAS
    Tcode BD10 ? Send Material Data
    Tcode WE05 ? Idoc List for watching any Errors
    Receiving System(Inbound ALE )
    Tcode SALE ? for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 ? Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 ? Idoc List for inbound status codes
    ALE IDOC Steps
    Sending System(Outbound ALE Process)
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Create Model View
    Tcode BD82 !V Generate partner Profiles & Create Ports
    Tcode BD64 !V Distribute the Model view
    This is Receiving system Settings
    Receiving System(Inbound ALE )
    Tcode SALE ?3 for
    a) Define Logical System
    b) Assign Client to Logical System
    Tcode SM59-RFC Destination
    Tcode BD64 !V Check for Model view whether it has distributed or not
    Tcode BD82 -- Generate partner Profiles & Create Ports
    Tcode BD11 Getting Material Data
    Tcode WE05 !V Idoc List for inbound status codes
    Message Type MATMAS
    Tcode BD10 !V Send Material Data
    Tcode WE05 !V Idoc List for watching any Errors
    STEP 1)a Goto Tcode SALE
    Click on Sending & Receiving Systems-->Select Logical Systems
    Here Define Logical Systems---> Click on Execute Button
    go for new entries
    -System Name : ERP000
    -Description : Sending System
    -System Name : ERP800
    -Description : Receiving System
    press Enter & Save
    it will ask Request
    if you want new request create new Request orpress continue for transfering the objects
    B) goto Tcode SALE
    Select Assign Client to Logical Systems-->Execute
    000--> Double click on this
    Give the following Information
    -Client : ERP 000
    -City :
    -Logical System
    -Currency
    -Client role
    Save this Data
    Step 2) For RFC Creation
    Goto Tcode SM59-->Select R/3 Connects
    Click on Create Button
    RFC Destination Name should be same as partner's logical system name and case sensitive
    to create the ports automatically while generating the partner profiles
    give the information for required fields
    RFC Destination : ERP800
    Connection type: 3
    Description
    Target Host : ERP000
    System No:000
    lan : EN
    Client : 800
    User : Login User Name
    Password:
    save this & Test it & RemortLogin
    STEP 3) Goto Tcode BD64 -- click on Change mode button
    click on create moduleview
    short text : xxxxxxxxxxxxxx
    Technical Neme : MODEL_ALV
    save this & Press ok
    select your just created modelview Name :'MODEL_ALV'.
    goto add message type
    Model Name : MODEL_ALV
    sender : ERP000
    Receiver : ERP800
    Message type :MATMAS
    save & Press Enter
    STEP 4) Goto Tcode BD82
    Give Model View : MODEL_ALV
    Partner system : ERP800
    execute this by press F8 Button
    it will gives you sending system port No :A000000015(Like)
    STEP 5) Goto Tcode BD64
    select the modelview
    goto >edit>modelview-->distribute
    press ok & Press enter
    STEP 6) goto Tcode : BD10 for Material sending
    Material : mat_001
    Message Type : MATMAS
    Logical System : ERP800
    and Execute
    STEP 7)goto Tcode : BD11 for Material Receiving
    Material : 100-300
    Message Type : MATMAS
    and Execute --> 1 request idoc created for message type Matmas
    press enter
    Here Master Idoc set for Messge type MATMAS-->press Enter
    1 Communication Idoc generated for Message Type
    Now go to the physical directory and check your idoc converted as an XML File.
    Note enter required message type
    OR try this
    Just pass the IDoc Document no in the FM - IDOC_XML_TRANSFORM.
    IDOCS_OUTPUT_IN_XML_FORMAT
    IDX_IDOC_TO_XML
    it will transform the IDoc in XML format
    Regards,
    Sridhar

  • Idoc-To-File-Material Master.

    Hi,
    Please let me know the Partner Type and Partner Function to create Partner Profile for Material Master data in SAP R/3 side.(Outbound).
    Rgds
    Ruchitha.

    Hi,
    This is expalined both the scenarios:
    Please follow the below process for configuration:
    Pre-requisites for Inbound IDoc to R/3 from PI:
    Configuration required at Xi side:
    Go to IDX1: configure the port.
    Go to IDX2: load the DOC metadata.
    Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
    Configiration required at R3 side:
    Maintain Logical System for PI (SALE transaction):
    Maintain Partner Profile for XI system(WE20):
    Pre-requisites for Outbound IDoc from R/3 to PI:
    Configurations required in R/3:
    Maintain Logical System (SALE)
    Define RFC Destination (SM59) which points to PI system
    Maintain Port (WE21)
    Maintain partner profile. (WE20):
    Maintain Distribution Model (BD64):
    DO let me know if you need more information
    Thanks and Regards,
    Chirag Gohil.

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

  • Need of distribution model in IDOC triggering

    Hi,
    I have one question dat is it necessary to maintain distibution model in BD64 for outbound IDOCs or only maintaining partner profile in WE20 is mandatory.
    I have seen some cases in which distribution model is not maintained.
    Please let me know the cases in which we maintain distribution model
    Thanks in advance.

    hi,
    The distribution model describes the ALE message flow between logical systems u2013 that is, it determines which messages are distributed to which logical systems.
    For example, you can make distribution dependent on conditions that you define as filters in the ALE distribution model.
    please refer this blogs for more info:
    Data Ditribution Model BD64 config
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a610f507d11d18ee90000e8366fc2/frameset.htm
    thanks ,

  • Idoc-xi-file scenario.  how to display file in html format

    I am not sure whether this is a valid question.........but want to confirm as it was asked by somebody
    In idoc-xi-file scenario.......  how to display file in html format ??
    Thanks in advance
    Kumar

    Hi Vijayakumar,
    Thanks for your reply !! You mean to say I got to use XSLT mapping and also .htm and .html extension together to produce the html file ?? or it is sufficient to use any one of them to produce the html file ??
    Regards
    Kumar

Maybe you are looking for

  • My Game API

    I just discovered this Forum and couldn't help but mention I have been working on a game API since early 97. I am still working on it (doesn't pay the bills) However, I think I have the absolutely most efficient and robust API for games for many many

  • PR Release Strategies on purchasing group basis

    Dear All, I want to define PR Release Strategies on purchasing group basis. please suggest process. Regards, Mukesh Chejara SAP

  • Static NAT Command Clarification

    Hi all : From one of existing configuration file, I found there is static NAT command as below : static (dmz,outside) 192.168.50.0 192.168.50.0 netmask 255.255.255.255 whereby the security level in the DMZ is 50 and the subnet is 192.168.50.0/24,whil

  • Redirecting when page NOT FOUND error occurs

    Does anyone now a way to redirect the client to a certain page whenever he encounters 404 NOT FOUND errors? I do not want to use a custom response page, I just want to redirect to a URL. The reason is our clients are WAP clients, and they do not see

  • Trx MM01.

    Hi, how can I set in MM01 trx in field Industry sector the default value <b>Mechanical engineering</b>? Best regards