Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

How to restrict authorization on TCode PA48

Former Member
0 Kudos

Hi Everbody,

We have restricted authorization at state level.

A person sitting in state will be able to hire only his state people he will not be able to hire other state people.Till time we were using PA40 for hiring

Now the situation is we have started using PA48 that hiring thorugh Erec.In this case the person sitting in state is now able to hire all the state people .

How to restrict this authoriztaion on hiring through PA48.Is there any objects available or do we create another object.or we need to create ZPA48.

1 ACCEPTED SOLUTION

former_member74904
Contributor
0 Kudos

I'm not sure on how your authorization concept is set up, but checks are being made on P_ORGIN and/or P_ORGXX when executing the hire function in PA48.

as Alex suggested doing a trace can be helpful in getting a more detailed view on the problem.

6 REPLIES 6

Former Member
0 Kudos

What does the trace say when you run it for PA48?

former_member74904
Contributor
0 Kudos

I'm not sure on how your authorization concept is set up, but checks are being made on P_ORGIN and/or P_ORGXX when executing the hire function in PA48.

as Alex suggested doing a trace can be helpful in getting a more detailed view on the problem.

Former Member
0 Kudos

Hi,

We have the same problem with PA48 transaction.

Have you find a solution ?

Thank you in advance

Sophie

Former Member
0 Kudos

I think Trace analysis can be the only solution for resolving it.. Check what authorization objects are checked during hiring of the people of own state and during hiring of other state.. Find out the difference and authorization canbe restricted accordingly.

For this you may have to add new check maintain in the transaction. For this new Z-transaction is preferred to make the changes. We should avoid changes of sap standard trxs.

The following infotypes are part of the hiring action and will be edited in the same sequence when the hiring action is performed:

This might be helpful to you:

0000 - Actions (to capture employee movement info in the organization)

0001 - Organizational Assignment (to capture employee positioning in the organization)

0002 - Personal Data

0006 - Address

0007 - Planned Working Time (Store planned working hours for the employee.)

0008 - Basic Salary

0009 - Bank Details

0014 - Recurring Payment

0015 - Additional payment

0016 - Contract Elements

2006 - Absence Quotas

Regards,

Sandip

0 Kudos

Hy,

According to the trace, unfortunately there is only an authorization check on the Tcode but no authorization check on company or country.

Sophie

0 Kudos

Try a trace in a DEV or QAS system where you only have one server? ST01 is server specific! (or switch servers in SM51).

Another possibility is that you are a consultant without an HR structural profile on a client's site because you are a vendor, and you have not secured SAP*'s profile as a part of your consulting? This should be one of the first things to do...

If you have a QA system with anonymized data in it, then reset a "real employee's" password and run PA48 with a trace on that user.

Chances are good that you will see the checks appearing...

Cheers,

Julius