<?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: Interface in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2947329#M694836</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INBOUND:&lt;/P&gt;&lt;P&gt;Step 1. EDI Subsystem creates an IDoc file from EDI Messages&lt;/P&gt;&lt;P&gt;2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.&lt;/P&gt;&lt;P&gt;3. Data in Control Record is validate against the Partner Profile.&lt;/P&gt;&lt;P&gt;4. IDoc is generated in Database and syntax check is carried out.&lt;/P&gt;&lt;P&gt;5. IDoc file is deleted once file read.&lt;/P&gt;&lt;P&gt;6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow. &lt;/P&gt;&lt;P&gt;7. Check for Process Immediately.&lt;/P&gt;&lt;P&gt;If NO&lt;/P&gt;&lt;P&gt;Execute RBDAPP01 Program&lt;/P&gt;&lt;P&gt;Else&lt;/P&gt;&lt;P&gt;Read Process Code from Partner Profile &lt;/P&gt;&lt;P&gt;Process Code Points to Function Module&lt;/P&gt;&lt;P&gt;Application Document Posted. &lt;/P&gt;&lt;P&gt;further help:&lt;/P&gt;&lt;P&gt;check url&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;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/ale/configuration.htm" target="test_blank"&gt;http://www.sapgenie.com/ale/configuration.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.sapdevelopment.co.uk/training" target="test_blank"&gt;http://www.sapdevelopment.co.uk/training&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And also u can get lots of inof from the below link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/ale/why_ale.htm" target="test_blank"&gt;http://www.sapgenie.com/ale/why_ale.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data Creation in Idoc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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 &lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDoc is a intermediate document to exchange data between two SAP Systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*IDocs are structured ASCII files (or a virtual equivalent). &lt;/P&gt;&lt;P&gt;*Electronic Interchange Document&lt;/P&gt;&lt;P&gt;*They are the file format used by SAP R/3 to exchange data with foreign systems.&lt;/P&gt;&lt;P&gt;*Data Is transmitted in ASCII format, i.e. human readable form&lt;/P&gt;&lt;P&gt;*IDocs exchange messages&lt;/P&gt;&lt;P&gt;*IDocs are used like classical interface files&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC types are templates for specific message types depending on what is the business document, you want to exchange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WE30 - you can create a IDOC type.&lt;/P&gt;&lt;P&gt;An IDOC with data, will have to be triggered by the application that is trying to send out the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FOr testing you can use WE19.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to create idoc?&lt;/P&gt;&lt;P&gt;*WE30 - you can create a IDOC type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more information in details on the same along with the examples can be viewed on:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/presentation.html" target="test_blank"&gt;http://www.sappoint.com/presentation.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_search.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_search.html&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://www.erpgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.erpgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To Create Idoc we need to follow these steps:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create Segment ( WE31)&lt;/P&gt;&lt;P&gt;Create Idoc Type ( WE30 )&lt;/P&gt;&lt;P&gt;Create Message Type ( WE81 )&lt;/P&gt;&lt;P&gt;Assign Idoc Type to Message Type ( WE82 )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Creating a Segment&lt;/P&gt;&lt;P&gt;Go to transaction code WE31&lt;/P&gt;&lt;P&gt;Enter the name for your segment type and click on the Create icon&lt;/P&gt;&lt;P&gt;Type the short text&lt;/P&gt;&lt;P&gt;Enter the variable names and data elements&lt;/P&gt;&lt;P&gt;Save it and go back&lt;/P&gt;&lt;P&gt;Go to Edit -&amp;gt; Set Release&lt;/P&gt;&lt;P&gt;Follow steps to create more number of segments&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create IDOC Type&lt;/P&gt;&lt;P&gt;Go to transaction code WE30&lt;/P&gt;&lt;P&gt;Enter the Object Name, select Basic type and click Create icon&lt;/P&gt;&lt;P&gt;Select the create new option and enter a description for your basic IDOC type and press enter&lt;/P&gt;&lt;P&gt;Select the IDOC Name and click Create icon&lt;/P&gt;&lt;P&gt;The system prompts us to enter a segment type and its attributes&lt;/P&gt;&lt;P&gt;Choose the appropriate values and press Enter&lt;/P&gt;&lt;P&gt;The system transfers the name of the segment type to the IDOC editor.&lt;/P&gt;&lt;P&gt;Follow these steps to add more number of segments to Parent or as Parent-child relation&lt;/P&gt;&lt;P&gt;Save it and go back&lt;/P&gt;&lt;P&gt;Go to Edit -&amp;gt; Set release&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create Message Type&lt;/P&gt;&lt;P&gt;Go to transaction code WE81&lt;/P&gt;&lt;P&gt;Change the details from Display mode to Change mode&lt;/P&gt;&lt;P&gt;After selection, the system will give this message &amp;#147;The table is cross-client (see Help for further info)&amp;#148;. Press Enter&lt;/P&gt;&lt;P&gt;Click New Entries to create new Message Type&lt;/P&gt;&lt;P&gt;Fill details&lt;/P&gt;&lt;P&gt;Save it and go back&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assign Message Type to IDoc Type&lt;/P&gt;&lt;P&gt;Go to transaction code WE82&lt;/P&gt;&lt;P&gt;Change the details from Display mode to Change mode&lt;/P&gt;&lt;P&gt;After selection, the system will give this message &amp;#147;The table is cross-client (see Help for further info)&amp;#148;. Press Enter.&lt;/P&gt;&lt;P&gt;Click New Entries to create new Message Type.&lt;/P&gt;&lt;P&gt;Fill details&lt;/P&gt;&lt;P&gt;Save it and go back&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;&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;&amp;lt;b&amp;gt;: Inbound processing example code&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Debugging inbound FM&amp;lt;/b&amp;gt;Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Maintain ALE attributes&amp;lt;/b&amp;gt;The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Link Message Type to Function Module (WE57) Client independent&amp;lt;/b&amp;gt;To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter transaction WE57 (ALE -&amp;gt; Extensions -&amp;gt; Inbound -&amp;gt; Allocate function module to logical message)&lt;/P&gt;&lt;P&gt;&amp;#149;	Select an entry (EG. IDOC_INPUT_ORDERS) and copy&lt;/P&gt;&lt;P&gt;&amp;#149;	Type in module name Z_IDOC_INPUT_ZINVRV&lt;/P&gt;&lt;P&gt;&amp;#149;	Type in basic IDoc type as ZINVRV01&lt;/P&gt;&lt;P&gt;&amp;#149;	Type in message type as ZINVRV&lt;/P&gt;&lt;P&gt;&amp;#149;	Type object type as IDOCINVOIC (Invoice document) - Used for workflow&lt;/P&gt;&lt;P&gt;&amp;#149;	Direction should be set to 2 for inbound&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter and save&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Define FM settings (BD51) Client independent&amp;lt;/b&amp;gt;&amp;#149;	Enter transaction BD51 (ALE -&amp;gt; Extensions -&amp;gt; Inbound -&amp;gt; Define settings for input modules)&lt;/P&gt;&lt;P&gt;&amp;#149;	Click on New entries&lt;/P&gt;&lt;P&gt;&amp;#149;	Type in the name of the new function module Z_IDOC_INPUT_ZINVRV&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter 0 for mass processing in the output column&lt;/P&gt;&lt;P&gt;&amp;#149;	Save and Exit&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Maintain process codes (WE42) Client dependent&amp;lt;/b&amp;gt;A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.&lt;/P&gt;&lt;P&gt;To maintain the process code follow these steps:&lt;/P&gt;&lt;P&gt;&amp;#149;	Log on to the appropriate receiving system client&lt;/P&gt;&lt;P&gt;&amp;#149;	Execute WE42 (ALE -&amp;gt; Extensions -&amp;gt; Inbound -&amp;gt; Maintaining process codes inbound)&lt;/P&gt;&lt;P&gt;&amp;#149;	Choose Inbound with ALE service&lt;/P&gt;&lt;P&gt;&amp;#149;	Choose Processing with function module&lt;/P&gt;&lt;P&gt;&amp;#149;	Click on Processing with function module and choose create icon&lt;/P&gt;&lt;P&gt;&amp;#149;	Click on New Entries&lt;/P&gt;&lt;P&gt;&amp;#149;	Type in process code ZINR and give it a description and save&lt;/P&gt;&lt;P&gt;&amp;#149;	Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter your process code ZINR&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter your function module Z_IDOC_INPUT_ZINVRV&lt;/P&gt;&lt;P&gt;NOTE: The next 6 steps are used in workflow error handling. &lt;/P&gt;&lt;P&gt;&amp;#149;	Enter IDPKFIDCMT in object type&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter MASSINPUTFINISHED in End event&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter IDOCINVOIC in IDoc object type&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter INPUTERROROCCURREDFI in IDoc start event&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter INPUTFINISHEDFI in IDoc End event&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter IDOCINVOIC in Application object type&lt;/P&gt;&lt;P&gt;You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.&lt;/P&gt;&lt;P&gt;To set up the workflow areas please consult the Workflow config guide.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Create inbound partner profile&amp;lt;/b&amp;gt;For each message type you need to maintain the inbound partner profiles.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Maintain receiving system partner profile (WE20) Client dependent&amp;lt;/b&amp;gt;To maintain inbound partner profiles read the document ALE configuration procedure:&lt;/P&gt;&lt;P&gt;&amp;#149;	Add the message type ZINVRV with process code ZINR.&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter the output mode (background, immediately) for inbound processing and NO message code.&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Test&amp;lt;/b&amp;gt;Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Test Procedures&amp;lt;/b&amp;gt;Unit and string testing needs to be conducted on the development together with result logging and sign-off.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Oct 2007 06:50:14 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-10-15T06:50:14Z</dc:date>
    <item>
      <title>Interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2947328#M694835</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hiii everybody,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;     Can anyone show me with example or program how to create inbound interface in ABAP-HR?&lt;/P&gt;&lt;P&gt;    Reply ASAP .as its urgent for me!&lt;/P&gt;&lt;P&gt; thank u!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Oct 2007 06:33:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2947328#M694835</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-15T06:33:06Z</dc:date>
    </item>
    <item>
      <title>Re: Interface</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2947329#M694836</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INBOUND:&lt;/P&gt;&lt;P&gt;Step 1. EDI Subsystem creates an IDoc file from EDI Messages&lt;/P&gt;&lt;P&gt;2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.&lt;/P&gt;&lt;P&gt;3. Data in Control Record is validate against the Partner Profile.&lt;/P&gt;&lt;P&gt;4. IDoc is generated in Database and syntax check is carried out.&lt;/P&gt;&lt;P&gt;5. IDoc file is deleted once file read.&lt;/P&gt;&lt;P&gt;6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow. &lt;/P&gt;&lt;P&gt;7. Check for Process Immediately.&lt;/P&gt;&lt;P&gt;If NO&lt;/P&gt;&lt;P&gt;Execute RBDAPP01 Program&lt;/P&gt;&lt;P&gt;Else&lt;/P&gt;&lt;P&gt;Read Process Code from Partner Profile &lt;/P&gt;&lt;P&gt;Process Code Points to Function Module&lt;/P&gt;&lt;P&gt;Application Document Posted. &lt;/P&gt;&lt;P&gt;further help:&lt;/P&gt;&lt;P&gt;check url&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;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/ale/configuration.htm" target="test_blank"&gt;http://www.sapgenie.com/ale/configuration.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.sapdevelopment.co.uk/training" target="test_blank"&gt;http://www.sapdevelopment.co.uk/training&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And also u can get lots of inof from the below link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/ale/why_ale.htm" target="test_blank"&gt;http://www.sapgenie.com/ale/why_ale.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data Creation in Idoc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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 &lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDoc is a intermediate document to exchange data between two SAP Systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*IDocs are structured ASCII files (or a virtual equivalent). &lt;/P&gt;&lt;P&gt;*Electronic Interchange Document&lt;/P&gt;&lt;P&gt;*They are the file format used by SAP R/3 to exchange data with foreign systems.&lt;/P&gt;&lt;P&gt;*Data Is transmitted in ASCII format, i.e. human readable form&lt;/P&gt;&lt;P&gt;*IDocs exchange messages&lt;/P&gt;&lt;P&gt;*IDocs are used like classical interface files&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC types are templates for specific message types depending on what is the business document, you want to exchange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WE30 - you can create a IDOC type.&lt;/P&gt;&lt;P&gt;An IDOC with data, will have to be triggered by the application that is trying to send out the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FOr testing you can use WE19.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to create idoc?&lt;/P&gt;&lt;P&gt;*WE30 - you can create a IDOC type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more information in details on the same along with the examples can be viewed on:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/presentation.html" target="test_blank"&gt;http://www.sappoint.com/presentation.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_search.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_search.html&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://www.erpgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.erpgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To Create Idoc we need to follow these steps:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create Segment ( WE31)&lt;/P&gt;&lt;P&gt;Create Idoc Type ( WE30 )&lt;/P&gt;&lt;P&gt;Create Message Type ( WE81 )&lt;/P&gt;&lt;P&gt;Assign Idoc Type to Message Type ( WE82 )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Creating a Segment&lt;/P&gt;&lt;P&gt;Go to transaction code WE31&lt;/P&gt;&lt;P&gt;Enter the name for your segment type and click on the Create icon&lt;/P&gt;&lt;P&gt;Type the short text&lt;/P&gt;&lt;P&gt;Enter the variable names and data elements&lt;/P&gt;&lt;P&gt;Save it and go back&lt;/P&gt;&lt;P&gt;Go to Edit -&amp;gt; Set Release&lt;/P&gt;&lt;P&gt;Follow steps to create more number of segments&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create IDOC Type&lt;/P&gt;&lt;P&gt;Go to transaction code WE30&lt;/P&gt;&lt;P&gt;Enter the Object Name, select Basic type and click Create icon&lt;/P&gt;&lt;P&gt;Select the create new option and enter a description for your basic IDOC type and press enter&lt;/P&gt;&lt;P&gt;Select the IDOC Name and click Create icon&lt;/P&gt;&lt;P&gt;The system prompts us to enter a segment type and its attributes&lt;/P&gt;&lt;P&gt;Choose the appropriate values and press Enter&lt;/P&gt;&lt;P&gt;The system transfers the name of the segment type to the IDOC editor.&lt;/P&gt;&lt;P&gt;Follow these steps to add more number of segments to Parent or as Parent-child relation&lt;/P&gt;&lt;P&gt;Save it and go back&lt;/P&gt;&lt;P&gt;Go to Edit -&amp;gt; Set release&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create Message Type&lt;/P&gt;&lt;P&gt;Go to transaction code WE81&lt;/P&gt;&lt;P&gt;Change the details from Display mode to Change mode&lt;/P&gt;&lt;P&gt;After selection, the system will give this message &amp;#147;The table is cross-client (see Help for further info)&amp;#148;. Press Enter&lt;/P&gt;&lt;P&gt;Click New Entries to create new Message Type&lt;/P&gt;&lt;P&gt;Fill details&lt;/P&gt;&lt;P&gt;Save it and go back&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assign Message Type to IDoc Type&lt;/P&gt;&lt;P&gt;Go to transaction code WE82&lt;/P&gt;&lt;P&gt;Change the details from Display mode to Change mode&lt;/P&gt;&lt;P&gt;After selection, the system will give this message &amp;#147;The table is cross-client (see Help for further info)&amp;#148;. Press Enter.&lt;/P&gt;&lt;P&gt;Click New Entries to create new Message Type.&lt;/P&gt;&lt;P&gt;Fill details&lt;/P&gt;&lt;P&gt;Save it and go back&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;&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;&amp;lt;b&amp;gt;: Inbound processing example code&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Debugging inbound FM&amp;lt;/b&amp;gt;Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Maintain ALE attributes&amp;lt;/b&amp;gt;The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Link Message Type to Function Module (WE57) Client independent&amp;lt;/b&amp;gt;To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter transaction WE57 (ALE -&amp;gt; Extensions -&amp;gt; Inbound -&amp;gt; Allocate function module to logical message)&lt;/P&gt;&lt;P&gt;&amp;#149;	Select an entry (EG. IDOC_INPUT_ORDERS) and copy&lt;/P&gt;&lt;P&gt;&amp;#149;	Type in module name Z_IDOC_INPUT_ZINVRV&lt;/P&gt;&lt;P&gt;&amp;#149;	Type in basic IDoc type as ZINVRV01&lt;/P&gt;&lt;P&gt;&amp;#149;	Type in message type as ZINVRV&lt;/P&gt;&lt;P&gt;&amp;#149;	Type object type as IDOCINVOIC (Invoice document) - Used for workflow&lt;/P&gt;&lt;P&gt;&amp;#149;	Direction should be set to 2 for inbound&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter and save&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Define FM settings (BD51) Client independent&amp;lt;/b&amp;gt;&amp;#149;	Enter transaction BD51 (ALE -&amp;gt; Extensions -&amp;gt; Inbound -&amp;gt; Define settings for input modules)&lt;/P&gt;&lt;P&gt;&amp;#149;	Click on New entries&lt;/P&gt;&lt;P&gt;&amp;#149;	Type in the name of the new function module Z_IDOC_INPUT_ZINVRV&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter 0 for mass processing in the output column&lt;/P&gt;&lt;P&gt;&amp;#149;	Save and Exit&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Maintain process codes (WE42) Client dependent&amp;lt;/b&amp;gt;A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.&lt;/P&gt;&lt;P&gt;To maintain the process code follow these steps:&lt;/P&gt;&lt;P&gt;&amp;#149;	Log on to the appropriate receiving system client&lt;/P&gt;&lt;P&gt;&amp;#149;	Execute WE42 (ALE -&amp;gt; Extensions -&amp;gt; Inbound -&amp;gt; Maintaining process codes inbound)&lt;/P&gt;&lt;P&gt;&amp;#149;	Choose Inbound with ALE service&lt;/P&gt;&lt;P&gt;&amp;#149;	Choose Processing with function module&lt;/P&gt;&lt;P&gt;&amp;#149;	Click on Processing with function module and choose create icon&lt;/P&gt;&lt;P&gt;&amp;#149;	Click on New Entries&lt;/P&gt;&lt;P&gt;&amp;#149;	Type in process code ZINR and give it a description and save&lt;/P&gt;&lt;P&gt;&amp;#149;	Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter your process code ZINR&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter your function module Z_IDOC_INPUT_ZINVRV&lt;/P&gt;&lt;P&gt;NOTE: The next 6 steps are used in workflow error handling. &lt;/P&gt;&lt;P&gt;&amp;#149;	Enter IDPKFIDCMT in object type&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter MASSINPUTFINISHED in End event&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter IDOCINVOIC in IDoc object type&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter INPUTERROROCCURREDFI in IDoc start event&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter INPUTFINISHEDFI in IDoc End event&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter IDOCINVOIC in Application object type&lt;/P&gt;&lt;P&gt;You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.&lt;/P&gt;&lt;P&gt;To set up the workflow areas please consult the Workflow config guide.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Create inbound partner profile&amp;lt;/b&amp;gt;For each message type you need to maintain the inbound partner profiles.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Maintain receiving system partner profile (WE20) Client dependent&amp;lt;/b&amp;gt;To maintain inbound partner profiles read the document ALE configuration procedure:&lt;/P&gt;&lt;P&gt;&amp;#149;	Add the message type ZINVRV with process code ZINR.&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter the output mode (background, immediately) for inbound processing and NO message code.&lt;/P&gt;&lt;P&gt;&amp;#149;	Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Test&amp;lt;/b&amp;gt;Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Test Procedures&amp;lt;/b&amp;gt;Unit and string testing needs to be conducted on the development together with result logging and sign-off.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Oct 2007 06:50:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/interface/m-p/2947329#M694836</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-15T06:50:14Z</dc:date>
    </item>
  </channel>
</rss>

