Skip to Content
avatar image
Former Member

Logical Paths created using /nFILE transaction used in InfoSpokes

Hi all,

I am creating an InfoSpoke in 3.5, wherein I am using logical file/Path to store the file generated on application server.

My path is something like this

/interface/CCD/BWD/outbound.. (Where BWD is development server)

When I will transport this to quality (Say BWQ), i want my path to be

/interface/CCQ/BWQ/outbound..

So will it automatically convert when I transport infospoke and Logical Path/File from development to quality?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Sep 04, 2008 at 11:49 AM

    It depends on the exact definition of the logical file name and path.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Use a Function Module exit (Z_FILENAME_EXIT_name). See below.<br/><br/>

      <strong>Use</strong><br/>

      The physical file name is used by the function module FILE_GET_NAME at runtime to compose a complete platform-specific file name. If nothing is entered in the field Logical path, the file name may also contain the file path. In this case, the file name applies only to one hardware platform and must conform to the syntax of this platform.<br/><br/>

      <strong>Procedure</strong><br/>

      Enter a file name. You can use reserved words, which are substituted by the current values at run time. Reserved words must be enclosed in angle brackets (ignore the '):<br/><br/>

      <strong>Reserved word</strong> <strong>Word to be substituted</strong><br/>

      <'OPSYS'> Operating system in call<br/>

      <'INSTANCE'> R/3 application instance<br/>

      <'SYSID'> R/3 application name in SY-SYSID<br/>

      <'DBSYS'> Database system in SY-DBSYS<br/>

      <'SAPRL'> R/3 release in SY-SAPRL<br/>

      <'HOST'> Host name in SY-HOST<br/>

      <'CLIENT'> Client in SY-MANDT<br/>

      <'LANGUAGE'> Log on language in SY-LANGU<br/>

      <'DATE'> Date in SY-DATUM<br/>

      <'YEAR'> Year in SY-DATUM, 4-character<br/>

      <'SYEAR'> Year in SY-DATUM, 2-character<br/>

      <'MONTH'> Month in SY-DATUM<br/>

      <'DAY'> Day in SY-DATUM<br/>

      <'WEEKDAY'> Day of the week in SY-FDAYW<br/>

      <'TIME'> Time in SY-UZEIT<br/>

      <'STIME'> Hour and minute in SY-UZEIT<br/>

      <'HOUR'> Hour in SY-UZEIT<br/>

      <'MINUTE'> Minute in SY-UZEIT<br/>

      <'SECOND'> Seconds in SY-UZEIT<br/>

      <'PARAM_1'> External parameter 1<br/>

      <'PARAM_2'> External parameter 2<br/>

      <'PARAM_3'> External parameter 3<br/><br/>

      <'P=name'> Name of a profile parameter (see Report RSPARAM for valid values)<br/><br/>

      <'V=name'> Name of a variable (stored in variable table)<br/><br/>

      <'F=name'> Return value of a function module<br/>

      Naming convention for this function module:<br/>

      FILENAME_EXIT_name<br/><br/>

      <'Y=name'> Return value of a function module<br/>

      Naming convention for this function module:<br/>

      Y_FILENAME_EXIT_name<br/><br/>

      <'Z=name'> Return value of a function module<br/>

      Naming convention for this function module:<br/>

      Z_FILENAME_EXIT_name<br/><br/>

      <strong>Dependencies</strong><br/>

      The function module for the run-time variable <F=name> must meet the following requirements:<br/>

      u2022 Name<br/>

      The name must begin with "FILENAME_EXIT_".<br/>

      u2022 Parameter<br/>

      - An export parameter with name "OUTPUT" must exist. No structure may exist for the parameters<br/>

      - Import parameters are only supported if they have default values.<br/>

      - Table parameters are not supported.<br/><br/>

      Valid example: FILENAME_EXIT_EXAMPLE.<br/>