XML Publisher FND LOAD

Step 1: Concurrent Program download and upload


FNDLOAD apps/apps 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct /export/home/appldev/XX_GL_TRI_BAL.ldt PROGRAM APPLICATION_SHORT_NAME=XXNPS CONCURRENT_PROGRAM_NAME=XX_GL_TRI_BAL

FNDLOAD apps/apps O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct /export/home/appldev/XX_GL_TRI_BAL.ldt

Step 2: XML Publisher data definition and template download and upload

FNDLOAD apps/apps O Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct XX_GL_TRI_BAL_TEMP_DATA.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=XXNPS DATA_SOURCE_CODE=XX_GL_TRI_BAL TMPL_APP_SHORT_NAME=XXNPS TEMPLATE_CODE=XX_GL_TRI_BAL

FNDLOAD apps/apps O Y UPLOAD $XDO_TOP/patch/115/import/xdotmpl.lct /export/home/appldev/XX_GL_TRI_BAL_TEMP_DATA.ldt

Step3: RTF(OR)Template file upload and download

java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD \
-DB_USERNAME apps \
-DB_PASSWORD apps \
-JDBC_CONNECTION erp-test:1528:UAT \
-LOB_TYPE TEMPLATE \
-APPS_SHORT_NAME XXNPS \
-LOB_CODE XX_GL_TRI_BAL \
-LANGUAGE en \
-TERRITORY US \
-LOG_FILE xdotmpl.log \
-DEBUG true

java oracle.apps.xdo.oa.util.XDOLoader UPLOAD \
-DB_USERNAME apps \
-DB_PASSWORD apps \
-JDBC_CONNECTION erp-dev.:1541:TEST \
-LOB_TYPE TEMPLATE \
-APPS_SHORT_NAME XXNPS \
-LOB_CODE XX_GL_TRI_BAL \
-LANGUAGE en \
-XDO_FILE_TYPE RTF \
-FILE_CONTENT_TYPE text/html  \
-FILE_NAME /export/home/appldev/XX_GL_TRI_BAL.rtf \
-CUSTOM_MODE FORCE

XDOLoader Utility to upload XML Templates

The XDOLoader utility is a Java-based command line program to load template (RTF, PDF, and XSL-FO), XML, and XSD files to the XML Publisher database tables. Before uploading any xml template you need to upload your concurrent program (if any) and data definitions through the FNDLOAD utility.

General Syntax to execute the XDOLoader utility as follows:

% java oracle.apps.xdo.oa.util.XDOLoader UPLOAD \ -DB_USERNAME <db_username> \ -DB_PASSWORD <db_password> \ -JDBC_CONNECTION <jdbc_con_string> \ -LOB_TYPE <lob_type> \ -APPS_SHORT_NAME <application_short_name> \ -LOB_CODE <lob_code> \ -LANGUAGE  \ -TERRITORY  \ -XDO_FILE_TYPE <xdo_file_type> \ -NLS_LANG <NLS_LANG> \ -FILE_CONTENT_TYPE <file_content_type> \ -FILE_NAME <file_name> \ -OWNER  \ -CUSTOM_MODE [FORCE|NOFORCE] -LOG_FILE <log file>

The parameters are described below:

• UPLOAD (Mandatory): The first parameter: UPLOAD will be implemented in the feature.
• DB_USERNAME (Mandatory): Database user name (example: apps).
• DB_PASSWORD (Mandatory): Database user password (example: manager).
• JDBC_CONNECTION (Mandatory): JDBC database connection string
  (example: ap000sun:1234:ebs).
• LOB_TYPE (Mandatory):  XDO LOB type. Valid values are: ‘TEMPLATE’, ‘XML_SCHEMA’ and ‘XML_SAMPLE’
• APPS_SHORT_NAME (Mandatory):  Application short name (example: AR).
• LOB_CODE (Mandatory):  XDO LOB code. Enter either the Template Code or the Data Definition Code.
• LANGUAGE (Optional): ISO two-letter language code (example: en).
• TERRITORY (Optional): ISO two-letter territory code (example: US), default is ’00’.
• XDO_FILE_TYPE (Mandatory):  Enter the XDO file type, valid values are: PDF, RTF, XLS, XSL-FO, XSL-HTML, XSL-XML, XSLTEXT, XSD, XML, RTF-ETEXT
• NLS_LANG (Optional): Enter the NLS_LANG environment variable.
• FILE_CONTENT_TYPE (Optional): Content type of the file (example: text/html, application/pdf)
• FILE_NAME (Mandatory): Name of the file you want to upload. You can give full path name of the file.
• OWNER (Optional): Owner of the template. Default is “ORACLE”.
• CUSTOM_MODE (Optional): Whether to force update. Valid values are FORCE and NOFORCE (default).
• LOG_FILE (Optional): Enter a file name for the output log file (default: xdotmpl.log).

Sample script to run the XDOLoader utility to upload a xml template:

echo  "----------------------------------------------------------------------" echo  "Please enter the following details needed for the XML XDOLoad process" echo  "This details can be found in the TNS entry" echo  "----------------------------------------------------------------------" echo "Enter Apps password  =>" read apps_pw echo "Enter Host TNS Database Server name  =>" read v_host echo "Enter Host Database TNS Port Number =>" read v_port echo "Enter Host Database SID name =>" read v_sid echo "Uploading rtf(XXFIN_SAMPLE_TEMPLATE.rtf) for the XML Template Definition" java oracle.apps.xdo.oa.util.XDOLoader UPLOAD \ -DB_USERNAME apps \ -DB_PASSWORD $apps_pw \ -JDBC_CONNECTION $v_host:$v_port:$v_sid \ -LOB_TYPE TEMPLATE \ -APPS_SHORT_NAME "IBY" \ -LOB_CODE "XXFIN_TEMPLATE_CODE" \ -LANGUAGE en \ -XDO_FILE_TYPE RTF-ETEXT \ -FILE_CONTENT_TYPE 'text/html' \ -FILE_NAME "$XXFIN_TOP/templates/XXFIN_SAMPLE_TEMPLATE.rtf" \ -CUSTOM_MODE FORCE echo  "Finish uploading rtf(XXFIN_SAMPLE_TEMPLATE.rtf) for the XML Template Definit

XML Publisher FND LOAD DOWNLOAD mode syntax

It surprises me how few people are aware of the generic loader (XDOLoader) for XML / BI Publisher (BIP) files.

Like FNDLOAD for AOL / XML Publisher metadata and WFLOAD for Workflow Item Types, XDOLoader is is a command line utility that allows you to migrate the BIP files between environments. The following BIP file types can be upload and downloaded:

- TEMPLATE
- XML_SCHEMA
- XML_SAMPLE
- DATA TEMPLATE

Call XDOLoader in DOWNLOAD mode to create a local copy of the relevant object.
Call XDOLoader in UPLOAD mode to load your local definitions into the database.

Here's the DOWNLOAD syntax and some examples for Oracle E-Business suite users:

DOWNLOAD MODE SYNTAX:
% java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD \
-DB_USERNAME \
-DB_PASSWORD \
-JDBC_CONNECTION \
-LOB_TYPE \
-APPS_SHORT_NAME \
-LOB_CODE \
-LANGUAGE \
-TERRITORY \
-LOG_FILE \
-DEBUG
KEY (for E-Business suite Users):

-DB_USERNAME: apps username for the target instance
-DB_PASSWORD: apps password for the target instance
-JDBC_CONNECTION: JDBC connection string (e.g. server:port:sid)
of the target instance
-LOB_TYPE: The XML Publisher object type.
One of 'TEMPLATE', 'XML_SCHEMA', 'XML_SAMPLE' or 'DATA TEMPLATE'
-APPS_SHORT_NAME: Application short name used to register the XML Publisher object
-LOB_CODE: Template code i.e. concurrent program short name
-LANGUAGE: ISO language code(i.e. en) used when registering the object
-TERRITORY: ISO language code(i.e. GB) used when registering the object
-LOG_FILE: Name of the log file. The default filename is xdotmpl.log
-DEBUG: Run in Debug mode. Valid values are 'true' or 'false'


DOWNLOAD MODE EXAMPLES:

This is the simple shell script that I use to download 'GB English' presentation and data templates.
(Note - Change your language and territory as appropriate):

-----------------------------------------
# Get parameters
apps_psw=$1
jdbc_con=$2
app_short_name=$3
lob_code=$4

# Download XML Publisher Template RTF and XSL
java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD \
-DB_USERNAME apps \
-DB_PASSWORD $apps_psw \
-JDBC_CONNECTION $jdbc_con \
-LOB_TYPE TEMPLATE \
-APPS_SHORT_NAME $app_short_name \
-LOB_CODE $lob_code \
-LANGUAGE en \
-TERRITORY GB \
-LOG_FILE xdotmpl.log \
-DEBUG true

# Download XML Publisher dataTemplate
java oracle.apps.xdo.oa.util.XDOLoader DOWNLOAD \
-DB_USERNAME apps \
-DB_PASSWORD $apps_psw \
-JDBC_CONNECTION $jdbc_con \
-LOB_TYPE DATA_TEMPLATE \
-APPS_SHORT_NAME $app_short_name \
-LOB_CODE $lob_code \
-LANGUAGE en \
-TERRITORY GB \
-LOG_FILE xdotmpl.log \
-DEBUG true
-----------------------------------------

ADDITIONAL NOTES:

1) Don't forget to download your XML Publisher metadata using the FNDLOAD utility. The control file name is xdotmpl.lct.

FNDLOAD Download And Upload Commands For Different AOL Components

FNDLOAD Upload and Download Commands For Different AOL Components

FNDLOAD Command To Downlod Printer Styles
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct xxaoa_file_name.ldt STYLE PRINTER_STYLE_NAME="printer style name"

FNDLOAD Command To Downlod Lookups

FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct xxaoa_file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME="prod" LOOKUP_TYPE="lookup name"

FNDLOAD Command To Downlod Descriptive Flexfield with all of specific Contexts
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct xxaoa_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"



FNDLOAD Command To Downlod 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 <username>/<password> O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct xxaoa_file_name.ldt DESC_FLEX DESCRIPTIVE_FLEXFIELD_NAME="PER_%"

FNDLOAD Command To Downlod Key Flexfield Structures:
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct xxaoa_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"

