Search Results locations
The PN_ADDRESSES_ALL
table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical data structure within the Property Manager (PN) module. It stores comprehensive address information for properties, lease agreements, and related entities managed in the system. This table serves as a centralized repository for all address-related data, ensuring consistency and accessibility across various transactional and reporting processes in Oracle EBS.
Table Structure and Key Columns
ThePN_ADDRESSES_ALL
table contains the following key columns:
- ADDRESS_ID: Primary key identifier for each address record.
- ADDRESS_LINE_1 to ADDRESS_LINE_4: Detailed street address components.
- CITY, STATE, POSTAL_CODE, PROVINCE, COUNTY: Geographic subdivisions of the address.
- COUNTRY: ISO country code for international addresses.
- STATUS: Indicates whether the address is active or inactive.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY: Standard Oracle audit columns.
Functional Integration
The table integrates with multiple Oracle EBS modules:- Property Manager (PN): Primary module utilizing this table for property and lease address storage.
- Accounts Payable (AP): Vendor address information may reference PN_ADDRESSES_ALL.
- Accounts Receivable (AR): Customer billing addresses may link to this table.
- General Ledger (GL): Legal entity addresses may be stored here.
Technical Considerations
Key technical aspects of the table include:- Multi-Org Architecture: The "_ALL" suffix indicates the table contains data for all operating units.
- Indexing Strategy: Typically indexed on ADDRESS_ID, COUNTRY, and POSTAL_CODE for performance.
- Validation Rules: Enforces address format standards through validation triggers.
- Storage Parameters: In 12.2.2, may utilize Oracle's Advanced Compression for space efficiency.
Data Relationships
The table maintains foreign key relationships with:PN_PROPERTIES_ALL
: Property location addressesPN_LEASES_ALL
: Lessor/Lessee addressesPN_LOCATIONS_ALL
: Physical location details
Customization Considerations
When extending the table:- Additional columns should follow Oracle's extension standards
- Custom validation logic must maintain data integrity
- Extensions should be registered in Oracle Application Developer
Upgrade Implications
Between 12.1.1 and 12.2.2:- Table structure remains largely consistent
- New validation rules may be introduced in 12.2.2
- Performance optimizations in later version
Best Practices
Recommended approaches for working with this table:- Use Oracle's address validation APIs rather than direct SQL
- Maintain address standardization across all modules
- Regularly purge obsolete addresses to maintain performance
PN_ADDRESSES_ALL
table represents a fundamental component of Oracle EBS's address management infrastructure, particularly within the Property Manager module. Its design reflects Oracle's comprehensive approach to global address handling, with flexibility to accommodate diverse international address formats while maintaining strict data integrity through relational constraints and validation logic.
-
Concurrent Program: PNLOCACT
12.1.1
execution_filename: pn_loc_status_change_pkg.activate_deact_location , product: PN - Property Manager , user_name: PNLOCACT , description: Activate / De-activate locations , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: PNLOCACT
12.2.2
execution_filename: pn_loc_status_change_pkg.activate_deact_location , product: PN - Property Manager , user_name: PNLOCACT , description: Activate / De-activate locations , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: PNEXPEAM
12.1.1
execution_filename: PN_EXP_TO_EAM_PVT.export_location_to_eam , product: PN - Property Manager , user_name: PNEXPEAM , description: Export Locations to Enterprise Asset Management , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: PNEXPCAD
12.1.1
execution_filename: PN_EXP_TO_CAD_ITF.exp_to_cad_itf , product: PN - Property Manager , user_name: PNEXPCAD , description: Export Locations and Space Allocations Data To CAD Interface , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: PNEXPEAM
12.2.2
execution_filename: PN_EXP_TO_EAM_PVT.export_location_to_eam , product: PN - Property Manager , user_name: PNEXPEAM , description: Export Locations to Enterprise Asset Management , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: PNEXPCAD
12.2.2
execution_filename: PN_EXP_TO_CAD_ITF.exp_to_cad_itf , product: PN - Property Manager , user_name: PNEXPCAD , description: Export Locations and Space Allocations Data To CAD Interface , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: PNIMPCAD
12.1.1
execution_filename: PN_CAD_IMPORT.import_cad , product: PN - Property Manager , user_name: PNIMPCAD , description: PN - Import Locations and Space Allocations Data From CAD Interface , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Concurrent Program: PNIMPCAD
12.2.2
execution_filename: PN_CAD_IMPORT.import_cad , product: PN - Property Manager , user_name: PNIMPCAD , description: PN - Import Locations and Space Allocations Data From CAD Interface , argument_method: Standard , enabled: Yes , execution_method: PL/SQL Stored Procedure ,
-
Lookup Type: PN_CITIES
12.1.1
product: PN - Property Manager , meaning: PN_CITIES , description: The lookup type for Cities in the Locations form. ,
-
Lookup Type: PN_CITIES
12.2.2
product: PN - Property Manager , meaning: PN_CITIES , description: The lookup type for Cities in the Locations form. ,
-
Table: PN_ADDRESSES_ALL
12.1.1
owner:PN, object_type:TABLE, fnd_design_data:PN.PN_ADDRESSES_ALL, object_name:PN_ADDRESSES_ALL, status:VALID, product: PN - Property Manager , description: Information on locations and service providers , implementation_dba_data: PN.PN_ADDRESSES_ALL ,
-
Table: PN_ADDRESSES_ALL
12.2.2
owner:PN, object_type:TABLE, fnd_design_data:PN.PN_ADDRESSES_ALL, object_name:PN_ADDRESSES_ALL, status:VALID, product: PN - Property Manager , description: Information on locations and service providers , implementation_dba_data: PN.PN_ADDRESSES_ALL ,
-
Table: PN_TENANCIES_HISTORY
12.2.2
owner:PN, object_type:TABLE, fnd_design_data:PN.PN_TENANCIES_HISTORY, object_name:PN_TENANCIES_HISTORY, status:VALID, product: PN - Property Manager , description: Track changes in the leased or subleased locations , implementation_dba_data: PN.PN_TENANCIES_HISTORY ,
-
Table: PN_TENANCIES_HISTORY
12.1.1
owner:PN, object_type:TABLE, fnd_design_data:PN.PN_TENANCIES_HISTORY, object_name:PN_TENANCIES_HISTORY, status:VALID, product: PN - Property Manager , description: Track changes in the leased or subleased locations , implementation_dba_data: PN.PN_TENANCIES_HISTORY ,
-
Table: PN_CONTACT_ASSIGNMENTS_ALL
12.1.1
owner:PN, object_type:TABLE, fnd_design_data:PN.PN_CONTACT_ASSIGNMENTS_ALL, object_name:PN_CONTACT_ASSIGNMENTS_ALL, status:VALID, product: PN - Property Manager , description: Llinks locations or leases with the site of a service provider. , implementation_dba_data: PN.PN_CONTACT_ASSIGNMENTS_ALL ,
-
Table: PN_CONTACT_ASSIGNMENTS_ALL
12.2.2
owner:PN, object_type:TABLE, fnd_design_data:PN.PN_CONTACT_ASSIGNMENTS_ALL, object_name:PN_CONTACT_ASSIGNMENTS_ALL, status:VALID, product: PN - Property Manager , description: Llinks locations or leases with the site of a service provider. , implementation_dba_data: PN.PN_CONTACT_ASSIGNMENTS_ALL ,
-
Table: PN_TENANCIES_ALL
12.1.1
owner:PN, object_type:TABLE, fnd_design_data:PN.PN_TENANCIES_ALL, object_name:PN_TENANCIES_ALL, status:VALID, product: PN - Property Manager , description: Information on leased or subleased locations , implementation_dba_data: PN.PN_TENANCIES_ALL ,
-
Table: PN_TENANCIES_ALL
12.2.2
owner:PN, object_type:TABLE, fnd_design_data:PN.PN_TENANCIES_ALL, object_name:PN_TENANCIES_ALL, status:VALID, product: PN - Property Manager , description: Information on leased or subleased locations , implementation_dba_data: PN.PN_TENANCIES_ALL ,
-
View: PN_LOCATIONS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PN.PN_LOCATIONS_V, object_name:PN_LOCATIONS_V, status:VALID, product: PN - Property Manager , description: This view is used as form view for the Locations form PNSULOCN.fmb used for defining space & its attributes , implementation_dba_data: APPS.PN_LOCATIONS_V ,
-
View: PN_LOCATIONS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PN.PN_LOCATIONS_V, object_name:PN_LOCATIONS_V, status:VALID, product: PN - Property Manager , description: This view is used as form view for the Locations form PNSULOCN.fmb used for defining space & its attributes , implementation_dba_data: APPS.PN_LOCATIONS_V ,