Welcome to the Veson Nautical Knowledge Base. In the Help Center, you can view the same articles and contact support as needed.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

The Bunker Requirement communicates request information from the Operator to the Bunker Manager.

Security Module Rights for the Bunker Requirements form differentiate between Operator and Bunker Manager responsibilities by allowing editing for the appropriate fields.

In the Operations module center , under Bunkers, click Bunker Requirement.

  • 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.

Note: Veslink provides a different form for entering bunker requirements.


 Related Config Flags
CFGEnableVesselBunkerGrade

CFGRequireAgentsToConfirmRequirement

CFGVerifyMatchingCompany

CFGLockConfirmedRequirements

CFGLockCancelledRequirements

CFGRequireFieldsInBunkerReqs

CFGLockPortNameInBunkerReqs

CFGRestrictBunkerRequirementToOneInquiryLine

CFGRequireReqDelDateInStandaloneBnkrReqs

CFGEnableVeslinkBunkeringFormDateSync

  • No labels