Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

FNDLOAD for AME’s

Posted on June 12th, 2008 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Have you tried OracleappsHub in ipad/iphone/smart Phone? Don't wait. try it today

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.

list

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.

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>

usage

 

  • 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 /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.

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>

usage

 

  • 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

4AME 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.

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

usage

  • 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

5AME 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

 

  • 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

usage

  • 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

7Attribute

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

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>

usage

  • 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

8Attribute 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

usage

  • 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

dgreybarrowSimilar Post

Related Posts

Posted in AOL | 10 Comments »Email This Post Email This Post | Print This Post Print This Post

Have you tried OracleappsHub in ipad/iphone/smart Phone? Don't wait. try it today
10 Responses
  1. Srinivas Says:

    Hi
    i am using the following command for attributes i tries for other rules, appr groups, and conditions also according to your syntax but its just creating an empty ldt file without attribute details.

    can you please let me know what is wrong usage in the below command.

    earliest response will be highly appreciated.

    FNDLOAD apps/xxxx 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesmatt.lct hubattributes.ldt AME_ATTRIBUTES APPLICATION_SHORT_NAME=’PER’ TRANSACTION_TYPE_ID= ‘HRSSA’ ATTRIBUTE_NAME=’XXTJX_WS_CHANGE_PAY_OUT_OF_CYCLE’

  2. Sanjit Anand Says:

    Srinivas,

    the code is correct. check the syntex, what you are using

  3. Srinivas Says:

    Syntax is correct the thing is that in 12i we have to use AME_TOP lct files. instead of PER_TOP…

    In 12i PER_TOP lct files will only work for download…

  4. Tom Says:

    Sanjit,

    I’m having the same issue, the download file is basically empty. I’m working on 11.5.10.2 and I don’t appear to have any errors.
    FNDLOAD apps/apps@OASISTST 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesmatt.lct ame_attribute1.ldt AME_ATTRIBUTES APPLICATION_SHORT_NAME=’PER’ TRANSACTION_TYPE_ID=’HRSSA’ ATTRIBUTE_NAME=’CSEA_SUPERVISOR_OR_EMPLOYEE_SUBMIT’;

  5. Sanjit Anand Says:

    Tom, I donot think there should be any reason for creating zero byte.

    Can you check your script
    $FND_TOP/bin/FNDLOAD apps/ 0 Y DOWNLOAD $PER_TOP/patch/115/import/amesmatt.lct AME_ATTRIBUTES ATTRIBUTE_NAME= TRANSACTION_TYPE_ID=
    APPLICATION_SHORT_NAME=

    i am suspecting TRANSACTION_TYPE_ID is going wrong.

    Could you please amesmatt.lct existance in the respective folder.

  6. sudhir Says:

    How do you migrate the custom folder definitions between the instances in Oracle Apps?

    Thank you!

  7. Sanjit Anand Says:

    as per list
    http://www.oracleappshub.com/oracle-application/great-fndload-part-ii/
    item 37 , FNDFOLD.LCT might be helpful for you.

    Try this
    FNDLOAD APPS/ 0 Y DOWNLOAD $FND_TOP/patch/115/import/fndfold.lct MISC_TXN_FOLDER.ldt FND_FOLDERS NAME=”

    FNDLOAD APPS/ 0 Y UPLOAD $FND_TOP/patch/115/import/fndfold.lct MISC_TXN_FOLDER.ldt

    Advice you to review the entity content first
    good luck
    sanjit

  8. Richard Tait Says:

    Hello,
    I wonder if anyone has managed to explain the essentially empty ldt file that Srinivas mentions? In my case I ran the command on a system last week and it created a useful ldt. This week when I run it I only get the data definition, not the data. No error messages. This now occurs with any of the lct files. I can’t see that any patches have been applied and without an error message I’m stumped. Has anyone found a fix? Many thanks.

  9. bedabrata Says:

    Use SSHRMS instead of HRSSA
    as TRANSACTION_TYPE_ID…

  10. Narayan Pillai Says:

    Hi Sanjit

    I wanted to know if the FNDLOAD scripts above can be used to migrate from one instance to another in R12 (12.0.6)

    Thanks
    Narayan

Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.