Note: Configuration flag CFGEnableRequirementDrivenBunkerWorkflow must be enabled.
...
This workflow comprises three phases:| Table of Contents |
|---|
| outline | true |
|---|
style | none- Creating a Bunker Plan
- Confirming Bunker Requirements
- Lifting Bunkers
Creating a Bunker Plan
When creating a bunker plan on the Voyage Bunkers form, you can do any of the following:
...
| Expand |
|---|
| title | Related Configuration Flags |
|---|
|
| CFGLockConfirmedRequirements | Prevents setting the status of a Bunker Requirement back to Preliminary after it has been set and saved as Confirmed. | | CFGLockCancelledRequirements | Prevents setting the status of a Bunker Requirement to any other status after it has been set and saved as Cancelled. | | CFGRequireFieldsInBunkerReqs | Enter a comma-separated list of of fields that are required in Bunker Requirements. Possible fields: company, reqQty, vessel, port, and requestedDeliveryDate. | | CFGLockPortNameInBunkerReqs | Prevents changing the Port name after a Bunker Requirement is created and saved with any status. - If you want to change the Port in a saved Bunker Requirement, you must cancel or delete the Bunker Requirement and then create a new one.
- The Port name at the top of the Bunker Requirement form must be the same as the Port name in the inquiry line.
| | CFGRestrictBunkerRequirementToOneInquiryLine | When enabled, you can only add one inquiry line to a Bunker Requirement. The inquiry line is kept in sync with the Req Qty field, regardless of inquiry line status. | | CFGRequireReqDelDateInStandaloneBnkrReqs | When enabled, the Requested Delivery Date field is a required field on Bunker Requirements that are not attached to a voyage. |
|
...