Search Results fnd_standard_date

Overview

APPS.OKC_RULE_ATTS_BLK_V is an Oracle E-Business Suite view that exposes the attribute definitions of attributes belonging to Oracle Contract Terms and Conditions (OKC) rule developer descriptive flexfields. It presents, in a flattened and decoded form, the flexfield column usage metadata for the "OKC Rule Developer DF" descriptive flexfield, joined to the rule definition and the associated value set. Its purpose is to allow applications, reports, and integrations to determine, for each rule (flexfield context), which attribute columns exist, their display sequence, their prompts, whether they are required, and what type of validation or value set they use.

The view is particularly relevant to code that must render or interpret rule attributes dynamically, since the value-set identification is translated into a single-letter value type. This is where the search term "fnd_standard_date" is significant: the view maps value sets named FND_STANDARD_DATE to the value type code 'D', distinguishing standard date-validated attributes from time values ('T'), general flexfield validation ('F'), amount ('A'), number ('N'), and unmapped values ('J').

Underlying Base Objects

The view is defined over three documented base objects, joined as follows:

• FND_DESCR_FLEX_COL_USAGE_VL — the descriptive flexfield column usage view. This supplies the flexfield context code (used as the rule code), the column sequence number, the application column name, the required flag, the form left prompt, the enabled flag, and the flex value set identifier.
• FND_FLEX_VALUE_SETS — accessed through a synonym, this table supplies the value set name, validation type, format type, maximum size, number precision, and uppercase-only flag. The join to this table is an outer join (FLEX_VALUE_SET_ID = VST.FLEX_VALUE_SET_ID (+)), so attributes with no associated value set are still returned with a NULL value set and a derived value type of 'J'.
• OKC_RULE_DEFS_V — the rule definition view, which links the rule code, application identifier, and descriptive flexfield name. This join restricts the column usage rows to those attributes that correspond to actual OKC rule definitions.

Because the base column usage view is language-dependent (_VL), prompts returned by this view reflect the session language.

Key Columns

• RLE_CODE — the descriptive flexfield context code, equal to the rule code from OKC_RULE_DEFS_V.
• COL_SEQ — the column sequence number, defining display or processing order of attributes within a rule.
• COL_NAME — the application column name, with special decoding of JTOT_OBJECT1_CODE, JTOT_OBJECT2_CODE, and JTOT_OBJECT3_CODE to JTOT_OBJECT1, JTOT_OBJECT2, and JTOT_OBJECT3 respectively.
• REQUIRED_YN — the flexfield required flag, indicating whether the attribute must be supplied.
• PROMPT — the form left prompt, used as the user-visible attribute label.
• VAL_TYPE — the derived value type: 'T' for OKC_TIMEVALUES, 'D' for FND_STANDARD_DATE, 'F' for flexfield validation, 'A' for OKC_AMOUNT value sets, 'N' for numeric format without a named value set, and 'J' when no value set applies.
• MAXIMUM_SIZE — the value set maximum size.
• NUMBER_PRECISION — the numeric precision, forced to NULL for the OKC_NUMBER value set.
• UPPERCASE_ONLY_FLAG — the value set flag indicating that entered values must be uppercase.

Common Use Cases and Queries

Typical usage retrieves the attributes for a given rule and inspects their value types, particularly to identify date attributes backed by FND_STANDARD_DATE.

SELECT rle_code, col_seq, col_name, required_yn, prompt, val_type, maximum_size
FROM   apps.okc_rule_atts_blk_v
WHERE  rle_code = :rule_code
ORDER BY col_seq;

To isolate standard date attributes:

SELECT rle_code, col_name, prompt
FROM   apps.okc_rule_atts_blk_v
WHERE  val_type = 'D';

The view is commonly used to drive dynamic UI generation, validate incoming rule attribute payloads in integrations, and produce mapping documentation for the OKC Rule Developer flexfield. Because the value set join is outer, callers should always test VAL_TYPE = 'J' when determining whether an attribute is free-form rather than value-set validated.