Search for existing answers to your product and support questions.
Familiarize yourself with our support site and learn best practices in working with our team.
Manage Service Requests, View and update service requests submitted by you and others in your organization.
Submit a new issue to our technical support team.
Oracle B2C Service insights from our Technical Support team subject matter experts
Browse resources to assist you in launching your implementation and ensure a successful go-live.
Access your OCI account.
Find product documentation for supported versions of B2C and documentation libraries for related service solutions.
You will have the tools to improve your customers' experience when you learn about all the things our products can do.
Find links for API documentation, Custom Processes, Customer Portal, and Agent Browser UI Extensibility Framework.
Explore how accelerators are designed to demonstrate how an integration scenario could be built using the public integration and extension capabilities of the Oracle B2C Service.
Prepare for a successful transition by reviewing upcoming release changes and enhancements.
Explore webinars, events, and feature kits to learn about B2C Service features, functionality, and best practices from the technical experts.
Oracle MyLearn offers a portfolio of free and paid subscription-based learning resources to help you gain valuable skills, accelerate cloud adoption, increase productivity, and transform your business.
Empower your team with the skills to implement, configure, manage, and use your applications with Customer Experience Cloud Training.
Our goal is to facilitate a friendly, supportive environment where members can easily collaborate with each other on solutions and best practices.
Ask and answer questions specific to B2C.
This is an exciting resource intended to help with your Oracle Service Cloud Analytics.
Share product improvement ideas and enhancement requests with Oracle Development, while collaborating with other Oracle customers and partners.
Update your phone number, email notification preferences, and severity 1 and severity 2 contact preferences.
View the contact managers within your organization.
Find contact information of the Technical Account Manager (TAM) and Client Success Manager (CSM) for your organization.
Environment:
Time zone, Interfaces, All versions
Issue:
When an end-user requests assistance, which time zone is used for the date / time stamp in the incident? Which time zone is used when the agent responds? Why would incident reference numbers be showing tomorrow's date?
Resolution:
The time zone used depends on how you have configured your application and how many interfaces you are using.
Using a Single Interface
If you have one interface, the time zone defined in the TZ_INTERFACE configuration setting (a hidden setting) is used for all time and date information, including the time stamp, the date created field and the date updated field, regardless of which time zone the end-user enters their request from. For example: If an end-user enters a request from New York and the TZ_INTERFACE setting is set to match the location of the company's home office in California, that is, the Pacific time zone, all time stamp entries will be in Pacific time -- even for entries from the end-user.
If you have one interface, the time zone defined in the TZ_INTERFACE configuration setting (a hidden setting) is used for all time and date information, including the time stamp, the date created field and the date updated field, regardless of which time zone the end-user enters their request from.
For example: If an end-user enters a request from New York and the TZ_INTERFACE setting is set to match the location of the company's home office in California, that is, the Pacific time zone, all time stamp entries will be in Pacific time -- even for entries from the end-user.
Using Multiple Interfaces
If you have multiple interfaces, each interface can be configured with a different time zone in the TZ_INTERFACE configuration settings. In this case, the time stamp that is included in incidents depends on which interface the end-user and the agent are using. For example: If an end-user enters an assistance request through an interface whose TZ_INTERFACE setting is set to East coast time (EST5EDT), all entries by that user will be in East coast time. If the agent responds to the request through an interface set to Mountain time, the agent's response will be in Mountain time (MST7MDT).
If you have multiple interfaces, each interface can be configured with a different time zone in the TZ_INTERFACE configuration settings. In this case, the time stamp that is included in incidents depends on which interface the end-user and the agent are using.
For example: If an end-user enters an assistance request through an interface whose TZ_INTERFACE setting is set to East coast time (EST5EDT), all entries by that user will be in East coast time. If the agent responds to the request through an interface set to Mountain time, the agent's response will be in Mountain time (MST7MDT).
Incidents created with tomorrow's date
There are a couple things to consider when you see incidents created with tomorrow's date. Check the setting TZ_INTERFACE. This will show you the time zone that the interface is set to. It may not be set to your local time zone. All transactions such as private notes and responses within the database will be set per the TZ_INTERFACE setting. The incident reference number prefix will change to "tomorrow's" date as soon as the first incident has been received on an interface within a current time greater than midnight. For example, if a site has two interfaces, one with a time zone equal to Australia/Sydney and the second interface is set to PST8PDT (American Pacific), the reference numbers for both interfaces will switch as soon as the first incident is submitted on the Australian interface. In this scenario, an incident will be created on the PST8PDT interface with "tomorrow's" date several hours before midnight PST.
There are a couple things to consider when you see incidents created with tomorrow's date. Check the setting TZ_INTERFACE. This will show you the time zone that the interface is set to. It may not be set to your local time zone. All transactions such as private notes and responses within the database will be set per the TZ_INTERFACE setting.
The incident reference number prefix will change to "tomorrow's" date as soon as the first incident has been received on an interface within a current time greater than midnight. For example, if a site has two interfaces, one with a time zone equal to Australia/Sydney and the second interface is set to PST8PDT (American Pacific), the reference numbers for both interfaces will switch as soon as the first incident is submitted on the Australian interface. In this scenario, an incident will be created on the PST8PDT interface with "tomorrow's" date several hours before midnight PST.
Note: For more information on configuring time zones, refer to Answer ID 605: Setting the time zone in Oracle B2C Service.