Search Results gr_dispatch_history_s

Overview

The APPS.GR_DISPATCH_HISTORY_PVT package body is a private (PVT-classified) PL/SQL implementation object within the Oracle E-Business Suite Process Manufacturing / Enterprise Trade Resource Management (ETRM) module. Its principal responsibility is the maintenance and management of dispatch history records associated with outbound shipments, loads, and delivery documentation. Dispatch history in this context tracks the lifecycle of shipment dispatches, including associated document files, organization and item context, and confirmations generated when goods leave a facility.

The package follows the standard Oracle EBS private API design pattern: the _PVT suffix indicates it is not intended for direct external invocation but is instead called by public wrapper packages, concurrent programs, or internal workflow logic. It is documented as VALID in the ETRM 12.2.2 repository and is referenced by two other database packages, confirming its role as a shared internal utility.

Key Procedures and Functions

Four documented procedures and functions are exposed within this package body:

• CREATE_DISPATCH_HISTORY_REC — The principal write procedure. It inserts a new row into the GR_DISPATCH_HISTORY table, capturing the dispatch event details for a given shipment, load, or document. This is the core transaction handler of the package.
• GET_CAS_NO — A retrieval function that returns the CAS (Chemical Abstracts Service) number associated with an item. This supports regulatory and hazardous-material documentation requirements for dispatched goods.
• GET_ORGANIZATION_CODE — A lookup function returning the organization code for a given inventory organization, derived from MTL_PARAMETERS. Used to populate dispatch records with consistent organizational identifiers.
• GET_ITEM_DESC — A retrieval function that returns the descriptive text for an inventory item, sourced from MTL_SYSTEM_ITEMS_KFV (the key flexfield view). This supports human-readable dispatch documentation.

No parameter lists are documented in the available metadata, and none should be assumed.

Tables Accessed

The package references the following tables through APPS synonyms:

• GR_DISPATCH_HISTORY and GR_DISPATCH_HISTORY_S — the primary data and sequence objects holding dispatch records.
• GR_UPLOAD_FILE_TMP — a temporary staging table used when dispatch data arrives via file upload or interface.
• EDR_FILES_B — the EDR document files base table, linking dispatch events to stored document files.
• FND_DOCUMENTS, FND_DOCUMENTS_VL, and FND_DOCUMENT_CATEGORIES — Oracle Applications document management tables used to attach and categorize dispatch documentation.
• MTL_PARAMETERS — inventory organization parameters supplying organization code context.
• MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV — item master and its descriptive flexfield view for item description and CAS lookup.
• FND_USER, FND_LANGUAGES, and DUAL — supporting reference objects for user identity, language-specific text, and singleton queries.

Usage Notes

Because this is a private package, it is not intended for direct invocation from custom code. It is typically called from public APIs or concurrent programs within the ETRM/Process Manufacturing dispatch flow. The dependencies on FND_API, FND_MSG_PUB, FND_PROFILE, and FND_MESSAGE indicate standard error-handling and message-stack behavior, so callers should check the message stack after execution. Dependencies on FND_CONCURRENT and FND_REQUEST suggest the package may submit or interact with concurrent requests, likely for document generation or interface processing. Given its reliance on document management and file tables, it is most active during dispatch confirmation, document attachment, and shipment documentation workflows. Customizations should target the public wrapper rather than this private body.