Search Results po_unique_identifier_cont_all




Overview
Explore in AI Chat

Overview

PO_UNIQUE_IDENTIFIER_CONT_ALL is a Purchasing (PO) module table in the Oracle E-Business Suite database, owned by the PO schema. Its documented purpose is purchase order document number control. The table acts as a numbering authority that tracks the highest unique identifier issued for a given document type within a given operating unit, so that Purchasing can hand out sequential, non-colliding document numbers for purchase orders and related purchasing documents.

The record is configured as a standalone object for data vault modeling purposes. Rather than representing a transactional event or a relationship between two entities, it holds a controlled counter per document class and organization. In warehouse terms, this behaves less like a transaction hub and more like a reference or control entity, so a modeler would typically treat it as its own small dimension or control record rather than as a link between business entities.

Key Information Stored

The table is documented with twelve columns. The most significant are listed below.

  • TABLE_NAME — identifies the purchasing document type or the underlying table whose numbering series is being controlled. This is part of the business key.
  • ORG_ID — the operating unit for which the numbering series applies. Document sequences are maintained per operating unit, so this column scopes each counter independently. It is also part of the business key.
  • CURRENT_MAX_UNIQUE_IDENTIFIER — the last (highest) unique identifier that has been allocated for the document type and organization. The next document number is derived by incrementing this value.
  • Audit and concurrency columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID and PROGRAM_UPDATE_DATE. These record who inserted and last changed the row, when, and through which concurrent program, request, or application, which is essential for diagnosing numbering gaps and duplicate-allocation problems.

The documented primary key is PO_UNIQUE_ID_UK1, defined on (TABLE_NAME, ORG_ID). The unique index PO_UNIQUE_ID_U1 covers the same column pair, confirming that the business key and the primary key coincide. There is therefore no separate surrogate key documented on this table; the composite of document type and operating unit is itself the unique identifier.

Common Use Cases and Queries

The principal operational concern is verifying that document numbering has not exhausted a range or duplicated a value. A support query to inspect the current high-water mark for a given series is:

SELECT table_name, org_id, current_max_unique_identifier, last_update_date, last_updated_by FROM po.po_unique_identifier_cont_all WHERE org_id = :org_id ORDER BY table_name;

Investigating why a new purchase order failed to save often involves checking whether the counter row is missing for the operating unit, or whether the program that updates it is failing. Joining the control row against FND_CONCURRENT_REQUESTS on REQUEST_ID, or against FND_USER on LAST_UPDATED_BY, shows which process last advanced the counter and when. Reporting use cases include auditing numbering ranges at period close, reconciling gaps between internal document numbers and the supplier-visible PO numbers, and reviewing per-operating-unit configuration after a new organization is set up.

Related Objects

Because the table is standalone with no documented foreign keys, relationships are functional rather than enforced. The most relevant associated objects are those whose document numbers this table governs and the E-Business Suite infrastructure columns it carries.

  • PO_HEADERS_ALL — the purchase order headers whose SEGMENT1/document numbers are served by the counters maintained here, matched by ORG_ID and document type.
  • PO_DOCUMENT_TYPES_ALL_B / PO_DOCUMENT_TYPES_ALL_TL — define the purchasing document types whose names correspond to the TABLE_NAME values holding a numbering series.
  • FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to trace the concurrent request that last advanced CURRENT_MAX_UNIQUE_IDENTIFIER.
  • FND_USER — joined on LAST_UPDATED_BY or CREATED_BY to attribute changes to a responsible user.
  • FND_APPLICATION — joined on PROGRAM_APPLICATION_ID to resolve the application owning the numbering program.
  • FND_CONCURRENT_PROGRAMS — joined on PROGRAM_ID to identify the program that maintains the counter.

These associations make PO_UNIQUE_IDENTIFIER_CONT_ALL a compact but critical control point for purchase order document numbering in Oracle EBS 12.1.1 and 12.2.2.