Results for “registration_number”

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

Overview

PER_ZA_TRAINING_V is a database view owned by the APPS schema in Oracle E-Business Suite, registered under the PER (Human Resources) product family. It is a South Africa (ZA) localization object, created to support statutory skills development reporting aligned with the National Qualifications Framework (NQF). The view's stated purpose, per Oracle's E-Business Suite Technical Reference Manual (ETRM), is to maintain the base table PER_ZA_TRAINING through the NQF forms delivered as part of the South African HR localization. In practice, the view is not a purely read-only reporting construct; it functions as the form-layer access path that Oracle Forms uses to query and maintain NQF training records for employees and applicants.

From a reporting and integration standpoint, PER_ZA_TRAINING_V exposes employee training and qualification data in a decoded, presentation-ready form. Because it resolves lookup codes into their meanings inline, it is directly usable by BI Publisher reports, custom concurrent programs, and inbound/outbound interfaces that need human-readable descriptions of NQF fields of learning and course types without a secondary lookup join. This makes it suitable both for transactional maintenance through the NQF forms and for downstream extract and reporting requirements in South African payroll and HR implementations.

Underlying Base Objects

The view is defined over two documented base objects:

• PER_ZA_TRAINING (SYNONYM) — the base table in which NQF training and qualification records are physically stored. All columns exposed by the view originate from this table; the view adds no persisted data of its own.
• HR_GENERAL (PACKAGE) — a public HR utility package. The view calls HR_GENERAL.DECODE_LOOKUP to translate stored lookup codes into their display meanings, and it is this call that establishes the dependency on the package within the view definition.

Because the view is a single-table projection with inline decoding, there is no join complexity: every row in PER_ZA_TRAINING yields exactly one row in PER_ZA_TRAINING_V, and DML performed through the view (as used by the NQF forms) is applied directly to the underlying table. The relationship is therefore one of strict row-for-row correspondence, with the view acting as a decoded facade over the table.

Key Columns

The view exposes twelve columns. The principal ones are:

• TRAINING_ID — primary identifier for the training record; the linking key for the entity.
• LEVEL_ID — reference to the NQF level associated with the training or qualification.
• PERSON_ID — the person (employee or applicant) to whom the training record belongs; the key for person-level reporting.
• FIELD_OF_LEARNING / FIELD_OF_LEARNING_MEANING — the stored lookup code for the NQF field of learning, and its decoded description via HR_GENERAL.DECODE_LOOKUP against lookup type ZA_NQF_FIELDS_OF_LEARNING.
• COURSE / COURSE_MEANING — the stored course code and its decoded meaning via lookup type ZA_NQF_COURSES.
• SUB_FIELD — further classification of the field of learning.
• CREDIT and NOTIONAL_HOURS — NQF credit value and notional learning hours attributable to the training.
• REGISTRATION_DATE and REGISTRATION_NUMBER — the date of registration and the external registration reference, typically used for SETA or NQF body submissions.

Common Use Cases and Queries

Typical scenarios include extraction of decoded NQF training data for statutory skills reporting, verification of registration details before submission to a SETA, and person-level summaries of credits and notional hours for learnership tracking.

A representative query retrieving decoded training details for a person:

• SELECT person_id, level_id, field_of_learning_meaning, course_meaning, sub_field, credit, notional_hours, registration_date, registration_number FROM per_za_training_v
• WHERE person_id = :p_person_id
• ORDER BY registration_date DESC;

Aggregate queries are equally common, for example summing credits and notional hours by field of learning to produce NQF submission summaries, or counting registrations by course meaning and date range for management reporting. Because the view performs the lookup decoding, these queries avoid additional joins to FND_LOOKUP_VALUES, though implementations requiring multi-language or date-effective lookup resolution should still consider joining the lookup views explicitly.