Search Results ja_cn_account_structures_kfv




Overview
Explore in AI Chat

Overview

The JA_CN_ACCOUNT_STRUCTURES_KFV view is a key flexfield (KFF) presentation object owned by the APPS schema in Oracle E-Business Suite. It exposes accounting structure definitions maintained for the Oracle China localization (JA_CN) as a concatenated, human-readable account segment string. In ETRM 12.2.2 the object is registered and VALID, and it belongs to the FND — Application Object Library product grouping, reflecting its role as a descriptive flexfield-style presentation layer rather than a China-specific transactional table.

The "_KFV" suffix indicates a key flexfield view, a pattern Oracle uses to join an underlying structure table to its segment columns and render the account as a delimited concatenation. Because it presents a single combined segment string alongside the individual segments, the view is suited to reporting, data extraction, and integration scenarios where consumers require a flat account representation rather than normalized segment columns. Applications and custom concurrent programs query it by ACCOUNT_STRUCTURE_ID or STRUCTURE_ID to resolve an account structure into its printable form.

Underlying Base Objects

The view is defined over a single documented base object: the synonym JA_CN_ACCOUNT_STRUCTURES, which resolves to the base table of the same name in the APPS schema. The view performs no joins to other tables; all columns are projected directly from the base structure row, with the concatenated and padded account strings derived at runtime through DECODE logic. The ROWID from the base table is passed through, preserving row-level addressability.

Notably, the concatenation logic is conditional on STRUCTURE_ID. When STRUCTURE_ID equals 101, the view builds a three-segment account (SEGMENT1.SEGMENT2.SEGMENT3); when STRUCTURE_ID equals 53279, it builds a two-segment account (SEGMENT1.SEGMENT2). For any other value, the concatenated column evaluates to NULL. This means the view is intentionally scoped to the specific China localization structures it was designed to support.

Key Columns

  • ACCOUNT_STRUCTURE_ID — The primary identifier for the accounting structure record, and the column most frequently used in lookups and join predicates.
  • STRUCTURE_ID — The key flexfield structure identifier that drives the conditional concatenation logic (101 and 53279 are the recognized values).
  • Concatenated segment string — The first derived column renders all non-null segments joined by periods; the second derived column applies LPAD padding (10 characters per segment for 101, 22 for 53279) to produce a fixed-width account string suitable for aligned reporting.
  • SEGMENT1 through SEGMENT10 — The individual account segments exposed both as raw values and, where applicable, as components of the concatenated string; SEGMENT11 through SEGMENT15 are also passed through.
  • ENABLED_FLAG and SUMMARY_FLAG — Standard key flexfield control indicators governing whether the structure is active and whether it represents a summary (parent) account.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating for the structure.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include resolving a stored ACCOUNT_STRUCTURE_ID into a readable account for reporting, validating that a structure is enabled before use, and extracting padded account strings for fixed-format interfaces. Since the view filters effectively on STRUCTURE_ID, queries against unsupported structure IDs will return NULL for the concatenated columns.

Resolve an account by identifier:

SELECT account_structure_id,
       structure_id,
       segment1, segment2, segment3
FROM   apps.ja_cn_account_structures_kfv
WHERE  account_structure_id = :p_id
AND    enabled_flag = 'Y';

List active structures for a known flexfield structure:

SELECT account_structure_id, segment1, segment2
FROM   apps.ja_cn_account_structures_kfv
WHERE  structure_id = 53279
AND    NVL(summary_flag,'N') = 'N'
ORDER  BY account_structure_id;

Because only two STRUCTURE_ID values yield a concatenated result, applications should always check STRUCTURE_ID before consuming the derived account string, and should join back to JA_CN_ACCOUNT_STRUCTURES when columns beyond those projected by the view are required.