Results for “extract_status_code”

5 results




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

Overview

FII.FII_FA_NEW_EXP_CJE_IDS is a transactional staging table within the Oracle E-Business Suite Financial Intelligence (FII) product family. Its documented purpose is to hold the new identifiers for Assets journal submissions that have not yet been extracted into the base summary. In practical terms, the table functions as an inbound queue for Asset-related journal entry identifiers, consumed by the Financial Intelligence extraction and summarization processes in Oracle EBS 12.1.1 and 12.2.2. Each row represents a journal submission that is known to the source Assets subledger but is not yet reflected in the FII base summary structures, allowing incremental extraction logic to identify only the newly arrived work.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault style model. That classification is best treated as a modeling suggestion rather than a strict schema assertion: because the table carries two foreign keys but does not itself serve as a join table between two hubs, it does not map cleanly to a link; it behaves more like a transient satellite or staging construct around the Assets journal entry hub. Its lifecycle is short — rows are typically purged or flagged once extraction has completed.

Key Information Stored

The table is documented with ten columns in the 12.1.1 physical schema. The most significant are:

  • CJE_EXP_ID — Foreign key to FII_FA_EXP_CJE_IDS; links the new identifier to the parent extracted-journal identifier record.
  • CJE_ID — Foreign key to FA_JOURNAL_ENTRIES; the actual Assets journal entry identifier awaiting extraction.
  • BOOK_TYPE_CODE — The Assets book (for example, a corporate or tax book) to which the journal entry belongs, a key business attribute for reporting and book-scoped extraction.
  • PERIOD_COUNTER — The accounting period identifier associated with the submission, used to scope extraction by period.
  • EXTRACT_STATUS_CODE — The processing state of the row, indicating whether extraction into the base summary has occurred. This is the principal control column for the queue.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording insertion.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification.

No surrogate primary key or unique business index is documented in the ETRM excerpt; the effective business key is the combination of CJE_EXP_ID, CJE_ID, BOOK_TYPE_CODE, and PERIOD_COUNTER. The two documented foreign keys define the referential integrity of the table.

Common Use Cases and Queries

Typical usage centers on monitoring and troubleshooting the Assets extraction pipeline. A common query identifies pending journal submissions by book and period:

SELECT n.CJE_ID, n.BOOK_TYPE_CODE, n.PERIOD_COUNTER, n.EXTRACT_STATUS_CODE
FROM FII_FA_NEW_EXP_CJE_IDS n
WHERE n.EXTRACT_STATUS_CODE = 'N'
ORDER BY n.CREATION_DATE;

Joining to the Assets journal table validates the source entry and supplies descriptive context:

SELECT n.CJE_ID, j.*
FROM FII_FA_NEW_EXP_CJE_IDS n, FA_JOURNAL_ENTRIES j
WHERE n.CJE_ID = j.JE_HEADER_ID;

Other scenarios include confirming whether a submission has been swept into the base summary, measuring extraction latency by comparing CREATION_DATE to LAST_UPDATE_DATE, and reconciling row counts by PERIOD_COUNTER against the base summary during period close. Backlog investigation and stale-row cleanup rely heavily on EXTRACT_STATUS_CODE and the audit columns.

Related Objects

The following objects are most significant in relation to this table, based on the documented foreign keys and FII/Assets domain context:

  • FII_FA_EXP_CJE_IDS — referenced via FII_FA_NEW_EXP_CJE_IDS.CJE_EXP_ID; the parent extracted-journal identifier table.
  • FA_JOURNAL_ENTRIES — referenced via FII_FA_NEW_EXP_CJE_IDS.CJE_ID; the Oracle Assets journal entry source.
  • FII_FA_EXP_CJE_DTLS — journal entry detail extraction rows covering the same Assets submissions.
  • FII_FA_BASE_SUMMARY and related FII base summary tables — the extraction target populated from this queue.
  • FA_BOOK_CONTROLS — source of BOOK_TYPE_CODE context for book validation and period status.
  • FII extraction concurrent programs (journal submission and base summary load requests) that read and update this table.

Because the table is a narrow staging queue, its dependencies are limited to those listed above; direct application API access is not documented, and manipulation should be reserved for data repair or remediation under Oracle guidance.