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:
Incidents, Interfaces, Time zones Oracle B2C Service
Resolution:
It is possible for incidents to be created with a reference number that indicates the next day. For example, an incident might be submitted on March 15, 2021 and the reference number begins with 210316 instead of 210315.
This can occur in applications that have multiple interfaces that use different time zones for each interface. If an incident has been submitted from an interface that has already begun the next calendar day, the reference number for that incident will reflect the date of that interface. Similarly, this will happen if an agent's staff account has the Time Zone field set and that agent submits an incident when the next calendar day has started for that timezone. This is because the reference number field is affected for the entire database, not for each individual interface.
The reference number of each incident submitted after that will reflect that next day, regardless of which interface the incident was submitted from. Once the first part of the reference number has increased, all following incidents will reflect that date. As a result, each incident submitted, regardless of interface, will reflect the new date in the reference number.
For example, a database has two interfaces, one that is set for the eastern U.S time zone and one set for the western U.S. time zone (three hours difference). If an end-user submits an incident at just after midnight on February, 2, 2021, from the eastern U.S. interface, the reference number created will be 210202-000000. In the western U.S., it is only 9:00 p.m. on February 1. All incidents submitted from the western interface for the next three hours will have a reference number that begins with 210202, even though the calendar date in that area is still February 1. This is due to the incident submitted from the eastern interface.
Note: The actual date and time stamps in the discussion thread are all correct according to the specific time zone configurations of each interface. In addition, the incident creation date is stored using the time for the interface through which the incident was submitted. It is only the reference number that may have cases where the reference reflects a different date than the date the incident was created.