Search Results default_headers




Overview
Explore in AI Chat

Overview

PO_R12_CAT_UPG_DEF_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Procurement module, owned by the APPS schema and declared with AUTHID CURRENT_USER. Its name reflects its role in the R12 catalog upgrade process: it supplies defaulting logic used when populating the header and line interface records processed by the companion package PO_R12_CAT_UPG_PVT. The package header carries the revision marker $Header: PO_R12_CAT_UPG_DEF_PVT.pls 120.1 2006/01/30, indicating that this code was authored as part of the original Release 12 upgrade infrastructure and has remained largely stable through 12.1.1 and 12.2.2.

The business purpose of the package is to ensure that records migrated or converted into the purchasing catalog during the R12 upgrade carry the mandatory and derived attribute values required before validation and import. Rather than requiring every source record to be fully populated, the defaulting package inspects the current header or line record, consults system parameters, session context, and reference tables, and fills in values that can be reliably inferred. This reduces the volume of incomplete interface rows that would otherwise fail validation.

Key Procedures and Functions

The documented package exposes two public procedures, both of which accept a single IN OUT parameter of a record type defined in PO_R12_CAT_UPG_PVT:

  • DEFAULT_HEADERS — Accepts a headers record of type PO_R12_CAT_UPG_PVT.record_of_headers_type. It applies defaulting rules to header-level attributes on the upgrade record before the record is passed to validation or insert logic. The parameter is passed IN OUT NOCOPY, so the caller's record is modified in place. This is the procedure most directly associated with the search term default_headers.
  • DEFAULT_LINES — Accepts a lines record of type PO_R12_CAT_UPG_PVT.record_of_lines_type and applies the corresponding defaulting rules to line-level attributes, again modifying the caller's record in place. Line defaults are typically derived from the parent header context as well as item and line-type reference data.

Tables Accessed

The package interacts with the following tables through APPS synonyms:

  • PO_HEADERS_INTERFACE and PO_HEADERS_ALL — source and target structures for header-level defaulting and validation context.
  • PO_SYSTEM_PARAMETERS_ALL — supplies purchasing system option values that feed default logic.
  • PO_SESSION_GT and PO_SESSION_GT_S — global temporary session structures used to carry runtime context across the upgrade run.
  • PO_AGENTS — used to derive and validate the buyer/agent attribute on headers and lines.
  • HR_ALL_ORGANIZATION_UNITS — provides operating unit and organization identifiers required for multi-org defaulting.
  • MTL_SYSTEM_ITEMS_B — item master reference used when defaulting line-level item attributes.
  • PO_LINE_TYPES_B — line type reference used to default line type and associated behavior.
  • DUAL and PLITBLM — utility references used for scalar evaluation and PL/SQL table handling.

Usage Notes

PO_R12_CAT_UPG_DEF_PVT is a PVT package and is not intended for direct invocation by end users or general custom code. It is called internally by PO_R12_CAT_UPG_PVT and is referenced by one other package in the ETRM metadata. In practice, invocation occurs indirectly through the R12 catalog upgrade concurrent programs that drive the header and line interface processing. Because it is a private API, Oracle does not guarantee its signature across releases; customers extending the upgrade path should call the public upgrade entry points rather than the defaulting procedures themselves. When troubleshooting upgrade failures related to missing or incorrect defaulted values, DBMS_OUTPUT tracing or SQL tracing on the calling upgrade program is the appropriate diagnostic approach, since the procedures operate on in-memory records passed by the caller.