Search Results wsh_cc_request_setups_pk

Overview

WSH_CC_REQUEST_SETUPS is a Shipping Execution (WSH) configuration table that stores request setup information used by the Oracle EBS Trade Compliance / Export Compliance engine. It defines the parameters, output characteristics, and classification category sets applied when compliance or country-of-origin screening requests are generated and dispatched from the shipping execution flow. Each row represents a discrete request definition — including the request type, version, deployment mode, handler, and output type — that governs how a compliance screening request is constructed, executed, and delivered. In EBS 12.1.1 and 12.2.2, the table supports the interaction between shipping transactions (deliveries, trips, ship-confirm processing) and the compliance screening layer (the so-called CC, or Compliance Check, request framework).

From a Data Vault modeling perspective, the mined FK structure classifies WSH_CC_REQUEST_SETUPS as standalone. No foreign-key dependents were identified, which suggests it is best modeled as a standalone hub or reference satellite rather than a link table; because it carries descriptive setup attributes alongside its identifier, a satellite-style treatment around the CC_REQUEST_SEQUENCE_ID business key is a reasonable modeling suggestion.

Key Information Stored

The documented physical schema comprises 22 columns owned by WSH. The most significant are:

• CC_REQUEST_SEQUENCE_ID — the surrogate primary key, enforced by WSH_CC_REQUEST_SETUPS_PK. It uniquely identifies each request setup record.
• MASTER_ORGANIZATION_ID / ORGANIZATION_ID — the operating unit or inventory organization scope under which the request setup applies.
• APPLICATION_ID / APPLICATION_USER_ID — the owning application and the responsible user for the request definition.
• REQUEST_TYPE_CODE / REQUEST_VERSION — the compliance request category and version, distinguishing screening types and their revision level.
• REQUEST_LANGUAGE / REQUEST_DATE_FORMAT / REQUEST_DEPLOYMENT_MODE — presentation and execution attributes controlling locale and runtime behavior.
• REQUEST_HANDLER / REQUEST_OUTPUT_TYPE — the handler program and the format in which output is produced.
• REQUEST_INCLUDE_FLAG — an inclusion toggle governing whether the request participates in processing.
• ADDITIONAL_ECE_COUNTRY_CHECK, ECCN_CATG_SET_ID, ADDL_CATG_SET_ID, HTS_CATG_SET_ID — compliance classification configuration, referencing ECCN, additional category, and HTS (Harmonized Tariff Schedule) category sets.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

The documented primary key is the only unique identifier cited; no separate business-key unique index is documented in the metadata, so CC_REQUEST_SEQUENCE_ID serves as both surrogate and operational lookup key.

Common Use Cases and Queries

Typical scenarios include auditing the active compliance request configurations for an organization, verifying which category sets (ECCN, HTS, additional) are attached to a request, and troubleshooting why a screening request did not execute. A representative query:

• SELECT cc_request_sequence_id, organization_id, request_type_code, request_version, request_handler, request_output_type FROM wsh.wsh_cc_request_setups WHERE organization_id = :org_id AND request_include_flag = 'Y';
• Join to audit columns to trace recent configuration changes: WHERE last_update_date >= :from_date.
• Reporting on classification coverage: SELECT request_type_code, eccn_catg_set_id, hts_catg_set_id FROM wsh.wsh_cc_request_setups;

Related Objects

The mined relationship data classifies this table as standalone, with no documented FK dependents. Related objects are therefore identified by shared WSH domain context rather than enforced joins:

• WSH_DELIVERY_ASSIGNMENTS / WSH_DELIVERIES — supplies the shipping context that triggers compliance screening requests.
• WSH_TRIPS / WSH_TRIP_STOPS — transportation context for export screening.
• Compliance category set tables (ECCN, HTS, additional category sets referenced by the CATG_SET_ID columns) — used to resolve classification values.
• FND_APPLICATION / FND_USER — resolve APPLICATION_ID and APPLICATION_USER_ID.
• Concurrent program / request tables — the REQUEST_HANDLER feeds the standard concurrent manager submission framework.

Because no FK constraints are documented, joins in custom reporting should be constructed on organization and request-type columns rather than on assumed referential relationships.