Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Trigger: Load or Discharge Completes for Each Cargo at Each Port
Load or discharge completes when an HF activity is entered or, if not, a PE activity is entered on the Port Activities form.
If the Counterparty is the same and there are multiple loads/discharges for it at the same port for the same Cargo, only one task is generated per Counterparty/Cargo combination.
If a VC In is marked as a CoLoad, one AR task is generated per VC In/Counterparty combination.
Port Function
Vessel Type
Counterparty
Tasks Generated
Analyst
Port Function
Vessel Type
Counterparty
Tasks Generated
Analyst
L
All
Supplier
AR
-
D
All
Receiver
AR
-
One Demurrage Time Bar Task is generated per cargo per port, except:
If the vessel is a tanker: One task is generated per counterparty with no separation per port or cargo.
If the vessel is not a tanker and the Cargo is Reversible all ports: One task is generated per cargo.
Port Function
Vessel Type
Counterparty
Tasks Generated
Analyst
Port Function
Vessel Type
Counterparty
Tasks Generated
Analyst
L
Nontanker
Owner from purchase (VC In) contract
AP
-
D
Nontanker
Owner from purchase (VC In) contract
AP
-
-
Nontanker
Owner from purchase (VC In Reversible all ports) contract
AP
-
-
Tanker
Owner from purchase (VC In) contract
AP
-
Trigger: The Voyage Completes
The voyage completes when an HF activity is entered or, if not, a PE activity is entered on the Port Activities form, and it's the last discharge operation in the voyage.
All relevant AR tasks update with AP Claim Received selected.
Port Function
Vessel Type
Counterparty
Tasks Generated
Analyst
Port Function
Vessel Type
Counterparty
Tasks Generated
Analyst
-
All
Owner
AP
-
No tasks are generated.
OVOV, RELT, TCOV, or VCOV Voyages
Trigger: Load or Discharge Completes for Each Cargo at Each Port
Load or discharge completes when an HF activity is entered or, if not, a PE activity is entered on the Port Activities form.
The AP Claim Received check box is not applicable because no AP tasks are generated.
NOTE. CFGAddPerVoyagePayableVcovReltTimeBarTask and the CFGUseCargoCounterpartyInTimeBarTask are mutually exclusive.
A single per-voyage AP task for the VC In Owner will be generated for VCOV/RELT voyages (similar to what the existing CFGAlwaysAddPerVoyageReceivableTimeBarTask does now for the AR task).
The new task will use the VC In ID as Cargo ID - and selecting it as hyperlink in the list will open a proper VC In.
The task will open as normal with counterparty listed as Owner - and we can create a laytime calc as normal for it;
If there’s an existing laytime calc for the Owner - it will be linked on task generation auto-magically - just like all other tasks do;
NOTE. CFGAddPerVoyagePayableVcovReltTimeBarTask and the CFGUseCargoCounterpartyInTimeBarTask are mutually exclusive.
The Demurrage Time Bar Task logic considers an OVOV or TCOV voyage to be Outcharter if the counterparty on any voyage cargo is an external company.
A cargo counterparty is considered an internal company if the Internal Address check box (not the Internal check box) is selected on the counterparty's Address Book record. If the Internal Address check box is not activated by the configuration flag: CFGAddBookInternalAddressText in the Address Book, the voyages are never Outcharter and the below logic does not apply.
The Voyage is not an Outcharter if the configuration flag: CFGUseCargoCounterpartyInTimeBarTask is enabled even if the internal address check box is not ticked.
Outcharter Voyage rules apply:
For voyages: OVOV, RELT, TCOV, or VCOV If the counterparty on any voyage cargo is external ("Internal Address" check box in the Address Book entry is NOT SET)
For voyages: SPOT or COAS - If the counterparty on any SALE cargo is external
For SPOT or COAS, if there is any SALE cargo with the "CoL" checkbox in the Voyage cargo grid - the voyage is not an Outcharter.
Trigger: The Last Load or Discharge of the Voyage Completes
The last load or discharge of the voyage with a cargo handling line completes when an HF activity is entered or, if not, a PE activity is entered on the Port Activities form.
Port Function
Vessel Type
Counterparty
Tasks Generated
Analyst
Port Function
Vessel Type
Counterparty
Tasks Generated
Analyst
L
All
Owner
AP
-
D
All
Owner
AP
-
-
All
Charterer
AR
-
Voyage Type: OVOV, RELT, TCOV, or VCOV Outcharter
Trigger: The Last Load or Discharge of the Voyage Completes
The last load or discharge of the voyage with a cargo handling line completes when an HF activity is entered or, if not, a PE activity is entered on the Port Activities form.
The AP Claim Received check box is not applicable because no AP tasks are generated.
A single per-voyage AP task for the VC In Owner will be generated for VCOV/RELT voyages (similar to what the existing CFGAlwaysAddPerVoyageReceivableTimeBarTask does now for the AR task).
The new task will use the VC In ID as Cargo ID - and selecting it as hyperlink in the list will open a proper VC In.
The task will open as normal with counterparty listed as Owner - and we can create a laytime calc as normal for it;
If there’s an existing laytime calc for the Owner - it will be linked on task generation auto-magically - just like all other tasks do;
NOTE. CFGAddPerVoyagePayableVcovReltTimeBarTask and the CFGUseCargoCounterpartyInTimeBarTask are mutually exclusive.
Name/Flag
Description
Name/Flag
Description
Use Cargo Counterparty in Time Bar Task CFGUseCargoCounterpartyInTimeBarTask
When enabled, the Charterer for Cargo contracts or Owner for VC In contracts will be used as the counterparty in Demurrage Time Bar Tasks instead of the Supplier or Receiver.
Enable Demurrage TB Tasks
CFGEnableDemTBTasks
Enables Demurrage Time Bar Tasks and the Demurrage Time Bar Task List, which also adds two fields to this form: Default Warning Days and Default Alert Days.
When enabled, Demurrage Time Bar Tasks are not generated for counterparties with Internal selected on their Address Book entries.
Always Add Per Voyage Receivable Time Bar Task CFGAlwaysAddPerVoyageReceivableTimeBarTask
When enabled, a single AR Demurrage Time Bar Task will be generated in OVOV, RELT, TCOV, or VCOV voyages for the Charterer for Cargo contracts. It will be generated regardless of whether a voyage is Outcharter or not.
Demurrage Timebar Tasks Completed Status List CFGDemTimebarTasksCompletedStatusList
Defines the comma-separated list of demurrage time bar tasks' statuses (one-character letters) that are considered "Completed ". Possible values are: "New" (W) "No Demurrage" (N) "Under Review" (R) "In Progress" (P) "Settled" (S) "Cancelled" (C) "Dispute" (D) "Claim Received" (E) "Claim Sent" (T) "Internal" (I) "Time Bar" (B)
When enabled, you can specify the supplier or receiver for each cargo handling in a Cargo or VC In contract.
Add Book Internal Address Text CFGAddBookInternalAddressText
When a value is specified, a new check box is displayed in the Address Book with the label being the value of the configuration flag (e.g. Internal Address). When the value is empty, the check box is not shown.
Demurrage Timebar Tasks Completed Status List CFGDemTimebarTasksCompletedStatusList
Defines the comma-separated list of Demurrage Time Bar Task Statuses that are considered Completed.
Use Cargo Time Bar Basis for Demurrage Time Bar Tasks CFGUseCargoTimebarBasisForDemTBTasks
When enabled, Time Bar Date and Target Date on the auto-generated Demurrage Time Bar Tasks will update using the Cargo's time bar settings (based on the Task's Cargo and Counterparty) when:
Relevant basis dates on the voyage are updated (such as BL/Disch Date or completion of discharge).