My Oracle Support Banner

How To Diagnose Issues With PRINT_COUNT And/Or PRINTED_DATE Being Updated Incorrectly in PO_HEADERS_ALL Table (Doc ID 1336689.1)

Last updated on APRIL 24, 2019

Applies to:

Oracle Purchasing - Version 11.5.10 to 12.2.3 [Release 11.5 to 12.2]
Information in this document applies to any platform.
Executable:POXPOPDF - PO Output for Communication

Purpose

There are several cases know that on approving / communication purchase orders the fields PRINT_COUNT and/or PRINTED_DATE in the table PO_HEADERS_ALL are updated incorrectly. In order cases these columns are not updated at at all, while it is expected that this should happen. This document provides an overview of some known issues.

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 There are several cases know that on approving / communication purchase orders the fields PRINT_COUNT and/or PRINTED_DATE in the table PO_HEADERS_ALL are updated incorrectly.
In order cases these columns are not updated at at all, while it is expected that this should happen.
This document provides an overview of some known issues.
 1. POXPOPDF sets print_count to 1 when EDI is enabled
 2. POXPOPDF Does Not Update PRINT_COUNT And PRINTED_DATE When Notification Method Is Set To Email
 3. Emailed PO's being picked up by Printed Purchase Order Report
 4. PRINT_COUNT gets incremented for change order approval of EDI enabled PO's
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.