Search Results cas_number




Overview
Explore in AI Chat

Overview

APPS.GR_DISPATCH_HISTORY_V is a prebuilt Oracle E-Business Suite view owned by the APPS schema and registered in the FND design data repository under the GR (Oracle Process Manufacturing / ETRM — Environmental, Training, and Regulatory Management) product. It exposes the dispatch history records that track when regulatory or safety documents were distributed to internal and external recipients. The view is classified as an internal view type and carries the standard Oracle warning that it is intended for use only by standard Oracle Applications programs; supported external access is not guaranteed, although it is widely queried in custom reports and integrations.

The view is VALID in both Oracle EBS 12.1.1 and 12.2.2 and is especially relevant in the ETRM module, which manages material safety data sheets (MSDS/SDS), labels, and hazardous-communication documentation. Because the view exposes the CAS_NUMBER column, it is frequently the target of searches for "cas_number" — the Chemical Abstracts Service registry number that uniquely identifies regulated substances on dispatched SDS documents.

Underlying Base Objects

The documented view definition references the following base objects in the APPS schema:

  • GR_DISPATCH_HISTORY (synonym) — the primary transactional table holding one row per dispatched document.
  • FND_DOCUMENTS_VL (view) — supplies document code and description via the FND document repository.
  • EDR_FILES_B (synonym) — the EDR (Engineering Data Repository / document file) table providing the stored document content and revision data.
  • HZ_PARTIES and HZ_PARTY_SITES (synonyms) — the TCA (Trading Community Architecture) tables that resolve recipient, addressee, and site details.
  • MTL_SYSTEM_ITEMS_B (synonym) — resolves item and inventory-item identifiers into item numbers.
  • FND_LOOKUP_VALUES (synonym) — decodes value sets such as dispatch method codes.

This join structure means the view offers a denormalized, human-readable picture of each dispatch event, combining the low-level GR transaction with party, item, and document-repository attributes.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing SDS dispatch, proving regulatory distribution, and tracing which CAS-numbered substances were sent to which customers.

  • List all dispatches for a given CAS number:
SELECT dispatch_history_id, cas_number, item, recipient,
       date_sent, dispatch_method_code
FROM   apps.gr_dispatch_history_v
WHERE  cas_number = :p_cas_number
ORDER  BY date_sent DESC;
  • Dispatch volume by recipient and month:
SELECT recipient, TRUNC(date_sent,'MM') sent_month, COUNT(*)
FROM   apps.gr_dispatch_history_v
GROUP  BY recipient, TRUNC(date_sent,'MM');

Because the object is flagged "Oracle Internal Use Only," any custom SQL should be treated as unsupported and validated against the base tables GR_DISPATCH_HISTORY and FND_DOCUMENTS_VL after upgrades to 12.1.1 or 12.2.2.