FNDLOAD Command To Downlod Concurrent Programs:
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct xxaoa_file_name.ldt PROGRAM APPLICATION_SHORT_NAME="prod" CONCURRENT_PROGRAM_NAME="concurrent name"

FNDLOAD Command To Downlod Value Sets:
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct xxaoa_file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME="value set name"

FNDLOAD Command To Downlod Value Sets with values:
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct xxaoa_file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME="value set name"

FNDLOAD Command To Downlod Profile Options:
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct xxaoa_file_name.ldt PROFILE PROxxaoa_file_name="profile option" APPLICATION_SHORT_NAME="prod"


FNDLOAD Command To Downlod Request Group:

FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct xxaoa_file_name.ldt REQUEST_GROUP REQUEST_GROUP_NAME="request group"APPLICATION_SHORT_NAME="prod"

FNDLOAD Command To Downlod Request Sets:
- DOWNLOAD -- Request set Def   --

FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct <xxaoa_filename.ldt> REQ_SET REQUEST_SET_NAME=<request set name>

DOWNLOAD     -- Request set link   --
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct <xxaoa_filename.ldt> REQ_SET_LINKS REQUEST_SET_NAME=<request set link name>

FNDLOAD Command To Downlod Responsibilities

FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct xxaoa_file_name.ldt FND_RESPONSIBILITY RESP_KEY="responsibility"

FNDLOAD Command To Downlod Responsibilities with all Security Groups:
FNDLOAD <username>/<PASSWORD> 0 Y DOWNLOAD FND_TOP/patch/115/import/afscursp.lct <USER>.ldt FND_USER USER_NAME="<USER>" SECURITY_GROUP=% DATA_GROUP_NAME=%


Notes for using FNDLOAD against FND_USER:-

1. After uploading using FNDLOAD, user will be promoted to change their password again during their next signon attempt.
2. All the responsibilities will be extracted by FNDLOAD alongwith User Definition in FND_USER
3. In the Target Environment, make sure that you have done FNDLOAD for new responsibilities prior to running FNDLOAD on users.

FNDLOAD Command To Downlod Menus:
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct xxaoa_file_name.ldt MENU MENU_NAME="menu_name"

FNDLOAD Command To Downlod Forms/Functions/Personalizations:
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct <xxaoa_file_name.ldt> FND_FORM_CUSTOM_RULES form_name=<form name>
OR
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct xxaoa_file_name.ldt FUNCTION FUNCTION_NAME=<function_name>
OR
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct xxaoa_file_name.ldt FORM FORM_NAME=<form_name>
OR
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct <xxaoa_file_name.ldt> FND_FORM_CUSTOM_RULES function_name=<function name>

FNDLOAD Command To Downlod User/Responsibilities:
FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct xxaoa_file_name.ldt FND_USER

FNDLOAD User Record

Download

FNDLOAD apps/password 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct your_output_dir/your_name.ldt FND_USER USER_NAME="USERNAME_TO_PROCESS"

FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct xxaoa_file_name.ldt FND_USER USER_NAME="USERNAME_TO_PROCESS"

FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct XX_FND_USER_ELO.ldt FND_USER USER_NAME='ELANGO'

FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct ./XX_FND_USER_ELO.ldt FND_USER USER_NAME='ELANGO'

FNDLOAD username/password@database 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct XXUSERNAME.ldt FND_USER USER_NAME=’XXUSERNAME’

Upload

FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct ./XX_FND_USER_ELO.ldt

FNDLOAD apps/password 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct your_output_dir/your_name.ldt

FNDLOAD Command To Downlod Alert:
FNDLOAD <username>/<password> 0 Y DOWNLOAD $ALR_TOP/patch/115/import/alr.lct my_file.ldt ALR_ALERTS APPLICATION_SHORT_NAME=FND ALERT_NAME=Alert name to download

FNDLOAD Command To Downlod Blob:
FNDLOAD <username>/<password> 0 Y mode configfile datafile entity [ param ... ]

FNDLOAD Command To Downlod Overwrite custom definitions:
FNDLOAD <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/.lct $XX_TOP/import/.ldt CUSTOM_MODE=FORCE


How To Transfer Custom Messages to another Instance:
a. Download the message from the source instance.
FNDLOAD <username>/<password> 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 <username>/<password> 0 Y UPLOAD @FND:patch/115/import/afmdmsg.lct password.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME=FND CUSTOM_MODE=FORCE

XML DATA DEFINITION:
FNDLOAD <username>/<password> O Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct <xxaoa_filename.ldt> XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=<application shortname>DATA_SOURCE_CODE=<data source code > TMPL_APP_SHORT_NAME=<template application short name>TEMPLATE_CODE=<template code>
The Above command downloads all the templates defined for this Particular Data Definition. For a particular template to be downloadeduse

FNDLOAD <username>/<password> 0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct <xxaoa_filename.ldt> XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=<application shortname>DATA_SOURCE_CODE=<datadefshortcode> TMPL_APP_SHORT_NAME==<template application short  name> TEMPLATE_CODE= <templatecode>

