Search Results request_deployment_mode

Overview

WSH_CC_REQUEST_SETUPS_V is an APPS-owned database view in the Oracle E-Business Suite Shipping Execution (WSH) module, valid in both 12.1.1 and 12.2.2. It exposes configuration data for Customs and Trade Compliance (CC) request setups, presenting the rules that determine which parties, applications, request handlers, and category sets are involved when compliance requests (such as ECCN or HTS classifications) are generated. Rather than requiring join logic against multiple HR, FND, and inventory tables, the view denormalizes the base setup table WSH_CC_REQUEST_SETUPS into a single queryable surface with resolved names, making it convenient for reporting, data extraction, and integration.

Underlying Base Objects

The view is defined over the base table WSH_CC_REQUEST_SETUPS (referenced via a synonym) and joins several supporting objects to resolve foreign keys into human-readable values. The documented referenced objects are:

• WSH_CC_REQUEST_SETUPS — the primary setup table holding each customs compliance request configuration record.
• HR_ORGANIZATION_UNITS (view) — joined twice to resolve the master organization and the requesting organization names.
• FND_USER — resolves the application user to a user name.
• FND_APPLICATION_TL — resolves the application to its translated application name.
• MTL_CATEGORY_SETS — outer-joined three times for ECCN, HTS, and additional category sets.
• HR_GENERAL and HR_SECURITY (packages) — used to enforce organization security on the returned records.

The view text is constructed as a UNION ALL, with a second branch substituting a null application user name, ensuring records without a valid user assignment still return.

Key Columns

• CC_REQUEST_SEQUENCE_ID — unique identifier for the request setup record; the primary lookup key.
• MASTER_ORGANIZATION_ID / MASTER_ORGANIZATION_NAME — the master organization and its resolved name.
• ORGANIZATION_ID / ORGANIZATION_NAME — the specific organization to which the setup applies.
• APPLICATION_ID / APPLICATION_NAME — the owning application and its translated name.
• APPLICATION_USER_ID / USER_NAME — the designated application user and resolved user name.
• REQUEST_TYPE_CODE, REQUEST_VERSION, REQUEST_LANGUAGE, REQUEST_DATE_FORMAT — parameters governing the generated request.
• REQUEST_DEPLOYMENT_MODE, REQUEST_HANDLER, REQUEST_OUTPUT_TYPE — how the request is processed and delivered.
• ADDITIONAL_ECE_COUNTRY_CHECK, REQUEST_INCLUDE_FLAG — compliance and inclusion flags.
• ECCN_CATG_SET_ID/CATEGORY_SET_NAME, HTS_CATG_SET_ID/CATEGORY_SET_NAME, ADDL_CATG_SET_ID/CATEGORY_SET_NAME — the category sets used for ECCN, HTS, and additional classification.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include auditing which compliance request setups exist per organization, validating that category sets and handlers are correctly assigned, and feeding downstream reporting. The view is preferable to querying the base table directly because names are pre-resolved and organization security is applied.

List all setups for a given organization:

SELECT cc_request_sequence_id,
       organization_name,
       request_type_code,
       request_handler,
       request_output_type
FROM   apps.wsh_cc_request_setups_v
WHERE  organization_id = :org_id;

Retrieve the category sets configured for compliance:

SELECT cc_request_sequence_id,
       eccn_catg_set_id, category_set_name,
       hts_catg_set_id,  category_set_name,
       addl_catg_set_id, category_set_name
FROM   apps.wsh_cc_request_setups_v
WHERE  request_include_flag = 'Y';

Because the view is read-only and exposes a stable column set across 12.1.1 and 12.2.2, it is well suited to custom reports and integrations that must remain consistent across upgrades.