Results for “gl_defas_resp_assign_v”

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

Overview

GL_DEFAS_RESP_ASSIGN_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the join between responsibility-level assignments of Definition Access Sets and the parent Definition Access Set definitions themselves. In the EBS security model, Definition Access Sets control access to segment value definitions and related GL account components, and this view consolidates the responsibility-to-access-set mapping with descriptive attributes from the access set header.

The view is a critical integration and reporting layer for security administrators, audit teams, and technical consultants validating how Definition Access Sets are granted to responsibilities. It is particularly relevant to queries involving the DEFAULT_MODIFY_ACCESS_FLAG, since this column identifies whether a given responsibility is permitted to modify the definitions protected by the associated access set. Because the view is a database object rather than a form-driven interface, it is typically consumed by custom reports, extracts, and diagnostic SQL.

Underlying Base Objects

Per the documented view text, GL_DEFAS_RESP_ASSIGN_V is defined over two synonyms:

• GL_DEFAS_ACCESS_SETS — the parent Definition Access Set definitions, joined on DEFINITION_ACCESS_SET_ID.
• GL_DEFAS_RESP_ASSIGN — the responsibility assignment records that bind a responsibility and application to a Definition Access Set.

The view performs an inner join on DEFINITION_ACCESS_SET_ID, so only assignment rows with a matching access set header are returned. All descriptive columns (DEFAS_ACCESS_SET_NAME, DEFAS) originate from GL_DEFAS_ACCESS_SETS, while assignment, audit, and flag columns originate from GL_DEFAS_RESP_ASSIGN. The view is read-only; DML must target the base tables.

Key Columns

• ROW_ID — the ROWID of the underlying GL_DEFAS_RESP_ASSIGN row, useful for identifying the exact assignment record.
• APPLICATION_ID / RESPONSIBILITY_ID — identify the application and responsibility context of the assignment.
• DEFINITION_ACCESS_SET_ID — foreign key linking the assignment to its access set.
• DEFAS_ACCESS_SET_NAME / DEFAS — the user-friendly and internal identifiers of the Definition Access Set.
• DEFAULT_FLAG — indicates whether the assignment is designated as the default.
• DEFAULT_VIEW_ACCESS_FLAG — whether the responsibility receives view access by default.
• DEFAULT_USE_ACCESS_FLAG — whether use access is granted by default.
• DEFAULT_MODIFY_ACCESS_FLAG — whether modify access is granted by default, directly answering the user's search term.
• STATUS_CODE — lifecycle status of the assignment record.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID) — standard EBS who-columns and concurrent request linkage.
• ATTRIBUTE1–15 and CONTEXT — descriptive flexfield support columns.
• SECURITY_GROUP_ID — supports multi-org security group filtering where applicable.

Common Use Cases and Queries

Typical scenarios include auditing which responsibilities can modify definitions, confirming default access grants after configuration changes, and reconciling access set assignments during cloning or upgrades. A representative query answering the user's search term follows:

• SELECT responsibility_id, application_id, defas_access_set_name, default_modify_access_flag FROM gl_defas_resp_assign_v WHERE default_modify_access_flag = 'Y' ORDER BY responsibility_id;
• SELECT defas_access_set_name, responsibility_id, default_view_access_flag, default_use_access_flag, default_modify_access_flag FROM gl_defas_resp_assign_v WHERE responsibility_id = :resp_id;
• SELECT COUNT(*) FROM gl_defas_resp_assign_v WHERE default_modify_access_flag = 'Y' AND status_code = 'A';

Because the view joins only the two primary tables, it is efficient for direct reporting and does not require invoking the GL responsibilities form. Consultants should remember that access is ultimately governed by the combination of the three default flags, and DEFAULT_MODIFY_ACCESS_FLAG is the most powerful of the three, since it permits alteration of the protected definitions.