Results for “process_fte_output”

12 results




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

Overview

OE_FREIGHT_RATING_PVT is a private PL/SQL package body in the APPS schema that supports freight rating and freight charge processing within Oracle Order Management. In Oracle EBS 12.1.1 and 12.2.2, freight charges are frequently modeled as order line adjustments rather than as separate charges, and this package provides the internal logic that translates calculated freight costs into adjustments on order lines. Because it is classified as a PVT (private) API, it is not intended for direct invocation by external or customer code; it functions as a supporting layer beneath the public Order Management APIs and the freight and transportation integration flows.

The package operates in close coordination with the pricing engine and with the fulfillment and transportation execution components. Its principal role is to take the output of a freight or rating calculation and apply the resulting monetary amounts as price adjustments against the appropriate order lines, so that freight is reflected consistently in order totals, pricing, and downstream billing.

Key Procedures and Functions

  • GET_LIST_LINE_TYPE_CODE — Returns the line type code used when constructing or interpreting a list of order lines for freight rating purposes. This supports the package's internal need to classify and filter order lines by their line type before freight amounts are calculated or applied.
  • PROCESS_FTE_OUTPUT — Consumes the output produced by the freight and transportation execution (FTE) processing and converts it into pricing adjustments on the associated order lines. This is the central routine that bridges the external rating result and the Order Management pricing structures.

Both routines are private implementation helpers. Their signatures and parameter lists are not part of the published interface, and they should not be called directly from custom code.

Tables Accessed

  • OE_ORDER_LINES — The base order line table. The package reads line information such as line identifiers and line types to determine where freight adjustments should be applied, and may also participate in updating freight-related line attributes.
  • OE_PRICE_ADJUSTMENTS — Stores the adjustment records applied to order lines. The package writes or updates entries here to represent the freight charge as a line-level price adjustment.
  • OE_PRICE_ADJUSTMENTS_S — The corresponding sequence or supporting table used when creating adjustment records, ensuring unique identifiers are assigned.
  • DUAL — Used for single-row evaluations and expression checks.
  • PLITBLM — The standard PL/SQL integer table type, used for handling collections of numeric identifiers within the package's internal logic.

In addition to these documented tables, the package depends on supporting PL/SQL components including OE_FREIGHT_RATING_UTIL, OE_ORDER_PRICE_PVT, OE_ORDER_PUB, OE_LINE_ADJ_UTIL, OE_MSG_PUB, OE_DEBUG_PUB, OE_GLOBALS, FND_API, FTE_PROCESS_REQUESTS, and STANDARD. These dependencies confirm that the package follows the EBS API programming standards, using FND_API for return status and message handling and OE_GLOBALS for shared Order Management constants.

Usage Notes

OE_FREIGHT_RATING_PVT is invoked indirectly rather than directly. It is typically driven when freight rating results are returned to Order Management and need to be materialized as order line adjustments. The dependency on FTE_PROCESS_REQUESTS indicates that the package may be triggered through the freight and transportation execution request flow, where a concurrent process supplies rating output that is then processed into pricing adjustments.

The package also participates in pricing recalculation, since it depends on OE_ORDER_PRICE_PVT and OE_LINE_ADJ_UTIL and writes into OE_PRICE_ADJUSTMENTS. When an order line is repriced or when freight is recalculated, the adjustment records maintained through this package may need to be refreshed.

Although the metadata indicates that OE_FREIGHT_RATING_PVT is not referenced by any other database object, the ETRM listing records it as referenced by two other packages, which reflects the internal private-API relationship. The presence of OE_FREIGHT_RATING_UTIL as a dependency suggests that shared rating utilities are separated from the private processing logic, with this package concentrating on the application of rating output rather than the rating algorithm itself.

Developers supporting freight behavior in Order Management should treat this package as internal infrastructure. Customizations should target the supported public APIs and the underlying freight and pricing configuration rather than modifying or calling this package directly, since its interface is not guaranteed across releases.