PA 30 Trasaction iview - Employee's own infotype records

[Former Member]

Hi,

Is there any way to create a trasaction iview for PA30 in Portal. It should directly get the employee;s own infotype records.

For example, Portal user id with "ESS_User" mapped to ECC user id "ESS_User" should retrieve the personnel number (pernr) infotype records attached to this "ESS_User" user id.

Is it possible through application parameter in transaction iview ? I know it might very tough to pass and control this application parameter.

The reason behind here is, there are so many infotype records which we need to publish and display in ESS which are not part of standard ESS services.

Please share your experiences, if it is possible through some other work around.

Regards,

Anil Kumar

[stuart_campbell]

Hi

From what I understand you want a Portal transaction similiar to PA30 specifically for an ESS end user?

this is because you want employees to maintain more of their own infotypes than the current ESS scenarios provide

The delivered ESS scenarios are specifically geared to Personal Information changes that may not have wider effects on payroll, employee status or other administrative level changes

HCM process and forms is indeed a useful new functionality provided by SAP but it is more geared

to HR administrators who have more than 1 PERNR to administrate and is specifically to open

the functions of PA40 via the Portal. In your example I believe you want an ESS end user have PERNR specific

access to PA30 for initial infotype maintainence rather than employee status or data changes.

It may be possible by assigning an employee an HR admin role with only responsibility for their own PERNR to allow end users to see and change more infotypes in the standard scenarios or by adding more infotypes to a custom scenario (say a MY_FIRST_DAYS process) - however some of the available infotypes or changes may have more of an impact than the delivered ESS persinfo scenarios - some could be administrative level changes affecting payroll or other HR operations - e.g increase salary etc - this would depend on how restricted the HR administrator role and scenarios are configured . Also unlike PA30 not all infotypes are available automatically via HCM process and forms - although the solution is flexible enough for you to add the ones you require

Best wishes

Stuart

[Former Member]

Hi Anil Kumar Venkatappa

I have the same issue. How solved this issue?

Kind Regards

[Former Member]

Hello,

As explained by straut, it is quite possible using the HR authorization objects (P_PERNR or P_ORGIN). However, it is lengthy process and lot of the basis work should be done by administrator for each of the pernr and each infotype object.

I did not liked the solution and therefore proceeding with HCM P & F framework provided by SAP which is a powerfull configurator workbench for mainitaning HR master data using employee-manager-HR approval processes.

Hope this helps.

Regards,

Anil Kumar.

[Former Member]

Hi Anil Kumar Venkatappa

I want use HCM Process & Forms, but the problem are the licence of Adobe.

I propouse this solution in the company.

I know when have that buy the licence of Adobe Cycle.

Kind Regards.

[Former Member]

Hi,

You can please get the information from following link

https://wiki.sdn.sap.com/wiki/display/EP/Creation%20of%20Different%20Types%20of%20iViews%20in%20EP%2...

[stuart_campbell]

Hi Anil

Unless I am missing an already existing transaction in R3, there is no way in the standard customizing to do this you are essentially creating a new user screen with no personnel number selection field and a transactional call which checks PERNR access for this user

I think instead maybe you should look at HR authorizations for R3 users - perhaps P_PERNR or P_ORGIN authorization objects can hellp deliver the requirement

Best wishes

Stuart