...
Page Properties | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Сhange Log:
Expand | ||||||
---|---|---|---|---|---|---|
|
Description
The Otalio Master plugin is designed to import crew bio data as well as data on embarkation and disembarkation from Otalio to Adonis. On importing, the system creates the sea-service activity for uploaded crew.
Info |
---|
Activity The sea-service activity is created only in case Department and Position XREFs are correctly defined (for more information, see APM Configuration). Otherwise, records are not imported to APM without activities. |
Data Processing Rules
Otalio sends a list of crew members onboard a vessel. Adonis, in its turn, compares the existing list of crew members with the one received from Otalio and processes data based on the following rules:
Crew members existing in the Adonis crew list but not found in the Otalio crew list are disembarked. The disembarkation date is set to the current date.
In case a crew member’s department or position got changed, the system closes the current activity=Today() -1d and creates a new sea-service activity linked to the new department and position code.
If a crew member is not available in the Adonis database, the system adds a crew member as well as creates a sea-service activity (datefrom=embarkation.ActualDate, DateTo=Null, TodateEstimated=disembarkation.ScheduledDate).
Field Mapping
...
Otalio
...
Adonis
...
Comments
...
CrewId
...
PW001P01.PIN
...
CrewId in the Otalio has format abc123456, so we need to subtract 3 chars at the beginning and create person with Pin number which left.
...
ProfileId
...
PW001P01_XREF.XREF_PIN
...
Otalio is the master database, the system is more transparent if the Otalio ProfileId is used in Adonis as well.
...
dateOfBirth
...
BIRTHDATE
...
placeOfBirth
...
PLACEOFBIRTH
...
firstName
...
FNAME
...
lastName
...
LNAME
...
MiddleName
...
MNAME
...
Gender
...
If a crew member is already available in the Adonis database, only bio data is updated.
While importing crew members' records to APM, the system assigns crew their PIN numbers by considering the external CrewID (in formats: abc123456, .abc123456) and retrieving its numeric part. That means the abc123456 external Crew ID corresponds to the 123456 PIN number in APM.
After the activity confirmation, the payroll information (payroll table and code) is fetched from the Contracts datagroup or Personal Details > the Seniority tab (in case the Contracts datagroup is not in use).
Field Mapping
Otalio | Adonis | Comment | ||||
---|---|---|---|---|---|---|
CrewId | PIN | |||||
ProfileId | Otalio external PIN | |||||
dateOfBirth | Birth date | |||||
placeOfBirth | Place of birth | |||||
firstName | First name | |||||
lastName | Last name | |||||
MiddleName | Middle name | |||||
Gender | Sex | |||||
Nationality | Nationality | |||||
boardCardIdP01 | .ALTERNATIVEPINCrew card number stored in the Alternative Pin field in the Personal Details datagroup. | |||||
embarkation.actualDate | P03.DATEFROM P01.EMPLOYMENTSTARTDATE | Assign to EMPLOYMENTSTARTDATE to make the person activeSea-service activity start date | ||||
disembarkation.scheduledDateP03.ESTIMATEDENDDATE | Sea-service activity planned end date | |||||
disembarkation.actualDateP03.DATETO | Sea-service activity actual end date | |||||
operationalPosition.Code Find code from pw001c000_XREF where XREF_CODE=operationalPosition.Code and Interface_xref='OTALIO' and TABLE_REF=2 | => use the code to find the numorgid to be assigned to P03.NUMORGIDXREF value of a position in the organization | For more information, see APM Configuration. | ||||
operationalDepartment.Code | Find code from pw001c000_XREF where XREF_CODE=operationalDepartment.Code and Interface_xref='OTALIO' and TABLE_REF=3 | P03.NUMORGID | reservationId | PW001P00_XREF.SEQUENCENO_XREF=ReservationId, PW001P00_XREF.SEQUENCENO_REF=P03.SEQUENCENO | XREF value of a department in the organization | For more information, see APM Configuration. |
reservationId | Otalio ID number of the sea-service activity |
Housekeeping
The section covers the download, installation, and configuration procedures of the Otalio Master plugin.
...
Once the download is complete, follow the link below to get the instructions on how to install the plugin:
Installing and distributing the Replicator plug-in
Setting Parameters
After the plugin is installed, it is necessary to specify parameters for the Site(s). To do this, follow the steps below:
...
Name | Value |
---|---|
SERVER_NAME | Address of the server hosting the APM database. |
DATABASE | Enter the database Database name used when installing Adonis Personnel Manager. |
DEBUGLOG | 0 / 1 (Extended log)- for the debug information in Replicator only. 7 - for the extended log; adds debug information into the log and stores request/response in the debug folder. |
SERVICE_PSW | Service password. |
SERVICE_URL | URL to the Otalio service. |
SERVICE_USER | Otalio user name. |
XREF | Interface name identifying the XREF codes used by this plugin. For more information, see APM Configuration. |
XREF_SEX_U | Additional Gender gender identification matching the APM value - [U] Unknown. |
XREF_SEX_N | Additional Gender gender identification matching the APM value - [N] Non-binary. |
SHIPCODE | Otalio’s Code code of the current vessel. |
DEBUGDAYS | The request/response files are now stored only for the specified number of days and then will be deleted. Note: If the DEBUGDAYS parameter is not defined, files will be stored within the current day only. |
ONB_CODEGCT Code of Seaservice activity | Activity code identifying the sea-service activity. See General Codes > Activities to check the code. |
| Two new parameters will be added in the next version of Otalio Master plugin |
DEF_PAYTABLE | parameter for Payscale Table |
DEF_PAYCODE | Parameter for Payscale Code |
...
Anchor | ||||
---|---|---|---|---|
|
...
Expand | ||
---|---|---|
| ||
To export data, it is required to define the Otalio Master plugin code reference. To do this, first, log in to the Adonis Personnel Manager. Once logged in, navigate to the Setup ribbon tab > General Codes > Miscellaneous > Interfaces and proceed with the following steps:
|
Expand | ||
---|---|---|
|
...
| ||
|