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

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

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

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

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

4. Rules

# You can find Rule Key in AME_RULES table

1. Rules
* FNDLOAD apps/@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/@destinationdb 0 Y UPLOAD $PER_TOP/patch/115/import/amesrulk.lct amerule.ldt
* FNDLOAD apps/@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/@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

6.WORKFLOW Migration

WFLOAD apps/pw 0 Y DOWNLOAD HRSSA.wft HRSSA
WFLOAD apps/pw 0 Y FORCE .wft
WFLOAD apps/pw 0 Y DOWNLOAD erphrms1_HRSSA.wft HRSSA
WFLOAD apps/pw 0 Y FORCE HRSSA.wft