My Oracle Support Banner

R12.1: AP: Invoice Approval Notification Assignment Not Working As Expected; The Assignee And Comments Are Cached From Previous Reassigned Transaction (Doc ID 2538736.1)

Last updated on DECEMBER 03, 2019

Applies to:

Oracle Payables - Version 12.1.3 to 12.2.6 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Symptoms

In Oracle Payables, on the Workflow Notification NEW reassign page, the Assignee and Comments field values shows as populated from the previous reassigned transaction.

The Assignee and Comments field values of a new reassignment should appear empty and Not be populated from the previous reassigned transaction.

Due to this issue, users invest additional time clearing the page, which is not efficient.

 

Steps To Reproduce::

  1. The end-user chooses a workflow(WF) notification for and Invoice XYZ (for example) from the worklist.
  2. Then click on [Reassign] to another ad hoc role.
  3. In the Reassign Notification screen
    1. Change the Assignee to a new role, for example: "XXXX".
    2. Enter comments; for example:  "BLAH, BLAH, BLAH".
    3. Click [Submit]
  4. The application goes back to the Worklist.
  5. Then, the same user picks another WF Notification for a different Invoice; for example: Invoice ABC.
  6. Then click on [Reassign].

  7. Instead of displaying the Assignee and Comments fields empty(NULL), the Reassign Notification page for Invoice ABC displays the information entered used before for Invoice XYZ:
      Assignee = "XXXX"
      Comments = "BLAH, BLAH, BLAH".

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.