Search Results ozf_sd_res_cust_intf_u1

Overview

The table OZF.OZF_SD_RES_CUST_INTF is a transactional interface table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It belongs to the Order Capture Foundation (OZF) schema where it stores customer detail rows received as part of a response payload from an external or upstream system. Specifically, the object functions as an inbound staging area for customer master data, contact information, and address attributes that must be validated and subsequently processed into the appropriate EBS entities.

The table stores data in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, indicating it is maintained within the transactional data area of the Applications database. The heuristic Data Vault classification mined from the documented foreign key structure indicates this object is a standalone entity. In Data Vault modeling terms, this suggests it behaves less like a link that resolves many-to-many relationships and more like a hub or satellite, capturing a unique business identifier with descriptive attributes. The unique index OZF_SD_RES_CUST_INTF_U1 on the RES_CUST_INTF_ID column reinforces this hub-like behavior by enforcing uniqueness on the primary identifier. Because it is an interface table, records typically carry a short lifecycle: they are inserted by an inbound process, marked as processed or failed, and then consumed or purged by a concurrent program.

Key Information Stored

The primary surrogate key for this table is RES_CUST_INTF_ID, which is also the single column that constitutes the primary key OZF_SD_RES_CUST_INTF_PK and the unique index OZF_SD_RES_CUST_INTF_U1. This identifier is the business-key candidate documented for the object and the column most likely to be referenced by associated processing logic.

The most significant descriptive columns include:

• CUSTNAME – the customer name, stored as a VARCHAR2(360).
• CUST_DUNS_NUMBER – the Data Universal Numbering System identifier for the customer.
• CUST_CAT_CODE – the category code assigned to the customer.
• CUST_EMAIL – the customer email address.
• CUST_TEL_NUMBER – the customer telephone number.
• PRTCCODE – the partner classification code for the customer.
• PADD_ADD1, PADD_ADD2, PADD_ADD3, PADD_CITY, PADD_COUNTRY, PADD_POSTAL_CODE, PADD_PO_BOX – the physical address components, including city, country, postal code, and PO box.
• REQUEST_NUMBER – the request number associated with the inbound response.
• SITE_USE_CODE – the site use code for the customer location.
• PROCESSED_FLAG – indicates whether the row has been processed.
• ERROR_TXT – the error reason recorded when row processing fails.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – descriptive flexfield structure and segment columns for extensibility.

These columns allow the interface to preserve both standard customer fields and customer-specific extensions before they are transformed into production customer records.

Common Use Cases and Queries

Typical use cases center on monitoring inbound integration health, diagnosing failures, and reconciling loaded versus rejected customer records. A frequent query filters on the processing status to identify unprocessed rows:

• Pending workload: SELECT RES_CUST_INTF_ID, CUSTNAME, REQUEST_NUMBER FROM OZF.OZF_SD_RES_CUST_INTF WHERE PROCESSED_FLAG IS NULL OR PROCESSED_FLAG = 'N';
• Error analysis: SELECT RES_CUST_INTF_ID, CUSTNAME, ERROR_TXT FROM OZF.OZF_SD_RES_CUST_INTF WHERE ERROR_TXT IS NOT NULL;
• Request-level reconciliation: SELECT REQUEST_NUMBER, COUNT(*) FROM OZF.OZF_SD_RES_CUST_INTF GROUP BY REQUEST_NUMBER ORDER BY REQUEST_NUMBER;

Reporting scenarios include throughput tracking by request number, duplicate detection by CUST_DUNS_NUMBER or CUSTNAME, and validation of address completeness before downstream customer creation. Because the table resides in APPS_TS_TX_DATA, queries should be tuned with appropriate filtering to avoid full scans on the transactional tablespace.

Related Objects

The documented relationship data classifies this object as standalone with no foreign key dependencies mined from the physical schema. Its principal related object is the unique index OZF_SD_RES_CUST_INTF_U1, which enforces uniqueness on RES_CUST_INTF_ID alongside the primary key OZF_SD_RES_CUST_INTF_PK. Downstream, the records staged here are consumed by EBS concurrent programs and customer interface routines that read PROCESSED_FLAG, ERROR_TXT, and the customer attribute columns before inserting into the production customer and site tables within the Trading Community Architecture (TCA) model, such as HZ_CUST_ACCOUNTS and HZ_PARTIES. The REQUEST_NUMBER and SITE_USE_CODE columns provide the linkage points used by those processing routines to associate interface rows with the originating request and the target customer site usage. The ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 flexfield columns allow the interface to be extended to map additional attributes required by the receiving process.