Results for “chk_job_id”

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

Overview

PE_JEI_BUS is a PL/SQL business logic package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Human Resources (PER) product family and encapsulates the server-side validation and maintenance logic for the Job Extra Information entity, which stores user-defined, flexfield-style attributes attached to job definitions. The package name reflects its origin as a generated table handler ("_BUS" denoting business logic) associated with the Job Extra Information (JEI) table and its row handler, consistent with the header source file pejeirhi.pkh dated 2005. The package sits between the presentation layer (typically the Job Extra Information maintenance form) and the underlying PER_JOB_EXTRA_INFO, PER_JOB_INFO_TYPES, and PER_JOBS tables.

Its responsibilities are twofold. First, it performs context resolution, notably deriving the legislation code associated with a given job extra information record. Second, it enforces data integrity through a standard set of validation routines invoked before insert, update, and delete operations. The package is documented as "Internal Development Use Only," meaning it is not a published public API and Oracle does not guarantee interface stability across releases. The ETRM metadata records an API classification of OTHER and lists eight documented procedures and functions.

Key Procedures and Functions

• RETURN_LEGISLATION_CODE — Returns the legislation code for a specific primary key value. The caller must pass an existing job extra information identifier; the business group's legislation code is returned. An error is raised if the value does not exist.
• CHK_JOB_INFO_TYPE — Validates that the job information type supplied exists in PER_JOB_INFO_TYPES with an active/inactive flag of 'Y'. Failure raises an application error and terminates processing.
• CHK_JOB_ID — Confirms that the referenced job identifier is valid against the PER_JOBS table before the extra information row is persisted.
• CHK_MULTIPLE_OCCURENCES_FLAG — Validates the multiple-occurrences indicator, which governs whether more than one extra information record may exist for a given job and information type combination.
• CHK_NON_UPDATEABLE_ARGS — Checks arguments that must not change after initial creation, protecting key or context attributes from unintended modification during update processing.
• INSERT_VALIDATE — Orchestrates the validation sequence executed prior to inserting a new job extra information row.
• UPDATE_VALIDATE — Orchestrates the validation sequence executed prior to updating an existing job extra information row.
• DELETE_VALIDATE — Orchestrates the validation sequence executed prior to deleting a job extra information row.

Individual parameter lists are deliberately not reproduced here; the documented signature for RETURN_LEGISLATION_CODE takes the job extra information identifier, and the remaining routines follow the generated table-handler convention.

Tables Accessed

• PER_JOB_EXTRA_INFO — The primary entity table. It holds the extra information rows keyed by the job extra information identifier and is read and written by the insert, update, and delete validation paths.
• PER_JOB_INFO_TYPES — The setup table defining valid information types, including the active/inactive flag. Read by CHK_JOB_INFO_TYPE to ensure the requested type is currently enabled.
• PER_JOBS — The job definition table. Read by CHK_JOB_ID to confirm that the parent job referenced by the extra information row exists.

All three tables are accessed through APPS synonyms, and all validation occurs within the same database session that performs the DML.

Usage Notes

PE_JEI_BUS is invoked indirectly rather than called directly by end users. The principal consumer is the Job Extra Information maintenance form, whose server-side triggers call the validate routines before committing changes, and whose post-query and context-sensitive logic may call RETURN_LEGISLATION_CODE. The package is also referenced by three other packages, which likely supply shared validation or defaulting logic for the same entity family.

Because the package is classified as internal development use only, customizations should not call its procedures directly. Sites requiring equivalent functionality should route changes through supported APIs or the standard forms. When extending validation, developers should be aware that modifying this package risks breaking the generated table handler and the documented dependency chain.