Skip to content

analysis.md

Latest commit

 

History

History
88 lines (64 loc) · 2.79 KB

analysis.md

File metadata and controls

88 lines (64 loc) · 2.79 KB

Analysis of Support Tickets for Order Management System

Ticket 1: Unusually High Order Amount

Ticket Description:
Customer reports that Order 102 shows an unusually high amount.

SQL Query Used:
SELECT *
FROM orders
WHERE amount > 1000;

Findings:
The query returned Order 102 with an amount of 9999.99, which is significantly higher than typical order values.

Likely Root Cause:
This appears to be a data entry error or incorrect value entered into the system.

Recommended Next Steps:

  • Confirm with the customer or sales team what the correct amount should be.
  • Update the order amount if necessary.
  • Add validation rules to prevent extremely large values in the future.

Ticket 2: Order Appears Without Customer Details

Ticket Description:
Order 103 appears in reports, but the customer details are blank.

SQL Query Used:
SELECT o.*, c.customer_name, c.region
FROM orders o
LEFT JOIN customers c
ON o.customer_id = c.customer_id
WHERE c.customer_id IS NULL;

Findings:
Order 103 has a customer_id of 4, but there is no matching customer record in the customers table. The customer fields return NULL.

Likely Root Cause:
This is a data integrity issue. The order was created with a customer ID that does not exist.

Recommended Next Steps:

  • Identify the correct customer for this order.
  • Update the order with the correct customer_id.
  • Implement validation to prevent orders from being created with invalid customer IDs.

Ticket 3: Negative Order Amounts

Ticket Description:
Finance team reports negative order amounts in their export.

SQL Query Used:
SELECT *
FROM orders
WHERE amount < 0;

Findings:
The query returned an order with an amount of -10.00.

Likely Root Cause:
This is likely a data entry mistake or a system bug that allowed negative values.

Recommended Next Steps:

  • Correct the negative amount.
  • Review system logic to ensure negative values are not allowed.
  • Add validation to prevent negative amounts during order creation.

Ticket 4: Zero Amount Orders Still Pending

Ticket Description:
Some orders show 0.00 amount but are still in Pending status.

SQL Query Used:
SELECT *
FROM orders
WHERE amount = 0
AND status = 'Pending';

Findings:
The query returned an order with a 0.00 amount and a status of Pending.

Likely Root Cause:
This may be an incomplete order, a test order, or a user who abandoned the process before entering an amount.

Recommended Next Steps:

  • Verify whether this order is legitimate or a test.
  • Contact the user if needed.
  • Add system checks to prevent orders from being saved with zero amounts unless explicitly allowed.