Field Level Security in Travel Management

[Former Member]

Hi,

We have a requirement in Travel Management where we need to restrict field level authorisation.

Once the Traveler submit the request & its approved by manager further it goes to accountant who does the screening & settlement part, here the account can modify the trip details such as expense type, Amount field, cost center & VAT code.

Our requirement is to restrict some fields which cannot be modified by accountant once the trip is approved how can we achive this scenario. the Authorisation object we are using is P_TRAVL.

Any idea suggestion.

Regards

Swapnil.

[Former Member · Accepted solution]

Hello,

For this please create transaction screen variant ,and map with user group they will have access to only modify certain feild values other will remain greyed out.

the tcode to create Transaction Variant is SDH0,please check with ABAPER tey will help you more.

Thanks,

Prasant

[Former Member]

Can we restrict Travel Approver to not able to make changes to the requests? The requirement is that the Trval approver should not be able to make changes to the requests and at the same time able to approve it as well.

In the P_TRAVL object, for approval to be successfull the object values below is required, and change access to requests is also using the same object values, hence if i remove the values below approval will fail eventhough changes to requests is restricted.

W11 AUTHF

21 AUTHS

Appreciate any help from any experts here.

Thanks

[Former Member]

This message was moderated.

[Former Member]

Dig S_TABU_LIN and check if this solution works. It worked for me for one requirement of field level security.

Let us know if this fits.

Thanks

Abhishek