Oracle Transactional Business Intelligence Idea Lab

Home› Oracle Analytics› Oracle Analytics Idea Labs› More Solutions Idea Labs› Oracle Transactional Business Intelligence Idea Lab

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

operate the database in the client's time zone

Submitted
63
Views
5
Comments
Marco Vargas-113764
Marco Vargas-113764 Rank 1 - Community Starter
in Oracle Transactional Business Intelligence Idea Lab

Organization Name

Nicomar Electronics

Description

We need our system at the database level to work with the client's time zone, i.e. Colombian time, not U.S. database time. The time zone changes but at the application level in the interface, but it does not work, so all transactions are recorded in the time zone that the database is in the system. That is, this way the Colombian time zone will appear in the system, in the internal records of the system and the databases will remain with the time zone where the server and its database are located.

 

Use Case and Business Need

all our transactions are reflected in the system with the u.s. time, which does not make it easy to keep track of the transaction for audit and consultation and closing dates that the volume of sales is too high in nicomar, we must generate transactions until 7pm otherwise stay with the 01 of the next month, which harms nicomar in times of operation and sales

More details

it only works at the interface level, it is changed and for the user the time of Colombia appears, but when carrying out transaction queries in the database they are left with the time of the United States, not the local time

Original Idea Number: 9c04d7cb68

1
Up
1 votes

Submitted · Last Updated

Comments

  • Glen Ryen
    Glen Ryen Rank 4 - Community Specialist

    Hi Marco,

    Are you using the Legal Entity time zone feature?  It sounds like you're not but you'd like to be, and/or that you don't have a timezone set on your LE.  Have you seen the following docs?

    Incorrect Invoice Date or Payment Defaults based on Local vs. UTC Time Zone Differences(1629641.1)

    Legal Entity Time Zone -vs- Preferences Time Zone [1910933.1]

    Queries could be another matter if you're talking about OTBI and/or BI Publisher reports, where user preferences for time zones could be coming into play.  But review your LE timezone settings and see if they're set appropriately first.

    Does that help?

    Glen

     

  • Rich Merkel
    Rich Merkel Rank 6 - Analytics Lead

    You can use the CAST as date function in OTBI to get rid of the timestamp issues.

     

  • Glen Ryen
    Glen Ryen Rank 4 - Community Specialist

    Hi Rich,

    Correct, CAST is one way to deal with removing a timestamp component from an OTBI analysis.  But I think the first issue here is the determination of accounting date, which does not have a time component.  So if an invoice is entered into the system at 8PM local time in Columbia (GMT-5) on May 31st, creation date in OTBI will have the time component that you could CAST to the value desired by the report user - either 31-May for someone running the report in Columbia or 01-Jun for someone in London HQ (hypothetically).  But the invoice is picking up an accounting date of 01-Jun when Marco would like it to be stamped 31-May.  It was still May locally when the invoice was keyed for that LE/Business Unit; users should be able to enter May transactions right up until midnight Columbia time and that's not happening here.

    Is that the issue, Marco?

    Glen

  • Karan K
    Karan K Rank 1 - Community Starter

    Hi Glen,

    Will setting up timezone at entity level would fix accounting date defaulting/picking for all applicable transactions.

    Thank you,

    Karan

  • Glen Ryen
    Glen Ryen Rank 4 - Community Specialist

    Hi Karan,

    Sorry for the late response, but correct - that's the intent of the LE timezone settings, to derive the correct accounting date for all applicable transactions.

    Hope that helps,

    Glen