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)
A VC In looks similar to a Cargo, except that it has an Owner field instead of a Charterer field and other fields related to a purchase rather than a sale; for details see information on the Cargo form. VC In contracts also appear on the Trading P&L Summary.
Enter the Number of Copies, Start Date, and Total Periods, and then click Create.
Edit line items for the copies as needed and then click OK.
Copying a VC In to a Cargo
To copy a VC In to a Cargo, click and then click Copy to Cargo.
Copying a VC In to a Cargo and Linking Back
To copy relevant details from a VC In to a Cargo and Link them in a Relet connection (similar to clicking on a Cargo), click and then click Copy to Cargo and Link Back. Pricing, demurrage, broker, and Extra Freight Terms details are not copied onto the Cargo.
Creating a Voyage Fixture from a VC In
To create a Voyage Fixture from the VC In, click . If the VC In is linked to a Sale Cargo, the Voyage Operation Type is set to RELT; otherwise, it is set to SPOT. After the Voyage Fixture is created, the button changes to .
Creating a Voyage Estimate from a VC In
To create a Voyage Estimate from a VC In, click , then click Add Cargo to New Estimate. A Voyage Estimate is created with the cargo. If a vessel has been nominated, the new Estimate uses with this vessel.
Creating a Voyage from a VC In
To create a voyage from the VC In, click . All the information from the VC In moves to the Voyage. After the Voyage is created, the button changes to .
If you have the Bulk Update Cargo ContractsModule Right selected, under Actions in Chartering, a column of check boxes appears in the VC In List. To bulk update VC Ins, select the contracts you want to update and then click the Bulk Update action link at the top of the list.
Acknowledging Revisions
If a Cargo or a VC In has at least one unacknowledged revision, its row is highlighted in the Voyage Manager Cargo List (CFGEnableVoyManagerCargoList).
Name/Flag Description Use Company Lob Trade Area Hierarchy
CFGUseCompanyLobTradeAreaHierarchy Sets up a hierarchy between Company, LOB, and Trade Area on several forms. Enable Voyage Manager Cargo List
CFGEnableVoyManagerCargoList Adds Cargo and Cargo Handling tabs to the Voyage Manager. The Cargo tab is similar to the Cargo List, but only includes cargoes associated with the voyage. The Cargo Handling tab is similar to the Cargo Handling form; it includes a list of all cargoes associated with the voyage, with a line for each load and discharge. Lines highlighted in yellow indicate transshipment cargoes, while lines highlighted in blue indicate interservice cargoes. If a Cargo or VC In has at least one unacknowledged revision, its row is highlighted in the Cargo List. Show Remittance in Cargo
CFGShowRemittanceInCargo Adds Remittance Bank, Invoice %, Payment Terms, and Balance % fields to the CP Terms Details, Cargo COA, Cargo, VC In COA, and VC In forms. Also adds a Remittance Bank field to Time Charter Other Information. Remittance information flows between these places; for example, fixing an Estimate will transfer the remittance information. On a Cargo COA, VC In, or Time Charter Out, changing the Company clears the remittance bank information, as this may change with a change to the Company. On a VC In COA or Time Charter In, changing the Owner clears the remittance bank information, as this may change with a change to the Owner. A default value for the Remittance Bank for each currency can be selected in the Address Bank Links tab entry for Cargo COA, Cargo, and Time Charter Out (Other Information) contracts, but it can be changed later. Enforce Operations Ledger Code Commissionable Property
CFGEnforceOpsLedgerCodeCommissionableProperty When enabled, the Commissionable setting of an Operations Ledger Code alone determines whether claim and freight adjustment line items are commissionable. When enabled, the commissionable setting cannot be overridden in invoices or per broker. Enable Contract Mirroring
CFGEnableContractMirroring Enables the following types of intercompany contracts to be mirrored: Cargo COA, VC In COA, Cargo, VC In, Time Charter In, Time Charter Out, and FFA/Option/Bunker Swap Trade. When a contract of one of these types is created with internal counterparties, a mirrored contract is automatically created from the opposite perspective, so that users from both legal entities can manage the contract and include it in both their operational planning and their trading exposure and P&L. When both CFGEnableContractMirroring and CFGEnableTCInvoiceMirroring are Y, and when a TC contract is mirrored, TCO invoices are mirrored from TCI invoices. Incremental invoice type is unavailable for such mirrored TC invoices. If an **OV voyage has cargoes with multiple internal charterers, it can be mirrored with multiple RELT voyages, one for each internal charterer's company. Default Claim Commission Invoice Setting
CFGDefaultClaimCommissionInvoiceSetting This flag controls the default setting for broker commissions on Claims by setting the default value of M on TC In, TC Out, Cargo, Cargo COA, VC In, and VC In COA broker grids. Possible values: 0 (default): Claims are not commissionable. 1: Claim commissions will be invoiced separately. 2: Commissions will be deducted from the Claim Invoice. Enable Commission Sharing
CFGEnableCommissionSharing When enabled, you can share commissions between internal broker companies. For more information, see Sharing Commissions with Internal Brokers. Also adds an Internal Counterparty column to the TCO Estimate Broker table. Enable Broker Rules
CFGEnableBrokerRules When enabled, Cargo Broker Rules and Time Charter Broker Rules can be defined to add default brokers to contracts. Also adds Add Default Brokers to the TCO Estimate toolbar to default internal brokers by applicable rules. Apply IC Adjustment to Xfrt
CFGApplyICAdjustmentToXfrt If enabled, for a model B mirrored freight contract (Cargo / VC In and Cargo / VC In COAs), an Extra Freight Term is adjusted by IC Adj % in the same way as the base freight, if the Extra Freight Term type is Rate or Lumpsum (not Percent). Enable Operations LOB
CFGEnableOpsLOB If enabled, displays an LOB (Line of Business) field on the Address (Type W), Voyage Estimate, Voyage Fixture, Voyage Manager, and contract forms. Enable Shuttle Freight Invoicing
CFGEnableShuttleFreightInvoicing Enables the Shuttle Tanker Workflow and master data forms necessary for freight invoicing of time and bunkers for both the actual voyage and theoretical return legs, most commonly used by shuttle tankers. Minimum Required Schema Version: 239 Enable VC In Booking
CFGEnableVCInBooking Enables the VC In Booking form. Adds an option to Keep Booking No. when copying a Cargo or VC In. Min. Required Schema Version: 243 Store Firming ETA on Cargo Trigger
CFGStoreFirmingETAOnCargoTrigger When a voyage’s status is set to the configuration flag value (forecast, scheduled, or commenced), a static Firming ETA field populates on the linked Cargo or VC In Itinerary/Options tab. You can compare this value with the actual ETA in a custom Report Designer report. To disable this flag, leave the value blank. Enable Cargo Delivered
CFGEnableCargoDelivered Enables you to save Cargoes, VC Ins, or bookings with only a load or discharge port.