Scenario:
The business enters into a formal agreement with a customer to supply goods over a defined period or quantity.
Action:
The user creates a sales contract in the system by entering customer details, contract validity, and supply terms.
Outcome:
The system generates a contract order and stores it for reference in future SAC orders.
Scenario:
The business wants to fulfill customer orders under an existing sales contract.
Action:
The user creates a SAC order by selecting the appropriate contract number during order entry.
Outcome:
The system links the SAC order to the contract and deducts the ordered quantity or value from the contract balance.
Scenario:
The user needs to view the remaining quantity or value available in the contract before placing an SAC order.
Action:
The system displays real-time contract balance when the user selects a contract during SAC order creation.
Outcome:
The user can ensure that orders do not exceed the agreed contract quantity or value.
Scenario:
The business wants to prevent deliveries that exceed the contract terms.
Action:
The system checks the SAC order quantity against the contract balance during order processing.
Outcome:
The system issues a warning or blocks the order if it exceeds the contract limits, depending on configuration.
Scenario:
Management wants to monitor how much of the contract has been fulfilled through SAC orders.
Action:
The user accesses SAC order tracking and contract utilization reports.
Outcome:
The system displays detailed information on fulfilled, pending, and delivered quantities against the contract.