Results for “slice_type_flag”

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

Overview

FII_TOP_SPENDERS_V1 is an internal database view belonging to the Financial Intelligence (FII) product family within Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, FII was positioned as an analytical and reporting layer that surfaced summarized financial and expense-related metrics to end users and downstream reporting components. The view is documented as an internal view, meaning it is not intended for direct customer access, extension, or customization; it supports the internal operation of FII reporting features rather than serving as a published integration interface.

The metadata explicitly designates FII as obsolete. This classification carries practical consequences. Oracle no longer develops or supports the FII product line, the object is documented as not implemented in the reference database, and the view therefore exists only in environments where the legacy FII schema objects were originally deployed. In a modern 12.2.2 environment, the object is most likely absent unless retained from an earlier release.

The user's search term "manager_id" aligns directly with the view's purpose. FII_TOP_SPENDERS_V1 ranks individuals by spending activity within the organizational hierarchy defined by manager relationships, making MANAGER_ID the central grouping attribute of the view.

Underlying Base Objects

The ETRM metadata records no documented base objects for this view, and no owner is listed. The view text, however, reveals its single source: a base table named FII_TOP_SPNDR_SUM_B. The "_B" suffix conventionally denotes a base table in Oracle Applications data model naming standards, indicating that this table stores persisted summary data rather than transient calculations. The view is therefore a thin projection over that summary table, exposing a selected subset of its columns.

A notable inconsistency exists between the view text and the documented column list. The SELECT statement references the column PRIM_PTD_G, while the documented columns list presents AMOUNT_G. This discrepancy suggests either an evolution of the underlying table across releases or an error in the documentation set. Consultants should verify the actual column name against the deployed table definition before writing any dependent SQL.

Because the metadata documents no base objects and the view is marked as not implemented, no dependency chain can be confirmed from the ETRM repository alone. Any analysis must fall back to the view text or to database catalog queries such as ALL_DEPENDENCIES.

Key Columns

• PERSON_ID — Identifier of the person whose spending activity is summarized. Typically joins to PER_ALL_PEOPLE_F or a related HR entity.
• PERIOD_ID — The accounting or reporting period to which the summarized amounts apply.
• MANAGER_ID — The manager responsible for the person, forming the hierarchical grouping used for ranking. This is the column most relevant to the user's search.
• RANK_WITHIN_MANAGER_PTD — The person's rank by period-to-date spending within their manager's organization.
• PRIM_PTD_G / AMOUNT_G — The period-to-date amount, expressed in the functional currency. The "_G" suffix indicates a Global/functional currency amount.
• NO_EXP_REPORTS_PTD — Count of expense reports submitted by the person for the period to date.
• SLICE_TYPE_FLAG — A discriminator flag indicating the type of data slice represented by the row, allowing multiple summary perspectives to coexist in one table.

Common Use Cases and Queries

Typical usage centers on identifying high-spending employees and comparing spend across managerial hierarchies.

SELECT person_id, manager_id, period_id,
       rank_within_manager_ptd, amount_g
FROM   fii_top_spenders_v1
WHERE  manager_id = :p_manager_id
AND    period_id  = :p_period_id
ORDER BY rank_within_manager_ptd;

To obtain the top spenders organization-wide for a period:

SELECT person_id, manager_id, amount_g
FROM   fii_top_spenders_v1
WHERE  period_id = :p_period_id
AND    slice_type_flag = :p_slice
ORDER BY amount_g DESC;

Because the view is obsolete and documented as not implemented, any query should first confirm object existence through ALL_VIEWS or ALL_OBJECTS. Where the view is unavailable, equivalent reporting should be sourced from standard Oracle Expense and Oracle Payables reporting tables rather than from FII summary objects.