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:
May 2015 and newer, any version if the site has an upgrade to May 2015 and newer in progress
Resolution:
Starting with May 2015 we are preparing to integrate a new Social experience with the Customer Portal, which is an alternative to (and will replace in the future) the Legacy Community beginning with the August 2018 version of the product. The new Social environment will allow logins for both agents and contacts; to accommodate this change, a new table called common_users has been created, in order to identify each individual. Due to this feature, the contacts and accounts records will begin to each have a corresponding record in the new table. More specifically, new accounts will have their ID's equal to their respective common_user_id. Since the common_users table is shared between contacts and accounts and considering newly created accounts require a unique common_user_id, gaps in the ID index will occur. This feature will affect all sites that were released in May 2015 or later. This will also impact sites which are in the process of upgrading to August 2015 or later versions, as the upgrade-pre steps will allocate common_user_id's for the existing accounts and contacts.
Within the common_users table, records will be sharing the same id space for that table's primary key "common_user_id". As a result, newly created accounts will be given the next available common_user_id's for their account_id's.
Example: common_user_id Record 1 account (acct_id) 2 contact (c_id) 3 contact (c_id) 4 account (acct_id) 5 account (acct_id) common_user_id = c_id or acct_id
Example:
common_user_id
Record
common_user_id = c_id or acct_id
For this reason, possible gaps in the accounts.acct_id values can occur because the common_users.common_user_id column that pulls its last_insert_id from is frequently incremented by other product transactions, for example newly created contacts.