Search Results meaning_nondb

Overview

APPS.SO_FREIGHT_CHARGE_TYPES_V is a reporting and integration view in the Oracle E-Business Suite Order Management (ONT) schema. It exposes the freight charge type definitions maintained in Oracle Order Management, joined to the Order Management lookup that supplies the code-to-meaning translation. The view belongs to the APPS schema and is documented for both Oracle EBS 12.1.1 and 12.2.2.

The view is a denormalized presentation of the SO_FREIGHT_CHARGE_TYPES base table. In addition to the base table's columns, it appends a single non-database column, MEANING_NONDB, which carries the user-facing meaning of the freight charge type code retrieved from SO_LOOKUPS. Because the meaning is sourced from a lookup and not stored on the base record, the column is labeled as non-database. This makes the view the preferred access point for reports, interfaces, and custom code that need the displayable freight charge type description alongside the persistent definition.

In the Order Management data model, freight charge types define the categories of freight and special charges that may be applied to an order, such as freight, insurance, or handling. Each definition carries a code, a name, an amount, and a currency. The view surfaces these attributes in a single queryable object, removing the need for consumers to perform their own lookup join.

Underlying Base Objects

The view is defined over two base objects referenced through APPS synonyms:

• SO_FREIGHT_CHARGE_TYPES (aliased FCT) — the primary table holding freight charge type definitions. The view selects ROWID as ROW_ID together with the table's identifying and descriptive columns.
• SO_LOOKUPS (aliased SL) — the Order Management lookup table. The join matches FCT.FREIGHT_CHARGE_TYPE_CODE to SL.LOOKUP_CODE, restricted to SL.LOOKUP_TYPE = 'FREIGHT_CHARGE_TYPE'. This restriction ensures only freight charge type lookup values contribute the MEANING_NONDB column.

The metadata additionally lists FND_GLOBAL (PACKAGE) as a referenced object. FND_GLOBAL is the standard EBS concurrent-program and session context package, typically referenced by views and forms to supply WHO columns and application context. Its presence reflects the standard APPS-layer dependency rather than a column-level join.

The relationship is therefore many-to-one from freight charge type records to lookup values: every row in SO_FREIGHT_CHARGE_TYPES that carries a matching, correctly typed lookup code produces one row in the view, enriched with that lookup's meaning. Because the lookup join is an equality match on lookup type and code, records whose code has no qualifying lookup entry are not returned.

Key Columns

• ROW_ID — the ROWID of the underlying SO_FREIGHT_CHARGE_TYPES row, useful for row-level identification and updates.
• FREIGHT_CHARGE_TYPE_ID — the primary key of the freight charge type definition.
• NAME — the user-defined name of the freight charge type.
• DESCRIPTION — free-form descriptive text for the charge type.
• FREIGHT_CHARGE_TYPE_CODE — the code that links the record to the FREIGHT_CHARGE_TYPE lookup and drives the view join.
• CURRENCY_CODE — the currency in which the freight charge amount is expressed.
• FREIGHT_CHARGE_AMOUNT — the default or defined amount associated with the charge type.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range governing when the charge type is active.
• MEANING_NONDB — the lookup meaning for the freight charge type code, provided for display purposes and not persisted on the base table.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit (WHO) columns describing record creation and last modification.

Common Use Cases and Queries

Typical uses include listing active freight charge types for order-entry validation, driving freight charge selection in custom order interfaces, and producing reference reports where the human-readable meaning is required alongside the code.

List active freight charge types with their meanings:

• SELECT freight_charge_type_id, name, freight_charge_type_code, MEANING_NONDB, currency_code, freight_charge_amount FROM apps.so_freight_charge_types_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));

Resolve a specific code to its defined charge type:

• SELECT freight_charge_type_id, name, currency_code, freight_charge_amount FROM apps.so_freight_charge_types_v WHERE freight_charge_type_code = :code;

Because the view already performs the lookup join, queries against it should not re-join SO_LOOKUPS for the same lookup type; doing so would duplicate the join logic and risk conflicting meanings. Standard EBS security applies: access is granted through the APPS schema and responsibility-based menus.