on 04-20-2007 7:21 PM
HI
I have a situation in hand.
The legacy system is sending the credit card number and the security number to XI system which then is passed to R/3 system while creating the orders.
The data is sent to XI through the HTTP post.
What I want to do is to mask the card number as 1234********5678 and the security number as *** . before the data is monitored in SXMB_MONI.
I dont wnat to make the card number avaliable in the monitoring but wnat to paa the exact card number to R/3
If anyone has any idea do let me know
Regards
Nikhil
We have encountered a problem where some orders are displaying the credit card in the order in va03 as partially masked. Certain people in our accounting department need to be able to see the entire credit card. Anyone know where this is being controlled?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
As explained above , you can restrict the monitoring the messages in moni
see the below links
restrict the messages from developers in SXMB_MONI - /people/michal.krawczyk2/blog/2006/01/02/xi-sxmbmoni--controlling-access-to-message-display
http://help.sap.com/saphelp_nw2004s/helpdata/en/12/5dd23aaad7b3408dde3c1577fda5b3/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/d0/c90f41026df223e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/882a40ce93185de10000000a1550b0/content.htm
Also you can resrtict the message / encrypt the messages , we can do , similarly we can use by Adapter modules.
Regards
Chilla
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
one quick thought oin this.....may u need to apply some encrytpion logic in sender and hence this will not reflected in moni and at the reciever side aplly the reverse of it (decryption) to get the card number.....check if this helps....and if u find or go to share ur exp on thios kindly keep posted
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nikhil,
I would suggest you a workaround on this. First while developing your interface you dont need to do anything since you will testing with some test data. But in production and quality you can restrict access to software components, integration scenario, interface and mapping objects aswell.
check with this blog:
/people/michal.krawczyk2/blog/2005/05/25/xi-how-to-add-authorizations-to-repository-objects
Also you restrict your message in sxmb_moni with this weblog:
/people/michal.krawczyk2/blog/2006/01/02/xi-sxmbmoni--controlling-access-to-message-display
So in you production and quality only the required users can see the message.
---Satish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.