Search Results update_supp_trade_profile

Overview

OZF_SUPP_TRADE_PROFILE_PUB is a public PL/SQL API in the Oracle E-Business Suite (EBS) Trading Community / Supplier Trade Profile module, owned by the APPS schema. In EBS 12.1.1 and 12.2.2 it provides a supported, programmatic interface for creating and maintaining Supplier Trade Profile records together with the associated code conversion and price protection setup data. The package is declared AUTHID CURRENT_USER, meaning executing privileges are resolved through the calling schema rather than the definer, and it exposes its functionality to external callers as a public API (noted as "PUB" and marked compatible in the API repository metadata). Its business purpose is to centralize the persistence logic for supplier trade profiles so that callers do not write directly to the underlying base tables, thereby preserving validation, audit columns, and object versioning.

Key Procedures and Functions

The ETRM documentation lists four documented program units, all within the OZF_STP business entity category:

• CREATE_SUPP_TRADE_PROFILE — Creates a new supplier trade profile record. It accepts the supplier trade profile record structure (supp_trade_profile_rec_type) and related setup data, populating the primary keys, WHO columns, and object version number for the new row.
• UPDATE_SUPP_TRADE_PROFILE — Updates an existing supplier trade profile record. This is the procedure most relevant to the search term "update_supp_trade_profile"; it modifies the trade profile attributes and related setup data, maintaining the object version number for optimistic locking.
• PROCESS_CODE_CONVERSION — Processes supplier code conversion setup data associated with the trade profile, writing to the code conversion tables.
• PROCESS_PRICE_PROTECTION — Processes price protection setup data, creating or updating the relevant records used for price protection processing.

Tables Accessed

The package references the following tables through APPS synonyms. Trade profile data is held in OZF_SUPP_TRD_PRFLS_ALL, which is the primary table written by the create and update routines. Supplier and site context is validated against AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL. Trading community records are resolved through HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, and HZ_LOCATIONS. Code conversion and price protection setup data is stored in OZF_SUPP_CODE_CONVERSIONS_ALL and its sequence OZF_SUPP_CODE_CONV_ALL_S, with settlement method and process configuration held in OZF_CLAIM_STTLMNT_METHODS_ALL and OZF_PROCESS_SETUP_ALL. DUAL supports PL/SQL structural evaluation and PLITBLM is used for local temporary character table operations.

Usage Notes

The API is a base-table substitution layer: it should be invoked instead of direct DML against OZF_SUPP_TRD_PRFLS_ALL and the associated setup tables. It carries no business event registration, so it does not raise a workflow or business event on completion. Typical callers include the Supplier Trade Profile maintenance forms, price protection and code conversion concurrent programs, and custom extensions or integration code that must seed or amend trade profile definitions. Because the record type initializes every attribute to FND_API.g_miss_* sentinels, callers must set only the columns they intend to change and rely on the API to distinguish missing values from explicit ones. The package is referenced by zero other packages per the metadata, confirming it sits at the top of its dependency chain as a terminal public API. Optimistic locking is enforced through the object_version_number, so callers performing updates should pass the current version to avoid concurrent modification conflicts.