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, Analytics
Resolution:
Incident thread data is retained in a separate table from the general incidents table. In addition, there are several different types of threads, which allows you to configure your report to include only certain thread types, such as Customer Entry or Customer Proxy.
Important! Typically, reports that include incident threads become large very quickly and generally take longer to generate. When you create a report that includes incident threads, you should include a run-time filter that includes a range for the incident created date. That way, you can test your report for a small range of dates, which will allow your report to generate more quickly.
When creating a report that includes an incident thread, it is important to define the data set to use the Incidents table as the primary table and then join the Threads table to the Incidents table. To do this, use the steps below:
With the data set defined properly, add filters and output columns to your report.
To restrict the thread to a specific type: Include a fixed or run-time filter based on the threads.entry_type field.
With the filter in place, you can add the thread as an output column for the report. From the Threads table, drag the Text (notes) field to be an output column. All thread of a type matching those set within your filter selection will be listed in the report results.
Reporting on the first thread entry
To include the first thread entry for an incident, first add a filter on incidents.ref_no or incidents.i_id; then use the following column definition:
substr(min(concat(date_format(threads.entered, 'YYYYMMDDHH24MISS'), concat(threads.seq, to_char(threads.note)))),16)
This can be modified to fit your needs. For example, if you want to report on the most recent thread entry, change the min() function to a max() function. Otherwise, if you want to return something other than the thread text, change the threads.note reference to your desired threads field.
For example: -- Most recent thread entry per incident: substr(max(concat(date_format(threads.entered, 'YYYYMMDDHH24MISS'), concat(threads.seq, to_char(threads.note)))),16) -- The channel ID for the first thread entry: substr(min(concat(date_format(threads.entered, 'YYYYMMDDHH24MISS'), concat(threads.seq, to_char(threads.chan_id)))),16)