Search Results pn_space_assign_emp_pkg




Overview
Explore in AI Chat

Overview

PN_SPACE_ASSIGN_EMP_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that encapsulates the data-access and validation logic for employee space assignments within Oracle Property Manager (Pn). In the EBS 12.1.1 and 12.2.2 releases, the package operates over the PN_SPACE_ASSIGN_EMP_ALL entity, which stores the allocation of physical office space (locations) to employees for a defined date range. The package provides the standard insert, lock, update, and delete primitives that the Property Manager forms and concurrent programs require in order to maintain assignment records consistently, and it additionally supplies validation routines that detect conflicting or duplicate assignments before they are written to the base table.

The object is classified as OTHER in the documented API classification and is therefore not a published open interface; it is an internal, form-support utility package used primarily by the Property Manager office-assignment UI and by the import and synchronization layers that feed it.

Key Procedures and Functions

The package exposes seven documented procedures and functions:

  • INSERT_ROW — Creates a new employee space assignment record in the base table.
  • LOCK_ROW — Acquires a row-level lock on an existing assignment, used to serialize concurrent maintenance from the form.
  • UPDATE_ROW — Modifies the attributes of an existing assignment record.
  • DELETE_ROW — Removes an assignment record from the base table.
  • CHECK_OFFICE_ASSIGN_GAPS — Validates the assignment date range against existing assignments for the same office or location to detect gaps or overlaps in occupancy.
  • CHECK_DUPEMP_ASSIGN — Detects duplicate assignments, ensuring that an employee is not assigned to conflicting space for overlapping periods.
  • GET_LEAST_ST_DATE_ASSIGNMENT — Returns the earliest start date among an employee's assignments, typically used to establish the effective beginning of an occupancy sequence.

These routines form the transactional core that the Property Manager form invokes during normal record maintenance; the two CHECK routines and the date-retrieval function enforce business rules before commits are permitted. Parameter signatures are intentionally not enumerated here, as the documented metadata does not publish them.

Tables Accessed

  • PN_SPACE_ASSIGN_EMP_ALL — The primary base table holding employee space assignment records; the insert, update, delete, and lock operations act directly on this entity.
  • PN_SPACE_ASSIGN_EMP_S — The corresponding sequence used to generate primary keys for new assignment rows.
  • PN_LOCATIONS and PN_LOCATIONS_ALL — Location master tables consulted by the gap-checking and duplicate-detection routines to resolve the office or space being assigned.
  • DUAL — Standard single-row utility table used for scalar evaluations and sequence retrieval.
  • PLITBLM — The standard Oracle Forms PL/SQL table-of-varchar2 type used for passing arrays of identifiers between the form and the package.

Usage Notes

PN_SPACE_ASSIGN_EMP_PKG is referenced by four other packages: PNP_UTIL_FUNC, PN_CAD_IMPORT, PN_CC_SYNC_PKG, and PN_SPACE_ASSIGN_CUST_PKG. The CAD import routine relies on it to load space assignments generated from CAD floor-plan data, while the synchronization package uses it to keep employee assignments aligned with customer assignments. Because it is an internal package rather than a public API, customization efforts should prefer the standard Property Manager forms and concurrent programs; direct calls are appropriate only in controlled extensions where the standard UI cannot express the required logic. In all cases, callers must respect the validation routines before committing, since the base table does not independently protect against overlapping assignments.