My Oracle Support Banner

Change Request on Planned PO Fails With INFORM_BUYER_PO_CHANGE When Finally Closed Releases Are Assigned to Inactive Buyer (Doc ID 2864802.1)

Last updated on APRIL 25, 2022

Applies to:

Oracle Purchasing - Version 12.2.8 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.8 version, Approvals - Req, PO

Requester Change Order Approval fails if buyer in the related PO Release is inactive (even if that Release is finally closed).

PORPOCHA Change Request ends with the error:

ERROR
-----------------------
 Release nnnnn. 1. Buyer is inactive. Please update the document with a valid buyer.

Wfstat shows exception INFORM_BUYER_PO_CHANGE for workflow type PORPOCHA as follows:

**** WorkFlow Item

Item Type Item Key Inst ID Parent Typ Parent Key Date Root Activity
---------- --------------- ------- ---------- --------------- ---------- ----------------------
PORPOCHA INFORM_345113_3 1 POREQCHA 529410-345110-3 13-OCT-21 INFORM_BUYER_PO_CHANGE

**** Activity Statuses

Inst ID Date Activity Status RESULT
------- ---------- ------------------------------- -------- ----------
1 13-OCT-21 ROOT/INFORM_BUYER_PO_CHANGE ERROR #STUCK

 
FND Debug log shows exception:

p_action_requested = DOC_SUBMISSION_CHECK
p_document_type = RELEASE
p_document_subtype = BLANKET
p_document_level = HEADER
...
Returning from PVT package
Back in GRP package. Returning to the caller SE
Error Count 1
PO_BUYER_INACTIVE
Buyer is inactive. Please update the document with a valid buyer.
PO Errors Y


Steps to reproduce:

-----------------------
 1. Requester logs into Purchasing/iProcurement responsibility
 2. Change request for the approved requisition is submitted (i.e.: change amount)
 3. POREQCHA workflow (Requester Change Order Approval) launches PORPOCHA workflow (PO Change Approval for Requester) to approve the Planned Purchase Order
 4. PORPOCHA workflow fails with error:
      "Release nnnnnn. 1. Buyer is inactive. Please update the document with a valid buyer."
       Where the Release numbers mentioned in the error message are the related Finally Closed PO releases

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
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.