Assigning physical file to logical file.

How to configure application server file with logical file.( I don't have full idea about this . what I know is using /nfile tcode we assign logical file name to application server path and
using 'FILE_GET_NAME' function module, by supplying logical file we get the path of our application server
My lead doesn't have idea about this. How to convey him about logical file using which assiging physical file path. Can you explain clearly, so that I will work with my lead and get work done.
Your help will be appreciated highly

FILE Transaction Code
FILE transaction - How to use.
FILE transaction

Similar Messages

Regarding assignment of physical path to logical file name

Hi All,
We have created one logical file name and assigned physical path to it in FILE tcode.
IN PATH table also these details got updated with correct logical file name & physical path.
But in my program when i have used FILE_GET_NAME F.M to retrieve physical path from logical file.
Here this F.M is not returning anything.
What is the issue over here.
We are working in ECC 6.0
Can anybody resolve this issue!
Thanks,
Deep.

do one thing i give my report so according to do this
*& Report ZMIO_MANU_VENDOR_EXTR
report zmio_manu_vendor_extr.
DATA BASE TABLES
tables: lfa1 ,eina, lfm1 .
STRUCTURES
*---structure for the vendor details.
data: begin of ws_lfa1 ,
lifnr type lfa1-lifnr,
name1 type lfa1-name1,
end of ws_lfa1 .
*---structure for the pur org details.
data: begin of ws_lfm1 ,
lifnr type lfm1-lifnr,
kalsk type lfm1-kalsk,
minbw type lfm1-minbw,
end of ws_lfm1 .
*---structure for the pur inf rec.
data: begin of ws_eina,
lifnr type eina-lifnr,
relif type eina-relif,
end of ws_eina .
*--structure for the output file
data: begin of ws_final,
lifnr(10) type c,
name1(35) type c,
kalsk(1) type c,
minbw(13) type c,
eoln(1) type c,
end of ws_final .
INTERNAL TABLES
*---internal table for vendor details
data:i_lfa1 like ws_lfa1 occurs 0.
*---internal table for pur org details
data:i_lfm1 like ws_lfm1 occurs 0.
*---internal table for pur inf details
data:i_eina like ws_eina occurs 0.
*---internal table for final file output
data:i_final like ws_final occurs 0.
*DATA : P_FLAG(1) TYPE C.
CONSTANTS
*-- Default file name
constants: c_filename_default(40) type c
value 'VOLSAP/MAXVRLIB/manu_retail_vendor',
c_kalsk(2) type c value '05'.
SELECTION SCREEN
selection-screen begin of block b1 with frame.
selection-screen: begin of block b2 with frame title text-001 .
select-options:s$lifnr for lfa1-lifnr .
parameters:p$relif as checkbox.
selection-screen end of block b2.
selection-screen: begin of block b3 with frame title text-002 .
parameters: p$file(128) obligatory default c_filename_default.
selection-screen end of block b3.
selection-screen end of block b1 .
START OF SELECTION
start-of-selection.
if not s$lifnr is initial.
perform get_vendor_data .
endif.
perform build_file .
perform display_file .
END OF SELECTION
end-of-selection .
*& Form GET_VENDOR_DATA
form get_vendor_data .
select lifnr
name1
from lfa1
into table i_lfa1
where lifnr in s$lifnr .
if not i_lfa1[] is initial.
sort i_lfa1 by lifnr .
select lifnr
kalsk
minbw
from lfm1
into table i_lfm1
for all entries in i_lfa1
where lifnr = i_lfa1-lifnr .
select lifnr
relif
from eina
into table i_eina
for all entries in i_lfa1
where lifnr = i_lfa1-lifnr
and relif = 'X'.
endif.
endform. " GET_VENDOR_DATA
*& Form BUILD_FILE
form build_file .
loop at i_lfa1 into ws_lfa1 .
ws_final-lifnr = ws_lfa1-lifnr .
ws_final-name1 = ws_lfa1-name1 .
read table i_lfm1 into ws_lfm1 with key lifnr = ws_lfa1-lifnr .
if ws_lfm1-kalsk = c_kalsk .
ws_final-kalsk = 'X'.
endif.
ws_final-minbw = ws_lfm1-minbw .
ws_final-eoln = 'X'.
if p$relif = 'X'.
CLEAR P_FLAG.
LOOP AT I_EINA INTO WS_EINA
WHERE LIFNR = WS_LFA1-LIFNR
AND RELIF = 'X'.
P_FLAG = 'X'.
EXIT.
ENDLOOP.
IF P_FLAG = 'X'.
APPEND WS_FINAL TO I_FINAL .
CLEAR WS_FINAL.
ENDIF
read table i_eina into ws_eina with key lifnr = ws_lfa1-lifnr
relif = 'X'.
if sy-subrc = 0.
append ws_final to i_final .
clear ws_final.
endif.
else.
append ws_final to i_final .
clear ws_final.
endif.
endloop .
endform. " BUILD_FILE
*& Form DISPLAY_FILE
form display_file .
data: l_lines type i.
describe table i_final lines l_lines.
if l_lines > 0.
perform open_file using p$file.
loop at i_final into ws_final.
transfer ws_final to p$file.
endloop.
close dataset p$file.
else.
write: / 'no data found'.
endif.
endform. " DISPLAY_FILE
*& Form open_file
Open an output file, customizing default name to include
vendor number and job completion timestamp.
form open_file using file_nm.
data: l_vendor like eina-lifnr,
l_timestamp(12) type c.
Get correct path/filename for the system we're running on
call function 'FILE_GET_NAME'
exporting
logical_filename = 'ZVOL'
parameter_1 = file_nm
importing
file_name = file_nm.
Open file for output
open dataset file_nm for output in text mode encoding default.
if sy-subrc ne 0.
message e368(00) with 'Error opening output file:' file_nm.
endif.
endform. "open_file
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.
Edited by: krupa jani on Aug 20, 2008 6:55 AM

File system error: The record ID is incorrect. Physical file: . Logical file:

Hi,
I face this error message when I try to 'process update' a dimention, sometime it works but sometime it failed with the error below:
Description: File system error: The record ID is incorrect. Physical file: . Logical file: .
My environment: Window Server 2008 R2+SQL Server 2008 R2.
Note: this issue can be resolved by full cube process, but I can't to that every time if it failed, just want to know what happen at backend of SSAS, It block me neary 2 week without any finding, really appreciate that someone can help on this.
I have do some research with google, I think the root cause here is not TopCount function(It may be a problem with SQL Server2005), also not the size limitation of 4GB size of .astore file.(I check the size of my cube under 'Data\XXX.db\' folder, which only
have few MB size).
Thanks,
Tom

Hi Tom,
Here is a microsoft fix
FIX: "File system error" occurs when you try to run a process update operation on a dimension in Microsoft SQL Server 2008 Analysis Services and in Microsoft SQL Server 2008 R2 Analysis Services
In your acenario, in order to fix this issue, please apply the latest Cumulative update and Service Pack according to your SQL Server version. Besides, there are two workarounds in that fix, plese try it and check if it works or not.
http://support.microsoft.com/default.aspx?scid=kb;en-US;2276495
Regards,
Charlie Liao
TechNet Community Support

Information about file Id, Logical file name and Physical file name

Hi All,
I am testing one program. Selection screen has 3 parameters, File Id, Logical File Name and Physical file name. In Physical File name, i am giving complete file name with path. But it is giving error. Please tell me, what is File id and what all information i need to enter for logical file name and physical file name.
Thanks
Puneet Aggarwal

hi,
try using this for filename.
parameters : p_file like rlgrap-filename.
Thanks,
Gaurav

FM to get F4 for application server file or logical file or dataset .

Hi all.
   Can any body pls let me know the FMs to get the F4 for applicattionserver file or logical file or unix file or dataset. Thanks in advance.
Kind Regards,
sami.

hi,
use the FM: 'F4_DXFILENAME_4_DYNP' in the below mentioned format:
p_file: is the field name in selection screen in which you have to enter the filepath:
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_DXFILENAME_4_DYNP'
    EXPORTING
      dynpfield_filename = 'P_FILE'
      dyname             = sy-cprog
      dynumb             = sy-dynnr
      filetype           = 'P'      "P-->Physical
      location           = 'P'     "P Presentation Srever
      server             = space.
hope it will help you
regards
rahul

In LSMW while executing the specify file step logical file name and path.

Hi ,
In LSMW , while executing the specify file step, logical file name and path is mandatory field to entry, but in some of other LSMW objects, these fields are not mandatory one, i want to know is it possible for me to do hide the logical file name and path field in specify file step.
thanks
Md nisar

Hi,
For some Transactions while executing the Specify file step Logical File and Logical Path are mandatory.
In this case Converted file will be stored in the application server. According to the specified Logical File and Logical path.
Hope this will help you....
Regards,
Tirumala Reddy

Conversion of Digital Performer files to Logic files

What's the way to convert Digital Performer (audio & midi) files to Logic files?

what i do is this:
save as OMF in DP, save as MIDI in DP, sometimes Logic can open the OMF file, it depends on the settings used with DP OMF export. Logic really *****, when it comes to READ OMF files! Some great helper is a software called AVTransfer, that exists for PC. This app converts an OMF file into an OMF(!) file and removes all unnecessary data in the OMF, so every app can open it. This helped me several times.
Another idea is, to put a second of silece on every audio track to position 0 and MERGE all audio tracks, so you get Audio Files that all start at the same position and can be saved as any file format you like. Its faster than you might think: copy this bit of audio to all audio tracks and then select all, MERGE and have a coffee, no need to sit in front of your monitor.
MIDI tracks will have to be exported separatly, bcause they are not saved to an OMF or to audio files.
But you will have to setup your instruments for MIDI playback by hand, maybe save a patch in DP for each software instrument, to load them up in logic again.
Hope that helps.

What are AL11 files and logical files

what are AL11 files and logical files

YES. these are the files that you use to load data.
Reg your question of how to see the data sources or view data, I replied yo your other question in other thread.
"is there any way by which we can check out that particular file in application server after the data has been loaded"
You can see this in data load monitor.
I dont know what do you mean by logical files.
Ravi Thothadri

Difference between logical file path and physical file path

Hi,
Can anyone tell me why logical file path is required and why physical file path is required? What exactly is the difference bet them?
Thanks in advance.
Regards,
PS.

Hi,
The function module FILE_GET_NAME convert a logical path into its corresponding physical path.
The advantage of using logical pathes within your applications is obivous:
If you need to change the physical path you just adjust it within transaction FILE yet no changes are required to your application.
http://help.sap.com/saphelp_erp2005vp/helpdata/en/25/ab3a57df3b11d189fc0000e829fbbd/frameset.htm
The file names that you use in ABAP statements for processing files are physical names. This means that they must be syntactically correct filenames for the operating system under which your R/3 System is running. Once you have created a file from an ABAP program with a particular name and path, you can find the same file using the same name and path at operating system level.
Since the naming conventions for files and paths differ from operating system to operating system, ABAP programs are only portable from one operating system to another if you use the tools described below.
To make programs portable, the R/3 System has a concept of logical filenames and paths. These are linked to physical files and paths. The links are created in special tables, which you can maintain according to your own requirements. In an ABAP program, you can then use the function module FILE_GET_NAME to generate a physical filename from a logical one.
Maintaining platform-independent filenames is part of Customizing. For a full description, choose Tools ® Business Engineer ® Customizing, followed by
Implement. projects ® SAP Reference IMG. On the next screen, choose Basis Components System Administration ® Platform-independent File Names.
For a more detailed description of the function module FILE_GET_NAME, enter its name on the initial screen of the Function Builder and choose Goto Documentation. On the next screen, choose Function module doc.
Another way of maintaining platform-independent filenames is to use the Transaction FILE. The following sections provide an overview of the transaction.
To create a logical filename, choose Logical filename definition, client-independent from the Navigation group box in Transaction FILE, then choose New entries. You define logical filenames
You can either define a logical filename and link it to a logical path (as displayed here), or you can enter the full physical filename in the Physical file field. In the latter case, the logical filename is only valid for one operating system. The rules for entering the complete physical filename are the same as for the definition of the physical path for the logical file. To display further information and a list of reserved words, choose Help.
If you link a logical path to a logical file, the logical file is valid for all syntax groups that have been maintained for that logical path. The filename specified under Physical file replaces the reserved word in the physical paths that are assigned to the logical path. To make the name independent of the operating system, use names that begin with a letter, contain up to 8 letters, and do not contain special characters.
Save your changes.
regards,
Omkar.

Mapping physical file name to logical file name

Hi All,
Can anybody let me know wht is the procedure to map a logical file name to physical file name. wht is the use of logical file name when there exists physical file name?
Thanx in Advance

As far as creating the Logical path its done through the transaction code file by using options
Steps are:
1. Logical file path definition which is logical file path name.
2. Assignment of physical path to logical path - where we give the physical path to the logical path name defined in the last step.
After creating the Logical path the procedure to attach the file name to the Logical path is as follows:
Use the function Module C13Z_FRONT_END_TO_APPL to upload the file from the front end to the application server.
Source file on front end will be the CSV file path which is to be uploaded to the application server
Target file on application server will be the physical path of the file on the application server where the file is to be uploaded.
Attach the physical path of the file on the application server to the Logical file using transaction code file.
Logical File: The Logical name of the file which will be used by the interfaces to upload the file
Physical file: The name of the physical file on the application server
Logical path: The path of the physical file on the application server where it is stored.
The possible reason for the use of Logical file name could be we can have directories within SAP in which we can have logical files stored. These files can be used by various interfaces. Different Logical paths can be used for different interfaces. the second reson can be to give more user friendly name to the file rather than a long physical name to the file.

Logical file name or logical path name incorrectly defined

Dear All,
We are doing archival in our IDES for test purpose before we do it to our Production.
Steps Performed
Copied AM_ASSET archive object to ZAM_ASSET
Logical Path
Logical path    ZAM_ASSET
Name            Asset
Syntax group    UNIX       Unix compatible
Physical path   /archive/test/<FILENAME>
Logical File Name
   Logical file    ZAMASSET
   Name            Asset
   Physical file   FI_<MONTH>_<DAY>.txt
   Data format     ASC
   Applicat.area   AM
   Logical path    ZAM_ASSET
But when we run the WRITE though SARA , in the job log we get the following
Logical file name or logical path name incorrectly defined
When generating a file name for an archive file that is to be created, the system determined that the logical file name FIAA_ARCHIVE_DATA_FILE or the logical path name ARCHIVE_GLOBAL_PATH was defined incorrectly.
But we have maintained a Logical name ZAMASSET , so we are unable to change the location of archived file and as well as the format.
So is there any setting we need to maintain apart from the logical file name and logical file path.
Suggestions are highly appreciated.
Thanks in anticipation

hi,
follow this steps :
- transaction SARA
- enter authorization objects, eg SD_VBAK
- hit button CUSTOMIZING
- Archiving Object-Specific Customizing: execute Technical Setting
- field Logical File Name enter or select ARCHIVE_DATA_FILE
- leave CONTENT REPOSITORY as blank if you are not using 3rd party for storing (eg. IBM Tivoli)
- back to customizing
- from Basis Customizing, execute : Cross-Client File Names/Paths
- on Logical FIle Path Definition, highlight (select) ARCHIVE_GLOBAL_PATH on the right pane
- double click on the Assignment of Physical Paths to Logical Path on the left pane
- double click on OS used, eg. UNIX, define Physical Path where archive file (on WRITE process) will be stored
- save changes made
- double click Logical File Definition, Cross Client on the left pane
- double click ARCHIVE_DATA_FILE on the right pane
- make sure that logical path is already set to ARCHIVE_GLOBAL_PATH
- save changes made
this setting also can be done using transaction FILE
we have experienced on this case using SAP standard archiving (SARA, SARI) and everything is fine with this setting above.
hope it help you.
rgds,
Alfonsus Guritno

How to creat the logical file name.

Hello All,
I want to create Logical file name in my program, So Please guide me in this issue.
Thanks

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
Thanks
mahesh

Logical file name(Need Urget Help)

Hi,
I'm extracting data from cube in the csv file formate, for this i used open hube and using logical file name,
logical file :Z_TEST
Name: folder name
Physical file: give the
server\test.csv
data formate:BIN.
when i run it. it is creating only one file(structure file) not creating data file.
Could you please help me to fix this problem,
Thanks

Hi Pria,
Please check :
Open Hub Destination with Flat File - Structure file is not correct
-Vikram

LOGICAL FILE PATH AND LIGICAL FILE NAME

1 I have one file(saritha.txt) on
Presentation sever and I want to create logical file and logical file path to application server?
please explain with example.

Hi,
u can create with the following one
CONCATENATE '/' sysid 'abap/if/monthly/fi/' INTO directory.
file name as combination of sys-uzeit and sy-udate.

Logical file paths invisible

Hello All,
Can any 1 share their views on why excialty Logical file paths & Logical file names are used.
From last 2 days we are facing an issue on our PRD system.
In our case Logical file paths & Logical file names are used for interfacing external Application programs.
The files are processed & sent either Inbound or Outbound.
Apparently, The Logical file paths(2 of them) which was visible earlier is now invisible. The reason for this is unknown. But the Interface functions still work well.
Is there a reason why its invisible suddenly? Can it be made visible again or do we need to create new ones?
Tx-code FILE is used for "Logical file path definition"
Please suggest,
Regards,
Ravi

Hi,
>Can any 1 share their views on why excactly Logical file paths & Logical file names are used.
Logical paths and files are very useful for 2 reasons.
You can write abap programs independant from the OS, you can even have different OS in the same system. For example the CI server onh Unix and the app servers on Windows.
On windows, it is also very useful to have paths independant of the environment (DEV, QAS, PRD) because you can use variables.
Example you can use this kind of syntax :
<P=SAPMSHOST>\SAP_IN\<SYSID>_<CLIENT>\DIR1\DIR2\<FILENAME>
For the "invisible paths", I have absolutely no idea because all my logical paths have never disapeared until someone deleted them.
Regards,
Olivier

Assigning physical file to logical file.

Similar Messages

Maybe you are looking for