Infospoke logical file name question

Experts,
We have what seems to be an anomaly that we need to understand.
On the application server, when we extract our infospokes, two files are generated , a schema and a data file.
the naming convention is like
zxxx.infoprovider_date
eg. zxxx.infoprovider_20080501
now what happens is,
sometimes, some data files,
come out on the application server with the name
zxxx.infoprovider_1date
These are the same files that came out fine(without the '1') on a previous date .
Also there are no duplicate files on the same date .
Any ideas what could be causing this change in file name?
Thanks
Edited by: CC on May 8, 2008 7:18 PM

Hi,
Just check the Job Log . It might show some messages as to what is causing such behavoiur.
regards,
Venkat

Similar Messages

InfoSpoke and Logical File Name

We have created an Infospoke to extract data to a logical file. When we define the Logical File Name Definition using the FILE transaction, we have to enter a physical file name. This will require us to create a new Logical File Name Definition for every Infospoke. Instead of hard coding the physical file name in the Logical File Name Definition for each InfoSpoke we would like to dynamically create the file name to include the InfoObject Name (cube, ODS object, etc) in the physical file name.
We have tried to use the <F=CPROG> substitution parameter in the logical file name. When the function module FILENAME_EXIT_CPROG is called we find that we do not have access to any information other then what is available in the system variables (structure SYST)
1. Are there any modification to the class CL_RSB_FILE_LOGICAL and method DETERMINE_FILENAME that we can make to create a logical file name that includes the InfoSpoke name?
2. Is there any way to access any system information from within the FILENAME_EXIT_CPROG function module that would give us the InfoSpoke information?

I think you can modify the method 'DETERMINE_FILENAME' for this.
In the call to FILE_GET_NAME_USING_PATH FM, add an additional parameter 'parameter_1', and set its value to O_R_REQUEST-N_OHDEST (this should have the open hub destination name).
call function.....
parameter_1 = O_R_REQUEST-N_OHDEST
If the logical filename contains placeholder (< > ??), it should now be replaced with the destination name.
I am not very familiar with ABAP objects. You might wish to check whethet it is possible without a 'modification' like this, where you create another Z implementation of the class and delegate(?).

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

Archiving : Change of Logical File Name & physical path

Hello friends,
We are doing archiving for a Z* archiving object.
We run a write job(not delete job till now) for this archiving object and it created archive files in .../SYS/GLOBAL directory as was expected from settings of Logical File Name and hence physical path corresponding to it. So far no problem..
Now, requirement is to change this path and for this i created a new Logical File Name with a different physical path.
My concern is, about already archived data in older path. Should i only run delete job for that session ?
Or should i copy the archive files to new path and then start delete job OR do a write job once again..
please suggest.
thanks
ashish

Hello Juan,
Ok, i can copy the files, those are not too many as we did it only for 2 months selection.
Can i go for write job again for same selection ? If yes, probably it will create a new session.. correct ? and then i will go for deletion for new session.
If this is also correct way, i want to do this.. as till now this has been one for only 2 months and we are going to do for 8 yrs.
One more question, will the be any problem for having 2 sessions for same selection.. means 2 write or archive job for same selection.
thanks
ashish

How to create the logical file name

Hi All,
    I have requirement where i need to post the Inventory Management data. for this i need to execute std. program RM07MMBL which is having logical file name in the selection screen. but i have placed my input file in application server.
   Can any one tell how to create the Logical filename which refers the physical path. I also tried <b>t-code SF01 & Table - FILENAMEC</b>I and found that we need to add an entry in this table but i really dont know how we have to do since this table cannot be maintained in SM30 also..
Help Me.
Thanks in Advance!...
Regards,
Ramkumar

Hi Ram,
Try using FILE transaction code...
Follow these steps to create:::
Double click on Logical file Path Definition
Click on New Entries,
Give Logical file Path name as Z_LOGICAL PATH and save it
now choose this path and double click on Assignemt of Physical path to Logical path
double click on the OS name
Give some description and give some Physical path name from AL11 transaction and save it
Now Double click on Logical File Name Definition,
Click on New Entries,
Give some logical file name: Z_LOGICAL_FILENAME
Physical file: test
Data Format: BIN
Logical Path: Z_LOGICAL PATH
Hope this helps
Regards,
Phani
Message was edited by:
        Sivapuram Phani Kumar

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

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

Logical file names and Physical file names

Hi Guys...
Can you let me know what is the difference between Logical file names and Physical file names?
Regards,
Rohit

Using Logical Files in ABAP Programs http://help.sap.com/saphelp_nw04/helpdata/en/9f/db95e635c111d1829f0000e829fbfe/content.htm
Creating and Defining Logical Filenames
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3df8358411d1829f0000e829fbfe/content.htm

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

To test how can we use the opt 'logical file name' to name the file based

Hi Sir/Madam,
to test how can we use the opt 'logical file name' to name the file based on the selection made in the dtp run for extracting data as flat file.

Hi Vishali,
In the DTP select the file location as application server and give the logical file path. The actual file and logical path can be created using transaction "FILE" and "AL11".
Rest of the process is same as that of extraction from local file.
Regards,
Durgesh.

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

I am getting data from a flat file and want to know how to create a logical file name instead of hard-coding the path.
Please help

Hi,
you can create logical file name in transaction SF01..
Hope it helps ,
Ravi

Logical file name transport

Hi Friends,
I have created logical path and logical file name using FILE Transaction code, the problem was logical Path was saved in transport request and logical file name not saved in Transport request, Could you please help me logical file name save are not in the transport request.
Thanks in advance,
Jayachandran.A

Run transaction FILE, in the menu goto "Table view", "transport", select or create a transport request. In node "logical file name definition, cross client", select your file names and in the menu bar click on "include in request"
Regards,
Raymond

TCODE SARA and its variant in logical file name

Hi forum,
how can I create a logical file name (FILE tcode) with execution varian of SARA for archiving ?
Regards.
Ganimede Dignan.

Hello Ganimede,
Apart from the very good note suggested by Naveen please check this as well;
http://help.sap.com/saphelp_nw2004s/helpdata/en/8d/3e4ec2462a11d189000000e8323d3a/content.htm
You ca get more information from SAP help- data archiving section.
Regards.
Ruchit.
Message was edited by:
Ruchit Khushu

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

Infospoke logical file name question

Similar Messages

Maybe you are looking for