Results for “workflow_item_type”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
WSH_EXCEPTION_DEFINITIONS_B is the base (language-independent) definition table for exception definitions within the Oracle E-Business Suite Shipping Execution (WSH) module. It stores the master record for every shipping exception that the system can raise, track, and manage — such as delivery holds, pick confirmations issues, or shipment discrepancies. Each row defines a reusable exception "template" that shipping operations reference when generating runtime exceptions. The table is the foundation of the exception framework in WSH, controlling severity, handling behavior, and workflow integration.
In Oracle EBS 12.1.1 and 12.2.2, this table is owned by the WSH schema and carries 31 documented columns, including the standard audit columns and a set of flexible attribute (descriptive flexfield) columns. Its heuristic Data Vault classification is hub-leaning, which suggests it functions primarily as a business-key hub: the stable identifier (EXCEPTION_DEFINITION_ID) anchors relationships, while descriptive properties and translations attach through satellite and translation tables. The presence of the ZD_EDITION_NAME column reflects the editioning framework introduced in 12.2.x for online patching.
Key Information Stored
The primary key is WSH_EXCEPTION_DEFINITIONS_B_PK, defined on EXCEPTION_DEFINITION_ID, a surrogate system-generated identifier. A unique business-key candidate is captured by WSH_EXCEPTION_DEFINITIONS_B_U1 (EXCEPTION_DEFINITION_ID, ZD_EDITION_NAME), which supports the editioning model used in multi-tenant patching.
- EXCEPTION_DEFINITION_ID — surrogate primary key uniquely identifying each exception definition.
- EXCEPTION_TYPE — categorizes the exception (e.g., delivery, pick, manifest).
- DEFAULT_SEVERITY — the default severity level assigned when the exception is raised.
- EXCEPTION_HANDLING — controls how the exception should be handled by the system.
- WORKFLOW_ITEM_TYPE and WORKFLOW_PROCESS — the Oracle Workflow item type and process invoked when workflow is enabled.
- INITIATE_WORKFLOW — flag indicating whether workflow should be started for this exception.
- UPDATE_ALLOWED — determines whether the exception definition can be modified.
- ENABLED — flag controlling whether the definition is active and usable.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns for extensibility.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
- ZD_EDITION_NAME — edition identifier used by the 12.2.x editioning framework.
Common Use Cases and Queries
This table is queried when configuring or auditing shipping exception rules, and when joining to the translation table to retrieve user-facing names and descriptions. Reporting scenarios include identifying enabled exceptions, reviewing workflow-enabled exceptions, and validating flexfield usage. Typical SQL:
- List enabled exception definitions:
SELECT EXCEPTION_DEFINITION_ID, EXCEPTION_TYPE, DEFAULT_SEVERITY FROM WSH.WSH_EXCEPTION_DEFINITIONS_B WHERE ENABLED = 'Y'; - Find workflow-driven exceptions:
SELECT EXCEPTION_DEFINITION_ID, WORKFLOW_ITEM_TYPE, WORKFLOW_PROCESS FROM WSH.WSH_EXCEPTION_DEFINITIONS_B WHERE INITIATE_WORKFLOW = 'Y'; - Join to translations:
SELECT B.EXCEPTION_DEFINITION_ID, T.NAME FROM WSH.WSH_EXCEPTION_DEFINITIONS_B B, WSH.WSH_EXCEPTION_DEFINITIONS_TL T WHERE B.EXCEPTION_DEFINITION_ID = T.EXCEPTION_DEFINITION_ID;
Related Objects
The most significant related object is the translation table, joined through the documented foreign key:
- WSH_EXCEPTION_DEFINITIONS_TL — holds the language-specific name and description; joined on EXCEPTION_DEFINITION_ID.
- Runtime shipping exception tables in the WSH schema that reference definitions when exceptions are raised against deliveries, trips, and containers (joined via EXCEPTION_DEFINITION_ID).
- Oracle Workflow object (WF_ITEM_TYPES) referenced through WORKFLOW_ITEM_TYPE.
- Shipping Execution setup and query views built over WSH_EXCEPTION_DEFINITIONS_B for the Shipping Transactions and exception inquiry forms.
-
Base Exception Definitions
-
Parameters for the main workflow process of the Business Rule Monitor.
-
APPS.WSH_EXCEPTION_DEFINITIONS_VL·↳ WSH_EXCEPTION_DEFINITIONS_B·↳ WSH_EXCEPTION_DEFINITIONS_TL·Explore WSH module →
-
View: JTF_BRM_PARAMETERS_V 12.2.2
View used for the business rule monitor form.
APPS.JTF_BRM_PARAMETERS_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ JTF_BRM_PARAMETERS·Explore JTF module →
-
This table stores territory group data
-
View: PA_EGO_LC_PHASES_V 12.2.2
- Retrofitted
APPS.PA_EGO_LC_PHASES_V·↳ PA_PROJECT_STATUSES·Explore PA module →
-
Change Management Actions
-
The staging table used by the collection program to validate and process data for table MSC_BIS_TARGET_LEVELS
-
Parameters for the main workflow process of the Business Rule Monitor.
-
This table stores territory group data
-
View: JTF_BRM_PARAMETERS_V 12.1.1
View used for the business rule monitor form.
APPS.JTF_BRM_PARAMETERS_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ JTF_BRM_PARAMETERS·Explore JTF module →
-
Base Exception Definitions
-
MSC_BIS_TARGET_LEVELS contains different combinations of dimension levels to be applied simultaneously to get a performance indicator relevant to a particular reporting need. For example, if someone wants to know sales revenues broken down
-
View: ENG_CHANGE_ACTIONS_VL 12.1.1
APPS.ENG_CHANGE_ACTIONS_VL·↳ ENG_CHANGE_ACTIONS·↳ ENG_CHANGE_ACTIONS_TL·Explore ENG module →
-
View: PA_PROJECT_STATUSES_V 12.1.1
This view provides the control items statuses.
APPS.PA_PROJECT_STATUSES_V·↳ PA_PROJECT_STATUSES·Explore PA module →
-
APPS.WSH_EXCEPTION_DEFINITIONS_V·↳ FND_LOOKUP_VALUES_VL·↳ WSH_EXCEPTION_DEFINITIONS_VL·Explore WSH module →
-
In this table a workflow process is linked to a business rule.
-
MSC_BIS_TARGET_LEVELS contains different combinations of dimension levels to be applied simultaneously to get a performance indicator relevant to a particular reporting need. For example, if someone wants to know sales revenues broken down
-
APPS.WSH_EXCEPTION_DEFINITIONS_VL·↳ WSH_EXCEPTION_DEFINITIONS_B·↳ WSH_EXCEPTION_DEFINITIONS_TL·Explore WSH module →
-
View: POR_HEADER_V 12.2.2
Requisition Header View
APPS.POR_HEADER_V·↳ AP_CARDS·↳ FND_GLOBAL·↳ FND_PROFILE·Explore ICX module →
-
APPS.WSH_EXCEPTION_DEFINITIONS_V·↳ FND_LOOKUP_VALUES_VL·↳ WSH_EXCEPTION_DEFINITIONS_VL·Explore WSH module →
-
View: BISBV_TARGET_LEVELS 12.1.1
APPS.BISBV_TARGET_LEVELS·↳ BIS_TARGET_LEVELS·↳ BIS_TARGET_LEVELS_TL·Explore BIS module →
-
View: PA_EGO_LC_PHASES_V 12.1.1
- Retrofitted
APPS.PA_EGO_LC_PHASES_V·↳ PA_PROJECT_STATUSES·Explore PA module →
-
In this table a workflow process is linked to a business rule.
-
View: CSD_REPAIR_TYPES_VL 12.1.1
This is the VL view of the Repair Types.
APPS.CSD_REPAIR_TYPES_VL·↳ CSD_FLOW_STATUSES_B·↳ CSD_REPAIR_TYPES_B·↳ CSD_REPAIR_TYPES_TL·Explore CSD module →
-
View: JTF_BRM_RULES_V 12.2.2
View used for the business rule workbench form.
APPS.JTF_BRM_RULES_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ JTF_BRM_PROCESSES·Explore JTF module →
-
View: JTF_BRM_RULES_V 12.1.1
View used for the business rule workbench form.
APPS.JTF_BRM_RULES_V·↳ FND_GLOBAL·↳ FND_LOOKUPS·↳ JTF_BRM_PROCESSES·Explore JTF module →
-
Change Management Actions
-
View: PA_PROJECT_STATUSES_V 12.2.2
This view provides the control items statuses.
APPS.PA_PROJECT_STATUSES_V·↳ PA_PROJECT_STATUSES·Explore PA module →
-
This table stores all the repair types.
-
View: POR_HEADER_V 12.1.1
Requisition Header View
APPS.POR_HEADER_V·↳ AP_CARDS·↳ FND_GLOBAL·↳ FND_PROFILE·Explore ICX module →
-
The staging table used by the collection program to validate and process data for table MSC_BIS_TARGET_LEVELS
-
View: ENG_CHANGE_ACTIONS_VL 12.2.2
APPS.ENG_CHANGE_ACTIONS_VL·↳ ENG_CHANGE_ACTIONS·↳ ENG_CHANGE_ACTIONS_TL·Explore ENG module →
-
View: PA_PROJ_STATUSES_V 12.2.2
This view provides the project statuses.
APPS.PA_PROJ_STATUSES_V·↳ PA_LOOKUPS·↳ PA_PROJECT_STATUSES·Explore PA module →
-
View: CSD_REPAIR_TYPES_VL 12.2.2
This is the VL view of the Repair Types.
APPS.CSD_REPAIR_TYPES_VL·↳ CSD_FLOW_STATUSES_B·↳ CSD_REPAIR_TYPES_B·↳ CSD_REPAIR_TYPES_TL·Explore CSD module →
-
Valid project status codes
-
Valid project status codes
-
View: BISVV_TARGETS 12.1.1
APPS.BISVV_TARGETS·↳ BIS_BUSINESS_PLANS·↳ BIS_BUSINESS_PLANS_TL·↳ BIS_TARGET_LEVELS·Explore BIS module →
-
This table stores all the repair types.
-
View: BISFV_TARGET_LEVELS 12.1.1
APPS.BISFV_TARGET_LEVELS·↳ BIS_DIMENSION_LEVEL_PUB·↳ BIS_INDICATORS·↳ BIS_INDICATORS_TL·Explore BIS module →
-
VIEW: JTF.JTF_BRM_PROCESSES# 12.2.2