Scenario:
The user needs to add new asset details based on the defined asset category and subcategory.
Action:
The user opens the Asset Master Cost Distribution screen, selects the asset type, and enters all required details such as asset code, asset name, and asset description.
Outcome:
The system saves the new asset details and displays the asset code and name in the left panel.
Scenario:
The user wants to search for a specific asset to view or update its details.
Action:
The user selects the appropriate asset type or enters the asset code.
Outcome:
The system displays the corresponding list of assets in the left panel for user selection.
Scenario:
The user must record the main details of an asset to ensure accurate tracking.
Action:
The user enters information such as asset code, name, description, location, department, and GRN number.
Outcome:
The system validates and saves the entered information for the selected asset.
Scenario:
The user needs to associate supplier and invoice information with the asset for financial records.
Action:
The user enters supplier name, quantity, invoice number, and selects or edits the invoice and capitalization dates.
Outcome:
The system updates the asset record with supplier and invoice details, linking them to the financial transaction.
Scenario:
The user defines the useful life and depreciation rate for an asset to calculate its value over time.
Action:
The user selects the useful life unit (years or days), enters the useful life, and specifies the depreciation percentage.
Outcome:
The system applies the defined depreciation rate during financial and accounting processes.
Scenario:
The user categorizes the asset based on its location, mode, and investment type.
Action:
The user selects the sub-location, asset mode, investment type, and shift details from the dropdown lists.
Outcome:
The system records the selected classification for reporting and depreciation tracking.
Scenario:
The user needs to update the mail server settings to ensure successful email delivery.
Action:
The user enters the existing mail server name and port, updates them with new details, and clicks Change.
Outcome:
The system saves the updated mail server configuration for future use.
Scenario:
The user needs to remove asset details that are no longer required and have no dependent transactions.
Action:
The user selects the asset type and asset name, clicks Delete, and confirms the deletion.
Outcome:
The system deletes the selected asset record after user confirmation.