Search Results minimum_value

Overview

The OKC_ACTION_ATTRIBUTES_V view is a seeded, VALID database object owned by the APPS schema within the OKC – Contracts Core product of Oracle E-Business Suite. It exposes the metadata that defines the action attributes used by Oracle Contracts (OKC) to describe, validate, and render contract-related actions and their associated fields. Functionally, it serves as the single, language-aware access point for action attribute definitions, allowing reports, forms, concurrent programs, and integration interfaces to retrieve attribute configuration without referencing the underlying base and translation tables directly.

Because the view joins the base attribute table to its translation table and filters by the session language, it returns each attribute in the language of the current user session. This makes it suitable for multilingual reporting and for embedded list-of-values lookups. In ETRM terms, the view is a read-oriented object and is typically consumed rather than modified by custom code.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema:

• OKC_ACTION_ATTRIBUTES_B – the base table holding the non-translated attribute definition, including data type, list flag, visibility, minimum and maximum values, format mask, and the many descriptive and DFF columns.
• OKC_ACTION_ATTRIBUTES_TL – the translation table holding language-specific values for the attribute name, description, and the SFWT flag.

The two tables are joined on AAEB.ID = AAET.ID, and the translation side is further restricted by AAET.LANGUAGE = USERENV('LANG'), ensuring that only the current session language rows are returned. The view retains the base table ROWID as ROW_ID, and carries OBJECT_VERSION_NUMBER to support the standard EBS optimistic locking conventions.

Key Columns

• ROW_ID / ID / AAL_ID – unique row identifier, attribute identifier, and the associated action-attribute-list identifier that groups the attribute.
• ELEMENT_NAME, NAME, DESCRIPTION – the internal DFF element name plus the translated display name and description returned from the TL table.
• DATA_TYPE, LIST_YN, VISIBLE_YN, DATE_OF_INTEREST_YN – control how the attribute is stored, whether a list of values applies, whether it is displayed, and whether it participates in date-of-interest logic.
• FORMAT_MASK, MINIMUM_VALUE, MAXIMUM_VALUE – formatting and validation boundaries. The MAXIMUM_VALUE column supplies the upper bound applied when validating a contract action attribute value, and is frequently the target of metadata-driven validation queries.
• ACN_ID, JTOT_OBJECT_CODE, NAME_COLUMN, DESCRIPTION_COLUMN, SOURCE_DOC_NUMBER_YN – linkage to the contract object/action and supporting document references.
• SEEDED_FLAG, APPLICATION_ID, ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 – standard EBS seed indicator, owning application, and descriptive flexfield context columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard audit columns.

Common Use Cases and Queries

Typical uses include listing the attributes available for a given action attribute list, retrieving validation bounds, and populating LOVs. To find the maximum value defined for a particular attribute element:

• SELECT id, aal_id, element_name, name, data_type, minimum_value, maximum_value FROM okc_action_attributes_v WHERE element_name = :p_element_name;
• SELECT id, name, minimum_value, maximum_value FROM okc_action_attributes_v WHERE aal_id = :p_aal_id AND visible_yn = 'Y';
• SELECT id, element_name, maximum_value FROM okc_action_attributes_v WHERE maximum_value IS NOT NULL AND seeded_flag = 'Y';

Because the view already applies the USERENV('LANG') filter, callers need not join the translation table or supply a language predicate; the returned NAME and DESCRIPTION reflect the current session language, which simplifies both EBS reports and external integration extracts.