Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

function module file_get_name

Former Member
0 Likes
2,415

functionality of FILE_GET_NAME.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,638

hi Venu,

Check this out

http://help.sap.com/saphelp_45b/helpdata/en/2a/fa02b7493111d182b70000e829fbfe/content.htm

FU FILE_GET_NAME

____________________________________________________

Text

Assign the Physical File Name Using a Logical File Name

Functionality

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.

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.

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.

Example

logical file name: MONTHLY_SALES_FILE

physical file name: VALUES<PARAM_1>

logical path: SALES_DATA_PATH

physical path (UNIX): /usr/<SYSID>/<FILENAME>

physical path (Windows): C:\SALES\<FILENAME>

Example 1

Get file name for UNIX platform

(current system: K11)

CALL FUNCTION 'FILE_GET_NAME'

EXPORTING

LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'

IMPORTING

FILE_NAME = FILE

FILE_FORMAT = FORMAT.

Result:

FILE = /usr/K11/VALUES

FORMAT = WK1

Example 2

Get file name for UNIX platform, passing a parameter

(current system: K11)

CALL FUNCTION 'FILE_GET_NAME'

EXPORTING

LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'

PARAMETER_1 = '_TST'

IMPORTING

FILE_NAME = FILE

FILE_FORMAT = FORMAT.

Result:

FILE = /usr/K11/VALUES_TST

FORMAT = WK1

Example 3

Get file name for WINDOWS platform, with file name extension

CALL FUNCTION 'FILE_GET_NAME'

EXPORTING

LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'

WITH_FILE_EXTENSION = 'X'

IMPORTING

FILE_NAME = FILE

FILE_FORMAT = FORMAT.

Result:

FILE = C:\SALES\VALUES.WK1

FORMAT = WK1

Notes

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.

The following concepts are used in the platform-independent assignment of file names:

Logical file name

A descriptive name for a file which is associated with these values:

physical file name

file format

logical file path.

If no logical file path is specified, the function module returns the physical file name only; placeholders are substituted by current values.

Physical file name

The physical file name may contain placeholders.

Logical file path

A descriptive name for a path which is associated with these values:

syntax groups (groups of operating systems)

physical file paths.

Physical file path

The physical file path is defined for a particular syntax group. It must contain the reserved word <FILENAME> as a placeholder for the file name. It may also contain other placeholders.

Operating system

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.

Both operating systems must be defined and assigned to a syntax group.

Syntax group

Group of operating systems with a common syntax for file and path names (e.g. HP-UX and SINIX).

Placeholder

Reserved words, set in angle brackets, which can be included in physical file and path names (e.g. <DATE>, <FILENAME>). 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.

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.

Parameters

CLIENT

LOGICAL_FILENAME

OPERATING_SYSTEM

PARAMETER_1

PARAMETER_2

PARAMETER_3

USE_PRESENTATION_SERVER

WITH_FILE_EXTENSION

USE_BUFFER

ELEMINATE_BLANKS

EMERGENCY_FLAG

FILE_FORMAT

FILE_NAME

Exceptions

FILE_NOT_FOUND

Function Group

SFIL

Regards,

santosh

Message was edited by: Santosh Kumar P

3 REPLIES 3
Read only

Former Member
0 Likes
1,638

Hi Venu,

look via se37 at the Documentation. There is an good Information.

Regards, Dieter

Read only

Former Member
0 Likes
1,638

hi venu ,

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

Read only

Former Member
0 Likes
1,639

hi Venu,

Check this out

http://help.sap.com/saphelp_45b/helpdata/en/2a/fa02b7493111d182b70000e829fbfe/content.htm

FU FILE_GET_NAME

____________________________________________________

Text

Assign the Physical File Name Using a Logical File Name

Functionality

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.

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.

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.

Example

logical file name: MONTHLY_SALES_FILE

physical file name: VALUES<PARAM_1>

logical path: SALES_DATA_PATH

physical path (UNIX): /usr/<SYSID>/<FILENAME>

physical path (Windows): C:\SALES\<FILENAME>

Example 1

Get file name for UNIX platform

(current system: K11)

CALL FUNCTION 'FILE_GET_NAME'

EXPORTING

LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'

IMPORTING

FILE_NAME = FILE

FILE_FORMAT = FORMAT.

Result:

FILE = /usr/K11/VALUES

FORMAT = WK1

Example 2

Get file name for UNIX platform, passing a parameter

(current system: K11)

CALL FUNCTION 'FILE_GET_NAME'

EXPORTING

LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'

PARAMETER_1 = '_TST'

IMPORTING

FILE_NAME = FILE

FILE_FORMAT = FORMAT.

Result:

FILE = /usr/K11/VALUES_TST

FORMAT = WK1

Example 3

Get file name for WINDOWS platform, with file name extension

CALL FUNCTION 'FILE_GET_NAME'

EXPORTING

LOGICAL_FILENAME = 'MONTHLY_SALES_FILE'

WITH_FILE_EXTENSION = 'X'

IMPORTING

FILE_NAME = FILE

FILE_FORMAT = FORMAT.

Result:

FILE = C:\SALES\VALUES.WK1

FORMAT = WK1

Notes

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.

The following concepts are used in the platform-independent assignment of file names:

Logical file name

A descriptive name for a file which is associated with these values:

physical file name

file format

logical file path.

If no logical file path is specified, the function module returns the physical file name only; placeholders are substituted by current values.

Physical file name

The physical file name may contain placeholders.

Logical file path

A descriptive name for a path which is associated with these values:

syntax groups (groups of operating systems)

physical file paths.

Physical file path

The physical file path is defined for a particular syntax group. It must contain the reserved word <FILENAME> as a placeholder for the file name. It may also contain other placeholders.

Operating system

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.

Both operating systems must be defined and assigned to a syntax group.

Syntax group

Group of operating systems with a common syntax for file and path names (e.g. HP-UX and SINIX).

Placeholder

Reserved words, set in angle brackets, which can be included in physical file and path names (e.g. <DATE>, <FILENAME>). 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.

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.

Parameters

CLIENT

LOGICAL_FILENAME

OPERATING_SYSTEM

PARAMETER_1

PARAMETER_2

PARAMETER_3

USE_PRESENTATION_SERVER

WITH_FILE_EXTENSION

USE_BUFFER

ELEMINATE_BLANKS

EMERGENCY_FLAG

FILE_FORMAT

FILE_NAME

Exceptions

FILE_NOT_FOUND

Function Group

SFIL

Regards,

santosh

Message was edited by: Santosh Kumar P