Chapter 3 SPOCK – the Building Block of OM

7/26/2019 Chapter 3 SPOCK the Building Block of OM

1/34

Chapter 3. SPOCK the Building Block of OM

We will now learn how the Organizational Management(OM) submodule is configured to map thebusiness requirement in a SAP system. We will see how a functional structure is mapped into the system.In this chapter, we will coer the following topics!

"he basic concepts of #$

%reating an organi&ational structure

Integrating #$ with Personnel Administration

The concepts of Organization Management

"he building bloc's of #$ are SP#%. "hey are described as follows!

S! "his stands for Position(for eample, *+ $anager, $ar'eting irector, and so on)

P! "his stands for Person

O! "his stands for Organizational unit(also 'nown as Org unit- it represents the department ina company)

C! "his stands for o!(for eample, manager, director, and so on)

K! "his stands for Cost Center

"ote

ote that both and P are eternal ob/ect types. "he ob/ect type, %ost %enter, is maintained in the 0I1%#module, and the P ob/ect type, Person, is maintained in the PA submodule. When we say eternal, it is simply notcreated in the #$ submodule.

SAP has deliered multiple interfaces to design an organi&ational structure, and we will understand eachof them separately.

#lucidating an organizational structure

An organi&ational structure is a functional structure. It simply represents the departmental hierarchy in acompany. It identifies each 2ob, Position, its functions, and where it reports to within the organi&ation. "hefollowing table is an eample of an organi&ational structure!

Compan$ name%epartments&su!org units'

Su!ordinatedepartments Positions o!s

A3% Paper %ompany(+oot organi&ational unit)

Administration #ffice

Superisor #ffice %ler'

+eceptionist

irector

$anager

Analyst

Administrat

or

Superisor*uman +esources *+ irector

3enefits

Administrator

*iring

$anager

*iring Analyst

0inance Accounts A1P $anager


2/34

Compan$ name%epartments&su!org units'

Su!ordinatedepartments Positions o!s

Payable

Accounts

+eceiable

A1P %ler'

A1+ $anager

A1+ %ler'

$anufacturing Pulp

Paper

$aintenance

Plant

superisor

"echnician

shift 4 5 67

"echnician

shift 8 5 67

$aintenance

superisor

Basic relationships !et(een organizational o!)ects"he relationships in organi&ational management are mostly similar to a parent5child structure in two ways.A Position can belong to an organi&ational unit, and inersely, can be incorporated by an organi&ational

unit. In the following table, Aindicates the bottom5up approach, while Bindicates the top5down approach!

*elationship t$pe *elated o!)ect t$pe *elationship name

A002 #5# An organi&ational unit reports to another organi&ational unit

B002 #5# "his is the line superisor of an organi&ational unit

A003 S5# All the Positions that reports to an organi&ational unit

B003 #5S A Position belongs to an organi&ational unit

A007 %5S A 2ob describes a Position

B007 S5% A Position is described by a 2ob

A012 S5# "he chief Position manages an organi&ational unit

B012 #5S An organi&ational unit is managed by a chief Position

A011 "his is the %ost %enter assignment

A008 P5S "his is a Position5to5Person relationship

B008 S5P "his is a Person5to5Position relationship

It is important to note that %ost %enter is always one sided unli'e other ob/ect types that can hae

both Aand B. It can be mapped either to an #rg unit or to a Position, depending on the business

requirement.

Tip

Irrespectie of the interface we use to create the structure, the ob/ect types are stored in the HRP1000table,

and the relationship between the two ob/ect types is stored in HRP1001.

When we discuss relationships, it is important to 'now the concept of the ealuation path in SAP. "heealuation path lets us create a relationship between two ob/ect types. An ealuation path can also hae asequence of ob/ect relationships. "he ealuation path can be accessed by naigating

to SP*O9 Personnel Management9 Organizational Management9 Basic Settings9 %ata Model#nhancement9 Maintain #+aluation Paths or iaOOAW. "he BOSSONLY"5code, for eample, is a


3/34

standard ealuation path that can be used in a report that will fetch the #rg units that hae

the B012relationship and the holder of the Position.

Building an organizational structure

"he different methods of building an organi&ational structure are as follows!

#rgani&ation and Staffing

Simple $aintenance

:pert $ode

Creating an organizational structure (ithdifferent interfaces

"here are multiple interfaces proided by SAP to build a functional structure. We will loo' at each of themin detail.

Organization and Staffing

"he #rgani&ation and Staffing method of building organi&ational structure is deliered by SAP in ascenario where thecompany does not hae an *+ module, but the organi&ational structure is needed forthe purpose of other modules, for eample, wor'flow requirements. ;sing this method, the organi&ationob/ects can be moed using the drag5and5drop approach. Also, we can add some etra attributes to theorgani&ational ob/ects.

"o wor' in this module, you hae to naigate to S,P #as$ ,ccess9 OrganizationalManagement9 Organizational Plan9Organization and Staffing9 PPOC# - Create. "he followingscreenshot demonstrates the naigation path!

When you use the PPOC# - Create"5code, it prompts you to enter the start date and end date, as seen inthe followingscreenshot. It is recommended that you hae the start date as bac'dated as possible,

say 01011900, for instance.


4/34

The relationship !et(een an Org unit and Position

We can use the PPOME"5code to use this interface ia the S,P #as$ ,ccessscreen. We can right5clic'

on Organizational unit, select ,ssign, and clic' on ncorporates, as shown in the following screenshot!


5/34

We will see how a %ost %enter is mapped to an #rg unit. %lic' on the ,ccountingtab after you eecute

the PPOME"5code.


6/34

Simple Maintenance

"he Simple $aintenance method, an older method of maintaining an organi&ational structure, is used tobuild an organi&ational structure and assign %ost %enter in an easy way on one screen itself. "his methodis recommended to build an organi&ational structure manually, in a scenario where the company has fewemployees. In this method, you can iew the organi&ational structure without haing to naigate much todifferent screens.

"his method can be accessed ia S,P #as$ ,ccessby naigating to S,P Menu9 /uman*esources9 Organizational Management9 #0pert Mode9 Simple Maintenance9 PPOC1O2%

Create. "his is shown in the following screenshot!

Also, we can directly access this method ia the PPOC_OLD"5code, which is shown in the following

screenshot!


7/34

:nter the required fields in the Create Organizational nitwindow to create the #rg unit. We will be ableto enter the #rg unit=s name, the abbreiation, as well as the long tet. In the Create Organizationalnitwindow, the users will hae the following two options!

O+erall +ie(! In this iew, the options and features cater to the users of SAP 3usiness Wor'flow

/uman *esources +ie(! In this iew, the options and features cater to the users of *+

After this is done, clic' on the %reate button in the top5left corner of the window, as shown in the followingscreenshot!

After performing the preceding steps, SAP automatically assigns an >5digit identifier that is unique to the

ob/ect. "he letter Oidentifies the ob/ect as an organi&ational unit.

"he positions are created by clic'ing on Staff assignments, as shown in the following screenshot!

After this, clic' on Positions...and a screen pops up wherein the required fields and alidity periods areentered (it=s recommend that you hae them bac'dated). SAP assigns a unique >5digit identifier to each


8/34

Position. "he letter Sidentifies the ob/ect as a Position. "he following screenshot shows a demonstration

of the preceding steps!

In the Create Positionswindow, we will enter the abbreiation and the long tet that identifies the

Position, the Sob/ect. "he following screenshot shows a demonstration of the preceding steps!

After performing the preceding steps, the /obs are created by clic'ing on Create )o!s- they are thenmapped to positions. We need to enter the abbreiation and its long tet and then clic' on the Sae button.

After clic'ing on the Create )o!sbutton, the Create o!swindow opens up, which is shown in thefollowing screenshot!


9/34

We can map the %ost %enter to the #rg units or Positions by naigating to 4oto9 ,ccount,ssignmentand then clic'ing on the Master cost center5tab, as shown in the following twoscreenshots!

After clic'ing on the Master cost center5tab, choose the appropriate %ost %enter and then clic' on theSae icon.

When we clic' on the ,ccount ,ssignmenttab, it will allow us to choose the releant %ost %enter thatneeds to be mapped to that #rg unit. "his is demonstrated in the following screenshot!


10/34

Creating a Cost Center

"he %ost %enter is an eternal ob/ect- it is created by a 0inance (0I) consultant and seres as anintegration point between *%$50I modules. "he %ost %enter is essentially used for epense classificationto 'now the brea'up of costs according to ?eneral @edger (?1@).

"hough %ost %enter belongs to the 0I module, it is useful to 'now the naigation path. "o access the %ost%enter, naigate toS,P #as$ ,ccess9 S,P Menu9 ,ccounting9 Controlling9 Cost centeraccounting9 Master %ata9 Cost Center9ndi+idual Processing9 KS67 - Create', as shown in thefollowing screenshot!

"he following screenshot shows the Create Cost Centerwindow that allows you to enter the %ost %entername and the alidity period!


11/34

Tip

"he alidity period is important when assigning it to an employee. "he start date of the %ost istribution

infotype0027must not be before the start date of the %ost %enter, or else, the system will throw an error.

The #0pert Mode

"he net interface that we will learn to use is PP67 - 4eneral. ;sing it, we can create any of the ob/ect

types such as O, S, C, and K. ;sing this method, we can maintain any type of attribute to any of the

organi&ational ob/ects. If any organi&ational structure needs to be built using uploaded programs,especially for large companies, the uploaded programs can use the epert method of building anorgani&ational structure.

"he :pert $ode can be accessed by naigating toS,P #as$ ,ccess9 S,P Menu9 OrganizationalManagement9#0pert Mode9 PP67 - 4eneral, as shown in the following screenshot!

Creating an organizational unit o!)ect in the #0pert Mode

"he ob/ect type and its relationships are created using the :pert $ode interface. "his interface isconenient to wor' with if we are familiar with the ob/ect types and the relationships between them. It is


12/34

normally used by functional consultants. "he following screenshot shows a demonstration of the processof ob/ect creation!

Select O!)ectand clic' on the %reate infotype button (or press F5). ?ie an ob/ect abbreiation as well asan ob/ect name for the #rg unit that we are creating. "his is demonstrated in the following screenshot!

Creating a position o!)ect in the #0pert Mode

