Search Results aso_apr_function_b

Overview

ASO_APR_FUNCTION_VL is a bilingual (MLS) validation view within the Oracle E-Business Suite Order Capture (ASO) module. It is part of the Oracle Advanced Pricing and Order Capture integration framework, where "APR" denotes the Advanced Pricing / Attribute Pricing Rule function registration facility. The view exposes a user-facing, translated list of registered functions that the Order Capture engine can invoke during pricing, attribute mapping, and rule execution against a sales order or quote line. Its primary purpose is to provide a language-aware presentation layer over the base function definition tables, so that application forms, LOVs, and concurrent programs display function names and descriptions in the session's current language rather than the base language stored in the transactional table.

In EBS 12.1.1 and 12.2.2, objects whose name ends in the suffix "_VL" (View, Language) follow the standard Oracle multi-language support (MLS) pattern. The view joins a "_B" (base) table, which holds language-independent columns and the primary key, with a "_TL" (translation) table, which holds the language-dependent descriptive columns keyed by LANGUAGE. The view is therefore classified as a reporting and integration access point rather than a transactional storage object; it is read-only from the perspective of calling code.

Underlying Base Objects

The view is defined over two documented base tables:

• ASO_APR_FUNCTION_B — the base table aliased as B. It supplies the surrogate key ASO_APR_FUNCTION_ID, the internal FUNCTION_NAME, PACKAGE_NAME, RETURN_DATATYPE, the WHO audit columns, and the 15 descriptive flexfield attribute columns plus CONTEXT.
• ASO_APR_FUNCTION_TL — the translation table aliased as T. It supplies the language-dependent USER_FUNCTION_NAME and DESCRIPTION columns.

The join condition is B.ASO_APR_FUNCTION_ID = T.ASO_APR_FUNCTION_ID, restricted by T.LANGUAGE = USERENV('LANG'). This predicate ensures that only the row matching the language of the current database session is returned, giving each function a single translated record per query. The view additionally projects B.ROWID as ROW_ID. It should be noted that the ETRM 12.2.2 metadata records this view as "Not implemented in this database" and lists no documented referenced base objects, indicating that in the reference environment the underlying tables were not present and the view definition was therefore not instantiated. In an operational 12.1.1 or 12.2.2 instance where ASO Advanced Pricing function seeding has been applied, the base and translation tables exist and the view resolves normally.

Key Columns

• ROW_ID — the ROWID of the base-table row, useful for direct row addressing in custom DML against the base table.
• ASO_APR_FUNCTION_ID — the primary key and foreign key linking base and translation records; the join and uniqueness anchor.
• FUNCTION_NAME — the internal, language-independent identifier of the registered function.
• PACKAGE_NAME — the PL/SQL package that implements the function logic invoked by the pricing or order capture engine.
• RETURN_DATATYPE — the datatype the function returns, informing callers how to interpret results.
• USER_FUNCTION_NAME — the translated, user-visible name displayed in forms and LOVs.
• DESCRIPTION — the translated description of the function's purpose.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — descriptive flexfield segments supporting extensible configuration.

Common Use Cases and Queries

Typical uses include validating that a function referenced by a pricing rule is registered, populating LOVs in Order Capture setup forms, and auditing which package implements a given function. A representative query lists all available functions in the session language:

SELECT ASO_APR_FUNCTION_ID, FUNCTION_NAME, USER_FUNCTION_NAME,
       PACKAGE_NAME, RETURN_DATATYPE
FROM   ASO_APR_FUNCTION_VL
ORDER BY USER_FUNCTION_NAME;

A second pattern looks up the implementing package for a specific function:

SELECT PACKAGE_NAME, DESCRIPTION
FROM   ASO_APR_FUNCTION_VL
WHERE  FUNCTION_NAME = :p_function_name;

Because the view filters on USERENV('LANG'), queries always return the translation appropriate to the connected session, making it suitable for both interactive and concurrent reporting without additional language handling.