Transaction Limiting ability to write

[Former Member]

When changing authorization objects, is there an ability to limit as to what field is modifiable. For example FBL5N if you drill down within that display of documents to the document level, and would like to modify it you will have the ability to modify all fields. In SAP is there a way to limit what fields may be modified. For example modify text but not any payment terms etc........

THanks as always.

[Former Member]

Hi Maritza, the answer is "it depends".

in XD02 for example, you can restrict access to maintain certain fields (controlled by F_*_AEN objects) via the auth concept, but in others there are configuration options which flag the availability of a field. Some can be controlled via user statuses too (I'm sure there are plenty more).

Other transactions don't have either options and you can use transaction variants (tx SHD0) to make some screen display only etc.

In the case of FBL5N you need the underlying auth to modify the financial doc (as in FB02) and from memory I don't <i>think</i> you can have field level security as standard for this tx.

[Former Member]

Hi Maritza, the answer is "it depends".

in XD02 for example, you can restrict access to maintain certain fields (controlled by F_*_AEN objects) via the auth concept, but in others there are configuration options which flag the availability of a field. Some can be controlled via user statuses too (I'm sure there are plenty more).

Other transactions don't have either options and you can use transaction variants (tx SHD0) to make some screen display only etc.

In the case of FBL5N you need the underlying auth to modify the financial doc (as in FB02) and from memory I don't <i>think</i> you can have field level security as standard for this tx.