Results for “status_flag”

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

Overview

FII_AR_SALES_CREDITS_D_T is a Financial Intelligence (FII) repository table within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. As documented in the ETRM metadata, its purpose is to store deleted sales credits associated with Oracle Receivables (AR) transactions. Sales credits represent the allocation of revenue and quota credit to individual salespersons attached to transaction lines. When such credit assignments are removed from the operational AR tables, this FII table preserves the deleted records to support historical analysis, audit trails, and reconciliation within the Financial Intelligence data mart. This is consistent with FII's broader role as the EBS financial data warehouse layer, which stages and historizes transactional data extracted from subledgers such as Receivables.

The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. In Data Vault modeling terms, this suggests the table behaves as a satellite: it holds descriptive, time-variant attributes (including deletion and DML state) keyed by a reference to a parent hub or link. The parent reference is the SALESCREDIT_PK foreign key pointing to RA_CUST_TRX_LINE_SALESREPS_ALL. Analysts designing downstream models should treat FII_AR_SALES_CREDITS_D_T as a historical descriptor table rather than a business hub, because its grain is tied to the sales credit record it tracks rather than to an independent business key.

Key Information Stored

The documented physical schema contains eight columns. The most significant are:

• SALESCREDIT_PK — The primary key of the table (FII_AR_SALES_CREDITS_D_T_PK) and simultaneously a foreign key to RA_CUST_TRX_LINE_SALESREPS_ALL. This is the surrogate link back to the operational sales credit record that was deleted.
• STATUS_FLAG — A status indicator describing the processing or lifecycle state of the deleted credit record within FII.
• DML_TYPE — Identifies the nature of the data manipulation event (for example, the insert/delete classification used by FII's change-capture logic to distinguish deleted versus retained rows).
• LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard EBS audit columns recording when and by whom the row was most recently modified.
• CREATION_DATE, CREATED_BY — Standard EBS audit columns recording initial row creation.
• LAST_UPDATE_LOGIN — The login session identifier associated with the last update.

Because SALESCREDIT_PK serves as both primary key and foreign key, it is the sole documented business-key candidate in this metadata; no separate unique index on a non-surrogate business column is provided. The absence of a distinct natural key reinforces the satellite interpretation.

Common Use Cases and Queries

Typical applications include reconstructing the history of sales credit assignments, auditing which salesperson allocations were removed and when, and feeding historical revenue-credit reports in Financial Intelligence dashboards. A frequent pattern joins the deleted-credit table back to its operational parent to recover context:

• Historical sales-credit audit: SELECT d.SALESCREDIT_PK, d.STATUS_FLAG, d.DML_TYPE, d.LAST_UPDATE_DATE FROM FII.FII_AR_SALES_CREDITS_D_T d, optionally joined to RA_CUST_TRX_LINE_SALESREPS_ALL s ON d.SALESCREDIT_PK = s.SALESREP_ID to retrieve the originating transaction line and salesperson.
• Change-capture reconciliation: filtering on DML_TYPE and STATUS_FLAG to isolate rows flagged as deletions, then comparing counts against current Receivables sales-credit volumes for data-quality checks.
• Trend reporting: grouping by LAST_UPDATE_DATE to show credit-removal activity over time by period or user (LAST_UPDATED_BY, CREATED_BY).

These queries should generally be restricted to the FII schema and oriented toward analytical rather than transactional workloads.

Related Objects

The most significant related objects follow from the documented foreign key relationship and the FII surrounding model:

• RA_CUST_TRX_LINE_SALESREPS_ALL — The operational Receivables table holding current sales credit assignments; the primary FK target via SALESCREDIT_PK.
• FII_AR_SALES_CREDITS_D_T_PK — The primary key constraint defining uniqueness on SALESCREDIT_PK.
• RA_CUST_TRX_LINES_ALL — Transaction lines to which sales credits attach, reached through the operational sales-credit table.
• RA_CUSTOMER_TRX_ALL — The parent AR transaction header providing context for reported credits.
• FII AR staging/interface tables and concurrent programs — The FII extraction and historical-load processes that populate this deletion-tracking table.
• AR standard reports and FII financial dashboards — Consumers that rely on historical sales-credit data for revenue and quota analysis.

Together these objects form the chain from the live AR transaction through the sales-credit assignment into the FII historical repository.