Procuring Flow Setup is not Triggered While Using Blanket Purchase Agreement (BPA) Based Catalog - TRANSACTION_FLOW_HEADER_ID Missing PO_LINE_LOCATIONS_ALL (Doc ID 1964124.1)

Last updated on JANUARY 31, 2016

Applies to:

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

Symptoms

TRANSACTION_FLOW_HEADER_ID column is null in po_line_locations_all for Purchase Orders created sourced to a BPA through the Buyer Work Center (BWC).  Procuring Flow setup is not triggered while using BPA based Catalog.  The global procurement and procuring organization is different than the receiving organization. Destination charge account and transaction flow header id, etc does not get populated and it does not interface to Accounts Receivable (AR) for inter-company settlement etc.


Replication Steps:
1. Global Blanket Agreement is created and assigned to different operating units, assuming global blanket agreement is created in operating unit A.
2. Use operating unit B to create a requisition.
3. Autrocreate the requisition into a standard purchase order.
4. Find that critical details for the intercompany flow are missing in po_line_locations_all - ex  TRANSACTION_FLOW_HEADER_ID

Other:
The process works as expected for the POs entered manually.  However, for same details, when It is created using BPA Catalog, the application does not follow the same intercompany process.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms