Search Results report_region_code

Overview

BIS_GRANTS_V is an APPS-owned, VALID database view shipped as part of the BIS (Applications BIS) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to expose grants that define how end users gain access to report regions delivered through Oracle's Application BIS reporting infrastructure. In practical terms, the view joins the EBS grants model (FND_GRANTS and FND_OBJECTS) with the form-function and menu structures (FND_FORM_FUNCTIONS and FND_MENU_ENTRIES) and correlates those with region metadata supplied by BIS through the AK region extension mechanism (BIS_AK_REGION_ITEM_EXTENSION).

When a report region is secured or personalized for a specific user, the association between that user, the role (menu), and the report region is persisted in FND_GRANTS. The BIS_GRANTS_V view flattens and labels these rows so that the report region code, represented by the alias REPORT_REGION_CODE, becomes directly available for reporting, troubleshooting, and entitlement review. This makes it the primary reference point for answering the question of which users hold which report-region-level grants, and for reconciling those grants against the functions and menus that expose them.

Underlying Base Objects

The view text documents four base objects, although ETRM metadata records no separately listed referenced base objects. They are:

• FND_FORM_FUNCTIONS (aliased F) — source of FUNCTION_ID and FUNCTION_NAME, used to identify the executable or function tied to a menu entry.
• FND_MENU_ENTRIES (aliased ME) — links MENU_ID to FUNCTION_ID and therefore connects roles to functions.
• FND_GRANTS (aliased FG) — the grant itself, supplying GRANTEE_KEY, MENU_ID, INSTANCE_PK1_VALUE, PARAMETER1, the audit columns, and the STRING keys GRANTEE_TYPE, INSTANCE_TYPE, PROGRAM_NAME, and OBJECT_ID.
• BIS_AK_REGION_ITEM_EXTENSION (aliased AKRIE) — supplies the REGION_CODE and the ATTRIBUTE24 column, which stores the comma-delimited list of function names associated with a region.
• FND_OBJECTS — referenced only in the subquery on OBJECT_ID with OBJ_NAME = 'HRI_PER', restricting grants to the human-resources person object.

The joins require ME.MENU_ID = FG.MENU_ID and F.FUNCTION_ID = ME.FUNCTION_ID, and match the region extension to functions using four LIKE patterns against ATTRIBUTE24, allowing the view to attribute a function to a region whether it appears first, middle, or last in the comma-separated list. Fixed predicates restrict the output to GRANTEE_TYPE = 'USER', INSTANCE_TYPE = 'INSTANCE', and PROGRAM_NAME = 'BIS_PMV_GRANTS'.

Key Columns

• GRANTED_TO — the grantee key from FND_GRANTS, i.e. the user receiving the grant.
• ROLE_ID — the menu identifier acting as the role through which the grant is assigned.
• REPORT_REGION_CODE — the region code from BIS_AK_REGION_ITEM_EXTENSION; this is the column users search for when the term report_region_code is used.
• GRANTED_FOR — the instance primary key value, identifying the specific instance of the granted object.
• DELEGATION_PARAMETER — the PARAMETER1 value associated with the grant, allowing parameterized delegation.
• START_DATE / END_DATE — the effective window of the grant.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit trail.

Common Use Cases and Queries

Typical usage is entitlement auditing and access troubleshooting for BIS report regions. A common query lists all active report-region grants for a user:

• SELECT granted_to, role_id, report_region_code, granted_for, start_date, end_date FROM apps.bis_grants_v WHERE granted_to = :user_name AND (end_date IS NULL OR end_date > SYSDATE);

Another frequently used pattern determines which users are granted a particular report region, directiing support staff to the identifier found by the report_region_code search:

• SELECT granted_to, role_id, start_date, end_date FROM apps.bis_grants_v WHERE report_region_code = :region_code ORDER BY granted_to;

The view is also used to reconcile grants against menus and functions prior to role redesign, and to detect stale grants by filtering on end_date. Because PROGRAM_NAME and OBJECT_ID are constrained internally, all rows returned represent BIS_PMV_GRANTS grants on the HRI_PER object, which simplifies reporting but means the view should not be used to inspect unrelated FND_GRANTS entries.