Search Results lock_supp_trade_profile




Overview
Explore in AI Chat

Overview

The APPS.OZF_SUPP_TRADE_PROFILE_PVT package is a private (PVT-classified) PL/SQL API within the Oracle E-Business Suite Trade Management (formerly Oracle Price Protection / DPP) module. Its principal business function is to manage Supplier Trade Profiles, which are the configuration records that define the commercial terms, tolerances, accounting defaults, and communication settings governing trade activity between a buying organization and its suppliers. Supplier Trade Profiles drive downstream price protection and deal-management processing, including the handling of supplier price increases, claim generation, authorization periods, grace days, and quantity-increase tolerances.

Because the package is classified as PRIVATE (PVT), it is not exposed as a public integration API. It is intended for internal consumption by the Trade Management application layer and by other EBS packages that orchestrate supplier trade profile maintenance. The package encapsulates the record structure supp_trade_profile_rec_type, which carries the full attribute set for a supplier trade profile — identifiers (supplier, supplier site, party, customer account and site), approval flags, GL accounting defaults (contra liability and cost adjustment accounts), default days covered, claim communication and frequency details, and descriptive flexfield (DFF) attributes (attribute_category through attribute8 and beyond). The header history references ER 7377460 (DFF support for the DPP section) and ER 7475578 (price protection price increase enhancement), confirming the package's role in supplier trade profile maintenance across 12.1.1 and 12.2.2.

Key Procedures and Functions

The metadata documents seven procedures and functions:

  • CREATE_SUPP_TRADE_PROFILE — Creates a new supplier trade profile record, populated from the supp_trade_profile_rec_type structure, and persists default term attributes.
  • UPDATE_SUPP_TRADE_PROFILE — Modifies an existing supplier trade profile, applying changes such as accounting defaults, tolerances, claim settings, and DFF attributes.
  • DELETE_SUPP_TRADE_PROFILE — Removes a supplier trade profile record. This is the procedure most relevant to the user search term delete_supp_trade_profile, and it is invoked when a profile is no longer required or must be purged.
  • LOCK_SUPP_TRADE_PROFILE — Acquires the record for update (via SELECT … FOR UPDATE) to prevent concurrent modification before a change is committed.
  • VALIDATE_SUPP_TRADE_PROFILE — Performs validation on the profile record, ensuring required fields and referential integrity are satisfied before DML.
  • CHECK_SUPP_TRD_PRFL_ITEMS — Verifies that line items associated with the profile exist and are consistent before allowing a create, update, or delete operation.
  • VALIDATE_SUPP_TRD_PRFL_REC — Validates the record structure passed in (the supp_trade_profile_rec_type), typically executing pre-DML field-level checks.

Tables Accessed

The package reads from and writes to the following tables via APPS synonyms:

  • OZF_SUPP_TRD_PRFLS and OZF_SUPP_TRD_PRFLS_ALL — the base table and its multi-org "ALL" counterpart, storing supplier trade profile header records.
  • OZF_SUPP_TRD_PRFLS_ALL_S — the sequence used to generate primary keys for the ALL table.
  • OZF_SYS_PARAMETERS — retrieved for system defaults and configuration values.
  • HZ_CUST_ACCOUNTS — validated against customer (supplier) account records to confirm the supplier identity referenced by the profile.
  • HZ_CUST_SITE_USES — validated against customer site use records, supporting site-level profile configuration.
  • DUAL — used for single-row queries, sequence validation, and constant retrieval.

Usage Notes

Because OZF_SUPP_TRADE_PROFILE_PVT is a private package, it is typically invoked from within the Trade Management application codebase and from the supplier trade profile maintenance form or its underlying OAF controller. Direct invocation from custom code is discouraged; integrators should prefer public APIs. Deletion of a supplier trade profile via DELETE_SUPP_TRADE_PROFILE is normally triggered from the Trade Management UI or from a concurrent program performing purge or archival of obsolete supplier trade profiles. The package is referenced by two other packages, which likely orchestrate profile lifecycle operations and should be reviewed before any customization. All calls execute within the APPS schema and rely on the standard fnd_global context for organization and user identifiers. Given the 12.1.1 / 12.2.2 target versions, the package behaves consistently in both releases and requires no known upgrade-specific code changes.