Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Search
Reply to this Thread Back to Thread List
Forum
Replies: 15 - Pages: 2 [ 1 2 | Next ] - Last Post: Feb 11, 2010 6:45 AM Last Post By: user9136716
Thanks,
Yasser
Post iProc related to Questions under the Procurement section instead of Financials..
Cheers
Ganesh
For further details you can refer to following MOS (Metalink) notes.
1st note (ID 293315.1) is an FAQ where you can find answers to your question.
The 2nd (ID 434143.1) contains a White Paper giving details of AME setups for Purchase
Requisitions.
293315.1 : 11.5.10 FAQ for Approvals Management (AME) Integration For iProcurement and
Purchasing
434143.1 : How To Setup And Use AME For Purchase Requisition Approvals
559886.1 : How To Find Versions And Enhancements, And Find The Right Documentation for
AME In Procurement
Thanks
Supro
Best Regards,
Yasser
You can use Position hierarchy in AME provided you have already defined it in HRMS
(full) or Purchasing (shared HR) and have jobs and employees assigned to positions. You
can create a position hierarchy using the structure you have provided and can use that
while defining the approval group using action types "hr position" (chain ends with an
approver having a fixed position) OR "hr position level" (chain contains a fixed number of
positions). This will require positions and jobs to be defined with eomloyees assigned
and then creating the hierarchy. I'll not sure if you are using that at this moment. Also
there can be multiple incumbents for "positions" like AP Accountant, Supervisor etc
based on your organization size and structure.
If you are not using position hierarchy in HRMS/ Purchasing as described above then,
alternatively if you have single employee linked to each of the "positions" (in that sense
if your are not using position hierarchy) and use same hierarchy for all your PR approvals
then you can use the following approaches to have similar result:
- Define an approval group with Chain of Authority action type. Voting Regime = 'Serial'.
Use static option (Active List) to include the approvers and order them using group
member's Order Number and type 'Unique', based on the structure you have given. You
can use "HR People" for approver type or FND Users. Here you can use the action type
"chain of authority includes an approval group" for list-creation rule type.
- Define separate approval group for each "position" in your structure and include
respective approver(s) using static or dynamic method (using query / function call). Thus
for the structure given you'll have 5 approval groups. Here also you can use "HR People"
for approver type or FND Users. Here you can use the action type "chain of authority
includes an approval group" for list-creation rule type.
Now these approval groups need to be included in Rule(s) that you define and any
associated condition based on your business requirement.
- Using another approach you can define Jobs and assign employees to these jobs.
Additionally you can populate supervisors for each employee. This has to be properly
maintained when there are changes in reporting hierarchy. Populate "Approval Authority"
field in job definition if you want to use "chains of authority based on absolute job level"
action type for this one. If employee-supervisor data is maintained then you can also use
"chains of authority based on number of supervisory levels" action type.
"chain of authority includes an approval group" >> if you are using approval group
"chains of authority based on absolute job level" >> can go upto 10 job levels. You need
to populate "Approval Authority" field in job definition for all jobs to be used here.
If your approval rules work this way then you need to setup conditions. Any rule setup
without a conditions is true for all the transaction for that transaction type.
Thanks
Supro
Error Message ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "APPS.PO_REQAPPROVAL_INIT1", line 7823 ORA-06512: at
"APPS.POR_AME_APPROVAL_LIST_WF1S", line 467 ORA-20001: Oracle Approvals
Management has found parallelization configuration details. The context in which ame_api has
been invoked does not support parallelization.
Best Regards,
Yasser
Also I need to understand how you are using the combination list-creation rule, is it for
"combining multiple
list-creation, pre-chain, and/or post-chain actions" OR for "combining multiple list-
modification and/or substitution actions".
You need to understand that, you cannot use static approvers through approval groups and
auto generated approvers say for HR position or Job etc together where parallelization is
not supported. Currently AME for PRs doesn't support parallelization of approvers.
Actually what is happenig here is that, AME is trying to "insert" the static approver based
on your approval group between auto generated approvers as per "Chains of authority
based on a particular HR position". Thus it is instructing AME to process those 2 separate
type of approvers in parallel and hence it is raising parallelization error. Use only one
method for generating your approver list.
Thanks
Supro
Best Regards,
Yasser
2. Check the voting regime of the approver groups which are having the issue are set to
'Serial'.
Groups Tab -> Select the appropriate Approval Group -> Voting Regime -> Set to 'Serial'
3. Check the order number for the approval groups / approvers withing the approval
group have unique order number
i.e.
For 1st Approval Group, Order Number = 1
For 2nd Approval Group, Order Number = 2 etc
There should not be same order number for 2 groups, if there are multiple approval
groups
If you find any issue as mentioned in point 1-3 then correct that and test. Otherwise you
can follow these Metalink Notes for debugging. These tests will required backend access
for running queries ...may be in some cases APPS.
Doc ID: 428552.1 >> How To Diagnose Issues With Approvals Management Engine
(AME) In Procurement
Doc ID: 338508.1 >> Error "Oracle Approvals Management has found parallelization
configuration..."
Otherwise for testing purpose try to set it up in a different way to identify the problem
and to confirm if any patch is needed.
4. For testing purpose, can you define 1 approval group for each position and then
assign the respective position to the corresponding group. i.e. 1 group for Buyer and
assign Buyer position; group order number unique & 1.
1 group for say Accountant and assign Accountant position; group order number unique
& 2 etc upto CEO position. I think you have total 5.
Define a rule and assign include all groups.
Test the approval process.
5. Since you have defined the positions and assigned jobs & employees try setting it up
in a different way and test.
Do not use approval group in this case. In the rule use action type "chains of authority
based on a particular HR position". Before you can use this go to Actions tab and for "hr
position" action type add an action and specify the CEO's position (Requires Approval
upto).
If not already defined, you might have define the usage for following mandatory
attributes required for "hr position" action type for "Purchase Requisition Approval"
transaction type. Attributes tab >> Add Attribute >> Pick from LOV >> "Use Selected
Name" button >> Continue.
Also set the values of these mandatory attributes for this action type. Check AME
implementation guide for details.
NON_DEFAULT_POSITION_STRUCTURE_ID
NON_DEFAULT_STARTING_POINT_POSITION_ID
TRANSACTION_REQUESTOR_POSITION_ID
Now setup a rule and select "chains of authority based on a particular HR position". It
you ask you to select the action previously defined under "hr position" action type.
Complete the setups and test.
Thanks
Supro
Regards,
Supro
Which is the closest action type that can be used instead of HR positions? Is it possible
to make use of these position hierachies in any way in the new action type? As it allows
business users to continue maintaining position hierarchies in core apps.
Another question is, how to setup an ability to change first default approver while
submitting requisitions for approval AFTER the pre-chain-of-authority approvals.
Thanks in Advance
Chetan
scenario below:
Action Type:
NAME: Hr Possition, then i created the possitions as set up in HR and on the possition
hirerarchy (i.e. 02.manager)
Conditions:
Condition Type: Ordinary
Attribute: PO_COST_CENTER
Data Type: String
Item Class: Line Item
String Value : Cost Center Number (i.e. 20050)
AND;
REQUISITION_TOTAL is greater than or equal to 0 and less than or equal to 20000,ZAR
Rule:
Action Type:hr possition
Action:Requires approval up to HR Positions:02.Manager
thanks in advance