09-03-2009 4:30 PM
All,
I am trying to secure XD02 so that the end user is able to VIEW all tabs but only add credit card data to the Payment Transaction tab. I did a trace on the activity and is still unsuccessful in securing this function. I tried using XD03 and just securing F_KNA1_APP to C1 still does not work. Any help would be appreciated.
09-07-2009 4:21 PM
Hi Daisy,
the data you are trying to restrict comes from KNA1 table and is at client level - which means this data is independent of either the company code nor the sales area
The object F_KNA1_GEN controls this data in the Payment transactions tab. please note that even if you have activity 03 for this value and if you have Bank Master data maintenance to the same user (transaction FI01, FI02) he will still be able to edit the payment transactions.
In a ideal set-up, the customer general data once set-up by a responisble team shouldnt be changed by the end-users, they should be able to create views for their company code and sales areas but not modify the general data. Achieving this is a extrermely difficlut task of you have customers shared between companies
But, if you can secure the set-up, then you can have F_KNA1_GEN as a display for the end-users and make use of the BAPI BAPI_CREDITCARD_CHECK to give access to payment card maintenance functionality
Either ways: It is complex situation and needs some careful thought and planning
09-03-2009 4:38 PM
<copy_and_and_paste_from_SU21_removed_by_moderator>
@ Prasant: Next time your user ID will be removed...
Please read the forum rules!
Julius
Edited by: Julius Bussche on Sep 3, 2009 7:24 PM
09-07-2009 4:21 PM
Hi Daisy,
the data you are trying to restrict comes from KNA1 table and is at client level - which means this data is independent of either the company code nor the sales area
The object F_KNA1_GEN controls this data in the Payment transactions tab. please note that even if you have activity 03 for this value and if you have Bank Master data maintenance to the same user (transaction FI01, FI02) he will still be able to edit the payment transactions.
In a ideal set-up, the customer general data once set-up by a responisble team shouldnt be changed by the end-users, they should be able to create views for their company code and sales areas but not modify the general data. Achieving this is a extrermely difficlut task of you have customers shared between companies
But, if you can secure the set-up, then you can have F_KNA1_GEN as a display for the end-users and make use of the BAPI BAPI_CREDITCARD_CHECK to give access to payment card maintenance functionality
Either ways: It is complex situation and needs some careful thought and planning