on 04-13-2015 6:39 AM
Hi
Transaction FB02 features in numerous risks in the standard GRC rule set.
Most users I am dealing with only require this transaction in order to change document line item and header level text, not payment terms, blocks, etc.
What is the most efficient way to render a risk-free version of this transaction? (i.e. only permit changes to text)
Thanks
Hi Lynton,
Did you find a solution to mitigate the FB02 risks?
Thanks,
Jay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lynton,
please check the note 827413.
Entries in customizing (OB32) "Document changes view" (V_TBAER) for "Field Can Be Changed" (field XAEND) can be made at "several" levels for each field.
for example:
AccTy Trans.Type Fld name CoCd Field Label Go to Details by double clicking on each line:
BSEG-SGTXT Text -> Field Can Be Changed
S BSEG-SGTXT Text -> Field Can Be Changed "X"
--> With this customizing entries, at FB02, field text can be changed only for line items that correpond to G/L accounts (S).
Other example, entries at OB32 are as follows:
AccTy Trans.Type Fld name CoCd Field Label Go to Details by double clicking on each line:
BSEG-SGTXT Text -> Field Can Be Changed "X"
S BSEG-SGTXT Text -> Field Can Be Changed " "
--> With this customizing entries, at FB02 text will displayed greyed only for those line items that correpond to G/L accounts (S).
Regards,
Monika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.