Search Results get_actual_datatype

Overview

APPS.QA_PLAN_ELEMENT_API is a public PL/SQL API within the Oracle E-Business Suite Quality Management (QA) module. It provides the programmatic interface for creating, maintaining, and validating plan elements and specification characteristics associated with QA collection plans and specifications. In the Oracle EBS 12.1.1 and 12.2.2 architectures, this package functions as the canonical business logic layer through which other QA components manipulate plan element definitions, character data types, specification limits, and contextual attributes such as department, job, and production line.

The package is classified as an API and holds VALID status in the APPS schema. It sits at the center of a dense dependency graph: it is referenced by twenty-two other packages, including QA_PLANS_PUB, QA_RESULTS_PUB, QA_SPECS_PUB, QA_CORE_PKG, QA_ERES_PKG, and the EAM work order quality utility EAM_WO_QUA_UTILITY_PVT. This breadth of reuse confirms that QA_PLAN_ELEMENT_API is foundational to plan and results processing across the Quality suite.

Key Procedures and Functions

The ETRM metadata documents 168 procedures and functions, reflecting a comprehensive validation and retrieval surface. Representative members include:

• FETCH_QA_SPEC_CHARS / FETCH_QA_PLAN_CHARS / REFETCH_QA_PLAN_CHARS — retrieve the set of characteristics attached to a specification or plan, supporting the plan element grid used throughout QA forms.
• KEYFLEX, NORMALIZED, DERIVED, HARDCODED, PRIMITIVE — determine the origin and nature of a plan element value, distinguishing user-entered, derived, hardcoded, or primitive (unconditionally captured) elements.
• VALUES_EXIST, EXISTS_QA_PLAN_CHARS, SQL_VALIDATION_EXISTS — existence and validation checks that confirm whether element values or validation rules are defined for a given context.
• ELEMENT_IN_PLAN, ELEMENT_IN_SPEC — verify whether a specific element is associated with a plan or specification.
• GET_ACTUAL_DATATYPE, GET_ELEMENT_DATATYPE — resolve the effective data type of a plan element or characteristic.
• GET_SPEC_LIMITS, GET_LOW_HIGH_VALUES — return specification limits and the low/high bounds used for results evaluation and out-of-specification determination.
• GET_DEPARTMENT_ID, GET_JOB_ID, GET_PRODUCTION_LINE_ID — resolve organizational context attributes tied to the element.

Tables Accessed

The package reads and writes through APPS synonyms against core EBS tables. Manufacturing and process tables — GME_BATCH_HEADER, GME_BATCH_STEPS, GME_BATCH_STEP_ACTIVITIES, GME_BATCH_STEP_RESOURCES, GME_PROCESS_PARAMETERS, and GMP_PROCESS_PARAMETERS — provide the process manufacturing context from which plan elements derive their values. Inventory tables MTL_ITEM_REVISIONS, MTL_LOT_NUMBERS, MTL_MATERIAL_STATUSES, and MTL_PARAMETERS supply item, revision, lot, and material status data used in validation and limit evaluation. Service and customer tables CSD_REPAIRS, CSI_ITEM_INSTANCES, CS_INCIDENTS, HZ_PARTIES, and JTF_TASKS_B link plan elements to repairs, installed base instances, incidents, parties, and tasks. Together these accesses enable the package to validate elements against real transactional and master data.

Usage Notes

QA_PLAN_ELEMENT_API is invoked indirectly rather than through direct end-user execution. Oracle Quality forms call the higher-level public packages (QA_PLANS_PUB, QA_SPECS_PUB, QA_RESULTS_PUB), which in turn delegate element-level operations to this API. Concurrent programs that process results interfaces and E-Records (QA_RESULTS_INTERFACE_PKG, QA_ERES_PKG) also depend on it. Because it is referenced by twenty-two packages, custom extensions should call it only through documented public entry points and never bypass validation logic. As with all APPS APIs, direct DML against the underlying tables should be avoided; all modifications must flow through this package to preserve data integrity across the QA plan, specification, and results model.