XML_FLAG on po_headers_all Table is Set to 'N' After Creating a PO With Communication Method as 'XML'.

(Doc ID 2259294.1)

Last updated on JUNE 26, 2017

Applies to:

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

Symptoms

On : 12.1.3 version, Purchase Order

ACTUAL BEHAVIOR
---------------
XML_FLAG is set to 'N' in po_headers_all table when approving PO with communication method as XML

This was working just fine before <Patch 22779630>

EXPECTED BEHAVIOR
-----------------------
correct XML_FLAG details i.e 'Y' should be populated in po_headers_all table if communication method is XML

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Install <Patch 22779630>
2. In the Buyer Work Center, create a new Purchase Order - select a supplier which is setup as a trading partner on the XML Gateway. The Communication Method automatically changes to XML, which is expected behaviour
3. Send the PO for approval
4. Check the XML_FLAG on po_headers_all table. The value is 'N', while we expect here a 'Y'

Another symptom may be as below

ACTUAL BEHAVIOR
---------------

When we create a new Purchase Order with Communication Method XML and submit it, then POAPPRV workflow is started but it does not launch child-flow "PO Xml Delivery" which sends XML via Outbound Monitor to Supplier.

EXPECTED BEHAVIOR
-----------------
POAPPRV workflow should launch the child-flow "PO Xml Delivery" if communication method is XML

 

 

 

Changes

 Issue started after Patch 22779630/25096931 applied

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