|
Title
Combining Infotype Records Purpose
This report serves to combine infotype records, which are split(infotype 1000 and 1001) and which overlap or are assignedsuccessively, into one record.
When integration between Personnel Administration and OrganizationalManagement is active, records of this type originate for technicalreasons, particularly after report RHINTE00 has been run.
You do not have to continue working with two records if they overlap orare assigned successively. A combined record contains exactly the samedata as two seperate records.
The advantage of combined records, is that the load on your database isreduced considerably.
The report combines split records for the following object types:
O Organizational unit
C Job
S Position
P Person
K Cost center
Records are only combined if the names of the objects are the same forall records in all languages.
This prerequisite is illustrated by these three examples, showing thebehavior of the report in various cases:
Example 1:
OT,,ID,,IT,,,,ST,,BEGDA,,,,ENDDA,,,,SPR,,SHORT,,LONG
O,,10,,1000,,1,,01.01.1998,,31.12.1998,,EN,,Sal.,,Sales
O,,10,,1000,,1,,01.01.1999,,31.12.9999,,EN,,Sal.,,Sales
These two records are combined to make the following record:
O,,10,,1000,,1,,01.01.1998,,31.12.1998,,EN,,Sal.,,Sales
Split infotype records (infotype 1000) can not be combined if theirshort texts and/or names are different (example 2). This restrictionalso applies if there is a difference between the translations of theabbrevaiations and/or names (example 3).
Example 2:
OT,,ID,,IT,,,,ST,,BEGDA,,,,ENDDA,,,,SPR,,SHORT,,LONG
O,,10,,1000,,1,,01.01.1998,,31.12.1998,,EN,,Sal.,,Sales
O,,10,,1000,,1,,01.01.1999,,31.12.9999,,EN,,Sal.,,Sales-1
In this example, the records are not cobined as the names of the tworecords are different.
Example 3:
OT,,ID,,IT,,,,ST,,BEGDA,,,,ENDDA,,,,SPR,,SHORT,,LONG
O,,10,,1000,,1,,01.01.1998,,31.12.1998,,EN,,Sal.,,Sales
O,,10,,1000,,1,,01.01.1999,,31.12.9999,,EN,,Sal.,,Sales
O,,10,,1000,,1,,01.01.1998,,31.12.1998,,DE,,Verk.,,Verkauf
O,,10,,1000,,1,,01.01.1999,,31.12.9999,,DE,,Verk.,,Verkauf-1
In this example, the records are not combined as the names aredifferent in German.
If the validity period of the translated records is shorter than thecombined records, the translated record is extended accordingly.
Example 4:
OT,,ID,,IT,,,,ST,,BEGDA,,,,ENDDA,,,,SPR,,SHORT,,LONG
O,,10,,1000,,1,,01.01.1998,,31.12.1998,,EN,,Sal.,,Sales
O,,10,,1000,,1,,01.01.1999,,31.12.9999,,EN,,Sal.,,Sales
O,,10,,1000,,1,,01.01.1998,,31.12.1998,,DE,,Verk.,,Verkauf
In this example, the first two records are combined and the third isextended. Features
Combining infotype records and the output of a log. Parameter
Combine Object parameter
Choose this parameter if you want to combine split infotype records forinfotype 1000 (object).
Combine Relationship parameter
Choose this parameter if you want to combine split infotype records forinfotype 1001 (relationship).
If you use the parameter without the following Relationshipparameter , all split infotype records (regardless of subtype) arecombined.
Relationship parameter
Use this parameter if you want to restrict the split records forinfotype 1001, which can be combined, according to subtype.
Test parameter
This parameter enables you to run this report as a test. No changes aremade to the database, a list of all records that have been changedduring an active run is produced.
The Test parameter is set as a default.Output
The records in the log are combined. Activities
Using the object selection parameter (sequential, structural andselection period) select the objects whose records you wish to combine.
Make the appropriate entries in Combine Object, CombineRelationship, Relationship and Test.
Choose Program -> Execute.
A log is produced, containing the records that have been combined orinformation explaining that no records exist that can be combined. |