What is Behavior From Workflow Type AMSAPRV and AMSGAPP about WF_ROLES ORIG_SYSTEM Value
(Doc ID 562607.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Trade Management - Version 11.5.10 to 184.108.40.206 [Release 11.5]
Information in this document applies to any platform.
Unable To Approve Quota With Error in scope of AMSGAPP approval type
The fix was to setup the approver as a resource an not a customer as it was the case in customer situation :
where name like '%fnd_user.username%';
2. If orig_system shows FND_USR and not PER, then do the following :
a. System Administrator > Security > User > Define > Query Your FND User (fnd_user.username).
b. Disassociate the user by clearing the employee field (note which employee is there because you will replace it in the next step).
c. Save the changes on form.
d. Enter the employee name again, then save again.
3. Check wf_roles to see if the orig_system for the user switched from 'FND_USR' to 'PER'.
4. If the user is not switched, then run the Synchronize Workflow LOCAL Tables request and when
it is complete,recheck wf_roles for the user to see if it has switched.
This will be effective for one user which is now able to generate lists
I dis check further that :
Offer approval is triggering an approval process ot type AMSAPRV = AMS Marketing Approval
Claim approval is triggering an approval process of type AMSGAPP = AMS Generic Marketing Approval
User noticed that the offer approval AMSAPRV was successful by using an approver with WF_ROLES.orig_system field having FND_USR as a value (could also be PER)
But the claim approval with type AMSGAPP was successful ONLY by using an approver with WF_ROLES.orig_system field having PER as a value
Is this the product design ?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document