Search Results get_org_organization_info

Overview

FTE_WSH_INTERFACE_PKG is an Oracle EBS application programming interface package owned by the APPS schema. Its primary responsibility is to broker changes between the Oracle Transportation Management (OTM) or Fleet Transportation Management execution layer and the Warehouse Management (WSH) shipping and trip data model. The package exposes a set of change-notification procedures that respond to events occurring on trips, trip segments, and trip stops, propagating the resulting data into the shipping tables that drive deliveries, delivery legs, and delivery details. It is a mechanism for synchronizing transportation execution events with the WSH delivery structures inside EBS.

The package header carries a legacy RCS identifier of $Header: FTEWSHIS.pls 120.1 2005/06/03, reflecting its origins in the FTE (Freight/Transportation Execution) product line that was later reconciled with WSH. The API classification in ETRM 12.2.2 is listed as OTHER, indicating that it does not fall under the standard PL/SQL API family conventions such as process_order or create_order, but instead serves as an event handler for change notifications. It defines a small set of record types — tripSegmentChangeInRecType, tripSegmentChangeOutRecType, segmentStopChangeInRecType, and segmentStopChangeOutRecType — plus action-type constants (G_ADD, G_UPDATE, G_DELETE, G_NO_CHANGE, G_TRIP_SEGMENT_DELETE) that classify the nature of each change passed into the procedures.

Key Procedures and Functions

The documented interface exposes three callable units, all procedures. No parameter lists are reproduced here; only the documented purpose of each is described.

• trip_segment_change — Handles addition, update, or deletion of a trip segment. The caller supplies the prior and revised trip records together with an inbound change record that carries the action type. The procedure processes the change and returns an outbound record, a return status, message count, and message data consistent with the FND API error-handling convention.
• segment_stop_change — Processes changes to individual stops within a trip segment. It accepts the current trip record, the old stop record, and the corresponding new stop record, along with the standard FND API control and status parameters. This allows stop-level edits to be reflected in the trip stop data.
• get_org_organization_info — The function the searcher requested. It retrieves organization information, reading from the HR organization information structures to resolve the operating unit or organization context under which transportation and shipping activity is performed. This context is typically required so downstream trip and delivery updates are written against the correct organization.

Tables Accessed

The package references a broad set of tables through APPS synonyms, spanning the FTE and WSH domains. FTE_TRIPS and FTE_WSH_TRIPS hold the FTE-side trip representations that participate in the change events. The WSH tables — WSH_TRIPS, WSH_TRIP_STOPS, WSH_NEW_DELIVERIES, WSH_DELIVERY_LEGS, and WSH_DELIVERY_DETAILS — represent the shipping delivery structures updated as trip, segment, and stop changes propagate. HR_ORGANIZATION_INFORMATION supplies organization-level attributes used by get_org_organization_info. FND_PRODUCT_GROUPS provides installation and product-group context. DUAL and PLITBLM are used for scalar selection and for message/error plumbing respectively.

Usage Notes

FTE_WSH_INTERFACE_PKG is not typically invoked by an end user directly. It is called by other programmatic components when a trip-related change must be reflected in shipping data, and the ETRM metadata notes that it is referenced by one other package, confirming its role as a shared service rather than an entry-point API. Because the interface accepts FND-style API version, initialization, commit, and return-status parameters, callers are expected to follow the standard EBS API invocation pattern: pass an API version, decide whether to initialize the message list and commit, and inspect X_return_status for success, expected error, or unexpected error signals.

In custom development or extensions, the package is best used indirectly — through the transportation and shipping flows that already call it — rather than by direct invocation. When the requested function get_org_organization_info is needed, it is generally called for read-only organization resolution and does not commit data. As with any APPS-owned package, callers should not modify the package body; extensions should wrap or reference the documented procedures and respect the FND message-handling contract.