Search Results fte_tender_pvt




Overview

FTE_TENDER_PVT is a private PL/SQL package owned by APPS within the Oracle E-Business Suite Transportation Management (ETRM) module. It implements the core tender-handling engine for freight tendering: the process by which a shipper offers a load, trip, or trip segment to a carrier, receives an accept or reject response, and routes that response back through Oracle Workflow for further processing. The package is declared with AUTHID CURRENT_USER, meaning executing privileges are resolved against the invoking schema rather than the defining schema. Its source header (FTETEPVS.pls, 120.1.12000000.1) indicates an established code line present in both 12.1.1 and 12.2.2.

The package defines two important sets of constants. Tender status constants (TENDERED, ACCEPTED, REJECTED, SHIPPER_CANCELLED, AUTO_ACCEPTED, NORESPONSE, RETENDERED, SHIPPER_UPDATED) enumerate the valid lifecycle states of a tender. Source constants (XML, CP, WL) identify how a tender or response originated, distinguishing XML messaging, the collaborative portal, and workflow-based events. These constants are used throughout the Transportation tender flows and constrain the values this package accepts and emits.

Key Procedures and Functions

Tables Accessed

  • WSH_TRIPS, WSH_TRIP_STOPS — Source trip and stop data used to validate and contextualize tender actions.
  • FTE_TENDER_SNAPSHOT — Storage for tender snapshots written and deleted by the snapshot procedures.
  • FTE_TENDER_ID_S — Sequence used to generate tender identifiers.
  • WF_PARAMETER_LIST_T — Workflow parameter list table used when raising tender events.
  • WSH_EXCEPTIONS — Destination for exception records, notably carrier arrival exceptions.
  • FND_USER — Resolves user context for processing and audit purposes.
  • DUAL, PLITBLM — Utility references for scalar evaluation and message handling.

Usage Notes

As a PVT (private) package, FTE_TENDER_PVT is not intended as a public integration surface; it is invoked by Transportation tender forms, Oracle Workflow event activities, and the other EBS packages that reference it, and is referenced by five packages in total. The documented table list contains no direct tender detail table such as FTE_TENDER, suggesting core tender persistence is handled by the referencing packages while this package orchestrates workflow events and validations. Customizations should not call this package directly; use the supported tender APIs instead. Because behavior is governed by the status and source constants, upgrades between 12.1.1 and 12.2.2 should be validated against those enumerated values.