Results for “gl_id_unearned”

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

Overview

FIIBV_AR_ARTT_TYPE_LCV is a Financial Intelligence (FII) base view that exposes the Receivables transaction type level of the AR Transaction Type dimension. It is a foundational building block within Oracle's Enterprise Data Warehouse / ETRM reporting layer, intended to feed dimension and hierarchy construction rather than to be queried directly by end users. The view's name follows the FII convention: "AR" denotes Receivables, "ARTT" denotes AR Transaction Type, and "LCV" indicates a level or consolidated view used within the dimensional model. FII as a product is documented as obsolete in this release, which means the view is retained for backward compatibility with existing ETRM/EDW materialized views, mappings, and dashboards rather than being an actively extended object. Note the metadata states "Not implemented in this database," indicating the definition exists in the repository but is not physically present in the current instance.

Underlying Base Objects

The view is defined over a single base table, RA_CUST_TRX_TYPES_ALL, aliased as CTT. This is the multi-org (org-striped) customer transaction types table in Oracle Receivables, holding both seeded and user-defined transaction types. Although the view text references EDW_INSTANCE.GET_CODE, a warehouse helper function used to stamp the source instance identifier, the documented referenced base object list is otherwise limited to RA_CUST_TRX_TYPES_ALL. The transaction type ID is concatenated with ORG_ID and the instance code to form a surrogate key, ensuring uniqueness across operating units and source instances. The design follows the standard FII pattern of deriving warehouse-level dimensional attributes from a transactional seed table while preserving operational columns for drill-down.

Key Columns

• TRX_TYPE_PK — Surrogate primary key built as CUST_TRX_TYPE_ID || '-' || ORG_ID || '-' || SUBSTR(EDW_INSTANCE.GET_CODE,1,40).
• TRX_CODE_FK / TYPE — The transaction type code used for joining to fact tables.
• TRX_TYPE_DP / NAME — Descriptive name of the transaction type for display in reports.
• TRANSACTION_TYPE — Repeated NAME column serving as the transactional label.
• ALLOW_FRT_FLAG, ALLOW_OVAPP_FLAG — Freight and overapplication allowances.
• CREATION_SIGN, DEFAULT_STATUS — Sign (debit/credit) and default status of the transaction type.
• GL_ID_CLEARING, GL_ID_FREIGHT, GL_ID_REC, GL_ID_REV, GL_ID_TAX, GL_ID_UNBILLED, GL_ID_UNEARNED — Account assignment identifiers for accounting integration.
• ORG_ID, SET_OF_BOOKS_ID — Multi-org and set of books context.
• START_DATE, END_DATE — Effective dating for the transaction type.
• INSTANCE — Source instance code from EDW_INSTANCE.GET_CODE.
• LAST_UPDATE_DATE — Change tracking for incremental loads.
• _DF:RAT:_EDW, _DF:JGT:_EDW — Data definition markers tying the view to ETRM extract and join metadata.

Common Use Cases and Queries

Because the view is obsolete and not implemented, production queries typically target the underlying table directly. When the view is present, it is used in ETRM mappings and dimensional loaders to populate AR Transaction Type dimension records with consistent surrogate keys and account mappings across operating units. A representative query for drill-down reporting would be:

SELECT trx_type_pk,
       trx_code_fk,
       name,
       transaction_type,
       default_status,
       org_id,
       set_of_books_id
  FROM fiibv_ar_artt_type_lcv
 WHERE org_id = :p_org_id
   AND status = 'A';

Analysts use these attributes to group AR transactions by type, compare debit versus credit creation signs, and reconcile GL assignments against accounting rules. Because FII is obsolete in 12.1.1 and 12.2.2, new implementations should migrate equivalent logic to supported AR and BI Publisher sources.