Sie sind auf Seite 1von 40

OM CONFIGURATION:

In OM you have to configure the following:

1. SET UP NUMBER ASSIGNMENT FOR ALL PLAN VERSIONS:-

In this step, you specify whether number assignment is plan version- specific or plan version-independent, in other words, valid for all plan versions. This decision is important since it affects the kind of subgroups (number intervals) you may use.

If you decide not to work with number assignment valid for all plan versions, you must create individual number intervals per plan version (and possibly also per object type). If you decide to use plan version- independent number assignment, you create number intervals that are valid for all plan versions. In this case, there is no danger of parallel number intervals occurring i.e. the same number interval for one object in one plan version and for a different object in another plan version.

Standard settings:-

In the standard sap r/3 system, number assignment is not valid for all plan versions.

Recommendation:-

If you plan to transfer data from plan version to plan version, we strongly recommend that you use number assignment valid for all plan versions to avoid objects being overwritten by others with different meanings.

Activities:-

1. Enter 'x' in the field value abbr. To activate number assignment for all plan versions.

Leave the field value abbr. Blank to deactivate this function.

2. Save your entries.

TCODE: - OONC

PATH:-

Img personnel managementorganizational management basic settings maintain number ranges set up number assignment for all plan versions.

2. MAINTAIN NUMBER RANGES:-

In this step, you specify the number ranges for your pd objects and the type of number assignment. You must assign a unique number to every object.

You have the following options:

Internal number assignment:-

If you want the sap system to assign the numbers, enter "in" in the 'nr' field. The number ranges are then indicated by the letters "in".

External number assignment:-

If you want the user to assign the numbers, enter "ex" in the 'nr' field. The number ranges are then indicated by the letters "ex".

You can define your own number ranges (subgroups) for individual plan versions (that are not valid for all plan versions) and object types. The names of the subgroups are set up so that the first characters specify the plan version and the last two specify the object type in detail. The structure of the subgroups depends on whether you are using number assignment valid for all plan versions or not.

Example:-

Number assignment for plan version 10 / object type s: subgroup 10s

Standard settings:

The entry $$$$ in the field subgroup represents all number ranges not listed explicitly. You should not delete this entry.

Recommendation:

Since the matchcode function is available for the selection of objects, it is generally not necessary to assign "mnemonic" numbers.

Sap recommends that you use internal number assignment.

Activities:-

1. Enter the subgroup for which you wish to set up number assignment.

The following entries are allowed (when number assignment is not valid for all plan versions).

$$$$ (plan version and object type are generic)

Pv$$ (plan version, object type is generic)

Pvot (plan version, object type)

The following entry is not allowed:

$$ot (plan version generic, object type)

The following entries are allowed (when number assignment is valid for all plan versions):

$$$$ (plan version and object type are generic)

$$ot (plan version generic, object type)

The following entries are not allowed:

Pvot (plan version, object type)

Pv$$ (plan version, object type is generic)

Save your entries. The systems automatically creates an external number range (ex) and an internal number range (in).

2. Specify the subgroup on the following screen and choose "change intervals".

3. A new data screen appears on which you can maintain number range intervals. Choose

"create interval".

4. Enter the code for the number assignment (in or ex), the lower limit and the upper limit of

the interval in the dialog box which then appears.

In the case of external number assignment, mark the field "ext" also.

5. Choose "insert" and save your entries.

TCODE: - OONR

PATH:-

Img personnel managementorganizational management basic settings maintain number ranges maintain number ranges.

3. MAINTAIN OBJECT TYPE:-

In this step, you make the settings necessary for changing standard object types and creating new object types.

You can make the following settings:

You can define the relationship that should be proposed in the course of the authorization check. For more information on this, please refer to the section "structural authorization".

You can create or change external object types that are not administered in pd (e.g. Object type "employee" from hr master data management).

In this case, you must specify the interface program used to access these object types.

You can define an object type hierarchy for evaluations (reporting).

You can, if necessary, change the id of a standard object type ("o" for organizational unit, "t" for task).

Example:

If you are reporting on positions, the report will include objects whose object type is the same as the value assigned to the semantic abbreviation "plste" in the parameter group "otype". (in this case 's').

You can maintain the controlling entries for object type-related transactions.

The information regarding which object type is to be edited in the transaction is stored for each object type-related transaction (po** = menu-guided infotype maintenance).

Note:

You can create two-digit object types in the range "01" to "99".

Activities:

1. Define the mandatory relationship, if required.

2. Create external object types and specify the program that accesses these object types.

3. Define an object type hierarchy for the evaluation (reporting).

4. Change the id of a standard object type only if it is absolutely necessary, observing the name

ranges reserved for customer-specific entries.

5. If you have created new object types, change the value of the semantic abbreviation of each

object type in the parameter group otype, where necessary.

Similarly, if necessary, change the value of the semantic abbreviation for each object type- related transaction in the parameter group tcode

TCODE: - OOOT

PATH:-

Img personnel management organizational management basic settings data model enhancement maintain object type.

4. MAINTAIN INFO TYPES:-

In this step, you can change the attributes of an infotype.

An infotype is a collection of logical or business-related characteristics of an object.

You can make the following settings:

You can change the infotype names.

You can assign infotypes to standard object types or to customer- specific object types.

You can define another time constraint for an infotype.

In the case of infotypes with underlying subtypes, the time constraint is defined per subtype. If you wish to create your own subtypes, you have to carry out the step "maintain subtypes" and define a time constraint per subtype.

Example:

The address elements (e.g. Postal code, city, street, house number etc.) Make up the address infotype, which could be appended to the object organizational unit, for example.

Note:-

You can create four-digit infotypes in the range from "9000" to "9999".

Requirements:-

You should already have edited the step "maintain object types" before doing so.

Recommendation:-

Customer-specific infotypes should be further subdivided for the individual hr modules.

Example of possible sub-divisions:

Infotype

Area

Customer master data

"9000" to "9099"

Customer plan data

"9100" to "9199"

Customer time data

"9200" to "9299"

Activities:-

1. Change the name of the infotype, if required.

2. Check and, if necessary, change the time constraint of the infotypes or subtypes.

3. Assign the infotypes to object types.

Note:

The 'cannot be maintained' field in the view "infotypes per object type" does not affect the customizing settings. This field (if it is set) merely specifies that you cannot maintain the infotype in question using the standard transactions.

TCODE: - OOIT

PATH:-

Img personnel management organizational management basic settings data model enhancement infotype maintenance maintain info types.

5. MAINTAIN SUB INFO TYPES:-

In this step, you maintain the settings necessary for creating subtypes for infotypes.

You can create new subtypes for standard infotypes or for customer- specific infotypes. In either case, you have to assign a time constraint to both subtypes and infotypes.

