My Oracle Support Banner

Duplicate Layaway Number Generated With Different Customer ID (Doc ID 1954468.1)

Last updated on JUNE 13, 2017

Applies to:

Oracle Retail Point-of-Service - Version 13.3 to 14.0 [Release 13.3 to 14.0]
Information in this document applies to any platform.

Symptoms

In an Oracle Retail Point of Service (ORPOS) a duplicate layaway number was found in the database associated with a different customer ID.

Prerequisites:

1. Customer A has a layaway transaction with a balance due.
2. Customer B has a layaway transaction with a balance due.

Steps to reproduce:

1. Scan the layaway number of Customer A to complete it.
2. Note that the system retrieves the layaway information for Customer B.

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.