Scenario: The user needs to request materials for stock, production, or project use.
Action: The user enters the item details, quantity, and purpose in the indent form.
Outcome: The system creates and saves a new purchase indent with a unique number.
Scenario: The user wants to provide the necessary information to complete the indent.
Action: The user enters the department, location, indent date, and item-wise quantity.
Outcome: The system validates and captures all details for further processing.
Scenario: The indent is related to a specific project, branch, or department.
Action: The user tags the indent with project code, branch, and department details.
Outcome: The system links the indent with the respective organisational units.
Scenario: The user needs to monitor the approval and processing status of the indent.
Action: The system assigns statuses like New, Approved, Rejected, Short-Closed, Cancelled, or Closed.
Outcome: The user tracks the current status and follows up for necessary actions.
Scenario: The indent requires internal approval before proceeding with procurement.
Action: The system routes the indent through the predefined approval workflow.
Outcome: The system updates the approval status and allows the next action.
Scenario: The approved indent is ready for conversion to requisition or purchase order.
Action: The user selects approved indents to generate enquiries or Purchase Orders.
Outcome: The system initiates procurement transactions based on indent data.
Scenario: The user needs to audit, track, or refer to past indents.
Action: The user opens indent records and checks linked transactions and status.
Outcome: The system displays historical data with references to follow-up documents.