Requests: Causes/ Sub-Causes Setup

Navigation Path: Gear Icon > Company Setup > Requests Setup > Root Causes / Sub-Causes

The Root Causes / Sub-Causes page allows administrators to configure the available root cause analysis options used within both the Requests and CAR modules. Administrators can add custom root causes and sub-causes, toggle module availability, and import aerospace industry-standard codes to meet their organization's quality management requirements.

You will need the Requests Admin role to access and modify this setup page. Additionally, your account must have a Requests module license to use this functionality. If you do not have a Requests license, please contact [e-mail] for licensing information.

Enable and Require Root Causes and Sub-Causes

This checkbox controls whether root cause analysis fields appear in Requests records. When enabled:

• Cause and Sub-Cause fields are added to the Discrepancy tab
• These fields become required during the discrepancy documentation process
• Users must complete root cause analysis as part of their quality workflow

Important: This checkbox cannot be enabled if the Root Causes / Sub-Causes table is empty. You must first add root cause entries before enabling this functionality.

Managing Root Causes / Sub-Causes

Adding New Root Causes / Sub-Causes
Click the "+ ADD CAUSE" button to create new root cause entries individually. You can specify:

• The root cause name
• Associated sub-cause option
• Which modules should have access to the new entries
• Note: Root causes can be enabled for one module or both modules. To remove from both modules, please use the trash icon. Removed entries can be added back.

Editing Root Causes / Sub-Causes
Click the pencil icon (✏️) in any row to modify existing entries. You can:

• Change the root cause or sub-cause names (affects all records using these entries)
• Toggle availability for Requests module
• Toggle availability for CAR module

Removing Root Causes / Sub-Causes
Click the trash icon (🗑️) to remove entries. Important considerations:

• Removed entries no longer appear in dropdown selections
• Existing records retain their root cause designations even after removal
• Removed entries cannot be selected for new records

Restoring Removed Root Causes / Sub-Causes
To restore previously removed entries:

1. Check the "Show Removed" checkbox in the top-right corner
2. Locate the removed entry in the table
3. Click the yellow refresh button
4. The entry will become available again in the selected modules

 

Import and Export Functionality

Export
Click the "EXPORT" button to download the current root causes / sub-causes table as an Excel file for review and analysis. Note that exported files are for review purposes only and are not compatible for re-import.

Import
To understand the import functionality, please read this article: Requests: Importing Defects and Causes

AS9131 Standard Codes
The system provides AS9131 aerospace standard root cause codes to help your organization get started quickly. Below are benefits to utilizing these codes:

• Pre-defined industry-standard root cause categories
• Ensures compliance with aerospace quality requirements
• Can be customized for module availability
• Provides consistent terminology across organizations

Filter Options

Show Only Requests Causes
Check this box to filter the table to display only root causes that are enabled for the Requests module. This helps focus on entries relevant to the Requests workflow.

Show Removed
Check this box to display previously removed entries alongside active ones. Removed entries appear in the table but cannot be selected in dropdown menus until restored.

 

Impact on Existing Records

Name Changes: Immediately reflected on all existing records that use the modified root cause or sub-cause.

Module Toggles: Do not affect existing records but control future availability in dropdown selections.

Removed Entries: Existing records retain the root cause and sub-cause names but users cannot select removed entries for new records.

Module Integration: Changes to module availability affect both Requests and CAR applications simultaneously.

Enable/Disable Requirement: Changing the "Enable and Require" setting affects all existing Requests records - entries will be removed from Closed records.