Results for “accepted_by”

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

Overview

OE_ID_TO_VALUE is a public PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its business purpose is to translate internal numeric identifiers stored on Oracle Order Management entities into their corresponding user-facing, display-ready values. Order Management tables persist foreign keys, lookup codes, and party/site identifiers as surrogate values, while the Order Management windows, OA-based pages, and reporting layers must present descriptive names such as a customer name, a ship-to organization, a payment term, or a freight term. OE_ID_TO_VALUE bridges that gap by centralizing the ID-to-description resolution logic so that Order Management forms, validation routines, and dependent packages do not each re-implement the same joins.

The package is classified as OTHER in the EBS Technical Reference Manual; it is a utility/helper package rather than a formal business API. It is not referenced by any other database object directly, but the referenced-object graph shows it depends heavily on Order Management, Receiving/Customer (HZ) and inventory base tables, and it is in turn invoked by approximately 39 other packages in the Order Management and related modules. This positions it as a well-established internal utility used broadly across the order-to-cash flows.

Key Procedures and Functions

The ETRM metadata documents 116 procedures and functions. Among the documented routines, the following are representative of the package's translation role:

• GET_ATTR_TBL — Returns the attribute table (descriptive flexfield or attribute mapping) used to resolve attribute display values.
• CONVERSION_TYPE — Resolves the currency conversion type identifier to its descriptive value for order and pricing display.
• DELIVER_TO_CONTACT, INVOICE_TO_CONTACT, SHIP_TO_CONTACT, INTERMED_SHIP_TO_CONTACT, SOLD_TO_CONTACT — Resolve the internal contact identifier for each order role (deliver-to, invoice-to, ship-to, intermediate ship-to, sold-to) into the contact name shown on the order.
• DELIVER_TO_ORG, INVOICE_TO_ORG, SHIP_TO_ORG, INTERMED_SHIP_TO_ORG, SOLD_TO_ORG — Resolve the internal organization identifier for each order role into the descriptive organization name.
• INVENTORY_ORG and SHIP_FROM_ORG — Return the descriptive name of the inventory and ship-from organizations associated with a line.
• ORDER_SOURCE and ORDER_TYPE — Translate the order source and order type identifiers into their displayed descriptions.
• PAYMENT_TERM — Returns the payment term description for an order or customer.
• SHIPMENT_PRIORITY and DEMAND_CLASS — Resolve shipping priority and demand class codes to their lookup meanings.
• FOB_POINT — Returns the free-on-board point description associated with the order or line.

Each routine performs a single-purpose lookup against the appropriate master or lookup table and returns a scalar descriptive value. No parameter lists are documented in the ETRM excerpt, so the individual signatures are intentionally not reproduced here.

Tables Accessed

The package resolves values against Order Management base tables such as OE_ORDER_HEADERS_ALL, OE_ORDER_LINES, OE_ORDER_SOURCES, OE_ORDER_TYPES_V, and the order role views (OE_SOLD_TO_ORGS_V, OE_SHIP_TO_ORGS_V, OE_INVOICE_TO_ORGS_V, OE_DELIVER_TO_ORGS_V, OE_SHIP_FROM_ORGS_V, OE_CONTACTS_V), which supply the source identifiers and descriptive columns.

Trading-partner attributes are resolved from the Oracle Receivables/HZ model: HZ_PARTIES, HZ_PARTY_SITES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_CONTACT_POINTS, and HZ_RELATIONSHIPS. These provide customer, site, contact, and address descriptions. Inventory and item context is drawn from MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, MTL_SYSTEM_ITEMS_VL, MTL_ITEM_UOMS_VIEW, MTL_UNITS_OF_MEASURE_VL, MTL_CUSTOMER_ITEMS, MTL_CUSTOMER_ITEM_XREFS, MTL_CROSS_REFERENCES, and MTL_CROSS_REFERENCE_TYPES. Organization context comes from ORG_ORGANIZATION_DEFINITIONS, ORG_FREIGHT, and OE_SHIP_METHODS_V.

Lookup and reference data are read from AR_LOOKUPS, FND_LOOKUPS, OE_LOOKUPS, OE_FND_COMMON_LOOKUPS_V, OE_AR_LOOKUPS_V, MFG_LOOKUPS, OE_GL_DAILY_CONVERSION_TYPES_V, OE_PAYMENT_TYPES_VL, OE_SALES_CREDIT_TYPES, OE_RA_RULES_V, OE_RA_TERMS_V, AR_DEFERRAL_REASONS, AR_RECEIPT_METHODS, IBY_CREDITCARD_ISSUERS_V, and QP_LIST_HEADERS_VL. Supporting context is obtained from FND_USER, RA_SALESREPS, JTF_RS_GROUPS_VL, PJM_PROJECT, RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES_ALL, OE_AGREEMENTS_VL, OE_SYS_PARAMETERS, and OE_PREPAYMENT_UTIL.

Usage Notes

OE_ID_TO_VALUE is an internal utility rather than a user-facing API. It is typically invoked from Order Management forms and OA framework pages when displaying an order, from validation and defaulting logic that must convert stored IDs back to descriptive values, and from dependent Order Management packages that need a consistent name-resolution routine. Because the ETRM lists it as referenced by 39 other packages, it should be treated as a shared internal dependency: customizations that call it inherit the same resolution semantics as standard Order Management functionality.

Direct invocation from custom code is possible for read-only translation purposes, but Oracle does not document the package as a supported public API, and its procedure signatures are not published in the ETRM excerpt. Customizations should therefore prefer documented Order Management APIs where available, and restrict direct calls to OE_ID_TO_VALUE to display-only scenarios where no supported alternative exists. The package requires no concurrent program registration of its own; it executes in the context of the calling form, page, or package. As with all APPS utility packages in Release 12.1.1/12.2.2, the resolution results respect the language and territory settings of the calling session, and the package remains VALID in the documented environment.