Search Results mtl_category_sets

Overview

WSH_CC_REQUEST_SETUPS_V is an APPS-owned reporting view in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that presents configuration data for Oracle Shipping cross-country (also referred to as "cross-customs" or CC) request setups. It exposes one row per defined cross-country request setup, combining request-level configuration attributes with resolved descriptive names for the operating unit, master organization, application, application user, and the category sets referenced by each setup. Because it resolves numeric identifiers and category set IDs into human-readable names, the view is intended for reporting, inquiry, and integration extraction rather than transaction processing.

Underlying Base Objects

The documented base objects are WSH_CC_REQUEST_SETUPS (SYNONYM), HR_ORGANIZATION_UNITS (VIEW), FND_APPLICATION_TL (SYNONYM), FND_USER (SYNONYM), MTL_CATEGORY_SETS (SYNONYM), HR_GENERAL (PACKAGE), and HR_SECURITY (PACKAGE).

• WSH_CC_REQUEST_SETUPS provides the driving rows and most of the setup columns, including request type, version, language, date format, deployment mode, handler, and output type.
• HR_ORGANIZATION_UNITS is joined twice to resolve the master organization name (HOU1) and the operating organization name (HOU2).
• FND_APPLICATION_TL resolves the application ID to an application name via the foundation application translation table.
• FND_USER resolves the application user ID to a user name.
• MTL_CATEGORY_SETS is joined three times, using outer joins, to resolve the ECCN category set, HTS category set, and additional category set IDs into category set names. HR_GENERAL and HR_SECURITY support organization security and name resolution semantics inherited from the HR organization model.

Key Columns

The view exposes the following columns. CC_REQUEST_SEQUENCE_ID is the primary sequence identified. MASTER_ORGANIZATION_ID and MASTER_ORGANIZATION_NAME identify the master organization associated with the setup, while ORGANIZATION_ID and ORGANIZATION_NAME identify the operating organization.

• APPLICATION_ID and APPLICATION_NAME identify the owning application; APPLICATION_USER_ID and USER_NAME identify the application user.
• REQUEST_TYPE_CODE, REQUEST_VERSION, REQUEST_LANGUAGE, REQUEST_DATE_FORMAT, REQUEST_DEPLOYMENT_MODE, REQUEST_HANDLER, REQUEST_OUTPUT_TYPE, and ADDITIONAL_ECE_COUNTRY_CHECK describe the cross-country request behavior and formatting.
• REQUEST_INCLUDE_FLAG indicates whether the request is included in processing.
• ECCN_CATG_SET_ID with CAT1.CATEGORY_SET_NAME, HTS_CATG_SET_ID with CAT2.CATEGORY_SET_NAME, and ADDL_CATG_SET_ID with CAT3.CATEGORY_SET_NAME are the three category set references resolved through MTL_CATEGORY_SETS.
• Standard audit columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN, plus the ROW_ID pseudo-column.

Common Use Cases and Queries

The view is typically queried when auditing which category sets (ECCN, HTS, and additional) are assigned to cross-country request setups for a given organization. A simple lookup follows.

• SELECT CC_REQUEST_SEQUENCE_ID, ORGANIZATION_NAME, MASTER_ORGANIZATION_NAME, REQUEST_TYPE_CODE, CATEGORY_SET_NAME_ECCN, CATEGORY_SET_NAME_HTS FROM APPS.WSH_CC_REQUEST_SETUPS_V WHERE ORGANIZATION_ID = :org_id.
• Joining through MTL_CATEGORY_SETS to validate that a category set is active and assigned to the expected structure prior to request execution.
• Reporting on request handler and output type by operating unit to standardize request deployment across legal entities.

The view is a read-only query structure; because it resolves names through joins with outer joins on the category sets, setups with no assigned category set return null category set names rather than being excluded. This makes it reliable for complete population reporting.