Results for “wms_dock_appointments_v”

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

Overview

The WMS_DOCK_APPOINTMENTS_V view is an APPS-owned database object within the Oracle E-Business Suite Warehouse Management (WMS) module. It serves as the primary data access point for the WMS dock appointment form, presenting a consolidated, language-aware record set describing scheduled dock appointments across warehouse organizations. A dock appointment represents a reserved time window at a specific dock, used to coordinate inbound and outbound carrier arrivals and to sequence warehouse labor and staging resources.

Because it is a view rather than a table, WMS_DOCK_APPOINTMENTS_V delivers a denormalized, read-optimized projection of the underlying dock appointment entity. It is intended for reporting, form-based inquiry, and integration scenarios where consumers require both the transactional appointment attributes (dock, organization, time windows, carrier, source document linkage) and the user-facing descriptive text (subject and description) in a single query. The view is listed as VALID in the ETRM metadata, indicating that its defining SQL resolves correctly against the referenced synonyms in the APPS schema for the documented 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The view is defined over two base objects, both referenced through synonyms in the APPS schema:

• WMS_DOCK_APPOINTMENTS_B — the base table holding the transactional and operational appointment data, joined on DOCK_APPOINTMENT_ID.
• WMS_DOCK_APPOINTMENTS_TL — the translation table holding the SUBJECT and DESCRIPTION attributes, joined on DOCK_APPOINTMENT_ID and filtered by T.LANGUAGE = USERENV('LANG').

The join between the two tables is an equi-join on the DOCK_APPOINTMENT_ID primary/foreign key relationship. The language filter uses the session's LANG environment value, which means the view automatically returns subject and description text in the language of the querying session — a standard EBS multilingual ("_TL") design pattern. The _B suffix denotes the base transactional table; the _TL suffix denotes the translated attributes table.

Key Columns

• DOCK_APPOINTMENT_ID — unique identifier of the dock appointment; the join key between the base and translation tables.
• APPOINTMENT_TYPE — classifies the appointment (for example, distinguishing inbound, outbound, or related appointment categories). This is the column most frequently targeted by the search term "appointment_type".
• DOCK_ID — identifies the dock at which the appointment is scheduled.
• ORGANIZATION_ID — the warehouse organization that owns the appointment.
• START_TIME / END_TIME — the scheduled window for the appointment.
• CARRIER / CARRIER_CODE — the carrier associated with the appointment.
• SOURCE_TYPE, SOURCE_HEADER_ID, SOURCE_LINE_ID — identify the source document and line from which the appointment was generated.
• TRIP_STOP — the trip stop reference for transportation planning.
• REP_START_DATE, REP_END_DATE, REP_ORIGIN, REP_FREQUENCY — attributes describing recurring appointment patterns.
• APPOINTMENT_STATUS — the current lifecycle status of the appointment.
• STAGING_LANE_ID — the staging lane associated with the appointment.
• SUBJECT / DESCRIPTION — translated descriptive text sourced from the _TL table.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit ("WHO") columns.

Common Use Cases and Queries

The view is commonly used to review scheduled dock activity by organization, to report on appointment volumes by type or status, and to expose dock appointment detail to downstream integrations. A typical query filtering by appointment type and organization might read:

SELECT dock_appointment_id,
       appointment_type,
       dock_id,
       organization_id,
       start_time,
       end_time,
       carrier,
       appointment_status,
       subject,
       description
FROM   apps.wms_dock_appointments_v
WHERE  organization_id = :org_id
AND    appointment_type = :appointment_type
AND    start_time BETWEEN :from_date AND :to_date
ORDER BY start_time;

Because the view filters on USERENV('LANG'), no additional language predicate is required by the caller. When joining the view to other WMS or shipping tables, restrict results with the ORGANIZATION_ID and START_TIME predicates to maintain performance. All queries should be executed with the APPS schema or an equivalent synonym context, as the object is owned by APPS.