Project

General

Profile

Bug #2941

Fix 500 Error While Posting Work Completion Certificate (WCC)

Added by Yashaditya Singh about 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
08/06/2026
Due date:
% Done:

0%

Estimated time:
Spent time:

Description

While posting a Work Completion Certificate (WCC), clicking the Confirm button in the confirmation dialog results in a 500 Internal Server Error, preventing the WCC from being posted successfully.

Steps to Reproduce:

Navigate to Works → Work Completions.
Open a WCC in Draft status.
Click the Post button.
In the confirmation dialog, click Confirm.
Observe the error.

Actual Result:

The API returns a 500 Internal Server Error when the Confirm button is clicked.
An error message is displayed: "An error occurred while posting the work completion certificate."
The WCC is not posted.

Expected Result:

The WCC should be posted successfully without any server error.
The corresponding station service expense should be created (if applicable), and the WCC status should be updated to Posted.
A success message should be displayed to the user.

Environment:

Module: Works → Work Completions
Action: Post Work Completion Certificate (WCC)
Issue Type: Backend/API (500 Internal Server Error)

#1

Updated by Yashaditya Singh about 2 months ago

I worked on the Accounts module by implementing and testing multiple enhancements. I added validation in the Work Order creation flow to ensure the Rate must be greater than 0 before allowing the record to be saved, and verified the corresponding API validation behavior. I also worked on the Service Bill module by implementing the auto-population of the Vendor Invoice Number based on the selected POSTED WCC, while ensuring the field is cleared when the vendor changes to prevent incorrect data. Additionally, I investigated and debugged the Stock Issue posting error related to insufficient warehouse stock by validating warehouse stock balances, goods receipt entries, stock ledger transactions, and warehouse mappings through database queries to identify the root cause.

Also available in: Atom PDF