AME Migration

We can Acheive AME migration through FNDLOADS.
AME migration typically involves migrating the following:
1. AME conditions
2. AME Approver Groups
3. AME Rules

AME Conditions:
------------------
The scripts used to Download LDT file which downloads the attributes associated with it: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>
The Script used to UPLOAD:
FNDLOAD apps/<passwd>@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesconk.lct <ldt filename>

Example:
FNDLOAD apps/apps 0 Y DOWNLOAD $AME_TOP/patch/115/import/amesconk.lct Cond_Name.ldt AME_CONDITIONS APPLICATION_SHORT_NAME='PER' TRANSACTION_TYPE_ID='SSHRMS' CONDITION_KEY='1091217454:10111'

AME Approver Groups:
----------------------------
There are two scripts that are required to be executed to migrate custom approver groups. One script downloads the structure of the approver group including the SQL query used to select members for any dynamic queries. The other script downloads data regarding the order number and voting regime of the approver group. There are several notes of interest regarding downloading of approver groups.

§  The download script only works for dynamic approver groups. It does not work for static approver groups.

§  The script does not readily recognize approver group names containing spaces. If the approver group(s) contains spaces, add the % wildcard symbol in between each word of the approver group to ensure it is downloaded properly

§  The primary approver group script does not allow for downloading all approver groups for a given transaction type. You must supply the name of an approver group or some matching pattern of multiple groups if the naming convention of the groups is similar.

§  To add to the previous point, it is recommended that in order to be able to download multiple approver groups at one time (instead of having to create multiple download files), use a common prefix when naming the approver group. For example, use <application short name>_cust as the prefix for approver group such as AP cust (name of the approver group).

§  The approver group configuration script does allow all approver group configuration for a given transaction type to be downloaded at one time.

Script to Download Approver Groups:
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>

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

Example:
FNDLOAD apps/apps 0 Y DOWNLOAD $AME_TOP/patch/115/import/amesappg.lct 'app_name'.ldt AME_APPROVAL_GROUPS APPLICATION_SHORT_NAME='PER' TRANSACTION_TYPE_ID='SSHRMS' APPROVAL_GROUP_NAME='approver_group_name' 

Script to Download Approver Group Configuration: 
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'

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

AME Rules:
--------------

The download of AME rules requires two scripts to be executed. The first script downloads information about the rule (e.g. name, description, etc) along with associated conditions and rule type. The second script downloads all associated actions for the rule. Both scripts allow all rules for a given transaction type to be downloaded. You can also download a specific rule. However, unlike some of the previous components, you cannot download a group of rules using a string wildcards. The reason for this is that the FNDLOAD scripts use the Oracle generated rule key as a parameter to download a specific rule. It is recommended to download all rules for a transaction type unless only a handful of new rules have been created and need to be migrated.

Script to 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>

Script to Upload:

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

Example:

FNDLOAD apps/apps 0 Y DOWNLOAD $AME_TOP/patch/115/import/amesrulk.lct 'Rule_Name'.ldt AME_RULES RULE_KEY='1091217454:10082' TRANSACTION_TYPE_ID='SSHRMS'  APPLICATION_SHORT_NAME='PER'

Note: Rule key can be found from AME_RULES table.

Script to Download Rule Action Types 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>]

Script to Upload:

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

Note: Static Approver groups cannot be migrated they need to be created manually. So we need to add to the Rules manually.