Results for “ozf_sd_res_dist_prices_intf”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OZF_SD_RES_DIST_PRICES_INTF is a Trade Management (OZF) interface table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It belongs to the Oracle Trade Management module, and its documented purpose is to hold the pricing information for each product. As the "_INTF" suffix indicates, this is a staging or interface table rather than a transactional master table. It typically receives pricing records from an external source or feeder program — such as a concurrent request managed through the standard request framework — validates them, and then passes the cleaned data into the Trade Management distribution pricing structures.

The object is documented with a VALID status in the OZF schema and is owned by the OZF product. It carries a primary key constraint, OZF_SD_RES_DIST_PRICES_INTF_PK, defined on the RES_DIST_PRICES_INTF_ID column. A unique index, OZF_SD_RES_DIST_PRICES_INTF_U1, also exists on RES_DIST_PRICES_INTF_ID, confirming that this identifier is both the surrogate primary key and the single business-key candidate. The table is classified heuristically as standalone in the Data Vault model. From a modeling perspective, therefore, the recommendation is that this table behaves as an isolated staging entity with no foreign-key dependencies to other tables in the documented structure; it may be treated as a hub-like staging object rather than a true hub, link, or satellite within a formal Data Vault design.

Key Information Stored

The documented physical schema contains eight columns. The most significant are:

• RES_DIST_PRICES_INTF_ID — the surrogate primary key, populated from the OZF_SD_RES_DIST_PRICES_INTF_PK sequence. It uniquely identifies each interface row and is also the only unique-index business-key candidate.
• REQUEST_LINE_ID — associates the interface record with a specific request line, providing traceability to the concurrent request that submitted the pricing data.
• REQUEST_NUMBER — the human-readable request number identifying the originating concurrent request.
• PRICE_TYPE_CODE — the code classifying the type of price being staged (for example, list price versus distribution price).
• MONETARY_AMOUNT — the numeric price or monetary value for the product record.
• GLOBAL_CURR_CODE — the currency code in which MONETARY_AMOUNT is expressed.
• PROCESSED_FLAG — the processing status indicator used by the import/validation program to mark rows as pending, successful, or failed.
• ERROR_TXT — the error message text populated when a row fails validation or processing.

Common Use Cases and Queries

This table is typically interrogated to diagnose interface failures, to verify data loaded by a Trade Management pricing import, and to report on unprocessed or erroneous rows. Common patterns include:

• Checking for records that have not yet been processed: SELECT * FROM OZF.OZF_SD_RES_DIST_PRICES_INTF WHERE PROCESSED_FLAG = 'N' OR PROCESSED_FLAG IS NULL;
• Reviewing validation failures by extracting the error text: SELECT RES_DIST_PRICES_INTF_ID, REQUEST_NUMBER, PRICE_TYPE_CODE, ERROR_TXT FROM OZF.OZF_SD_RES_DIST_PRICES_INTF WHERE ERROR_TXT IS NOT NULL;
• Reconciling amounts by currency: SELECT GLOBAL_CURR_CODE, SUM(MONETARY_AMOUNT) FROM OZF.OZF_SD_RES_DIST_PRICES_INTF GROUP BY GLOBAL_CURR_CODE;
• Auditing a specific concurrent request load via REQUEST_NUMBER or REQUEST_LINE_ID joins to the request tables.

Related Objects

The documented relationship data classifies this object as standalone, meaning no foreign-key dependencies were mined from its structure. Consequently, related objects are inferred from naming and functional context rather than from documented FK constraints:

• OZF_SD_RES_DIST_PRICES — the likely base/target table that receives validated interface rows.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_NUMBER for request-level traceability.
• FND_CONCURRENT_PROGRAMS — identifies the pricing import program.
• OZF_SD_RES_DIST_PRICES_INTF_PK — the primary key constraint object.
• OZF_SD_RES_DIST_PRICES_INTF_U1 — the unique index enforcing uniqueness of RES_DIST_PRICES_INTF_ID.
• FND_CURRENCIES — referenced through GLOBAL_CURR_CODE for currency validation.

Because the metadata documents no explicit foreign keys, join conditions to these related objects should be confirmed against the live instance before being relied upon in production SQL.