My Oracle Support Banner

Bad Characters in Item Scan Prevents Persistence to Xcenter (Doc ID 3030197.1)

Last updated on JUNE 20, 2024

Applies to:

Oracle Retail Xstore Office Cloud Service - Version 23.2 and later
Information in this document applies to any platform.

Symptoms

In Xstore V21.0.2 Integrated with XOCS V24:

Users are seeing that on occasion a bad scan of an item will insert and persist bad characters within CDATA. This prevents the poslog data for the transaction from persisting the the xcenter db and broadcast to back end systems

Steps to Reproduce:

1. Login-->choose associate-->assign customer.
2. In the virtual scanner, copy and paste any item and include a bad character and hit enter.
3. Item not on file prompted...choose ok.
4. Enter required description/dept./price.
5. Once item is added to the sale, complete the sale tendering with cash.
6. Review the poslog and you will notice the poslog contains bad characters which are persisted to xcenter within item CDATA.

Expected: The invalid xml/bad characters should not prevent the poslog data from persisting to xcenter db and broadcast to backend systems.

Actual: The bad character causes the poslog data to be stuck in the xcenter replication queue and is unable to persist to the xcenter db and backend systems.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.