One unique aspect of a global implementation is that multiple locations may use the same system at the same time.
What if , You need to implement Timezones for each Legal entity like US, UK, Singapore and China in your Global single Instance.
Business transactions need to be accounted for in the correct period, in particular for financial transactions such as invoicing, collections,
etc. In addition, global instances with locations in vastly different geographical regions need the ability to close each location at period end in their own time zone.Therefore , you need to have understanding for Time Zone Features in EBS R12.
Date Fields in Oracle E-Business Suite can be classified under these broad categories
This is Typically Date/Time which are associated as a part of transaction creation or maintenance.
Typical example in EBS context are Transaction date, Order Date, Shipment Date, service order effective date etc.
|Accounting Date||This is Typically GL Date. This date determines which Accounting period the transaction Accounting period the should be booked in.|
|Server (database) Date||
This is dates that are primarily used in Data base operations.
Such dates are typically user to capture as Creation Date,Last updated Date
Standard Oracle provides three Time Zone features that can be used:
|Oracle Time Zone Features||Description|
|Server Time Zone||
This determines the date and time on which Database dates are determined
In absence of Legal Entity Time Zone or User Preferred Time zone set up, this is the default time zone on which all date fields are determined
|Legal entity Time Zone||This determines the Accounting Date for certain in-scope transactions related to Accounting|
|User Preferred Time Zone||This determines the time zone displayed for in-scope Transaction Dates|
Doc ID 402650.1 -UPTZ User-Preferred Time Zone Support in Oracle E-Business Suite Release 12
Doc ID 726851.1 -LETZ (Legal Entity Timezone)