How TO Migrate Work Flows From One Instance to other:
WFLOAD <username>/<password> 0 Y DOWNLOAD <xxaoa_filepath.wft> <item type>

Execute Following Command to upload the workflow to target instance:

WFLOAD <username>/<password> 0 Y UPLOAD <xxaoa_filepath.wft>

UPLOAD UPLOAD COMMANDS For Different AOL Components:

Note: UPLOAD command is same for all except replacing the .lct and passing any extra parameters if you want to pass

FNDLOAD Command To upload Ldt file for a Concurent Program
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a Data Definition
FNDLOAD <username>/<password> O Y UPLOAD $XDO_TOP/patch/115/import/xdotmpl.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a Request Set
FNDLOAD <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a Request Set Links
FNDLOAD <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a Lookup Up
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a request group for a Concurrent Program
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a request group for a Request Set
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a Value Set
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a Value Set with values
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a DFF
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a DFF for a particular attribute column
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a profile Option
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt

FNDLOAD Command To upload Ldt file for a Audit Group
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/affaudit.lct file_name.ldt

FNDLOAD Command  To upload Ldt file for a Audit Schema
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/affaudit.lct file_name.ldt

FNDLOAD Command  To upload Ldt file for a Responsibility
FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt


FNDLOAD Command  To upload Ldt file for a XML Data Definition
UPLOAD
FNDLOAD <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct <xxaoa_filename.ldt>
FNDLOAD <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct <xxaoa_filename.ldt>

FNDLOAD <username>/<password> O Y DOWNLOAD  $XDO_TOP/patch/115/import/xdotmpl.lct <xxaoa_filename.ldt> XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=<application short name>DATA_SOURCE_CODE=<data source code > TMPL_APP_SHORT_NAME=<template application short  name>TEMPLATE_CODE=<template code>

FNDLOAD apps/apps O Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct /export/home/appldev/XDO_XXNPS_GL_VRNC.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=SQLGL DATA_SOURCE_CODE=XXNPS_GL_VRNC TMPL_APP_SHORT_NAME=SQLGL TEMPLATE_CODE=XXNPS_GL_VRNC

FNDLOAD <username>/<password> O Y UPLOAD $XDO_TOP/patch/115/import/xdotmpl.lct <xxaoa_filename.ldt>

The Above command downloads all the templates defined for this Particular Data Definition. For a particular template to be downloaded use

FNDLOAD <username>/<password> O Y UPLOAD $XDO_TOP/patch/115/import/xdotmpl.lct <xxaoa_filename.ldt>

FNDLOAD Command to upload ALERTS
FNDLOAD <username>/<password> 0 Y UPLOAD $ALR_TOP/patch/115/import/alr.lct  <ldt filename>


FNDLOAD Command TO Upload an NLS Language:
FNDLOAD <username>/<password> 0 Y UPLOAD <controlfile.lct> <datafile.ldt> \
- UPLOAD_MODE=NLS CUSTOM_MODE=FORCE WARNINGS=TRUE

FNDLOAD Concept for Oracle Apps

What is 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 AOL data Migration takes place necessary to synchronize the data across databases instance during

• Installations (New desc. flex field creations etc)
• Upgrades (Apps upgrade etc)
• Maintenance (Value set changes etc)

Then… What.. FNDLOAD

Yes, that is one and only oracle solution. It can be defined as a concurrent program that can move Oracle Applications data between database and text file representations. Or this can be defined as FNDLOAD can download data from an application entity into an editable text file, which can be uploaded to another database.

How it works

Conversion between database format and text file format is specified by a configuration file. Oracle does provide confirmation file and it is important to just pass the configuration file name and then just call the loader and leave everything .The schematic visual representation of the loader is like:

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
• Attachments
• Messages
• Value Sets and Values
• Lookup Types
• User Responsibilities
• Printer Definitions
• FND Dictionary
• Help Configuration
• Document Sequences
• Concurrent Manager Schedules

Then…what are advantages when using FNDLOAD are : 

1. 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/dba’s
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!!

And these are some Disadvantages also : 

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

The Syntax

To use FNDLOAD, the following syntax is needed.

FNDLOAD apps/appspwd 0 Y mode configfile datafile entity [parameter1…..]

As you can see, some info is needed.- First you will need to know the Apps password.

• The mode is either DOWNLOAD or UPLOAD.
• The configfile is the file that Fndload needs to download on upload data.
• T he data file is the output file, in which the downloaded data is written
• The entity is the entity you want to download,
• Parameters van is passed to download a certain Alert

Modes of Operation

This is important because it would drive the whole flow, and it always be two mode .. Upload and Download…

Example of download:

FNDLOADapps/pwd 0 Y DOWNLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt \ PROGRAM CONCURRENT_PROGRAM_NAME= concurrent_program_short_name> APPLICATION_SHORT_NAME=<application_short_name>

Example of Upload

FNDLOAD apps/pwd 0 Y UPLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt - CUSTOM_MODE=FORCE undocumented parameter

WHAT IS FNDLOADLoad Options:

• Application level OR single entity level download
  • (Example) Download all the profile options of Inventory or just the INV: Default Primary UOM
• Entire OR Partial upload of a data file
  • (Example) Upload the entire myfile.ldt or just a single enity indicated by - and mode UPLOAD or UPLOAD_PARTIAL
  • Entity name required for UPLOAD_PARTIAL mode
