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.
How does the milestones and milestone_instances tables work?
Environment:
February 2015 Console
Resolution:
If you recently upgraded to the February 2015 version, you will be able to view canned milestones "Resolution Due" for an incident after a new site is created or upgraded.
For SLAs that have response times defined, you can have resolution due dates and times calculated automatically. Times are calculated when an SLA instance is added to an incident.
To create the incident milestones report you can follow the below steps:
1. Create a new report with the following column definitions.
Initial Response Status
if(incidents.status_type=2,100,round(((date_diff(sysdate(), incidents.rel_due))*-1)/60,0))
Initial Response Due
incidents.rel_due
Time Remaining
if(incidents.status_type=2,0,round(((date_diff(incidents.rel_due, sysdate())))/60,0))
Resolution Due Status
round(((date_diff(sysdate(), milestone_instances.due_date))*-1)/60,0)
Resolution Due
milestone_instances.due_date
if(incidents.status_type=2,0,round(((date_diff (milestone_instances.due_date,sysdate())))/60,0))
2. Use the following conditional formatting for the Initial Response Status and Resolution Due Status columns.
Greater than 15
Image Only
Flag
Green
Less than or equals 0
Red
Less than or equals 15
Yellow
3. Use the Minutes (Days, Hours, Minutes) format for both Time Remaining columns.
4. Set the following report options to refresh the data regularly:
5. Clear all of the check boxes in the Customize Record Commands window so that no commands will be available at runtime.
6. Click the Save and Close button to save the custom report and exit the report design center.
Technical Architecture:
Table ‘milestones’
milestone_id – Primary key for this table. There would be one canned milestone currently, which would be ‘Initial Resolution Due’.
Name – The name of the milestone. This would be unique. In this release only one canned milestone would be created, i.e. ‘Initial Resolution Due’. When we support custom milestones a new canned milestone ‘Initial Response Due’ would be also added. These two milestones would be applicable to all SLAs.
Table 'milestone_instances'
i_id – The incident ID this record is associated too. Foreign key refers i_id from incidents table. This is a composite primary key with milestone_id.
milestone_id - The milestone ID for this record. This is a foreign key referring milestone_id in milestones table. One incident can have only one type of milestone associated. This is a composite primary key with i_id.
due_date - This would store the due_date for the milestone. In this release it would only store resolution due date time value for the incident. It would be updated based on algorithm currently used for initial_response_due field on table ‘incidents’. This would be a read-only field for clients (CX/MAPI/CP).
For more information, refer to the Configuring resolution due calculations section in online documentation for the version your site is currently running. See also Create the incident milestones report. To access Oracle B2C Service manuals and documentation online, refer to the Documentation for Oracle B2C Service Products.