Search Results recovery_space_std_desc

Overview

PN_SPACE_ASSIGN_CUST_V is a reporting view in the Oracle E-Business Suite Property Manager (PN) module, owned by the APPS schema and shipped with a VALID status in both the 12.1.1 and 12.2.2 releases. It denormalizes the customer space assignment entity into a single, query-friendly row that combines lease-backed property locations with the customer records occupying them. Rather than joining PN_SPACE_ASSIGN_CUST to the property location, lease, and Oracle Trading Community Architecture (TCA) tables directly, developers, report authors, and integration interfaces query this view to obtain one consolidated line per customer space assignment, including descriptive customer attributes such as category, class, and profile class.

The view is read-only in practice and is intended for reporting, concurrent program output, and inbound/outbound integrations that need to resolve a space assignment to its customer master data. Because it also exposes WHO columns, descriptive flexfield attributes (ATTRIBUTE_CATEGORY through ATTRIBUTE15), and recovery/lease attributes, it is frequently used as the source for leased-space occupancy reports and for reconciliation between Property Manager and Receivables or Lease Management.

Underlying Base Objects

The view is defined over eleven documented objects. PN_SPACE_ASSIGN_CUST is the driving base table, supplying the assignment identifier, allocated and utilized area, assignment dates, comments, descriptive flexfield columns, and the LEASE_ID foreign key. PN_LOCATIONS contributes location detail, including LOCATION_CODE, SUITE, LOCATION_TYPE_LOOKUP_CODE, UOM_CODE, ORG_ID, and the location's active date range. PN_LEASES provides the lease name through the PLE alias.

Customer data is sourced from the TCA layer: HZ_CUST_ACCOUNTS_ALL supplies the account and STATUS, HZ_PARTIES supplies PARTY_NAME and SIC_CODE, HZ_CUST_SITE_USES_ALL supplies the customer site location, HZ_CUSTOMER_PROFILES supplies the profile class, and HZ_CUST_PROFILE_CLASSES, exposed as HCPC.NAME, supplies PROFILE_CLASS. Three lookup sources provide decoded values: FND_LOOKUPS supplies the customer class meaning (L_CLASS.MEANING) and the customer category meaning (L_CAT.MEANING), AR_LOOKUPS supplies the recovery type description, and a lookup supplies RECOVERY_SPACE_STD_DESC. FND_GLOBAL is referenced as a package, typically for session or organization context in the view's WHERE clause.

Key Columns

• CUST_SPACE_ASSIGN_ID, LOCATION_ID, LEASE_ID — primary and foreign keys linking the assignment to its location and lease.
• CUST_ACCOUNT_ID, SITE_USE_ID, CUSTOMER_NAME, CUSTOMER_SITE — the customer account, the specific site use, and the resolved party name and site address.
• CUSTOMER_CLASS, CUSTOMER_CATEGORY — decoded lookup meanings (L_CLASS.MEANING and L_CAT.MEANING) that answer the common "customer_class" search term directly.
• PROFILE_CLASS, SIC_CODE, STATUS — profile classification, industry code, and customer account status.
• CUST_ASSIGN_START_DATE, CUST_ASSIGN_END_DATE — effective period of the customer's occupancy.
• ALLOCATED_AREA, ALLOCATED_AREA_PCT, UTILIZED_AREA, UOM_CODE — area metrics and unit of measure for the assigned space.
• RECOVERY_SPACE_STD_CODE, RECOVERY_TYPE_DE, RECOVERY_SPACE_STD_DESC — recovery terms applied to the assignment.
• ORG_ID — multi-org operating unit context, carried from PN_LOCATIONS.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield values for site-specific extensions.

Common Use Cases and Queries

A frequent scenario is listing all customer space assignments with their decoded class and category for a given operating unit, which maps directly to the "customer_class" search:

SELECT cust_space_assign_id,
       customer_name,
       customer_class,
       customer_category,
       profile_class,
       allocated_area,
       uom_code
FROM   apps.pn_space_assign_cust_v
WHERE  org_id = :p_org_id
AND    NVL(cust_assign_end_date, SYSDATE + 1) > SYSDATE
ORDER  BY customer_name;

Another common pattern reconciles active occupancy against lease terms, joining LEASE_NAME and the assignment dates to confirm that a customer's occupancy window falls within the lease period. Because the view already resolves HZ_PARTIES and HZ_CUST_ACCOUNTS_ALL, reports can group area by customer class or SIC_CODE without additional TCA joins. Integration interfaces that feed an external occupancy or chargeback system typically select the assignment ID, customer account, location code, allocated area, and the flexfield attributes, using CUST_SPACE_ASSIGN_ID as the unique integration key. Consumers should note the view is defined in APPS and that all synonyms resolve to the TCA and PN base objects, so grants must follow standard EBS read-only conventions.