APM 2024.30.4

APM-8424

Payroll Calculation by Terminated MAIN Contract

mplemented payroll calculation by the terminated Main/Amendment contract as default (no need to set the Contract type option):

In case a sub-contract has an empty or predefined contract type but the Calculate Contract by FIFO Principle option is disabled in General Codes, then it is calculated and closed within the scope of the Main/amendment contract. Otherwise, if the Calculate Contract by FIFO Principle option is enabled General Codes, the subcontract is calculated and closed separately.

APM-8419

Payroll Accumulators do not store values for the whole period with "Payroll Calculation by Contract"

In the Accumulators tab, values are available in the current payroll period based on the selected closed contract in the Calculated Contract drop-down list:

In case Total is chosen in the Calculated Contract drop-down list, then it shows the total accumulator values in the payroll period:

APM-8503

Not possible to configure Entry Codes for overtime transfer to payroll

The issue is fixed. All the necessary properties are loaded in Payscale table → Overtime → Transactions → Method Configuration → Field Setting → Property.

The system doesn’t hang long when adding fields.

APM-8504

Timesheets datagroup not working

The issue has been fixed. Data is successfully loaded in the Timesheet datagroup.

APM-8447

Wrong rate is picked up by the script

When the Contracts datagroup is in use, the Entry Code script handles the field with reference to a particular payscale rate column correctly (XA, XB…).

APM-8460

Payment to "Bank of Philippine Island" is rejected

The Transaction reference No field includes 4 components: Period+'Advance'+GUID part (3 digits)+Datetime part (15 digits). The max length is 30 chars.

To make an output value unique, applied the below-mention shortages for hardcoded text values allowing more space for the Datetime value:

• Advance → Adv

• Addition → Addi

APM-8458

Attachment is missing after sending mail from APM

The issue has been fixed. It is possible to send attachments via Tools -> Send Mail.

APM-7998

Project Details: check crew assigned to the shifts

In the Rotation Planning module > Maintenance > the Project Details tab, the Project Requirements table includes the following columns:

• The Planned column shows number of positions in the plan.

• The Crew Assigned column shows the number of persons assigned to the shift crossing today’s date and the Vessel Project dates with defined positions.

APM-8346

Kadmos balance action manual selection

On enrollment, the Payroll balance action may be either automatically set to Kadmos or manually set to any other balance action. It depends on the preset setup:

• If the Use Kadmos as Primary Payment Method checkbox is selected in Setup, the Payroll balance action of enrolled crew members changes to Kadmos. Please note that the balance action might still be changed.

• If the Use Kadmos as Primary Payment Method checkbox is unchecked, after crew enrollment, the balance action is not set to Kadmos and other balance actions can be used.

APM-8378

Payroll calculation process per contract termination in period

Implemented a new calculation approach that calculates payroll always based on the contract termination. To activate it, navigate to General Options > Payroll > General > Payroll Calculate By Contract:

APM-8391

Additional issues with the Berenberg bank file

In the Payroll module, provided the following enhancements:

• Applied the validation of the Berenberg format

• Added the validation report to display the warnings on missing data.

APM-8404

Payroll Calculation by Contract should not consider sub-contracts or amendments

Implemented the Calculate Contract BY FIFO principle contract type option. A contract is handled as a termination contract to be calculated separately in period if:

• The Calculation by contract global option is selected

• The contract with contract type option is selected

• The contract has EDNDATE in the current payroll period

APM-8416

"Auto entry when activity starts on 31st" does not consider the Transaction Codes setup on Activity Code or Payscales

Fixed the issue. In case the Auto entry when activity starts on 31st option in use, entries are not generated.