Customer Order Request XML Has Duplicate Sequence Numbers For All The Payments In Case of Multiple Tenders (Doc ID 2101030.1)

Last updated on MARCH 27, 2017

Applies to:

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

Symptoms

In case of multiple payments for a transaction performed on Point of Service(POS), the line <seq_no> tag is not getting increased to the next value rather all the sequence numbers are set to zero therefore while OMS tries persist the Payment line into its own table it fails with the integrity constraint error as the seq_no column is also a part of primary key in the Order Management System.

Steps to recreate the issue:

1. Create a Customer Order and use Credit, Cash tenders for Payment.
2. Notice that the Customer Order XML generated has below payment details showing <ns20:seq_no>0</ns20:seq_no> 

           <ns20:seq_no>0</ns20:seq_no>
           <ns20:payment_type>CREDIT</ns20:payment_type>
           <ns20:currency_code>USD</ns20:currency_code>
           <ns20:amount>48.00</ns20:amount>
           -----------------------------------------------------
           <ns20:seq_no>0</ns20:seq_no>
           <ns20:payment_type>CASH</ns20:payment_type>
           <ns20:currency_code>USD</ns20:currency_code>
           <ns20:amount>63.70</ns20:amount>

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms