Results for “org_id”

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

Overview

The QA_PLANS_API package is a public PL/SQL API in the Oracle E-Business Suite Quality Management module. It encapsulates the core business logic required to create, retrieve, and validate Quality plans (QA_PLANS) and to resolve the organizational context in which those plans operate. The package is declared with AUTHID CURRENT_USER, meaning its unqualified references to database objects are resolved in the schema of the calling user; in practice it is invoked through APPS synonyms and executed against the APPS schema. Its principal purpose is to shield callers — typically Oracle Forms, concurrent programs, and custom extensions — from the underlying table structures by exposing stable programmatic interfaces for querying plan identity, plan names, organization identifiers, and lookup-derived plan types. The package has been stable since at least the 2003 code baseline (header version 115.4) and remains documented in ETRM for EBS 12.1.1 and 12.2.2, where it is referenced by five other packages.

Key Procedures and Functions

• EXISTS_QA_PLANS — Boolean function that determines whether a Quality plan exists for a given plan identifier; used for pre-validation before further processing.
• FETCH_QA_PLANS — Procedure that retrieves the plan record into the package's cached state so that subsequent accessor functions return data for that plan.
• ORG_ID — Returns the organization identifier associated with a plan.
• PLAN_ID — Resolves a plan name to its numeric plan identifier.
• VALID_PLAN_ID — Boolean validity check confirming that a supplied plan identifier corresponds to an existing plan.
• PLAN_NAME — Returns the descriptive name of a plan given its identifier.
• GET_ORG_ID — Derives an organization identifier from an organization code, allowing callers to translate a user-facing code into the internal organization key.
• GET_PLAN_TYPE — Returns the plan type for a supplied lookup code. This is the function most commonly sought when searching "get_plan_type"; it maps a value from the plan-type lookup into its descriptive or classified form, enabling callers to validate or display plan type information without querying FND_LOOKUP_VALUES directly.

Tables Accessed

The package reads and writes the QA_PLANS table, the primary store of Quality plan definitions, which underlies the fetch, existence, validity, name, and identifier functions. FND_LOOKUP_VALUES is accessed to resolve lookup codes, notably for plan type and organization-related lookups used by GET_PLAN_TYPE. MTL_PARAMETERS supplies organization context so that plans can be scoped and validated against valid inventory organizations. PLITBLM is referenced in relation to plan line or item-level data, supporting the package's ability to associate plans with their component records. All accesses occur through APPS synonyms, consistent with the AUTHID CURRENT_USER declaration.

Usage Notes

QA_PLANS_API is typically invoked from the Quality Management forms and from concurrent programs that must validate or resolve plan attributes before processing. Custom code should call the public functions rather than querying QA_PLANS or FND_LOOKUP_VALUES directly, since the API centralizes lookup resolution and organization validation. Because the package is referenced by five other packages, changes to its behavior can cascade; callers should observe the documented signatures and treat the package as a stable integration point. GET_PLAN_TYPE in particular should be used whenever a plan-type lookup code must be converted to its meaningful value, ensuring consistent interpretation across forms, reports, and extensions in both 12.1.1 and 12.2.2 environments.