Results for “action_note”

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

Overview

FTE_ORDER_HISTORY_V is an internal reporting view within the Oracle E-Business Suite Transportation Execution (FTE) module. It exposes the action history associated with transportation orders, presenting a denormalized, query-ready projection of order-level events such as creation, status changes, and other workflow actions recorded against a logistics order. The view is documented in ETRM 12.2.2 as an internal view, meaning it is not part of Oracle's published public interface but is used by the application's own forms, concurrent programs, or diagnostic logic. Because it joins buyer language, user identity, and party information into a single row per history event, it is well suited to operational inquiries that would otherwise require multiple joins across FND, HZ, and POM schemas. The metadata notes the view is "Not implemented in this database" in the sample environment, which indicates availability depends on whether the FTE module and POM order objects are licensed and installed.

Underlying Base Objects

The view text is defined over five underlying objects. POM_ACTION_HISTORY (aliased POH) is the driving table and supplies the core history records, including sequence number, action type, action date, and the actioning user. POM_ORDER_HEADERS (aliased PO) supplies the order context and the BUYER_LANG_CODE used for lookup language resolution. FND_LOOKUP_VALUES (aliased LK1) provides the translated meaning for the action type from the lookup type 'FTE_ORDER_ACTION'. HZ_PARTIES (aliased HZP) supplies the PARTY_NAME, joined via a left outer join on ACTION_USER_ID = PARTY_ID, so party data is optional. FND_USER (aliased USR) supplies the EMAIL_ADDRESS, also joined on ACTION_USER_ID via CUSTOMER_ID, again as an outer join. The joins are constrained so that OBJECT_TYPE_CODE must equal 'LOGISTICS' and the lookup language must default to 'US' when no buyer language is present.

Key Columns

• OBJECT_ID — The logistics order number the history row belongs to; joins to POM_ORDER_HEADERS.ORDER_NUMBER.
• OBJECT_ID2 — A secondary identifier for the same record, typically a line or related object reference.
• OBJECT_TYPE_CODE — Filtered to 'LOGISTICS', identifying the history context.
• SEQUENCE_NUM — Ordering key for the history timeline; the view is sorted ascending by this column.
• ACTION_TYPE — The code of the action performed, translated through the FTE_ORDER_ACTION lookup.
• MEANING — The user-facing, language-resolved description of ACTION_TYPE.
• ACTION_DATE — Timestamp of the action event.
• ACTION_USER_ID — Identifier of the user who performed the action; matches the search term and is the join key to both HZ_PARTIES and FND_USER.
• ACTION_NOTE — Free-text annotation recorded with the action.
• PARTY_NAME — Name of the party associated with the acting user, if resolvable.
• EMAIL_ADDRESS — Email address of the acting user from FND_USER, if resolvable.

Common Use Cases and Queries

Because the view combines user identity, party name, and email in a single result set, it is commonly used to audit who acted on an order and when, and to drive notification or reporting logic. A typical query retrieves the full action trail for a specific order:

• SELECT sequence_num, action_type, meaning, action_date, action_user_id, party_name, email_address, action_note FROM fte_order_history_v WHERE object_id = :order_number ORDER BY sequence_num;
• To isolate a specific actor, filter on the searched column: SELECT object_id, action_type, action_date, action_note FROM fte_order_history_v WHERE action_user_id = :user_id ORDER BY action_date DESC;
• To report on action frequency by user: SELECT action_user_id, meaning, COUNT(*) FROM fte_order_history_v GROUP BY action_user_id, meaning ORDER BY 3 DESC;

Administrators should note the outer joins mean PARTY_NAME and EMAIL_ADDRESS may be null when the acting user is not registered in HZ_PARTIES or FND_USER, and that reliance on an internal view carries upgrade risk between 12.1.1 and 12.2.2.