<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Inbound ALE Process in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-ale-process/m-p/3340814#M800854</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Process in Outbound Application Layer&lt;/P&gt;&lt;P&gt;1.	Selection program (Ex: RBDSEMAT / DB10)  reads the master data object from the database and creates a master IDoc and stored in memory.&lt;/P&gt;&lt;P&gt;2.	Program calls ALE service layer by using Function Module MASTER_IDOC_DISTRIBUTE passes the master IDoc and the receiver information. &lt;/P&gt;&lt;P&gt;Process in Outbound ALE Interface Layer&lt;/P&gt;&lt;P&gt;Receiver determination &amp;#150; If receivers are not known, they are determined from the customer distribution model. If receiver is not found, processing ends.&lt;/P&gt;&lt;P&gt;1.	IDoc Filtering&lt;/P&gt;&lt;P&gt;2.	Segment Filtering&lt;/P&gt;&lt;P&gt;3.	Field Conversion&lt;/P&gt;&lt;P&gt;4.	Version Change for Segments &amp;amp;Version Change for IDocs&lt;/P&gt;&lt;P&gt;5.	Communication IDocs Generated&lt;/P&gt;&lt;P&gt;6.	Syntax Check Performed &lt;/P&gt;&lt;P&gt;7.	IDocs Dispatched to the Communication Layer&lt;/P&gt;&lt;P&gt;(Note: It Create Communication IDoc and transfer it to Communication layer by the dispatch program RSEOUT00)&lt;/P&gt;&lt;P&gt;Process in Outbound Communication Layer&lt;/P&gt;&lt;P&gt;1.	To dispatch an IDoc to a destination system&lt;/P&gt;&lt;P&gt;&amp;amp;#61656;	Read Port Definition&lt;/P&gt;&lt;P&gt;&amp;amp;#61656;	Partner Profile for Destination System&lt;/P&gt;&lt;P&gt;&amp;amp;#61656;	Read RFC Destination (Communication Log to Remote SAP System).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.	System Calls INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.&lt;/P&gt;&lt;P&gt;3.	FM invoked are temporarily stored in tables ARFCSSTATE &amp;amp; ARFCSDATA.&lt;/P&gt;&lt;P&gt;4.	ARFC_DEST_SHIP transports the data to the target system.&lt;/P&gt;&lt;P&gt;5.	ARFC_EXECUTE executes the stored function module.&lt;/P&gt;&lt;P&gt;6.	If communication problem occurs, the program RSARFCSE is automatically scheduled to run on a periodic basis to process the specific entry.&lt;/P&gt;&lt;P&gt;7.	Turn this automatic option ON and OFF in the tRFC parameters in RFC destination.&lt;/P&gt;&lt;P&gt;8.	If transmission is successful, entries from ARFCSSTATE &amp;amp; ARFCSDATA tables are deleted.&lt;/P&gt;&lt;P&gt;9.	If automatic option is turned off, you can process failed entries on a mass basis using program RSARFCEX.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 23 Jan 2008 11:17:49 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-23T11:17:49Z</dc:date>
    <item>
      <title>Inbound ALE Process</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-ale-process/m-p/3340812#M800852</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt; please help me in ALE Inbound process also.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2008 11:12:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-ale-process/m-p/3340812#M800852</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-23T11:12:25Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound ALE Process</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-ale-process/m-p/3340813#M800853</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IDOCs:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC is an Intermediate Document'. It is simply a data container used to exchange information &lt;/P&gt;&lt;P&gt;between any two processes that can understand the syntax and semantics of the data.&lt;/P&gt;&lt;P&gt;An IDOC is created as a result of executing an Outbound ALE or EDI process.&lt;/P&gt;&lt;P&gt;In an inbound ALE or EDI process, an IDOC serves as input to create an application document.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.&lt;/P&gt;&lt;P&gt;This number is unique with in the client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOCs are independent of the sending and receiving systems. &lt;/P&gt;&lt;P&gt;IDOCs are independent of the direction of data exchange. &lt;/P&gt;&lt;P&gt;In the IDOCs, data is stored in text format. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC will wait until the Remote System is Active. &lt;/P&gt;&lt;P&gt;*IDOC Definition Components&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-------------------------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basic Idoc Type: Basic Idoc type defines the structure and format of the business document &lt;/P&gt;&lt;P&gt;that is to be exchanged between two systems. Basic Idoc type can refer to an SAP provided&lt;/P&gt;&lt;P&gt;basic IDOC type or a customer developed basic IDOC type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A basic IDOC type has the following characteristics: &lt;/P&gt;&lt;P&gt;Name : A basic Idoc type can be assigned upto a thirty character name.&lt;/P&gt;&lt;P&gt;List of permitted segments: The segments make up the IDOC structure.&lt;/P&gt;&lt;P&gt;Hierarchy of segments : The hierarchy of segments specifies the physical sequence and&lt;/P&gt;&lt;P&gt;any parent - child relationship in the segments.&lt;/P&gt;&lt;P&gt;Mandatory Vs Optional Segments : When used in the IDOC type, each segment has&lt;/P&gt;&lt;P&gt;an attribute that defines whether the segment is option or mandatory.&lt;/P&gt;&lt;P&gt;Minimum/Maximum range for each segment: It defines the maximum and minimum&lt;/P&gt;&lt;P&gt;number of timesa data record corresponding to a segment cn exist in an IDOC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Segments : A segment defines the format and structure of a data record. &lt;/P&gt;&lt;P&gt;Segments are reusable componets. A segment consists of various fields that represent data&lt;/P&gt;&lt;P&gt;in data record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC Run time components: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-------------------------------------------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A unique IDOC number 16 digits is allocated. &lt;/P&gt;&lt;P&gt;One control record is attached to the IDOC. &lt;/P&gt;&lt;P&gt;Segments translate into data records. &lt;/P&gt;&lt;P&gt;Status records are attached. &lt;/P&gt;&lt;P&gt;Sytax rules are checked. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC Record Types: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="-------------------------------------------------------------------------------" /&gt;&lt;P&gt;1. Control Record : The control record contains all of the control information about an IDOC,&lt;/P&gt;&lt;P&gt;this information basically includes the IDOC number, sender and receiver information,&lt;/P&gt;&lt;P&gt;and information such as the message type it represents and the IDOC type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;there is only one control record per IDOC. &lt;/P&gt;&lt;P&gt;The stucture of the control record is the same for all the IDOCs and is defined by SAP. &lt;/P&gt;&lt;P&gt;The structure of the control record is defined by the data dictionary structure EDI_DC40. &lt;/P&gt;&lt;P&gt;The control record is stored in the EDIDC table. &lt;/P&gt;&lt;P&gt;2. Data Record : Data records contain the application data. A data record has two sections&lt;/P&gt;&lt;P&gt;Administrative Section and a Data section.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Administrative section cotain the segment name, client, IDOC number, segment number, &lt;/P&gt;&lt;P&gt;hierarchy level information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Data section of a data record is a stram of 1000 bytes where the actual data resides. &lt;/P&gt;&lt;P&gt;The data record is defined by the data dictionary structure EDI_DD40. &lt;/P&gt;&lt;P&gt;Data records for IDOCs stored in the EDID4 table. &lt;/P&gt;&lt;P&gt;3. Status Record : Status records are attaced to an IDOC throughout the process as&lt;/P&gt;&lt;P&gt;the IDOC achieves different milestones or encounters an error. At every milestone a statu code,&lt;/P&gt;&lt;P&gt;date and time are assigned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for &lt;/P&gt;&lt;P&gt;inbound processes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message Type: Identifies what type of information transformed between logical systems or partners. &lt;/P&gt;&lt;P&gt;Message type is not a local object type , it is transportable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Port : A Port defines the medium in which data is exchanged between the two systems in &lt;/P&gt;&lt;P&gt;the ALE process, IDocs are transferred via memory.&lt;/P&gt;&lt;P&gt;1. TRFC ports are used for ALE communicaion.&lt;/P&gt;&lt;P&gt;2. File Ports used by EDI&lt;/P&gt;&lt;P&gt;3. CPI-C ports used to communicate with R/2 systems.&lt;/P&gt;&lt;P&gt;4. Internet ports used to connect with Internet Applications.&lt;/P&gt;&lt;P&gt;5. ABAP-PI ports used to process data via the ABAP programming interface.&lt;/P&gt;&lt;P&gt;6. XML ports used to process files in XML format.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Partner Profiles: &lt;/P&gt;&lt;P&gt;A partner profile has three views, which maintain different parameters for the partner.&lt;/P&gt;&lt;P&gt;1. The General Parameters View : Values are stored in table EDPP1.&lt;/P&gt;&lt;P&gt;2. The Outbound Parameters view : Values are stored in table EDP13, except for the&lt;/P&gt;&lt;P&gt;Message control parameter , which are stored in table EDP12.&lt;/P&gt;&lt;P&gt;3. The Inbound Parameters View: Values are stored in table EDP21.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Transaction Codes : &lt;/P&gt;&lt;P&gt;WE31- Segment Creation&lt;/P&gt;&lt;P&gt;WE30 - IDOC structure&lt;/P&gt;&lt;P&gt;WE81 - Message type creation&lt;/P&gt;&lt;P&gt;WE82 - Link between Message type and IDOC type.&lt;/P&gt;&lt;P&gt;WE21 - Creation of POrt&lt;/P&gt;&lt;P&gt;WE20 - Partner Profile creation&lt;/P&gt;&lt;P&gt;WE19 - Test tool for IDOC Processing.&lt;/P&gt;&lt;P&gt;SALE - ALE (Application Linking and Enabling) settings&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go through the link for basics related to IDOCs:&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6cdd507d11d18ee90000e8366fc2/plain.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check these links.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap.html" target="test_blank"&gt;http://www.sappoint.com/abap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check this PDF documents for ALE and IDoc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf" target="test_blank"&gt;http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf" target="test_blank"&gt;http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf" target="test_blank"&gt;http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf" target="test_blank"&gt;http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf" target="test_blank"&gt;http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check below link. It will give the step by step procedure for IDOC creation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.supinfo-projects.com/cn/2005/idocs_en/2/" target="test_blank"&gt;http://www.supinfo-projects.com/cn/2005/idocs_en/2/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check these out..&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="2402859"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check below link. It will give the step by step procedure for IDOC creation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.supinfo-projects.com/cn/2005/idocs_en/2/" target="test_blank"&gt;http://www.supinfo-projects.com/cn/2005/idocs_en/2/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ALE/ IDOC&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap.html" target="test_blank"&gt;http://www.sappoint.com/abap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;go trough these links.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap/ale2.pdf" target="test_blank"&gt;http://www.sappoint.com/abap/ale2.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/abap.html" target="test_blank"&gt;http://www.sappoint.com/abap.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc" target="test_blank"&gt;http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419" target="test_blank"&gt;http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/index.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/index.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_sample.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_sample.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2008 11:15:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-ale-process/m-p/3340813#M800853</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-23T11:15:14Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound ALE Process</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-ale-process/m-p/3340814#M800854</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Process in Outbound Application Layer&lt;/P&gt;&lt;P&gt;1.	Selection program (Ex: RBDSEMAT / DB10)  reads the master data object from the database and creates a master IDoc and stored in memory.&lt;/P&gt;&lt;P&gt;2.	Program calls ALE service layer by using Function Module MASTER_IDOC_DISTRIBUTE passes the master IDoc and the receiver information. &lt;/P&gt;&lt;P&gt;Process in Outbound ALE Interface Layer&lt;/P&gt;&lt;P&gt;Receiver determination &amp;#150; If receivers are not known, they are determined from the customer distribution model. If receiver is not found, processing ends.&lt;/P&gt;&lt;P&gt;1.	IDoc Filtering&lt;/P&gt;&lt;P&gt;2.	Segment Filtering&lt;/P&gt;&lt;P&gt;3.	Field Conversion&lt;/P&gt;&lt;P&gt;4.	Version Change for Segments &amp;amp;Version Change for IDocs&lt;/P&gt;&lt;P&gt;5.	Communication IDocs Generated&lt;/P&gt;&lt;P&gt;6.	Syntax Check Performed &lt;/P&gt;&lt;P&gt;7.	IDocs Dispatched to the Communication Layer&lt;/P&gt;&lt;P&gt;(Note: It Create Communication IDoc and transfer it to Communication layer by the dispatch program RSEOUT00)&lt;/P&gt;&lt;P&gt;Process in Outbound Communication Layer&lt;/P&gt;&lt;P&gt;1.	To dispatch an IDoc to a destination system&lt;/P&gt;&lt;P&gt;&amp;amp;#61656;	Read Port Definition&lt;/P&gt;&lt;P&gt;&amp;amp;#61656;	Partner Profile for Destination System&lt;/P&gt;&lt;P&gt;&amp;amp;#61656;	Read RFC Destination (Communication Log to Remote SAP System).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.	System Calls INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.&lt;/P&gt;&lt;P&gt;3.	FM invoked are temporarily stored in tables ARFCSSTATE &amp;amp; ARFCSDATA.&lt;/P&gt;&lt;P&gt;4.	ARFC_DEST_SHIP transports the data to the target system.&lt;/P&gt;&lt;P&gt;5.	ARFC_EXECUTE executes the stored function module.&lt;/P&gt;&lt;P&gt;6.	If communication problem occurs, the program RSARFCSE is automatically scheduled to run on a periodic basis to process the specific entry.&lt;/P&gt;&lt;P&gt;7.	Turn this automatic option ON and OFF in the tRFC parameters in RFC destination.&lt;/P&gt;&lt;P&gt;8.	If transmission is successful, entries from ARFCSSTATE &amp;amp; ARFCSDATA tables are deleted.&lt;/P&gt;&lt;P&gt;9.	If automatic option is turned off, you can process failed entries on a mass basis using program RSARFCEX.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jan 2008 11:17:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-ale-process/m-p/3340814#M800854</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-23T11:17:49Z</dc:date>
    </item>
  </channel>
</rss>

