For some clients, the IMOS Company Code is a mandatory field that is critical for correct operations and financial records and should not be omitted. In order to accommodate many different business structures, IMOS offers many different several ways to default the IMOS Company Code field throughout the system. Depending on your workflow, you may want to choose one set of configuration flags over another in order to ensure the correct defaulting.
Default Company on the Voyage Manager
The default company on the
...
Voyage Manager populates in the Company field when the voyage is first scheduled. Once the default company is populated, it can be manually edited
...
but will
...
no longer be
...
subject to
...
changes to its source
...
.
...
When the voyage is scheduled:
- When there is a Cargo Fixture/TCO
...
- Fixture,
...
- the first source for the Company is the Cargo Fixture/TCO
...
- Fixture.
- When there is
...
- no Cargo Fixture/TCO Fixture or the Company on the Cargo/TCO Fixture is empty:
- If CFGDefaultCompanyOnTciSelect = Y, the default company is
...
- sourced from the
...
- Head Fixture/TCI
...
- Fixture.
...
- If
...
- CFGDefaultCompanyOnTciSelect = N,
...
- the default company
...
- is empty.
- When there is no Cargo Fixture/TCO Fixture or the Company on the Cargo/TCO/TCI/Head Fixture is empty:
- If CFGAssignDefaultCompanyOnVoyage = Y, the default company is sourced from the Vessel details.
- If CFGAssignDefaultCompanyOnVoyage = N, the default is empty.
The default Company is determined using the following hierarchy of sources:
- Selling Fixture
- Buying Fixture
- Vessel
IMOS only tracks down the hierarchy if the corresponding flags are enabled.
...
Default Company on Voyage
...
IMOS follows this logic to default the company on a Voyage Estimate:
...
Estimates
When a new Voyage Estimate is created, the Company field will always default to the default estimate template (.TDEFAULT).
When nominating a vessel on the Voyage Estimate:
- If CFGDefaultCompanyOnTciSelect = Y, IMOS will use the Company from the TCI Fixture (If the vessel is a TC vessel).
- If CFGDefaultCompanyOnTciSelect = N and CFGDefaultCompanyFromVessel = Y, IMOS will use the Company from the Vessel set to Nominated Vessel.
- If both flags are enabled, then IMOS will first lookup the Company from the TCI Fixture; if empty, IMOS will lookup the Company from the Vessel details.
Default Company on
...
Cargoes
IMOS follows this logic to default the company on a Cargo:
...
- If CFGDefaultCompanyFromVessel = Y
...
- , IMOS will use the Company from the Vessel set to Nominated Vessel
...
- .
- If CFGDefaultCompanyFromVessel = N and CFGDefaultCompanyOnCargoImport = Y, IMOS will use whichever company is part of the cargo message XML.
Default Company on Time
...
Charters
IMOS follows this logic to default the company on a Time Charter:
...
If CFGDefaultCompanyFromVessel = Y
...
, IMOS will use the Company from the Vessel set to Nominated Vessel.
- CFGDefaultCompany is indeed used to determine the company to be used on a newly-created voyage.
- However, CFGDefaultCompany appears to be the last level of fallback if none of the other ways of determining the default company work, i.e., there are several other methods of determining the default company whichtakeprecedence over CFGDefaultCompany. These include the company of the various contracts linked to the voyage (TCI, TCO, COA, Cargo, etc.) and the company of the Vessel. Some flags involved in this are CFGUseVtypeCompany, CFGUseContractCompany, and CFGRequireCompanyMatchForInvoice.
- There does not appear to be any mechanism for defaulting the company on cargoes or estimates.
- As a note, CFGUseContractCompany appears to make Company a required field on most contracts.
Jonathan, if you have seen anything that contradicts the above, let me know. However, assuming the above is correct, it seems to me that there's no way to describe this functionality within the name of the config flag itself. I think the answer must lie in providing better documentation of Voyage Manager's Company field. The documentation page that touches on the VoyMan Company field is here, and doesn't address any of this at present:
https://wiki.veson.com/display/imosv78/Operations+Tab+-+Voyage+Manager
Let me know if you agree that updating the documentation is the way to go. Notifying Judy for her information.| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
| Page Properties | ||||||
|---|---|---|---|---|---|---|
| ||||||
|