Search Results fte_tender
Overview
FTE_TENDER_PVT is the private application programming interface supporting Oracle E-Business Suite's Freight and Transportation Execution (FTE) tender-processing framework. Tender processing is the mechanism by which a shipper issues a load offer to a carrier and manages the carrier's response — acceptance, rejection, counter-offer, update, or cancellation — within Oracle Transportation Management and the EBS logistics modules. This package encapsulates the business logic, validation routines, workflow event publication, and snapshot management that together constitute the tender lifecycle. It is classified as a private (PVT) API, meaning it is intended for internal consumption by other FTE packages and public wrappers rather than for direct invocation by external consumers or custom code. The package is referenced by five other packages within the EBS codebase, confirming its role as a shared internal service layer. The header indicates it has been in service since at least the 11i-to-12.x lineage, with the last recorded revision in release 12.0.0.
Key Procedures and Functions
The package exposes twenty-two documented procedures and functions that collectively handle the tender request and response workflow. The core lifecycle procedures are RAISE_TENDER_REQUEST and RAISE_TENDER_EVENT, which compose the workflow parameter list and publish the tender to the notification/approval process. RAISE_TENDER_ACCEPT, RAISE_TENDER_REJECT, and RAISE_TENDER_UPDATE generate the corresponding events when a carrier acts on a tender. HANDLE_TENDER_RESPONSE, HANDLE_CANCEL_TENDER, and HANDLE_UPDATE_TENDER process incoming responses and drive the state transitions that the package recognizes via constants for NOTIFIED, APPROVED, REJECTED, and abort statuses.
Validation and authorization are handled by VALIDATE_TENDER_REQUEST, CAN_PERFORM_THIS_ACTION, CAN_PERFORM_THIS_ACTION_STR, IS_AUTO_ACCEPT_ENABLED, and CHECK_THRESHOLD_FOR_STOP, the last of which evaluates stop-level thresholds before permitting an action. Snapshot management is provided by TAKE_TENDER_SNAPSHOT and DELETE_TENDER_SNAPSHOT, which preserve the weight and volume data at the moment a tender is raised. GET_ITEM_KEY retrieves the item key used to link workflow events to the trip. Response handling includes UPDATE_CARRIER_RESPONSE, CHECK_CARRIER_ARRIVAL_TIME, LOG_CARRIER_ARR_EXC, and RELEASE_TENDER_BLOCK, while COMPLETE_CANCEL_TENDER finalizes cancellation processing.
Tables Accessed
The package reads and writes several core EBS tables through APPS synonyms. FTE_TENDER_ID_S supplies the sequence used to generate tender identifiers. FTE_TENDER_SNAPSHOT stores the stored weight, volume, and stop-level snapshots taken when a tender is raised and is cleaned up when the tender is cancelled or completed. WSH_TRIPS and WSH_TRIP_STOPS provide the trip and stop context against which tenders are validated and thresholds checked. WSH_EXCEPTIONS records exception conditions, including carrier arrival exceptions logged by LOG_CARRIER_ARR_EXC. FND_USER resolves user identity for audit and authorization checks. WF_PARAMETER_LIST_T, a workflow parameter list type, is used to pass structured parameters to workflow events, while PLITBLM and DUAL support internal list manipulation and singleton queries.
Usage Notes
Because FTE_TENDER_PVT is a private package, it is not documented for direct customer invocation. It is typically called by the public FTE tender APIs, Oracle Transportation Management integration flows, and the tender-related forms and concurrent programs that compose the user-facing freight execution process. Custom development that requires tender behavior should call the corresponding public API rather than this private package. Developers who do read this source should note its dependence on workflow event publication, snapshot storage, and exception logging — all of which are required for the tender state machine to function correctly.