Search Results hz_industrial_reference_pkg




Overview
Explore in AI Chat

Overview

HZ_INDUSTRIAL_REFERENCE_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the OTHER API category. It provides the low-level data access layer for the HZ_INDUSTRIAL_REFERENCE entity, which belongs to the Oracle Trading Community Architecture (TCA) and the broader Customer/Party model. An industrial reference in this context denotes a classification value that associates a party, organization, or customer record with an industry sector or industrial reference code used for segmentation, reporting, and regulatory categorization.

The package encapsulates the standard insert, update, lock, and delete operations against the underlying table so that higher-level TCA APIs and forms do not issue direct DML against the base table. Its presence in the ETRM object inventory with a VALID status confirms that the package is a supported, compiled component of the 12.1.1 and 12.2.2 code lines. The dependency metadata shows that it also relies on the SYS.STANDARD package, which is the implicit PL/SQL base package present in every compiled unit.

Because it is classified as OTHER rather than a public TCA API, the package is intended primarily for internal consumption by other TCA components rather than for direct customer extension.

Key Procedures and Functions

ETRM documents four procedures for HZ_INDUSTRIAL_REFERENCE_PKG. Each performs a single, well-defined operation against the industrial reference entity:

  • INSERT_ROW — Creates a new industrial reference row in the base table. It is the creation path used when a new industry reference or classification is established for a party.
  • UPDATE_ROW — Modifies an existing industrial reference row, supporting changes to the attribute values of a previously created record.
  • DELETE_ROW — Removes an existing industrial reference row from the base table.
  • LOCK_ROW — Acquires a row-level lock on the specified industrial reference record. This is the standard Oracle Forms and API concurrency mechanism, used to guarantee that a record cannot be modified by another session between the time it is queried and the time it is updated or deleted.

These four operations form the canonical CRUD-plus-lock pattern found in many TCA maintenance packages. The documented metadata does not expose parameter lists, and no public specification of argument signatures should be assumed from this documentation alone.

Tables Accessed

The only documented table referenced by this package is HZ_INDUSTRIAL_REFERENCE, accessed through its APPS synonym. All four procedures operate against this single table:

  • HZ_INDUSTRIAL_REFERENCE — Stores the industrial reference records themselves. INSERT_ROW writes new rows, UPDATE_ROW changes existing attribute values, DELETE_ROW removes rows, and LOCK_ROW selects a row for update to serialize concurrent access.

No other base tables are documented as direct dependencies, which indicates that the package is narrowly scoped to this one entity and does not cascade changes into related party or customer tables on its own. Any such propagation would be the responsibility of the calling API, such as HZ_ORG_INFO_PUB.

Usage Notes

HZ_INDUSTRIAL_REFERENCE_PKG is referenced by HZ_ORG_INFO_PUB, the public TCA organization information API. This means the package is typically invoked indirectly: a caller updates organization-level industry information through HZ_ORG_INFO_PUB, and that API in turn delegates the industrial reference maintenance to this package. The self-referencing dependency entry also confirms the package is listed in the TCA dependency graph alongside its own body.

Direct invocation by customers is not recommended. Because the package is classified as OTHER and is not a published public API, its specification is not guaranteed to remain stable across patches or upgrades. Customizations and extensions should instead use the supported public APIs, such as HZ_ORG_INFO_PUB, which provide the sanctioned entry points for industrial reference data. In Oracle Forms-based maintenance screens for organization or customer information, the underlying block DML is likewise routed through this package rather than executed directly against HZ_INDUSTRIAL_REFERENCE.

When troubleshooting industrial reference data issues, DBAs and developers should inspect this package's dependent code and the calling stack from HZ_ORG_INFO_PUB, since the package itself performs minimal logic beyond locking, validation-free DML, and row persistence against a single table.