Home > Bunkering > Bunker Requirement
...
Rows are highlighted according to the Operations Lists Settings:
...
You can use the Bunker Requirement List to check on the status of a Bunker Requirement.
Bunker Requirement
The Bunker Requirement communicates request information from the Operator to the Bunker Manager.
...
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 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. If there are multiple Bunker Requirements for this port, IMOS chooses the first one to sync to (the one with the lower Requirement ID for that port with that fuel type). If the Bunker Requirement Request Status is Canceled, or if Procurement Status is Completed or Canceled, IMOS will not update the Bunker Requirement's Delivery date. | Show Bunker Quantity Range on Requirement CFGShowBunkerQtyRangeOnReq | When enabled, the min/max values for each fuel type will be added to the Inquiries and Purchases grid on the Bunker Requirement form. | Change Paid By or For Account to either TCI Owner or TCO Charterer CFGEnableNonOperatorBunkerPurchases | When enabled, you can change the Paid By or For Account fields to either TCI Owner or TCO Charterer and the record will stay linked with the Bunker Purchase. Bunker Invoices paid by TCI Owner/TCO Charterer cannot be invoiced. |
|