Results for “decimal_precision”

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

Overview

QA_CHARS_API is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an API within the Quality Management (QA) module. Its central role is to provide a programmatic, reusable interface to the QA_CHARS table, which stores the definition and configuration metadata for quality collection elements. In the E-Business Suite quality model, a collection element represents a single data point that an operator must capture against an inspection or a collection plan—for example, an inspection result, measurement, or attribute value.

The package therefore acts as a metadata access layer for these elements. Rather than allowing forms, concurrent programs, and other PL/SQL units to query QA_CHARS directly, QA_CHARS_API exposes functions that return individual attributes of an element keyed by its element_id, plus procedures that pre-fetch element rows into a session-level cache. This abstraction centralizes element attribute logic, reduces direct table hits, and provides a stable interface that many other packages and forms depend upon. The ETRM metadata records QA_CHARS_API as a referenced object for approximately twenty other packages, confirming its position as a foundational utility in the quality schema.

Key Procedures and Functions

The package exposes 26 documented procedures and functions. The element attribute accessors form the largest group; each accepts an element_id and returns one property of the corresponding QA_CHARS row:

• EXISTS_QA_CHARS — returns a Boolean indicating whether an element exists for the supplied identifier.
• FETCH_QA_CHARS — retrieves a single element into the package cache.
• FETCH_PLAN_CHARS — pre-fetches all elements belonging to a plan, introduced to minimize repeated QA_CHARS queries when most or all plan elements will be accessed.
• GET_ELEMENT_ID — resolves an element name to its numeric identifier.
• HARDCODED_COLUMN, FK_MEANING, FK_LOOKUP_TYPE, SQL_VALIDATION_STRING, DATATYPE, DEFAULT_VALUE, DISPLAY_LENGTH, DECIMAL_PRECISION, LOWER_REASONABLE_LIMIT, UPPER_REASONABLE_LIMIT, PROMPT, DATA_ENTRY_HINT, MANDATORY_FLAG — return specific descriptive or behavioral attributes of an element, such as its prompt text, datatype, mandatory flag, reasonable limits, and validation-related information.
• REMOVE_ORDER_BY_FROM_SQL — a utility that strips an ORDER BY clause from a supplied SQL string.
• FORMAT_SQL_FOR_VALIDATION and FORMAT_SQL_FOR_LOV — build validation and List of Values SQL statements, accepting organization and creator context.

Tables Accessed

QA_CHARS_API is documented as referencing three tables through APPS synonyms:

• QA_CHARS — the primary source table holding element definitions and the attributes returned by the accessor functions.
• QA_PLAN_CHARS — links elements to collection plans and is read by FETCH_PLAN_CHARS to identify all elements associated with a given plan.
• PLITBLM — a generic EBS table used to store large text fragments, typically accessed in connection with the SQL formatting functions.

Usage Notes

QA_CHARS_API is invoked from Oracle Forms, concurrent programs, and custom PL/SQL code throughout the Quality module. Typical usage begins with GET_ELEMENT_ID or EXISTS_QA_CHARS to validate an element, followed by the attribute accessors to obtain prompt, datatype, and validation information needed to render or process a collection element dynamically. For batch operations covering an entire plan, callers should prefer FETCH_PLAN_CHARS so that all elements are cached in a single pass rather than issuing repeated single-row fetches. Because the package is a shared dependency for numerous other packages, customizations should call it rather than replicating its logic, and any extension should preserve the existing element_id-based signatures to avoid breaking dependent code.