My Oracle Support Banner

Pin_crypt_app Utility Behavior is Different (Doc ID 2306089.1)

Last updated on JULY 08, 2022

Applies to:

Oracle Communications Billing and Revenue Management - Version 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?


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

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