Purchase Orders: Operating Unit Level 'Workflow Start Process' Set At Document Types (Solution to Use AME For Some Operating Unit and Not AME for Other Operating Units) (Doc ID 1619566.1)

Last updated on MARCH 20, 2017

Applies to:

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

Symptoms

There is a requirement to have some Operating Units (OUs) used in Purchase Order (PO) Approval Management Engine (AME) approval.  It is found that some OUs use the old method of approval hierarchy (approval group/approval assignment) when using the same Document Style:

Replication steps:

1.  Navigate from the Purchasing responsibility to Document Style Setups:
Setup>Purchasing Document Styles

Note the following parameter setttings:

Name = Standard Style
Type = Standard Purchase Order is enabled
Workflow Startup Process = PO AME Approval Top Process
AME Transaction Type = Purchase Order Approval

2.  Then navigate to Document Types:
Setup>Purchasing Document Types

Note the following parameter setttings:

for US OU:
 Workflow Start Process = PO AME Approval Top Process

for Canada OU:
 Workflow Start Process = PO Approval Top Process

3.  Create a Purchase Order for $1000 created for US OU and $2000 for Canada OU

However it is found the POs move the AME routes though its setup only for US OU only.

Moreover, if  the ‘Workflow Startup Process’ is changed at the Document  Style level to ‘PO Approval Top Process’, even the Purchase Orders created in the US OU will stop taking the AME route.

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