cancel
Showing results for 
Search instead for 
Did you mean: 

CreditCard numbers masked when performing a select query on BP with CC's

Former Member
0 Kudos

Hello,

We just upgraded our 8.8 PL11 db to PL14. Now, when I run a SQL Query:


SELECT T0.CardCode, cast(T0.CrCardNum as varchar(100)) + '     ' + CAST(T0.CardValid AS VARCHAR(11)) +  '   ' + T1.PymntGroup
 FROM OCRD T0
INNER JOIN OCTG T1 ON T0.GroupNum = T1.GroupNum

the output shows the Credit Card Number as an encrypted/masked string. Is this an undocumented change? Or a bug? or am I missing a setting somewhere?

Thank You in advance!

Curt

Accepted Solutions (1)

Accepted Solutions (1)

K_Pauquet
Advisor
Advisor
0 Kudos

Hi Curt,

please check here:

Administration -> Systsem Initialisation -> Company Details -> Basis Initialisation

There is a checkbox for 'Mask Credit Card Number'. Once you untick that your query should work ok.

Please see also SAP Note 1470529.

All the best,

Kerstin

Former Member
0 Kudos

I work with the 8.8.2 pl9

and after I've checked the box for 'Mask Credit Card Numer', I can't uncheck it.

I have Professional User license and it's a It's a Superuser.

Is there something else I need to do to untick it?

Shai

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Curt,

You can check it from SQL Server Management Studio to see if they are encrypted or not.

Thanks,

Gordon

Former Member
0 Kudos

Gordon, if you meant for me to attempt executing this script in MSSMS, I did, and this also returned an encrypted string.

Or do you mean for me to check a setting on the db properties?

Thanks again,

Curt

Former Member
0 Kudos

Check the setting on the db table properties.

Former Member
0 Kudos

The only difference I can see, is from the old PL11 OCRD table where the CrCardNum length is 20, and now in PL14 it's 64, and the size used to be 40 and now it's 128...

Any other ideas?

Thanks again Gordon

Former Member
0 Kudos

128 is in need for encrypt. That is the evidence the table is now meet PCI security requirement.