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:
Oracle B2C Service, Product listing Knowledge Advanced
Resolution:
If the question is in Japanese characters on an en_US-configured interface, this implies the question is in en_US (English/United States) language. In such a case, very limited Japanese keyword searching is supported as the question is considered as English. The Japanese language is a very contextual language and it might only work for a single character in Japanese if it is not a skip list.
To support Japanese language search, it is required to have Japanese language selected as part of the search request. Beyond a potential customized solution, this is accomplished by default from the interface locale. There can only be one language mapped to an Oracle B2C Service Interface, and similarly there can only be one Knowledge Advanced locale mapped to an Oracle B2C Service Interface. This means that if Japanese characters are to be accepted in search a Japanese language pack should be applied to the Oracle B2C Service interface, and a locale mapped to the Japanese language should be associated with that interface within Knowledge Advanced Authoring.
This is not to say that some searches using Japanese characters with such a setup will always not return results. The chief problem would be tokenization. The English tokenizer will treat any sequence of Japanese characters as a single token, but the OLT Japanese tokenizer might see it as several. So the tokens / stems that the English parser tries to find might not appear in the content at all, even if the raw individual characters do. If a document is auto-recognized as Japanese it won't use the English tokenizer, it'll use the Japanese one, so there will be a mismatch. Even if it's regarded as an English doc, if there's a phrase or sentence in Japanese, it'll all probably be treated as a single large token. Further, the tokenizer won't do anything at all with Japanese grammar, which is more morphological (word endings change) than syntax (different word order).