Wednesday, December 23, 2015

How to Migrate AME Setup using FNDLOAD



Step 1: Create Attribute
select * from ame_attributes where name= 'TESTING WITH FNDLOAD'

--> Download
FNDLOAD apps/<EnterAppsPassword> 0 Y DOWNLOAD $AME_TOP/patch/115/import/amesmatt.lct attr2.ldt AME_ATTRIBUTES ATTRIBUTE_NAME="TESTING WITH FNDLOAD" TRANSACTION_TYPE_ID="SSHRMS"
APPLICATION_SHORT_NAME="PER"

--> Upload
FNDLOAD apps/<EnterAppsPassword> 0 Y UPLOAD $AME_TOP/patch/115/import/amesmatt.lct attr2.ldt


Step 2: Create Attribute Usages
select * from ame_attribute_usages where attribute_id = (select attribute_id from ame_attributes where name= 'TESTING WITH FNDLOAD')

--> Download
FNDLOAD apps/<EnterAppsPassword> 0 Y DOWNLOAD $AME_TOP/patch/115/import/amesmatr.lct attr2usg.ldt AME_ATTRIBUTE_USAGES ATTRIBUTE_NAME="TESTING WITH FNDLOAD" TRANSACTION_TYPE_ID="SSHRMS"
APPLICATION_SHORT_NAME="PER"

--> Upload
FNDLOAD apps/<EnterAppsPassword> 0 Y UPLOAD $AME_TOP/patch/115/import/amesmatr.lct attr2usg.ldt



Step 3: Create Attribute Conditions
select * from ame_conditions where attribute_id =  (select attribute_id from ame_attributes where name= 'TESTING WITH FNDLOAD')

-->  Download
FNDLOAD apps/<EnterAppsPassword> 0 Y DOWNLOAD $AME_TOP/patch/115/import/amesconk.lct attr2cond.ldt AME_CONDITIONS TRANSACTION_TYPE_ID="SSHRMS" APPLICATION_SHORT_NAME="PER" ATTRIBUTE_NAME="TESTING WITH FNDLOAD"

CONDITION_KEY = “339364792:16388”  -> Can be used instead of ATTRIBUTE_NAME if specific conditions needs to be moved

-->  Upload 

FNDLOAD apps/<EnterAppsPassword> 0 Y UPLOAD $AME_TOP/patch/115/import/amesconk.lct attr2cond.ldt

Step 4: Create Approver Group (Dynamic Only)
Note: FNDLOAD cannot move Static Approver Groups due to its limitations, one can move the same using API's
 
SELECT *
  FROM ame_approval_groups
 WHERE name = 'Test to Move using FNDLOAD2'

-->  Download
FNDLOAD apps/<EnterAppsPassword> 0 Y DOWNLOAD $AME_TOP/patch/115/import/amesappg.lct appr1.ldt  AME_APPROVAL_GROUPS APPROVAL_GROUP_NAME="Test to Move using FNDLOAD2" TRANSACTION_TYPE_ID="SSHRMS" APPLICATION_SHORT_NAME="PER"

--> Upload
FNDLOAD apps/<EnterAppsPassword> 0 Y UPLOAD $AME_TOP/patch/115/import/amesappg.lct appr1.ldt




Step 4: Create  Approver Group  Config
SELECT * from ame_approval_group_config where approval_group_id = ( SELECT approval_group_id
  FROM ame_approval_groups
 WHERE name = 'Test to Move using FNDLOAD2')

-->  Download
FNDLOAD apps/<EnterAppsPassword> 0 Y DOWNLOAD $AME_TOP/patch/115/import/amesaagc.lct apprconfig.ldt AME_APPROVAL_GROUP_CONFIG APPROVAL_GROUP_NAME="Test to Move using FNDLOAD%" TRANSACTION_TYPE_ID="SSHRMS" APPLICATION_SHORT_NAME="PER"
-->  Upload 

FNDLOAD apps/<EnterAppsPassword> 0 Y UPLOAD $AME_TOP/patch/115/import/amesaagc.lct apprconfig.ldt


Step 5: Create  Rule
select * from ame_rules where description=  'Rule to Test FND Load'
select * from ame_rule_usages where rule_id = ( select rule_id from ame_rules where Description=  'Rule to Test FND Load')

-->  Download
FNDLOAD apps/<EnterAppsPassword> 0 Y DOWNLOAD $AME_TOP/patch/115/import/amesrulk.lct amrrule.ldt AME_RULES RULE_KEY="339364792:16874" TRANSACTION_TYPE_ID="SSHRMS" APPLICATION_SHORT_NAME="PER"

-->  Upload
FNDLOAD apps/<EnterAppsPassword> 0 Y UPLOAD $AME_TOP/patch/115/import/amesrulk.lct amrrule.ldt




Step 6: Create  Rule Action Type Usages
-->  Download
FNDLOAD apps/<EnterAppsPassword> 0 Y DOWNLOAD $AME_TOP/patch/115/import/amesactu.lct ameruleactions.ldt AME_ACTION_USAGES RULE_KEY="339364792:16874" TRANSACTION_TYPE_ID="SSHRMS" APPLICATION_SHORT_NAME="PER"

-->  Upload
FNDLOAD apps/<EnterAppsPassword> 0 Y UPLOAD $AME_TOP/patch/115/import/amesactu.lct ameruleactions.ldt

Ref: How To Migrate AME Setups From One Instance To Another (Doc ID 1168883.1)


1 comment:

  1. Nice reference to AME migration. There is an app : MigrationLogiK at http://migratinologik.com which allows all FNDLOAD migrations to be automated using intuitive front end interface. Time and efforts saving is significant.

    ReplyDelete