• Custom mode force update
  • To override Oracle's upload algorithm and update the custom AOL data regardless, use CUSTOM_MODE= FORCE
  • UPLOAD_MODE= REPLACE (only for menus)
• Support for NLS uploads
  • NLS data uploads for translated columns are supported, use UPLOAD_MODE= NLS

Then ..Where is Config File Located

By default Oracle delivers most of configuration files you can use to download certain entities.

• Configuration files with extension .lct
  • On Unix - all the configuration files are in $FND_TOP/patch/115/import directory
  • On Unix – Oracle also places the original configuration files in $FND_TOP/admin/import directory
• Data files with extension .ldt

and..FNDLOAD File Structures is

• The config 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

Take a note FNDLOAD File Structures

• The data files (.ldt) have both entity definition and the data
• It also shows the version and the location of the config file (.lct) that was used
• Without the config file, data file is useless
• Without the data file, config file is meaningless

..Remember regarding FNDLOAD Files

• Key files: .lct and .ldt
• You must run the FNDLOADas apps user not as applsys or any other, otherwise you will receive Ora-6550
• Both are easily readable, editable and portable
• DO NOT MODIFY Oracle’s .lct files
• Use your favorite editor (I would suggest Textpad or Editplus) 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 faster (Why can’t I access that? 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)  1 - Printer Styles

• FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt STYLE PRINTER_STYLE_NAME="printer style name"

   - Lookups

  FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME="prod" LOOKUP_TYPE="lookup name"

   - Descriptive Flexfield with all of specific Contexts

  FNDLOAD apps/apps@seed115 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="prod" DESCRIPTIVE_FLEXFIELD_NAME="desc flex name" P_CONTEXT_CODE="context name"

  
  
   - Concurrent Programs

  FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME="prod" CONCURRENT_PROGRAM_NAME="concurrent name"

   - Value Sets

  FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME="value set name"

   - Value Sets with values

  FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME="value set name"

   - Profile Options

  FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt PROFILE PROFILE_NAME="profile option" APPLICATION_SHORT_NAME="prod"

   - Requset Group

  FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt REQUEST_GROUP REQUEST_GROUP_NAME="request group" APPLICATION_SHORT_NAME="prod"

  - Request Sets

  FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt REQ_SET APPLICATION_SHORT_NAME="prod" REQUEST_SET_NAME="request set"

   - Responsibilities

  FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY RESP_KEY="responsibility

   - Menus

  FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt MENU MENU_NAME="menu_name"

   â€“ Forms/Functions

  FNDLOAD apps/apps@seed115 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt FND_FORM_CUSTOM_RULES The Upload syntax for all styles: FNDLOAD apps/apps@seed115 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt

   User/Responsibilities

  FNDLOAD apps/apps@seed115 0 Y DOWNLOAD @FND:patch/115/import/afscursp.lct file_name.ldt FND_USER Then UPLOAD FNDLOAD apps/apps@seed115 0 Y UPLOAD [UPLOAD_PARTIAL] @FND:patch/115/import/afscursp.lct file_name.ldt FND_USER [<USER>]

   
  
  

Moving Form Personalizations Between Instances

Once you create and test personalizations in your test instance, you can move them to production instances. Personalizations can be extracted by the loader on a per-function basis or per-form basis (that is, each loader file will contain all of the personalizations for a single function or form, respectively). Note that upon uploading, all prior personalizations for that function are first deleted, and then the contents of the loader file are inserted.
The loader syntax is as follows:

To download rules for a particular function:
FNDLOAD / 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct FND_FORM_CUSTOM_RULES function_name=
Note: this style is not recommended, as the personalizations that affect a particular function can now be a mix of function- and form-level rules.
To download rules for a particular form:
FNDLOAD/ 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lctFND_FORM_CUSTOM_RULES form_name=

To download all personalizations (all forms and functions):
FNDLOAD / 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct FND_FORM_CUSTOM_RULES
Upload:
FNDLOAD / 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct

R12 - How to migrate AME setups using FNDLOAD

Oracle Approvals Management (AME) is a self-service Web application that enables users to define business rules governing the process for approving transactions in Oracle Applications .This enables development of custom rules to manage transaction approvals that is integrated with multiple Oracle EBS applications such as HR, PO, AP and UMX.

If you want to migrate the AME setup like rules,conditions,approval groups etc. from one instance to another instance, you can use some of them by mean of FNDLOAD utility. The process is similar to what we are regularly using for other AOL Objects.

FNDLOAD will have such ldt file through which you can use.

Here are the details steps for each setup's.

1. Condition:

The script that downloads AME conditions allows you to download all conditions for a given transaction type or only those associated with a particular attribute or group of attributes.

Download
FND_TOP apps/<apps password> 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesconk.lct <ldt filename> AME_CONDITIONS CONDITION_KEY=<condition key> TRANSACTION_TYPE_ID=<trans typs id> APPLICATION_SHORT_NAME=<application short name>

Upload
FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesconk.lct <ldt filename>

