PPOME - taking away transport request

Question

Hello,
I was hoping someone with PPOME / workflow knowledge could help me here... Currently, are company locks down the transaction code PPOME, meaning you have to submit a transport request any time making a change to the struture, when a user...
THe way we have it setup is we have an organization unit at the highest level, followed by a position, and then a user assigned to the position.
What we would like to do is anytime we want to change a user (add/remove from a position), we would like for it to NOT ask for a transport request, but anytime some tries to change a position or organization unit, it does...
I hear this may be possible... cna someone tell me how/if it is?

Answer 1

Hi,
I assume you can find a test environment where you can change table T77S0 Group TRSP Sem.abbr. CORR value to X that should stop transport request window popping up when saving data in PPOME.
Then to demonstrate how we can control  PPOME access using authorisations I would create a test user (SU01)  and test role (PFCG).
In PFCG assign tcodes PPOME, PPOSE and SU53 to the test role. Since you have tcode PPOSE assigned it will bring authorisation object PLOG with required display values (PLOG: 1000, 1001 | * | C, O, P, S, T, US | 01 | DISP, LISD | * ).
Then you need to change the maintenance PLOG value to limit access to create relationships between S and US and specifically relationships A008 and B008. Some background for PLOG object fields:
Infotype and object type concept in HR works like object model. Infotype 1000 holds the name of the object. There are numerous different object types but PPOME displays mainly Jobs (C), organisational units (O), positions (S), persons (P), tasks (T) and users (US).
Infotype 1001 hold the relationship information between objects. When you assign user to a position you actually create a relationship (intoype 1001) between objects S and US. Relationships have different codes to describe the relationsip. In infotype 1001 the code is a subtype of the relationship. You can see all available values per infotype from table T778U.
So our second PLOG object should have authorisation to create infotype 1001 for object type S with subtype A008 and since relationships need to be created both ways I also need authorisation to create infotype 1001 for object type US with subtype B008. (PLOG: 1001 | * | S, US | 01 | * | A008, B008). If you want to restrict more specifically who can create and delimit relationships you can use different function codes (INSE, CUTI etc).
Play around and eventually HR object type and infotype concept is very straight forward. It's so different to other modules of SAP that it may first look bit weird...
Cheers, s