Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Self Service Procurement Cloud Release 13: Consider Legal Entity Time Zones in Date Conversions in S

edited Jan 17, 2018 12:16PM in Self Service Procurement

Summary

Convert Dates based on Legal Entity Time Zones in Requisitions

Content

Business Problem:

Self Service Procurement captures several dates as part of the create requisition process including:

a) Conversion Date (used for foreign currency conversions)

b) Need by Date (used in downstream purchasing flows) and

c) Budget Date (used for budgetary control and encumbrance transactions).

If the business operates in different time zones, there arise potential issues when using these dates. 

Take the following use cases:

1. Currency conversion rates for a customer, whose financial division was based in the US, were loaded at midnight Pacific time.  The cloud database servers use UTC timezone, say with a business division in Asia. In this scenario, when user in Asia tries to create a requisition during early IST hours e.g  9 A.M. IST, the requisition creation process ran into an issue because the system was not be able to find any rates because they did not yet exist for the new day in Asia. The currency conversion rates were still as of the previous day.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!