Search Results ozf_location_pvt




Overview
Explore in AI Chat

Overview

OZF_LOCATION_PVT is a private PL/SQL package in the APPS schema that serves as the address and location resolution layer for Oracle Trade Management (formerly Oracle Field Sales/Telesales, OZF module) within Oracle E-Business Suite 12.1.1 and 12.2.2. The package is classified as a PVT (private) API, indicating it is intended primarily for internal consumption by other ETRM packages and views rather than as a directly callable public interface for customer extensions. Its central responsibility is to translate between surrogate location identifiers and the formatted, human-readable address and party information stored in the Oracle Trading Community Architecture (TCA) model.

The dependency metadata confirms this role: OZF_LOCATION_PVT depends only on SYS.STANDARD, while it is referenced by OZF_ALLOCATION_ENGINE_PVT, OZF_TARGET_CLOB_V, and itself. This positions the package as a low-level utility consumed by the allocation engine and by target/segmentation views, both of which require consistent address rendering and location identity resolution when evaluating accounts, sites, and parties.

Key Procedures and Functions

  • FORMAT_ADDRESS — Renders a location record into a single, display-ready address string. This centralizes address formatting logic so that allocation, targeting, and reporting components present addresses consistently regardless of the underlying TCA storage structure.
  • GET_LOCATION — Retrieves the location details associated with a given site or party site, returning the address attributes needed by callers. It acts as the primary read accessor against the TCA location tables.
  • GET_LOCATION_ID — Resolves and returns the location identifier for a site or party site context, enabling callers to obtain the surrogate key required for subsequent lookups or joins.
  • GET_PARTY_NAME — Returns the party name (customer, prospect, or organization) associated with a party or party site, supporting denormalized display of names on allocation and target screens.

No parameter lists are documented in the ETRM metadata; consumers should rely on the published package specification in the APPS schema rather than assuming signatures.

Tables Accessed

The package reads from the core TCA tables through APPS synonyms:

  • HZ_LOCATIONS — the master address record; the source for FORMAT_ADDRESS and GET_LOCATION.
  • HZ_PARTY_SITES — links parties to locations; central to resolving location identifiers and party context.
  • HZ_CUST_ACCT_SITES_ALL and HZ_CUST_SITE_USES_ALL — customer account site and site-use assignments, used to identify which sites are relevant for trade management allocations.
  • HZ_PARTIES — supplies party names for GET_PARTY_NAME.
  • OZF_ACCOUNT_ALLOCATIONS — the ETRM allocation table, read when resolving locations in an allocation context.

Usage Notes

Because OZF_LOCATION_PVT is a private package, it is not exposed as a formal public API. It is most commonly invoked indirectly: OZF_ALLOCATION_ENGINE_PVT calls it during allocation processing, and OZF_TARGET_CLOB_V uses it when materializing target and segmentation data that includes address or party-name attributes. Custom code should generally call the public TCA APIs or the higher-level OZF packages rather than OZF_LOCATION_PVT directly, since private packages may change without notice between patch levels. Where direct invocation is unavoidable, developers should confirm the specification in the target release (12.1.1 versus 12.2.2), as the internal signature may differ.