...
- If a port call with a Bunker Requirement is changed, the Bunker Requirement remains linked to the new port call, but if the Bunker Alert List is enabled, it will have a Bunker Requirement Alert. If the port call is deleted, the Bunker Requirement is unlinked after the voyage is saved and shows as unlinked in the Bunker Requirement List. An unlinked Bunker Requirement can be linked to a different port call or canceled.
- If there is an existing lifting at the Port, in the Planned Liftings grid, editing Req Qty automatically adjusts Opr Qty by the same amount. When this happens, the Opr Qty field is highlighted and a tooltip explains the difference in value between the two fields.
- The selection of vendors in the Agent field is limited to the nominated agents specified for the portcallport call.
Note: Veslink provides a different form for entering bunker requirements.
Port Expenses
When port expenses are entered in on the Bunker Requirement form, they will contribute to the total Bunker Price Total cost of a given bunker lifting and the same , which will be reflected in the Bunker the Bunker Details Report.
| Expand |
|---|
| title | Related Configuration Flags |
|---|
|
| Name/Flag | Description |
|---|
Enable Vessel Bunker Grade
CFGEnableVesselBunkerGrade | Specifies the Fuel Grade in a G (Grade) column on the Vessel or Time Charter In/Out form, which defaults the value on the Bunker Requirement; it can be overridden but is required for Confirmed status. | Require Agents to Confirm Requirement
CFGRequireAgentsToConfirmRequirement | Requires values for Port Agents when confirming a Bunker Requirement. | Verify Matching Company
CFGVerifyMatchingCompany | Displays a validation error if any of a voyage's or Voyage Estimate's linked contracts or Bunker Requirements has a different Company set than the voyage company. | Lock Confirmed Requirements
CFGLockConfirmedRequirements | Prevents setting the status of a Bunker Requirement back to Preliminary after it has been set and saved as Confirmed. | Lock Cancelled Requirements
CFGLockCancelledRequirements | Prevents setting the status of a Bunker Requirement to any other status after it has been set and saved as Cancelled. | Require Fields in Bunker Requirements
CFGRequireFieldsInBunkerReqs | Enter a comma-separated list of of fields that are required in Bunker Requirements. Possible fields: company, reqQty, vessel, port, and requestedDeliveryDate. | Lock Port Name in Bunker Requirements
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.
| Restrict Bunker Requirement to One 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. | Require Requirement Del Date in Standalone Bunker Requirements
CFGRequireReqDelDateInStandaloneBnkrReqs | When enabled, the Requested Delivery Date field is a required field on Bunker Requirements that are not attached to a voyage. | Enable Veslink Bunkering Form Date Sync
CFGEnableVeslinkBunkeringFormDateSync | When enabled, upon submission and approval of a Veslink Bunkering Form, the Bunkering Completed time and date field from that form will be synced with the Bunker Requirement Delivery field and the Bunker Invoice Delivery Date field, if they exist. If there are multiple requirements for the given port call, it updates each one of them. |
|
...