Search Results ozf_supp_trd_prfls_pkg




Overview
Explore in AI Chat

Overview

OZF_SUPP_TRD_PRFLS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and validated as VALID in the ETRM metadata for release 12.2.2 (and applicable to 12.1.1). The package forms part of the Oracle Trade Management (OZF) module, which governs supplier trade profiles, accruals, claims, and funds within the EBS Advanced Pricing and Trade Management suite. Its role is to encapsulate the core Data Manipulation Language (DML) operations performed against supplier trade profile records, insulating dependent objects from direct table manipulation and enforcing consistent row-level handling logic.

The package is classified in ETRM as an "OTHER" API, indicating it is not a public, externally supported application programming interface but rather an internal utility package. Its dependency footprint is narrowly scoped: it references only the SYS.STANDARD package (implicitly, as a compiled PL/SQL unit) and the APPS synonym for OZF_SUPP_TRD_PRFLS_ALL. Conversely, it is referenced by OZF_SUPP_TRADE_PROFILE_PVT and by itself, confirming that it functions as a low-level access layer beneath the private trade profile API.

Key Procedures and Functions

ETRM documents four procedures within the package. Parameter lists are not published in the metadata; only the names and their evident purpose are presented below.

  • INSERT_ROW — Inserts a new supplier trade profile row into the underlying table. It is the entry point for creating trade profile records, typically supplying the profile identifiers, supplier association, and attribute values required to establish a new profile.
  • UPDATE_ROW — Modifies an existing supplier trade profile row. This procedure applies changes to the mutable attributes of a trade profile, such as profile name, status, or associated descriptive details, while preserving the row's identity.
  • DELETE_ROW — Removes an existing supplier trade profile row. It handles the physical deletion of the profile record from the base table, ensuring the profile is no longer available to dependent trade management logic.
  • LOCK_ROW — Acquires a row-level lock on a specified supplier trade profile. This is a concurrency-control primitive used by higher-level packages to prevent simultaneous modification of a profile during read-modify-write cycles.

The absence of additional documented procedures suggests a deliberately minimal surface, with validation and business rules resident in the calling OZF_SUPP_TRADE_PROFILE_PVT package rather than in this utility layer.

Tables Accessed

The package operates against a single documented base object: OZF_SUPP_TRD_PRFLS_ALL, accessed through an APPS synonym. This table stores supplier trade profile definitions, which underpin trade management activities such as supplier funding, promotions, and accrual tracking. The "_ALL" suffix conventionally indicates an Oracle multi-org table whose rows are partitioned by operating unit or organization identifier, implying that the DML procedures may implicitly honor the current organization context. All four documented procedures — insert, update, delete, and lock — are directed at this table, and no other tables are recorded as referenced.

Usage Notes

This package should not be invoked directly by customer extensions, as it is an internal implementation detail rather than a supported public API. It is normally called by OZF_SUPP_TRADE_PROFILE_PVT, the private package that provides the higher-level business API and orchestrates validation, security, and multi-org handling before delegating physical DML to OZF_SUPP_TRD_PRFLS_PKG. In typical EBS flows, the chain of invocation begins with a Trade Management form or a concurrent program, passes through the public/private API, and terminates in these DML procedures.

Custom code that must manipulate supplier trade profiles should target OZF_SUPP_TRADE_PROFILE_PVT rather than this package, to inherit its validation and organizational logic. Direct calls to INSERT_ROW, UPDATE_ROW, DELETE_ROW, or LOCK_ROW bypass those safeguards and risk data inconsistency. The package is also referenced by itself, indicating possible internal recursion or shared private helper calls. Because no parameter details are published in ETRM, integrators relying on this object should extract the package specification from the APPS schema in the target environment before attempting any reference.