RE: [sap-acct] BKPF & Credit Card Number tokenization
Posted by
Admin at
|
Share this post:
|
|
0 Comments
 | Posted by ebushman (VP, Solutions Engineering) on Feb 1 at 3:10 PM |  Mark as helpful |
LOL!
Dave,
I did have a look in my own ECC 6 system before posting this. There is no credit card field with a CCNUM domain. However, I did ask around internally as well after posting and learned that some customers with IS solutions (like AFS which I believe Rahul is using) do appear to have credit card number fields in BKPF, but (as you point out) with different domains than CCNUM. The CCNUM_30F is a good example.
The consultant from our sister company PrimeSys who is working with Rahul replied to me that he would get with Rahul on this. It may be that they simply change the domain to CCNUM, it may be that they also add a conversion exit to the CCNUM_30F domain.
But yes, that was a bit of a curveball!
Eric W. Bushman
Vice President, Solutions Engineering
www.paymetric.com<http://www.paymetric.com>
________________________________
From: Dave Thornburgh via sap-acct [mailto:sap-acct@Groups.ITtoolbox.com]
Sent: Monday, February 01, 2010 1:25 PM
To: Eric Bushman
Subject: RE: [sap-acct] BKPF & Credit Card Number tokenization
[http://userimages.toolbox.com/user/b_138126.jpg]
Posted by Dave Thornburgh
on Feb 1 at 2:52 PM
[http://images.ittoolbox.com/vt/icons/vote.png]Mark as helpful<http://it.toolbox.com/api/ContentVote/3275188/1/1/>
Eric -
It looks like we caught you, this time.
There is in fact a CCNUM field in BKPF - at least in ECC6. Since we jumped
all the way from 4.0B, I don't know when the fields (that and CCINS) were
added. The underlying domains are different, though (CCINS_30F and
CCNUM_30F).
The data appear to be copied into BKPF long after transactional
encryption/tokenization normally takes place - the values in BKPF are not
normally cleartext. On the other hand, the OP sounded as if they're trying
to mass tokenize data already in place from existing transactions. If
that's the case, then I repeat - the program being used was not written or
implemented properly.
[imagines sounds of EB rapidly scrambling to examine his own source code]
:)
Dave
From: ebushman via sap-acct [mailto:sap-acct@Groups.ITtoolbox.com]
Sent: Saturday, January 30, 2010 6:45 AM
To: Dave Thornburgh
Subject: RE: [sap-acct] BKPF & Credit Card Number tokenization
Posted by ebushman (VP, Solutions
Engineering)
on Jan 30 at 9:45 AM
<http://it.toolbox.com/api/ContentVote/3271753/1/1/> Mark this reply as
helpfulMark as helpful
Rahul,
The BKPF table doesn't have a standard Credit Card Number field so it
appears that the field was added as a custom field at some point.
Is the field name "CCNUM" and does it link to the domain CCNUM? If not that
could explain why it isn't being picked up (per Dave Thornburgh's comment)
and there may be custom code somewhere else that was added to enable the
encryption functionality you were previously using.
Eric Bushman
www.paymetric.com<http://www.paymetric.com>
________________________________
From: Dave Thornburgh via sap-acct [mailto:sap-acct@Groups.ITtoolbox.com]
Sent: Friday, January 29, 2010 3:04 PM
To: Eric Bushman
Subject: RE: [sap-acct] BKPF
[http://userimages.toolbox.com/user/b_138126.jpg]
Posted by Dave Thornburgh
on Jan 29 at 4:17 PM
[http://images.ittoolbox.com/vt/icons/vote.png]Mark as
helpful<http://it.toolbox.com/api/ContentVote/3271206/1/1/>
Rahulv -
If you're doing tokenization, that is provided by third party software. If
it's not taking care of CCNUM in all tables everywhere, then it's not
written (or implemented) correctly. Contact your vendor.
Dave
From: rahulv via sap-acct [mailto:sap-acct@Groups.ITtoolbox.com]
Sent: Friday, January 29, 2010 7:27 AM
To: Dave Thornburgh
Subject: [sap-acct] BKPF
Posted by rahulv (SAP FICO
Consultant)
on Jan 29 at 10:34 AM
when we are tokenizing the credit card number, all tables are getting
updated, except the BKPF table
when we are tried to encrypt it there was no problem with the BKPF table...
but why its a problem when you are decrypting it and tokenizing or masking
Please provide any suggestions or any OSS Notes on this
Appreciated
__.____._ Dave,
I did have a look in my own ECC 6 system before posting this. There is no credit card field with a CCNUM domain. However, I did ask around internally as well after posting and learned that some customers with IS solutions (like AFS which I believe Rahul is using) do appear to have credit card number fields in BKPF, but (as you point out) with different domains than CCNUM. The CCNUM_30F is a good example.
The consultant from our sister company PrimeSys who is working with Rahul replied to me that he would get with Rahul on this. It may be that they simply change the domain to CCNUM, it may be that they also add a conversion exit to the CCNUM_30F domain.
But yes, that was a bit of a curveball!
Eric W. Bushman
Vice President, Solutions Engineering
www.paymetric.com<http://www.paymetric.com>
________________________________
From: Dave Thornburgh via sap-acct [mailto:sap-acct@Groups.ITtoolbox.com]
Sent: Monday, February 01, 2010 1:25 PM
To: Eric Bushman
Subject: RE: [sap-acct] BKPF & Credit Card Number tokenization
[http://userimages.toolbox.com/user/b_138126.jpg]
Posted by Dave Thornburgh
on Feb 1 at 2:52 PM
[http://images.ittoolbox.com/vt/icons/vote.png]Mark as helpful<http://it.toolbox.com/api/ContentVote/3275188/1/1/>
Eric -
It looks like we caught you, this time.
There is in fact a CCNUM field in BKPF - at least in ECC6. Since we jumped
all the way from 4.0B, I don't know when the fields (that and CCINS) were
added. The underlying domains are different, though (CCINS_30F and
CCNUM_30F).
The data appear to be copied into BKPF long after transactional
encryption/tokenization normally takes place - the values in BKPF are not
normally cleartext. On the other hand, the OP sounded as if they're trying
to mass tokenize data already in place from existing transactions. If
that's the case, then I repeat - the program being used was not written or
implemented properly.
[imagines sounds of EB rapidly scrambling to examine his own source code]
:)
Dave
From: ebushman via sap-acct [mailto:sap-acct@Groups.ITtoolbox.com]
Sent: Saturday, January 30, 2010 6:45 AM
To: Dave Thornburgh
Subject: RE: [sap-acct] BKPF & Credit Card Number tokenization
Posted by ebushman (VP, Solutions
Engineering)
on Jan 30 at 9:45 AM
<http://it.toolbox.com/api/ContentVote/3271753/1/1/> Mark this reply as
helpfulMark as helpful
Rahul,
The BKPF table doesn't have a standard Credit Card Number field so it
appears that the field was added as a custom field at some point.
Is the field name "CCNUM" and does it link to the domain CCNUM? If not that
could explain why it isn't being picked up (per Dave Thornburgh's comment)
and there may be custom code somewhere else that was added to enable the
encryption functionality you were previously using.
Eric Bushman
www.paymetric.com<http://www.paymetric.com>
________________________________
From: Dave Thornburgh via sap-acct [mailto:sap-acct@Groups.ITtoolbox.com]
Sent: Friday, January 29, 2010 3:04 PM
To: Eric Bushman
Subject: RE: [sap-acct] BKPF
[http://userimages.toolbox.com/user/b_138126.jpg]
Posted by Dave Thornburgh
on Jan 29 at 4:17 PM
[http://images.ittoolbox.com/vt/icons/vote.png]Mark as
helpful<http://it.toolbox.com/api/ContentVote/3271206/1/1/>
Rahulv -
If you're doing tokenization, that is provided by third party software. If
it's not taking care of CCNUM in all tables everywhere, then it's not
written (or implemented) correctly. Contact your vendor.
Dave
From: rahulv via sap-acct [mailto:sap-acct@Groups.ITtoolbox.com]
Sent: Friday, January 29, 2010 7:27 AM
To: Dave Thornburgh
Subject: [sap-acct] BKPF
Posted by rahulv (SAP FICO
Consultant)
on Jan 29 at 10:34 AM
when we are tokenizing the credit card number, all tables are getting
updated, except the BKPF table
when we are tried to encrypt it there was no problem with the BKPF table...
but why its a problem when you are decrypting it and tokenizing or masking
Please provide any suggestions or any OSS Notes on this
Appreciated
Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
In the Spotlight
Share Knowledge About SAP Scripting. Join the New Discussion Group
View this thread online
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
_.____.__ 
