Last updated on AUGUST 21, 2016
Applies to:Oracle iSupplier Portal - Version: 12.0.0
Information in this document applies to any platform.
On R12 instance:
When a Supplier profile Administrator reviews the Bank Accounts added by a supplier and approves
or rejects or puts under a verification a bank acoount request, an email should be sent out to the
supplier informing them of the action taken by the Buyer admin . This howewer is not happening.
Log on as Sysadmin and query the status monitor for Workflow 'POS Supplier Registration
and Profile Management'. Find that the bank account related notifications are in the deferred
status and are later erroring out . The error message is always similiar to Failed Activity
Notifications on bank account request approved
Activity Type Notice
Error Name WFNTF_ROLE
Error Message 3205: 'POSSPM1_PACCOUNT_ACTION_3_04212007_111234' is not a valid role or user name.
Error Stack Wf_Notification.SendGroup(POSSPM1_PACCOUNT_ACTION_3_04212007_111234, POSSPM1,
ACCOUNT_APPROVED, WF_ENGINE.CB) Wf_Engine_Util.Notification_Send(POSSPM1,
POSSPM1_PACCOUNT_APPROVED_3_1742075473, 185037, OSSPM1:ACCOUNT_APPROVED)
Wf_Engine_Util.Notification(POSSPM1, POSSPM1_PACCOUNT_APPROVED_3_1742075473, 185037, RUN)
Note: Other processes like Approval Request for Prospective Vendor Registration etc which are a part of the same workflow go through succesfully.
Steps To Reproduce:
The issue can be reproduced will with the following steps:
1. Log on as a supplier external user . Create a new Bank account
2. Now log on as a buyer administrator and review Bank Accounts. Either approve or reject or put the
bank account request under verification.
Now the 'POS Supplier Registration and Profile Management' workflow should send an email to the
supplier informing them of the action taken by the admin. The notification never goes through. On
examining the Workflow using SYSADMIN login, find the activity 'Setup receivers for account actions'
is in the deferred state.
3. Run the Workflow Background process with Parameter 'Deferred Proccess' to Yes then this
workflow immediately errors out.
NOTE: Running the 'Synchronize WF Local tables' request set before running the Workflow
Back groung Engine process does not help either.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms