Nhi guru's cross apps what is basic type,idoc type , message type

nhi guru's cross apps what is basic type,idoc type , message type  plz help me i am larning how to work on idocs using ale explain me like realtime environment

Hi,
Hi,
i got this data from sdn .plz go thru might be helpful
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
For creating a IDOC u need to Create a segment type in WE31.The internal table in which we store the data to be passed to the IDOc thos fielda are defined in fieldname and data element.Save and release the segment.
Create IDOC type in WE30. Give min and max types. Mark it as mandatory.
Create Message type in WE81.Assign it to a change request and save it.
Link this message type with IDOC type in WE82.
Then start your coding and pass the details of Data and control records.
Just have a look at these links:
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
Creation of IDOC:
idoc creation
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=creation%20of%20idoc&cat=sdn_all&start=11
ALE/ IDOChttp://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
i think this will helps u
<b>reward is usefull</b>

Similar Messages

  • In cross apps what is basic type,idoc type , message type

    in cross apps what is basic type,idoc type , message type  explain to me breflley how to work on realtime plz help me i am learning

    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
    Check these step-by-step links
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287
    https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985

  • What is the process code for message type FIXEDASSET_CREATE?

    Hi all
    please tell me that what is the process code for
    MESSGAE TYPE = FIXEDASSEt_CREATE,
    FUNCTION MODULE = IDOC_INPUT_FIXEDASSET_CREATE,
    BASIC TYPE = FIXEDASSET_CREATE01 ?
    thanx in advance.......
    Edited by: Prachi Sharma on Jan 11, 2008 7:45 AM
    Edited by: Prachi Sharma on Jan 11, 2008 8:03 AM

    Hi,
    Check the Tcodes WE41 and WE42 for Outbound and Inbound process codes
    Check below Tables as well
    EDE1T
    EDE2T
    EDE5T
    EDE6T
    TEDE5
    TEDE6
    Regards,
    Satish

  • What is the process code for Message type FUNDMA

    Hi,
    I am sending CO elements to the distributed server using ALE. Can somebody tell me what is the process code for the message type FUNDMA?
    Thanks
    William

    Check entries of table VEDI_TMSG1. This contains Message types and associated Process codes.
    Hope this helps.
    ashish

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

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

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

  • What is the user exit for message type BENREP, IDoc BENEFIT3?

    Hello,
    We are looking for a user exit to use with IDoc BENEFIT3.  Our benefits provider requires information which is not stored in any infotype in SAP, but can be calculated based on 3 existing infotypes.  We need a user exit for this. 
    We thought we could use PBEN0018 w/function module EXIT_SAPLHRBEN00FEATURE_018, but our ABAP developer says this doesn't access any IDoc tables. HR_BEN_IDOC_SEND doesn't work for this purpose either.  We also found PBEN0033 for function module HR_BEN_GET_IDOC_EVENTS, but this is labeled as obsolete.
    Does anyone know if there is an exit for this?
    Thanks much!
    Anke

    For future reference in case anyone is trying to do this, we were not able to find a suitable user exit to enhance BENEFIT3 IDoc, so we put in an OSS note and received the following response:
    "...currently there is no user exit/Badi in SAP Benefits Administration
    to enhance IDoc BENEFIT3. Such functionality is indeed missing in the
    system, which means that you will need to submit a development
    request to enhance the system in this respect in a future release."
    Anke

  • Basic of IDOC and ALE

    Hi All,
    I am beginner of ALE IDOC.
    Please tell me in details whats is Control Records, Data Records and Status Records in details.
    Thnks in Advance,
    awards will be given.
    Ulhas

    Hi,
    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 u201CThe table is cross-client (see Help for further info)u201D. 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 u201CThe table is cross-client (see Help for further info)u201D. 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)
    u2022 Create a Customer Distribution Model (CDM);
    u2022 Add appropriate message types and filters to the CDM;
    u2022 Generate outbound partner profiles;
    u2022 Distribute the CDM to the receiving systems; and
    u2022 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 u2013 Creating IDoc Type from Change Pointers
    RSEOUT00 u2013 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
    Regards,
    Shiva Kumar

  • What is ale and idoc  after small explanation

    plz send me reply

    Hi,
    Check this info.
    <b>ALE</b>
    ALE means of creating and operating distributed applications.
    Application Link Enabling (ALE) guarantees a distributed, but integrated, R/3 installation. This involves business-controlled message exchange using consistent data across loosely linked SAP applications.
    Applications are integrated using synchronous and asynchronous communication - not by using a central database.
    ALE consists of the following layers:
    Application services
    Distribution services
    Communication services
    Refer
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    Check this link ALE and EDI
    <b>IDOC</b>
    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
    Hope this resolves your query.
    Reward all the helpful answers.
    Regards

  • IDOC question on Message type and Basic Type - Partner Profile

    Hi all,
    I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
    My question is about the setup of Partner Profile creation (WE20).
    When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
    Questions:
    1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables.  I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
    2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
    Thanks.
    tuff

    Tuff,
    Below are my thoughts,
    There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
    OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
    Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order -  ORDRSP.
    And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
    Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
    In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
    2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
    Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
    Regards,
    Chen

  • What is Message Type & IDOC Type?

    He Experts!,
    What is Message Type & IDOC Type? What is the difference between them?
    Thanks in advance.
    Sekhar

    Hi,
    Please try these transaction codes.
    WE82 - Message Type and IDoc Type
    WE64 - Process Codes (Inbound and Outbound) for Message Type.
    Message type. A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterizes the data sent across systems and relates to the structure of the data called an IDOC type (see below). For example, MATMAS is a message type for Material Master, and INVOIC is a message type for an Invoice (Billing Document). ALE supports over 200 message types in R/3 and about 200 application areas.
    IDOC type and IDOC. An Intermediate Document (IDOC) type represents the structure of the data associated with a message type (DEBMAS02 for message type DEBMAS — Customer Master, and WMMBID02 for message type WMMBXY— Goods Movements), while an IDOC is an object containing the data of a particular message type. IDOCs are data containers with intelligence built in. Each IDOC contains one and only one business object. For example, an IDOC of type SHPMNT01, message type SHPMNT, will contain data only of one Shipment Document. Generally, the architecture of an IDOC is independent of the message type by virtue of ALE’s ability to redefine it for any message type.
    Use transaction BD64 or the following menu path to maintain the model: From the IMG (Implementation Guide), Cross-Application Components -> Distribution (ALE) (*) -> Distribution Customer Model -> Maintain Distribution Customer Model Directly -> Maintain Distribution Customer Model Directly.
    Thanks,
    Sankar M

  • What is the use and functionality of a message type

    Hi,
    I am new to abap. Can anybody tell me what is the use of the message type? What is it used for?
    There is an interface which is using an extended idoc type ZFIDCCP02 (Basic Type FIDCCP02). This extended idoc type is used for other interfaces and the interface in question. However the other interfaces are using the standard message type FIDCC2, but the interface in question is using a customized message type.
    Any idea what could be the reason?
    Thanks in advance.
    Mick

    Hi Mick,
    Message type tells the about the actual meaning of Idoc..
    later if you want to send data to external system the idoc type or extension type is not used..
    the message type is used for rest of the process..
    Idoc type is know as structure..
    << Cut and paste without attribution from http://www.*******************/2009_01_01_archive.html removed >>
    << Cut and paste without attribution from http://searchsap.techtarget.com/sDefinition/0,,sid21_gci852485,00.html removed >>
    << Points unassigned >>. 
    Regards,
    Prabhudas
    Edited by: Prabhu Das on May 14, 2009 8:38 PM
    Edited by: Rob Burbank on May 25, 2009 4:30 PM

  • What is  SAP XI  & PO MESSAGE TYPE

    DEAR ALL
    HAPPY NEW YEAR
      I NEED TO KNOW WHAT IS SAP. XI
    WHAT IS MEAN BY P.O. MESSAGE  TYPE
    THANKS IN ADVANCE
    VIVEK

    hi
    SAP Exchange Infrastructure (SAP XI) enables you to implement cross-system processes. It enables you to connect systems from different vendors (non-SAP and SAP) in different versions and implemented in different programming languages (Java, ABAP, and so on) to each other. SAP Exchange Infrastructure is based on an open architecture, uses open standards (in particular those from the XML and Java environments) and offers those services that are essential in a heterogeneous and complex system landscape:
    ●     Modeling and design of messages, transformations, and cross-component integration processes
    ●     Configuration options for managing collaborative processes and message flow
    ●     Runtime for message and process management
    ●     Adapter Engine for integrating heterogeneous system components
    ●     Central monitoring for monitoring message flow and processes
    SAP XI supports internal company scenarios and cross-company scenarios.
    refer following
    http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
    >WHAT IS MEAN BY P.O. MESSAGE TYPE
    it is nothing but nessages used for diffrent outputs of PO  i.e. output types
    e.g.
    ACE1     Import declaration
    AUFB     Dunning ord confirm
    ET01     Material label
    MAHN     Dunning
    NEU     Purchase order
    u can check them in NACE and EF
    regards
    SAP Learner
    WEZL     GR count list

  • CLFMAS Basic type (IDOC)

    Hi,
    BD10 is used to send material master and message type MATMAS can be used for it.
    Like that i want to send data related to basic type CLFMAS01 and message type CLFMAS
    which transaction should i use.
    Rgds,
    Ganesh

    Hello,
    For classification use BD93 transaction but make sure your distribution model is set up.
    <removed by moderator>
    Edited by: Thomas Zloch on Dec 9, 2010 2:43 PM - please do not ask for ...

  • What is fault message type in mapping

    hi folks,
                what is the use of fault message type in message mapping . where do we use them .please spare a little time to type rather to refer to  other blogs. have a nice day

    Hi Bose
    Fault messages are used to propogate / send back the error maessage to the calling application. This is used when there is a failue and the sending system needs to know what the error was. This is more of catching Application Errors.
    Also please go through the link below to get the details for fault messages...
    http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
    fault message is a message that describes an application-specific error situation
    we have standardised fault message in XI.
    Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
    In the synchronous case, when an application-specific error occurs on the inbound side, instead of sending a response message back to the sender, the application can send a fault message to handle the error.
    The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case asynchronous of Java server proxies, the fault message is part of a negative application acknowledgement
    Application-specific means that the application on the inbound side triggers the error itself because, for example, the request message did not contain sufficient information
    See the below links
    http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
    Asynchronus RFC  exception handling
    XI Alerts are not getting triggered from proxy servers
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-a258cf083bca
    /people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
    Fault Message
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    You can use Fault messages when you want to handle errors at the Inbound side ie at the destination side.
    check this nice blog also
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    Fault Messages
    http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
    Usage of Fault Messages in Synchronous interfaces
    /people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
    usage of fault messages in asynchronous interfaces
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    Have a look at "/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client"
    for more details  have a look on  these links
    <b>
    Fault messages -</b> /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    Also ref:
    <b>Handling Web Service SOAP Fault Responses in SAP NetWeaver XI -</b>
    /people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
    check this out
    http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
    demo - /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1 - this is sure to help you.
    Thanks!!!
    Regards
    Abhishek Agrahari

  • EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

    Hi All,
    We are facing some issues regarding EDI 821 and EDI 823 file mappings.
    We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
    EDI 823 - Lock Box
    Basic IDOC type - FINSTA01
    Message type - FINSTA
    Process Code  - FINS
    The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
    EDI 821 -
    Basic IDOC type - PEXR2002
    Message type - PAYEXT OR REMADV
    Process Code  - PEXC OR REMA
    We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
    We are trying different combinations but nothing is working so far.
    I need the following things to proceed furthur.
    1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
    2)If those are not correct, can you please let me know the correct entries
    3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then  I can re check it.
    4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
    thanks in advance for all your help.
    Please let me know if my question is not clear.
    Thanks,
    Ramesh.

    Hi Ramesh,
    I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
    First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
    Are you can give me the exact error and i can help you as well.
    Thanks,
    Mahesh.

Maybe you are looking for