Skip to Content
author's profile photo Former Member
Former Member

ALE IDOC

Hello viewers

I am lalitha i wanted to know about ale idoc

can i get any material regarding ALE IDOC with examples or any site id where i can get to learn in detailed about ALE IDOC.

ThankU

withregards .

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 07, 2008 at 06:10 PM
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 08, 2008 at 05:11 AM

    hi lalitha,

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

    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 if it is usful,

    Thanks,

    Srikanth.A

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 08, 2008 at 05:15 AM

    ALE (Application Linking and Enabling)

    Ale Technology is SAP’s technology to support distributed yet integrated processes across several SAP systems.

    Distributed Process:

    A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.

    Need for Distributed Process:

    • Business in Different Geographical Locations.

    • Non availability of dedicated network.

    • Cultural and language differences in Geographical locations.

    • Running of Mission-critical Applications (Like Maintenance downtime etc.).

    • Separate up gradation of Modules.

    Distributed SAP SYSTEM – CHALLENGES

    • A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.

    • Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.

    • Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.

    • Receiving systems that can handle their own problems and not tie up the sending system.

    • Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.

    • A sound technology and methodology that can be used in all distribution scenarios.

    SAP Distributed environment:

    ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.

    ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.

    Benefits of ALE:

    • Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.

    • Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.

    • Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.

    ALE Architecture:

    It consists of an Outbound process, an Inbound process, and an Exception – Handling process.

    Outbound Process:

    ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.

    1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.

    2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.

    3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.

    4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.

    Inbound Process:

    The inbound process receives an IDoc and creates a document in the system.

    1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.

    2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.

    3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.

    Over view of IDocs:

    IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.

    IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDoc’s definition and IDoc Data is an instance of the IDoc Type.

    IDoc Types:

    IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.

    An IDoc is an instance of an IDoc Type and consists of three types of records.

    i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.

    ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.

    iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.

    Message in IDoc Type:

    A Message represents a specific type of document transmitted between two partners.

    Outbound Process in IDocs:

    Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.

    The Customer Model:

    A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.

    Message control:

    Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.

    Change Pointers:

    The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.

    Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.

    IDoc Structure:

    A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.

    Selection Program:

    Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection program’s design depends on the triggering mechanism used in the process.

    Filter Objects;

    Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.

    Port Definition:

    A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.

    RFC Destination:

    The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.

    Partner Profile:

    A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDoc’s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.

    Service Programs and Configuration Tables:

    The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.

    Process flow for Distributing Transactional Data:

    Transactional data is distributed using two techniques: with Message control and without message control.

    Process flow for Distributing Master Data:

    Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.

    Triggering the Outbound Process via Stand-Alone Programs:

    Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.

    The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.

    Triggering the Outbound Process via Change Pointers:

    The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.

    A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.

    Processing in the Application Layer:

    The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.

    Processing in the ALE Interface Layer:

    Processing in the ALE Layer consists of the following steps:

    • Receiver Determination: The determination of the receiver is done through Customer Distribution Model.

    • IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.

    • Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.

    • Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.

    • Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.

    • Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.

    • Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).

    • Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc – Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch – ALE Service).

    • IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).

    Processing in the Communication Layer:

    To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.

    Inbound Process in IDocs:

    An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.

    Posting Program:

    Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.

    Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.

    Workflow:

    A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.

    Partner Profile;

    A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.

    Process flow for the Inbound process via a Function Module:

    In this process, IDocs are received from another system and passed to the posting function module directly.

    1. Processing in the communication Layer:

    The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.

    2. Processing in the ALE/EDI Interface Layer:

    • Basic integrity check: A basic integrity check is performed on the control record.

    • Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.

    • Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc – Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).

    • IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).

    • IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.

    3. Processing in the Posting Module:

    The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.

    The results of execution are passed back via the function module’s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

    Reward Points if helpful.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 08, 2008 at 11:37 AM

    Hi,

    see this if it is helpful.

    ALE IDOC

    Sending System(Outbound ALE Process)

    Tcode SALE - for

    a) Define Logical System

    b) Assign Client to Logical System

    Tcode SM59-RFC Destination

    Tcode BD64 - Create Model View

    Tcode BD82 - Generate partner Profiles & Create Ports

    Tcode BD64 - Distribute the Model view

    Message Type MATMAS

    Tcode BD10 - Send Material Data

    Tcode WE05 - Idoc List for watching any Errors

    Receiving System(Inbound ALE )

    Tcode SALE - for

    a) Define Logical System

    b) Assign Client to Logical System

    Tcode SM59-RFC Destination

    Tcode BD64 - Check for Model view whether it has distributed or not

    Tcode BD82 -- Generate partner Profiles & Create Ports

    Tcode BD11 Getting Material Data

    Tcode WE05 - Idoc List for inbound status codes

    ALE IDOC Steps

    Sending System(Outbound ALE Process)

    Tcode SALE ?3 for

    a) Define Logical System

    b) Assign Client to Logical System

    Tcode SM59-RFC Destination

    Tcode BD64 - Create Model View

    Tcode BD82 - Generate partner Profiles & Create Ports

    Tcode BD64 - Distribute the Model view

    This is Receiving system Settings

    Receiving System(Inbound ALE )

    Tcode SALE - for

    a) Define Logical System

    b) Assign Client to Logical System

    Tcode SM59-RFC Destination

    Tcode BD64 - Check for Model view whether it has distributed or not

    Tcode BD82 -- Generate partner Profiles & Create Ports

    Tcode BD11 Getting Material Data

    Tcode WE05 - Idoc List for inbound status codes

    Message Type MATMAS

    Tcode BD10 - Send Material Data

    Tcode WE05 - Idoc List for watching any Errors

    1)a Goto Tcode SALE

    Click on Sending & Receiving Systems-->Select Logical Systems

    Here Define Logical Systems---> Click on Execute Button

    go for new entries

    1) System Name : ERP000

    Description : Sending System

    2) System Name : ERP800

    Description : Receiving System

    press Enter & Save

    it will ask Request

    if you want new request create new Request orpress continue for transfering the objects

    B) goto Tcode SALE

    Select Assign Client to Logical Systems-->Execute

    000--> Double click on this

    Give the following Information

    Client : ERP 000

    City :

    Logical System

    Currency

    Client role

    Save this Data

    Step 2) For RFC Creation

    Goto Tcode SM59-->Select R/3 Connects

    Click on Create Button

    RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles

    give the information for required fields

    RFC Destination : ERP800

    Connection type: 3

    Description

    Target Host : ERP000

    System No:000

    lan : EN

    Client : 800

    User : Login User Name

    Password:

    save this & Test it & RemortLogin

    3)

    Goto Tcode BD64 -- click on Change mode button

    click on create moduleview

    short text : xxxxxxxxxxxxxx

    Technical Neme : MODEL_ALV

    save this & Press ok

    select your just created modelview Name :'MODEL_ALV'.

    goto add message type

    Model Name : MODEL_ALV

    sender : ERP000

    Receiver : ERP800

    Message type :MATMAS

    save & Press Enter

    4) Goto Tcode BD82

    Give Model View : MODEL_ALV

    Partner system : ERP800

    execute this by press F8 Button

    it will gives you sending system port No :A000000015(Like)

    5) Goto Tcode BD64

    seelct the modelview

    goto >edit >modelview-->distribute

    press ok & Press enter

    6)goto Tcode : BD10 for Material sending

    Material : mat_001

    Message Type : MATMAS

    Logical System : ERP800

    and Execute

    7)goto Tcode : BD11 for Material Receiving

    Material : mat_001

    Message Type : MATMAS

    and Execute --> 1 request idoc created for message type Matmas

    press enter

    Here Master Idoc set for Messge type MATMAS-->press Enter

    1 Communication Idoc generated for Message Type

    this is your IDOC

    Change Pointers

    I know how to change the description of a material using ALE Change Pointers.

    I will give the following few steps

    1) Tcode BD61---> check the change pointers activated check box

    save and goback.

    2) Tcode BD50---> check the MATMAS check box save and comeback.

    3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.

    4) Tcode BD52---> give message type : matmas press ok button.

    select all what ever you want and delete remaining fields.

    save & come back.

    5) 5) go to Tcode MM02 select one material and try to change the description and save it

    it will effects the target systems material desciption will also changes

    6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute

    give Message type : MATMAS and Executte

    ALE/IDOC Status Codes/Messages

    -


    01 Error --> Idoc Added

    30 Error --> Idoc ready for dispatch(ALE Service)

    then goto SE38 --> Execute the Program RBDMIDOC

    29 Error --> ALE Service Layer

    then goto SE38 --> Execute the Program RSEOUT00

    03 Error --> Data Passed to Port ok

    then goto SE38 --> Execute the Program RBDMOIND

    12 Error --> Dispatch ok

    Inbound Status Codes

    50 Error --> It will go for ALE Service Layer

    56 Error --> Idoc with Errors added

    51 Error --> Application Document not posted

    65 Error --> Error in ALE Service Layer

    for 51 or 56 Errors do the following steps

    goto WE19 > give the IDOC Number and Execute >

    Press on Inbound function Module

    for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error

    with regards,

    sowjanya.gosala.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 08, 2008 at 12:58 PM
    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.