Creation of Custom OM (Organizational Management) Infotype

CREATION OF CUSTOM OM (ORGANIZATIONAL MANAGEMENT) INFOTYPE

Summary
This document explains how to create the custom OM infotype (9018) to store
the cost distribution details of the employee. A Webdynpro application is
created to provide the manager and employee to update the cost objects at
their position level in the infotype.
In the standard cost distribution infotype 1018 we cannot save
the cost objects details at the operation/activity level. To maintain the cost
object details for an employee at the operation/activity level and fulfill the
business requirement we create a custom organizational infotype (9018).

Table of Contents
2

Summary...................................................................................2
Table of Contents..............................................................3
Background................................................................................4
Procedure..................................................................................5
Code Sample..............................................................................12
Output Result.............................................................................13
Conclusion.................................................................................15

Background
In the standard SAP we can store the cost distribution details for an employee
in the infotype 1018, but in the infotype we can maintain the details at the
3

order level only. As per the requirement we need to add the activity/operation,
percentage and activity description fields in the infotype 1018. In the standard
infotype (1018) it is not possible to add these fields in the table control, so we
will create the custom OM infotype 9018 with additional fields like
activity/operation, activity description and the percentage.

OM infotypes are used when defining the organizational plans. The user
can create many organizational plan versions, but only one version is
Active.

The organizational plan is a display of the organizational structure that

shows the relationships between different objects such as organizational
units, position and persons.

The most frequently used organizational objects are organizational unit,

position, job (general description of the position) and person
(representing the employee in PA).The organizational hierarchy is
created by the relationships between objects (Relationship infotype
1001).

There are many similarities in developing the OM and PA infotypes.

However in case of OM, we use a different transaction to support it
PPCI (Personnel Planning Infotype copier).

Procedure
Go to the transaction code SE11 and create the structure HRI9018 with the
necessary fields which is required like activity/operation, percentage and the
activity description.
4

Figure 1 Transaction SE11, Create the structure HRI9018

Custom Fields

Create the structure P9018 which is the copy of Structure P1018 with the
appended structure HRI9018.

Run the transaction PPCI (Personnel Planning Infotype Copier), Enter the new
Infotype 9018 (you can use any value between 9000-9999), define the infotype
name and click on create.

Figure 2 Transaction PPCI, Create the Infotype 9018 (Default accounting)

Select Field Infotype and click on create (In the Infotype Block).The system
generates (among others) the transparent table HRP9018, Index HRP9018~1,
structure P9018, Module pool MP901800, Screen 1000, 2000, 3000 and some
table entries.
We can choose between two infotype categories: Field infotype and table
infotype. Field infotype are used when fields are filled only once within the
infotype itself. Table infotype let you store data in a tabular structure in one
infotype record.
Run the transaction PPCI, enter 9018 for the new infotype (you can use any
value between 9000-9999), define the infotype name and click on create.
Figure 3 Transaction PPCI, Infotype 9018 (Default accounting)

Infotype Created

Go to the transaction code SM30, to maintain the infotype attributes. The most
important thing to define is the assignment of the new infotype to the standard
object type position. Input the table name T777I, and click on maintain button.

Figure 4 Transaction SM30, Describe the Attributes of the Infotype 9018

(Default accounting).

Select the infotype 9018 in the list and double click on the infotype per object
type in the left navigation panel. Click on new entries and define the records.

10

Figure 5 Transaction SM30, Defining the Object type for the Infotype 9018
(Default accounting).

NOTE: The NO maintenance checkbox in the infotypes per object type view
does not affect the customized settings.This only signifies that you cannot
maintain the infotype using the standard transaction.
Now return to the maintenance view to define the time constraint for the new
infotype. Choose new infotype and double click on the time constraint in the
left hand navigation panel. Click on new entries.
Figure 6 Transaction SM30, Defining the Time constraints for the Infotype
9018 (Default accounting).

11

12

CODE SAMPLE:
Create a subscreen 100 which contains all the necessary fields like Work order,
activity/operation, activity/operation description and percentage.

Figure 7 Table control screen containing only those fields which are
required as per requirement:

13

OUTPUT RESULT:
Now we are able to create the default accounting detail for an employee at
activity/operation level.
Go to the transaction code PP01 and create the record for an employee at its
position level.

Figure 8 Transaction code PP01, to create the cost object on Employee

Position.

14

Select the Infotype 9018and press on create button to create the cost object
details on employee position.
Figure 9 Transaction code PP01, Default accounting (Infotype 9018) screen
to create the records:

15

Enter the valid order number and choose the activity/operation field value
from the F4 help with respect to the order number.

The cost object details get stored in the database tables HRP9018 and
HRT9018.

16

Get the TABNR field value from the HRT9018 table and pass the value in the
HRT9018 table:
HRT9018 table store the cost object details:

CONCLUSION:

Because of limitation of not able to enhance standard

infotype 1018 to include field Operation/Activity, a custom infotype 9018 has

to be developed, which will include fields Work Order, Operation/Activity and
Percentage. Now we are able to create the default cost object on employee
position.

17