Using a Logical File definition in LSMW

Hi all,
is there any way that we can use a Logical File (defined in transaction FILE) as an application server file in the "specify files" step, instead of having to enter the physical path/file?
Thanks in advance,
Justin

Hello,
Check pages 46 and 47 of the following document :
[http://sapabap.iespana.es/manuales/pdf/lsmw.pdf|http://sapabap.iespana.es/manuales/pdf/lsmw.pdf]
You can only use a logical filename for subsequent programs (example direct input programs) not for the actual input file of your LSMW.
Wim

Similar Messages

Using a Logical File (FILE) in an External Command (SM69)

I have an external command defined in SM69 that runs a script on the application server. The command is called from within an ABAP program with SXPG_CALL_SYSTEM. It currently works as it should.
The issue is that the external command is defined as:
sh /absolute/path/to/script/file
I have been told to instead set up a logical file in FILE so that the command would be:
sh <MY_SCRIPT_LOGICAL_NAME>
I've gone into FILE and defined MY_SCRIPT_LOGICAL_NAME as:
Logical File = MY_SCRIPT_LOGICAL_NAME
Name = Descriptive Text
Physical File = <SYSID>actualname.scr
Data Format = ASC
App Area = HR
Logical Path = SCRIPT_PATH
where SCRIPT_PATH is also defined in FILE with the physical path of:
/iface/<SYSID>/outboundhr/scripts/<FILENAME>
So when I try executing the command with SM49 as defined as:
sh <MY_SCRIPT_LOGICAL_NAME>
I just get Exception raised: OTHERS
If I define the command as:
ls <MY_SCRIPT_LOGICAL_NAME>
I get the same thing, Exception raised: OTHERS
I'm guessing that the logical file name isn't getting translated. Does anyone know if it should in this instance? Is anyone using a logical file as part of an external command?
Thanks much.

I think you must use FM FILE_GET_NAME to translate the logical file name to a physical one before executing the command.
Like:
DATA: physical_file_name(60),
 my_script_logical_name(60) VALUE 'CLASSIFICATION',
 format(3).
CALL FUNCTION 'FILE_GET_NAME'
EXPORTING
 logical_filename = my_script_logical_name
IMPORTING
 file_format = format
 file_name = physical_file_name
EXCEPTIONS
 file_not_found = 1
 OTHERS = 2.
Rob
Message was edited by: Rob Burbank

Can u tell me where we exactly use the logical file.

hi,
this is pandu,can u tell me where we exactly use the logical file,
what is the use of the logical file in detailed explanation.
regards,
pandu.

http://help.sap.com/saphelp_nw04/helpdata/en/9f/db95e635c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/8d/3e4ec2462a11d189000000e8323d3a/content.htm

Using hierarchyial property files definitions for localization

Hi,
I am interested in knowing about tools or techniques using which I can establish a hierarchial properties files.
Eg: I have "Ok" buttons being used all over my application. I want to have a common file that defines the key value pair for OK and not repeat the value in each module specific properties file. Some thing like Java inheritance.
Appreciate help regarding the same.

Thanks Gautam for your reply.
Yes, I have tried. But as I mentioned above ATG DUST provides mechanism for unit testing that does not conform the unit-testing philosophy (yes, it is my IMHO and there probably should holly-war begin :-) ).
My idea is to create 'pure' unit tests with component properties harcoded in Java class files.
Edited by: 951305 on 7.8.2012 7.58
Edited by: 951305 on 7.8.2012 7.59

Logical file path problem in lsmw

Hi folks,
I created logical file path in FILE tcode. its created and assigned physical file path to logical file path.
then i am assigning that logical file path into lsmw step (specify file step).
under specify file i am assigning into import data and convert data.
once read data step completed read data must be save under this physical file but data is not saving under this path.
can any one help me out this..
1.can any one help how to create physical file in file tcode
2.how to assigne that physical file to lsmw step specify file

Hi Srikanth,
There is no need to create the logical file path using the FILE transaction.
Under Specify file step, you need to give your local file path in LEGACY DATA Section.
Please check the below link in using the LSMW step by step.
http://wiki.sdn.sap.com/wiki/display/ABAP/LSMWStepsin+Detail
Hope this helps.
Regards,
Satish Kanteti

