Search Results pos_cont_addr_requests

Overview

POS_CONT_ADDR_REQUESTS is a transactional table in the POS schema, owned by the iSupplier Portal module in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores requests submitted through the supplier-facing iSupplier Portal to create, modify, or otherwise link supplier contacts and addresses. Each row represents a single request record that associates a supplier mapping with a contact party and a party site, tying together the contact-side and address-side request records that were generated when a supplier initiated a change through the portal. The table therefore acts as the junction that consolidates the two halves of a contact-and-address change workflow into a single trackable unit.

From a data modeling perspective, the ETRM metadata classifies this object heuristically as a link table. This classification is a modeling suggestion rather than a documented Oracle designation: the table exists to resolve and record relationships among suppliers, contacts, and addresses, and its identity and business meaning are derived from the entities it connects rather than from an intrinsic transactional lifecycle of its own.

Key Information Stored

The table contains 13 documented columns. The most significant are grouped below.

CONT_ADDR_REQUEST_ID — the surrogate primary key, enforced by the POS_CONT_ADDR_REQUEST_PK constraint and also surfaced through the unique index POS_CONT_ADDR_REQUEST_U1. It uniquely identifies each contact-and-address request record.
MAPPING_ID — references POS_SUPPLIER_MAPPINGS, identifying the supplier mapping (the supplier-to-user relationship) under which the request was raised.
CONTACT_PARTY_ID — references HZ_PARTIES, identifying the contact party associated with the request.
PARTY_SITE_ID — references HZ_PARTY_SITES, identifying the specific party site (address location) tied to the request.
CONTACT_REQ_ID — references POS_CONTACT_REQUESTS, linking the request to its contact-side request record.
ADDRESS_REQ_ID — references POS_ADDRESS_REQUESTS, linking the request to its address-side request record.
REQUEST_STATUS — the current processing state of the request (for example, pending, approved, or rejected), driving workflow routing and supplier visibility.
REQUEST_TYPE — the category of the request, distinguishing the kind of contact or address change being requested.
Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture who created and last modified the row and when, supporting audit and concurrency requirements.

The surrogate primary key CONT_ADDR_REQUEST_ID is the only documented business-key candidate; the remaining columns are foreign keys or descriptive attributes rather than alternate unique identifiers.

Common Use Cases and Queries

The table is primarily queried by iSupplier Portal administrators and support analysts tracking the status of supplier-submitted contact and address changes, and by integration developers reconciling portal requests against the resulting master records in the HZ (Trading Community Architecture) tables.

Monitoring open requests: SELECT cont_addr_request_id, request_type, request_status, creation_date FROM pos.pos_cont_addr_requests WHERE request_status = 'PENDING';
Resolving a request to its supplier and parties by joining to POS_SUPPLIER_MAPPINGS and HZ_PARTIES on MAPPING_ID and CONTACT_PARTY_ID.
Drill-through from a contact request or address request to its combined record using CONTACT_REQ_ID or ADDRESS_REQ_ID.
Reporting request volumes by status, type, and date for supplier onboarding dashboards.

Related Objects

POS_SUPPLIER_MAPPINGS — joined on MAPPING_ID; identifies the supplier mapping.
POS_CONTACT_REQUESTS — joined on CONTACT_REQ_ID; supplies the contact-side request detail.
POS_ADDRESS_REQUESTS — joined on ADDRESS_REQ_ID; supplies the address-side request detail.
HZ_PARTIES — joined on CONTACT_PARTY_ID; provides the contact party master record.
HZ_PARTY_SITES — joined on PARTY_SITE_ID; provides the party site and address location.

These foreign key relationships make POS_CONT_ADDR_REQUESTS a central link between the POS request tables and the HZ registry, and the natural starting point for any query tracing the lifecycle of a supplier contact-and-address change.