Example:
FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesconk.lct amecondition.ldt AME_CONDITIONS APPLICATION_SHORT_NAME='PER' TRANSACTION_TYPE_ID='HRSSA' ATTRIBUTE_NAME='PROCESS_NAME' CONDITION_KEY='317772662:44552';
FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesconk.lct amecondition.ldt

2. Dynamic Approval group /Approve Groups:

An approver group can either be an ordered set of one or more approvers (persons and/or user accounts) or it can be a list, which is dynamically generated at rule evaluation time.

Download
FND_TOP apps/<apps password> 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesappg.lct <ldt filename> AME_APPROVAL_GROUPS APPROVAL_GROUP_NAME=<name of approval group> TRANSACTION_TYPE_ID=<trans typs id> APPLICATION_SHORT_NAME=<application short name>

Upload
FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesappg.lct <ldt filename>

Example:
FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesappg.lct ameapprovalgroup.ldt AME_APPROVAL_GROUPS APPROVAL_GROUP_NAME='Dyn Apprv Hub Approval Group' TRANSACTION_TYPE_ID='HRSSA' APPLICATION_SHORT_NAME='PER'
FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesappg.lct ameapprovalgroup.ldt

3. Dynamic Approval group config:

Download
FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesaagc.lct ameapprovalgroupusage.ldt AME_APPROVAL_GROUP_CONFIG APPROVAL_GROUP_NAME='Dyn. Post HROPs Approval Group' TRANSACTION_TYPE_ID='HRSSA' APPLICATION_SHORT_NAME='PER'

Upload
FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesaagc.lct ameapprovalgroupusage.ldt

4. AME Rule:

An approval rule is a business rule that helps determine a transactions approval process. Rules are constructed from conditions and actions.

The AME rules can be downloaded for information about the rule (e.g. name, description, etc) along with associated conditions and rule type.

Download
$FND_TOP/bin/FNDLOAD apps/<apps password> 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesrulk.lct <ldt filename> AME_RULES RULE_KEY=<Rule Key > TRANSACTION_TYPE_ID=<trans typs id> APPLICATION_SHORT_NAME=<application short name>

#You can find Rule Key in AME_RULES table
Upload
FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesrulk.lct amerule.ldt

Example:
FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesrulk.lct amerule.ldt AME_RULES RULE_KEY='317772662:54567' TRANSACTION_TYPE_ID='HRSSA' APPLICATION_SHORT_NAME='PER'
FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesrulk.lct amerule.ldt

5. AME Rule Action Type Usage:

Download
FNDLOAD apps/<apps pw> 0 Y DOWNLOAD amesactu.lct <download file name>.ldt AME_ACTION_USAGES APPLICATION_SHORT_NAME=<FND application short name> TRANSACTION_TYPE_ID=<AME transaction type short name> [RULE_KEY=<Rule Key>]

# Rule Key is found in AME_RULES table
Upload
FNDLOAD apps/apps 0 Y UPLOAD amesactu.lct usage<download file name>.ldt

Ex:
FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesactu.lct ameactionusage.ldt AME_ACTION_USAGES RULE_KEY='317772662:54567' TRANSACTION_TYPE_ID='HRSSA' APPLICATION_SHORT_NAME='PER'
FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesactu.lct ameactionusage.ldt

6. Transaction Types

An application that uses AME to govern its transactions’ approval processes is termed an integrating application. An integrating application may divide its transactions into several categories where each category requires a distinct set of approval rules. Each set of rules is called a transaction type. Different transaction types can use the same attribute name to represent values that are calculated in different ways or fetched from different places.

Download
FNDLOAD apps/<apps pwd> 0 Y DOWNLOAD amescvar.lct <download file name>.ldt AME_CALLING_APPS APPLICATION_SHORT_NAME=<FND application short name> TRANSACTION_TYPE_ID=<AME transaction type short name>

Upload
FNDLOAD apps/<apps pwd> 0 Y UPLOAD amescvar.lct <download file name>.ldt

Eg:
FNDLOAD apps/apps 0 Y DOWNLOAD amescvar.lct hubtrantype.ldt AME_CALLING_APPS APPLICATION_SHORT_NAME=SQLAP TRANSACTION_TYPE_ID=SBTRANSTYPE
FNDLOAD apps/apps 0 Y UPLOAD amescvar.lct hubtrantype.ldt

7. Attribute

Attributes are business variables with a single value for a particular transaction. 
Download

FNDLOAD apps/<apps password> 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesmatt.lct <ldt filename> AME_ATTRIBUTES ATTRIBUTE_NAME=<attribute name> TRANSACTION_TYPE_ID=<trans typs id> APPLICATION_SHORT_NAME=<application short name>

Upload
FNDLOAD apps/<apps pwd> 0 Y UPLOAD amesmatt.lct <ldt download file name>

Example:
FNDLOAD apps/apps 0 Y DOWNLOAD amesmatt.lct hubattributes.ldt AME_ATTRIBUTES APPLICATION_SHORT_NAME=SQLAP
TRANSACTION_TYPE_ID= SBTRANSTYPE ATTRIBUTE_NAME=SB_CUST_ATTRIBUTE
FNDLOAD apps/apps 0 Y UPLOAD amesmatr.lct hubattributeusages.ldt

8. Attribute Usage

