<?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 IDoc processing language in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-processing-language/m-p/2116623#M443095</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi IDocers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we have ORDRSP (base type ORDERS05) inbound Idocs set to automatic processing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now we found out that the processing language changes from IDoc to IDoc. We have to take care of this behaviour because the existing processing function (now under reconstruction) uses CALL TRANSACTION to maintain pricing conditions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This fails if the condition units (e.g. ST vs PC) are not supplied in processing (logon) language. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls. let us know if there is a safe way to find out the actual language from the IDoc and (additionally) if there is a function module for UNIT translation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Apr 2007 13:22:40 GMT</pubDate>
    <dc:creator>Clemenss</dc:creator>
    <dc:date>2007-04-16T13:22:40Z</dc:date>
    <item>
      <title>IDoc processing language</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-processing-language/m-p/2116623#M443095</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi IDocers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we have ORDRSP (base type ORDERS05) inbound Idocs set to automatic processing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now we found out that the processing language changes from IDoc to IDoc. We have to take care of this behaviour because the existing processing function (now under reconstruction) uses CALL TRANSACTION to maintain pricing conditions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This fails if the condition units (e.g. ST vs PC) are not supplied in processing (logon) language. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls. let us know if there is a safe way to find out the actual language from the IDoc and (additionally) if there is a function module for UNIT translation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TIA,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Apr 2007 13:22:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-processing-language/m-p/2116623#M443095</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2007-04-16T13:22:40Z</dc:date>
    </item>
    <item>
      <title>Re: IDoc processing language</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-processing-language/m-p/2116624#M443096</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;Did you set the defaults for the user id, which processes the idocs? Find out the user id which is used to process the idocs and then go to t.code: SU01 and under the Defaults tab you can set the default language.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using a custom FM to process your inbound idocs, then you can also set the default language usign the SET LANGUAGE command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And, for converting/translating the units you can use this FM:&lt;/P&gt;&lt;P&gt;1. CONVERSION_EXIT_CUNIT_OUTPUT - This will convert ST into PC&lt;/P&gt;&lt;P&gt;2. CONVERSION_EXIT_CUNIT_INPUT - This will convert PC into ST&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Sumant.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;null&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Apr 2007 13:58:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-processing-language/m-p/2116624#M443096</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-16T13:58:06Z</dc:date>
    </item>
    <item>
      <title>Re: IDoc processing language</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-processing-language/m-p/2116625#M443097</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;the IDocs come from XI via user ALEREMOTE. It could not be determined what triggers the deviation in LogOn languages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OK, in BI we convert the quantity units using CUNIT_OUTPUT. Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Apr 2007 16:29:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/idoc-processing-language/m-p/2116625#M443097</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2007-04-16T16:29:25Z</dc:date>
    </item>
  </channel>
</rss>

