Search Results qa_plan_char_action_outputs




Overview
Explore in AI Chat

Overview

The QA_PLAN_CHAR_ACTION_OUTPUTS table is a core data object within the Oracle E-Business Suite (EBS) Quality Management (QA) module, specifically for versions 12.1.1 and 12.2.2. It serves a critical function in the execution of quality collection plans by defining the mapping between action output variables and specific collection plan characteristics (elements). This table acts as a configuration repository that dictates how data captured during a quality inspection is processed and assigned to predefined variables for subsequent use in calculations, validations, or automated actions. Its existence is fundamental to enabling dynamic and data-driven workflows within the quality inspection process.

Key Information Stored

The table's primary purpose is to link an action to a specific collection element via a named token. The key columns, as defined by its primary and foreign keys, are:

  • PLAN_CHAR_ACTION_ID: A foreign key referencing QA_PLAN_CHAR_ACTIONS. This identifies the specific action rule defined within a collection plan.
  • TOKEN_NAME: The name of the output variable or token that will receive a value. This token is used within action logic.
  • CHAR_ID: A foreign key referencing QA_CHARS. This column stores the identifier for the specific collection plan characteristic (e.g., a measurement, test, or attribute) whose value will be assigned to the TOKEN_NAME.

Together, the PLAN_CHAR_ACTION_ID and TOKEN_NAME form the table's primary key, ensuring a unique mapping per action. The structure effectively answers the question: "For this action, which collection element's result populates which variable?"

Common Use Cases and Queries

This table is primarily accessed for understanding and debugging the behavior of automated actions in collection plans. A common reporting use case is to generate a list of all output mappings for a given collection plan or a specific action within it. For instance, a developer or analyst might run a query to see all variables that will be set by actions in a plan. A typical SQL pattern joins this table to QA_PLAN_CHAR_ACTIONS and QA_CHARS to translate IDs into meaningful names.

SELECT pca.action_id,
       pcao.token_name,
       qc.name characteristic_name
FROM qa_plan_char_action_outputs pcao,
     qa_plan_char_actions pca,
     qa_chars qc
WHERE pcao.plan_char_action_id = pca.plan_char_action_id
AND pcao.char_id = qc.char_id
AND pca.plan_id = :p_plan_id;

Another critical use case is during the runtime execution of a collection plan, where the EBS application logic queries this table to determine which collected value to assign to an action's internal variable before evaluating the action's conditions.

Related Objects

The QA_PLAN_CHAR_ACTION_OUTPUTS table has defined dependencies on two other key QA tables, forming a central link in the action configuration chain.

  • QA_PLAN_CHAR_ACTIONS: This is the parent table. The foreign key QA_PLAN_CHAR_ACTION_OUTPUTS.PLAN_CHAR_ACTION_ID references QA_PLAN_CHAR_ACTIONS. This relationship ties each output mapping to a specific action rule.
  • QA_CHARS: This table stores the definition of all collection characteristics. The foreign key QA_PLAN_CHAR_ACTION_OUTPUTS.CHAR_ID references QA_CHARS, linking the output variable to the actual data element being collected in the plan.

Understanding these relationships is essential for any data analysis or extension involving the flow of data from collection through automated quality actions.