Using logical files to query the AS400

Post Author: mrcarden
CA Forum: Data Connectivity and SQL
We are using Crystal Reports 10 and I am trying to write a report that pulls data from the AS400. We have never had a problem pulling data before because we always pulled from physical files. This time I am trying to pull data from a logical file that spans two physical files. Apparently there is a limitation in crystal that does not allow you to use a logical file? Does anyone know if there is a way around this? Any help would be appreciated and would save me a ton of work. If I cannot get the report to do this for me then I will have to write a program to pull the data from these two physical files into a new file and go from there.
Thanks!
Mike

Please refer to online document "OnDemWebSvcs.pdf". You can download this doc at:
Admin -> Web Services Administration -> Download Documentation
Edited by: PPL on Oct 8, 2011 12:13 AM

LSMW Logical file 'CS_BI_BOM_CREATE' is not assigned to physical file

Hi all,
I am creating LSMW tool for BOM by standard batch input program.
In the specify files push button i m getting this error
Logical file 'CS_BI_BOM_CREATE' is not assigned to physical file 'LSMW_C_MDM.119_MAT_BOM_001.lsmw.conv'
Message no. /SAPDMC/LSMW_OBJ_060045
anybody know how to proceed?
If i am going to Tcode - file and setting this one then i require a change request.
Is this the right way to proceed by changing it in "file" tcode.
Tell me all possible options.

Hi,
double click on row Converted data with file 'LSMW_C_MDM.119_MAT_BOM_001.lsmw.conv'
enter in field Logical Path: LSMW_C_MDM.119_MAT_BOM_001.lsmw.conv
enter in field Logical File: LSMW_C_MDM.119_MAT_BOM_001.lsmw.conv
and SAVE
the second option is go in transaction file and create the missing 'LSMW_C_MDM.119_MAT_BOM_001.lsmw.conv'
Regards Vassko!

Using logical files

Hi all,
I have an internal PDF-table that needs to be written to a file on the server, and I have been adviced to use a logical file.
Is it possible to use the OPEN DATASET functionality in conjunction with a logical file? If so, can you please provide me with an example?
All helpful answers will be rewarded.
Regards,
Mari Virik

Hi..
Steps to use Logical files
1. We can Maintain Logical Filenames in Tcode FILE.
2. We can call the FM File_Name_Get
This FM name takes the logical File name as input and Returns the Physical file
3. OPEN DATASET <Filename>
Reward if Helpful

Logical File creation in Logical path

Hi all,
I am after an info, how to create different logical file name in the same physical path.
Suppose I have physical path: X/claims/interface/outbound which is assigned to logical path LP
Now under this path I want to store some logical file say 1, 2, and 3
What would be the naming convention? & how to do it?
Any help would be highly appreciated.
Regards,
Kironmoy Banerjee.

Hi,
Use FM u2018FILE_GET_NAMEu2019 to assign the physical file name using a logical file name.
Remember you need to create u2018logical file nameu2019 using transaction u2013 FILE.
R/3 applications run on various platforms with various file systems. Hence we use platform-independent logical file names in our application programs.
Function module u2018FILE_GET_NAMEu2019 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>.
Santosh
Edited by: Santhosh Nagaraj on Sep 30, 2009 2:45 PM

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

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.

OHD - Logical File Name

Hello all,
I have a question about using a logical file name in an OHD (BI 7.0). Because we need to transport the OHD to a different server, we cannot use the File option in defining the OHD. We need to use the option, Logical File. In t-Code FILE, we cannot seem to create a physical path that the OHD recognizes.
This is the path in AL11 where we want the file to end up: /usr/sap/BIP/DVEBMGS17/work/GGLF010.CSV with a server of prdsap01. We are creating the OHD in a different system with a different server and path. How should the physical path (mapped to the logical path) be defined. I know we have to use <FILENAME> to represent the OHD output file (GGLF010). What variables do we use for the rest of the path? Do the variables have to be specifically defined or are they delivered by SAP?
Any help would be greatly appreciated!
Sheila

