Pin_crypt_app Utility Behavior is Different
Last updated on SEPTEMBER 19, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On Billing and Revenue Management (BRM) version 7.5.0 Patch Set 17.
Using encryption feature of BRM to store BANK_NO and DEBIT_NUM fields in PAYINFO_DD_T table for DD(Direct Debit) customer types.
However, it was observed that the encrypted value using pin_crypt_app utility is not same as the value that is stored in BRM DB using pin_crypt_upgrade utility.
Created Account with BANK_NO and DEBIT_NUM as 123456. Below snapshot shows its encrypted value in PAYINFO_DD_T table.
Output of pin_crypt_app utility for value 123456 is :
Why pin_crypt_app utility is generating different values at different places?
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