Results for “get_display_name”

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

Overview

APPS.HZ_DSS_UTIL_PUB is a public PL/SQL package body within the Oracle EBS Trading Community Architecture (TCA) / Data Security and Subledger (DSS) framework. Its principal responsibility is to evaluate and enforce Data Security (DSS) rules on HZ (Trading Community) entities, such as parties, party relationships, classifications, and contact points. The package determines which DSS group applies to a given entity, validates whether a record satisfies the criteria defined for that group, and supports secure access to HZ data by Oracle EBS applications. The source header ($Header: ARHPDSUB.pls 120.13.12010000.2 2008/09/17) indicates the object belongs to the AR (Receivables) product family and is maintained under the ARHPDSUB source file. In the context of 12.1.1 and 12.2.2, this utility package operates as a core dependency of the DSS/Data Security enforcement layer used across TCA-consuming modules. The user-supplied search term "DSG XDCCC" aligns with the package's role in DSS Group (DSG) determination and cross-entity criteria checking, reflecting its function in evaluating secured entity criteria.

Key Procedures and Functions

The documented public API exposes seven procedures and functions. Each serves a specific role in the DSS evaluation and context lifecycle:

• TEST_INSTANCE — Evaluates a specific instance against DSS criteria to determine whether the instance satisfies the defined security rules.
• GET_GRANTED_GROUPS — Returns the set of DSS groups granted to a user or entity, forming the basis for access determination.
• DETERMINE_DSS_GROUP — Identifies the DSS group applicable to a given entity or context by matching against configured criteria.
• ASSIGN_DSS_GROUP — Assigns a DSS group to an entity, persisting the association for subsequent security enforcement.
• SWITCH_CONTEXT — Alters the active security context (for example, switching the applicable organization or user context) under which DSS evaluation proceeds.
• GENERATE_PREDICATE — Produces a SQL predicate fragment representing the DSS rules, which is then injected into queries to restrict data visibility.
• GET_DISPLAY_NAME — Retrieves the display name associated with a DSS group or entity for presentation in the user interface.

The package body also declares private helper procedures, including STAMP_CHILD_ENTITIES and a family of check_* functions (check_created_by_module_cr, check_classifications, check_classification_cr, check_relationship_types, check_relationship_type_cr, is_relationship_party, and get_parent_...). These private utilities validate classification, relationship-type, and created-by-module conditions. Notably, check_relationship_types carries a Bug 5687869 reference (Nishant) and takes a relationship_id parameter, while the child-entity stamping routine accepts object primary keys p_object_pk1 through p_object_pk5, allowing DSS rules to be propagated across related entities.

Tables Accessed

The package reads and writes DSS configuration and TCA data through APPS synonyms. It depends on HZ_DSS_CRITERIA (criteria definitions used by DETERMINE_DSS_GROUP and predicate building), HZ_DSS_GROUPS_B (group headers for GET_GRANTED_GROUPS and GET_DISPLAY_NAME), HZ_DSS_ENTITIES and HZ_DSS_SECURED_ENTITIES (entity-to-group mappings and secured entity assignments), and HZ_DSS_SCHEME_FUNCTIONS (functions invoked during criterion evaluation). TCA data tables include HZ_CLASS_CODE_DENORM, HZ_CODE_ASSIGNMENTS, HZ_CONTACT_POINTS, and HZ_LOCATIONS, used by the classification and entity checks. Security and menu metadata is drawn from FND_GRANTS, FND_OBJECTS, FND_OBJECT_INSTANCE_SETS, FND_USER, FND_FORM_FUNCTIONS, and FND_COMPILED_MENU_FUNCTIONS, which tie DSS grants to users, functions, and permission sets. These accesses explain the package's dual role: it validates business entities while consulting function-security metadata to enforce user-level DSS access.

Usage Notes

This package is referenced by 16 other packages, confirming it as a foundational utility within the TCA DSS layer rather than an end-user-callable API. It is typically invoked indirectly from Oracle forms, concurrent programs, and OAF pages that query or display HZ entities, and from other packages that need to determine or enforce DSS group membership. Customizations and extensions should call the public procedures (for example, GET_GRANTED_GROUPS, DETERMINE_DSS_GROUP, or GENERATE_PREDICATE) rather than the private helpers. Because SWITCH_CONTEXT and GENERATE_PREDICATE influence the active security context and generated SQL, callers must ensure context is correctly established and restored to avoid unintended data exposure. Extensions should also respect the DSS setup tables, as incorrect group or criteria configuration will directly affect the predicates generated for secured queries in 12.1.1 and 12.2.2 environments.