Search Results create_es_employee

Overview

PER_ES_CREATE_EMPLOYEE is a country-specific Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM as "OTHER." It provides a localized entry point for creating employee records that conform to Spanish (ES) statutory and reporting requirements. The package encapsulates the logic required to insert a new person and assignment into the Oracle Human Resources data model while populating the Spanish-specific "per information" flexfield attributes that carry legally mandated identifiers. Typical deployments of this package are found in EBS 12.1.1 and 12.2.2 environments where the Spanish localization (the "ES" legislative context) has been installed and the corresponding DFF segments for Spain are configured.

The header comment preserved in the source indicates the package was shipped in early 2007 and carries version identifier 120.0.12000000.1, consistent with the file naming conventions used across the Spanish HR localizations. The package is a thin wrapper: its public surface exposes a single procedure that accepts already-validated input values and relies on the standard PER_ALL_PEOPLE_F infrastructure to persist the record.

Key Procedures and Functions

The package exposes exactly one documented program unit:

• CREATE_ES_EMPLOYEE — Creates a Spanish employee. The procedure accepts the employee's last name, first name, national identifier, and three generic "per information" attributes. The header comments map these three slots to specific Spanish DFF segments: the first and last name map to the primary name attributes, the identifier type maps to p_per_information2, and the identifier value maps to p_per_information3. Based on the signature, the procedure performs the person creation and attribute population in a single call, shielding callers from the individual DFF segment names.

No functions, additional overloads, or private helper signatures are exposed in the documented metadata. Because the procedure is defined in the package specification, it is callable directly from PL/SQL, forms, or concurrent program logic.

Tables Accessed

The ETRM metadata documents a single referenced table, accessed through an APPS synonym:

• PER_ALL_PEOPLE_F — The core Oracle HR person and assignment entity. The package writes the new employee row here, using the effective-dated structure to establish the person's start date and primary assignment. The Spanish DFF attributes supplied through the per-information parameters are stored on this record (or on the associated person DFF columns), making the DFF segments available to downstream Spanish reporting, Social Security filings, and statutory extracts.

No other tables appear in the documented reference set, though in practice the procedure will implicitly touch supporting HR entities such as business groups and assignment types during the insert.

Usage Notes

PER_ES_CREATE_EMPLOYEE is intended for programmatic employee creation, not for interactive data entry through the standard Spanish HR forms. It is typically invoked from:

• Custom PL/SQL — Data migration, interface, or rapid-hire scripts that need to bulk-create Spanish employees with localized identifiers already populated.
• Concurrent programs and interfaces — Batch loads that transform legacy or third-party employee data into the EBS HR schema for Spanish legal entities.
• Other PL/SQL packages — The ETRM records that this package is referenced by one other package, indicating it participates as a reusable building block within the localization layer rather than being called directly by end-user forms.

Because the procedure bypasses the standard validation performed by the full HR employee API, callers must supply valid, complete values for the national identifier and per-information segments. The caller is also responsible for commit or rollback handling, and for ensuring that the business group and legislative context resolve to the Spanish configuration. Given its date of shipment and its dependence on legacy DFF segment positions, the package should be reviewed against current Spanish legal requirements (for example, NIF/NIE handling) before reuse in new development.