Vous êtes sur la page 1sur 3

Organizational Management Definition Organizational Management - Info-types , Tables, Transaction Codes & Actions Organizational Management Paths OM Basic:


INFO TYPES: Info types are information tables which capture all logically related data. They are identified by four digit number. The number ranges from 0000 to 9999.

TO SEE INFO TYPES OF OM/PD AND LSO/MBO, use transaction code SM30 and enter table T777i. Info types do not store any data. An info type is a structure and not a table. For every info type, there is a backend data base table. To see any back end data base table, we may use transactions S11/SE16/SE16N. TIME CONSTRAINTS: Time constraints are for deciding as to how many records we can have at a given period of time. The length of time constraint is 1. A Time Constraint indicates whether more than one info type record may be available at one time. The following Time Constraint Indicators are permissible: Time Constraint 1: An Info Type record must be available at all times. This record may have no gaps. We may not delete the record last stored on the database because all records of this Info Type would otherwise be deleted. Time Constraint 2: Only one record must be available at one time, but time gaps are permitted. Time Constraint 3: Any number of records may be valid at one time, and time gaps are permitted. Time Constraint A: Only one record may ever exist for this Info Type. This record is valid from 01.01.800 to 31.12.9999. Splitting is not possible. Time Constraint B: Only one record may ever exist for this Info Type. It is valid from 01.01.800 to 31.12.9999. Splitting is not possible, but can be deleted. Time Constraint T: The time constraint values depend on subtype. Time Constraint Z: This refers to or points to Time Management Info Types. The time constraint for these Info Types depends on the time constraint class defined in view V_554Y_B 1 Without gap. No deletion. Example: Org objects. Bank Account 2 W/o gaps. Can be deleted. Most info types have this time constraint. 3 There can be multiple valid active records, with gaps. Deletion is possible. Examples: Children. Cell phone numbers. 4 - A Example: IT 0003. There is no other info type with this TC. Cannot be deleted. 5 - B Like A. Can be deleted. There are six ways or methods for handling Organizational Objects. They are:

1. Simple Maintenance 2. Matrix Organization

3. 4. 5. 6.

Organization and Staffing Actions Expert Mode General Structure



2. 3. 4.

RHINTE00 PA to OM: The client may not implement OM. After some time they may need OM. At that time we have to this program. When we run this program, whatever positions existing in PA will go to OM from PA the program reads form IT 0001 and enter in OM. However, reporting structure should be maintained manually. A/0008 Holder. Whenever we hire a person, the system will create relationship A/0008. When we upload OM and Employee Master Data separately, this relationship is not loaded. Hence we have to run program RHINTE00. Whenever we upload, we must compulsorily run RHINTE00 to create relationship. RHINTE10 OM to PA: Suppose we created all in OM. We can hire only through PA Module. When we hire, we should get data from OM. RHINTE20 Consistency Check. Compares data in OM and PA. This program will show the missing objects. Comparison will be done with object IDs, the eight digit code. RHINTE30 After learning PA, we will study this.