Results for “create_history”

50+ results




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

Overview

APPS.CREATE_HISTORY is a PL/SQL package owned by the APPS schema that provides the history-recording logic for Oracle E-Business Suite transportation and logistics processing. Its responsibilities center on the creation and maintenance of historical audit records for shipment activity and booking activity. In the Oracle EBS architecture, packages of this classification (OTHER) act as internal utility or service layers invoked by higher-level APIs, concurrent programs, or form logic rather than as standalone public APIs. CREATE_HISTORY therefore functions as a supporting component that captures state changes and lifecycle events so that downstream reporting, tracking, and audit functions can present an accurate historical view of transportation transactions.

The package is documented as VALID in the APPS schema under the ETRM (E-Business Suite Technical Reference Manual) metadata for release 12.2.2, and is equally applicable to the 12.1.1 code line. It carries a direct dependency on SYS.STANDARD, the standard PL/SQL package, which confirms that the unit is a normal compiled PL/SQL package with a specification and a body.

Key Procedures and Functions

Two program units are documented within the package:

  • SHIPMENT_HISTORY — Responsible for creating and managing historical records associated with shipment transactions. This routine supports the shipment lifecycle by capturing the events and attribute changes that constitute a shipment's audit trail.
  • BOOKING_HISTORY — Responsible for creating and managing historical records associated with booking transactions. It performs the analogous history-recording role for bookings, ensuring that booking-related activity is preserved for tracking and reporting.

The ETRM metadata does not publish detailed parameter lists for these units. Consequently, descriptions here are limited to their documented purpose. Callers should obtain signature details directly from the package specification in the target instance or from the source in the EBS installation media rather than relying on inferred parameters.

Tables Accessed

The ETRM documentation excerpt for CREATE_HISTORY lists no referenced tables through APPS synonyms, and the package specification itself does not enumerate table dependencies. As a result, no table-level access can be asserted from the documented metadata. In practice, a history package of this nature typically inserts into and queries history tables corresponding to its shipment and booking subject areas, but the specific object names are not part of the documented record and should be verified against the package body on the instance. The only confirmed dependency recorded is on SYS.STANDARD.

Usage Notes

CREATE_HISTORY is referenced by the APPS schema itself and, per the documented metadata, is not referenced by any other package. This pattern is characteristic of a leaf-level utility invoked directly by execution-layer components — most commonly Oracle Forms event logic, workflow activities, or concurrent programs that process shipments and bookings — rather than by other PL/SQL APIs. Customizations should treat the package as an internal implementation detail: the documented procedures may be called where history recording is required, but because parameter interfaces are not published in the ETRM, custom code should bind to the actual package specification shipped with the instance. When troubleshooting missing or incorrect history, the first diagnostic step is to confirm that the calling form or concurrent program completes its transaction and commits, since history rows are only persisted on commit of the invoking unit of work.