Results for “customer_fk_key”

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

Overview

The view ISC_RISK_SHIP_DLQT_S belongs to the ISC – Supply Chain Intelligence product family in Oracle E-Business Suite, a module that Oracle has since designated as obsolete. It is a reporting-oriented database object designed to surface open order backlog information at the intersection of shipping status and delivery delinquency. In practice, the view consolidates backlog quantities and monetary values into a single denormalized structure, allowing supply chain analysts and operational planners to assess both how much order value is pending shipment and how much of that backlog has slipped past its promised delivery date.

The suffix "_S" in the view name, consistent across Supply Chain Intelligence reporting objects, typically denotes a summary or staging-oriented view intended for downstream analysis rather than transaction processing. Because the object is a view and not a table, it holds no data of its own; it dynamically derives its result set from an underlying EDW (Enterprise Data Warehouse) foundation table. The view therefore functions as a presentation layer, exposing a curated set of business measures and dimensional keys in a form convenient for BI Publisher reports, Discoverer workbooks, or ad-hoc SQL used by supply chain risk analysts.

Notably, the documented ETRM metadata states that this object is not implemented in the current database. This indicates that in the specific environment referenced by the documentation, the view either was never deployed, has been removed, or applies only to particular ISC release configurations. Consumers referencing the view on a live 12.1.1 or 12.2.2 instance should verify its existence via ALL_VIEWS or DBA_VIEWS before relying on it in production queries.

Underlying Base Objects

The view text defined in the ETRM metadata shows that ISC_RISK_SHIP_DLQT_S is constructed entirely from a single source object: ISC_EDW_BACKLOG_SUM1_F. The suffix "_F" indicates a fact table within the Oracle Supply Chain Intelligence data warehouse schema, and the name "BACKLOG_SUM1" suggests it is the primary backlog summary fact, aggregated at a defined grain — most likely operating unit, customer, and order header.

The view performs no joins, unions, or filters. It is a straightforward projection with column renaming and NVL-based defaulting applied to the numeric measures. This design confirms its role as a convenience layer: rather than requiring report developers to know the internal column names of the EDW fact table, the view presents business-friendly aliases while guaranteeing that null measures are returned as zero, avoiding arithmetic errors in aggregations.

Because the view is defined over an EDW fact object rather than over the transactional Order Management tables (such as OE_ORDER_HEADERS_ALL or WSH_DELIVERY_DETAILS), its freshness depends on the ETL process that populates the Supply Chain Intelligence warehouse. Data latency between the operational system and this view is therefore expected and must be accounted for in reporting cycles.

Key Columns

• OPER_UNIT_FK_KEY — Foreign key to the operating unit dimension, enabling multi-org reporting segmentation.
• CUSTOMER_FK_KEY — Foreign key to the customer dimension; the join key underlying the user's customer_name search interest.
• CUSTOMER_NAME — The denormalized customer name, allowing reports to display customer identity without an explicit dimension join.
• ORDER_NUMBER — The order number associated with the backlog summary record.
• BOOKED_DATE — The date the order was booked, aliased from DATE_BOOKED in the underlying fact.
• SHIP_BKLG_LINE_COUNT and SHIP_BKLG_AMT_G — Count of lines and monetary value of backlog pending shipment (functional currency).
• DLQT_BKLG_LINE_COUNT and DLQT_BKLG_AMT_G — Count of lines and monetary value of backlog that is delinquent relative to promised dates.
• DAYS_OPEN — Number of days the order has remained open.
• MAX_DAYS_LATE — The greatest number of days any line in the record is past due.
• HEADER_ID — Internal order header identifier, useful for drill-through to transactional detail.

Common Use Cases and Queries

A typical use case is identifying customers with the largest delinquent backlog value, which supports escalation and customer-service prioritization:

• Backlog by customer: SELECT customer_name, SUM(ship_bklg_amt_g), SUM(dlqt_bklg_amt_g) FROM isc_risk_ship_dlqt_s GROUP BY customer_name ORDER BY 3 DESC;
• Aged delinquency review: SELECT order_number, customer_name, days_open, max_days_late FROM isc_risk_ship_dlqt_s WHERE max_days_late > 30;
• Operating-unit comparison: grouping by oper_unit_fk_key to compare shipment backlog and delinquency ratios across organizations.

Because the object is documented as not implemented in the reference database and belongs to an obsolete module, administrators on 12.1.1 or 12.2.2 should confirm availability and consult the corresponding EDW fact table directly if the view is absent.