Results for “bom_operation_skills_v”

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

Overview

BOM_OPERATION_SKILLS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Bills of Material (BOM) product family. The view exposes the skill, competence, and qualification requirements attached to routing operations and their associated resources. In manufacturing environments, operations frequently require operators or equipment to hold specific certifications or demonstrated competencies — for example, a welding step may require a certified welder rated at a particular proficiency, or a test operation may require an operator qualified on calibrated instrumentation. BOM_OPERATION_SKILLS_V presents these requirements in a denormalized, human-readable form, resolving the numeric foreign keys stored in the base table into descriptive competence, rating, and qualification names. The view is read-only and serves reporting, integration, and inquiry purposes rather than transactional entry. It is useful wherever downstream systems — shop floor execution, work instruction generation, quality management, or custom OBIEE/BI Publisher reports — must determine what skills a given operation demands before work is released or assigned.

Underlying Base Objects

The view is defined over four referenced objects, all exposed through synonyms in the APPS schema:

• BOM_OPERATION_SKILLS — the driving base table that stores one row per skill requirement linked to a standard operation, routing operation sequence, and resource.
• PER_COMPETENCES — the Oracle HRMS competences table, supplying the competence name (PC.NAME).
• PER_RATING_LEVELS — the HRMS rating levels table, supplying the rating scale value and short name used to build the displayed skill level.
• PER_QUALIFICATION_TYPES — the HRMS qualification types table, supplying the qualification name (PQT.NAME).

All three HRMS lookups are joined with outer-join syntax (the (+) operator), so a row in BOM_OPERATION_SKILLS is returned even when its competence, rating level, or qualification type is not defined. The final join predicate contains a compound OR condition that permits a rating level to match a competence either by shared rating scale or by direct competence linkage, or to fall through when either side is null. This permissive join prevents valid skill rows from being dropped during reporting.

Key Columns

The view exposes the primary key components and descriptive attributes of the underlying skill record. Notable columns include:

• ROW_ID — the ROWID of the base BOM_OPERATION_SKILLS row, providing a stable handle for updates or drill-back.
• LEVEL_ID, STANDARD_OPERATION_ID, ORGANIZATION_ID, OPERATION_SEQUENCE_ID, RESOURCE_ID — the routing context identifying which organization, operation sequence, and resource the skill requirement applies to.
• COMPETENCE_ID / COMPETENCE — the competence key and its resolved name from PER_COMPETENCES.
• RATING_LEVEL_ID / SKILL_LEVEL — the rating level key and a concatenated display value in the form "step value-name" from PER_RATING_LEVELS; the DECODE returns NULL when both components are empty, so users searching on "skill_level" see a clean blank rather than a stray hyphen.
• QUALIFICATION_TYPE_ID / QUALIFICATION — the qualification key and resolved name from PER_QUALIFICATION_TYPES.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard audit columns carried through from the base table.

Common Use Cases and Queries

Typical applications include generating skill matrices for a routing, validating that all operations are covered by qualified labor, and feeding shop floor or quality systems. The following query lists all skills for a given organization and operation sequence:

• SELECT operation_sequence_id, resource_id, competence, skill_level, qualification
• FROM  bom_operation_skills_v
• WHERE organization_id = :org_id
• AND   operation_sequence_id = :op_seq;

To find operations requiring skills at or above a given rating, filter on SKILL_LEVEL or join RATING_LEVEL_ID to PER_RATING_LEVELS. To identify skill requirements lacking a resolved competence (data quality checks), select rows where COMPETENCE IS NULL. Because all lookups are outer-joined, such queries safely surface orphaned records without dropping the skill row itself.