Search Results exists_property_id




Overview

PN_CAD_IMPORT is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the Property Manager (PN) application family. Its name and object dependencies indicate that it provides the server-side engine for importing Computer-Aided Design (CAD) drawing data — space, property, and location records — into the Oracle Property Manager repository. In EBS 12.1.1 and 12.2.2, Property Manager supports the ingestion of CAD files (such as AutoCAD DWG/DXF exports) so that floor plans, space polygons, and associated attributes can be translated into native PN entities without manual data entry. PN_CAD_IMPORT encapsulates the core logic that validates identifiers, resolves property and location references, writes interface-table rows, and finally loads the staged data into the production tables. The package is documented as VALID in the ETRM metadata, confirming it is compiled and active in the 12.2.2 environment. It has a narrow dependency footprint: it references only SYS.STANDARD directly and is referenced by itself and by RRS_SITES_PKG, suggesting a contained, purpose-built utility rather than a widely shared foundation package.

Key Procedures and Functions

  • IMPORT_CAD — The primary entry point. It orchestrates the full CAD import flow, driving staging, validation, and final load of the uploaded drawing data.
  • LOCATIONS_ITF — Handles the locations interface, populating or processing the PN_LOCATIONS_ITF staging table used to bridge external CAD data into PN_LOCATIONS_ALL.
  • IS_ID_CODE_VALID — A validation function that confirms whether a supplied identifier code is legitimate before it is used to link CAD elements to PN records.
  • EXISTS_PROPERTY_ID — A boolean-style check that determines whether a given property identifier already exists, preventing duplicate inserts.
  • SPACE_ALLOCATIONS_ITF — Manages the space allocation interface, translating CAD-derived space assignments into rows suitable for the employee/space assignment tables.
  • PUT_LOG — Writes diagnostic or status messages to the import log, supporting traceability of the CAD load run.
  • PUT_LINE — A lower-level logging utility that outputs a single line to the log target, used by PUT_LOG and other routines.
  • GET_LOCATION_TYPE — Returns the classification of a location, used to determine how a CAD element should be interpreted during import.

Tables Accessed

The package reads and writes the following documented tables, referenced through APPS synonyms:

  • PN_LOCATIONS_ALL — The master location table; CAD-derived locations are inserted or updated here.
  • PN_LOCATIONS_ITF — The locations interface/staging table populated by LOCATIONS_ITF before final load.
  • PN_PROPERTIES_ALL — Stores property records against which CAD space and location data are validated.
  • PN_ADDRESSES_ALL — Provides address context for locations created through the import.
  • PN_EMP_SPACE_ASSIGN_ITF and PN_SPACE_ASSIGN_EMP_ALL — Interface and base tables for employee-to-space assignments, populated by SPACE_ALLOCATIONS_ITF.
  • PA_PROJECTS_ALL and PA_TASKS — Referenced to associate imported space or property data with Projects (PA) records and tasks.

Usage Notes

PN_CAD_IMPORT is typically invoked indirectly rather than from a user-facing form. It is most commonly driven by the CAD import concurrent program or by an internal Property Manager flow that uploads a CAD file, stages the parsed geometry and attributes, and then calls IMPORT_CAD to complete the load. Because it is referenced by RRS_SITES_PKG, it may also be invoked programmatically from resource/site-related processing. Custom extensions that need to bulk-load space and location data from external CAD or facility-management systems can call the public procedures directly, but should populate the corresponding interface tables (PN_LOCATIONS_ITF, PN_EMP_SPACE_ASSIGN_ITF) first and rely on IS_ID_CODE_VALID, EXISTS_PROPERTY_ID, and GET_LOCATION_TYPE for pre-validation. After the load, the logging routines PUT_LOG and PUT_LINE provide an audit trail of outcomes and errors.