We will now try to understand how a Position ob/ect is created. 0ollow the steps mentioned in thepreceding section aboutcreating an organi&ational unit. Instead of selecting Organizational unitas O!)ectT$pe, select Position. "he demonstration is shown in the following screenshot!


13/34

As shown in the following screenshot, enter all the fields /ust as it was done when creating anorgani&ational unit!

Creating a o! o!)ect in the #0pert Mode


14/34

In the Maintain o!)ectwindow, the different statuses that we will find are as follows!

,cti+e

Planned

Su!mitted

,ppro+ed

*e)ected

"he statuses are useful if we want an approal5type mechanism of wor'flow based on different statuses. Ingeneral, all #$ ob/ects are created in the ,cti+estatus.

When we clic' on Create o!)ect, the Create O!)ectwindow allows you to enter the ob/ect description andname, as shown in the following screenshot!


15/34

Tip

"he ob/ect abbreiation is, by standard, 48 characters in length, and the ob/ect name is 6 characters in length.We can find the length of each field by pressing F1from the field and clic'ing on the technical information.ouble clic' on table name in field data.

The concept of "um!er *anges

It=s important to 'now where the ob/ect Is are actually generated from. :ach ob/ect has a unique numberthat=s associated with it.

"o chec' what number is assigned to the different subgroups, naigate to SP*O9 PersonnelManagement9Organizational Management9 Basic Settings9 Maintain "um!er *anges9 Maintain"um!er *anges. "he following screenshot shows the Change 8ie( 9"um!er ,ssignment9:O+er+ie(window!


16/34

We can also access the preceding window ia the OONR"5code. After clic'ing on the "um!er range

maintenancetab in the preceding screenshot, the *ange Maintenancewindow appears, as shown in thefollowing screenshot!

When we can clic' on the nter+alstab (the pencil icon depicts that we can change interals), shown inthe preceding screenshot, the nter+al Maintenancewindow opens up, as shown in the followingscreenshot!


17/34

Scenarios (here (e use e0ternal num!er assignment

@et=s say that the company has ob/ect 'eys (numbers) already defined in an eisting system and would li'ethe same numbers to be brought oer to SAP too.

%onsider the number range is $$$$. "he first two $$represent the plan +ersionand the net two $

$represent the ob/ect type. 0or eample, 01Orefers to the number range for organi&ational units. o

changes may be needed in this table.

We can also access the "um!er *ange O!)ect Maintenancewindow ia the SNRO"5code. In thefollowing screenshot,RP_PLANis umber +anges for Personnel Planning!

%lic' on the *angesbutton in the following screenshot (or press F7). It leads to the +ange $aintenancewindow for Personnel Planning!

After performing the preceding step, the subgroup for Personnel Planning is displayed. In the following

screenshot, RP_Planis the ob/ect that we choose for #rgani&ation $anagement number ranges, 01is

the Plan ersion, and Odenotes the ob/ect type!


18/34

The Plan 8ersion

"he Plan Bersion lets us simulate multiple ersions in parallel. It allows us to manage different scenarios inthe #$. We can hae a number of plan ersions, but only one can be actie and current.

Plan ersions can be configured by naigating to SP*O9 Personnel Management9 4lo!al Settings inPersonnel Management9 Plan 8ersion Management9 Maintain Plan 8ersion. "he following screenshot

shows the Change 8ie( 9Plan 8ersions9: O+er+ie(window!

We hae to set the plan ersion by mapping the plan ersion I into the T77S0table.

Plan ersions can be actiated by naigating to SP*O9 Personnel Management9 4lo!al Settings inPersonnel Management9 Plan 8ersion Management9 Set acti+e Plan 8ersion. "he followingscreenshot shows the Change 8ie( 9Set ,cti+e Plan 8ersion9: O+er+ie(window!

"o actiate the plan ersion, we use the PSO6 Set Plan 8ersionoption, which can be found bynaigating toOrganizational Management9 Settings!


19/34

We can actiate the Plan Bersion directly ia the PCO0"5code, as shown in the following screenshot!

After performing the preceding step, a window will open up as'ing you to gie the Plan 8ersion. Afterselecting your Plan 8ersion, clic' on the %ontinue button, as shown in the following screenshot!

@et=s say we want to maintain the Plan Bersion. We can do this by accessing the configurable tables ia a

particular node or directly ia table maintenance. We hae to eecute the SM301SM31"5code and then

enter the table name, as shown in the following screenshot!

%lic'ing on the Maintainbutton will ta'e us to a configurable table, as shown in the following screenshot!


20/34

We can also go directly to the node by clic'ing on Customizing. "his is shown in the following screenshot!

#nce we clic' on the Customizingbutton, the following screen appears- clic' on Continue (;oSpecif$ing Pro)ect!

After clic'ing on Continue (;o Specif$ing Pro)ect, the M4 acti+ities o+er+ie( (indo(appears- clic'on 4lo!al Settings in Personnel Management!


21/34

After clic'ing on 4lo!al Settings in Personnel Management, clic' on the %ontinue button, as shown inthe following screenshot!

After clic'ing on the %ontinue button, we will see the Maintain Plan 8ersionsnode, as shown in thefollowing screenshot!

After clic'ing on the Maintain Plan 8ersionsnode, the Plan 8ersionsscreen will appear, as shown in thefollowing screenshot!

In the preceding screenshot, you=ll find the Print icon- clic' on it or press CtrlC P. "he following screenshotappears!


22/34

Creating an organizational structure using the #0pert Mode

We will now see how the organi&ational structure is created ia #0pert Modeby naigating to S,P #as$,ccess9 /uman *esources9 Organizational Management9 #0pert Mode9 PO76 Organizationalnit. "he following screenshot shows how this is done!

We can perform the preceding steps directly ia the PO10"5code.


23/34

It=s 'nown as D:pert $odeD simply because you must hae a good understanding of the ob/ect types andrelationships to build the structure using this interface. "he following screenshot shows the status of thestructure!

As seen in the preceding screenshot, we will see the status indicating that it starts the application to buildthe organi&ational unit. "he following screenshot shows how an ob/ect is created!

"o create positions, we naigate to S,P #as$ ,ccess9 /uman *esources9 OrganizationalManagement9 #0pert Mode9 PO73 - Positions. "his is demonstrated in the following screenshot!


24/34

We can perform the preceding steps directly ia the PO13"5code. "he following screenshot shows

the Maintain Positionwindow that appears after creating a Position!

"o create an ob/ect, we can choose the ob/ect and clic' on the %reate infotype (or press F5) and thefollowing window appears. "hen, clic' on the Sae!


25/34

"o create 2obs, we naigate to S,P #as$ ,ccess9 /uman *esources9 OrganizationalManagement9 #0pert Mode9PO63 - o!s, as shown in the following screenshot!

We can perform the preceding steps directly ia the PO03"5code. "he following window appears after

creating an ob/ect!


26/34

%hoose an ob/ect, clic' on the %reate infotype button seen in the preceding screenshot, then enter therequired fields in the following Create O!)ectwindow, and clic' on the Sae button!

Configuring the ta!le

0or the table configuration steps, the %ata Bro(serscreen needs to be used. "hen, enter the table name(for eample,hrp1000), as seen in the following screenshot!


27/34

#nce we enter the table name, the respectie table comes up, as seen in the following screenshot!

"he relationship between ob/ects is always two5sided such as A13, where A is the bottom5up approach and3 is the top5down approach. "he relationship with %ost %enter is always one side- it is represented

by A011.

"he relationship between ob/ect types is maintained in the HRP1001table. "his can be seen in the

following screenshot!

"he permitted relationships are stored in the T777Etable. "he OOVK"5code gies us the completed iew

of the +elationship between #b/ects. We can chec' using the SM30or SM31"5code, as seen in the

following screenshot!

;sing the SM30or SM31"5code, the ,llo(ed *elationshipswindow appears as shown in the following

screenshot!


28/34

ntegrating Organization Management (ith

Personnel ,dministration"he dataflow between the #rgani&ational $anagement and Personnel Administration submodules iscontrolled ia a system table.

ntegration s(itches

A system table can be accessed ia multiple ways, directly ia SP*O, "5code, or ia table maintenance.We will eplore all the methods in detail.

0irst, we will access a system table by naigating to SP*O9 Personnel Management9 OrganizationalManagement9ntegration9 ntegration (ith Personnel ,dministration9 Set up ntegration (ith

Personnel ,dministration. "he naigation path is shown in the following screenshot!

Secondly, we will access the system table ia the SM301SM31table maintenance "5code. "he following

screenshot appears after eecuting the "5code!


29/34

0inally, we will access the system table ia the OOPS"5code, as shown in the following screenshot!

After eecuting the OOPS"5code, the *+ $aster ata Integration window in the following screenshot

appears!


30/34

In the preceding screenshot, E denotes that data transfer from #$ and PA is actie. "he changes made inthe PA side of the world can be transferred to the #$ side using ata "ransfer reports that we will see inthe following section.

"he PLOGItable actually holds the ob/ect types and ob/ect Is that can be accessed ia the SE16table,

which is the %ata Bro(serwindow!

In the %ata Bro(serwindow, clic' on the "able %ontents button. We can gie the Plan 8ersion, O!)ectT$pe, and clic' on the :ecute button as shown in the following screenshot!

"he following screenshot shows the net window that shows the selected entries!

%ata Transfer Tools

"here are standard data transfer reports proided by SAP- these reports facilitate the transfer of ob/ectsbetween the #$ and PA submodules. "hey help the PA and #$ submodules to be in sync after they are


31/34

eecuted. "he reports can be accessed ia the SE38or SA38"5code, which opens the ,B,P

#ditorwindow wherein you can enter the Program"5code as shown in the following screenshot!

*/"T# *eports

"he RHINTE00, RHINTE10, RHINTE20, and RHINTE30tools facilitate data transfer from #$ to PA

and ice ersa.

@et=s eplore RHINTE00with a scenario. Say, we hae uploaded $aster in the Personnel Administration

side, and we see the #rg data in the 0001infotype. *oweer, we don=t find the Position and Person

mapping in the #$ side. In this case, we will ma'e use of RHINTE00, which opens the following windowafter it is eecuted.


32/34

After selecting the Personnel "um!er, the *eport-Specific Settingswindow appears as follows!

We will unflag the Testrun and eecute RHINTE00. "hen, we will eecute the SM37"5code to chec' the

scheduled 2ob as shown in the following screenshot!


33/34

#nce we process the 2ob, we will be able to eecute the "5code. "he 2ob will be listed with the name ofthe 2ob and the user I.

The purpose of the OM tool

"he */"T#C/#CKtool is a ery useful tool to use to chec' inconsistencies in integration. "he missingob/ect type and its relationship, if any, are highlighted, and it allows the consultant to chec' theconfiguration settings.


34/34

All the reports hae the standard documentation maintained to eplain the report purpose. We can seethem by clic'ing on the %ocumentationchec'bo and then on the %ispla$button.

Summar$

In this chapter, we hae coered all the interfaces proided by SAP to design and deelop the

organi&ational structure. We hae learned arious "5codes and table names to configure the #$submodule. We hae also coered the data5transfer tools proided that sere as an integration pointbetween the #$ and PA submodules.

In the net chapter, we will closely loo' at configuring the Personnel Administrationsubmodule and eplorethe standard functionalities proided by SAP.

Chapter 3 SPOCK – the Building Block of OM

Documents