Results for “t_v1000”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.OE_FREIGHT_RATING_PVT package is an internal, private (PVT) PL/SQL package within Oracle Order Management that supports the freight rating and freight charge calculation process. Freight rating in Oracle EBS determines applicable freight charges for order lines and returns based on carrier, shipping method, weight, and rate structures; the results are recorded as price adjustments against the order. This package provides the underlying engine that evaluates freight terms and produces rating output consumed by the pricing and order capture flows.
The package header header declares an extensive library of collection types (T_DATE, T_NUM, and numerous T_Vn VARCHAR2 collections) alongside Bulk_Line_Adj_Rec_Type, a record type modeling a bulk price adjustment row for order lines. These types allow the freight rating logic to process multiple lines and freight adjustments in bulk rather than row by row, which is essential for performance during high-volume order entry or batch pricing runs. The package compiles with AUTHID CURRENT_USER, meaning privileges are evaluated against the invoking schema; as is standard for _PVT APIs, it is not intended for direct external invocation.
Key Procedures and Functions
Two program units are documented in the package metadata:
- GET_LIST_LINE_TYPE_CODE — A function that returns the list line type code associated with a supplied numeric key. It resolves the pricing list line type code used to classify a freight charge line within the pricing adjustment structure, typically distinguishing freight charges from other charge types such as surcharges or discounts. It operates against the package global
g_list_line_type_code_recandg_list_line_type_code_tblcache. - PROCESS_FTE_OUTPUT — A procedure that processes freight term engine (FTE) output returned from external freight rating. It accepts an order header identifier together with the FTE source line table, the order line table, the computed freight rates, a configuration count, a UI flag, and a flag controlling whether pricing should be called for freight rating. It writes the resulting freight rate data back onto the order lines and records the associated freight charges as price adjustments.
The presence of the Bulk_Line_Adj_Rec_Type record and its collection types indicates that freight adjustment rows are staged and applied through array-based processing for efficiency.
Tables Accessed
The package references the following objects through APPS synonyms:
- OE_ORDER_LINES — The order line detail table. The package reads order line attributes and writes or updates freight-related values returned by the rating process.
- OE_PRICE_ADJUSTMENTS and OE_PRICE_ADJUSTMENTS_S — The pricing adjustment and its translated (TL-style) companion table. Freight charges are persisted as adjustments linked to the header or lines, with columns such as
price_adjustment_id,adjusted_amount, andoperandrepresented by the record type. - DUAL — Used for scalar lookups and simple value retrieval.
- PLITBLM — The PL/SQL integer table indexed by binary integer used for bulk operations.
Usage Notes
As a _PVT package, OE_FREIGHT_RATING_PVT is not a public API and is not documented for customer extension. It is invoked internally by Oracle Order Management and freight/pricing components — the metadata records that it is referenced by two other packages, which drive the call sequence during order pricing and freight calculation. Freight rating is typically triggered when an order is booked or repriced, or through pricing-related concurrent programs that evaluate freight terms in batch.
Customizations should never call this package directly. Sites requiring freight charge logic should use the supported public APIs such as OE_ORDER_PUB and the pricing APIs, whose freight handling internally depends on this private layer. The APPS-owned reference is included here for diagnostic and troubleshooting purposes, for example when tracing why a freight adjustment was or was not written to OE_PRICE_ADJUSTMENTS during pricing. Note that the search term "APPIAN PREMIUM FREIGHT APPROVAL" does not correspond to any documented object or procedure in this package; no such function exists in the ETRM metadata for OE_FREIGHT_RATING_PVT.