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

Technology to be used for IDOC generation ALE

hi sir/medam

i m fresher in ale ..plz tel about ale nd where use ale for some details..nd how creat idoc and how use in ale..

tahnks

mukesh goyal

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Nov 20, 2007 at 07:59 AM

    Hi

    Application Linking Enabling - Purpose:

    Application Link Enabling (ALE) supports the distribution of business functions and processes across loosely coupled R/3 Systems. Connections from R/2 and non-SAP systems are supported.

    Implementation Considerations:

    Distributing business applications and at the same time ensuring data consistency is practical because:

    The increasing globalization of markets has led to the physical division of organizational units.

    Business processes are not restricted to one organization only and an increasing number of customers and vendors are involved.

    The performance of an R/3 System can be improved by distributing the business applications.

    Features:

    ALE supports the configuration and operation of distributed applications. ALE supports the configuration and operation of distributed applications. ALE handles the Message Exchange

    Between Distributed Applications across loosely coupled R/3-System, ensuring that data is always consistent.

    Applications are integrated using a local database rather than a central one. There is no data retention. ALE ensures data is distributed and coordinated using asynchronous communication. ALE uses synchronous connections for reading data.

    ALE supports:

    ?

    Distribution of applications between different releases of R/3 Systems

    Continued data exchange after a release upgrade without requiring special maintenance

    Customer-specific extensions

    Communication interfaces that allow connections to non-SAP systems

    Coupling of R/3 and R/2 Systems

    ALE has functions for controlling messages flows (Audit) and for eliminating malfunctions.

    ALE and R/3 Procedure Model:

    The R/3 Procedure Model provides cross-application information required for implementing R/3 software. The model is like a phase model whereby work steps are assigned to each phase and one or more Customizing works steps are associated with each phase.When implementing ALE functions you should refer to the R/3 procedure model to ensure that R/3 is implemented in a well structured way.

    If ALE is to be supported in an R/3 System installation, implementation of the R/3 procedure model is affected at four points:

    ?Determining functions and processes

    Specifying global settings

    Modeling company structure

    Modeling control data and master data

    If ALE business processes are supported, functions and processes must be defined on a cross-system basis. The message types exchanged between the systems are described in the distribution model. When defining organizational units like company codes and plants in the R/3 System, it is important to note that these have to be unique worldwide, across all systems. For example, the plant 0001 can only exist in one R/3 System.

    Message Exchange between Distributed Applications:

    Purpose:

    The basis for distributing application functions is asynchronous message exchange via ALE outbound and inbound processing.

    Prerequisites:

    Data exchange is based on IDoc. IDoc are created and dispatched by message types and by methods in distributed systems.

    Process Flow:

    An application creates a master IDoc containing the relevant data. The IDoc is passed to the ALE layer where it is prepared for dispatch. After the IDoc has been successfully transferred it is read by the target system and inbound processing is triggered. The data is processed either fully automatically or part manually according to the settings until is posted in the application.

    Inbound and outbound processing can either be carried out for each individual IDoc or by massprocessing, whereby several IDoc are bundled together in one packet and processed in one step.

    IDoc Definition:

    An intermediate document (IDoc) is a container for exchanging data between R/3, R/2 and non-SAP systems.

    Use:

    ALE uses IDoc to exchange data between logical systems. Non SAP-systems can use IDoc as the standard interface for data transfer. IDoc are created by message types and (object) methods when data is to be distributed.

    Structure:

    An IDoc represents a configuration of an IDoc type that determines the IDoc structure. An IDoc consists of a header, several data segments and status records.The functions of the individual elements of an IDoc are as follows:

    The contents, structure, sender, receiver and current status of the IDoc are defined in the IDoc header.

    Each data segment contains a standard header consisting of a sequential segment

    number, a description of the segment type and a 1000 character long string field

    containing the actual data of the segment.

    ?The status records show the history of the processing steps applied to the IDoc so far.

    The structure of the IDoc is recorded in the SAP System. The structure definition covers the

    following:

    The segment sequence. Hierarchical relationships between segments are possible.

    The number of times a segment can occur is specified for each segment, as is

    whether the segment is a mandatory segment or an optional segment.

    The fields contained in a segment. In the example shown above the IDoc contains a

    header segment that has to be the first segment of the message.

    Thereafter there must be at least one additional item. The following conditions apply:

    Each item must be followed by at least one sub-item and at most 99

    Up to 9999 text segments can appear after an item's sub-items (optional)

    The last segment in a message must be an accumulation segment (ACCUM)

    An IDoc can only contain character fields.

    Modeling Distribution:

    Purpose:

    To implement the distribution of business application processes and functions using ALE you need to construct a logical Distribution Model of the whole system. Within the framework of this configuration customers can specify what applications are to run on what systems and what messages are to be exchanged between the applications .

    Distribution Model:

    Definition: The distribution model describes the ALE message flows between logical systems.

    Use:

    You can specify the relationships between logical systems, message types, BAPIs and filters inthe distribution model. Applications and the ALE layer use the model to determine the receivers and to control data distribution.

    Structure:

    In the distribution model you can specify the messages to be sent to a logical system. You can also define requirements for message content and dispatch in the Filters. The distribution model consists of one or more views that you can define. With more complex distribution tasks you can assign business sub-areas or groups of logical systems to separate views. To ensure correct functioning the relevant views of the distribution model must be available in all the logical systems involved in ALE. You can find the functions for distributing views in Customizing for ALE.

    Please go thru the below links

    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

    for ALE/IDOC configurations plz check the following thread:

    Application Linking Enabling - Purpose:

    Application Link Enabling (ALE) supports the distribution of business functions and processes across loosely coupled R/3 Systems. Connections from R/2 and non-SAP systems are supported.

    Implementation Considerations:

    Distributing business applications and at the same time ensuring data consistency is practical because:

    The increasing globalization of markets has led to the physical division of organizational units.

    Business processes are not restricted to one organization only and an increasing number of customers and vendors are involved.

    The performance of an R/3 System can be improved by distributing the business applications.

    Features:

    ALE supports the configuration and operation of distributed applications. ALE supports the configuration and operation of distributed applications. ALE handles the Message Exchange

    Between Distributed Applications across loosely coupled R/3-System, ensuring that data is always consistent.

    Applications are integrated using a local database rather than a central one. There is no data retention. ALE ensures data is distributed and coordinated using asynchronous communication. ALE uses synchronous connections for reading data.

    ALE supports:

    ?

    Distribution of applications between different releases of R/3 Systems

    Continued data exchange after a release upgrade without requiring special maintenance

    Customer-specific extensions

    Communication interfaces that allow connections to non-SAP systems

    Coupling of R/3 and R/2 Systems

    ALE has functions for controlling messages flows (Audit) and for eliminating malfunctions.

    ALE and R/3 Procedure Model:

    The R/3 Procedure Model provides cross-application information required for implementing R/3 software. The model is like a phase model whereby work steps are assigned to each phase and one or more Customizing works steps are associated with each phase.When implementing ALE functions you should refer to the R/3 procedure model to ensure that R/3 is implemented in a well structured way.

    If ALE is to be supported in an R/3 System installation, implementation of the R/3 procedure model is affected at four points:

    ?Determining functions and processes

    Specifying global settings

    Modeling company structure

    Modeling control data and master data

    If ALE business processes are supported, functions and processes must be defined on a cross-system basis. The message types exchanged between the systems are described in the distribution model. When defining organizational units like company codes and plants in the R/3 System, it is important to note that these have to be unique worldwide, across all systems. For example, the plant 0001 can only exist in one R/3 System.

    Message Exchange between Distributed Applications:

    Purpose:

    The basis for distributing application functions is asynchronous message exchange via ALE outbound and inbound processing.

    Prerequisites:

    Data exchange is based on IDoc. IDoc are created and dispatched by message types and by methods in distributed systems.

    Process Flow:

    An application creates a master IDoc containing the relevant data. The IDoc is passed to the ALE layer where it is prepared for dispatch. After the IDoc has been successfully transferred it is read by the target system and inbound processing is triggered. The data is processed either fully automatically or part manually according to the settings until is posted in the application.

    Inbound and outbound processing can either be carried out for each individual IDoc or by massprocessing, whereby several IDoc are bundled together in one packet and processed in one step.

    IDoc Definition:

    An intermediate document (IDoc) is a container for exchanging data between R/3, R/2 and non-SAP systems.

    Use:

    ALE uses IDoc to exchange data between logical systems. Non SAP-systems can use IDoc as the standard interface for data transfer. IDoc are created by message types and (object) methods when data is to be distributed.

    Structure:

    An IDoc represents a configuration of an IDoc type that determines the IDoc structure. An IDoc consists of a header, several data segments and status records.The functions of the individual elements of an IDoc are as follows:

    The contents, structure, sender, receiver and current status of the IDoc are defined in the IDoc header.

    Each data segment contains a standard header consisting of a sequential segment

    number, a description of the segment type and a 1000 character long string field

    containing the actual data of the segment.

    ?The status records show the history of the processing steps applied to the IDoc so far.

    The structure of the IDoc is recorded in the SAP System. The structure definition covers the

    following:

    The segment sequence. Hierarchical relationships between segments are possible.

    The number of times a segment can occur is specified for each segment, as is

    whether the segment is a mandatory segment or an optional segment.

    The fields contained in a segment. In the example shown above the IDoc contains a

    header segment that has to be the first segment of the message.

    Thereafter there must be at least one additional item. The following conditions apply:

    Each item must be followed by at least one sub-item and at most 99

    Up to 9999 text segments can appear after an item's sub-items (optional)

    The last segment in a message must be an accumulation segment (ACCUM)

    An IDoc can only contain character fields.

    Modeling Distribution:

    Purpose:

    To implement the distribution of business application processes and functions using ALE you need to construct a logical Distribution Model of the whole system. Within the framework of this configuration customers can specify what applications are to run on what systems and what messages are to be exchanged between the applications .

    Distribution Model:

    Definition: The distribution model describes the ALE message flows between logical systems.

    Use:

    You can specify the relationships between logical systems, message types, BAPIs and filters inthe distribution model. Applications and the ALE layer use the model to determine the receivers and to control data distribution.

    Structure:

    In the distribution model you can specify the messages to be sent to a logical system. You can also define requirements for message content and dispatch in the Filters. The distribution model consists of one or more views that you can define. With more complex distribution tasks you can assign business sub-areas or groups of logical systems to separate views. To ensure correct functioning the relevant views of the distribution model must be available in all the logical systems involved in ALE. You can find the functions for distributing views in Customizing for ALE.

    Please go thru the below links

    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

    for ALE/IDOC configurations plz check the following thread:

    Application Linking Enabling - Purpose:

    Application Link Enabling (ALE) supports the distribution of business functions and processes across loosely coupled R/3 Systems. Connections from R/2 and non-SAP systems are supported.

    Implementation Considerations:

    Distributing business applications and at the same time ensuring data consistency is practical because:

    The increasing globalization of markets has led to the physical division of organizational units.

    Business processes are not restricted to one organization only and an increasing number of customers and vendors are involved.

    The performance of an R/3 System can be improved by distributing the business applications.

    Features:

    ALE supports the configuration and operation of distributed applications. ALE supports the configuration and operation of distributed applications. ALE handles the Message Exchange

    Between Distributed Applications across loosely coupled R/3-System, ensuring that data is always consistent.

    Applications are integrated using a local database rather than a central one. There is no data retention. ALE ensures data is distributed and coordinated using asynchronous communication. ALE uses synchronous connections for reading data.

    ALE supports:

    ?

    Distribution of applications between different releases of R/3 Systems

    Continued data exchange after a release upgrade without requiring special maintenance

    Customer-specific extensions

    Communication interfaces that allow connections to non-SAP systems

    Coupling of R/3 and R/2 Systems

    ALE has functions for controlling messages flows (Audit) and for eliminating malfunctions.

    ALE and R/3 Procedure Model:

    The R/3 Procedure Model provides cross-application information required for implementing R/3 software. The model is like a phase model whereby work steps are assigned to each phase and one or more Customizing works steps are associated with each phase.When implementing ALE functions you should refer to the R/3 procedure model to ensure that R/3 is implemented in a well structured way.

    If ALE is to be supported in an R/3 System installation, implementation of the R/3 procedure model is affected at four points:

    ?Determining functions and processes

    Specifying global settings

    Modeling company structure

    Modeling control data and master data

    If ALE business processes are supported, functions and processes must be defined on a cross-system basis. The message types exchanged between the systems are described in the distribution model. When defining organizational units like company codes and plants in the R/3 System, it is important to note that these have to be unique worldwide, across all systems. For example, the plant 0001 can only exist in one R/3 System.

    Message Exchange between Distributed Applications:

    Purpose:

    The basis for distributing application functions is asynchronous message exchange via ALE outbound and inbound processing.

    Prerequisites:

    Data exchange is based on IDoc. IDoc are created and dispatched by message types and by methods in distributed systems.

    Process Flow:

    An application creates a master IDoc containing the relevant data. The IDoc is passed to the ALE layer where it is prepared for dispatch. After the IDoc has been successfully transferred it is read by the target system and inbound processing is triggered. The data is processed either fully automatically or part manually according to the settings until is posted in the application.

    Inbound and outbound processing can either be carried out for each individual IDoc or by massprocessing, whereby several IDoc are bundled together in one packet and processed in one step.

    IDoc Definition:

    An intermediate document (IDoc) is a container for exchanging data between R/3, R/2 and non-SAP systems.

    Use:

    ALE uses IDoc to exchange data between logical systems. Non SAP-systems can use IDoc as the standard interface for data transfer. IDoc are created by message types and (object) methods when data is to be distributed.

    Structure:

    An IDoc represents a configuration of an IDoc type that determines the IDoc structure. An IDoc consists of a header, several data segments and status records.The functions of the individual elements of an IDoc are as follows:

    The contents, structure, sender, receiver and current status of the IDoc are defined in the IDoc header.

    Each data segment contains a standard header consisting of a sequential segment

    number, a description of the segment type and a 1000 character long string field

    containing the actual data of the segment.

    ?The status records show the history of the processing steps applied to the IDoc so far.

    The structure of the IDoc is recorded in the SAP System. The structure definition covers the

    following:

    The segment sequence. Hierarchical relationships between segments are possible.

    The number of times a segment can occur is specified for each segment, as is

    whether the segment is a mandatory segment or an optional segment.

    The fields contained in a segment. In the example shown above the IDoc contains a

    header segment that has to be the first segment of the message.

    Thereafter there must be at least one additional item. The following conditions apply:

    Each item must be followed by at least one sub-item and at most 99

    Up to 9999 text segments can appear after an item's sub-items (optional)

    The last segment in a message must be an accumulation segment (ACCUM)

    An IDoc can only contain character fields.

    Modeling Distribution:

    Purpose:

    To implement the distribution of business application processes and functions using ALE you need to construct a logical Distribution Model of the whole system. Within the framework of this configuration customers can specify what applications are to run on what systems and what messages are to be exchanged between the applications .

    Distribution Model:

    Definition: The distribution model describes the ALE message flows between logical systems.

    Use:

    You can specify the relationships between logical systems, message types, BAPIs and filters inthe distribution model. Applications and the ALE layer use the model to determine the receivers and to control data distribution.

    Structure:

    In the distribution model you can specify the messages to be sent to a logical system. You can also define requirements for message content and dispatch in the Filters. The distribution model consists of one or more views that you can define. With more complex distribution tasks you can assign business sub-areas or groups of logical systems to separate views. To ensure correct functioning the relevant views of the distribution model must be available in all the logical systems involved in ALE. You can find the functions for distributing views in Customizing for ALE.

    Please go thru the below links

    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

    for ALE/IDOC configurations plz check the following thread:

    Application Linking Enabling - Purpose:

    Application Link Enabling (ALE) supports the distribution of business functions and processes across loosely coupled R/3 Systems. Connections from R/2 and non-SAP systems are supported.

    Implementation Considerations:

    Distributing business applications and at the same time ensuring data consistency is practical because:

    The increasing globalization of markets has led to the physical division of organizational units.

    Business processes are not restricted to one organization only and an increasing number of customers and vendors are involved.

    The performance of an R/3 System can be improved by distributing the business applications.

    Features:

    ALE supports the configuration and operation of distributed applications. ALE supports the configuration and operation of distributed applications. ALE handles the Message Exchange

    Between Distributed Applications across loosely coupled R/3-System, ensuring that data is always consistent.

    Applications are integrated using a local database rather than a central one. There is no data retention. ALE ensures data is distributed and coordinated using asynchronous communication. ALE uses synchronous connections for reading data.

    ALE supports:

    ?

    Distribution of applications between different releases of R/3 Systems

    Continued data exchange after a release upgrade without requiring special maintenance

    Customer-specific extensions

    Communication interfaces that allow connections to non-SAP systems

    Coupling of R/3 and R/2 Systems

    ALE has functions for controlling messages flows (Audit) and for eliminating malfunctions.

    ALE and R/3 Procedure Model:

    The R/3 Procedure Model provides cross-application information required for implementing R/3 software. The model is like a phase model whereby work steps are assigned to each phase and one or more Customizing works steps are associated with each phase.When implementing ALE functions you should refer to the R/3 procedure model to ensure that R/3 is implemented in a well structured way.

    If ALE is to be supported in an R/3 System installation, implementation of the R/3 procedure model is affected at four points:

    ?Determining functions and processes

    Specifying global settings

    Modeling company structure

    Modeling control data and master data

    If ALE business processes are supported, functions and processes must be defined on a cross-system basis. The message types exchanged between the systems are described in the distribution model. When defining organizational units like company codes and plants in the R/3 System, it is important to note that these have to be unique worldwide, across all systems. For example, the plant 0001 can only exist in one R/3 System.

    Message Exchange between Distributed Applications:

    Purpose:

    The basis for distributing application functions is asynchronous message exchange via ALE outbound and inbound processing.

    Prerequisites:

    Data exchange is based on IDoc. IDoc are created and dispatched by message types and by methods in distributed systems.

    Process Flow:

    An application creates a master IDoc containing the relevant data. The IDoc is passed to the ALE layer where it is prepared for dispatch. After the IDoc has been successfully transferred it is read by the target system and inbound processing is triggered. The data is processed either fully automatically or part manually according to the settings until is posted in the application.

    Inbound and outbound processing can either be carried out for each individual IDoc or by massprocessing, whereby several IDoc are bundled together in one packet and processed in one step.

    IDoc Definition:

    An intermediate document (IDoc) is a container for exchanging data between R/3, R/2 and non-SAP systems.

    Use:

    ALE uses IDoc to exchange data between logical systems. Non SAP-systems can use IDoc as the standard interface for data transfer. IDoc are created by message types and (object) methods when data is to be distributed.

    Structure:

    An IDoc represents a configuration of an IDoc type that determines the IDoc structure. An IDoc consists of a header, several data segments and status records.The functions of the individual elements of an IDoc are as follows:

    The contents, structure, sender, receiver and current status of the IDoc are defined in the IDoc header.

    Each data segment contains a standard header consisting of a sequential segment

    number, a description of the segment type and a 1000 character long string field

    containing the actual data of the segment.

    ?The status records show the history of the processing steps applied to the IDoc so far.

    The structure of the IDoc is recorded in the SAP System. The structure definition covers the

    following:

    The segment sequence. Hierarchical relationships between segments are possible.

    The number of times a segment can occur is specified for each segment, as is

    whether the segment is a mandatory segment or an optional segment.

    The fields contained in a segment. In the example shown above the IDoc contains a

    header segment that has to be the first segment of the message.

    Thereafter there must be at least one additional item. The following conditions apply:

    Each item must be followed by at least one sub-item and at most 99

    Up to 9999 text segments can appear after an item's sub-items (optional)

    The last segment in a message must be an accumulation segment (ACCUM)

    An IDoc can only contain character fields.

    Modeling Distribution:

    Purpose:

    To implement the distribution of business application processes and functions using ALE you need to construct a logical Distribution Model of the whole system. Within the framework of this configuration customers can specify what applications are to run on what systems and what messages are to be exchanged between the applications .

    Distribution Model:

    Definition: The distribution model describes the ALE message flows between logical systems.

    Use:

    You can specify the relationships between logical systems, message types, BAPIs and filters inthe distribution model. Applications and the ALE layer use the model to determine the receivers and to control data distribution.

    Structure:

    In the distribution model you can specify the messages to be sent to a logical system. You can also define requirements for message content and dispatch in the Filters. The distribution model consists of one or more views that you can define. With more complex distribution tasks you can assign business sub-areas or groups of logical systems to separate views. To ensure correct functioning the relevant views of the distribution model must be available in all the logical systems involved in ALE. You can find the functions for distributing views in Customizing for ALE.

    Please go thru the below links

    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

    for ALE/IDOC configurations plz check the following thread:

    Application Linking Enabling - Purpose:

    Application Link Enabling (ALE) supports the distribution of business functions and processes across loosely coupled R/3 Systems. Connections from R/2 and non-SAP systems are supported.

    Implementation Considerations:

    Distributing business applications and at the same time ensuring data consistency is practical because:

    The increasing globalization of markets has led to the physical division of organizational units.

    Business processes are not restricted to one organization only and an increasing number of customers and vendors are involved.

    The performance of an R/3 System can be improved by distributing the business applications.

    Features:

    ALE supports the configuration and operation of distributed applications. ALE supports the configuration and operation of distributed applications. ALE handles the Message Exchange

    Between Distributed Applications across loosely coupled R/3-System, ensuring that data is always consistent.

    Applications are integrated using a local database rather than a central one. There is no data retention. ALE ensures data is distributed and coordinated using asynchronous communication. ALE uses synchronous connections for reading data.

    ALE supports:

    ?

    Distribution of applications between different releases of R/3 Systems

    Continued data exchange after a release upgrade without requiring special maintenance

    Customer-specific extensions

    Communication interfaces that allow connections to non-SAP systems

    Coupling of R/3 and R/2 Systems

    ALE has functions for controlling messages flows (Audit) and for eliminating malfunctions.

    ALE and R/3 Procedure Model:

    The R/3 Procedure Model provides cross-application information required for implementing R/3 software. The model is like a phase model whereby work steps are assigned to each phase and one or more Customizing works steps are associated with each phase.When implementing ALE functions you should refer to the R/3 procedure model to ensure that R/3 is implemented in a well structured way.

    If ALE is to be supported in an R/3 System installation, implementation of the R/3 procedure model is affected at four points:

    ?Determining functions and processes

    Specifying global settings

    Modeling company structure

    Modeling control data and master data

    If ALE business processes are supported, functions and processes must be defined on a cross-system basis. The message types exchanged between the systems are described in the distribution model. When defining organizational units like company codes and plants in the R/3 System, it is important to note that these have to be unique worldwide, across all systems. For example, the plant 0001 can only exist in one R/3 System.

    Message Exchange between Distributed Applications:

    Purpose:

    The basis for distributing application functions is asynchronous message exchange via ALE outbound and inbound processing.

    Prerequisites:

    Data exchange is based on IDoc. IDoc are created and dispatched by message types and by methods in distributed systems.

    Process Flow:

    An application creates a master IDoc containing the relevant data. The IDoc is passed to the ALE layer where it is prepared for dispatch. After the IDoc has been successfully transferred it is read by the target system and inbound processing is triggered. The data is processed either fully automatically or part manually according to the settings until is posted in the application.

    Inbound and outbound processing can either be carried out for each individual IDoc or by massprocessing, whereby several IDoc are bundled together in one packet and processed in one step.

    IDoc Definition:

    An intermediate document (IDoc) is a container for exchanging data between R/3, R/2 and non-SAP systems.

    Use:

    ALE uses IDoc to exchange data between logical systems. Non SAP-systems can use IDoc as the standard interface for data transfer. IDoc are created by message types and (object) methods when data is to be distributed.

    Structure:

    An IDoc represents a configuration of an IDoc type that determines the IDoc structure. An IDoc consists of a header, several data segments and status records.The functions of the individual elements of an IDoc are as follows:

    The contents, structure, sender, receiver and current status of the IDoc are defined in the IDoc header.

    Each data segment contains a standard header consisting of a sequential segment

    number, a description of the segment type and a 1000 character long string field

    containing the actual data of the segment.

    ?The status records show the history of the processing steps applied to the IDoc so far.

    The structure of the IDoc is recorded in the SAP System. The structure definition covers the

    following:

    The segment sequence. Hierarchical relationships between segments are possible.

    The number of times a segment can occur is specified for each segment, as is

    whether the segment is a mandatory segment or an optional segment.

    The fields contained in a segment. In the example shown above the IDoc contains a

    header segment that has to be the first segment of the message.

    Thereafter there must be at least one additional item. The following conditions apply:

    Each item must be followed by at least one sub-item and at most 99

    Up to 9999 text segments can appear after an item's sub-items (optional)

    The last segment in a message must be an accumulation segment (ACCUM)

    An IDoc can only contain character fields.

    Modeling Distribution:

    Purpose:

    To implement the distribution of business application processes and functions using ALE you need to construct a logical Distribution Model of the whole system. Within the framework of this configuration customers can specify what applications are to run on what systems and what messages are to be exchanged between the applications .

    Distribution Model:

    Definition: The distribution model describes the ALE message flows between logical systems.

    Use:

    You can specify the relationships between logical systems, message types, BAPIs and filters inthe distribution model. Applications and the ALE layer use the model to determine the receivers and to control data distribution.

    Structure:

    In the distribution model you can specify the messages to be sent to a logical system. You can also define requirements for message content and dispatch in the Filters. The distribution model consists of one or more views that you can define. With more complex distribution tasks you can assign business sub-areas or groups of logical systems to separate views. To ensure correct functioning the relevant views of the distribution model must be available in all the logical systems involved in ALE. You can find the functions for distributing views in Customizing for ALE.

    Please go thru the below links

    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

    for ALE/IDOC configurations plz check the following thread:

    IDOC status codes

    This appendix describes the IDOC status codes and the corresponding event severities. For more detailed information about IDOC status codes, refer to the appropriate SAP documentation.

    Note:

    Harmless events are generated only if the specific IDOC was in an error state in the previous polling cycle. Otherwise, no events are generated.

    The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:

    Outbound IDOCs

    Code Error Event Severity SAP Meaning

    02 Yes Error Error passing data to port

    03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK

    04 Yes Error Control information of EDI subsystem

    05 Yes Error Translation

    06 No Harmless Translation

    07 Yes Error Syntax check

    08 No Harmless Syntax check

    09 Yes Error Interchange handling

    10 No Harmless Interchange handling

    11 Yes Error Dispatch

    12, 13, 14 No Harmless OK

    15 Yes Warning Interchange acknowledgement negative

    16 No Harmless Functional acknowledgement

    17 Yes Warning Functional acknowledgement negative

    18 No Harmless Triggering EDI subsystem

    20 Yes Error Triggering EDI subsystem

    22 No Harmless Dispatch OK, acknowledgement still due

    23 Yes Error Retransmission

    24 No Harmless Control information of EDI subsystem

    25 Yes Warning Processing despite syntax error

    26 Yes Error Syntax check

    27 Yes Error ALE error

    29 Yes Error Error in ALE services

    30 No Harmless Ready for dispatch (ALE)

    31 No Harmless IDOC is marked for deletion

    33 No Harmless Original of an IDOC which was edited

    34 Yes Error Error in control record of IDOC

    36 Yes Error Timeout error; electronic signature not performed

    37 Yes Error IDOC added incorrectly

    38 No Harmless IDOC archived

    39 No Harmless Receive confirmed

    40 Yes Error Application document not created in target system

    41 No Harmless Application document created in target document

    The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:

    Inbound IDOCs

    Code Error Event Severity SAP Meaning

    51, 52 Yes Error Posting error

    53 No Harmless Posting successful

    54 Yes Error Error during formal application check

    55 No Harmless Formal application check

    56 Yes Error IDOC with error added

    60 Yes Error Syntax error

    61 Yes Warning Processing despite syntax error

    62 No Harmless IDOC passed to application

    63 Yes Error Error passing IDOC to application

    64 No Harmless IDOC ready to be passed to application

    65 Yes Error ALE error

    68 No Harmless IDOC is marked for deletion

    70 No Harmless Original of an IDOC which was edited

    73 No Harmless IDOC archived

    idoc extension

    Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)

    - Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.

    - Click on Create new and enter a description and press enter.

    - Click on ZIDOCTYPE01 and then on the Create icon.

    - Enter ZIDOCTYPE as the segment type, click on Segment Editor.

    - Enter a description for your segment type and create.

    - Enter a description for your segment, enter each field required in your IDoc and press enter to validate.

    - Save and generate, press back

    - To release the segment choose Goto, Release from the menu.

    - Check the box on the line of your segment.

    - Save, back and enter.

    - Your Idoc type structure should be displayed with your new segment.

    - Save and back.

    - To release the Idoc type choose Extras, Release type from the menu and Yes.

    ALE FUNCTION MODULE ENHANCEMENTS

    Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.

    The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:

    • For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.

    • From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.

    • Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.

    Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.

    All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.

    When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:

    • Execute transaction CMOD.

    • Enter name of project, say CSTMAST1.

    • Click on Create.

    • Enter a description of the project.

    • Save.

    • Click on SAP Enhancements.

    • Enter VSV00001 for Enhancement.

    • Save.

    Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.

    As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.

    The two important factors to consider while developing the customer function are:

    1. The point in the ALE function module where the function exit occurs

    2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.

    Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.

    Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.

    Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.

    Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:

    • From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.

    • Find Customer Function 001.

    • Double-click on 001.

    • The function EXIT_SAPLVV01_001 will be displayed.

    • Double-click on INCLUDE ZXVSVU01.

    • You will be asked to create a new include object. Proceed as desired.

    • Enter code (as in Listing 1).

    • Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).

    Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.

    To maintain the contact personâs business address of a customer:

    • Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.

    • Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.

    With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.

    Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.

    The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.

    Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.

    also refer 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

    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


    reward is uesfull

    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.