Tuesday, February 28, 2017

How to Enable AME for GL Journal Approval



My title Prerequisites for doing AME setup
1) Person should have "Approval management Business Analyst" responsibility and "Approval management Administrator" responsibility  attached.
2) All roles for Approval management should be added to user login by using "user management" responsibility.
3) Grant Access has been given for AME.


Front End Setup steps in GL Module

Step1 : Enable journal Approval in ASM


Go to General Ledger Super User -> Setup -> Financials -> Accounting Setup Manager -> Accounting Setups
 Here search for ledger you want to enable AME for and click on Go button.

Click on Update Accounting Options:


In primary Ledger Section, Click on update in first row i.e. Ireland USD.



Now in left hand section, Click on Ledger options, you will be taken to the below screen:


Now in "Journal processing " Section , select the check box "Enable Journal Approval". Click on next, next and finish.

 Step2 : Enable require journal Approval in Journal Source

Go to General Ledger Super User -> Setup -> Journal -> Sources
 
 
 
Now query for the source for which you want to enable AME. and select the check box of "Require Journal Approval" and save the details.
 
 
 

 Step3: Set the required profile options:

Mandatory:

GL: Use Approval Management (AME) for journal approval  -  "Yes"
Journals: Allow Preparer Approval                                           -  "Yes"
 

Optional:

Journals: Find Approver Method                                            - "Go Direct"
GL: Number of journal lines to display in AME journal approval notification - "10"
 
 

Step4 : AME SETUP Steps

1) Create the Attribute as per your business requirement
2) Create the conditions based on attributes
3) Create Approver Group either static or dynamic based on your requirement
4) Use Existing Action type as "Approval group of chain authority".
5) Create an AME rule by using condition and approver group created.
 
Test the AME setup if done properly or not by using test workbench by providing Transaction id .Once journal Entry is created, data goes into GL_JE_HEADERS and GL_JE_LINES table. JE_BATCH_ID value is used as a TRANSACTION_ID in AME.
 
To create Journal Entry go to general Ledger Super User-> Journals -> Enter
 
 
 
When you save these details , below Approve button will get enabled. Once you press Approve button, it will send notification to Approver.
 
 
I hope this article will be useful for you people. Please let me know if you have any questions on the same. post your queries in comments section, will respond you.
 
 
 
 

Friday, February 24, 2017

Create Grant Access for Transaction Types to User



1. Login to Oracle Application. Go to Function Administrator Responsibility and Under the security tab, click on Grant link. You will be taken to the below screen. Enter the fields as shown and click on next button

2.  Keep Data context as all rows and click on next.

3. Here Select  set as "AME Calling Applications". And click next button.

4. You will see the review page, check all the details here. If all fine click on Finish.


By this way you can create grant access to User for AME Transaction Types.
 

 

Sunday, February 12, 2017

FNDLOAD upload and download commands in oracle apps

FNDLOAD UPLOAD AND DOWNLOAD COMMANDS


Message

FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afmdmsg.lct <Name of ldt file>.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME=<application short name> MESSAGE_NAME="message code"

FNDLOAD  <username>/<password>  0 Y UPLOAD $FND_TOP/patch/115/import/afmdmsg.lct <Name of ldt file>..ldt UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

Concurrent Program

FNDLOAD  <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct <Name of ldt file>.ldt PROGRAM APPLICATION_SHORT_NAME=<application_short name> CONCURRENT_PROGRAM_NAME="XXCUST_CP"
FNDLOAD  <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct <Name of ldt file>.ldt UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

Data Definition

FNDLOAD  <username>/<password> 0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct <Name of ldt file>.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=<application_short name>  DATA_SOURCE_CODE=XXCUST_DS
FNDLOAD  <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afsload.lct <Name of ldt file>.ldt

Request Set

FNDLOAD  <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct <Name of ldt file>.ldt REQ_SET REQUEST_SET_NAME='XXCUST_RS'

FNDLOAD  <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct  <Name of ldt file>.ldt UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

Request Set Link

FNDLOAD  <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct <Name of ldt file>.ldt REQ_SET_LINKS REQUEST_SET_NAME='XXCUST_LNK'

FNDLOAD  <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct  <Name of ldt file>.ldt UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

Lookups

FNDLOAD  <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct <Name of ldt file>.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME=<application_short name> LOOKUP_TYPE=<lookup type>
FNDLOAD  <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/aflvmlu.lct  <Name of ldt file>.ldt UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

Profile

FNDLOAD  <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct <Name of ldt file>.ldt PROFILE PROFILE_NAME=<profile name> APPLICATION_SHORT_NAME=<application_short name>
FNDLOAD  <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afscprof.lct <Name of ldt file>.ldt 

Menu

FNDLOAD  <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct <Name of ldt file>.ldt MENU MENU_NAME=<Menu Name >
FNDLOAD  <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afsload.lct <Name of ldt file>.ldt

Form Function

FNDLOAD  <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct <Name of ldt file>.ldt FUNCTION FUNC_APP_SHORT_NAME=<application short name > FUNCTION_NAME=<function name>
FNDLOAD  <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afsload.lct <Name of ldt file>.ldt

Descriptive Flex fields with all of specific Contexts

 FNDLOAD   <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct <Name of ldt file>.ldt DESC_FLEX P_LEVEL=:COL_ALL:REF_ALL:CTX_ONE:SEG_ALL? APPLICATION_SHORT_NAME=<application_short name>
DESCRIPTIVE_FLEXFIELD_NAME="desc flex name" P_CONTEXT_CODE="context name"
 FNDLOAD   <username>/<password> 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct <Name of ldt file>.ldt


Request Group


 FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct <Name of ldt file>.ldt REQUEST_GROUP REQUEST_GROUP_NAME="request group"APPLICATION_SHORT_NAME=<application_short name>
 FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt

Value Sets & Value Sets with values

 FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct <name of ldt file>..ldt VALUE_SET FLEX_VALUE_SET_NAME="value set name"
 FNDLOAD <username>/<password> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct <name of ldt file>.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME="value set name"
 FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct <name of ldt file>.ldt
 FNDLOAD <username>/<password> O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt