Search Results ozf_sd_res_cust_intf




Overview
Explore in AI Chat

Overview

The OZF_SD_RES_CUST_INTF table is a Trade Management (OZF) interface staging table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold customer details sent as part of a response — typically the inbound payload returned by an external source data (SD) system such as a third-party data provider, distributor, or point-of-sale feed. The table acts as an intermediate landing area where customer master attributes are captured before validation, enrichment, or transfer into the Oracle customer model.

From a modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. No enforced foreign keys or parent references are documented, so the table is best treated as an independent staging hub keyed by its own surrogate identifier. Each row represents one customer record as received in a response message, and rows are tracked through a processing status and error text rather than through relational dependencies on other OZF tables.

Key Information Stored

The table is documented with 34 columns. The primary key is defined by the constraint OZF_SD_RES_CUST_INTF_PK on RES_CUST_INTF_ID, and the same column also appears in the unique index OZF_SD_RES_CUST_INTF_U1. RES_CUST_INTF_ID therefore serves as the surrogate primary key and is the only documented business-key candidate, making it the natural join key for downstream processing.

  • RES_CUST_INTF_ID — surrogate identifier and primary key; the unique business-key candidate.
  • CUSTNAME — customer name as supplied in the response.
  • CUST_DUNS_NUMBER — D-U-N-S number used for customer identification and matching.
  • CUST_CAT_CODE — customer category code for classification.
  • CUST_EMAIL, CUST_TEL_NUMBER — primary contact email and telephone number.
  • PRTCCODE — partner or promotional reference code associated with the customer.
  • PADD_ADD1, PADD_ADD2, PADD_ADD3, PADD_CITY, PADD_COUNTRY, PADD_POSTAL_CODE, PADD_PO_BOX — the party address block (address lines, city, country, postal code, PO box) used for address validation and site creation.
  • REQUEST_NUMBER — correlates the row with the originating request or batch submission.
  • SITE_USE_CODE — indicates the intended site use (for example, bill-to or ship-to) for the address.
  • PROCESSED_FLAG — processing status indicator controlling re-processing.
  • ERROR_TXT — validation or import failure messaging for rejected rows.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield columns, available for client-specific extensions.

Common Use Cases and Queries

The principal use case is monitoring and troubleshooting an outbound customer data request and its corresponding response. Integration specialists query the table to find rows that failed processing, to re-drive them, and to reconcile the count of received customers against the count submitted. Typical patterns include:

  • Retrieving unprocessed rows: SELECT * FROM ozf.ozf_sd_res_cust_intf WHERE processed_flag = 'N'.
  • Isolating failures: SELECT res_cust_intf_id, custname, cust_duns_number, error_txt FROM ozf.ozf_sd_res_cust_intf WHERE error_txt IS NOT NULL.
  • Correlating a batch by request: SELECT * FROM ozf.ozf_sd_res_cust_intf WHERE request_number = :p_request_number.
  • De-duplicating received customers using the D-U-N-S number before customer import.
  • Reporting on response volumes and success rates by category code or site use code.

Because the table carries no documented FK relationships, joins are performed on the surrogate key or on REQUEST_NUMBER and CUST_DUNS_NUMBER via application logic rather than declarative constraints.

Related Objects

The metadata identifies this table as standalone, so related objects are inferred from the Trade Management response-processing flow rather than from enforced foreign keys.

  • OZF_SD_RES_CUST_INTF itself — the header/detail grouping of response customer lines keyed by RES_CUST_INTF_ID.
  • HZ_CUST_ACCOUNTS and HZ_PARTIES — the TCA tables into which validated customer and party records are ultimately loaded.
  • HZ_LOCATIONS and HZ_PARTY_SITES — TCA address targets populated from the PADD_* address columns and SITE_USE_CODE.
  • OZF_SD_REQ_* request-side interface tables — the outbound counterpart sharing REQUEST_NUMBER.
  • TCA APIs (for example, the customer account creation API) — the standard programmatic path for converting staged rows into TCA records.
  • Concurrent programs and interface error reporting views used to submit, monitor, and retry the response import.