Search Results update_prc_parameter
Overview
FTE_LANE_PKG is a PL/SQL package owned by APPS that encapsulates the core business logic for managing transportation lanes and their associated rate structures within Oracle E-Business Suite. In the Oracle Transportation Management/Enterprise Transportation Management (ETRM) context of 12.1.1 and 12.2.2, a "lane" represents a defined origin-to-destination shipping path between a carrier and a shipper, along with its distance, transit time, service type, equipment type, commodity categorization, and effective dating. FTE_LANE_PKG provides the programmatic interface through which lane records, lane commodities, lane service assignments, rate charts, schedules, and pricing parameters are created, validated, updated, and retrieved. The package is classified as an OTHER API, meaning it is intended primarily for internal use by Oracle's own forms and concurrent programs rather than as a formally published public API, although it is referenced by six other packages in the EBS schema, indicating it operates as a foundational utility layer for lane-related functionality.
Key Procedures and Functions
The package exposes eighteen documented procedures and functions organized around identifier generation, record retrieval, validation, and DML operations.
- GET_LANE_ID and GET_NEXT_LANE_ID — retrieve the identifier for an existing lane and generate the next available lane identifier, respectively, drawing from the FTE_LANES sequence table.
- GET_NEXT_LANE_COMMODITY_ID, GET_NEXT_LANE_SERVICE_ID, GET_NEXT_SCHEDULE_ID, and GET_NEXT_PRC_PARAMETER_ID — generate surrogate keys for lane commodities, lane services, schedules, and pricing parameters. GET_NEXT_SCHEDULE_ID, the object of the user's search, is the accessor that supplies the next primary key value for the FTE_SCHEDULES table.
- GET_SCHEDULE — returns schedule information for a given lane.
- INSERT_LANE_TABLES, INSERT_SCHEDULES, and INSERT_PRC_PARAMETERS — perform multi-table inserts across the lane, schedule, and pricing parameter entities, often driven by the lane_tbl and related collection types declared in the package header.
- UPDATE_LANE_FLAGS, UPDATE_LANE_RATE_CHART, and UPDATE_PRC_PARAMETER — modify editable/viewable flags, rate chart associations, and pricing parameters.
- DELETE_ROW — removes a lane-related row.
- VERIFY_OVERLAPPING_DATE, CHECK_LANES, CHECK_EXISTING_LOAD, and FIND_TYPE — validation utilities that detect date overlaps, verify lane integrity, test for existing loads, and resolve type classifications before commit.
Tables Accessed
The package operates against the core ETRM lane tables through APPS synonyms. FTE_LANES and its shadow table FTE_LANES_S hold the primary lane definitions. FTE_LANE_COMMODITIES and FTE_LANE_COMMODITIES_S store commodity categorizations and basis information per lane. FTE_LANE_SERVICES and FTE_LANE_SERVICES_S capture service type assignments. FTE_LANE_RATE_CHARTS links lanes to rate lists. FTE_SCHEDULES and FTE_SCHEDULES_S store scheduled sailing or transit records. FTE_PRC_PARAMETERS and FTE_PRC_PARAMETERS_S hold pricing parameters. QP_LIST_HEADERS_B and QP_LIST_HEADERS_TL are referenced to validate and interpret the Oracle Advanced Pricing list headers associated with lane rate charts. DUAL is used for sequence-style singleton queries, and PLITBLM is the PL/SQL table-to-index-by-table conversion utility used to materialize the package's INDEX BY BINARY_INTEGER collections.
Usage Notes
FTE_LANE_PKG is typically invoked from the Oracle EBS transportation lane setup forms, from concurrent programs that bulk-load or migrate lane data, and from custom extensions that need to insert or validate lane records programmatically. Because the package is classified as OTHER rather than a published API, its signatures are not guaranteed to remain stable across patches, and developers calling it from custom code should treat the interface as subject to change. The identifier-generating functions such as GET_NEXT_SCHEDULE_ID are commonly reached indirectly when forms create child schedule rows, while the validation routines (VERIFY_OVERLAPPING_DATE, CHECK_LANES) are called before commit to enforce date-range and referential integrity. Downstream packages that depend on FTE_LANE_PKG should be reviewed during upgrades between 12.1.1 and 12.2.2 to confirm that the underlying table synonyms and any internal dependencies on QP_LIST_HEADERS have not shifted.
-
APPS.FTE_LANE_PKG SQL Statements
12.1.1
-
APPS.FTE_LANE_PKG SQL Statements
12.2.2
-
PACKAGE: APPS.FTE_LANE_PKG
12.2.2
-
PACKAGE: APPS.FTE_LANE_PKG
12.1.1
-
PACKAGE BODY: APPS.FTE_LANE_PKG
12.1.1
-
PACKAGE BODY: APPS.FTE_LANE_PKG
12.2.2
-
APPS.FTE_LANE_PKG dependencies on FTE_LANE_PKG
12.1.1
-
APPS.FTE_LANE_PKG dependencies on FTE_LANE_PKG
12.2.2
-
APPS.FTE_LANE_PKG dependencies on FTE_PRC_PARAMETERS
12.1.1
-
APPS.FTE_LANE_PKG dependencies on FTE_PRC_PARAMETERS
12.2.2
-
APPS.FTE_LANE_PKG dependencies on FTE_UTIL_PKG
12.1.1
-
APPS.FTE_LANE_PKG dependencies on FTE_UTIL_PKG
12.2.2