Results for “ozf_process_setup_all”

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

Overview

OZF_PROCESS_SETUP_ALL is a Trade Management (OZF) transactional setup table within Oracle E-Business Suite, documented as VALID in the OZF schema. Its purpose is to store Price Protection Execution process setup details, specifically controlling whether individual Price Protection processes are enabled or disabled and whether they execute automatically or must be triggered manually. Because Price Protection involves complex workflows for claim and accrual processing, this table functions as a configuration control point that drives runtime behavior of the Price Protection engine.

Under a heuristic Data Vault classification mined from its foreign key structure, this table is modeled as a standalone entity. In Data Vault terms, this suggests treating it as an independent satellite or reference table rather than as a link table. The only documented foreign key relationship is the SECURITY_GROUP_ID column referencing FND_SECURITY_GROUPS, indicating that data access is filtered through Multi-Org / security group mechanisms. The table is uniquely identified by OZF_PROCESS_SETUP_ALL_U1 on PROCESS_SETUP_ID.

Key Information Stored

The physical schema for release 12.2.2 documents 34 columns. The most significant include:

• PROCESS_SETUP_ID — the surrogate primary key and the business-key candidate, enforced by unique index OZF_PROCESS_SETUP_ALL_U1.
• SUPP_TRADE_PROFILE_ID — associates the process setup with a supplier trade profile, effectively the parent configuration record.
• ORG_ID — the operating unit, supporting Multi-Org access control.
• PROCESS_CODE — identifies which Price Protection execution process the setup applies to.
• ENABLED_FLAG — determines whether the process is active or inactive.
• AUTOMATIC_FLAG — indicates whether the process runs automatically or requires manual invocation.
• OBJECT_VERSION_NUMBER — used for optimistic locking during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, CREATED_FROM — concurrent program and origin tracking columns.
• SECURITY_GROUP_ID — the documented foreign key to FND_SECURITY_GROUPS.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF-enabled descriptive flexfield columns for extensibility.

Common Use Cases and Queries

Typical use cases center on validating and troubleshooting Price Protection behavior. A common query joins the table to supplier trade profiles and reports which processes are enabled or automatic:

• SELECT process_setup_id, supp_trade_profile_id, process_code, enabled_flag, automatic_flag FROM ozf.ozf_process_setup_all WHERE org_id = :org_id;
• Auditing: retrieve rows where last_update_date > :cutoff to identify recent configuration changes.
• Diagnostics: filter on enabled_flag = 'N' to detect disabled processes that may explain missing claim processing.
• Reporting: count active automatic versus manual processes grouped by process_code.

Related Objects

The most significant dependencies and related objects include:

• FND_SECURITY_GROUPS — joined via ozf_process_setup_all.security_group_id = fnd_security_groups.security_group_id.
• OZF_SUPP_TRADE_PROFILES — the implied parent of SUPP_TRADE_PROFILE_ID for supplier trade profile definitions.
• OZF_PROCESS_SETUP — the base table, with _ALL indicating org-specific data storage.
• OZF_CLAIMS, OZF_CLAIM_LINES — downstream claim processing affected by these setup flags.
• OZF_ACCRUALS — accrual processing governed by the same execution controls.