Search Results emp_cc

Overview

FII_BIS_FARSP_V is an internal Oracle EBS 12.1.1 / 12.2.2 view that belongs to the FII (Financial Intelligence) product family. Its documented purpose is to support Asset Responsibility PM Viewer Reports, a class of FII reporting output that associates fixed asset records with the responsibility assigned to individual employees. The view is not exposed through a standard concurrent program interface; ETRM describes it as internal, meaning it exists to feed downstream report or publisher logic rather than to be invoked directly by end users.

The defining characteristic of the view is dynamic key flexfield resolution. Rather than emitting all segments of a chart of accounts combination, it selects the single segment dictated by the accounting flexfield structure mapped to a given asset book type. This is achieved by calling FII_BIS_FADST_PKG.GET_ACCT_FLEX_SEG, which returns a value such as 'SEGMENT1' through 'SEGMENT30' depending on the book. The DECODE ladder then maps that returned segment identifier to the corresponding column in the underlying accounting flexfield source, producing both an employee-level account combination and a responsibility-level account combination in a normalized, single-column form.

Underlying Base Objects

The ETRM metadata records that FII_BIS_FARSP_V is not implemented in the source database and reports no documented referenced base objects. The view text nevertheless reveals two principal data sources: an employee source supplying EMP.FULL_NAME, and one or more accounting flexfield sources supplying SEGMENT1 through SEGMENT30, aliased here as DHCC and DHCC2. The DECODE logic references both aliases, indicating that the view reconstructs account combinations from two related flexfield contexts, one attributed to the employee and one attributed to the responsibility or book assignment.

Because no base objects are formally documented, DBAs verifying the view in a live instance should query DBA_DEPENDENCIES and DBA_VIEWS to confirm the concrete tables behind the DHCC aliases in that specific installation. The view text is truncated in the ETRM excerpt, and additional joins and filters may exist beyond the visible portion.

Key Columns

• EMPLOYEE — the full name of the employee associated with the asset responsibility, sourced from EMP.FULL_NAME.
• EMP_CC — the employee's account combination, expressed as the single flexfield segment returned by FII_BIS_FADST_PKG.GET_ACCT_FLEX_SEG for the relevant book type. The trailing '%' fallback in the DECODE indicates that when the segment name is not recognized, a wildcard is returned rather than a specific segment value.
• Responsibility account segment — derived from the DHCC alias through the same DECODE pattern, supplying the account combination for the responsibility side of the report.
• Book type context — BC.BOOK_TYPE_CODE, which drives the package call and determines which flexfield segment is projected for both account columns.

The repeated SEGMENT1–SEGMENT30 branches confirm support for accounting flexfields configured with up to thirty segments, accommodating enterprise structures across the range of Oracle EBS 12.1.1 and 12.2.2 chart of accounts designs.

Common Use Cases and Queries

The primary use case is sourcing data for the Asset Responsibility PM Viewer report. A typical query retrieves the employee-to-account mapping for a reporting period:

• SELECT employee, emp_cc FROM fii_bis_farsp_v;
• SELECT employee, emp_cc FROM fii_bis_farsp_v WHERE emp_cc = :account_segment_value;
• SELECT employee, emp_cc, responsibility_segment FROM fii_bis_farsp_v ORDER BY employee;

The user query term "default_code_comb_id" does not appear within the FII_BIS_FARSP_V text. That column name belongs to fixed asset and account generator contexts elsewhere in Oracle Assets, and searches combining the two terms typically reflect an attempt to reconcile an asset's default code combination with the responsibility account derived by this view. Because the view resolves segments dynamically rather than exposing a code_combination_id numeric key, it cannot be joined directly on default_code_comb_id; reconciliation must instead be performed on the concatenated segment values produced by the DECODE logic.