| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Note: Configuration flag CFGEnableRequirementDrivenBunkerWorkflow must be enabled.
...
This workflow comprises three phases:
Table of Contents outline true style none
Creating a Bunker Plan
When creating a bunker plan on the Voyage Bunkers form, you can do any of the following:
...
When you create the first preliminary requirement, Req Qty and Opr Qty (read-only) in the requirement default to 1,000 MT (the value of Opr Qty on the Voyage Bunkers form). Req Qty on the Voyage Bunkers and Bunker Requirement forms are kept in sync; you can update the value in one of these fields, and it updates the other field as well.
Confirming Bunker Requirements
To confirm a Bunker Requirement, edit its Req Qty as needed and then set its Request Status to Confirmed. On the Voyage Bunkers form, Opr Qty becomes read-only, and its value equals the sum of Req Qty in all confirmed requirements.
...
You decide to cancel the 200 MT requirement. When a confirmed requirement is cancelled or deleted, this triggers another update to the Voyage Bunkers Opr Qty. The 200 MT value is removed from the plan, which now shows 1,000 MT.
Lifting Bunkers
After bunkers have been lifted, Opr Qty on the Voyage Bunkers form changes to show the actual lifted amounts on the vessel.
- If you create additional confirmed requirements for the same port, the Opr Qty does not recalculate because it shows only the sum of the lifted amounts.
- You can still create additional liftings for the same port, and the value of the liftings add to the value in the Opr Qty field in the Voyage Bunkers form.
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|