Search Results isc_edw_book_sum1_fstg

Overview

ISC_EDW_BOOK_SUM1_FSTG is a staging table within the Oracle Supply Chain Intelligence (ISC) product family, historically delivered as part of the Oracle E-Business Suite data warehouse and analytics layer. The ISC module was positioned as a supply chain intelligence application that consolidated transactional data from order management, shipping, and fulfillment into aggregated, dimensional structures suitable for analytical reporting. This particular object functions as a first-stage (FSTG) staging table that temporarily holds booking summary records prior to their transformation, validation, and load into downstream fact and dimension tables.

The table belongs to the ISC schema and carries a documented physical footprint of 76 columns in the ETRM 12.1.1 release. Notably, the ETRM metadata classifies ISC - Supply Chain Intelligence as obsolete, and the specific record carries the annotation "Not implemented in this database." This indicates that the object may exist as a residual dictionary definition from an optional or retired ISC installation, rather than as an actively used table in a standard EBS 12.1.1 or 12.2.2 environment.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is "standalone," with a single documented relationship to CS_SYSTEMS_ALL_B_TEMP via the ROW_ID column. The table's dimensional-key pattern — a cluster of FK/FK_KEY pairs — nonetheless suggests it acts as a loading satellite or transient staging structure that resolves dimensional references before populating a consolidated bookings summary fact.

Key Information Stored

The most significant columns reflect the table's purpose as a bookings summary staging area:

• BOOKINGS_PK — the surrogate primary key of the staging row.
• ROW_ID — a reference key documented as relating to CS_SYSTEMS_ALL_B_TEMP; this is a primary candidate for the table's business-identifier linkage.
• INSTANCE, INSTANCE_FK, INSTANCE_FK_KEY — identify the source instance and support repeated load cycles.
• BOOKED_LIST_AMT_B / _G — booked list amount in base and global currency.
• BOOKED_AMT_B / _G — the booked revenue amount in both currency views.
• SHIPPED_AMT_B / _G, INVOICED_AMT_B / _G, FULFILLED_AMT_B / _G — the corresponding shipped, invoiced, and fulfilled amount measures, each split into base and global currency.
• DATE_BOOKED, DATE_ORDERED, DATE_LATEST_SHIP, DATE_LATEST_FULFILLED — the key date landmarks that define the lifecycle of each summarized order.
• ORDER_NUMBER, HEADER_ID — order identity columns linking back to order management.
• COLLECTION_STATUS, ERROR_CODE, OPERATION_CODE, REQUEST_ID — the standard staging control columns that drive error handling and restart logic.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE25, USER_FK1-5, USER_MEASURE1-5 — extensibility slots for customer-defined dimensions and measures.

A second set of FK/FK_KEY pairs points to DATE_BOOKED, BILL_TO_CUST, SET_OF_BOOKS, OPERATING_UNIT, and CURRENCY_BASE dimensions, indicating that the staging design anticipates a conformed dimensional model.

Common Use Cases and Queries

Because the object is documented as not implemented, direct queries are unlikely to return data in most environments. Nevertheless, reference queries in the ISC staging idiom remain instructive:

• Identifying failed staging rows: SELECT BOOKINGS_PK, ERROR_CODE, REQUEST_ID FROM ISC.ISC_EDW_BOOK_SUM1_FSTG WHERE COLLECTION_STATUS = 'ERROR';
• Reconciling staged booked amounts against the shipped and invoiced measures.
• Auditing collection progress by INSTANCE and REQUEST_ID for a given interface run.

Typical reporting use cases include bookings-to-fulfillment pipeline analysis, currency-balance comparison between BOOKED_AMT_B and BOOKED_AMT_G, and dimensional enrichment through BILL_TO_CUST, OPERATING_UNIT, and SET_OF_BOOKS keys before publication to the target fact.

Related Objects

The documented relationship data names one explicit reference target:

• CS_SYSTEMS_ALL_B_TEMP — referenced by ISC_EDW_BOOK_SUM1_FSTG.ROW_ID, providing the source-system instance context.

Beyond this explicit FK, the column cluster implies downstream dependence on the order management header (HEADER_ID), bill-to customer, set of books, operating unit, and currency dimension tables, plus the standard interface staging framework used throughout ISC. In a functional ISC installation, this table would be populated by a concurrent interface program and consumed by an aggregation or fact-load routine; in obsolete or non-implemented configurations, it should be treated only as a dictionary artifact.