My Oracle Support Banner

Planned Purchase Order And Local Blanked Purchase Agreement Using AME Document Style (Doc ID 1940962.1)

Last updated on MAY 11, 2020

Applies to:

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

Symptoms

For Standard Purchase Order (SPO) approval the Approval Management Engine (AME) is being used. In order to do so, the setup steps in <Note: 1487713.1> were followed.  As the Buyer Work Center is not being used, the SPOs are created through forms. This implies that the Standard Document Style has to be used and therefore the document style (Navigation: Setup > Purchasing > Document Styles) is defined as shown below.

The issue is that when Document Style (Standard Style) is defined for SPOs, it does not exclude the local Blanket Agreements (BPAs) or Planned Purchase Orders (PPOs) document types, hence enforcing the AME workflow for those document types.  When the user creates a BPA or PPO the AME workflow is initiated instead of standard PO workflow but fails approval.

 

As the document style setup takes precedence over document type setup, this setup implies that when submitting a BPAs or PPOs for approval AME is being used to approve these documents. As a result the local BPAs and PPOs cannot be approved as currently the PO AME Approval only supports SPOs and global Purchase Agreements as per <Note: 1548540.1>.

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.