Example:-

Infotype

Subtype

1001

relationships

A003 belongs to

1001

relationships

B003 incorporates

1042

schedule model

0001 main schedule pattern

1042

schedule model

0002 alternative schedule pattern

1042

schedule model

Temp temporary schedule

The schedule model infotype (1042) is subdivided into the subtypes 0001 "main schedule pattern", 0002 "alternative schedule pattern" and temp "temporary schedule".

Note:-

You can create four-digit subtypes in the range from "9000" to "9999".

Recommendation:-

Relationships are special subtypes of the infotype "relationship". This function is dealt with separately since there are a number of special points to note when setting up these subtypes. For this reason, you should create relationships in the step "maintain relationships".

Activities:-

1. Create further subtypes for infotypes if required.

2. Append a time constraint to each subtype.

Further notes:-

For further information, please refer to step maintain infotypes".

TCODE: - OOSU

PATH:-

Img personnel management organizational management basic settings data model enhancement infotype maintenance maintain sub info types.

6. MAINTAIN USER-DEFINED SETTINGS FOR INFOTYPE:-

In this step, you make the following customer-specific settings for infotypes:

You enter the screen number of the single infotype screen if you are not using the standard screen 2000.

You enter the screen number of the list screen for infotypes if you are not using the standard screen 3000.

You specify whether text can be created for an infotype.

You specify whether the infotype can be maintained in a basic transaction.

You specify how blank lines in language-specific infotypes are to be processed.

You specify whether entries in table infotypes are to be sorted.

Activities:-

1. Choose new entries.

2. Enter the number of the infotype you want to configure.

3. Enter the alternative screen number.

4. Make any other settings required.

5. Save your entries.

TCODE: - ?

PATH:-

Img personnel management organizational management basic settings data model enhancement infotype maintenance maintain user-defined settings for infotype

7. MAINTAIN COUNTRY SPECIFIC INFO TYPES:-

In this activity, you specify that an infotype is only relevant for a particular country or countries, in other words, a country-specific infoype. This determines whether an infotype is displayed via country settings in basic transactions.

Example

You flag three infotypes as country-specific for france. When you choose france under 'country settings' in a personnel planning transaction, all international infotypes and the three country- specific infotypes are displayed.

Standard settings

The standard system contains no country-specific assignment for infotypes.

Activities:-

1. Choose new entries.

2. Enter an infotype.

3. Select the country indicator of the country you want to assign the infotype to.

4. Save your entries.

TCODE: - ?

PATH:-

Img personnel management organizational management basic settings data model enhancement infotype maintenance maintain country specific info types.

8. MAINTAIN RELATIONSHIP MAINTENANCE:-

In this step, you make the settings that are required for creating relationships.

By creating relationships between objects, you can display all the structures that exist in personnel management.

Relationships are special subtypes of infotype 1001. Each relationship has two relationship types, indicated by a and b. For each relationship created (a or b), the corresponding inverse relationship is automatically set up.

You can make the following settings:

You can create new relationships.

You can control the response of the system (error messages, warnings, information) if the 100% mark is exceeded in the case of "weighted" relationships.

You can show or hide the weighting percentage of a relationship and, if required, define additional data for a relationship. You can specify, for example, in the view 'additional relationship info' whether the recursiveness check should be active for your own relationships or not.

Caution!

Apart from controlling the weighting, you should consult sap before making any other changes to this view.

You can define the object types that are allowed for each relationship and inverse relationship.

You can set up external relationships.

External relationships are relationships between external object types i.e. Object types that are not stored in the plog database in personnel development and planning. (see also the step "maintain object types").

You can enter a time constraint for each relationship.

You can change the "alias" name (semantic abbreviation) of a relationship.

Note: - you can create 3-character relationships in the range "aaa" to "zzz". You should only use letters for this!

Example:-

Relationship

Inverse relationship

A002 reports to

B002 is line supervisor of

A003 belongs to

B003 incorporates

A007 describes

B007 is described by

Requirements:-

Before you create a new relationship, it should already have been created as a subtype of infotype 1001 "relationships" in the step "maintain subtypes".

Activities:-

1. Create new relationships, if necessary.

2. Specify whether an error message, a warning or an information message should be issued

when a weighted relationship exceeds 100%.

3. Specify whether the weighting percentage of a relationship should be displayed or hidden in

the relationship infotype.

4. Deactivate the recursiveness check, if necessary.

5. Specify which relationships should be allowed for which object types.

6. If you have created external object types, you may have to create the required external

relationships.

7. Enter a time constraint for each relationship and inverse relationship.

8. Only change the relationship abbreviation ("alias" name) if it is absolutely necessary.

Note:-

The "cannot be maintained" field in the view "allowed relationships" does not have any effect on customizing settings. This field (if it is set) merely specifies that the relationship in question cannot be maintained using the standard transactions.

TCODE: - OOVK

PATH:-

Img personnel management organisational management basic settings data model enhancement relationship maintenance maintain relationships.

9. DEFINE TIME CONSTRAINT DEPENDING ON TARGET OBJECT TYPE:-

In this step, you define alternative time constraints for relationships depending on the target

object type.

Example:-

A

position in your enterprise can be described by only one job (target object type "c") but by

as

many tasks as required (target object type "t").

Requirements:-

You should have already carried out the step maintain relationships and entered the value "3" for the time constraint of the corresponding relationship.

Standard settings:-

The standard sap r/3 system contains a number of predefined time constraints that are target object type-dependent.

Recommendation:-

It is recommended that you use the time constraints supplied.

Activities:-

Define you own target object type-dependent time constraints if necessary.

Further notes:-

The assignment of additional conditions for this function may only be carried out by sap since it is equivalent to a program modification.

TCODE: - OOZR

PATH:-

Img personnel management organisational management basic settings data model enhancement relationship maintenance define time constraint depending on target object type.

10. MAINTAIN EVALUATION PATHS:-

In this step, you create the evaluation paths you require.

An evaluation path is an instruction to the system which determines which object types and relationship(s) are to be included in an evaluation of your organizational plan.

One or more relationships are then used as "navigation paths" for evaluating structural information in your organizational plan (relating to the organizational or reporting structures) or matrix organization. The sequence of the relationships included in the evaluation path is decisive in how the results of the evaluation are displayed.

Example:-

Evaluation path "staff assignments along organizational structure" (sbesx):

No. Object type a/b relationship priority type rel. Object skip

 

010

O

B 003

* S

020

S

A 008

* P

030

O

B 002

* O

For more information on priorities, see also: priority

First of all in this evaluation path, the positions assigned (s) to an organizational unit (o) are determined, then, the holder (p) assigned to each position is determined. As well as this, the next organizational unit down in the organizational structure is determined, the above procedure then takes place for this organizational unit. This procedure is repeated for all further subordinate organizational units.

In the "skip" field, you specify that a particular relationship is to be included in the evaluation path, but that the last object type in this relationship is not to be displayed.

So, if the skip field were selected in the first line of the above example, this would mean that the organizational units and persons would be displayed, but not the positions that the persons occupy.

Activities:-

1. Check the evaluation paths in the sap standard system.

2. Create your own evaluation paths. These must be alphanumeric and have a- maximum of

eight digits. They must begin with the letter "z".

Further notes:-

Each relationship is defined by its short name ("a002", for example) and the evaluation text as an evaluation path and cannot, therefore, be changed. You can change the evaluation text but not the short name of other evaluation paths.

Create new evaluation paths, if you have defined new objects and want to carry out evaluations for them in conjunction with object types that already exist. You also need new evaluation paths if you are modifying existing evaluation paths, by selecting a "skip" field, for example. Copy the evaluation path into the customer name space (beginning with "y" or "z") and enter an evaluation path.

TCODE: - OOAW

PATH:-

Img personnel management evaluation paths.

organisational

management basic

settingsmaintain

11.

MAINTAIN PERSONNEL ACTIONS:

In

this step, you make the system settings necessary for setting up a personnel action.

A

personnel action is a collection of several logically connected infotypes in the system which,

in

an exact sequence, are used for processing and are used for a particular system activity (see

"create organizational unit", for example).

Personnel actions are identified by a key.

You assign the following to each step of a personnel action:

A plan version

An object type

An infotype or subtype

A status

Default values for screen entry

You also control, which function codes are used by an infotype (within a personnel action).

In a transaction controlled by a personnel action (pq**), you must determine the object types for which the action is to be executed. For each transaction related to an object type and controlled by a personnel action, specify which default personnel action (pq**m) is to be processed by the corresponding transaction.

For each default personnel action within a transaction controlled by personnel actions, you can access a process description.

Example:-

Personnel action "create organizational unit":

Personnel action

Plan ver.

Objtype

Infotype

Subtype

Fcode

Varfield

O

**

O

1000

   

Inse

O

**

O

1002

0001

Inse

 

O

**

O

1003

   

Inse

O

**

O

1001

A011

Inse

K

The personnel action "create organizational unit" includes the following steps:

Creating the "object" infotype (1000)

Creating the "description" infotype (1002) with the "general description" subtype (0001)

Creating the "department/staff" infotype (1003)

Creating the "relationship" infotype (1001) with the "cost center assignment" subtype (a011) for object type "k" (cost center).

Activities:

1. Create the required personnel actions.

2. For each personnel action, determine the following:

Corresponding object type

Required infotypes and subtypes

Function code (insert, copy)

The plan versions for which the personnel action is to be valid

The planning status in which the objects are to be created.

Entering default values is optional.

3. Enter the object type that is to be processed as well as the key of the personnel action for the

transaction to be controlled by a personnel action.

Further notes:

Ensure that you arrange infotypes in a logical order when defining a personnel action. The "object" infotype must always be processed first and must have line number "001".

A personnel action may only be defined for one object type.

You can create three-digit personnel actions between "001" and "999".

TCODE: - OOMT

PATH:-

Img personnel management personnel actions.

organisational

management basic

settingsmaintain

12. ACTIVATE INHERITANCE OF ACCOUNT ASSIGNMENT FEATURES:-

In this step, you can determine that account assignment features (controlling area, company code and business area) of organizational units are to be inherited by subordinate positions.

Standard settings

Inheritance is deactivated as standard (value ' ').

Activities

If you want to activate inheritance, enter an 'x'.

TCODE: - OOCINH

PATH:-

Img personnel management organisational management basic settingsactivate inheritance of account assignment features.

13. SET UP TRANSPORT CONNECTION:-

In

wish to use to transport personnel planning objects from the customizing client.

There are three possible transport options:

Automatic transport connection:-

With the automatic transport connection, a dialog box always appears after you create, change, or delete objects asking you to assign the object to a transport request or to create a new request.

Transport via object lock (repair flag):-

If you decide to use the object lock option, there is no automatic query regarding a transport request. However, you can use the report rhmove50 (transport of objects using object lock) to transport any objects that were changed.

No automatic transport connection (automatic transport connection is deactivated):-

If you decide not to use the automatic transport connection, there is no automatic query regarding a transport request when you create, change or delete an object. This means that you have transport the changed objects yourself. You do so with the report rhmove30 (manual transport)

You have to enter the objects to be transported yourself, which means that you have to ensure that all changed objects have been transported.

Standard settings:-

In the standard sap r/3 system, the automatic transport connection is active - the value abbr. Field is blank.

Activities:-

1. Specify which type of transport connection you wish to use with one of the following entries in the value abbr. Field:

Entry: ' ' (blank) = automatic transport connection

Entry: 'x' = no automatic transport connection

Use the report rhmove30 (manual transport)in this case to transport all objects.

Entry:’t’ = transport via object lock (repair flag)

you

this

step,

you

specify

which

type

of

transport

connection

Use the report rhmove50 in this case to transport all objects.

2. Save your entries.

TCODE: - OOCR

PATH:-

Img personnel management organisational management transport set up transport connection.

14. MANUAL TRANSPORT:

In this activity, you execute report rhmove30 (manual transport connection). Use this report to transport or delete objects when you are not using the automatic transport connection.

Activities:-

Run report rhmove30 for the objects you want to change or delete.

For more detailed information on running this report, refer to the report documentation on manual transport connection.

TCODE: - OG00

PATH:-

Img personnel management organisational management transport manual transport

15. SETUP INTEGRATION WITH PERSONNEL ADMINISTRATION:-

In this step, you activate integration between organizational management and hr master data in

personnel administration. This guarantees data consistency between the two components.

Example

A person is to be transferred from the position "controlling administrator" to the position

"manager of controlling". As soon as this transfer has taken place in organizational management, the corresponding changes are made in the "organizational assignment" infotype

(0001) in personnel administration.

A person can also be transferred between positions in personnel administration using the

personnel action "organizational change". The relevant changes will then be made in organizational management.

Requirements

Using the entry "plogi plogi", you specify the active plan version that is to be the integrated plan version for organizational management, personnel development, personnel cost planning, shift planning and training and event management.

The entry has the function of a main switch: if this entry has the value ' ' (switch "off"), integration is switched off. If a plan version is determined using the switch, integration in this plan version is active for all persons who correspond to the feature "plogi" (see below).

The entry "plogi orga" must contain an 'x'. This activates integration between organizational management and personnel administration via infotype 0001 ("organizational assignment").

Activating integration has the following effects:

Changes to organizational management objects (organizational unit, job, position, cost center) relevant to integration are transferred to personnel administration

Changes to the organizational assignment of employees (infotype 0001) are transferred from personnel administration to organizational management.

Activating integration

The sequence in which you carry out preparations for activating integration depends on which one of the following is true of your enterprise:

You have personnel administration set up and want to install organizational management for the first time.

You have organizational management set up and want to install personnel administration for the first time.

You want to install both applications for the first time.

In all three cases, you must ensure that personnel administration (infotype 0001) and organizational management (organizational assignment of employees) contain consistent data.

If the master data regarding the organizational assignment of the person is available in infotype 0001 (organizational unit, job, position and cost center), you must start report rhinte00.

If organizational management data is available, start report rhinte10. This will create the relevant information in the personnel administration tables.

If the organizational assignment (position and organizational unit of a person) is also to be transferred from organizational management into infotype 0001 in personnel administration, you also have to start report rhinte30.

If you are installing both applications and integration is active, you can only maintain the organizational assignment (infotype 0001) of a person in personnel administration using an action. Alternatively, you can assign persons to positions in organizational management.

We recommend that you always make organizational changes using an action in personnel administration as by doing this, you will also be able to adjust information on working time and salary for this person.

You can build up one of the databases for the two components first without active integration and then proceed as described above.

In all three cases, report rhinte20 can correct any inconsistencies that may occur.

To activate integration, you must check or make the following settings in addition to those you have already made in the step "global settings in personnel management":

1. Basic settings

Integration switch for organizational assignment (t77s0: plogi orga)

Default position (plogi preli)

Update file pannnn (plogi prelu)

Department switch (ppabt ppabt)

Default value for personnel subarea (ppint btrtl)

Default value for personnel area (ppint persa)

Transfer short or long texts from organizational management to

Personnel administraiton (plogi textc, plogi texto, plogi texts)

2. Participating in integration

The feature "plogi" contains criteria with which you can determine the persons in your enterprise or personnel structure for whom integration should apply.

The criteria are:

Company code

Personnel subarea

Employee group

Employee subgroup

You can combine any of these criteria for integration. You can activate integration for all employeed or just for certain company codes, personnel subareas, employee groups, employee subgroups or for different combinations.

Note

If integration is active, it is possible to relate persons and positions (relationship b008). For this reason, it may be necessary to define relationship characteristics to control the validity of relationships that are created. The system would then send out a warning or error message if, for example, a position was to be occupied and the working time of the holder exceeded the planned working time or if a person is assigned to one or more positions for more than 100% of their working time.

Carry out the step maintain relationships".

Activities

Make the following settings in the recommended order:

1. Using the entry "plogi orga", determine whether integration between organizational

management and personnel administration is active. If you do not want integration to be active, enter ' ' (blank).

2. You should not change the entry "plogi preli". You can, however,change the name of a

position with this number (see value of semantic abbrevation for the entry "plogi preli") in customizing for personnel administration.

3. In the entry "plogi prelu", determine whether master data is to be updated online or by batch

input.

4. In the entry "ppabt ppabt", determine whether only organizational units indicated as infotype

1003 "department" for a position are to be read.

5. Determine the default value for the the personnel subarea in the entry "ppint btrtl".

6. Determine the default for the personnel area in the entry "ppint persa".

7. In the entry "plogi textc", determine whether the short texts rather than the long text for jobs

created in organizational management are to be transferred into personnel administration.

8. In the entry "plogi texto", determine whether the short texts rather than the long texts for

organizational units created in organizational management are to be transferred to personnel administration.

9. In the entry "plogi texts", determine whether the short texts, rather than the long texts for

positions created in organizational management are to be transferred into personnel administration.

10. In the feature "plogi", determine for which persons integration should be activated for based

on the criteria company code, personnel subarea, employee group and employee subgroup.

Note: in the standard system, the switch &plogi is set to "x" (all).

11. If you set the switch plogi evenb to 'x' setzen, you can make organizational changes that

include a change of company code.

12. According to the set up in your enterprisee (see activating integration), start one of the

reports in the step "tools for integration".

Further notes

For detailed specifications, refer to the documentation on the entries in the "semantic group" und "semantic abbreviation" fields.

You can display specific documentation on the feature in the transaction; you will find a general feature description under help -> extended help.

TCODE: - OOPS

PATH:-

Img personnel management organisational management integration with pa setup integration with pa.

16. TRANSFER DATA FROM PA:-

In this step, you can copy the objects and relationships set up in personnel administration into organizational management using the report rhinte00.

This program reads the objects of infotype 0001 "organizational assignment" which were created in personnel administration. On this basis, the following records are created in organizational management. As a prerequisite, you must have selected the "create objects" or "create objects" and "create relationships" parameters in report rhinte00.

For the cost center-related relationships, you must also enter the relevant object type in the "cost center related to" parameter.

Objects (infotype 1000):

Work center (object type a)

Job (object type c)

Organizational unit (object type o)

Position (object type s)

Relationships (infotype 1001):

S

to p (person is holder of position, b 008) or

A

to p (person is holder of work center, b 008)

C

to s (job describes position, a 007)

O

to s (organizational unit includes position, b 003)

O

to k (cost center assignment, a 011) or

S

to k (cost center assignment, a 011)

Once this program has been executed, a batch input session (btci) must be processed (providing the option for creation of a batch input session was selected). The session is processed automatically when the system is started or you can start it via system -> services -> batch input -> edit. The session is given the name of the user who logged on to the system.

This program uses the standard relationships listed in the maintain relationships step when creating relationships between the object types referred to.

The program outputs a batch input session or a list of the objects found for the session. In addition, a list of the personnel numbers which have no relationship to a position is output.

If the session runs without any errors, the status "fin" is displayed. Otherwise, the status "err" is displayed.

Activities

1. Start the program without creating a batch input session.

2. If personnel numbers were found that are not assigned to a position, correct these by

A) Deactivating the integration switch in the set up integration with personnel administration step (entry plogi orga).

B) correcting the data for the persons concerned.

Make sure that all persons are assigned to a position or to a work center.

3. Activate integration again (see 2.a).

4. Start the program rhinte00 again, this time with creation of a batch input session. This session

can be started automatically or manually.

Further notes

For more information, particularly on the entry parameters, see the online documentation for the report rhint00 via system -> services -> reporting and the menu entry goto -> documentation.

TCODE: - OOPH

PATH:-

Img personnel management organisational management integration integration with pa transfer data from pa.

17. PREPARE INTEGRATION WITH PA:-

In this step, you can transfer objects created in organizational management into personnel administration tables using report rhinte10.

In doing this, you fulfil the prerequisite for writing data from personnel administration tables to the "organizational assignment" infotype using report rhinte30.

The following object types are relevant for integration:

Organizational management

Personnel administration

 

Work center

(object type a)

Tables t528b, t528t

Job

(object type c)

Tables t513, t513s

Position

(object type s)

Tables t528b, t528t

Org.unit

(object type o)

Table t527x

Only objects that exist as status 1 (active) in the integration plan version are taken into account (see the entry "plogi plogi" in the set up integration with personnel administration step.

Data for the objects relevant for integration can be changed in infotype 0001 "organizational assignment" for personnel administration.

A program run can be executed for all object types.

Activities

1.

Start the report in test mode.

2.

Check the results.

3.

Start the report again without the "test" parameter so that you can make the required changes

to

the table.

TCODE: - OOHP

PATH:-

Img personnel management organisational management integration integration with pa prepare integration with pa.

18. TRANSFER DATA TO PA / TRANSFER ORG. ASSIGNMENT IN BATCH INPUT FOLDER FOR INFOTYPE 0001:-

In this step, you can use report rhinte30 to update the "organizational assignment" infotype (0001) for the personnel number you have selected with the data generated in previous organizational management actions.

The report creates a batch input folder for the personnel number, which is updated from the "organizational assignment" infotype for the person. The organizational assignment determined in organizational management using organizational objects, positions, jobs, work centers and cost centers is transferred into infotype 0001.

You can find information on activating batch input updates in the description of the entry "plogi prelu" in the step "set up integration with personnel administration".

Requirements

To start the report, integration between organizational management and personnel administration must be active (see "set up integration with personnel administration").

Activities

To update infotype 0001 for a personnel number or an area of personnel numbers, start report

rhinte30

Further notes

For additional information, see the online documentation on report rhinte30 via system -> services -> reporting, goto menu entry -> documentation.

TCODE: - OOHQ

PATH:-

Img personnel management organisational management integration with pa transfer data to pa.

19. CHECK INTEGRATION CONSISTENCY / CREATE MISSING OBJECTS (OM OR PA):-

In this step, you use report rhinte20 to determine whther data for objects relevant to integration is available in both personnel administration and organizational management.

Entries in the following tables (personnel administration) is compared to the corresponding objects created in file hrpnnn in the integration plan version (organizational management).

Personnel administration table

Organizational management object

T513/t513s

Job

T528b/t528t

Position, work center

T527x

Organizational unit

Objects missing in either personnel administration or organizational management can be added immediately.

Activities

1. Start report rhinte20.

2. Avoid inconsistencies.

TCODE: - OOPP

PATH:-

Img personnel management organisational management integration integration with pa check integration consistency.

20.

SETUP INTEGRATION WITH COST ACCOUNTING:

In this step, you set the controlling area that is used as a default value for cost accounting.

If you create relationships between cost centers and positions or organizational units, the system asks you to assign the cost center to a controlling area (cost centers are always assigned to a controlling area). In such cases, the value you define in this step is used as the default.

Activities

1. In the "abbr. Value" (abbreviation value) field, select the controlling area that is to be used

as the default value for cost accounting (enter ppint ppint).

2. Save your entry.

Further notes

For more information, refer to the documentation on "semantic group" and "semantic abbreviation" field entries.

TCODE: - OOCO

PATH:-

Img personnel management organisational management integration setup integration with cost accounting.

21. SETUP INTEGRATION FOR COST DISTRIBUTION:

Plogi costd

The plogi costd entry enables you to activate integration between organizational management and personnel administration for cost distribution.

Requirements

Integration between organizational management and personnel administration must be active.

The plogi feature must be set so that the holders participate in integration.

You must be in the active plan version.

Activities

To activate integration, enter "x".

TCODE: - OOCDIST

PATH:-

Img personnel management organisational management integration setup integration for cost distribution.

22. TO ACTIVATE / DEACTIVATE “VACANCY” INFOTYPE:-

In this step, you specify whether a position is vacant by virtue of infotype 1007 "vacancy" appended to it or whether every unoccupied position should be regarded as vacant.

By "vacancy", sap means that a position which is unoccupied is to be re-filled.

This data is particularly necessary for the recruitment module (transfer of vacant positions). If you wish to activate integration with recruitment, you have to set the switch ppvac ppvac in table t77so to 1. In order to re-occupy a position using the recruitment module, you have to create an infotype 1007 record. The system then creates a record in the pa table t75ox, thus setting up the interface with the recruitment module.

If the switch ppvac ppvac in table t77so is set at 0, integration with recruitment is inactive and consequently, every unoccupied position is viewed as vacant.

Activities

Specify whether the vacancy is to be maintained via infotype 1007.

Further notes

For information on possible entries, please refer to the documentation on the field entry semantic abbreviation.

TCODE: - OOVB

PATH:-

Img personnel management organisational management infotype settings activate / deactivate “vacancy” infotype.

23. MAINTAIN WORKING TIME GROUPS:

In this step, you edit entries in the check table for the "work schedule" infotype in the "work schedule group" field. You determine which: employee groups or employee subgroups belong to which work schedule group. Work schedule groups can be created as subtypes of infotype 1011 in the step maintain subtypes.

Maintain infotype 1011 for the organizational objects (organizational units, positions, work centers) in your enterprise, if you do not want to restrict working times with rule values (see the step maintain rule values). In this way, you can specify a specific working time for individual positions or organizational units and their subordinate organizational objects.

You can define working times of subordinate positions according to the inheritance principle using organizational units. By defining work schedule groups, you can determine, according to which employee group or subtype a position belongs to, the working time that it is assigned.

The advantage of this is that if the working time of several positions change, there is less data input if all the positions are assigned to a work schedule group.

Example

The positions assigned to an organizational unit all belong to the same employee group but are divided into two employee subgroups (according to infotype 1013). You can assign each subgroup specific working times using infotype 1011 which has been maintained for the organizational unit and the positions assigned to it.

Requirements

The working time stored for a working time group for an organizational unit can be evaluated if infotype 1013 "employee group/subgroup" is maintained for positions.

Before you assign your employee groups and employee subgroups to work schedule groups, you must have defined the subtypes for infotype 1011 "work schedule" in the step maintain subtypes ("work schedule group" is a subtype of the "work schedule" infotype).

Standard settings

As standard, employee groups and subgroups are already assigned to the following work schedule groups. These work schedule groups are set up as subtypes of infotype 1011 in the step maintain subtypes.

0001”salaried employees"

0002”hourly payed workers"

All "all work schedule groups"

Activities

Assign a combination of employee groups and subgroups to a work schedule group.

You can group together combinations of employee groups and subgroups that have not been assigned using a generic key (by entering *).

Further notes

The work schedule is only used as a reference in organizational management and does not affect payroll accounting, for example. The work schedule is, therefore, a guideline for planned working times in your enterprise.

TCODE: - OOGP

PATH:-

Img personnel management organisational management infotype settings working time maintain working time groups.

24. MAINTAIN RULE VALUES:

In this step, you define a rule value for the average working time that applies generally in your enterprise. Do this if you have not created infotype 1011 "work schedule" for your organizational units, positions and work centers.

With the entry "workt daily", you define a rule value for daily working time (in hours).

With the entry "workt daymt", you define a rule value for monthly working time (in days).

With the entry "workt daywk", you define a rule value for weekly working time (in days).

With the entry "workt dayyr", you define a rule value for annual working time (in days).

With the entry "workt perck", you determine which of these values is to be used as the the basis for the calculation of planned working times.

If you want to use these rule values as default values for the maintenance of infotype 1011, define which of the values you want to use.

With the entry "workt perck", you determine whether the daily, weekly, monthly or annual working time (see above) is to be used as the basis for the calculation of planned working times.

If you do not want to use a default value for the maintenance of infotype 1011, define which working time type is to be permitted and how large the number range is to be:

With the entry "workt perck", you determine whether the daily, weekly, monthly or annual working time is to be permitted as the basis for calculation of planned working times.

With the entries "workt maxhr" and "workt minhr", you specify the maximum and minimum values of daily working time to check plausability for the maintenance of infotype 1011, "work schedule". If this value is exceeded or is not reached, a warning appears.

You can define evaluation paths, with which working times for objects for which infotype 1011 has not be maintained, can be found:

With the entries "workt patha", "workt patho" and "workt paths", you determine evaluation paths, which the system uses to read working times for work centers, positions or organizational units.

If infotype 1011 has not be maintained for a position, for example, you can use the entry "workt paths" to determine the working time by reading the working time of the organizational unit to which the position is assigned.

If infotype 1011 has not be maintained for this organizational unit, the system reads the working time of the next superior organizational unit ("workt patho").

The following evaluation paths must be entered in table t778a.

Standard settings

Workt daily 800

Workt daymt 2170

Workt daywk 500

Workt dayyr 26000

Workt maxhr 2400

Workt minhr 100

Workt patha wrkt_ao

Workt patho wrkt_o

Workt paths wrkt_so

Workt perck m

Recommendation

The working time values that are determined by an overall rule value in infotype 1011 for an organizational unit, are used as the basis for the working time check. A working time check takes place, if you fill a position with a person. The working time for the position (from infotype 1011) is compared to the person's working time (from infotype 0007 of personnel administration). If these times differ, a warning appears.

The entry workt perck should always be the same as the corresponding entry in personnel administration.

If you do not want to maintain infotype 1011, you can change the entry workt perck at any time, as long as the entry in personnel administration is also changed.

If you want to maintain infotype 1011, decide this before begin the set up.

Otherwise you risk rounding errors and loss of data.

We generally recommend that you maintain infotype 1011 for the organizational objects in your enterprise (the root organizational unit at least), as this is the only way that a history will be kept of changes to working times.

Activities

1. Enter valid average working times per day as well as per week, month and year.

These entries must be to two decimal places, for example, the value 2170 for entry "workt daymt" means 21.7 days per month or a value of 800 for entry "workt dayly" means 8,00 hours per day.

D

= "workt daily"

W

= "workt daywk"

M

= "workt daymt"

Y

= "workt dayyr"

3.

Change the maximum or minimum values of working time per day.

This entries must also be to two decimal places, for example, a value of 1000 means 10,00 hours per day.

4. If you have defined specific evaluation paths in the step maintain evaluation paths, check

the default values entered.

TCODE: - OORW

PATH:-

Img personnel management organisational management infotype settings working time maintain rule values.

25. SET UP CHECK VALUES FOR AUTHORITIES / RESOURCES:-

In this step, you maintain the check table for infotype 1010 "authorities/resources".

This infotype is divided into two subtypes in the sap standard system:

"Authorities" are authorities and powers of attorney, which describe positions (regardless of their holders).

"Resources" are assigned to work centers (and positions), which require particular technical features.

Requirements

Before you create authorities, you must have specified subtypes for infotype 1010 in the step maintain subtypes.

Standard settings

The following subtypes are set up as standard:

0001 "authorities/powers of attorney"

0002 "technical resources"

Activities

Enter your authorities and resources requirements.

TCODE: - OOKO

PATH:-

Img personnel management organisational management infotype settings set up check values for authorities / resources.

26. SET UP CHECK VALUES FOR HEALTH EXAMINATION:-

In this step, you maintain the check table for infotype 1009 "health examinations".

This infotype is divided into two subtypes in the sap standard system:

Using the subtype "health exclusion", you can flag work centers that may not be filled by persons with previous illnesses.

For example, persons who have suffered from tuberculosis may not work in the cantine.

Using the subtype "preventive medical checkup", you can flag work centers which require examinations to be carried out at regular intervals (eye examinations, for example).

Requirements

Before you create preventive medical checkups, you must have determined subtypes for infotype 1009 in the step maintain subtypes.

Standard settings

The following subtypes are set up as standard.

0001 "health exclusion"

0002 "examination"

Activities

Enter the types of examinations required for health exclusions and examinations as well as the intervals at which the examinations are to take place.

TCODE: - OOGV

PATH:-

Img personnel management organisational management infotype settings set up check values for health examination.

27. SET UP CHECK VALUES FOR RESTRICTION:-

In this step, you maintain the check table for infotype 1006 "restrictions".

Using the restrictions from the infotype, you determine the work centers that are unsuitable for particular groups of persons, due to the working time or the type of activities involved.

Requirements

If you want to add reasons for these restrictions, set up the check table for reasons.

Standard settings

The standard system contains the following restrictions:

0001 "not suitable for female employees"

0002 "not suitable for severely challenged."

0003 "not suitable for adolescents"

Activities

Enter restrictions as required.

TCODE: - ?

PATH:-

Img personnel management organisational management infotype settings set up check values for restriction.

28. SET UP CHECK VALUES FOR REASON:-

In this step, you define reasons for all the "restrictions" in infotype 1006. These reasons can be combined with all the restrictions in infotype 1006.

Requirements

You must have first set up the restrictions check table in order to allocate the reasons.

Standard settings

The standard system contains the following reasons:

0001 "x rays"

0002 "night work"

0003 "often have to lift over 10kg"

0004 "piecework"

Activities

Enter reasons to meet your requirements.

TCODE: - ?

PATH:-

Img personnel management organisational management infotype settings set up check values for reason.

29. SET UP CHECK VALUES FOR BUILDING:-

In this step, you maintain addresses for buildings.

Building addresses are used to give information on the location of objects such as work centers or resources (rooms).

Note

In the step "maintain infotypes", you can specify in the "infotypes per object type" view which object types refer to a building address. Do so by entering the alternative screen number for the desired object type for the "address" infotype 1028.

Activities

Enter the required addresses.

TCODE: - ?

PATH:-

Img personnel management organisational management infotype settings set up check values for building.

30. SET SUBTYPES FOR QUOTA PLANNING:-

In this operation you define customer-specific subtypes of infotype 1019 (quota planning), and define further planning types in addition to the existing ones (first planning, second planning).

Activities

To define further subtypes of infotype 1019 quota planning, proceed as follows:

1. Call up the activity maintain subtypes

2. Select one of the existing table entries for infotype 1019 and choose new entries.

3. Make the desired entries regarding further subtypes, and save.

TCODE: - ?

PATH:-

Img personnel management organisational management infotype settings quota planning set subtypes for quota planning.

31.

DEFINE PLANNING TYPES AND PERIODS:-

This step enables you to enter settings that are used to determine the planning type and planning time frames during quota planning.

A planning type is selected for each round of planning; that is, the system determines whether

this is the first round of planning, or the second, etc. Within his or her application scenario, the user can only plan using the planning type flagged as current in this step.

The period (weeks, months, calendar quarters, years) is also entered for which the required positions must be planned.

The entire planning period is then entered for which the user must specify planning figures per round of planning. Note that the planning period should not be any longer than approximately three years because longer planning periods have a detrimental effect on performance.

Further notes

The activity is components.

performed for

the organizational

management

and

manager's

desktop

The following applies to manager's desktop: you enter settings that enable the line manager to schedule positions required in the future for organizational units directly subordinate to him or her as manager.

TCODE: - ?

PATH:-

Img personnel management organisational management infotype settings quota planning define planning types and periods.

32. DEFINE CALCULATION IN FULL TIME EQUIVALENTS (FTE):-

In this activity, you make settings relating to the calculation of the planning quota using full-

time equivalents (ftes). An fte is the target capacity (expressed in full-time positions) and corresponds to the relationship between the working time defined for a position and the working time defined for the organizational unit to which the position is assigned.

In

this activity, you can also specify that the value of an fte should be determined on the basis

of

the staffing percentage of the position in conjunction with the capacity utilization level of

the employee (person) who is assigned to this position.

Standard settings

The default value of the switches workt fteq and work ftep in the standard system is ' '.

Activities:-

1.

If you set the switch workt fteq to 'x', you are specifying that you want to carry out quota

planning using ftes rather than positions. In this case, you can use ftes with up to two places after the decimal point.

2. Using the switch workt ftep, you can specify that the value of an fte should either be

determined solely on the basis of the the planned working time of the position (switch = ' '), or on the basis of the staffing percentage of the position in conjunction with the capacity utilization level of the employee (person) (switch = 'x').

The latter option is particularly useful for calculating the required positions in an organizational unit in ftes - where the actual working time of an employee (person) in a position is of significance.

A) When the switch is set to ' ', two scenarios are possible:

Infotype 1011 (working time) is not defined for the position. In this case, an fte has the value

1.

Infotype 1011 (working time) is defined for the position. The value of an fte is determined using the inheritance logic contained in infotype 1011 (working time).

Examples:

If the weekly working time defined for a position is 20 hours, and if a weekly working time of 40 hours has been defined in infotype 1011 for the organizational unit to which the position is assigned, then the full-time equivalent is the working time of the position (20) divided by the working time of the organizational unit (40) = 0.5.

If, on the other hand, a weekly working time of 40 hours is defined for the position, and a weekly working time of 36 hours for the organizational unit, the value for the fte would be 40/36 = 1.11.

B) if you have set this switch to 'x', there are also two possible scenarios:

The position is unstaffed, or staffed by a user.

In this case, the value of the fte is 0.

The position is staffed by an employee (person).

In this case, the value of the fte is the product of the staffing percentage (a/b 008 relationship between s and p) and the capacity utilization level (stored in infotype 0008 of personnel administration), where 100% corresponds to the value 1.

Example:-

The staffing percentage is 100%, the capacity utilization level 50%. Following on from this, the value for an fte is 1 x 0.5 = 0.5. If the staffing percentage and capacity utilization level were both 50%, the value of the fte would be 0.5 x 0.5 = 0.25.

Further notes

Before you set the work fteq switch, make sure you know what the requirements in your company are. If you change the switch from 'x' to ' ' later, any decimal fractions in your quota planning will be truncated!

TCODE: - OOFT

PATH:-

Img personnel management organisational management infotype settings quota planning define calculation in full time equivalents (fte)

33. DEFINE MATRIX TYPES:-

Two different principles of subdivision overlap on the same level in a matrix organization, that is, there is vertical as well as horizontal division. In conjunction with organizational management, the points at which the two dimensions meet can, for example, represent positions that must perform tasks for both the vertical and horizontal dimension.

In this step, you define matrix types, which specify how the matrix organization will appear according to the selection of object types in the two dimensions.

First, you create start object types that are to be allocated to both the horizontal and vertical dimensions of the matrix organization.

By entering an evaluation path for each dimension ("sbesx", for example), you determine which additional object types are to be displayed in the matrix view and which object structures are therefore to be displayed in the structure view. Finally, you specify the type of relationship (matrix relationship) between the objects and the two dimensions.

Example:-

The following is an example of how a matrix organization works in an enterprise:

Example: - division matrix organization

An enterprise in the consumer industry has several hundred employees and is organized in a hierarchy according to function. After a while, three product groups or divisions form: the stereo department, the domestic appliances department and the bicycle department.

The division matrix organization is based on a division organization, overlapped by a hierarchy based on function. The managers of the divisions are responsible for their divisions, which are profit centers, and therefore economically, but not legally, independent enterprises.

The primary functions of these divisions are production and sales processes such as marketing, development or manufacturing, as well as secondary functions such as financial accounting, payroll and human resources, these are also functions of the central areas.

This leads to employees being subordinate to two people. The manager of financial accounting and payroll is subordinate both professionally and for matters of discipline to the manager of his division, he also follows the guidelines of the financial accounting and payroll areas.

The matrix provides you with a clear picture of the structure of the enterprise as described above and displays and evaluates the employees that are subordinated twice (and the positions they occupy), their allocation by function on the one hand, and the division they belong to on the other.

The central areas (object type o) are represented by organizational units in the vertical dimension, dimension 1, and the divisions (object type il) are arranged in dimension 2, the horizontal dimension. Assignments between the dimensions and the relationship period are represented by the points at which the dimensions cross.

The matrix relationship is employee (position) "belongs organizationally to" division x (a222), or Division x "incorporates sap organizational objects" (b 222).

To display the entire structure of dimension 1 (including the positions relevant to the matrix relationship), you must have entered the evaluation path "sbesx" in the previous example.

Activities

1. Choose 'new entries'.

The 'new entries: add detail' screen appears.

2. Enter an abbreviation of up to 10 characters and a name of up to 25 characters for the new

matrix type. You can use "division" and "division organization", for example.

3. Enter a name of up to 25 characters for the current dimension and select an object type (in

the above example, "central area" or "division" as well as object types "o" and "il").

4. By entering an evaluation path (for example: "sbesx"), you determine which structure within

the dimension can be displayed in the structure view. You do not have to enter an evaluation path if the objects in a dimension do not form a structure.

5. Select a name for the matrix organization which should apply to objects from both dimensions (a/b222, see above).

Further notes

You can enter the matrix type you defined in this step in the initial screen of matrix maintenance. The parameters of the matrix type will automatically be transferred to the dialog box. You then only have to enter the start objects for both dimensions.

TCODE: - OO9M

PATH:-

Img personnel management organisational management matrix organization define matrix types.

34.

SET UP EDITING PARAMETERS FOR STAFFING SCHEDULE:

In this step, you maintain the control parameters for format of staff assignments. Staff assignments represent the assignment of a holder (employee or r/3 user) to a position and its corresponding organizational unit.

For release 4.6b, report staff assignments was fully revised. The previous report was renamed rhsbes10. The revised report has the name rhsbes00. Depending on which report you want to use, you can specify function modules and evaluation paths in the parameter group sbes in table

t77s0.

In the parameter group sbes, you can enter the following function modules for report rhsbes10:

Function module to control the specific format of the list output

Function module to control the format of the additional personal data in the list output

Function module to control the specific format of the titles in the staff assignments

In the parameter group sbes, you can define the following evaluation paths for the reports rhsbes00 and rhsbes10:

Evaluation path for enhanced staff assignments:-

This evaluation path determines the manager, position holders as well as substitutes and successors in an organizational unit.

Evaluation path for staffing schedule:-

This evaluation path determines the manager and position holders in an organizational unit.

Evaluation path for organizational structure:-

This evaluation path determines the organizational units along an organizational structure that are to be considered in the staff assignments.

Evaluation path for position hierarchy:-

This evaluation path determines the position hierarchy (within) the organizational structures in the staff assignments

Standard settings:-

The following function modules and evaluation paths are set up as standard:

For report rhsbes10

Rh_sbes_li (staff assignments output)

Rh_sbes_pa (additional data on persons in staff assignments)

Rh_sbes_tp (title of staff assignments)

For reports rhsbes00 and rhsbes10

O-s-pext (evaluation path for enhanced staffing schedule)

O-s-pnor (evaluation path for staffing schedule)

Orgeh (evaluation path for organizational structure)

S-s (evaluation path for position hierarchy)

Activities:-

Enter the function modules and evaluation paths you require.

Further notes

Customer-specific function modules

Customer-specific functions modules are only supported by report rhsbes10.

Customer-specific function modules must have the same interface as sap function modules. The easiest way to create your own function modules is to copy an existing function module and adjust it to fit your requirements. It will be automatically created in the function group rhsd and will meet all technical system requirements. A customer-specific function module can also, however, be created in its own function group.

TCODE: - OOBS

PATH:-

Img personnel management organisational management dialog control set up editing parameters for staffing schedule

35. CUSTOMER ENHANCEMENTS (USER EXITS):

This step enables you to implement enhancements rhgb0001, rhgp0001, and rhsi0001 with their

components:-

Rhgb0001

Saplrhgb+cus: additional info on/off

Saplrhgc+cus: additional info on/off

Exit_saplrhgb_001: further info on/off

Exit_saplrhgb_002: fill text for customer-specific field

Exit_saplrhgb_002: fill header for customer-specific field

Rhgp0001

Saplrhgp+cus:

Exit_saplrhgp_001: further info on/off

Exit_saplrhgp_002: fill text for customer-specific field

Exit_saplrhgp_003: fill header for customer-specific field

Rhsi0001

Saplrhsi+cus: additional info on/off

If you want to implement one of these enhancements, you must first create a project and then assign the enhancement to the project. You then create coding for the enhancement, if necessary, and activate the project.

You are advised to use these enhancements together, and to assign them to a joint project.

Before creating a project, you are strongly advised to read the documentation on enhancing sap transactions, which you can access after calling this customizing activity by choosing help -> application help.

If you require general information on enhancements, call the sap library and choose bc - changing the sap standard. You are also provided with specific information on each enhancement after you have assigned it to your project.

Warning

You should only perform this activity if both of the following conditions have been met:

Sap standard processes do not meet your requirements.

You have detailed knowledge of programming in abap.

Activities

Create a project.

1. Enter a name for your project.

2. Choose enhancement -> create.

3. Enter a short text for your project, and choose save.

Assign components to your project.

4. Choose components.

5. Enter the name of the components you want to implement.

6. If you require detailed information on a component, choose documentation.

7. Choose save.

8. Choose back.

Make your changes to the coding.

9. Choose components.

10. Choose change.

11. Choose the component for which you want to enter new coding.

12. Choose include zxpbco01.

The system requires you to create this include. This enables you to enter your new coding.

Activate your project.

13. Go back to the initial screen, and choose activate project.

TCODE: - CMOD

PATH:-

Img personnel management organisational management dialog control customer enhancements (user exits).

36. SETTING FOR SIMPLE MAINTENANCE:

In this activity, you can set the following for the simple maintenance view:

System behaviour for delimiting or deleting an object, if other objects are subordinate to it

How chief positions are displayed

Standard settings

Entry ppom extck contains the value 'x'.

Entry ppom leper contains the value ' '.

Activities

Entry ppom extck enables you to determine whether, when you are delimiting or deleting an organizational unit or a position,

An error message is to appear advising that the subordinate objects must first be moved, deleted or delimited

Enter the value 'x'.

Direct changes to the assignment of subordinate objects is to be possible

Enter the value ' '.

This setting affects the following relationships:

Organizational unit - organizational unit

- position

- cost center

Position - person

- user

- business partner

Entry ppom leper enables you to determine,

Whether all chiefs for an organizational unit are to be displayed

Enter the value 'x'.

Whether only the current (key date) and the next chief of an organizational unit are to be displayed

Enter the value ' '.

TCODE: - OOPPOMSET

PATH:-

Img personnel management organisational management dialog control setting for simple maintenance.