Download
FNDLOAD apps/<apps password> 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesmatr.lct <ldt filename> AME_ATTRIBUTE_USAGES ATTRIBUTE_NAME=<attribute name> TRANSACTION_TYPE_ID=<trans typs id> APPLICATION_SHORT_NAME=<application short name>

Upload 
FNDLOAD apps/<apps pwd> 0 Y UPLOAD amesmatr.lct <download file name>.ldt

Example:
FNDLOAD apps/apps 0 Y DOWNLOAD amesmatr.lct hubattributeusage.ldt AME_ATTRIBUTE_USAGES aPPLICATION_SHORT_NAME=SQLAP
FNDLOAD apps/apps 0 Y UPLOAD amesmatr.lct hubattributeusages.ldt

FNDLOAD for AME’s

Oracle Approvals Management (AME) is a self-service Web application that enables users to define business rules governing the process for approving transactions in Oracle Applications .This enables development of custom rules to manage transaction approvals that is integrated with multiple Oracle EBS applications such as HR, PO, AP and UMX.
If you want to migrate the AME setup like rules,conditions,approval groups etc. from one instance to another instance, you can use some of them by mean of FNDLOAD utility. The process is similar to what we are regularly using for other AOL Objects.

FNDLOAD will have such ldt file through which you can use.



You should read the lct first before using any FNDLOAD Command. In the lct, there is an Entity section, where the Entity details are mentioned.Newcomer in OracleApps if you are not familiar with lcts, i would suggest you to go through the DOWNLOAD section and find the bind variables, which are mandatory.
Here are the details steps for each setup's availability till date.

Condition

The script that downloads AME conditions allows you to download all conditions for a given transaction type or only those associated with a particular attribute or group of attributes.

 Download

  FND_TOP apps/<apps password> 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesconk.lct <ldt filename> AME_CONDITIONS CONDITION_KEY=<condition key> TRANSACTION_TYPE_ID=<trans typs id> APPLICATION_SHORT_NAME=<application short name>

 UPLOAD

FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesconk.lct <ldt filename>

• FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesconk.lct amecondition.ldt AME_CONDITIONS APPLICATION_SHORT_NAME='PER' TRANSACTION_TYPE_ID='HRSSA' ATTRIBUTE_NAME='PROCESS_NAME' CONDITION_KEY='317772662:44552';
• FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesconk.lct amecondition.ldt

Dynamic Approval group /Approver Groups

An approver group can either be an ordered set of one or more approvers (persons and/or user accounts) or it can be a list, which is dynamically generated at rule evaluation time.


FND_TOP apps/<apps password> 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesappg.lct <ldt filename> AME_APPROVAL_GROUPS APPROVAL_GROUP_NAME=<name of approval group> TRANSACTION_TYPE_ID=<trans typs id> APPLICATION_SHORT_NAME=<application short name>


FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesappg.lct <ldt filename>

• FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesappg.lct ameapprovalgroup.ldt AME_APPROVAL_GROUPS APPROVAL_GROUP_NAME='Dyn Apprv Hub Approval Group' TRANSACTION_TYPE_ID='HRSSA' APPLICATION_SHORT_NAME='PER'
• FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesappg.lct ameapprovalgroup.ldt

Dynamic Approval group config

FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesaagc.lct ameapprovalgroupusage.ldt AME_APPROVAL_GROUP_CONFIG APPROVAL_GROUP_NAME='Dyn. Post HROPs Approval Group' TRANSACTION_TYPE_ID='HRSSA' APPLICATION_SHORT_NAME='PER'


FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesaagc.lct ameapprovalgroupusage.ldt

AME Rule

An approval rule is a business rule that helps determine a transaction’s approval process. Rules are constructed from conditions and actions.
The AME rules can be downloaded for information about the rule (e.g. name, description, etc) along with associated conditions and rule type.

$FND_TOP/bin/FNDLOAD apps/<apps password> 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesrulk.lct <ldt filename> AME_RULES RULE_KEY=<Rule Key > TRANSACTION_TYPE_ID=<trans typs id> APPLICATION_SHORT_NAME=<application short name>
# You can find Rule Key in AME_RULES table

FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesrulk.lct amerule.ldt

• FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesrulk.lct amerule.ldt AME_RULES RULE_KEY='317772662:54567' TRANSACTION_TYPE_ID='HRSSA' APPLICATION_SHORT_NAME='PER'
• FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesrulk.lct amerule.ldt

AME Rule Action Type Usage

FNDLOAD apps/<apps pw> 0 Y DOWNLOAD amesactu.lct <download file name>.ldt AME_ACTION_USAGES APPLICATION_SHORT_NAME=<FND application short name> TRANSACTION_TYPE_ID=<AME transaction type short name> [RULE_KEY=<Rule Key>]
# Rule Key is found in AME_RULES table


FNDLOAD apps/apps 0 Y UPLOAD amesactu.lct <download file name>.ldt

• FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesactu.lct ameactionusage.ldt AME_ACTION_USAGES RULE_KEY='317772662:54567' TRANSACTION_TYPE_ID='HRSSA' APPLICATION_SHORT_NAME='PER'
• FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesactu.lct ameactionusage.ldt
  

Transaction Types

