Infotye Authorization

[Former Member]

Client Req is in PA30 screen, HR Users maintains Master Data through some Master data Infotypes & FI Users use Payroll Infotypes for Payroll processing like 0008, 14,15, 580- 591.

Now the problem is for FI users Master Data Infotypes like 0000, 0001, 0002 et.., should be in display mode, not in editable mode whereas payroll Infotypes can be created, changed & deleted.

can this be acheived throug some authorizatio something?? If so can any1 explain how todo the same...

[Former Member]

answered

[sikindar_a]

hi

Define the Roles in the tcode PFCG

and give the Autorisations as per the Roles which u want for the user according to that Infotypes

for reading give R like that

[Former Member]

Hi,

the authorizations can be provided on infotypes level.

Authorization Object: P_ORGIN HR: Master Data

Fields: INFTY Infotype

SUBTY Subtype

AUTHC Authorization level

PERSA Personnel Area

PERSG Employee Group

PERSK Employee Subgroup

VDSK1 Organizational Key

Definition:

The object HR: Master data (P_ORGIN) is used for authorization checks of personal data. Checks are performed only when INFTY HR infotypes are edited or read.

When you call up a transaction for editing of personal data, the system checks that you at least have one read authorization ( AUTHC_D authorization level R). If you do, a more specific authorization check is carried out within the transaction. In HR reports that use the <DS:RE.SAPDBPNP logical database PNP , the system checks whether the user has a read

authorization for all infotypes before it displays the selection screen. This is then followed by a more precise check for each selected person. The authorization objects .S_PROGRAM ABAP/4:

Program run checks and UO.P_ABAP HR:

Reporting must also be taken into account.

Note that values specified for the individual fields do not generally contain other values. The value ' ' must therefore be specified explicitly. The value ' ' must always be used for the subtype field (reason: the field is initial if the infotype does not support any subtypes, or if the subtype has not been specified).

Field Details:

INFTY Infotype

SUBTY Subtype

AUTHC_D Authorization level

PERSA Personnel area

PERSG Employee group

PERSK Employee subgroup

VDSK1 Organizational key .

This will give you over view of authorization check but this job is done done by basis consultant.

chandu

[Former Member]

Hi,

In addition to the above mentioned fields for authorization, if you want to add any new fields like personal subarea this can be also done.

Depending on these fields you can filter the access to the infotypes on various conditions.

But yes it is very true you will need to create two roles and then add the P_ORIGIN object and depending on your field defne the authorization in this object.

Thanks

Santoshi

[former_member583520]

Hi,

This one is possible through the authorization.

Pls ask the basis consultant and tell them what you want for HR and FI authorization particularly.

Then they will do the process.

Thanks and Regards,

Revathi.

[Vivek_V]

Of course this will be achieved through Authorisation.

In Authorisation you create roles. In your scenario you need to have two roles

- one for maintenance of HR InfoTypes

- two for maintenance of Payroll InfoTypes and display of HR InfoTypes

VK