Changing infotype Basic pay (IT0008) and then park it!

Question

Hie Guys!
We doing an implementation for a public service utility and these guys need tight authorisations on their salary reviews before they are taken as effective! One thing they want to happen is for a user to change a record linked to salaries like the Basic pay infotype, park it in the system before saving it and then one or two Super users has a look into it before it is passed on as effective.Meanwhile they would want the employee's basic pay  to still be at its previous level until they authorise it!
Please any GURUS out there give me a hand and sort this one out!
Tazkkl.

Answer 1

Hi,
Authorization objects enable complex checks of an authorization, which allows a user to carry out an action. An authorization object can group up to 10 authorization fields that are checked in an AND relationship.
For an authorization check to be successful, all field values of the authorization object must be maintained accordingly. The fields in an object should not be seen as input fields on a screen. Instead, fields should be regarded as system elements, such as infotypes, which are to be protected.
You can define as many system access authorizations as you wish for an object by creating a number of allowed values for the fields in an object. These value sets are called authorizations. The system checks these authorizations in OR relationships
Structural Authorizations
Structural profiles are assigned in a different way to general authorization profiles. To assign structural profiles, you use table T77UA (User Authorizations = Assignment of Profile to User), not Role Maintenance (PFCG transaction) as with general authorization profiles. The authorization profiles are specified in the T77PR table (Definition of Authorization Profiles).
You can protect (sub) structures by making relevant entries in this table
A useru2019s Overall Profile is determined from the intersection of his or her structural and general
authorization profiles, when you use both structural and general authorizations.
The structural profile determines which object in the hierarchical structure the user has access to; the general profile which object data (infotype, subtype) and which type of authorization (Read, Write, ...) the user has for these objects. The access mode for authorization objects in HR Master Data is determined in the AUTHC field (Authorization Level).
Steps to do Structural Authorization:
Step1: TC OOAC (table T77S0)
Activate the Structural Authorization switch
Step 2: TC OOSP
Create Structural Authorization profiles
Step 3: Assign Structural Authorization profile to user Id
Transaction Code: SE38 and assign report RHRPROFL0 enter object id for example (Organization unit)
Assign regular Role authorization
Table - T77UA (User Authorizations = Assignment of Profile to
User), not Role Maintenance (PFCG transaction)
The Table T77Pr - authorization profiles are specified in the T77PR table.
You can protect (sub) structures by making relevant entries in this table.
Rupa Prasad