UNIX in Oracle APPS Host Program by Avinash
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Transfering the Files from server1 to the server2 when ever they place TEXT data files in server1 and loading the data into the custom staging table by calling CTL file and after loading then moving the files in server2 from one path to another path#####################################################################################
## Program name: XX_EXP_FTP_INBOUND.prog
##
## This program runs for loading the data of XX Expeditors
## into the staging table and renames the data file by appending the date to it.
##
## Parameters:
## $i name of file to be uploaded
## $1 user/password of the database
##
## Created by: Creation Date Changes
##
##-----------------------------------------------------------------------------------------------------------------------
MOP_FCP_LOGIN=$1; export MOP_FCP_LOGIN
MOP_FCP_USERID=$2; export MOP_FCP_USERID
MOP_FCP_USERNAME=$3; export MOP_FCP_USERNAME
MOP_REQID=$4; export MOP_REQID
ORA_USER_PASS=$1; export ORA_USER_PASS
USERID=$2; export USERID
USERNAME=$3; export USERNAME
REQUESTID=$4; export REQUESTID
L_USER_NAME="XX"
L_PWD="Rs8&kcH4"
L_REMOTE_PATH="/XX/outgoing"
L_REMOTE_FILE="*.TXT"
L_LOCAL_PATH= "XX_TOP/bin/XX_EXP_INBOUND"
echo "Server Name is : " $L_SERVER_NAME
echo "User Name : " $L_USER_NAME
echo "Password : " $L_PWD
echo "Remote Path is : " $L_REMOTE_PATH
echo "Remote File is : " $L_REMOTE_FILE
echo "Local Path is : " $L_LOCAL_PATH
echo "Database is : " $MOP_FCP_LOGIN
cd $L_LOCAL_PATH
ftp -nv ftp.expd.com <<EOF> $XX_TOP/bin/XX_EXP_INBOUND/log.log1 2>&1
user $L_USER_NAME $L_PWD
ascii
prompt
cd $L_REMOTE_PATH
mget *.TXT
mdelete *.TXT
echo "Sucessfully deleted the file in Remote and placed the files in local XX_EXP_INBOUND/Archive Directory"
bye
EOF
echo "All are files are Successfully copied to local Inbound path"
COUNT=`find $XX_TOP/bin/XX_EXP_INBOUND/ *.TXT -type f -maxdepth 1 -exec ls -l {} \;|wc -l`
echo $COUNT
if [ $COUNT -gt 0 ]
then
for i in `find $XX_TOP/bin/XX_EXP_INBOUND/ *.TXT -type f -maxdepth 1 -exec ls {} \;`
do
sqlldr apps/apps control=$XX_TOP/bin/XX_EXP_SHIP_CTL.ctl data=$i log=$XX_TOP/bin/XX_EXP_SHIP_CTL.log
mv $i $XX_TOP/bin/XX_EXP_INBOUND/Archive
echo "SQL*Loader execution successful"
echo "Loaded files are moved to Archive Successfully"
done
else
echo "No files exist to load"
fi
##################################################################################
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Transfering the Files from server1 to the server2 when ever they place TEXT data files in server1 and loading the data into the custom staging table by calling CTL file and after loading then moving the files in server2 from one path to another path#####################################################################################
## Program name: XX_EXP_FTP_INBOUND.prog
##
## This program runs for loading the data of XX Expeditors
## into the staging table and renames the data file by appending the date to it.
##
## Parameters:
## $i name of file to be uploaded
## $1 user/password of the database
##
## Created by: Creation Date Changes
##
##-----------------------------------------------------------------------------------------------------------------------
MOP_FCP_LOGIN=$1; export MOP_FCP_LOGIN
MOP_FCP_USERID=$2; export MOP_FCP_USERID
MOP_FCP_USERNAME=$3; export MOP_FCP_USERNAME
MOP_REQID=$4; export MOP_REQID
ORA_USER_PASS=$1; export ORA_USER_PASS
USERID=$2; export USERID
USERNAME=$3; export USERNAME
REQUESTID=$4; export REQUESTID
L_USER_NAME="XX"
L_PWD="Rs8&kcH4"
L_REMOTE_PATH="/XX/outgoing"
L_REMOTE_FILE="*.TXT"
L_LOCAL_PATH= "XX_TOP/bin/XX_EXP_INBOUND"
echo "Server Name is : " $L_SERVER_NAME
echo "User Name : " $L_USER_NAME
echo "Password : " $L_PWD
echo "Remote Path is : " $L_REMOTE_PATH
echo "Remote File is : " $L_REMOTE_FILE
echo "Local Path is : " $L_LOCAL_PATH
echo "Database is : " $MOP_FCP_LOGIN
cd $L_LOCAL_PATH
ftp -nv ftp.expd.com <<EOF> $XX_TOP/bin/XX_EXP_INBOUND/log.log1 2>&1
user $L_USER_NAME $L_PWD
ascii
prompt
cd $L_REMOTE_PATH
mget *.TXT
mdelete *.TXT
echo "Sucessfully deleted the file in Remote and placed the files in local XX_EXP_INBOUND/Archive Directory"
bye
EOF
echo "All are files are Successfully copied to local Inbound path"
COUNT=`find $XX_TOP/bin/XX_EXP_INBOUND/ *.TXT -type f -maxdepth 1 -exec ls -l {} \;|wc -l`
echo $COUNT
if [ $COUNT -gt 0 ]
then
for i in `find $XX_TOP/bin/XX_EXP_INBOUND/ *.TXT -type f -maxdepth 1 -exec ls {} \;`
do
sqlldr apps/apps control=$XX_TOP/bin/XX_EXP_SHIP_CTL.ctl data=$i log=$XX_TOP/bin/XX_EXP_SHIP_CTL.log
mv $i $XX_TOP/bin/XX_EXP_INBOUND/Archive
echo "SQL*Loader execution successful"
echo "Loaded files are moved to Archive Successfully"
done
else
echo "No files exist to load"
fi
##################################################################################
Create a link for the Shell script
Eg:- ln –s
$FND_TOP/bin/fndcpesr XX_EXP_FTP_OUTBOUND
Eg:- ln –s
$FND_TOP/bin/fndcpesr <Shell_Script_Name>
after creating the link in execuatble call the shell
script name with having the execution method as 'HOST'
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Approval Groups
1. Approval Groups – Download
FNDLOAD apps/pw 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesappg.lct xx_gssm_ame_apgrps.ldt AME_APPROVAL_GROUPS APPROVAL_GROUP_NAME=xx% TRANSACTION_TYPE_ID=’SSHRMS’ APPLICATION_SHORT_NAME=PER
Approval Groups – Upload
FNDLOAD apps/pw1 0 Y UPLOAD $PER_TOP/patch/115/import/amesappg.lct xx_gssm_ame_apgrps.ldt
2. Approval Groups Configuration – Download
FNDLOAD apps/pw 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesaagc.lct xx_gssm_ame_apgrps_cf.ldt AME_APPROVAL_GROUP_CONFIG APPROVAL_GROUP_NAME=xx% TRANSACTION_TYPE_ID=’SSHRMS’ APPLICATION_SHORT_NAME=PER
Approval Groups Configuration – Upload
FNDLOAD apps/pw1 0 Y UPLOAD $PER_TOP/patch/115/import/amesaagc.lct xx_gssm_ame_apgrps_cf.ldt
1. Approval Groups – Download
FNDLOAD apps/pw 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesappg.lct xx_gssm_ame_apgrps.ldt AME_APPROVAL_GROUPS APPROVAL_GROUP_NAME=xx% TRANSACTION_TYPE_ID=’SSHRMS’ APPLICATION_SHORT_NAME=PER
Approval Groups – Upload
FNDLOAD apps/pw1 0 Y UPLOAD $PER_TOP/patch/115/import/amesappg.lct xx_gssm_ame_apgrps.ldt
2. Approval Groups Configuration – Download
FNDLOAD apps/pw 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesaagc.lct xx_gssm_ame_apgrps_cf.ldt AME_APPROVAL_GROUP_CONFIG APPROVAL_GROUP_NAME=xx% TRANSACTION_TYPE_ID=’SSHRMS’ APPLICATION_SHORT_NAME=PER
Approval Groups Configuration – Upload
FNDLOAD apps/pw1 0 Y UPLOAD $PER_TOP/patch/115/import/amesaagc.lct xx_gssm_ame_apgrps_cf.ldt
Conditions
1. Conditions – Download
FNDLOAD apps/pw 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesconk.lct xx_gssm_ame_cond.ldt AME_CONDITIONS ATTRIBUTE_NAME=’xx%’ TRANSACTION_TYPE_ID=’SSHRMS’ APPLICATION_SHORT_NAME=PER
Conditions – Upload
FNDLOAD apps/pw1 0 Y UPLOAD $PER_TOP/patch/115/import/amesconk.lct xx_gssm_ame_cond.ldt
FNDLOAD Migration
scripts for AME Attribute, Condition, Approval Groups, Rules and Transaction
Types
1. Attribute – Download
FNDLOAD apps/pw 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesmatt.lct xx_gssm_ame_attr.ldt AME_ATTRIBUTES ATTRIBUTE_NAME=’xx%’ TRANSACTION_TYPE_ID=’SSHRMS’ APPLICATION_SHORT_NAME=PER
Attributes – Upload
FNDLOAD apps/pw1 0 Y UPLOAD $PER_TOP/patch/115/import/amesmatt.lct xx_gssm_ame_attr.ldt
2. Attribute Usage – Download
FNDLOAD apps/pw 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesmatr.lct xx_gssm_ame_attr_usg.ldt AME_ATTRIBUTE_USAGES ATTRIBUTE_NAME=’xx%’ TRANSACTION_TYPE_ID=’SSHRMS’ APPLICATION_SHORT_NAME=PER
Attribute Usages – Upload
FNDLOAD apps/pw1 0 Y UPLOAD $PER_TOP/patch/115/import/amesmatr.lct xx_gssm_ame_attr_usg.ldt
Data
Synchronization?
Data Synchronization is a process in
which some setup data would be synchronized, and this would be more important
when you are working in Oracle application development/implementation project.
The equally important that ATG data Migration takes place necessary to
synchronize the data across databases instance during
· Installations (New descriptive flex field creations etc)
· Upgrades (Apps upgrade etc.)
· Maintenance (Value set changes etc.)
· Installations (New descriptive flex field creations etc)
· Upgrades (Apps upgrade etc.)
· Maintenance (Value set changes etc.)
Generic Loader (FNDLOAD)The Generic Loader
(FNDLOAD) is a concurrent program that can move Oracle Applications data
between database and text file representations. The loader reads a
configuration file to determine what data to access. For information on
specific configuration files consult the Open Interfaces Guide for your product
group.
From an FNDLOAD perspective, there is
absolute no limitation on parallel execution. Parallel upload of concurrent
programs and responsibilities should through fine unless upload logic in LCT
file restrict the same.
There is no way to limit the download
of the value hierarchy data with the existing flexfield loader logic.
If this data is removed manually from the .ldt file generated when downloading data, the upload might error out as a result and this is NOT a supported method of using fndload and the corresponding generated data.
If this data is removed manually from the .ldt file generated when downloading data, the upload might error out as a result and this is NOT a supported method of using fndload and the corresponding generated data.
OverviewThe 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.
The Generic Loader downloads data
from a database according to a configuration (.lct) file, and converts the data
into a data file (.ldt file). 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 a 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.
When downloading, the Generic Loader
creates a second file, called the data file that contains the structured data
selected for downloading. The data file has a standard syntax for representing
the data that has been downloaded. When uploading, the Generic Loader reads a
data file to get the data that it is to upload. In most cases, the data file
was produced by a previous download, but may have come from another source. The
data file cannot be interpreted without the corresponding configuration file
available.
What can be done?
These are the extensive list which can be done through FNDLOAD
· Concurrent Programs, Executables
· Request Groups, Request Sets
· Profile Options
· Key and Descriptive Flexfields
· Menus and Responsibilities
· Forms and Form Functions/Personalizations
· Attachments
· Messages
· Value Sets and Values
· Lookup Types
· User Responsibilities
· Printer Definitions
· FND Dictionary
· Help Configuration
· Document Sequences
· Alerts
· Concurrent Manager Schedules
These are the extensive list which can be done through FNDLOAD
· Concurrent Programs, Executables
· Request Groups, Request Sets
· Profile Options
· Key and Descriptive Flexfields
· Menus and Responsibilities
· Forms and Form Functions/Personalizations
· Attachments
· Messages
· Value Sets and Values
· Lookup Types
· User Responsibilities
· Printer Definitions
· FND Dictionary
· Help Configuration
· Document Sequences
· Alerts
· Concurrent Manager Schedules
The FNDLOAD: Concurrent Program –
FNDLOAD can be executed as a concurrent program.
Some advantages when using FNDLOAD1. Because
downloaded data is stored in a text file, version administration is possible
2. There is nothing to worry to go to purchase because Investment = 0$
3. No learning curve. this is relief for developer and dba
4. Fully supported and recommended by Oracle
5. Capture the migrations in a file and use it during installations, clones etc. to migrate in batch
6. Pin-point when something happened and where (database) easily
7. Your AOL data migration process is now simplified and streamlined goal attained
2. There is nothing to worry to go to purchase because Investment = 0$
3. No learning curve. this is relief for developer and dba
4. Fully supported and recommended by Oracle
5. Capture the migrations in a file and use it during installations, clones etc. to migrate in batch
6. Pin-point when something happened and where (database) easily
7. Your AOL data migration process is now simplified and streamlined goal attained
Some disadvantages when using FNDLOAD1. Applications
patching mechanisms use FNDLOAD heavily possibility of negative impact is not
zero
2. UPLOAD_MODE=REPLACE only for menus
3. No validation against migrating database/instance sensitive data
2. UPLOAD_MODE=REPLACE only for menus
3. No validation against migrating database/instance sensitive data
SyntaxThe Generic Loader is a concurrent program
named FNDLOAD. The concurrent executable takes the following parameters:
FNDLOAD apps/pwd 0 Y mode configfile
datafile entity [ param ...]
where
where
pwd>The APPS schema and password in the form
username/password[@connect_string]. If
connect_string is omitted, it is taken in a platform-specific manner from the environment
using the name TWO_TASK.
connect_string is omitted, it is taken in a platform-specific manner from the environment
using the name TWO_TASK.
< 0 Y >Concurrent program flags.
mode
UPLOAD or DOWNLOAD. UPLOAD causes the datafile to be uploaded to the database. DOWNLOAD causes the loader to fetch rows and write them to the datafile.
UPLOAD or DOWNLOAD. UPLOAD causes the datafile to be uploaded to the database. DOWNLOAD causes the loader to fetch rows and write them to the datafile.
The configuration file to use (usually with a suffix of .lct, but not enforced or supplied by the loader).
The data file to write (usually with a suffix of .ldt, but not enforced or supplied by the loader). If the data file already exists, it will be overwritten.
The entity(ies) to upload or download. When uploading, always upload all entities, so specify a “-” to upload all entities.
< [param] >Zero or more additional parameters
are used to provide bind values in the access SQL (both UPLOAD and DOWNLOAD).
Each parameter is in the form NAME=VALUE. NAME should not conflict with an
attribute name for the entities being loaded.
Modes of OperationThis is important because it would
drive the whole flow, and it always be either Upload or Download.
Example of downloadFNDLOAD apps/pwd 0 Y DOWNLOAD
${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt \ PROGRAM
CONCURRENT_PROGRAM_NAME= concurrent_program_short_name>
APPLICATION_SHORT_NAME=
Example of UploadFNDLOAD apps/pwd 0 Y UPLOAD ${FND_TOP}/patch/115/import/afcpprog.lct
myfile.ldt – CUSTOM_MODE=FORCE undocumented parameter
What are FNDLOAD Options?· Application level
OR single entity level download
o (Example) Download all the profile options of Inventory or just the INV: Default Primary UOM
· Entire OR Partial upload of a data file
o (Example) Upload the entire myfile.ldt or just a single entity indicated by – and mode UPLOAD or UPLOAD_PARTIAL
o Entity name required for UPLOAD_PARTIAL mode
· Custom mode force update
o To override Oracle’s upload algorithm and update the custom AOL data regardless, use CUSTOM_MODE= FORCE
o UPLOAD_MODE= REPLACE (only for menus)
· Support for NLS uploads
o NLS data uploads for translated columns are supported, use UPLOAD_MODE= NLS
o (Example) Download all the profile options of Inventory or just the INV: Default Primary UOM
· Entire OR Partial upload of a data file
o (Example) Upload the entire myfile.ldt or just a single entity indicated by – and mode UPLOAD or UPLOAD_PARTIAL
o Entity name required for UPLOAD_PARTIAL mode
· Custom mode force update
o To override Oracle’s upload algorithm and update the custom AOL data regardless, use CUSTOM_MODE= FORCE
o UPLOAD_MODE= REPLACE (only for menus)
· Support for NLS uploads
o NLS data uploads for translated columns are supported, use UPLOAD_MODE= NLS
Where is Configuration File LocatedBy default Oracle
delivers most of configuration files that can be used to download certain
entities.
· Configuration files with extension .lct
o On Unix – all the configuration files are in $FND_TOP/patch/115/import directory
o On Unix Oracle also places the original configuration files in $FND_TOP/admin/import directory
· Data files with extension .ldtFNDLOAD File Structure
· The configuration files (.lct) are delivered and maintained by Oracle.
· It has entity definitions, parent-child relationships and user input parameters identified by :NAME.
· Downloading a parent automatically downloads all children – (Example) Concurrent Program download.
· The data files (.ldt) have both entity definition and the data.
· It also shows the version and the location of the configuration file (.lct) that was used.
· Without the configuration file, a data file is useless.
· Without the data file, a configuration file is meaningless.
· Configuration files with extension .lct
o On Unix – all the configuration files are in $FND_TOP/patch/115/import directory
o On Unix Oracle also places the original configuration files in $FND_TOP/admin/import directory
· Data files with extension .ldtFNDLOAD File Structure
· The configuration files (.lct) are delivered and maintained by Oracle.
· It has entity definitions, parent-child relationships and user input parameters identified by :NAME.
· Downloading a parent automatically downloads all children – (Example) Concurrent Program download.
· The data files (.ldt) have both entity definition and the data.
· It also shows the version and the location of the configuration file (.lct) that was used.
· Without the configuration file, a data file is useless.
· Without the data file, a configuration file is meaningless.
FNDLOAD Files· Key files: .lct and .ldt
· FNDLOAD must be run as the apps user not as applsys or any other user, otherwise an Ora-6550 error will be received.
· Both are easily readable, editable and portable.
· Do not modify Oracle .lct files.
· Use a favorite editor to manipulate only the .ldt files but be cautious about data type, length, delimiter placements etc.
· Use the log file outputs or .ldt file contents creatively for quick file comparisons and answer questions as: (Why can this be accessed? What is that profile option name, value and level? What is the value set used for that DFF segment attribute10 etc.)
· Partial string searches (which value set has Priority something in its where clause, etc)
· FNDLOAD must be run as the apps user not as applsys or any other user, otherwise an Ora-6550 error will be received.
· Both are easily readable, editable and portable.
· Do not modify Oracle .lct files.
· Use a favorite editor to manipulate only the .ldt files but be cautious about data type, length, delimiter placements etc.
· Use the log file outputs or .ldt file contents creatively for quick file comparisons and answer questions as: (Why can this be accessed? What is that profile option name, value and level? What is the value set used for that DFF segment attribute10 etc.)
· Partial string searches (which value set has Priority something in its where clause, etc)
Some
sample examples
1 – Printer Styles
FNDLOAD apps/pwd@seeddb 0 Y
DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt STYLE
PRINTER_STYLE_NAME=”printer style name”
2 – Lookups
FNDLOAD apps/pwd@seeddb 0 Y DOWNLOAD
$FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME=”prod”
LOOKUP_TYPE=”lookup name”
3 – Descriptive Flexfield with all of specific Contexts
FNDLOAD apps/pwd@seeddb 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afffload.lct file_name.ldt DESC_FLEX
P_LEVEL=?COL_ALL:REF_ALL:CTX_ONE:SEG_ALL? APPLICATION_SHORT_NAME=”prod”
DESCRIPTIVE_FLEXFIELD_NAME=”desc flex name” P_CONTEXT_CODE=”context name”
4 – Multiple Flexfields
Use a combination of
APPLICATION_SHORT_NAME and DESCRIPTIVE_FLEXFIELD_NAME names ie.
APPLICATION_SHORT_NAME=PER >> will download all PER flexfields
DESCRIPTIVE_FLEXFIELD_NAME=PER_% >> will download all flexfields that
start with ‘PER_’.
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct
file_name.ldt DESC_FLEX DESCRIPTIVE_FLEXFIELD_NAME="PER_%"
file_name.ldt DESC_FLEX DESCRIPTIVE_FLEXFIELD_NAME="PER_%"
5 – Key Flexfield Structures
FNDLOAD apps/pwd@seeddb 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afffload.lct file_name.ldt KEY_FLEX
P_LEVEL=?COL_ALL:FQL_ALL:SQL_ALL:STR_ONE:WFP_ALL:SHA_ALL:CVR_ALL:SEG_ALL?
APPLICATION_SHORT_NAME=”prod” ID_FLEX_CODE=”key flex code”
P_STRUCTURE_CODE=”structure name”
6 – Concurrent Programs
FNDLOAD apps/pwd@seeddb 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM
APPLICATION_SHORT_NAME=”prod” CONCURRENT_PROGRAM_NAME=”concurrent name”
7 – Value Sets
FNDLOAD apps/pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct
file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME=”value set name”
8 – Value Sets with values
FNDLOAD apps/pwd@seeddb 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE
FLEX_VALUE_SET_NAME=”value set name”
9 – Profile Options
FNDLOAD apps/pwd@seeddb 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afscprof.lct file_name.ldt PROFILE
PROFILE_NAME=”profile option” APPLICATION_SHORT_NAME=”prod”
10 – Request Group
FNDLOAD apps/pwd@seeddb 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct
file_name.ldt REQUEST_GROUP REQUEST_GROUP_NAME=”request group”
APPLICATION_SHORT_NAME=”prod”
11 – Request Sets
FNDLOAD apps/pwd@seeddb 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afcprset.lct file_name.ldt REQ_SET APPLICATION_SHORT_NAME=”prod”
REQUEST_SET_NAME=”request set”
12 – Responsibilities
FNDLOAD apps/pwd@seeddb 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY
RESP_KEY=”responsibility"
13 – Responsibilities with all Security Groups
FNDLOAD apps/ 0 Y DOWNLOAD FND_TOP/patch/115/import/afscursp.lct .ldt
FND_USER USER_NAME="" SECURITY_GROUP=% DATA_GROUP_NAME=%
FND_USER USER_NAME="" SECURITY_GROUP=% DATA_GROUP_NAME=%
14 – Menus
FNDLOAD apps/ pwd@seeddb 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afsload.lct file_name.ldt MENU MENU_NAME=”menu_name”
15 – Forms/Functions/Personalizations: Refer to the
System Administrator’s Guide on dependencies
FNDLOAD / 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct
FND_FORM_CUSTOM_RULES form_name=
FND_FORM_CUSTOM_RULES form_name=
OR
FNDLOAD / 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt
FUNCTION FUNCTION_NAME=
OR
FNDLOAD / 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct
file_name.ldt FORM FORM_NAME=
OR
FNDLOAD / 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct
FND_FORM_CUSTOM_RULES function_name=
16 – User/Responsibilities
FNDLOAD apps/ pwd@seeddb 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_USER
17 – Alert
FNDLOAD apps/pwd 0 Y DOWNLOAD
$ALR_TOP/patch/115/import/alr.lct my_file.ldt ALR_ALERTS
APPLICATION_SHORT_NAME=FND ALERT_NAME=Alert name to downloa
$ALR_TOP/patch/115/import/alr.lct my_file.ldt ALR_ALERTS
APPLICATION_SHORT_NAME=FND ALERT_NAME=Alert name to downloa
18 – Blob
With Release 12.1.1, FNDLOAD supports
BLOB data (upload / download ) to better serve content-rich applications.
FNDLOAD apps/pwd 0 Y mode
configfile datafile entity [ param ... ]
19 – Overwrite custom definitions
FNDLOAD apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/.lct $
XX_TOP/import/.ldt CUSTOM_MODE=FORCE
XX_TOP/import/.ldt CUSTOM_MODE=FORCE
20 – Load an NLS Language
FNDLOAD / 0 Y UPLOAD \
- UPLOAD_MODE=NLS CUSTOM_MODE=FORCE WARNINGS=TRUE
- UPLOAD_MODE=NLS CUSTOM_MODE=FORCE WARNINGS=TRUE
21 – Migrate the role registration process from one
instance to another
a. Please navigate to the path:
$FND_TOP /patch/115/import/US/umxrgsvc.ldt
b. The following command can be used
to download:
FNDLOAD apps/@(instance name) O Y DOWNLOAD
$FND_TOP/patch/115/import/umxrgsvc.lct umxrgsvc.ldt UMX_REG_SERVICES
REG_SERVICE_CODE UMX
c. The following command can be used
to upload:
FNDLOAD apps/@(instance name) O Y UPLOAD
$FND_TOP/patch/115/import/umxrgsvc.lct umxrgsvc.ldt UMX_REG_SERVICES
REG_SERVICE_CODE UMX
22 – Transfer Custom Messages to another Instance
a. Download the message from the
source instance.
FNDLOAD apps/apps 0 Y DOWNLOAD @FND:patch/115/import/afmdmsg.lct
password.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME=FND
MESSAGE_NAME=PASSWORD-INVALID-NO-SPEC-CHAR
b. Move the custom LDT file
(password.ldt) over to the destination instance.
c. Upload the custom message to the
destination instance.
FNDLOAD apps/apps 0 Y UPLOAD @FND:patch/115/import/afmdmsg.lct
password.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME=FND CUSTOM_MODE=FORCE
23 – Download UMX Roles and Role Assignment data from one
instance and upload to another.
To download from one instance:
FNDLOAD 0 Y DOWNLOAD
$FND_TOP/patch/115/import/afrole.lct
umxroles.ldt WF_ROLE ORIG_SYSTEM=UMX%
umxroles.ldt WF_ROLE ORIG_SYSTEM=UMX%
To upload to another instance:
FNDLOAD 0 Y UPLOAD
$FND_TOP/patch/115/import/afrole.lct
umxroles.ldt
umxroles.ldt
References:
· Oracle Applications Systems
Administrator Guide – Configuration
Notes:
1. Give special attention when
downloading Menus or Responsibilities. In the case for several developers
modifying Responsibilities and Menus, then be very careful. Not being careful
will mean that untested Forms, Functions, and Menus will become available in
the clients Production environment besides the tested Forms, Functions, and
Menus.
2. Be very careful when downloading
flexfields that reference value sets with independent values for GL Segment
Codes. By doing so, downloading and extracting all the test data in GL Codes
that might not be applicable for production.
3. There are several variations possible
for FNDLOAD. For example, restricting the download and upload to specific
segments within Descriptive Flexfields.
4. FNDLOAD is very reliable and
stable, if used properly.
5. Please test the FNDLOAD properly,
so as to ensure that no unexpected data occurs.
6. As the name suggests, FNDLOAD is
usedful for FND related objects. However, in any implementation, it’s required
to migrate the Setups in Financials and Oracle HRMS from one environment to
another. Oracle iSetup can be used for this. Some of the things that can be
migrated using Oracle iSetup are GL Set of Books, HR Organization Structures,
HRMS Employees, Profile Options Setup, Suppliers, Customers, Tax Codes &
Tax Rates, Financials Setup, Accounting Calendars, Chart of Accounts, GL
Currencies.
The Generic Loader
(FNDLOAD) is a concurrent program that can transfer Oracle Application entity
data between database and text file.The loader reads a configuration file to
determine which entity to access.
1 – Printer Styles
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt STYLE PRINTER_STYLE_NAME=”printer style name”
2 – Lookups
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME=”FND”
LOOKUP_TYPE=”lookup name”
3 – Descriptive Flexfield with all of specific Contexts
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt DESC_FLEX P_LEVEL=’COL_ALL:REF_ALL:CTX_ONE:SEG_ALL’ APPLICATION_SHORT_NAME=”FND” DESCRIPTIVE_FLEXFIELD_NAME=”desc flex name” P_CONTEXT_CODE=”context name”
Examples:
Note <<274528.1>> – Note How To Download Single Context Using FNDLOAD For Descriptive Flexfield.
Note <<256573.1>> – How To Download/Upload Descriptive Flexfield With Name $SRS$.
4 – Key Flexfield Structures
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt KEY_FLEX P_LEVEL=’COL_ALL:FQL_ALL:SQL_ALL:STR_ONE:WFP_ALL:SHA_ALL:CVR_ALL:SEG_ALL’ APPLICATION_SHORT_NAME=”FND” ID_FLEX_CODE=”key flex code” P_STRUCTURE_CODE=”structure name”
5 – Concurrent Programs
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME=”FND” CONCURRENT_PROGRAM_NAME=”concurrent name”
6 - Value Sets
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME=”value set name”
7 – Value Sets with values
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME=”value set name”
8 – Profile Options
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt PROFILE PROFILE_NAME=”profile option” APPLICATION_SHORT_NAME=”FND”
9 – Request Groups
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt REQUEST_GROUP REQUEST_GROUP_NAME=”request group” APPLICATION_SHORT_NAME=”FND”
10 – Request Sets
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt REQ_SET
APPLICATION_SHORT_NAME=”FND” REQUEST_SET_NAME=”request set”
Examples:
Note <<247126.1>> – How To Download Request Set Definition From One Instance And Upload On Another Instance
11 – Responsibilities
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY RESP_KEY=”responsibility”
12 – Menus
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt MENU MENU_NAME=”menu_name”
1 – Printer Styles
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt STYLE PRINTER_STYLE_NAME=”printer style name”
2 – Lookups
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME=”FND”
LOOKUP_TYPE=”lookup name”
3 – Descriptive Flexfield with all of specific Contexts
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt DESC_FLEX P_LEVEL=’COL_ALL:REF_ALL:CTX_ONE:SEG_ALL’ APPLICATION_SHORT_NAME=”FND” DESCRIPTIVE_FLEXFIELD_NAME=”desc flex name” P_CONTEXT_CODE=”context name”
Examples:
Note <<274528.1>> – Note How To Download Single Context Using FNDLOAD For Descriptive Flexfield.
Note <<256573.1>> – How To Download/Upload Descriptive Flexfield With Name $SRS$.
4 – Key Flexfield Structures
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt KEY_FLEX P_LEVEL=’COL_ALL:FQL_ALL:SQL_ALL:STR_ONE:WFP_ALL:SHA_ALL:CVR_ALL:SEG_ALL’ APPLICATION_SHORT_NAME=”FND” ID_FLEX_CODE=”key flex code” P_STRUCTURE_CODE=”structure name”
5 – Concurrent Programs
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME=”FND” CONCURRENT_PROGRAM_NAME=”concurrent name”
6 - Value Sets
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME=”value set name”
7 – Value Sets with values
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME=”value set name”
8 – Profile Options
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt PROFILE PROFILE_NAME=”profile option” APPLICATION_SHORT_NAME=”FND”
9 – Request Groups
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt REQUEST_GROUP REQUEST_GROUP_NAME=”request group” APPLICATION_SHORT_NAME=”FND”
10 – Request Sets
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt REQ_SET
APPLICATION_SHORT_NAME=”FND” REQUEST_SET_NAME=”request set”
Examples:
Note <<247126.1>> – How To Download Request Set Definition From One Instance And Upload On Another Instance
11 – Responsibilities
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY RESP_KEY=”responsibility”
12 – Menus
FNDLOAD apps/apps O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt MENU MENU_NAME=”menu_name”
No comments:
Post a Comment