Table: POS_CONT_ADDR_REQUESTS 12.2.2
owner:POS, object_type:TABLE, fnd_design_data:POS.POS_CONT_ADDR_REQUESTS, object_name:POS_CONT_ADDR_REQUESTS, status:VALID, product: POS - iSupplier Portal , description: Requests for supplier contact and address links , implementation_dba_data: POS.POS_CONT_ADDR_REQUESTS ,
VIEW: POS.POS_CONT_ADDR_REQUESTS# 12.2.2
owner:POS, object_type:VIEW, object_name:POS_CONT_ADDR_REQUESTS#, status:VALID,
SYNONYM: APPS.POS_CONT_ADDR_REQUESTS 12.1.1
owner:APPS, object_type:SYNONYM, object_name:POS_CONT_ADDR_REQUESTS, status:VALID,
SYNONYM: APPS.POS_CONT_ADDR_REQUESTS 12.2.2
owner:APPS, object_type:SYNONYM, object_name:POS_CONT_ADDR_REQUESTS, status:VALID,
VIEW: POS.POS_CONT_ADDR_REQUESTS# 12.2.2
TABLE: POS.POS_CONT_ADDR_REQUESTS 12.2.2
owner:POS, object_type:TABLE, fnd_design_data:POS.POS_CONT_ADDR_REQUESTS, object_name:POS_CONT_ADDR_REQUESTS, status:VALID,
APPS.POS_PROFILE_CHANGE_REQUEST_PKG SQL Statements 12.2.2
TABLE: POS.POS_CONT_ADDR_REQUESTS 12.1.1
owner:POS, object_type:TABLE, object_name:POS_CONT_ADDR_REQUESTS, status:VALID,
APPS.POS_PROFILE_CHANGE_REQUEST_PKG SQL Statements 12.1.1
Table: POS_CONTACT_REQUESTS 12.2.2
owner:POS, object_type:TABLE, fnd_design_data:POS.POS_CONTACT_REQUESTS, object_name:POS_CONTACT_REQUESTS, status:VALID, product: POS - iSupplier Portal , description: Supplier Contact Requests , implementation_dba_data: POS.POS_CONTACT_REQUESTS ,
12.1.1 DBA Data 12.1.1
Table: POS_ADDRESS_REQUESTS 12.2.2
owner:POS, object_type:TABLE, fnd_design_data:POS.POS_ADDRESS_REQUESTS, object_name:POS_ADDRESS_REQUESTS, status:VALID, product: POS - iSupplier Portal , description: Supplier Address Requests , implementation_dba_data: POS.POS_ADDRESS_REQUESTS ,
Table: POS_SUPPLIER_MAPPINGS 12.2.2
owner:POS, object_type:TABLE, fnd_design_data:POS.POS_SUPPLIER_MAPPINGS, object_name:POS_SUPPLIER_MAPPINGS, status:VALID, product: POS - iSupplier Portal , description: References to supplier parties and/or supplier requests , implementation_dba_data: POS.POS_SUPPLIER_MAPPINGS ,
12.2.2 DBA Data 12.2.2
12.2.2 DBA Data 12.2.2
12.2.2 DBA Data 12.2.2
12.2.2 FND Design Data 12.2.2
12.1.1 DBA Data 12.1.1
PACKAGE BODY: APPS.POS_PARTY_MERGE_PKG 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:POS_PARTY_MERGE_PKG, status:VALID,
PACKAGE BODY: APPS.POS_PROFILE_CHANGE_REQUEST_PKG 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:POS_PROFILE_CHANGE_REQUEST_PKG, status:VALID,
PACKAGE BODY: APPS.POS_PARTY_MERGE_PKG 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:POS_PARTY_MERGE_PKG, status:VALID,
12.2.2 DBA Data 12.2.2
12.1.1 DBA Data 12.1.1
12.2.2 DBA Data 12.2.2
PACKAGE BODY: APPS.POS_PROFILE_CHANGE_REQUEST_PKG 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:POS_PROFILE_CHANGE_REQUEST_PKG, status:VALID,
PACKAGE BODY: APPS.POS_VENDOR_REG_PKG 12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:POS_VENDOR_REG_PKG, status:VALID,
PACKAGE BODY: APPS.POS_VENDOR_REG_PKG 12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:POS_VENDOR_REG_PKG, status:VALID,
APPS.POS_PARTY_MERGE_PKG SQL Statements 12.2.2
APPS.POS_PARTY_MERGE_PKG SQL Statements 12.1.1
PACKAGE BODY: APPS.POS_PROFILE_CHANGE_REQUEST_PKG 12.1.1
PACKAGE BODY: APPS.POS_PROFILE_CHANGE_REQUEST_PKG 12.2.2
Table: HZ_PARTY_SITES 12.2.2
owner:AR, object_type:TABLE, fnd_design_data:AR.HZ_PARTY_SITES, object_name:HZ_PARTY_SITES, status:VALID, product: AR - Receivables , description: Links party to physical locations , implementation_dba_data: AR.HZ_PARTY_SITES ,
APPS.POS_VENDOR_REG_PKG SQL Statements 12.1.1
APPS.POS_VENDOR_REG_PKG dependencies on POS_CONT_ADDR_REQUESTS 12.1.1
APPS.POS_PROFILE_CHANGE_REQUEST_PKG dependencies on POS_CONT_ADDR_REQUESTS 12.1.1
APPS.POS_PARTY_MERGE_PKG dependencies on POS_CONT_ADDR_REQUESTS 12.1.1
APPS.POS_VENDOR_REG_PKG dependencies on POS_CONT_ADDR_REQUESTS 12.2.2
APPS.POS_PARTY_MERGE_PKG dependencies on POS_CONT_ADDR_REQUESTS 12.2.2
APPS.POS_PROFILE_CHANGE_REQUEST_PKG dependencies on POS_CONT_ADDR_REQUESTS 12.2.2
APPS.POS_VENDOR_REG_PKG SQL Statements 12.2.2
PACKAGE BODY: APPS.POS_PARTY_MERGE_PKG 12.1.1
PACKAGE BODY: APPS.POS_PARTY_MERGE_PKG 12.2.2
Table: HZ_PARTIES 12.2.2
owner:AR, object_type:TABLE, fnd_design_data:AR.HZ_PARTIES, object_name:HZ_PARTIES, status:VALID, product: AR - Receivables , description: Information about parties such as organizations, people, and groups , implementation_dba_data: AR.HZ_PARTIES ,
eTRM - POS Tables and Views 12.2.2
description: This table is used during release 11i to release 12 upgrade. It stores vendor_ids of vendors who are considered in iSupplier Portal TCA Supplier upgrade scripts. ,
APPS.POS_PROFILE_CHANGE_REQUEST_PKG dependencies on FND_GLOBAL 12.1.1
APPS.POS_PROFILE_CHANGE_REQUEST_PKG dependencies on FND_GLOBAL 12.2.2
APPS.POS_PROFILE_CHANGE_REQUEST_PKG dependencies on PO_VENDORS 12.2.2
APPS.POS_PROFILE_CHANGE_REQUEST_PKG dependencies on PO_VENDORS 12.1.1
APPS.POS_PROFILE_CHANGE_REQUEST_PKG dependencies on POS_SUPPLIER_MAPPINGS 12.1.1
APPS.POS_PROFILE_CHANGE_REQUEST_PKG dependencies on POS_SUPPLIER_MAPPINGS 12.2.2