An application that uses AME to govern its transactions’ approval processes is termed an integrating application. An integrating application may divide its transactions into several categories where each category requires a distinct set of approval rules. Each set of rules is called a transaction type. Different transaction types can use the same attribute name to represent values that are calculated in different ways or fetched from different places.

FNDLOAD apps/<apps pwd> 0 Y DOWNLOAD amescvar.lct <download file name>.ldt AME_CALLING_APPS APPLICATION_SHORT_NAME=<FND application short name> TRANSACTION_TYPE_ID=<AME transaction type short name>

FNDLOAD apps/<apps pwd> 0 Y UPLOAD amescvar.lct <download file name>.ldt

• FNDLOAD apps/apps 0 Y DOWNLOAD amescvar.lct hubtrantype.ldt AME_CALLING_APPS APPLICATION_SHORT_NAME=SQLAP TRANSACTION_TYPE_ID=SBTRANSTYPE
• FNDLOAD apps/apps 0 Y UPLOAD amescvar.lct hubtrantype.ldt

Attribute
Attributes are business variables with a single value for a particular transaction. The typical example for attributes in AME are:

• transaction’s total amount
• percentage of discount
• an item’s category
• a person’s salary

FNDLOAD apps/<apps password> 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesmatt.lct <ldt filename> AME_ATTRIBUTES ATTRIBUTE_NAME=<attribute name> TRANSACTION_TYPE_ID=<trans typs id> APPLICATION_SHORT_NAME=<application short name>


FNDLOAD apps/<apps pwd> 0 Y UPLOAD amesmatt.lct <ldt download file name>

• FNDLOAD apps/apps 0 Y DOWNLOAD amesmatt.lct hubattributes.ldt AME_ATTRIBUTES APPLICATION_SHORT_NAME=SQLAP
  TRANSACTION_TYPE_ID= SBTRANSTYPE ATTRIBUTE_NAME=SB_CUST_ATTRIBUTE
• FNDLOAD apps/apps 0 Y UPLOAD amesmatr.lct hubattributeusages.ldt

Attribute Usage

FNDLOAD apps/<apps password> 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesmatr.lct <ldt filename> AME_ATTRIBUTE_USAGES ATTRIBUTE_NAME=<attribute name> TRANSACTION_TYPE_ID=<trans typs id> APPLICATION_SHORT_NAME=<application short name>


FNDLOAD apps/<apps pwd> 0 Y UPLOAD amesmatr.lct <download file name>.ldt

• FNDLOAD apps/apps 0 Y DOWNLOAD amesmatr.lct hubattributeusage.ldt AME_ATTRIBUTE_USAGES aPPLICATION_SHORT_NAME=SQLAP
• FNDLOAD apps/apps 0 Y UPLOAD amesmatr.lct hubattributeusages.ldt
  
  ==============  *********************  ====================
  
  FNDLOAD Migration scripts for AME  Attribute, Condition, Approval Groups, Rules and Transaction Types.
  
  A. Attribute
  
  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
  
  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
  
  1. Attributes – Upload
  
  FNDLOAD apps/pw1 0 Y UPLOAD $PER_TOP/patch/115/import/amesmatt.lct xx_gssm_ame_attr.ldt
  
  2. Attribute Usages – Upload
  
  FNDLOAD apps/pw1 0 Y UPLOAD $PER_TOP/patch/115/import/amesmatr.lct xx_gssm_ame_attr_usg.ldt
  
  B. 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
  
  1. Conditions – Upload
  FNDLOAD apps/pw1 0 Y UPLOAD $PER_TOP/patch/115/import/amesconk.lct xx_gssm_ame_cond.ldt
  
  C. 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
  
  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
  
  
  1. 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 – Upload
  
  FNDLOAD apps/pw1 0 Y UPLOAD $PER_TOP/patch/115/import/amesaagc.lct xx_gssm_ame_apgrps_cf.ldt
  
  4. Rules
  
  # You can find Rule Key in AME_RULES table
  
  1. Rules
  
  * FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesrulk.lct amerule.ldt AME_RULES RULE_KEY=’317772662:54567′ TRANSACTION_TYPE_ID=’HRSSA’ APPLICATION_SHORT_NAME=’PER’
  
  
  * FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesrulk.lct amerule.ldt
  
  * FNDLOAD apps/<passwd>@sourcedb 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesactu.lct ameactionusage.ldt AME_ACTION_USAGES RULE_KEY=’317772662:54567′ TRANSACTION_TYPE_ID=’HRSSA’ APPLICATION_SHORT_NAME=’PER’
  
  * FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesactu.lct ameactionusage.ldt
  
  5. Transaction Type
  
  An application that uses AME to govern its transactions approval processes is termed an integrating application. An integrating application may divide its transactions into several categories where each category requires a distinct set of approval rules. Each set of rules is called a transaction type. Different transaction types can use the same attribute name to represent values that are calculated in different ways or fetched from different places.
  
  * FNDLOAD apps/apps 0 Y DOWNLOAD amescvar.lct hubtrantype.ldt AME_CALLING_APPS APPLICATION_SHORT_NAME=SQLAP TRANSACTION_TYPE_ID=SBTRANSTYPE
  
  * FNDLOAD apps/apps 0 Y UPLOAD amescvar.lct hubtrantype.ldt