<?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 processing program for classification data change in iDocs in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-processing-program-for-classification-data-change-in-idocs/m-p/3888864#M934118</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Siddhu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Creating a Function Module (Direct Inbound Processing) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This step describes how to create a function module which is identified by the IDoc Interface using a new process code and called from ALE (field TBD52-FUNCNAME). Direct inbound processing using a function module (not using a workflow) always includes the ALE layer. This setting (processing with function module and ALE layer) is identified by the value 6 in the field TEDE2-EDIVRS, which is read by the function module IDOC_START_INBOUND. IDOC_START_INBOUND then calls ALE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Prerequisites&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must have completed the required steps in Defining and Using a Basic Type .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Choose Tools ® ABAP Workbench ® Development ® Function Builder, and create a new function module. &lt;/P&gt;&lt;P&gt;Create the segments as global data in your function group. The function module should copy the application data from the segments into the corresponding application tables and modify the IDoc status accordingly. If an error occurs, the function module must set the corresponding workflow parameters for exception handling. &lt;/P&gt;&lt;P&gt;Activate the function module: From the initial screen of the Function Builder select .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the example, create the function module IDOC_INPUT_TESTER with a global interface. The function module is called when an IDoc of type TESTER01 is received for inbound processing. You will assign an application object ("standard order") to this IDoc type and therefore maintain tables from SD. To do this, call transaction VA01 using the command CALL TRANSACTION. Please note that the intention here is not to simulate a realistic standard order, but only to illustrate how data reaches application tables from an IDoc table via segment structures (form routine READ_IDOC_TESTER) and how the function module triggers an event for exception handling (by returning suitable return variables to the ALE layer in the FORM routine RETURN_VARIABLES_FILL).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A comprehensive example of the code for an inbound function module is provided in the ALE documentation in the SAP Library under  Example Program to Generate an IDoc. This function module, for example, also checks whether the logical message is correct and calls a (fictitious) second function module which first writes the application data and then returns the number of the generated document. In addition, status 53 is only set if the application document was posted correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see this link&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7df143d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7df143d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;karthik&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 May 2008 13:12:30 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-05-29T13:12:30Z</dc:date>
    <item>
      <title>Inbound processing program for classification data change in iDocs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-processing-program-for-classification-data-change-in-idocs/m-p/3888863#M934117</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;Can anyone provide me the program name or function module name for&lt;/P&gt;&lt;P&gt;Inbound processing program for iDocs for Classification data change in R/3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, what is the importance of the parameter:&lt;/P&gt;&lt;P&gt;UPDATETASK in INPUT_METHOD import parameter of the function module&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC_INPUT_CLFMAS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Sid&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 May 2008 11:59:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-processing-program-for-classification-data-change-in-idocs/m-p/3888863#M934117</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-29T11:59:44Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound processing program for classification data change in iDocs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-processing-program-for-classification-data-change-in-idocs/m-p/3888864#M934118</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Siddhu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Creating a Function Module (Direct Inbound Processing) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This step describes how to create a function module which is identified by the IDoc Interface using a new process code and called from ALE (field TBD52-FUNCNAME). Direct inbound processing using a function module (not using a workflow) always includes the ALE layer. This setting (processing with function module and ALE layer) is identified by the value 6 in the field TEDE2-EDIVRS, which is read by the function module IDOC_START_INBOUND. IDOC_START_INBOUND then calls ALE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Prerequisites&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You must have completed the required steps in Defining and Using a Basic Type .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Choose Tools ® ABAP Workbench ® Development ® Function Builder, and create a new function module. &lt;/P&gt;&lt;P&gt;Create the segments as global data in your function group. The function module should copy the application data from the segments into the corresponding application tables and modify the IDoc status accordingly. If an error occurs, the function module must set the corresponding workflow parameters for exception handling. &lt;/P&gt;&lt;P&gt;Activate the function module: From the initial screen of the Function Builder select .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the example, create the function module IDOC_INPUT_TESTER with a global interface. The function module is called when an IDoc of type TESTER01 is received for inbound processing. You will assign an application object ("standard order") to this IDoc type and therefore maintain tables from SD. To do this, call transaction VA01 using the command CALL TRANSACTION. Please note that the intention here is not to simulate a realistic standard order, but only to illustrate how data reaches application tables from an IDoc table via segment structures (form routine READ_IDOC_TESTER) and how the function module triggers an event for exception handling (by returning suitable return variables to the ALE layer in the FORM routine RETURN_VARIABLES_FILL).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A comprehensive example of the code for an inbound function module is provided in the ALE documentation in the SAP Library under  Example Program to Generate an IDoc. This function module, for example, also checks whether the logical message is correct and calls a (fictitious) second function module which first writes the application data and then returns the number of the generated document. In addition, status 53 is only set if the application document was posted correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see this link&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7df143d711d1893e0000e8323c4f/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7df143d711d1893e0000e8323c4f/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;karthik&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 May 2008 13:12:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/inbound-processing-program-for-classification-data-change-in-idocs/m-p/3888864#M934118</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-29T13:12:30Z</dc:date>
    </item>
  </channel>
</rss>

