The application programs which use the function module FILE_GET_NAME always receive a file name in the global directory from this function module. The definitions in the Customizing tables of the platform-independent file names are apparently ignored. Changes in the transactions SF01, SF02 and SF03 have no influence on this problem. It appears that the file name is permanently linked to the application program in the global directory.
Cause and prerequisitesThe function module FILE_GET_NAME always returns a file name in the global directory if no file name could be generated using the settings in the Customizing tables.
In addition, the function module supplies the message that such a problem has occurred in the parameter EMERGENCY_FLAG. The application program which uses the file names in the global directory, does not respond to this message from the function module FILE_GET_NAME
The most frequent cause for this problem is a missing entry for the underlying operating system. You can make this entry via the transaction SF04. The transaction SF04 recognizes the current operating system automatically and makes an entry. You can recognize this entry because it is displayed selected. Please go into the detail maintenance for this entry and enter the respective syntax group there. Only now is the function module FILE_GET_NAME able to find the physical path which you can maintain per syntax group via the transaction SF03. After saving your changes, the problem should be solved.
If the problem occurs even though an entry exists, you must check the entries again in the transaction SF01 and SF03.
You can use the transaction SF07 to check your settings in the Customizing tables of the platform-independent file names.
No comments:
Post a Comment