Search Results x_read_only_flag

Overview

APPS.FEM_DIM_UTILS_PVT is a private (PVT) PL/SQL package body in the Oracle E-Business Suite Financials Enterprise Territory/Profitability Management (ETRM) family of applications, used across releases 12.1.1 and 12.2.2. The package encapsulates low-level utility logic for managing and validating dimension-related metadata within the ETRM data model, particularly dimensions, dimension attributes, dimension groups, and dimension members. It centralizes reusable routines that other, higher-level ETRM packages and forms depend on, rather than exposing them directly as public APIs. The package is documented with 22 procedures and functions and is referenced by one other package, confirming its role as a supporting utility layer. A distinctive element relevant to the search term "x_read_only_flag" is the package's function Get_Dim_Attr_Req_Flag_Access, which computes whether the Required Attribute Flag (and, by extension, related accessibility or read-only controls) may be updated for a dimension's attributes. The accessibility determination is derived dynamically from member table state, so the read-only behavior of the UI reflects the underlying data rather than being hard-coded.

Key Procedures and Functions

The documented routines fall into several functional clusters:

• Accessibility and security context: GET_DIM_ATTR_REQ_FLAG_ACCESS returns the accessibility of the Required Attribute Flag for a dimension's attributes; GET_DIM_ATTRIBUTE_ACCESS and GET_DIM_ATTRIBUTE_ACCESS_DEL return attribute-level access including delete eligibility; GET_DIM_GROUP_ACCESS and GET_DIM_MEMBER_ACCESS return access rights for groups and members respectively. SET_SECURITY_CONTEXT, SET_SECURITY_DIM_CONTEXT, and SET_NON_SECURITY_CONTEXT, together with SET_NON_SECURITY_DIM_CONTEXT, establish the session-level security and dimension context used by the access functions.
• Member operations: CREATE_COMP_DIM_MEMBER, MEMBER_INSERT_ROW, MEMBER_UPDATE_ROW, and MEMBER_DELETE_ROW handle creation, insertion, update, and deletion of dimension members; GROUP_HAS_MEMBERS determines whether a group is populated; CHECK_UNIQUE_MEMBER enforces member uniqueness; and DO_MEMBER_ADV_SEARCH performs advanced member search.
• Attribute operations: ATTRIBUTE_INSERT_ROW, ATTRIBUTE_UPDATE_ROW, and ATTRIBUTE_DELETE_ROW manage dimension attribute records, while GRP_ATTRIBUTE_VALIDATION validates attribute values against group definitions.
• Diagnostics: The private procedure pd is a development-only debug stub that performs no operation in shipped code.

The logic in Get_Dim_Attr_Req_Flag_Access illustrates the utility pattern: it reads the base member table name from FEM_XDIM_DIMENSIONS, dynamically counts members, and returns an access flag that effectively governs whether an attribute flag is read-only or editable.

Tables Accessed

The package reads and writes the core ETRM metadata tables via APPS synonyms:

• Dimension metadata: FEM_DIMENSIONS_B, FEM_DIM_ATTRIBUTES_B, FEM_DIM_ATTR_GRPS, FEM_XDIM_DIMENSIONS (source of member_b_table_name and dimension definitions).
• Member and attribute data: FEM_ACTIVITIES, FEM_ACTIVITIES_S, FEM_COST_OBJECTS, FEM_COST_OBJECTS_S, FEM_PRODUCTS_ATTR, FEM_CAL_PERIODS_ATTR, FEM_COL_POPULATION_TMPLT_B, FEM_COND_DIM_CMP_DTL.
• Supporting and control tables: FEM_LEDGERS_B, FEM_DHM_METADATA_OPS_KEY_S, and FND_RESPONSIBILITY (used to derive responsibility-based security context).

These tables supply the metadata, member/attribute rows, and responsibility information required for access checks and DML operations.

Usage Notes

FEM_DIM_UTILS_PVT is invoked indirectly rather than by end users. ETRM setup and administration forms call its member and attribute DML routines when users create or modify dimensions, members, and attributes, and the access functions drive dynamic read-only and enable/disable behavior in those forms. The procedure is also called from other ETRM PL/SQL packages (one documented referrer), typically within the same session after a security context has been established. Because it is a private package, customization should avoid direct invocation; instead, use the supported public ETRM APIs. Note the 12.1.1 header references a 120.21.12010000.3 build dated 2008, relevant when reviewing cross-release compatibility in 12.1.1 and 12.2.2.