Results for “pn_space_assign_cust_all”

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

Overview

PN_SPACE_ASSIGN_CUST_ALL is a Property Manager (PN) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores customer space assignment information. Each row represents the allocation of physical space within a leased or owned property to a specific customer, expressed through allocation percentages, allocated and utilized areas, and effective date ranges. The table is owned by the PN schema and is registered as VALID in the ETRM repository, holding 41 documented columns.

Functionally, the table links customer-facing receivables entities (customer accounts and site uses) to property-side lease and tenancy structures, and to Oracle Projects and General Ledger for expense and project accounting. From a Data Vault modeling perspective, the mined FK structure classifies this object as satellite-leaning: it carries descriptive, time-bound allocation attributes around a natural business key (CUST_SPACE_ASSIGN_ID) rather than acting as a pure hub or a pure association link. This classification is a heuristic suggestion based on foreign key topology, not a prescriptive design.

Key Information Stored

The surrogate primary key is CUST_SPACE_ASSIGN_ID, enforced by the PN_SPACE_ASSIGN_CUST_PK constraint. A unique index, PN_SPACE_ASSIGN_CUST_U1, exists on the same column, so the documented business-key candidate coincides with the surrogate key rather than introducing a separate composite natural key.

• CUST_ACCOUNT_ID — the customer account receiving the space assignment; joins to HZ_CUST_ACCOUNTS.
• SITE_USE_ID — the specific customer site use (for example a bill-to or ship-to location) tied to the assignment; joins to HZ_CUST_SITE_USES_ALL.
• LOCATION_ID — the property location being allocated.
• TENANCY_ID and LEASE_ID — the tenancy and lease under which the space is assigned; join to PN_TENANCIES_ALL and PN_LEASES_ALL respectively.
• CUST_ASSIGN_START_DATE and CUST_ASSIGN_END_DATE — the effective period during which the assignment is in force.
• ALLOCATED_AREA_PCT, ALLOCATED_AREA, and UTILIZED_AREA — the percentage and measured quantities of space allocated and actually used.
• UOM_CODE — the unit of measure in which the area quantities are expressed.
• EXPENSE_ACCOUNT_ID — the GL account combination charged for the space; joins to GL_CODE_COMBINATIONS.
• PROJECT_ID and TASK_ID — the Oracle Projects project and task charged with the space; join to PA_PROJECTS_ALL and PA_TASKS.
• RECOVERY_SPACE_STD_CODE, RECOVERY_TYPE_CODE, and FIN_OBLIG_END_DATE — recovery-basis codes and the financial obligation end date used in rent and expense recovery processing.
• ORG_ID — the multi-org operating unit context, and CUST_SPACE_COMMENTS for free-text notes.

Standard EBS audit columns are present, including CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and the fifteen ATTRIBUTE (flexfield) columns with ATTRIBUTE_CATEGORY.

Common Use Cases and Queries

Typical reporting asks include customer space occupancy, recovery basis and account derivation, and reconciliation to lease and tenancy records. A representative occupancy query for a single tenancy is:

• SELECT csa.cust_account_id, csa.site_use_id, csa.allocated_area, csa.utilized_area, csa.uom_code FROM pn_space_assign_cust_all csa WHERE csa.tenancy_id = :tenancy_id AND :as_of_date BETWEEN csa.cust_assign_start_date AND csa.cust_assign_end_date;
• Join to HZ_CUST_ACCOUNTS (ON csa.cust_account_id = hca.cust_account_id) to resolve customer names for occupancy reports.
• Join to PN_LEASES_ALL and PN_TENANCIES_ALL (ON csa.lease_id = l.lease_id AND csa.tenancy_id = t.tenancy_id) to roll up assignments by lease or property.
• Join to PA_PROJECTS_ALL and PA_TASKS (ON csa.project_id = p.project_id AND csa.task_id = t.task_id) for project-charged space reporting.
• Filter by ORG_ID to restrict results to the operating unit, and by RECOVERY_TYPE_CODE or RECOVERY_SPACE_STD_CODE to isolate recoverable versus non-recoverable space.

Downstream recovery and receivables detail lines are keyed by CUST_SPACE_ASSIGN_ID, so the table also supports reconciliation of recovery or AR call activities back to the original space assignment.

Related Objects

The most significant referenced tables follow the documented foreign key graph:

• HZ_CUST_ACCOUNTS — via CUST_ACCOUNT_ID; provides the customer identity.
• HZ_CUST_SITE_USES_ALL — via SITE_USE_ID; identifies the customer site use.
• PN_TENANCIES_ALL — via TENANCY_ID; the tenancy that governs the assignment.
• PN_LEASES_ALL — via LEASE_ID; the underlying lease record.
• GL_CODE_COMBINATIONS — via EXPENSE_ACCOUNT_ID; the expense account combination.
• PA_PROJECTS_ALL and PA_TASKS — via PROJECT_ID and TASK_ID; project and task charging context.
• PN_REC_ARCL_DTLLN_ALL and PN_REC_EXPCL_DTLLN_ALL — these detail tables reference back to PN_SPACE_ASSIGN_CUST_ALL through their CUST_SPACE_ASSIGN_ID column, making them the primary dependent consumers of the assignment record.

These relationships position PN_SPACE_ASSIGN_CUST_ALL as a central junction between customer, property, project, and accounting entities within Oracle Property Manager.