This discussion is archived
12 Replies Latest reply: Nov 16, 2012 8:26 AM by Hussein Sawwan-Oracle RSS

FNDLOAD problem 11g

968711 Newbie
Currently Being Moderated
Hi,

I need to execute FNDLOAD script.
I'm trying to go to FND_TOP path and then execute FNDLOAD script.
could u tell me ...where at what place i need to execute the script.

Database: 11g
Apps: R12.1

Thanks.
  • 1. Re: FNDLOAD problem 11g
    Hussein Sawwan-Oracle Employee ACE
    Currently Being Moderated
    I need to execute FNDLOAD script.
    I'm trying to go to FND_TOP path and then execute FNDLOAD script.
    could u tell me ...where at what place i need to execute the script.

    Database: 11g
    Apps: R12.1
    You can find FNDLOAD under $FND_TOP/bin directory. However, you do not need to go that directory to run FNDLOAD, just login as applmgr user, source the application env file and then you can run FNDLOAD from any directory.

    Thanks,
    Hussein
  • 2. Re: FNDLOAD problem 11g
    968711 Newbie
    Currently Being Moderated
    I don't have login access with applmgr, I logged in userid and executed env file.

    when i type FNDLOAD after executing env file, it is not recognizing, it says not found:

    also, can u let me know ...path for FND_TOP.
  • 3. Re: FNDLOAD problem 11g
    Hussein Sawwan-Oracle Employee ACE
    Currently Being Moderated
    965708 wrote:
    I don't have login access with applmgr, I logged in userid and executed env file.

    when i type FNDLOAD after executing env file, it is not recognizing, it says not found:

    also, can u let me know ...path for FND_TOP.
    If you source the correct application env file, you should be able to run FNDLOAD from any directory. To get the value of $FND_TOP directory, issue "echo $FND_TOP" after you source the application env file.

    Thanks,
    Hussein
  • 4. Re: FNDLOAD problem 11g
    968711 Newbie
    Currently Being Moderated
    I did execute .env file.
    when i type below at ......appl/fnd/12.0.0/bin , I get below message.

    $ FNDLOAD
    Message Dictionary couldn't open the FND message file for language US. Message Dictionary Error- A file pathname could not be constructed for the application FND. This error often indicates that the Application Basepath (e.g. FND_TOP) or Subdirectory (APPLMSG) environment variables do not have a valid value.

    USAGE-INSUFFICIENT ARGUMENTS
    USAGE-DEFAULT
    $



    Thanks.
  • 5. Re: FNDLOAD problem 11g
    Hussein Sawwan-Oracle Employee ACE
    Currently Being Moderated
    965708 wrote:
    I did execute .env file.
    when i type below at ......appl/fnd/12.0.0/bin , I get below message.
    What does "echo $FND_TOP" return?
    $ FNDLOAD
    Message Dictionary couldn't open the FND message file for language US. Message Dictionary Error- A file pathname could not be constructed for the application FND. This error often indicates that the Application Basepath (e.g. FND_TOP) or Subdirectory (APPLMSG) environment variables do not have a valid value.

    USAGE-INSUFFICIENT ARGUMENTS
    USAGE-DEFAULT
    Looks like you have not sourced the application env file.

    What does "which FNDLOAD" return?

    The env file can be found under $APPL_TOP directory "APPS<CONTEXT_NAME>.env".

    Thanks,
    Hussein
  • 6. Re: FNDLOAD problem 11g
    968711 Newbie
    Currently Being Moderated
    "which FNDLOAD" returns below:
    -------------------------------------------------

    ./FNDLOAD
  • 7. Re: FNDLOAD problem 11g
    Hussein Sawwan-Oracle Employee ACE
    Currently Being Moderated
    965708 wrote:
    "which FNDLOAD" returns below:
    -------------------------------------------------

    ./FNDLOAD
    What about "echo $FND_TOP" and "echo $APPL_TOP"?

    Thanks,
    Hussein
  • 8. Re: FNDLOAD problem 11g
    968711 Newbie
    Currently Being Moderated
    For both echo statements , it gives below output:

    ksh: echo : not found
  • 9. Re: FNDLOAD problem 11g
    Hussein Sawwan-Oracle Employee ACE
    Currently Being Moderated
    965708 wrote:
    For both echo statements , it gives below output:

    ksh: echo : not found
    This means that you have sourced the application env file and the echo executable file is not set in the PATH.

    Whatever user you are logged in as, please set the PATH to match the one that is set to applmgr user and try then (after sourcing the application env file).

    Thanks,
    Hussein
  • 10. Re: FNDLOAD problem 11g
    Chettarjee Newbie
    Currently Being Moderated
    I have created a concurrent request for using FNDLOAD. Please check this if this useful to you.

    1.0     XX GENERIC DOWNLOADER FOR PROMOTES (FNDLOAD)

    This Concurrent request is used by Developer to extract configuration information to a Physical file.

    Responsibility     : XX Application Developer
    Navigation      : Run Requests Run
         XX Generic DownLoader for Promotes (FNDLOAD)


    Parameters:
    Loader Configuration File:     LCT_PATH/afcpprog.lct
    Data File          :     LDT_PATH/XX_CON_ XXARR600_1234.ldt
    Entity          :     PROGRAM
    Parameter1          :     APPLICATION_SHORT_NAME=XXIF
    Parameter2          :     CONCURRENT_PROGRAM_NAME=XXARR600
    Parameter3          :

    Note: The location of lct files in the PRODUCTION will be similar to that of in TRAIN instance.

    Caution: Do not introduce space between texts in the Parameters.

    2.0     XX GENERIC UPLOADER FOR PROMOTES (FNDLOAD)
    Responsibility     : XX Application Developer
    Navigation      : Run Requests Run
         XX Generic Uploader for Promotes (FNDLOAD)


    Parameters:
    Loader Configuration File:     LCT_PATH/afcpprog.lct
    Data File          :     LDT_PATH/XX_CON_ XXARR600_1234.ldt
    Entity               :     PROGRAM
    Parameter1          :     UPLOAD_MODE=REPLACE
    Parameter2          :     CUSTOM_MODE=FORCE
    Parameter3          :

    Note: The loader and Data file shall refer to production folders. The location of lct files in the PRODUCTION will be similar to that of in TRAIN or DEVLP instance.

    Caution: Do not introduce space between texts in the Parameters.

    Concurrent Program     XX Generic DownLoader for Promotes (FNDLOAD)     Create a new concurrent program
    XX Generic DownLoader for Promotes (FNDLOAD)
    Short Name     : XX_FNDLOAD_DN
    Application     : XX Customizations/Interfaces
    Description     : Generic Loader for Promotes (FNDLOAD)
    Executable     : FNDLOAD
    Format          : Text
    Style          : Landscape
    Parameters
    For parameters please refer to SR document
    Concurrent Program     XX Generic Uploader for Promotes (FNDLOAD)     Create a new concurrent program
    XX Generic Uploader for Promotes (FNDLOAD)
    Short Name     : XX_FNDLOAD_UP
    Application     : XX Customizations/Interfaces
    Description     : Generic Loader for Promotes (FNDLOAD)
    Executable     : FNDLOAD
    Format          : Text
    Style          : Landscape
    Parameters
    For parameters please refer to SR document

    3.0     OVERVIEW
    FNDLOAD is a Generic Loader used to download application data from an Oracle Application instance (usually DEVLP/TEST/TRAIN) into a portable, editable text and then can be uploaded into another Oracle Application instance (PROD).

    The Generic Loader can download data from an application entity into a portable, editable text file. This file can then be uploaded into any other database to copy the data. Conversion between database store and file format is specified by a configuration file that is read by the loader.

    4.0     FNDLOAD UTILITY
    The Generic Loader downloads data from a database according to a configuration (.lct) file, and converts the data into a data file (.ldt). The Generic Loader can then upload this data to another database using a configuration file.

    The loader operates in one of two modes: DOWNLOAD or UPLOAD. In the DOWNLOAD mode, data is downloaded from the database to a text file; in the UPLOAD mode, data is uploaded from the text file to the database.

    Data structures supported by the loader include master-detail relationships and foreign key reference relationships.

    In both DOWNLOADing and UPLOADing, the structure of the data involved is described by a configuration file. The configuration file describes the structure of the data and also the access methods to use to copy the data into or out of the database. The same configuration file may be used for both UPLOADing and DOWNLOADing.

    The FNDLOAD executable can be found in $FND_TOP/bin and associated lct files are located in $FND_TOP/patch/115/import. Each FNDLOAD download execution will create .ldt and .log files. Upon execution of the FNDLOAD program, the created log file needs to be checked to verify that data has been downloaded or uploaded correctly.

    FNDLOAD can be executed as a Concurrent Program or as a UNIX command line utility with the following format and parameters.
    FNDLOAD apps/pwd 0 Y mode configfile datafile entity [parameter]
    Where
    < apps/pwd >          Apps schema/password
    < 0 Y >               Concurrent Program flags (0 – zero)
    < mode >          UPLOAD or DOWNLOAD
    < configfile >          Configuration lct file to use.
    < datafile >     Name of ldt data file written out when the FNDLOAD runs. This file is then used in an FNDLOAD upload to load the downloaded data into another application instance.
    < entity >     Entities to upload or download.
    < [param] >     Zero or more additional parameters used to provide bind values.


    5.0     SCOPE OF THE DOCUMENT
    FNDLOAD is applicable for the following configuration items only. Any configuration item other than the below mentioned will not be supported or documented.
    1.     Concurrent Executable
    2.     Concurrent Proram
    3.     Request Group
    4.     Value Set
    5.     Form
    6.     Form Function
    7.     Menu
    8.     LookupTypes&Code 
    6.0     NOMENCLATURE
    The name convention should be followed for download of ldt files. The typical ldt file should be named as XX_ENT_XXEntity_1234.ldt where
    XX           – Denotes Custom folder
    ENT           – Name of the entity(As mentioned below table)
    XXEntity     – Name of the Actual Entity in use
    1234           – Release Management number
    S No     Entity Short Name     Entity Name
    1.          EXE     Concurrent Executable
    2.          CON     Concurrent Program
    3.          RQG     Request Group
    4.          VST     Value Set
    5.          FRM     Form
    6.          FNC     Form Function
    7.          MNU     Menu
    8.          LKP     Lookup Type & Codes

    7.0     DETAILED USAGE OF FNDLOAD FOR EACH ENTITY
    7.1     CONCURRENT EXECUTABLE
         Download the executables entities using the afcpprog.lct
    Parameters in the concurrent program should be as follows for DOWNLOAD
    Concurrent Program: XX Generic DownLoader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afcpprog.lct
    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_EXE_ XXARR600_1234.ldt
    Entity          :     EXECUTABLE
    Parameter1     :     APPLICATION_SHORT_NAME=XXIF (YOUR App. Short Name)
    Parameter2          :     EXECUTABLE_NAME = XXARR600 (YOUR Exec. Short Name>

         Upload the executables entities using the afcpprog.lct
    Parameters in the concurrent program should be as follows for UPLOAD
    Concurrent Program: XX Generic Uploader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afcpprog.lct
    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_EXE_ XXARR600_1234.ldt
    Entity          :     EXECUTABLE
    Parameter1     :     UPLOAD_MODE=REPLACE
    Parameter2          :     CUSTOM_MODE=FORCE
    Parameter3     :     APPLICATION_SHORT_NAME=XXIF (YOUR App. Short Name)
    Parameter4          :     EXECUTABLE_NAME = XXARR600 (YOUR Exec. Short Name>
    7.2     CONCURRENT PROGRAM
         Download the concurrent program entities using the afcpprog.lct
    Parameters in the concurrent program should be as follows for DOWNLOAD
    Concurrent Program: XX Generic DownLoader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afcpprog.lct
    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_CON_XXARR600 _1234.ldt
    Entity          :     PROGRAM
    Parameter1          :     APPLICATION_SHORT_NAME=XXIF< App. Short Name>
    Parameter2          :     CONCURRENT_PROGRAM_NAME = XXARR600 < Con.Prg.Short Name>
         Upload the concurrent program entities using the afcpprog.lct
    Parameters in the concurrent program should be as follows for UPLOAD
    Concurrent Program: XX Generic Uploader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afcpprog.lct
    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_CON_ XXARR600_1234.ldt
    Entity          :     EXECUTABLE
    Parameter1     :     UPLOAD_MODE=REPLACE
    Parameter2          :     CUSTOM_MODE=FORCE
    Parameter3     :     APPLICATION_SHORT_NAME=XXIF [Optional parameter as this entity is available in the ldt file]
    Parameter4     :     CONCURRENT_PROGRAM_NAME = XXARR600 [Optional parameter as this entity is available in the ldt file]
    It is good practice to give the parameters
    7.3     REQUEST GROUP
         Download the Request Group entities using the afcpreqg.lct
    Parameters in the concurrent program should be as follows for DOWNLOAD
    Concurrent Program: XX Generic DownLoader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afcpreqg.lct
    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_RQG_XXREQG_1234.ldt
    Entity          :     REQUEST_GROUP
    Parameter1          :     APPLICATION_SHORT_NAME=FND < App. Short Name>
    Parameter2          :     REQUEST_GROUP_NAME=Application Developer Reports < Req.Grp Name> Not the code

         Upload the Request Group entities using the afcpreqg.lct
    Parameters in the concurrent program should be as follows for UPLOAD
    Concurrent Program: XX Generic Uploader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afcpreqg.lct

    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_RQG_XXREQG_1234.ldt
    Entity          :     REQUEST_GROUP
    Parameter1     :     UPLOAD_MODE=REPLACE
    Parameter2          :     CUSTOM_MODE=FORCE
    Parameter3     :     APPLICATION_SHORT_NAME=FND [Optional parameter as this entity is available in the ldt file]
    Parameter4     :     REQUEST_GROUP_NAME=Application Developer Reports [Optional parameter as this entity is available in the ldt file]
    It is good practice to give the parameters
    7.4     VALUE SET
         Download the Value Sets entities using the afffload.lct
    Parameters in the concurrent program should be as follows for DOWNLOAD
    Concurrent Program: XX Generic DownLoader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afffload.lct
    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_VST_XXVALUESET_1234.ldt
    Entity          :     VALUE_SET
    Parameter1          :     FLEX_VALUE_SET_NAME= XXVALUESET< Value Set Name>
         Upload the Value Sets entities using the afffload.lct
    Parameters in the concurrent program should be as follows for UPLOAD
    Concurrent Program: XX Generic Uploader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afffload.lct

    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_VST_XXVALUESET_1234.ldt
    Entity          :     VALUE_SET
    Parameter1     :     UPLOAD_MODE=REPLACE
    Parameter2          :     CUSTOM_MODE=FORCE
    Parameter3     :     FLEX_VALUE_SET_NAME= XXVALUESET [Optional parameter as this entity is available in the ldt file]
    It is good practice to give the parameters

    7.5     FORM
         Download the Forms entities using the afsload.lct
    Parameters in the concurrent program should be as follows for DOWNLOAD
    Concurrent Program: XX Generic DownLoader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afsload.lct
    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_FRM_XXFORM_1234.ldt
    Entity          :     FORM
    Parameter1          :     FORM_APP_SHORT_NAME=XXIF
    Parameter2          :     FORM_NAME= XXFORM

         Upload the Forms entities using the afsload.lct
    Parameters in the concurrent program should be as follows for UPLOAD
    Concurrent Program: XX Generic Uploader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afsload.lct

    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_FRM_XXFORM_1234.ldt
    Entity          :     FORM
    Parameter1     :     UPLOAD_MODE=REPLACE
    Parameter2          :     CUSTOM_MODE=FORCE
    Parameter3     :     FORM_APP_SHORT_NAME=XXIF [Optional parameter as this entity is available in the ldt file]
    Parameter4     :     FORM_NAME= XXFORM [Optional parameter as this entity is available in the ldt file]
    It is good practice to give the parameters

    7.6     FORM FUNCTION
         Download the Function (form function) entities using the afsload.lct
    Parameters in the concurrent program should be as follows for DOWNLOAD
    Concurrent Program: XX Generic DownLoader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afsload.lct
    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_FNC_XXFUNC_1234.ldt
    Entity          :     FUNCTION
    Parameter1          :     FUNC_APP_SHORT_NAME=XXIF
    Parameter2          :     FUNCTION_NAME=XXFUNC

         Upload the Function (form function)entities using the afsload.lct
    Parameters in the concurrent program should be as follows for UPLOAD
    Concurrent Program: XX Generic Uploader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afsload.lct

    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_FNC_XXFUNC_1234.ldt
    Entity          :     FUNCTION
    Parameter1     :     UPLOAD_MODE=REPLACE
    Parameter2          :     CUSTOM_MODE=FORCE
    Parameter3     :     FUNC_APP_SHORT_NAME=XXIF [Optional parameter as this entity is available in the ldt file]
    Parameter4     :     FUNCTION_NAME=XXFUNC [Optional parameter as this entity is available in the ldt file]
    It is good practice to give the parameters

    7.7     MENU
         Download the Menu entities using the afsload.lct
    Parameters in the concurrent program should be as follows for DOWNLOAD
    Concurrent Program: XX Generic DownLoader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afsload.lct
    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_MNU_XXMENU_1234.ldt
    Entity          :     MENU
    Parameter1          :     MENU= XXMENU

         Upload the Menu entities using the afsload.lct
    Parameters in the concurrent program should be as follows for UPLOAD
    Concurrent Program: XX Generic Uploader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/afsload.lct

    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_MNU_XXMENU_1234.ldt
    Entity          :     MENU
    Parameter1     :     UPLOAD_MODE=REPLACE
    Parameter2          :     CUSTOM_MODE=FORCE
    Parameter3     :     MENU= XXMENU [Optional parameter as this entity is available in the ldt file]
    It is good practice to give the parameters

    7.8     LOOKUP TYPES & CODE
         Download the Lookup Types entities using the aflvmlu.lct
    Parameters in the concurrent program should be as follows for DOWNLOAD
    Concurrent Program: XX Generic DownLoader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/aflvmlu.lct
    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_LKP_XXLOOKUP_1234.ldt
    Entity          :     FND_LOOKUP_TYPE
    Parameter1          :     APPLICATION_SHORT_NAME=XXIF
    Parameter2          :     LOOKUP_TYPE=XXLOOKUP
         Upload the Lookup Types entities using the aflvmlu.lct
    Parameters in the concurrent program should be as follows for UPLOAD
    Concurrent Program: XX Generic Uploader for Promotes (FNDLOAD)
    Loader Configuration File :      /traindb/oracle/trainappl/apps/apps_st/appl/fnd/
    12.0.0/patch/115/import/aflvmlu.lct

    Data File          :     /traindb/oracle/trainappl/apps/apps_st/appl/xxif_data/
    XX_LKP_XXLOOKUP_1234.ldt
    Entity          :     FND_LOOKUP_TYPE
    Parameter1     :     UPLOAD_MODE=REPLACE
    Parameter2          :     CUSTOM_MODE=FORCE
    Parameter3     :     APPLICATION_SHORT_NAME=XXIF [Optional parameter as this entity is available in the ldt file]
    Parameter4     :     LOOKUP_TYPE=XXLOOKUP [Optional parameter as this entity is available in the ldt file]
    It is good practice to give the parameters
    The following table lists the most common entities that can be downloaded and/or uploaded and the associated FNDLOAD configuration (.lct) file.
    Note: Some lct file formats support multiple entity types.
    Config(.lct) File     Used for     Entity     Parameters
    afcpprog.lct     Concurrent Executable     EXECUTABLE     APPLICATION_SHORT_NAME
    EXECUTABLE_NAME
    afcpprog.lct     Concurrent Program     PROGRAM     APPLICATION_SHORT_NAME
    CONCURRENT_PROGRAM_NAME
    afcpreqg.lct     Request Groups     REQUEST_GROUP     APPLICATION_SHORT_NAME
    REQUEST_GROUP_NAME
    afffload.lct     Flexfield Value Sets     VALUE_SET     FLEX_VALUE_SET_NAME
    afsload.lct     Forms     FORM     FORM_APP_SHORT_NAME
    FORM_NAME
    afsload.lct     Function     FUNCTION     FUNC_APP_SHORT_NAME
    FUNCTION_NAME
    afsload.lct     Menu     MENU     MENU_NAME
    aflvmlu.lct     Lookups Configuration File     FND_LOOKUP_TYPE     APPLICATION_SHORT_NAME
    LOOKUP_TYPE
                   


    8.0     CAUTION / WARNING
    Use only the loader files provided by Oracle E-business Suite. If you use files not provided by Oracle E-Business Suite or modify the provided scripts you risk corrupting your database. Oracle does not support the use of custom loader files or modified Oracle E-Business Suite loader files.

    9.0     LIMITATIONS
    When the TRAIN data is uploaded to PROD instance, the WHO columns will display the data as in TRAIN instance and the data fields (Created_Date and Last Updated Date) are truncated and the format will be DD-MON-YYYY

    10.0     MISCELLANEOUS
    APPS user should have access for FNDLOAD to read, write and execute permissions.

    11.0     OPEN / CLOSE ISSUES
  • 11. Re: FNDLOAD problem 11g
    968711 Newbie
    Currently Being Moderated
    Hussein,

    Could you let me know...how to set echo executable file in the PATH.


    Thanks.
  • 12. Re: FNDLOAD problem 11g
    Hussein Sawwan-Oracle Employee ACE
    Currently Being Moderated
    965708 wrote:
    Hussein,

    Could you let me know...how to set echo executable file in the PATH.


    Thanks.
    Login as applmgr user, source the application and issue "echo $PATH". Use the same path to set your OS user path by using one of the following:

    1) Manually --> export PATH=<Path you get from applmgr>:$PATH
    2) Update the .bash_profile of your OS user and login again -- Issue "echo $PATH" to verify

    Thanks,
    Hussein

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points