I don't know if this is relevant to this issue, but seems related.
When using OHD I noticed that two files are produced, the data file and the header file, unfortunatly when writing to the application server the file names output are identical. Therefore the header file overwrites the data file - anyone else experience this???
It is not possible to do anything about this using FILE settings so as a workaround (becasue I couldn't find/ an OSS note) I modified the standard class to ensure the data and header files names were unique:
METHOD: DETERMINE_FILENAME of class CL_RSB_FILE_GENERAL
o_filename_ctrl = l_filename.
*{ INSERT
*SAP BUG RENAMING HEADER FILE ELSE DUPLICATE FILES WILL OCCUR!!!
REPLACE '.CSV' IN o_filename_ctrl with '_HDR.CSV'.
*} INSERT
clear n_requid_current.
endmethod.
This assumes that the file output has .CSV as a file extension. This worked and now I get both the header and the data file.
If anyone could let me know if you have experienced this and how you resolved it would be nice.
cheers,
Asep

Test script logic file - Errror "Invalid Dimension Account"

Hi BPC Experts,
I am a new bee in BPC and have developed HCM applicaton in BPC 5.1. The Appset contains Finance, Rate & HCM applications.
I am working on HCM and wants to write a script logic file for HCM and it is giving an ERROR "Invalid Dimensin Account".
I have following dimensions in HCM Application:
account_hc --> type A
category_hc --> type C
company_hc --> type E
time_hc       --> time t
costcenter_hc --> type u
datasrc_hc      --> type d
employerole_hc --> type u
geography_hc --> type u
rptcurrency_hc --> type r.
I had defined Dimensions in system_cnstants file as mentioned below.
// application constants
*FUNCTION CATEGORYDIM         =CATEGORY_HC
*FUNCTION TIMEDIM =TIME_HC
*FUNCTION CURRENCYDIM =RPTCURRENCY_HC
*FUNCTION ENTITYDIM =COMPANY_HC
*FUNCTION ACCOUNTDIM =ACCOUNT_HC
*FUNCTION INTCODIM =INTCO
*FUNCTION CATEGORYDIM         =CATEGORY
*FUNCTION TIMEDIM =TIME
*FUNCTION CURRENCYDIM =RPTCURRENCY
*FUNCTION ENTITYDIM =ENTITY
*FUNCTION ACCOUNTDIM =ACCOUNT
// This part is needed when a RATE cube
// is associated to the application
// (FX = single or multi currency)
*FUNCTION THISAPP =HCM
*FUNCTION RATEAPP =RATE
*FUNCTION RATEENTITYDIM =RATESRC
*FUNCTION RATEACCOUNTDIM =RATE
*FUNCTION INPUTCURRENCYDIM =INPUTCURRENCY
*FUNCTION RATEENTITYMBR =RATEINPUT
*FUNCTION RATESRCCALCMBR =RATECALC
*FUNCTION AVGRATEID=AVG
*FUNCTION ENDRATEID=END
I tried to validate and save standard default script logic. But it gives me an error " NO match defined for lookup dimension Category"
So I could not use default logic file to write my script logic. Hence I have created HCM logic file. and Given the following script logic.
*XDIM_MEMBERSET ACCOUNT = XYZ_INC_RetPlan
*WHEN ACCOUNT
*IS XYZ_INC_RetPlan
*REC(FACTOR = 1.1, ACCOUNT)
*ENDWHEN
*COMMIT
While validat & save, I get an error "Invalid Dimension Account".
I do not understand why these errors occuring.
I have checked Category & Account dimensions checked. Every thing is ok. I have created Input schedules and they are working ok. It means the dimensions are fine.
Then why the error ?
Can you guys please guide me.
Appreciate your kind help.

Eswara,
try to close down BPC for ExCEl in case your IS/Reports are trying to access the APPlication.And also any other BPC ADmin screens accessing the same Application/Dimension.
1)try to only do a "process " on the account dimension without including the processing for Applications...
2)then try to do a process on the application.
Now your script should be able to recognize Account dimension and validate fine..
hope this helps...

Using a Logical File definition in LSMW

Similar Messages

Maybe you are looking for