What should be considered when setting up cruise ships and time zones?
As the ship passes time zones, it's recommended that these changes be maintained in CT. Time Zone is used when setting the time/date stamp for transactions. The location time zone will convert from the current server time to the time zone listed in the location record. Posting will be available as of midnight for the location time zone configured. Corporate manages the Time Zone setting for the location and, therefore, would update when the ship changes position and then run replication to process the update on the boat.
Here are some examples where time zone affects the application:
- CDP Error Remediation will use login location time zone
- If it is corporate logging into EMW, then it uses the Company Time Zone
- If it is a ship location, then it uses the Location Time Zone
- Transaction and Report Date selection availability will be based on Location Time Zone offset
- Posting for the ship will be based on server time, indicating when it is midnight
- GMT is derived from the Oracle database using sys timestamp
Transactions that would be affected by an invalid Time Zone:
- Customer Order:
- Create Date is the current date based on the time zone of the ship
- Approval, Picklist, and Invoicing - all based on the time zone of the ship
- Reconcile is the current date based on the time zone of the ship
- Location Transfers:
- Cannot create a transfer in the future
- Inventory Adjustments / Recipe Adjustments:
- Cannot create adjustments in the future
- Inventory Counts:
- Cannot enter counts for a future date
- Posting:
- Cannot post until midnight (server time)
- Simple Receipt:
- Cannot create a Simple Receipt in the future and set the Actual Delivery Date for a future date
- Vendor Orders/ Master Order:
- Cannot reconcile a Vendor Order in the future
- Reports:
- Cannot retrieve data for a future date
- CDP Imports:
Menu Mix, if sent for a future date, will fail.
Related Articles
Comments
0 comments
Please sign in to leave a comment.