Handling messages for IDOC

Hi all,
Now Iam getting message in Business work place (SBWP) only
for an idoc if partnerprofile is not found.I need to get
messages for every case say when it is processed or with errors etc.. in my inbox.
Please tell me how to go with this problem.
Any help will be appreciated.
regards
chandu.

Hi Sai,
You have to define a workflow which will send the messages in case of any error.
for this first you have to identify the agents or the persons to which the messages have to sent in of the failures and then associate these agents with the workflow.
Then you will be able to get the message in your inbox if you are selected as the agent.
Regards.
Lavanya.

Similar Messages

  • Question concerning How To Handle Acknowledgments for IDoc

    Hello everybody,
    in the document
    https://websmp103.sap-ag.de/~sapdownload/011000358700003477212005E/HowTo_IDOC_Ack_20040817RR.pdf
    it is not explicitly emphasized whether the receiver system has to be a SAP system.
    So my question: Has the receiving system (that send the acknowledgement back) to be a SAP system?
    Regards Mario

    Mario,
    To send Idoc acks's from an SAP system back to an SAP system, these are ther following steps that would be needed.
    1. The Idoc ALEAUD needs to be have an entry in the outbound partner profile of the SAP system. A report needs to be scheduled to send the Ack;'s to XI,.
    2. In XI, an idoc comm channel should be created with respect to the SAP system that is waiting for the acknowledgement.  --> name the comm channel as say idocAckChannel.
    3. Create a receiver agreement for this channel. The sender Service will the SAP system sending the Ack, the receievr service will be the business system for the SAP system receving the ack , the intreface name and namespace make it as *.
    Now, when XI receives the ack from the SAP system, it will look for the Receievr Agreement for this Ack and then use the Ack Comm channel to send the Acknowledegement back.
    Regards,
    Bhavesh

  • Materials for idoc

    Hi am interested to learn about idocs can you provide me some useful links

    Hi saranya srithar  ,
    IDoc is an Intermediate document that holds application data.
    A container used to exchange data
    It is independent of the complex SAP structure to store data.
    It serves as the vehicle for data transfer.
    IDoc Type defines the structure and format in which the data is exchanged.
    It is similar to a structure in SAP
    IDoc data is an instance of IDoc Type
    IDoc  acts as a standard SAP interface to exchange business data through ALE.
    From an SAP system, an IDoc can be sent to and received from
    An SAP R/3 system
    An SAP R/2 system
    An EDI subsystem
    Any third-party application software
    Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
    These r all the t/codes which we will come across in IDocs:
    TCODE     TTEXT
    BD10     Send Material
    BD100     IDoc display object channel view
    BD101     Consistency check
    BD102     Outbound registry
    BD103     Inbound registry
    BD104     maintain tbd53
    BD105     Maintain Supported Business Objects
    BD11     Get Material
    BD12     Send customer
    BD13     Get customer
    BD14     Send vendor
    BD15     Open vendor
    BD16     Send Cost Center
    BD17     Get Cost Center
    BD18     Send General Ledger Account
    BD19     Get General Ledger Account
    BD20     IDoc passed to application
    BD21     Select change pointer
    BD22     Delete change pointers
    BD23     Delete serialization data
    BD24     Send Cost Elements
    BD25     Send Activity Type
    BD26     Get Activity Type
    BD27     Send cost center activity prices
    BD28     Send obj/cost element control data
    BD30     Distribute material object list
    BD31     Distribute document object list
    BD32     Distribute plant allocations(matBOM)
    BD33     Distribute material variants (ALE)
    BD34     Distribute order BOM
    BD35     Send Business Process Groups
    BD36     Send Business Processes
    BD37     Send Business Process Price
    BD40     Read change pointer for group
    BD41     Dispatch IDocs for group
    BD42     Check IDocs for group
    BD43     Post IDocs for group
    BD44     Assign Message Types to Serlz. Group
    BD47     Dependencies between methods
    BD48     Dependency method - message
    BD50     Activate Change Ptrs for Mess. Type
    BD51     Maintain function modules (inbound)
    BD52     Activ.change pointer per chng.doc.it
    BD53     Reduction of Message Types
    BD54     Maintaining Logical Systems
    BD55     Maintain IDoc Conversion
    BD55OLD     Maintain IDoc Conversion
    BD56     Maintain IDoc Segment Filters
    BD57     Maintain link and serialization ty.
    BD58     Convert organizational units
    BD59     Allocation object type -> IDoc type
    BD60     Additional data for message type
    BD61     Activate Change Pointers - Generally
    BD62     Define Segment Conversion Rule
    BD62OLD     Define Segment Conversion Rule
    BD63     Transport ALE Tables of Message Type
    BD64     Maintenance of Distribution Model
    BD65     Maintain IDoc type required fields
    BD66     IDoc type field -> change doc.field
    BD67     Maintain methods (inbound)
    BD68     Maintain Lists
    BD68OLD     Maintain Lists
    BD69     Assignment of Message Type to IDoc
    BD70     Synchronize Number Ranges
    BD71     Define FM for dependent bus. object
    BD72     Activate Events
    BD73     Reposting of IDocs (ALE)
    BD75     Convert IDoc Status
    BD77     Distribution of control data
    BD78     Monitoring control data distribution
    BD79     Maintain IDoc Conversion Rules
    BD79OLD     Maintain IDoc Conversion Rules
    BD81     Filter objects parameter filtering
    BD82     Generate Partner Profiles
    BD83     Send IDocs after an ALE error
    BD84     Post IDocs after ALE error
    BD85     Consistency check for transfer
    BD86     Consistency check for sales
    BD87     Status Monitor for ALE Messages
    BD89     Control data model. - initial screen
    BD91     Send Characteristic
    BD92     Send Class
    BD93     Send Classification
    BD95     Specify ALE object types
    BD96     filter objects of receiver determin.
    BD97     Assign RFC dest. to Logical Systems
    BD98     Consistency Check Workflow Connectn.
    BD99     Message type dependencies
    WE02     Display IDoc
    WE05     IDoc Lists
    WE06     Active IDoc monitoring
    WE07     IDoc statistics
    WE08     Status File Interface
    WE09     Search for IDocs by Content
    WE10     Search for IDoc in Archive
    WE11     Delete IDocs
    WE12     Test Modified Inbound File
    WE14     Test Outbound Processing
    WE15     Test Outbound Processing from MC
    WE16     Test Inbound File
    WE17     Test Status File
    WE18     Generate Status File
    WE19     Test tool
    WE20     Partner Profiles
    WE21     Port definition
    WE23     Verification of IDoc processing
    WE24     DefaultValuesForOutboundParameters
    WE27     DefaultValues for Inbound Parameters
    WE30     IDoc Type Development
    WE31     Development IDoc Segment
    WE32     Development IDoc View
    WE34     Object for Display of XML IDocs
    WE40     IDoc Administration
    WE41     Process codes, outbound
    WE42     Process codes, inbound
    WE43     Funct.module: Status record display
    WE44     Partner Types and Checks
    WE45     Forward (inbound) (V3, EDILOGADR)
    WE46     Error and Status Processing
    WE47     Status Maintenance
    WE50     System process codes: Texts
    WE51     System process codes: Change texts
    WE54     FMs for changing file names
    WE55     Function Module for Path Names
    WE56     IDoc Administration
    WE57     Assignment Messages for Appl. Objs
    WE58     Status process codes: Texts
    WE59     Change status process codes
    WE60     Documentation for IDoc types
    WE61     Documentation for IDoc record types
    WE62     Documentation for segments
    WE63     Documentation
    WE64     Documentation message types
    WE70     Conversion: Basic types
    WE71     Conversion: Extensions
    WE72     Conversion: IDoc types
    WE73     Conversion: Logical messages
    WE81     Logical message types
    WE82     Assign Messages for IDoc Type
    WE84     Assignment of IDoc and appl. fields
    WE85     Create Rule Names
    WEBU     Printing Labels via Assortment List
    WEDI     EDI Basis
    WEINBQUEUE     IDoc Inbound Queue
    WEKF     Purchase order SAP Retail
    WEL0     Forward (inbound) (EDILOGADR)
    WEL1     EDI: Interface Invoice for EDILOGADR
    WELI     Maintain Status Groups
    cheers!
    gyanaraj

  • Sending Acknowledgements for IDOCs

    I have reviewed the document "How To... Handle Acknowledgements for IDOC" and "Configuration Tips for a Business Service/Integration Process to Send Back ALE Audit IDOC".  These don't seem to work for the situation I have.
    We have two R3 systems sending IDOCs to XI, one located in the US and one in Germany.  The above documentation (from what I can tell) expects you to only have one R3 system.  For example, when setting up the Adapter-Specific Identifiers, there is only one spot to enter in the Logical System or R3 System ID.
    Is there a way to set up IDOC Acknowledgements if you have more than one R3 system that can be sending IDOCs?

    Hi Larry,
    for each R/3 create one business system service. Depending of the control data in your idoc (you can examine the sender R/3 system in the IDOc header data) create different receiving systems.
    Regards Mario

  • Did anyone know how to update status for Idoc Finsta01

    Hi ,
    Did anybody did updating idoc status and message for idoc type FINSTA01.
    In Lockbox idoc_input_lockbx.
    If any BADI avilibale fr this to update.
    Thanks,
    Madhu

    Option 1:
    See SAP Help as below you will get the idea-
    Certain IDoc statuses are classified as archivable in the standard system, while others are not. You can display or change this classification.
    The current status of an IDoc must be archivable before the IDoc can be archived.
    Procedure
    Choose SAP Menu -> Tools -> Business Communications -> IDoc Basis -> Control -> Status -> Maintain Status Value.
    To change entries, choose .
    Select the required status. By double-clicking you can call a detail screen, in which you can display or change the archivability.
    By using or you can display or change all statuses one after another.
    Option2: I think it might be possible using generate status file for the outbound IDOC and then change the status in the file further process it. But I am not sure, I just had a look at the Xns in WEDI and made this story
    Thanks,
    Naren

  • Handling acknowledgement for sender idoc from multiple receivers

    Hi,
    Problem: Sender IDOC mapped to multiple FILE receivers. So sender system is SAP, receivers are BS_SYS1, BS_SYS2 and BS_SYS3. The partner profile for IDOC is set as BS_SYS. Due to this, I can enter BS_SYS in the Adapter-Specific Identifiers of one of the services say BS_SYS1. But all three will send acknowledgements and the ack messages for BS_SYS2 and BS_SYS3 error out in MONI due to
    'Unable to convert sender service BS_SYS2 to an ALE logical system' and 'Unable to convert sender service BS_SYS3 to an ALE logical system'. How do I solve this since I am not able to set BS_SYS in all three services/adapter-specific identifiers box at the same time.
    Anyone have this issue before? I am guessing one option is to create logical systems BS_SYS2 and BS_SYS3 in SAP and have the aleaud messages routed to these logical systems. But when there are say scores of receivers, it is a clumsy solution.
    Thanks
    JB

    007,
    nice to have here
    You have alternatives:
    1. Just use one business system with different inbound interfaces / receiver agreements / communication channels and conditions at interface determination
    2. Create a Business Process which is doing the split. This could lead to some minus performance but you would be able to handle the acknowledgements in a senseful way (you get 3 ackn for one send msg)
    Regards,
    Udo

  • Handling Fault Messages for JDBC Receiver (Syn Inbound)

    Dear Freinds,
    Can we handle fault messages for JDBC Receiver which is synchronous.
    OB Proxy Syn  <>  IB JDBC Syn
    1. How to handle the same ? Please give some examples.
    2. Should we use Stored Procedures at Oracle side to handle the fault messages and send back as response to the Proxy Response. Will it work.
    Thanks & Regards
    K.Ramesh

    Dear Friend,
    I have 2 interfaces where Proxy is OB & JDBC is IB. In the first interface both sender and Receiver are synchronous and in the second one it is Async.
    In the first interface i have to send one field from R/3 table along with Native SQL query string to XI and the response of the SELECT query is sent back to the sender.
    Assume if no fields are selected based on the field sent then proper error message has to be sent instead of the response message.
    In the second interface i will be using UPDATE query at Asyn JDBC receiver.
    How to do this if you are having JDBC Receiver.
    I saw in many blogs where they had mentioned that we cannot handle fault messages in the Receiver JDBC.
    KIindly explain.
    Thanks
    K.Ramesh

  • Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 ,214

    Hi friends,
    Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 (Response to a Load Tender)., 214 (Shipment Status )
    For shipement status i got trxstc01 for idoc type .. but its only before 4.6 version ..for 4.7 its not there .. please give the alternate for that ...
    Thanks in Advance ....
    If any one is provide exact answer i will give Max marks ..
    Edited by: ajay KOLLA on Aug 6, 2009 8:04 AM

    Hi,
    Have you resolved this issue. If yes, can you please let me know. Im actually looking for same for EDI 867 (guess it is for summary report and need to know message type, Idoc type associated with this).
    Rgds
    Sudhanshu

  • Message type ,IDOC TYPE , PROCESS CODE for Edi 990

    Hi ,
    Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 (Response to a Load Tender).
    Thanks in Advance.
    Ajay Kolla

    Hi
    Pls check the below links
    1. http://www.erpgenie.com/sap/sapedi/ansi.htm
    2. http://www.erpgenie.com/sap-technical/ale-edi-b2b/master-data-message-types-idoc-types
    Hope this may helps you.
    Regards
    Sirigiri

  • Any Idea Which Message type/Idoc Type should be used for FI Invoice

    Hi Experts,
    Any idea what message type/Idoc type should be used for FI invoice. We are going to send IDOC from R/3 to Non-SAP System using ALE. We are using T-codes FV60/FV65.
    Thanks,
    Sony

    Hi Sony,
    I never dealt with FI IDoc.
    I think you need to setup EDI outgoing payment in IMG. Please take look this report <b>RFFOALE1</b> - ALE Distribution of Payment Data and <b>RFFOEDI1</b> and check also the program documentation.
    Hope this will help.
    Regards,
    Ferry Lianto

  • Workflow notification is not tiggered for IDoc of message type 'WPUWBW'

    Hi All,
            I would like to know the setting up of workflow notification for IDoc message type 'WPUWBW' (idoc of different message type is getting notified). Please provide pointers and also the steps for the above issue.
    Regards,
    PSS

    Hi Ferry,
    System checks for the IDOC version and then calls the EXIT if the versions are different .Following is the code snippet that ensures the above thing in include LBD11F0T :
      Change IDOC version if target <> current version.
      IF  F_EXCEPTION-MSGTY IS INITIAL
        AND (    F_IDOC_CONTROL-IDOCTP <> TARGET_IDOCTP
              OR F_IDOC_CONTROL-CIMTYP <> TARGET_CIMTYP ).
        PERFORM CHANGE_IDOC_VERSION TABLES   T_IDOC_DATA
                                    USING    TARGET_IDOCTP
                                             TARGET_CIMTYP
                                    CHANGING F_IDOC_CONTROL
                                             CHANGED_FLAG
                                             F_EXCEPTION.
      ENDIF.                               "End of  if subrc = 0
    Have you tested it ? Pls suggest if I am wrong somewhere.
    Thanks and Regards
    Gurpreet Singh

  • Do we need to create message interfaces for idocs and rfcs thatare imported

    do we need to create message interfaces for idocs and rfcs thatare imported
    from sap server
    in scenarios from sap system to file or vice versa
    i knew that we need not create message types
    do we also skip creating message interfaces

    hi,
    you create an abstract message interface for IDOC only if you want to use
    them in a BPM (integration process)
    for more about IDOCs have a look at my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • FILE-IDOC, no message no IDOC

    Hi experts..
    iam working in FILE-IDOC scenario.  when the scenario is excuted , the file is picking and archiving in the given directory. but when i check in  SXMB_MONI the message is not cretaed and finally the the IDOC is
    not created in destination system.
    i cheked in RWB --adapter monitaring --the adapetr in sucess status.
    please tell me what could be the reason?
    Regards
    vasavir.

    Hii
    Place a file in the specified source location.
    once the scenario is configured correctly then the adapter picks the file based on the time specified in the pollinterval and process the file.and based on IDX1 IDX2 settings the file is posted to SAP R3.and in R3 check the idoc in WE05 or WE02.
    there you can find the status of the idoc.
    these links will help u for checking ur scenario and error handling :
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
    Error handling in File ---IDOC Scenario
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
    Regards

  • What is the internal  processing for idocs

    Dear friends this is subbu working as a abap consultant.
    can any body explain the how idocs are transfered (inbound process and outbound process)

    1.Here out bound means sender.Inbound mens --receiver.
    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.
    SAP ALE & IDOC<<<<
    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.
    There are two filtering in IDoc.
    Segment Filtering:
    Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
    Data Filtering:
    Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
    Please check this link for more information.
    http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
    Reward points..

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

Maybe you are looking for