Search Results hz_dss_scheme_functions




Overview
Explore in AI Chat

Overview

HZ_DSS_SCHEME_FUNCTIONS is a Receivables (AR) module table that defines the relationship between data security schemes and the Oracle E-Business Suite functions they govern. Within the Oracle EBS 12.1.1 and 12.2.2 data model, the table acts as a mapping construct that determines which application functions are available to a given security scheme and which data operation (such as view, create, update, or delete) is permitted for each function. This mechanism underpins the Data Security Scheme (DSS) framework used by Oracle Receivables and related modules to restrict functional access based on user or responsibility classification.

From a Data Vault modeling perspective, the mined FK structure suggests HZ_DSS_SCHEME_FUNCTIONS is satellite-leaning. It carries descriptive attributes (STATUS, audit columns, versioning columns) that qualify the intersection of a security scheme and a form function. The natural hub-like roles are played by the referenced parent objects HZ_DSS_SCHEMES (via SECURITY_SCHEME_CODE) and FND_FORM_FUNCTIONS (via FUNCTION_ID), while HZ_DSS_SCHEME_FUNCTIONS itself functions as the qualifying satellite that records contextual attributes about that relationship.

Key Information Stored

The table is owned by the AR schema and contains 11 documented columns. The most significant columns are:

  • SECURITY_SCHEME_CODE — Business identifier of the data security scheme. Part of the composite primary key and of the unique index HZ_DSS_SCHEME_FUNCTIONS_U1.
  • DATA_OPERATION_CODE — Code indicating the permitted data operation (for example, view, insert, update, delete) that the scheme allows for the function.
  • FUNCTION_ID — Foreign key to FND_FORM_FUNCTIONS, identifying the specific Oracle EBS function being secured.
  • STATUS — Indicates the active or inactive state of the scheme-function association.
  • OBJECT_VERSION_NUMBER — Optimistic locking counter used by the Oracle Application Framework (OAF) to detect concurrent updates.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified the record and from which login.
  • ZD_EDITION_NAME — Editioning column introduced in EBS 12.2 online patching, allowing multiple editions of the same logical row to coexist during an ADOP cycle. It also participates in the unique index HZ_DSS_SCHEME_FUNCTIONS_U1.

The surrogate primary key is defined by HZ_DSS_SCHEME_FUNCTIONS_PK, a composite of SECURITY_SCHEME_CODE, DATA_OPERATION_CODE, and FUNCTION_ID. The unique business-key candidate is expressed by HZ_DSS_SCHEME_FUNCTIONS_U1, which extends the composite key with ZD_EDITION_NAME to accommodate editioning.

Common Use Cases and Queries

Typical scenarios include auditing which functions are exposed by a given security scheme, diagnosing access-related issues reported by users, and reporting on the functional footprint of each scheme for compliance reviews.

A representative query to list the functions associated with a scheme joins HZ_DSS_SCHEME_FUNCTIONS to FND_FORM_FUNCTIONS:

  • SELECT s.SECURITY_SCHEME_CODE, s.DATA_OPERATION_CODE, f.FUNCTION_NAME, s.STATUS FROM HZ_DSS_SCHEME_FUNCTIONS s, FND_FORM_FUNCTIONS f WHERE s.FUNCTION_ID = f.FUNCTION_ID AND s.SECURITY_SCHEME_CODE = :scheme;

A reverse lookup identifies which schemes reference a specific function, useful before disabling or modifying a form function:

  • SELECT SECURITY_SCHEME_CODE, DATA_OPERATION_CODE, STATUS FROM HZ_DSS_SCHEME_FUNCTIONS WHERE FUNCTION_ID = :function_id;

Reporting queries commonly filter on STATUS = 'A' to return only active associations and exclude superseded edition rows by restricting ZD_EDITION_NAME appropriately during ADOP maintenance windows.

Related Objects

  • FND_FORM_FUNCTIONS — Referenced through HZ_DSS_SCHEME_FUNCTIONS.FUNCTION_ID; provides the function name and description for reporting.
  • HZ_DSS_SCHEMES — Parent scheme definition referenced by SECURITY_SCHEME_CODE.
  • HZ_DSS_SCHEME_OBJECTS — Companion table mapping schemes to data objects, often queried alongside this table to obtain a complete scheme definition.
  • HZ_DSS_SCHEME_ROLES — Links schemes to roles and is frequently joined for access analysis.
  • FND_RESPONSIBILITY and FND_USER — Joined indirectly through the DSS role and scheme hierarchy to trace effective user access.
  • FND_APPLICATION — Supplies the application context for functions referenced here.

Together these objects form the DSS access model used by Receivables and shared across EBS modules that enforce data security at the function and object level.