Search Results fnd_id_flex_structures_v

Overview

GL_COA_MAPPINGS_V is a General Ledger (GL) view owned by the APPS schema and exposed as a reporting and integration interface within Oracle E-Business Suite 12.1.1 and 12.2.2. It presents chart of accounts (COA) mapping definitions stored in the GL_COA_MAPPINGS base table, resolving the numeric chart of accounts identifiers into the descriptive structure names maintained by the Flexfields infrastructure. Each row represents a single mapping that translates account combinations from a source chart of accounts to a target chart of accounts, together with its effective dating and security attributes.

The view is primarily consumed by concurrent programs, forms, and custom reporting logic that need to enumerate or validate cross-chart-of-accounts mappings without joining directly to the flexfield structure views. Because it encapsulates the join to FND_ID_FLEX_STRUCTURES_V and applies the GL# key flexfield code filter, it presents only General Ledger charts of accounts, shielding callers from the underlying key flexfield mechanics. It also embeds function-based security logic, so query results are automatically filtered according to the responsibilities and privileges of the connected user.

Underlying Base Objects

The view is defined over four documented objects:

• GL_COA_MAPPINGS (SYNONYM) — the primary source of mapping records, supplying the mapping identifier, name, description, effective dates, security flag, and audit columns.
• FND_ID_FLEX_STRUCTURES_V (VIEW) — joined twice, once as FROM_COA and once as TO_COA, to resolve the source and target chart of accounts identifiers into structure names. Both joins are restricted to APPLICATION_ID = 101 (General Ledger) and ID_FLEX_CODE = 'GL#'.
• FND_DATA_SECURITY (PACKAGE) — invoked through CHECK_FUNCTION to evaluate view, use, and modify privileges against the GL_DAS_COA_MAPPING data security object.
• FND_GLOBAL (PACKAGE) — supplies USER_NAME, which is passed to the data security check for the current session.

The join condition links MAP.FROM_COA_ID to the FROM_COA structure's ID_FLEX_NUM and MAP.TO_COA_ID to the TO_COA structure's ID_FLEX_NUM. This reliance on FND_ID_FLEX_STRUCTURES_V explains the frequent association of this view with searches for that flexfield structure view.

Key Columns

• ROW_ID / MAPPING_ID / NAME — the row identifier, the internal COA mapping identifier, and the user-defined mapping name.
• FROM_CHART_OF_ACCOUNTS_NAME / FROM_CHART_OF_ACCOUNTS_ID — the source chart of accounts structure name and its ID_FLEX_NUM.
• TO_CHART_OF_ACCOUNTS_NAME / TO_CHART_OF_ACCOUNTS_ID — the target chart of accounts structure name and its ID_FLEX_NUM.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the active date range governing when the mapping is valid.
• SECURITY_FLAG — indicates whether data security is enforced for the mapping.
• VIEW_PRIVILEGE / USE_PRIVILEGE / MODIFY_PRIVILEGE — derived flags ('Y' or 'N') returned by FND_DATA_SECURITY.CHECK_FUNCTION for the respective GL_DAS_COA_MAPPING_V, _U, and _M security functions.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and DESCRIPTION.

Common Use Cases and Queries

Typical scenarios include listing all mappings between two charts of accounts, identifying active mappings as of a given date, and auditing which mappings the current user may view or modify. The security privilege columns make the view suitable for building permission-aware LOVs and reports.

Sample query listing active mappings with resolved chart of accounts names:

• SELECT mapping_id, name, from_chart_of_accounts_name, to_chart_of_accounts_name, start_date_active, end_date_active, view_privilege, use_privilege, modify_privilege FROM gl_coa_mappings_v WHERE security_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

A second query filters by source and target structures to report a specific conversion path, and a third selects only rows where MODIFY_PRIVILEGE = 'Y' to drive maintenance forms. Because privilege evaluation depends on FND_GLOBAL.USER_NAME and the FND_DATA_SECURITY package, results vary by responsibility and are best tested within the target operating context.