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:
Mailboxes, Sites updating to August 2013 or newer
Resolution:
This answer is applicable if you have been informed that you have duplicate mailboxes.
There must be a 1:1 correspondence between pop accounts and mailboxes enabled for incoming mail across your site/s. The reply to or from address for a pop account can be used in multiple mailboxes across interfaces, but they must be enabled for only outgoing mail.
If you do not intend to create incidents assigned to a particular interface with the duplicate mailbox:
Simply remove the pop details from one mailbox and disable incoming mail. Since techmail runs in parallel on each interface, you may find slightly better performance if you choose to leave the mailbox enabled on an interface which has fewer mailboxes enabled for incoming mail.
Simply remove the pop details from one mailbox and disable incoming mail.
Since techmail runs in parallel on each interface, you may find slightly better performance if you choose to leave the mailbox enabled on an interface which has fewer mailboxes enabled for incoming mail.
If you do intend to create incidents assigned to a particular interface with the duplicate mailbox:
Check for some other mechanism (such as business rules) that assigns incidents to a particular interface. If there is no mechanism then there are probably incidents created by techmail assigned to both interfaces contrary to your business process. If there is a mechanism in place you will have to make changes to the mechanism to allow it to function with a new mailbox on the duplicate interface or with all mail arriving on one interface. Then either create a new mailbox enabled for both incoming and outgoing mail and assign it to the duplicate interface; or disable incoming mail from the duplicate mailbox and remove the pop information.
Check for some other mechanism (such as business rules) that assigns incidents to a particular interface. If there is no mechanism then there are probably incidents created by techmail assigned to both interfaces contrary to your business process.
If there is a mechanism in place you will have to make changes to the mechanism to allow it to function with a new mailbox on the duplicate interface or with all mail arriving on one interface. Then either create a new mailbox enabled for both incoming and outgoing mail and assign it to the duplicate interface; or disable incoming mail from the duplicate mailbox and remove the pop information.
Cause:
Pulling mail from the same mailbox from two interfaces confuses product processes which assign created incidents to a specific interface (or brand).