Field Update and Invalid Data Update Problems in Payment Method (Doc ID 859125.1)

Last updated on JUNE 22, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.1]
Information in this document applies to any platform.
***Checked for relevance on 08-Nov-2012***

Symptoms

For a Credit Card Payment method:
1) Invalid data update to the Payment Method is accepted but then the payinfo cannot be updated again.
2) Updating all of the inherited fields of a substructure updates none of them, while updating one less than all the fields updates everything correctly.


Steps To Reproduce:

1. Create an account with a valid credit card (card number 4444111122223333).
2. Manage the Payment Method to update all the fields including country.
         Expected Result: Fields are all updated in the object.
         Actual Result: Object gets new revision but no fields are actually updated.
3. Manage the Payment Method and set the card number to "123456" (invalid card number).
         Expected Result: Validation error.
         Actual Result: Data is written to the database, with the side effect that the payment method is corrupted beyond fixing.
4. Try to Manage the Payment Method again - nothing happens (dialog is not displayed).

Note that the above issue can be reproduced using Customer Center or testnap.




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