Results for “consolidate_lines”

8 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.FTE_SOURCE_LINE_CONSOLIDATION package is a component of Oracle E-Business Suite's Freight and Transportation Execution (FTE) module, which underpins the Oracle Transportation Management integration for outbound and inbound logistics processing. In Oracle EBS 12.1.1 and 12.2.2, this package serves a specialized business function: it consolidates source document lines prior to transmission to the transportation execution engine. Source documents may include order lines, delivery lines, or shipment request lines originating from Order Management, Shipping Execution, or Inventory. Consolidation groups these lines into fewer, logically unified records so that the downstream carrier selection and rating engine processes them efficiently, applying consistent service levels, routing, and cost determination. The package is classified as an OTHER API, meaning it is intended primarily for internal use by the FTE framework rather than direct customer invocation, though it is callable by dependent packages. Its declaration uses AUTHID CURRENT_USER, so it executes with the privileges of the calling user, which is consistent with an internal integration utility operating within the APPS schema context.

Key Procedures and Functions

The package exposes a single documented procedure:

  • CONSOLIDATE_LINES — The core consolidation routine. It accepts collections of source lines and source headers, along with an action identifier, and returns a standard FTE return status, message count, and message data. Its role is to merge related source lines into consolidated groupings that the carrier services engine can process. The procedure operates on the FTE_PROCESS_REQUESTS-defined table types (fte_source_line_tab and fte_source_header_tab), which are passed as IN OUT NOCOPY parameters, allowing the consolidated results to be returned in place without unnecessary copying. The p_action parameter governs which consolidation behavior is applied, and the outbound status parameters follow the standard EBS API error-handling convention (S = success, E = error, U = unexpected) with the message stack retrieved via FND_MSG_PUB when additional detail is required.

Tables Accessed

Through APPS synonyms, the package references the following objects:

  • MTL_SYSTEM_ITEMS — Provides item master attributes needed to determine item classification, freight characteristics, and whether lines are consolidatable, since consolidation logic often depends on item-level freight and handling parameters.
  • WSH_CARRIERS and WSH_CARRIER_SERVICES — Supply carrier and service-level definitions. Consolidation groups lines by carrier and service so that the transportation engine receives coherent, uniformly rateable blocks.
  • DBMS_UTILITY — Used for standard PL/SQL utility functions, commonly to retrieve the error stack or format diagnostic messages during exception handling.
  • PLITBLM — The PL/SQL table management package used to initialize, extend, and manipulate the associative-array collections passed between the caller and this package.

Usage Notes

The package is referenced by one other FTE package, indicating it operates as a subordinate utility within the broader FTE processing chain rather than as a top-level entry point. Typical invocation occurs when the FTE framework prepares source lines for carrier selection and rating — for example, during freight rating of delivery lines or shipment requests. It is generally invoked from server-side PL/SQL code or FTE concurrent processing, not from a standard EBS form. Because it is classified as OTHER and its parameters depend on internal record types (FTE_PROCESS_REQUESTS collections), customizations should avoid calling it directly; instead, integrators should use the supported FTE public APIs that internally invoke consolidation. In 12.1.1 and 12.2.2, behavior is consistent, though developers should be aware that the package header is an older artifact (circa 2002) and predates the 12.2 online patching model; any customization should be registered carefully to avoid invalidation during editioning. Standard diagnostic practice applies: check x_return_status first, and only retrieve messages when the status is not 'S'.