Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.4.0]
Information in this document applies to any platform.
Custom reports run under SAP BusinessObjects Enterprise XI, version 12.1.0.
The reports read some BRM OOB fields such as PAYINFO_CC_T.debit_num which are encrypted with MD5 with prefix "&md5|". When using pin_crypt.dll from BRM 7.3.1, it can decrypt this field correctly.
However, on an upgraded BRM system (7.4 PS17), the DB is using a stronger encryption AES. The same debit_num field cannot be decrypted with pin_crypt_aes.dll which came from BRM 7.3.1 as in BRM 7.4, pin_crypt_aes.dll cannot be found anywhere.
1) Does 7.4 version of pin_crypt_aes.dll exist?
2) Did the AES encryption format change between v7.3.1 and 7.4 PS17?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms