2.1 Using Auto-Authorization Feature

This topic gives information on using Auto-Authorization Feature.

You must map the user groups to the menu items or the task for which auto-authorization is applicable to allow the auto-authorization feature for a user group and a certain set of menu items using the Auto Auth screen.

You can use this screen to map user groups to the tasks for which Auto-authorization is applicable. If the User Administrator or the Module Administrator users do not maintain the setup for each of the user groups in this screen, the auto-authorization is not enabled for that user group.

For UT transaction screen, you can derive auto authorization status along with branch, Function ID and User Level Auto Auth Preference using Auto Auth screen. If the Branch, Function ID and menu level auto auth maintenance is derived as A, then you should auto authorize a UT Transaction record.

• First priority will be Infra level Auto Auth Derivation (branch, function ID and user level).
• Second priority will be Auto Auth Derivation based on Auto Auth setup maintenance SMDAUTAU.
• Third priority will be Auto Auth derivation FBC Access restriction detail UTDFAR.

If in all three levels if the auto auth check is returning TRUE, then the system will auto authorize a record.

Table 2-2 Priority and Auto-Authorization

Priority	Auto-Authorization
First	If there is no maintenance done in FBC Access restriction detail UTDFAR, then auto auth check will happen using Infra level Auto Auth Derivation and Auto Auth Setup Maintenance SMDAUTAU.
Second	If there is no maintenance done in Auto Auth Setup Maintenance SMDAUTAU, then auto auth check will happen using Infra level Auto Auth Derivation and FBC Access restriction detail.
Third	If there is no maintenance done in Auto Auth Setup Maintenance SMDAUTAU and FBC Access restriction detail UTDFAR. Then auto auth check will happen using Infra level auto auth derivation.