IDOC Scenario: Filling ED40 in XI to SAP automatically or not

Hello,
I was trying to let XI fill the ED40 data of my IDOC and set the flag in
receiver channel, that he should not take these information from payload.
It seems he took wrong data. So from where he take these information?
I disabled the ED40 segment in mapping. So in sxmb_moni I couldn't see
the information he put into the fields. If I don't disable them, he says that
required fields are not mapped.
thanks
chris
Edited by: Christian Riekenberg on Jul 10, 2008 1:16 PM

> I disabled the ED40 segment in mapping. So in sxmb_moni I couldn't see
> the information he put into the fields. If I don't disable them, he says that
> required fields are not mapped.
Hi,
if you look into ED40 segment you will see there are some fields with occurrence 1:1, and that means you have to have some values in those fields (if not disabled this segment). Either you map the hard coded the vaules using constant function or map with some other source fields to these mandatory fields. But make sure there shuld be some data in case if you map with source fields.
So this is the reason you are getting a message "required fields are not mapped".
IF you are using EDIDC40 then you have to tick the check box take the values from payload, otherwise If you disable EDIDC40 then the values will be automaticall taken care by XI.
Regards,
Sarvesh

Similar Messages

  • How can I include the Header Information....for a File to IDOC Scenario

    Hi,
    I made a File to IDOC Scenario with DEBMDM06 for MDM>XI>SAP R/3. The Header Information in the XML File which is at the XI end is Missing. For that reason In Tcode SXMB_MONI we are getting an Error that <b>"HEADER Information Missing: Message should Start with EDI_DC40"</b> i.e the Header Information.
      My Question is that whether we can do some changes in the Message mapping Step in the Integration Repository. I HardCoded the Few mandatory Fields that were there but it Again gave me the Same Error as above.
    Can you please Suggest some Solution for this. Since the data is Coming in from MDM part the Header information is not there but It actually Important as it has got all the Port Information.
      Kindly Inform me some Solutions.
    Thanks & Regards
    Somnath

    Hi Suraj,
      Thanks for ur Reply, but Since we are Doing a File to IDOC Scenario the IDOC DEBMDM is on the Right Side in Message Mapping and as U know it is Mandatory to Map an IDOC on the Right Part. EDI_DC40 is coming as it is there in the IDOC but our XML File Does not have that. If we Don't Map then it Becomes RED, which is an Error.
      Furthermore in the Receiver Agreement we have put the Necessary Details such as Sender Service and Receiver Service along with the IDOC Communication Channels.
      Can U give as a Better Insight on this Note how to check the Header Part as it is mandatory to MAP.We also tried to HARDCODE it by putting those Values and Mapping them to a Constant but it is Giving the Same Error.
    Thanks and Regards
    Somnath

  • Http - iDoc scenario - ID

    Hi,
    HTTP - XI - iDOC  is my scenario.....
    i am facing problem in iDoc adapter...
    the error category is idoc adapter and the error id is "ATTRIBUTE_INV_SND_SERV"
    Which RFC destination and port should in mention in Communication Channel? Either the receiver or XI?
    forward your suggestions....
    Thanks,
    RPN

    hi rpn,
    check this links
    Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers
    Maintain Logical System name and System ID and Client number.
    Check the following blog.
    The specified item was not found.
    Unable to convert sender service to an ALE logical system
    ATTRIBUTE_INV_SND_SERV
    XI 3.0, Party and Service problems (IDoc inbound)
    Trouble shooting file to IDOC and IDOC to file
    Troubleshooting  File-to-IDOC Scenario in XI.
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
    see the below links
    ALE configuration for pushing idocs from SAP to XI
    Introduction to IDoc-XI-File scenario and complete walk through for starters.
    idoc settings Configuration steps required for posting idoc's(XI)
    Also
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
    IDOc testing - Generate Test Case for an IDOC Scenario
    regards
    srinivas

  • IDOC scenario Debugging

    Hi,
       I want to debug the IDOC senarios(Both File to Idoc and Idoc to file ).. for this.. from where can we start.. and what are the things we need to check.. how can we debug the scenarios...
    i mean.. just give me the descriptive steps..
    Thanks
    BABU

    HI,
    1. Start with checking the status in sm58 of sender R/3
    Follow the steps
    No message in found in XI in IDOC to FILE scenario
    2. Try deleating the IDoc from IDX2 and refiring the same.
    3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
    In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
    4. Monitor the SM58 in R/3 for IDOC status.
    5. Trouble shooting file to IDOC and IDOC to file
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
    Refer below links for indepth troubleshooting
    File to IDOC, trouble shooting
    Refer below steps
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    IDOC to File steps to be followed please verify your scenario with it
    R3 system.
    1. Create SM 59 RFC destination to XI,.
    2. We21 - Create port to XI.
    3. We 20 -- Maintain Partner Profile for the outbound Idoc.
    XI SLD
    1. Create technical system for R3 system
    2. Create Business System for the Client of the R3 system.
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    These are the required steps for IDoc to File scenario...
    In R3 (i.e., your IDES system)...
    RFC dest to XI (sm59) - any name
    Logical system (bd54) - any name
    Port to XI (we21) - any name
    Partner profile for the logical system (we20) - use Logical system name created in bd54
    In XI...
    RFC dest to R3 (sm59) -
    Port to R3 (idx1) -
    create metadata for the idoc (idx2)
    In sld...
    create business system for R3 with Logical system name as r3 sys.
    In we19
    and give in control record as
    Sender : Port ; Partner
    Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
    see the below links
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    Also
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
    IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
    Thanks
    Swarup
    Edited by: Swarup Sawant on Feb 9, 2008 1:32 PM

  • Problem in Idoc scenario

    Hi
    Can anyone tell me how to determine the status of an iDoc in recieving system.
    Please be specific

    Hi,
    enter WE05 transaction code in R/3 and hear u will c the status of IDOC wether it is posted succesfully.
    1. Start with checking the status in sm58 of sender R/3
    Follow the steps
    No message in found in XI in IDOC to FILE scenario
    2. Try deleating the IDoc from IDX2 and refiring the same.
    3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
    In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
    4. Monitor the SM58 in R/3 for IDOC status.
    5. Trouble shooting file to IDOC and IDOC to file
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
    Refer below links for indepth troubleshooting
    File to IDOC, trouble shooting
    Refer below steps
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    IDOC to File steps to be followed please verify your scenario with it
    R3 system.
    1. Create SM 59 RFC destination to XI,.
    2. We21 - Create port to XI.
    3. We 20 -- Maintain Partner Profile for the outbound Idoc.
    XI SLD
    1. Create technical system for R3 system
    2. Create Business System for the Client of the R3 system.
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    These are the required steps for IDoc to File scenario...
    In R3 (i.e., your IDES system)...
    RFC dest to XI (sm59) - any name
    Logical system (bd54) - any name
    Port to XI (we21) - any name
    Partner profile for the logical system (we20) - use Logical system name created in bd54
    In XI...
    RFC dest to R3 (sm59) -
    Port to R3 (idx1) -
    create metadata for the idoc (idx2)
    In sld...
    create business system for R3 with Logical system name as r3 sys.
    In we19
    and give in control record as
    Sender : Port ; Partner
    Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
    see the below links
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    Also
    /people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
    IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario

  • How to fill controlrecord in File to Idoc scenario

    Dear experts,
    Currently I have a working file->Idoc scenario in which I fill Idoc-controlrecordvariables as follows:
    - field SNDPOR: name of XI developmentsystem (via a constant)
    - field RCVPOR: name of SAP developmentsystem (also via a constant)
    - same for fields like SNDPRN and RCVPRN etc.
    In Development this works fine. Then I transport the design objects to the next environment. But when I want to test the same in Acceptence or Production, it won't work because the fields are still filled with the settings for the Development system.
    Can I fill these fields via some systemvariable in stead of a constant? Or is there another way?
    Thanks,
    William
    Edited by: JWD on Aug 31, 2010 2:20 PM

    Hi,
    1)Uncheck option Apply contraol record values from Payload in IDoc receiver channel.
    2)Disable EDI_DC40 control record in message mapping.
    this two steps will solve your problem at configuration time it will take the values irresctive of environment.so you no need to maiantain constant values..
    Regards,
    Raj

  • Simple IDoc to IDoc scenario with SAP PI

    Hi!
    I would like to implement a very simple IDoc_to_IDoc scenario.
    i have two clients in SAP ECC 6.0 and would like to send/receive IDoc (e.g. material) with SAP PI.
    Can some one please give exact the technical steps(tcodes, action in XI Tools) to realize this issue?
    Any helpful information/documentation/SDN blogs will be very appreciated.
    Thom

    hi,
    Communication Channels:
    1) No Sender Channel is required as we are using IDOC.
    2) CC_OUT_IDOC_MATMAS05 [Send the data from Xi to CGNSAP01]. 
    Transaction Codes Used: 
    SM59- To Create RFC Destinations
    WE21- To Create IDoc Ports
    SALE- To Create Logical System
    WE20- To Create Partner Profiles
    BD64- Display Distribution Model
    WE19- To Trigger an IDoc 
    IDX1- Port Maintenance in IDoc Adapter
    IDX2- Metadata Overview for IDoc Adapter 
    Regards.

  • ATTRIBUTE_IDOC_RUNTIME error in File-IDOC Scenario

    Hi,
    I got this error in FIle-IDOC scenario.
    ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>Transaction IDX1: Port SAPMMX, client , RFC destination contain errors
    There are many threads on same issue. Almost in all threads, the suggestion given was, we need to check the Channel Definition(Port should be SAP<SYSID> and not SAP<SYSID>_<CLIENT>)
    I have given the proper values for RFC desitnation and port. Even then, I m getting this error.
    Is there any other suggestions?

    Hi aarthi,
    I suggest u chk all d settings dat u hav done..
    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)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    Step 6)
         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 7)
         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.
    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.
    SAP r3
    sm59(status check)(no message)
    WE02(status check)
    WE05(status check)
    BD87(status check)
    Xi
    IDx5(Idoc check)
    SU53(authorization check)
    reward points if helpful...
    MenoN

  • Doubt regarding  ALE SETTINGS in IDOC scenario.

    Hi Friends,
            I have some doubts regarding ALE settings for IDOC scenarios,  can anyone  please clarify my doubts.
    For exmaple take IDOC to FILE scenario
    The knowledge i got from SDN is --
    One need to do at the  R3 side is  --- RFC DESTINATION (SM59)  for the XI system.
                                                       --- TRFC PORT  for sending IDOC  to the  XI system
                                                       --- CREATING LOGICAL SYSTEM
                                                       --- CREATING PARTNER PROFILE 
                   at the XI side is  --- RFC  Destination ( For SAP sender system)
                                           --- CREATING  PORT  for receiving IDOC from the SAP sending system(IDX1).
    1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
    In IDOC to IDOC scenario-------
      2.  Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
      3.  If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
    y we r creating receiver communication channel in the case of FILE to IDOC scenario?
      4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                    FILE to IDOC scenario,                                                                               
    IDOC to IDOC scenario individually.
    Thanks in advance.
    Regards,
    Ramana.

    hi,
    1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
    it is a mandatory step in doing ALE configurations
    2. We create 1 RFC destination each in R3 and XI.
        R3 RFC destination points to Xi and
        XI RFC destination  points to R3
    3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
    4. ALE settings for all IDOC scenarios are same  as follows....
    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.
    SAP r3
    sm59(status check)(no message)
    WE02(status check)
    WE05(status check)
    BD87(status check)
    Xi
    IDx5(Idoc check)
    SU53(authorization check)
    Reward points if helpful
    Prashant

  • IDoc scenario

    Hi all,
      I have done file to idoc scenario. in that
    No error in sxmb_moni
    IN SAP system( we05)
    EDI: Partner profile inbound not available
    Status 56
    Message from
    Control records is-> patner
    Recipient Information
    (EMPTY)
    IDS47800
    LS
    Sender Information.
    SAPC08
    NW4SR1
    LS
    When select the options in
    IDOC adapter
    1. Apply control record from the payload.
    I took help from these wlg
    https://websmp201.sap-ag.de/nw-howtoguides
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    if IDOC adapter , select the options,
    1. Apply control record from the payload.
    2. Take sender from payload.
    3. take receiver from payload.
    Then
    Error in sxmb_moni
    Error: Copy sender from payload: Sender not in
    Objects that have created->
    Object created in Sap(r/3)C47 for client 800
    SM59-> C08_010  
    WE21->(NW4SR1_C08)Port->NW4SR1_C08,R.d.->C08_010
    BD54->IDS47800 (Client ->800)
    WE20->IDS47800;Patnerno->IDS47800,P.T.->L.S.
                  Inboudn parmtrs->CREMAS( Patnerno IDS47800,P.T.->LS,M.T.->CREMAS,Process code->CRE1
    Object created in XI C08 for client 010
    SM59-> IDS47800
    IDX1-> SAPC47,Client->800,R.D.->(IDS47800)
    IDX2-> SAPC47,Idoc type->cremas03,client 800
    /* BD54-> NW4SR1,Client 010 (NW4SR1)  **In sld Sender service l.s. NW4SR1 updated in Business system (pdp( third party) in Integration Directory                    */
    SLD->T.S.(WEB as abap and logical system is ->IDS47800)
               B.S. whose name is VAGUABAP(WEB as abap for above T.S.)
    In Integration Directory-> sender service(pdp) and receiver service(VAGUABAP)
    May i go for modelview concept? when we go for model view? can any body tell compleate steps for file to idoc with an example(not IR and ID Objects). or send any document. mailid -> [email protected]
    Friends, Please find where I have done mistake. Your help is rewardable.

    Hi,
    Have a look into this-
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    Techincal System and product will be created. Then create a business system for the R/3 technical system. Also fill out Partner profile entries in the R/3 in WE20 ->outbound parameters and test it..
    Regards,
    moorthy

  • Reg:Steps in IDOC Scenario

    Hi,
        I am very new to IDOC concept so can anyone tell me what is the use and why do we want to create,
    1)RFC Destination
    2)Port
    3)Logical sysytem name
    4)Partner Profile ,in IDOC Scenario and also let me know the steps that I have to implement  while doing that scenario.
    Thanks in advance
    B.Lavanya

    Hi,
    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,PROCEED AS FOLLOWS
    STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
    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)   Create an RFC Destination to XI 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 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 ‘Generate Partner Profiles’
        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-> ‘Distribute’ to the destination client
        Popup window appears ,press Enter
    You will be intimated about the the Modal View Distributed
                 Step2:Repository
    1)       From the Integration Builder page, select “Integration Repository”. This will launch the Java Web Start Application. Log with the User id and password from the  Integration Server
    2)       Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
             From the list of Software Component Versions, Choose your own software component version .Click Import.
    3)       On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this  software component. A screen will appear .Switch to display mode. After doing this first add  a namespace under Namespaces.
             Your NameSpace is urn : DSZVFGD
    4)       Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
             After this specify the connection parameters to the R/3 system:
    4.1)     System  :SAPFOX
    4.2)     Client  :800
             Then Save it. The new namespace will be visible under software component version node in the left frame.
             Under the namespace node,  you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
    4.3)     Application server:172.25.5.7
    4.4)     System number:00
    4.5)     User name: DEVELOPER
    4.6)     Password: Password of Sap R/3 system.
             Then click continue .You will find IDOC node. Click on this node and select the   Idoc  which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the    Idoc will be available into XI as Message types. So no need to create any  Idoc Structure. We need to create a structure for file only.
    5).      Under your namespace in the left frame, expand the node “Interface objects”. You will find a node “DATA TYPES”
    6)        Create new data types.
    6.1)      Right click on “Data types” and select “New”.
               Your Data Type is :DT_FILE
              In the data type Editor ,Create a structure having Elements of type String  ,  integer,  Boolean , Float etc as per the requirement.
              Save the object.
    6.2)      The Import function for XSD  files enables you to upload message definitions from external sources. The object type “External Definition” is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from “External Definition
              no need to create Data types. They are imported directly as Message types.
    6.3)      To do so, In the left hand frame  Under  ” Interface objects” Create a new object of type “External Definition” and give name to it.
              Select the following.
    6.3.1)    Category: XSD.
    6.3.2)    Messages: From All Available Global Elements.
    6.3.3)    File:
              Once the XSD is imported, click on “Message” tab , You should be able to see 2 messages(Request and Response)
    7).      Create a new Message  Type.
    7.1)     In the left hand frame under “Interface objects”, right click on the “Message types” and select new.
    7.2)     Give a suitable name to the Message type.(MT_ messagetype).
    7.3)     For the section “Data type used” you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
             Save it.
    8).     Create a Message interface
    8.1)    In the left hand frame under “Interface objects”, right click on the “Message Interface” and select new and name(MI_ messageinterface) it
    8.2).   The interface Should be  Inbound  and mode should be Asynchronous  .It should reference your Message type(Use F4 or Search help).
            Save it.
    9) .    Create a graphical mapping  between the target document and the sender .
    9.1)    In the left hand frame ,expand “Mapping objects”. Right click on “Message mapping” and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
    9.2)    As Source message select  your own Idoc .You can choose “Search  for Integration Object”.As a reminder you can find your Idoc or Rfc under Software Component-  >     Namespace->Imported Objects.
    9.3)    As Target Message you can choose your Message type  .Choose “Search  for Integration Object”.
    9.4)    Now that we have defined the  Source and Target message, we can start defining the Mapping rules.
    9.5)    Map the fields of  Source document  to the equivalent fields in  Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the   Source fields to the respective Target Fields.
            Save It.
    9.6)    You can also Test your Mapping by selecting the 'Test Tab'.
    9.7)    Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
    10).     Create an Interface Mapping.
    10.1)   In the left hand Frame  expand “Mapping objects”. Right Click on “Interface Mapping” and  Name it. You are in a Interface Mapping Editor .Assign the following References.
    10.2)   Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose” Search  for Integration Object”.
    10.3)   Target interface:    Your Inbound Interface( The Target document interface).
            Then Select  'Read Interface' and Assign your  'Mapping Program' .
            Mapping Program: Your Message mapping.
            Then Save it.
    11.)    Finally , in the left hand frame ,go to your change list and Activate it
               STEP 3: Directory
    1)      From the Integration Builder page, select “Integration Directory”. This will launch the Java Web Start Application. Log with the User id and password from the  Integration Server.
            Create a Scenario Object
    2).     The First Step is to create a Scenario Object
            This will serve as container for all your configuration work. Create and save a scenario object
    3)      In the left hand frame you can see the created scenario object. Under that Object Expand the node “Service without Party” and right –click on “Business System”->Assign Business System
    4)      In the wizard , leave the party name blank and then select  your own Business System. Uncheck the box ”Create Communication Channel Automatically”.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
    5) .    Create a Communication Channel.
    6).     Expand your service and right click on “Communication Channel”. Name your Communication Channel
            Here we need to configure the adapter.
         Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
              For the Receiver, Specify the following Parameters
    6.1       For the adapter type , use the F4 help  and select FILE.
    6.2       Specify “Receiver” since the adapter will be  sending XML files from XI to the  FTP server.
    6.3       Specify the following parameters.
              Transport Protocol: File Transport Protocol.(FTP)
              Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
              Adapter Engine: Integration Server
              For the File system access Parameters, enter the following
              Source Directory:VILAS
              File Name: Input.txt
    6.4       For the FTP Connection Parameters, Specify the Following
              Server: 172.25.7.116
              Port: 21(by default)
              Data Connection: Passive
              Connection security: None
              Connection Mode:  Permanently
              Transfer Mode: Binary
    6.5       For Processing Parameters, Specify the following
              File construction mode: Add Time Stamp
              File Type: Binary
    6.6       For Content Conversion Parameters, Specify the Following
              RecordSet Structure:
              Adapter Status: Active
              The receiver file adapter is now configured. Save your Communication Channel.
               Create an Receiver Determination.
    7).       From the left frame Create a new “Receiver Determination” object. This is the main part of routing process, where you assign a receiver for your message.
    7.1)      Select your sender service and interface.
              Sender:
              Party:  blank
              Service:  Sender service(Business system)
              Interface : Sender interface
    7.2)      In the “Configured Receivers” area ,  choose the Service for the Target System.. Save your Receiver Determination
                Create an Interface Determination.
    7.3)       Next create an “Interface Determination” object. Now that we have defined a receiver of message  ,we need to assign an Inbound interface and an Interface mapping
    7.3.1)     In the Receiver Determination   you just created, have a look at the area “Configuration Overview for Receiver Determination”   at bottom of your screen and press Refresh  for that the Business system you assigned is displayed  in that area as well.
    7.3.2)     In the column “Receiver(Partner/Service)” open the details by clicking the node .The Entry “Not defined” shows you that there is no interface determination present.
               Right click on the Entry “Not defined” and select “ New specific”,  in order to create a new interface determination object
    7.3.3)     You are now in  the screen “Edit Interface Determination”. In the section “Configured Inbound Interfaces” select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
               After choosing the Inbound Interface,  It is shown in the Interface Determination
    7.3.4)     A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
    7.3.5)     When you are done ,  Save the Interface determination object.
    8.)         Create a Sender Agreement.
               In the left hand frame , right click on “Sender Agreement” ->New
    8.1)       Specify the following:
               Party: blank
               Service: Select your own Business system
               Interface: Outbound Interface
    8.2)       In the screen “Edit Service Agreement” use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
    9.)         Create a Receiver Agreement.
               Finally you will create a  'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
    9.1)       Go back to the main screen for your receiver determination. In the area “Configuration Overview for Receiver Determination” at the bottom of your screen click Refresh.
    9.2)       In the Column “Receiver Agreement(Communication Channel) “ right click and select “New Specific”.
               Specify the following:
               Party: blank
               Service: Select your own Business system
               Interface: Inbound Interface
    9.3)       In the screen ”Edit Receiver Agreement” for the field Receiver Communication Channel use  the input help F4 and select your communication channel. Save and Close it
               Your Configuration is complete. Activate the objects.
    PLZ REWARDS POINTS
    VIKAS

  • R3 settings for IDOC-IDOC scenario

    Hi,
    For IDOC to IDOC scenario what are the settings we have to in R3 System other than XI configuration settings.
    What are setting for both sender and receiver side.
    Thanks,
    Kishore

    Hi Kishore,
    http://help.sap.com/saphelp_nw04/helpdata/en/18/22b800773211d396b20004ac96334b/content.htm
    http://www.erpgenie.com/index.php?option=com_content&task=view&id=346&Itemid=57
    http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci994575,00.html?NextURL=http%3A//searchsap.techtarget.com/expert/KnowledgebaseAnswer/0%2C289625%2Csid21_gci994575%2C00.html
    http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
    Refer this material..
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    You can directly create an iDoc using some transaction like...
    Use TCODE bd10 - to Send Data
    and TCODE bd11 - to Get Data
    and you can check the IDoc List using TCODE we02.
    As you want step by step procedure.
    1. Define Logical System and Assign Logical System
    TCODE sale
    2. Define RFC
    TCODE sm59
    3. Define Port
    TCODE we21
    4. Define Partner Profile
    TCODE we20
    5. Define Distribution Model
    TCODE bd64
    6. Send Data
    TCODE bd10
    7. Get Data
    TCODE bd11
    8. IDoc List
    TCODE we02
    There are basically two types of IDOCs.
    Basic IDOCs
    Extended IDOCs
    Idoc Components
    Basic Idoc
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extension Idoc
    Extending the functionality by adding more segments to existing Basic IDOCs.
    Creation of IDoc
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Create IDOC Type
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    u can also check all these links related to idocs
    http://www.allsaplinks.com/idoc_sample.html
    http://www.allsaplinks.com/
    http://www.sap-img.com/
    http://www.sappoint.com/abap.html
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
    http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
    http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
    Reward points if this helps
    Regards
    Pragathi.

  • Separation of business processes in IDoc scenarios

    Hello!
    We have implemented an IDoc -> XI -> IDoc scenario with complex mappings and enhanced receiver determination using the value mapping API in which about 15 different R/3 platforms send IDocs to XI for internal ordering.
    All R/3s are using standard IDoc types like DELFOR.DELFOR02, DESADV.DELVRY03, ORDCHG.ORDERS05, ORDERS.ORDERS05 and ORDRSP.ORDERS05. As XI gets more and more used additional projects are coming up in which we will also use exactly the same IDoc types.
    Especially when using enhanced receiver determination it now gets extremely difficult to separate the different business processes once they use the same IDoc types. The projects do not only share the same receiver determination object but what is even worse they also share the same message mapping object to determine the receiver. This makes development, testing and MTP extremely difficult and requires coordination over several project teams.
    Within R/3 business scenarios can easily be separated using different message codes and message functions. However, once the R/3 post IDocs to XI there is no clear separation possible any more.
    Of course, every project can implement own Java classes for enhanced receiver determination and transport the archives separately but still the problem is that all the projects using the same IDoc message type share the same message mapping object to the determine the receiver. This means that it would be necessary to fill the input parameters for the enhanced receiver determination classes of ALL projects within the same object. Either by putting logic in the graphical mapping or writing another Java function to call the different Java classes for enhanced receiver determination based on the message code and message function.
    From a design perspective it is no good approach to mingle logic for different projects and business scenarios in the same development objects. What alternatives do we have? Does SAP plan to support a separation using message code and message function for IDoc scenarios in the Integration Repository?
    Regards, Tanja

    Hello!
    Does nobody have any comments on this?
    Regards, Tanja

  • JMS to IDOC scenario...

    Hi,
    I am doing an JMS to IDOC scenario...
    where will i mention saying there is a logical system in R3(Partner profile).The IDoc should reach that Logical system only.I have a doubt on this....Because we are disabling the IDOC EDIDC segemnt in Recever segment.so.
    Please guide me.

    You fill the mandt field like SNDRPRT, RCVRPRT and others in the mapping and you can take care of rest in the R/3 side.
    You could fill up it in mapping and apply the Check box as mark for considering the control record from Payload in communication channel. Just pass the mandatory fields as you have used the details to configure the prtner profile and port.
    You could also specify the Adapter specific attributes with the same logical system name in Busines system or service that could fill-up the control records internally.
    Refer
    http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/frameset.htm
    SAP Network Blog: Manipulating Idoc Control Records from Payload
    Manipulating Idoc Control Records from Payload
    changing IDOC control record by XSL Mapping

  • Serialize ---- Proxy to Idoc scenario

    Hi Folks,
                I m using Proxy to Idoc scenario and am trigerring proxy messages one after other from my function module on the outbound side. However sometimes idoc2 gets posted before idoc1.
    My requirement is that idoc2 to be processed only after idoc1 is successfully posted. Where and how do I serialize the idoc processing?
    --- AKJ

    Hi,
    This issue is basically at ur receiver IDoc side, when its getting processed.
    To ensure, ur IDoc 2 gets processed only after IDoc 1, changes can be done during message mapping.
    During mapping, inside control records of target IDoc, there is an 'serial' field. Fill this 'serial' field with a new unique number which increases with each and every new IDoc creation.
    This serial field with increasing number will be used during processing of IDocs in a sequence.
    Refer SAP Note - 752194 & 152239 for more details..
    Please let me know if still there are any issues.
    Thanks,
    Anoop

Maybe you are looking for