Results for “fnd_functions”

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

Overview

POS_DATA_SECURITY is an internal Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM as an "OTHER" API type. Its business purpose is to resolve and assemble the data-security context that governs how a given user or party may access records in Oracle Point of Sale and closely related Oracle Trade Management / Oracle Advanced Pricing flows. Rather than acting as a public, generally reused API, the package is designed as a supporting utility that computes privilege and visibility information used by other POS components. The package is referenced by one other package in the ETRM dependency graph, confirming its role as a subordinate helper rather than a directly invoked application interface. In Oracle EBS 12.1.1 and 12.2.2, this kind of security package is essential to enforcing operating unit, party, and grant-based access rules, and it relies heavily on the foundation (FND) and Trading Community (HZ) data models to derive those rules at runtime.

Key Procedures and Functions

The ETRM metadata documents a single public routine for this package body: GET_PRIVILEGES_PROSP. Based on its naming and the package's security role, this function is intended to return the set of privileges applicable to a prospect or prospective customer record, determining what the calling session is permitted to view or act upon. The remainder of the package body consists of internal (spec-private) helper functions that are not part of the package specification. These include GET_OBJECT_ID, which resolves a functional object name to its numeric OBJECT_ID using FND_OBJECTS; GET_GROUP_INFO, which builds a delimited list of active membership relationships (RELATIONSHIP_CODE = 'MEMBER_OF') for a given party by querying HZ_RELATIONSHIPS; and GET_COMPANY_INFO, which returns company-level context for a party. GET_GROUP_INFO returns a formatted string of group identifiers and falls back to the literal 'NULL' when no active, date-valid membership exists.

Tables Accessed

Through APPS synonyms, POS_DATA_SECURITY reads from five documented tables. FND_OBJECTS supplies the object identifiers used to map internal object names to the security framework. FND_GRANTS is the core grants repository that defines which users or roles hold which privileges, and it underpins the privilege resolution performed by GET_PRIVILEGES_PROSP. FND_USER provides the application user identity against which grants and privileges are evaluated. HZ_RELATIONSHIPS stores party-to-party relationships, allowing the package to determine group memberships and organizational associations (for example, membership and company information). PLITBLM is an Oracle-supplied PL/SQL index-by table type used for in-memory collections within the package logic. The package is read-oriented; the documented evidence indicates it queries these tables to compute security context rather than maintaining application data.

Usage Notes

POS_DATA_SECURITY is typically invoked indirectly. Because it is registered as an "OTHER" API and referenced by another package, callers normally reach it through that dependent POS package rather than calling GET_PRIVILEGES_PROSP directly. In practice, it executes during user-facing operations such as opening a Point of Sale or Trade Management form, running security-filtered queries, or executing concurrent programs that must restrict records to the privileges of the requesting user. Developers performing customizations or extensions should treat the internal helper functions as unsupported and rely only on GET_PRIVILEGES_PROSP. The user search term "fnd_functions" reflects the common pattern of resolving FND security metadata; note that this package resolves objects through FND_OBJECTS and privileges through FND_GRANTS and FND_USER, which are the relevant foundation tables for this access model. Any customization should account for the fact that group and company resolution depends on date-effective HZ_RELATIONSHIPS rows.