My Oracle Support Banner

Using Autocreate The Requisition Is Not Created Into A Purchase Order And No Errors Are Encountered (Doc ID 1409466.1)

Last updated on MAY 07, 2019

Applies to:

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

Symptoms

Purchase Orders are not getting autocreated from requisition without any errors.

Replication Steps:
1. Purchasing responsibility.
2. Create requisition.
3. Approve requisition
4. Using autocreate form, query for the requisition and try to convert it into a Purchase Order.
5. Nothing happens. No error also noted.

Other:
The trace file shows the following:
PARSING IN CURSOR #44 len=195 dep=1 uid=173 oct=6 lid=173 tim=1328602289222336 hv=3740950577 ad='83f72a18' sqlid='4pyc4xvggns1j'
UPDATE PO_UNIQUE_IDENTIFIER_CONT_ALL SET CURRENT_MAX_UNIQUE_IDENTIFIER = CURRENT_MAX_UNIQUE_IDENTIFIER +1 WHERE TABLE_NAME = :B2 AND ORG_ID = :B1 RETURNING CURRENT_MAX_UNIQUE_IDENTIFIER INTO :O0
END OF STMT

ERROR #42:err=1 tim=1328602289296595
STAT #42 id=1 cnt=0 pid=0 pos=1 obj=0 op='UPDATE PO_HEADERS_ALL (cr=0 pr=0 pw=0 time=0 us)'
STAT #42 id=2 cnt=1 pid=1 pos=1 obj=44959 op='INDEX UNIQUE SCAN PO_HEADERS_U1 (cr=1 pr=0 pw=0 time=0 us cost=0 size=22 card=1)'
CLOSE #42:c=0,e=1,dep=1,type=3,tim=1328602289296901

err=1 represents a unique constraint violation.

Changes

 

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
Changes
Cause
Solution


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