Oracle Support Page (Marlow)

Permanent contract holders are usually paid when ashore as well as during service periods on board. 

The below procedure explains how this is setup in Oracle.  

Esentially, crew that are not status 0 will continiue to receive wages if:

1. The most recent Financial Offer entry has been marked as ‘permanent contract’
   
   
2. Seafarer is on status 11 (new status is created for permanent contract holders)

Please follow the below steps as applicable: 

- Scenario 1: Employee actually joins and leaves vessels

- Scenario 2: Employee never joins a vessel and works ashore

Scenario 1a:  
Employee actually joins a vessel

• F/O created and ticked / flagged as ‘permanent contract’

        Note: In order for Crew Accounts to know how to pay the seafarer whilst ashore, you will also need to select the 

       appropriate option for the Travel Days.  Please select either:

       - Travel (seafarer will be paid as per contract rules) or

       - Full (seafarer will receive full wages)

• Seafarer record signed on and F/O entry activated as normal
• Seafarer receives wages as normal 

NOTE FOR SEAFARERS THAT HAVE NEVER BEEN MARKED AS ''PERMANENT CONTRACT' HOLDER: 

if the seafarer is ashore, lined up and needs to be paid before sign on, then please do the following:

- Do not create a new Proposal and F/O

- Go the the previous / last F/O entry and create a new version (covering the period up to sign on)

- Inform IT (Niki) who will activate the entry and tick the 'permanent contract' box.  That will enable auto payments.

Scenario 1b:  
Employee actually disembarks (and should continue to receive wages whilst ashore)

• Seafarer signed off as normal
• Because the more recent F/O is ticked as ‘permanent contract’ the seafarer is automatically set to status 11 (not status 1) 
• Create new version on F/O that was used for last assignment
  • Duration = period that crewmember will be ashore 
  • Wages = as applicable for time ashore (Note:  can be different from the wages paid during time on board.  For example, overtime payments can be excluded from this version if required). 
  • Addenda Reason = PASH (PAYMENTS ASHORE)
  • Tick the contract as 'Permanent SEA' (see 1a above)
  • Activate the entry via the 'Active Addendum' button
    
    
• No SEA print out is required whilst the seafarer is ashore and the entry is automatically excluded from the SEA Missing Scans pending list 
  
  
  
• You can also line the seafarer up for the next assignment and create the new F/O as normal.  The crewmember will continue to be paid as per the version you created for his time ashore (points 1 to 3 above) until he is signed on (at which point the newly created F/O for the next assignment will be activated). 

Scenario 1c:  

Cancel contract and stop payments (WHILST ASHORE)

Note: All users have access to remove crew from status 11 and set them on an inactive status.  A warning message is displayed and an automatic email is dispatched as confirmation 

Scenario 2:  

Employee does not actually join a vessel but needs to be paid whilst working ashore (shore-based inspector etc)

• F/O created and ticked / flagged as ‘permanent contract’.
• Proposal to be rejected
• Seafarer’s record manually set to status 11 from the employee file.
• An auto email is sent to operations and crew accounts group for their info

If you try to manually change seafarer’s status to 11 without a rejected Proposal a message will be displayed.

Scenario 3:  

How do I cancel payments for a seafarer that is not on board?

The seafarer will continue to be paid until either:

    a) the 'permanent contract' tick is removed or

    b) seafarer is set to an inactive status

For B (seafarer is set to an inactive status) an auto email is generated as confirmation:

Wages flow

The extended permanent contract, calculate travel days the whole period since the seafarer is not onboard.         

It’s inserted by default to the next month, until the status of the seafarer is removed from permanent