<?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: function module file_get_name in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-file-get-name/m-p/1504284#M233183</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Venu,&lt;/P&gt;&lt;P&gt;look via se37 at the Documentation. There is an good Information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Dieter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 31 Aug 2006 11:57:03 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-08-31T11:57:03Z</dc:date>
    <item>
      <title>function module file_get_name</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-file-get-name/m-p/1504283#M233182</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;functionality of FILE_GET_NAME.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Aug 2006 11:54:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-file-get-name/m-p/1504283#M233182</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-31T11:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: function module file_get_name</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-file-get-name/m-p/1504284#M233183</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Venu,&lt;/P&gt;&lt;P&gt;look via se37 at the Documentation. There is an good Information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Dieter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Aug 2006 11:57:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-file-get-name/m-p/1504284#M233183</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-31T11:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: function module file_get_name</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-file-get-name/m-p/1504285#M233184</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi venu ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  The FM is documented well , if you want more u can check where-used-list of that FM and checkout how it works in real time&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Aug 2006 12:00:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-file-get-name/m-p/1504285#M233184</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-31T12:00:21Z</dc:date>
    </item>
    <item>
      <title>Re: function module file_get_name</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-file-get-name/m-p/1504286#M233185</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Venu,&lt;/P&gt;&lt;P&gt; Check this out&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_45b/helpdata/en/2a/fa02b7493111d182b70000e829fbfe/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_45b/helpdata/en/2a/fa02b7493111d182b70000e829fbfe/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FU FILE_GET_NAME&lt;/P&gt;&lt;P&gt;____________________________________________________&lt;/P&gt;&lt;P&gt;Text&lt;/P&gt;&lt;P&gt;Assign the Physical File Name Using a Logical File Name&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;R/3 applications run on various platforms with various file systems. This function module enables you to use platform-independent logical file names in your application programs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Based on definitions maintained in customizing tables for platform-independent file names, the function module converts a logical file name to the corresponding physical file name and path for the hardware platform concerned.&lt;/P&gt;&lt;P&gt;For this conversion to work for different platforms, the definition of a logical file name must include a logical file path, which in turn is converted to different physical file paths, depending on the particular platform. The platform-specific file name returned by the function module is composed of the physical file path for the current platform and the physical file name associated with the logical file name. Placeholders in physical file and path names are substituted at runtime by the corresponding current values.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logical file name: MONTHLY_SALES_FILE &lt;/P&gt;&lt;P&gt;physical file name: VALUES&amp;lt;PARAM_1&amp;gt; &lt;/P&gt;&lt;P&gt;logical path: SALES_DATA_PATH &lt;/P&gt;&lt;P&gt;  physical path (UNIX): /usr/&amp;lt;SYSID&amp;gt;/&amp;lt;FILENAME&amp;gt; &lt;/P&gt;&lt;P&gt;  physical path (Windows): C:\SALES\&amp;lt;FILENAME&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example 1&lt;/P&gt;&lt;P&gt;Get file name for UNIX platform&lt;/P&gt;&lt;P&gt;(current system: K11)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL                                                                                FUNCTION                                                                                'FILE_GET_NAME'&lt;/P&gt;&lt;P&gt;   EXPORTING&lt;/P&gt;&lt;P&gt;      LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'&lt;/P&gt;&lt;P&gt;   IMPORTING&lt;/P&gt;&lt;P&gt;      FILE_NAME = FILE&lt;/P&gt;&lt;P&gt;      FILE_FORMAT = FORMAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Result:&lt;/P&gt;&lt;P&gt;FILE = /usr/K11/VALUES&lt;/P&gt;&lt;P&gt;FORMAT = WK1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example 2&lt;/P&gt;&lt;P&gt;Get file name for UNIX platform, passing a parameter&lt;/P&gt;&lt;P&gt;(current system: K11)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL                                                                                FUNCTION                                                                                'FILE_GET_NAME'&lt;/P&gt;&lt;P&gt;   EXPORTING&lt;/P&gt;&lt;P&gt;      LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'&lt;/P&gt;&lt;P&gt;      PARAMETER_1 = '_TST'&lt;/P&gt;&lt;P&gt;   IMPORTING&lt;/P&gt;&lt;P&gt;      FILE_NAME = FILE&lt;/P&gt;&lt;P&gt;      FILE_FORMAT = FORMAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Result:&lt;/P&gt;&lt;P&gt;FILE = /usr/K11/VALUES_TST&lt;/P&gt;&lt;P&gt;FORMAT = WK1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example 3&lt;/P&gt;&lt;P&gt;Get file name for WINDOWS platform, with file name extension&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL                                                                                FUNCTION                                                                                'FILE_GET_NAME'&lt;/P&gt;&lt;P&gt;   EXPORTING&lt;/P&gt;&lt;P&gt;      LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'&lt;/P&gt;&lt;P&gt;      WITH_FILE_EXTENSION = 'X'&lt;/P&gt;&lt;P&gt;   IMPORTING&lt;/P&gt;&lt;P&gt;      FILE_NAME = FILE&lt;/P&gt;&lt;P&gt;      FILE_FORMAT = FORMAT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Result:&lt;/P&gt;&lt;P&gt;FILE = C:\SALES\VALUES.WK1&lt;/P&gt;&lt;P&gt;FORMAT = WK1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notes&lt;/P&gt;&lt;P&gt;All definitions needed for the platform-independent assignment of file names are maintained client-independently with transaction FILE. Logical file names (but not logical file paths) can also be defined specifically for the current client with transaction SF01. Transaction SF07 generates a list of current definitions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following concepts are used in the platform-independent assignment of file names:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Logical file name&lt;/P&gt;&lt;P&gt;A descriptive name for a file which is associated with these values:&lt;/P&gt;&lt;P&gt;physical file name&lt;/P&gt;&lt;P&gt;file format&lt;/P&gt;&lt;P&gt;logical file path.&lt;/P&gt;&lt;P&gt;If no logical file path is specified, the function module returns the physical file name only; placeholders are substituted by current values.&lt;/P&gt;&lt;P&gt;Physical file name&lt;/P&gt;&lt;P&gt;The physical file name may contain placeholders.&lt;/P&gt;&lt;P&gt;Logical file path&lt;/P&gt;&lt;P&gt;A descriptive name for a path which is associated with these values:&lt;/P&gt;&lt;P&gt;syntax groups (groups of operating systems)&lt;/P&gt;&lt;P&gt;physical file paths.&lt;/P&gt;&lt;P&gt;Physical file path&lt;/P&gt;&lt;P&gt;The physical file path is defined for a particular syntax group. It must contain the reserved word &amp;lt;FILENAME&amp;gt; as a placeholder for the file name. It may also contain other placeholders.&lt;/P&gt;&lt;P&gt;Operating system&lt;/P&gt;&lt;P&gt;Presentation server and application server can run under different operating systems. The current value for the application server can be obtained from the system field SY-OPSYS, the value for the presentation server by calling function module WS_QUERY.&lt;/P&gt;&lt;P&gt;Both operating systems must be defined and assigned to a syntax group.&lt;/P&gt;&lt;P&gt;Syntax group&lt;/P&gt;&lt;P&gt;Group of operating systems with a common syntax for file and path names (e.g. HP-UX and SINIX).&lt;/P&gt;&lt;P&gt;Placeholder&lt;/P&gt;&lt;P&gt;Reserved words, set in angle brackets, which can be included in physical file and path names (e.g. &amp;lt;DATE&amp;gt;, &amp;lt;FILENAME&amp;gt;). You can find information on possible reserved words in the online help (F1 help) for the fields physical file name and physical file path when maintaining platform-independent file names with transaction FILE.&lt;/P&gt;&lt;P&gt;If the logical path associated with a logical file name does not specify a physical path for the current operating system (syntax group), the path stored in the profile parameter DIR_GLOBAL of the current system is used for generating a complete platform-specific file name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Parameters&lt;/P&gt;&lt;P&gt;CLIENT&lt;/P&gt;&lt;P&gt;LOGICAL_FILENAME&lt;/P&gt;&lt;P&gt;OPERATING_SYSTEM&lt;/P&gt;&lt;P&gt;PARAMETER_1&lt;/P&gt;&lt;P&gt;PARAMETER_2&lt;/P&gt;&lt;P&gt;PARAMETER_3&lt;/P&gt;&lt;P&gt;USE_PRESENTATION_SERVER&lt;/P&gt;&lt;P&gt;WITH_FILE_EXTENSION&lt;/P&gt;&lt;P&gt;USE_BUFFER&lt;/P&gt;&lt;P&gt;ELEMINATE_BLANKS&lt;/P&gt;&lt;P&gt;EMERGENCY_FLAG&lt;/P&gt;&lt;P&gt;FILE_FORMAT&lt;/P&gt;&lt;P&gt;FILE_NAME&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exceptions&lt;/P&gt;&lt;P&gt;FILE_NOT_FOUND&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Function Group&lt;/P&gt;&lt;P&gt;SFIL&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;santosh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: Santosh Kumar P&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Aug 2006 12:06:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-file-get-name/m-p/1504286#M233185</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-08-31T12:06:03Z</dc:date>
    </item>
  </channel>
</rss>

