Search Results update_move

Overview

APPS.FTE_MOVES_PVT is a private PL/SQL package within the Oracle E-Business Suite Freight and Transportation Execution (FTE) module, classified under the ETRM (E-Business Suite Transportation Management) product family. The package encapsulates the core business logic for maintaining move records, which represent planned or executed transportation activities linking a lane, service level, and trip context. Moves are the atomic units that FTE uses to describe the movement of goods across a transportation network; they carry carrier and trip planning references such as the CM trip number and TP plan name, along with planning status indicators and standard WHO audit columns.

The _PVT suffix indicates that this is a private package, meaning its procedures are intended to be consumed by other public APIs, table handlers, or internal FTE packages rather than being called directly by customer extensions. The declaration AUTHID CURRENT_USER confirms the package executes with the privileges of the invoker, which is typical for private implementation packages that assume the caller has already passed through a sanctioned public interface.

A defining characteristic of the package is its MOVE_REC_TYPE record type, declared explicitly "in sync with the table definition for trips" and used across the package's table handlers and calling packages. The record mirrors every column of the FTE_MOVES table, including the full set of developer descriptive flexfield columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15) and the standard audit and program columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID). A companion associative array type, MOVE_ATTR_TBL_TYPE, indexes collections of these records by BINARY_INTEGER, supporting bulk processing.

Key Procedures and Functions

• CREATE_MOVE — Creates a new move record. According to the inline documentation, it returns the generated MOVE_ID to the caller and will generate a move name automatically when one is not supplied.
• UPDATE_MOVE — Modifies an existing move record, applying changed attributes through the MOVE_REC_TYPE structure.
• DELETE_MOVE — Removes a move record from the FTE data model.
• MARK_MOVE_REPRICE_FLAG — Sets the reprice indicator on a move, signalling that freight charges must be recalculated. This supports rate and cost adjustment workflows.
• LOCK_MOVE — Acquires a logical lock on a move, protecting it from concurrent modification during multi-step processing.
• POPULATE_RECORD — The procedure most relevant to the searched term. It assembles a populated MOVE_REC_TYPE instance, mapping row data from the FTE_MOVES table into the package's record structure so that callers can work with move attributes without issuing their own queries. This is the standard mechanism by which the PVT layer converts relational rows into the private record type consumed by CREATE_MOVE, UPDATE_MOVE, and the other mutating procedures.
• GET_NAME — Resolves or generates the display name for a move, supporting the automatic naming behaviour referenced in the CREATE_MOVE documentation.

Tables Accessed

• FTE_MOVES — The primary move entity table. All create, update, delete, and populate operations target this table; its column list defines the MOVE_REC_TYPE structure.
• FTE_MOVES_S — The sequence (or secondary) object associated with move identifier generation, used during CREATE_MOVE to obtain the MOVE_ID returned to the caller.
• FTE_TRIP_MOVES — The association table linking moves to trips, consulted and maintained to keep trip-to-move relationships consistent when moves are locked, deleted, or reassigned.

Usage Notes

Because FTE_MOVES_PVT is a private package, it is normally invoked indirectly. The most common invocation paths are internal FTE table handlers, the public FTE move API that wraps this package, and transportation planning processes. One other package is documented as referencing it, reinforcing its role as a shared implementation layer rather than a standalone entry point.

Typical call flows pass a MOVE_REC_TYPE populated by POPULATE_RECORD into CREATE_MOVE or UPDATE_MOVE, with the caller supplying FND_API.G_FALSE for the initialization message list flag when message stack initialization is already handled. When a move is edited concurrently — for example, during trip planning or re-rating — LOCK_MOVE precedes the update, and MARK_MOVE_REPRICE_FLAG is set so downstream freight costing re-evaluates charges.

The package emits debug output through the WSH debug subsystem (constants c_sdebug and c_level1, c_debug and c_level2), so diagnostics can be enabled using standard WSH debug profile options. Header information shows the source file as FTEMVTHS.pls. Custom code should not call these procedures directly; developers extending FTE should use the corresponding public APIs, which preserve validation, security, and message-handling semantics.