Search Results grp_attribute_validation
Overview
FEM_DIM_UTILS_PVT is a private PL/SQL package in the Application Object Library owner schema APPS, part of the Enterprise Territory Management (formerly Territory Manager) / dimension management infrastructure that underpins Oracle E-Business Suite. It provides the utility layer that supports dimension member, dimension attribute, and dimension group maintenance operations, together with the security-context and access-check plumbing required before any such maintenance can proceed. In Oracle EBS 12.1.1 and 12.2.2 the package is catalogued under the FEM (Financials Enterprise Management / dimension) module and is classified as a private (PVT) API, meaning it is an internal implementation unit not intended for direct customer invocation. It is referenced by one other package, which acts as the public-facing front end that calls these utilities.
The package encapsulates two broad responsibilities. The first is access resolution: a family of functions evaluates whether the current user, given responsibility and personal-flag context, may read, update, or delete a given dimension attribute, dimension group, or dimension member. The second is row-level maintenance: procedures that perform the physical insert, update, and delete of dimension members and attributes, along with validation and uniqueness checks.
Key Procedures and Functions
The documented procedures and functions divide into access control, security context, and data maintenance groups.
- GET_DIM_ATTR_REQ_FLAG_ACCESS, GET_DIM_ATTRIBUTE_ACCESS, and GET_DIM_ATTRIBUTE_ACCESS_DEL return whether attribute-level access is permitted, with the DEL variant handling delete-switcher behaviour separately from update logic.
- GET_DIM_GROUP_ACCESS and GET_DIM_MEMBER_ACCESS return access decisions for dimension groups and members; the group function accepts an operation type to distinguish update from delete operations.
- GRP_ATTRIBUTE_VALIDATION validates an attribute against a dimension group.
- SET_SECURITY_CONTEXT, SET_SECURITY_DIM_CONTEXT, SET_NON_SECURITY_CONTEXT, and SET_NON_SECURITY_DIM_CONTEXT establish or clear the security context, optionally scoped to a dimension, before maintenance calls are made.
- MEMBER_INSERT_ROW, MEMBER_UPDATE_ROW, and MEMBER_DELETE_ROW perform row-level DML for dimension members.
- ATTRIBUTE_INSERT_ROW, ATTRIBUTE_UPDATE_ROW, and ATTRIBUTE_DELETE_ROW perform the equivalent row-level DML for dimension attributes; this is the group containing the searched identifier attribute_insert_row.
- CREATE_COMP_DIM_MEMBER creates a composite dimension member using the standard FND_API error-handling conventions.
- DO_MEMBER_ADV_SEARCH, GROUP_HAS_MEMBERS, and CHECK_UNIQUE_MEMBER support advanced member search, group membership testing, and uniqueness validation.
Tables Accessed
The package reads and writes the core dimension and territory data model through APPS synonyms. FEM_DIM_ATTRIBUTES_B and FEM_DIM_ATTR_GRPS back attribute and attribute-group maintenance. FEM_DIMENSIONS_B and FEM_XDIM_DIMENSIONS hold dimension definitions. FEM_COST_OBJECTS and FEM_COST_OBJECTS_S store member and cost-object records, while FEM_ACTIVITIES and FEM_ACTIVITIES_S cover activity-based members. FEM_CAL_PERIODS_ATTR, FEM_PRODUCTS_ATTR, and FEM_COND_DIM_CMP_DTL support attribute and condition detail handling. FEM_COL_POPULATION_TMPLT_B and FEM_DHM_METADATA_OPS_KEY_S support population templates and metadata operations keys. FEM_LEDGERS_B supplies ledger context, and FND_RESPONSIBILITY is consulted for responsibility-based security resolution.
Usage Notes
Because FEM_DIM_UTILS_PVT is a private package, it is not registered as a public API and should not be called from custom code. It is invoked indirectly by the single referencing package, and in practice is exercised through the Oracle Forms-based dimension and territory administration screens, where attribute and member edits trigger the access checks and the ATTRIBUTE_INSERT_ROW and MEMBER_INSERT_ROW routines. Security context setup procedures must be called before maintenance routines so that access decisions are correctly evaluated. Custom integrations should use the supported public dimension APIs rather than this private utility layer.