GRC
HR
SCM
CRM
BI


Blog

 

The importance of table T77S0 in SAP HCM module (Part I)

by Rinky Karthik

February 24, 2012

This is Rinky Karthik and today I am going to discuss about the systems table T77S0. The T77S0 table is SAP’s hidden treasure. Strangely you will not find much documentation on any of SAP’s help site or class regarding the details of this table and the role it plays on top of configuration. More interestingly the F1 help feature that would provide with a meaningful definition on any field in SAP renders no value on most of T77S0 switches. I learned the importance of the T77S0 table the hard way. 11 years back when I started my career in SAP HCM field (there weren’t much information in the 'World Wide Web and social media was still in its preschool stage), I was literally awake for couple of nights trying to make the “Account Assignment values Inheritance by Position” work. I stumbled upon the T77S0 table then and it was a surprise revelation! In last few years I have come across many implementations where custom ABAP coding or custom user exits have been done to achieve something that a simple switch in T77S0 could do. Its sheer ignorance and that’s why I was tempted to write this piece of article today to help my fellow SAP HCM consultants to discover the T77S0 Pandora’s box.

 

It’s a big list and I will focus on the main PA/OM Groups and Switches in this article. Subsequently in my next article I will focus on Talent management series and the PLOGI switches.

 

PPINT Group

 

Group

Sem. Abbr.

Value

Description

PPINT

BTRTL

 

Default value for personnel subarea

PPINT

PERSA

 

Default value for personnel area

PPINT

PPINT

 

Default value for controlling area

 

PPINT- BTRTL/PERSA/PPINT: Ideally you would configure/update IT1008 Account assignment feature to default these values during a hire action or feature ABKRS. You may be surprised to know that , in this value dropdown you can select the Personnel Subarea, Personnel Area and Controlling Area for each of the Sem. Abbr. to default these values each time user performs any Action.

 

 

PPOM Group

 

Group

Sem. Abbr.

Value

Description

PPOM

CCODE

         

Maintain Cost Distribution (IT1018) Using CompCode

PPOM

EVENT

         

Object processing with actions ('X'=active)

PPOM

EXTCK

X

Switch error message delimit/delete object

PPOM

INHIC

X

'X': PPOM: Obligatory Inheritance of Company Code

PPOM

INHIH

X

'X': PPOM: Obligatory Inheritance of Contr. Area

PPOM

INHS

X

Inheritance of acc. ass. features by positions

PPOM

LEPER

         

Manager info: ' ' = key d ate, 'X' = period

PPOM

NOREF

         

Do not update object manager

PPOM

REFSH

         

Update Subtree According to the Memory

 

 

 

CCODE:

 In IT1018 (Cost Distribution) for Object type O – Org Unit, cost centers are maintained as standard by entering the cost center and corresponding controlling area. However there are limitations if cost accounting is activated for multiple company codes. If this is the case, the system only allows data to be posted to the cost center's company code. You cannot post data to any company code for the controlling area.

 

  Switch PPOM CCODE allows you to change the standard behavior:

 

  o   If the switch is set (PPOM CCODE = X), in the case of cost accounting for multiple company codes  you can enter any company code (that belongs to the cost center's controlling area).

 

  o   If the switch is not set (PPOM CCODE 0 ' '), the standard behavior  applies.

 

EVENT

 

In PPOME if you are moving an employee between two positions if this switch is active ( X = Active), you will get a pop up box to select the PA40 actions and perform via the action.

 

EXTCK

 

This switch is used to determine when delimiting or deleting an Organization Unit or Position, if :

 

  • The system should generate an error message that subordinate objects must first be moved, deleted or delimited. For this option, enter the value 'X'.

 

  • Direct modification of the assignment of subordinate objects is possible. For this option, enter the value ' '.

 

INHIC

 

This is one of the Key switches under OM along with INHIH and INHS. This defines:

 

  • If ‘X’ is selected, Obligatory or mandatory inheritance of Company Code is active and the positions will inherit t he Company code from the Org Unit.
  • If ‘  ‘ is selected, the inheritance is not active and a position can be assigned to different company codes. If your organization uses only one Company Code for all positions you may select ‘X’ otherwise you select blank.

 

INHIH

 

Obligatory inheritance of Controlling Area

 

 

  • If ‘X’ is selected, Obligatory or mandatory inheritance of Controlling Area is active and the positions will inherit the Ctr. area from the Org Unit.
  • If ‘  ‘ is selected , the inheritance is not active and a position can be assigned to different controlling areas. If your organization uses only one Controlling area for all positions  you may select ‘X’ otherwise you select blank.

INHS

 

INHS is another very important switch in OM.  This switch defines if the account assignment features such as (Company Code/Controlling area/Business Area) are passed on from Org Units to Positions.

 

You can input ‘X’ to activate this inheritance. It’s advisable to activate this inheritance in matrix org structures.

 

LEPER

 

In simple maintenance view you can define if:

 

  • All chiefs in an organizational unit should be displayed. For this option, enter the value 'X'.

 

  • Only t he current (key date) chief or the next future chief of an organizational unit should be displayed. For this option, enter the value ' '.

 

NOREF

 

You can use the OM_OBJM_NO_LAST_SEAR user parameter to switch off the setup of the "last search" in the object manager for specific users.

 

By selecting ‘X’ you can switch off the automatic refresh function for the Object Manager.

 

REFSH

 

This is mainly used for the Organization Management portion of CRM and not HCM. By ‘X’ here the Org structure is refreshed.

 

 

Hope this information was useful to you. See you next time.

Did you find this blog helpful? Get access to the latest updates and resources from SAPinsider with a free subscription.

Get the SAPinsider subscription now »»

An email has been sent to:






More from SAPinsider



COMMENTS

Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!


SAPinsider
FAQ