|
SAP Community Network Forums
»
SAP Solutions
»
ERP HCM (HR)
Thread: Duplicate Object IDs
 |
This question is not answered.
|
|
Replies:
3
-
Pages:
1
-
Last Post:
Nov 9, 2009 3:35 AM
Last Post By: sapuser909
|
|
|
|
|
|
|
Duplicate Object IDs
Posted:
Nov 3, 2009 7:29 AM
|
|
|
|
Hello Gurus...
We have some object IDs in which we can find both position and org unit with same 8 digit number.
For example, If one of the positions get assigned with 50021000, we can find an org unit as well with same number which was created sometime/longtime back.
At what instances, this problem will come...? Please help me in this regard.
We have $$$$ only with the number range maintenance.
Cheers
Vinay
|
|
|
|
|
|
Re: Duplicate Object IDs
Posted:
Nov 8, 2009 2:48 PM
in response to: vijai vinai
|
|
|
|
Hello Vinay,
there is another point you might want to check. Are the objects you see in the table really your company objects? A very common error when setting up HR systems is that the admin forgets that HR Infotypes are technically customizing tables and sap delivers junk entries in these tables. If your client was copied from client 000 with customizing and without applying the necessary sap note you have copied tons of junk objects into the destination client. Check Table HRP1000 ff. for this.
Best Regards
Roman
|
|
|
|
|
|
Re: Duplicate Object IDs
Posted:
Nov 9, 2009 3:35 AM
in response to: vijai vinai
|
|
|
|
There is nothing wrong with your object ID being duplicating. You need to understand that in the Object table structure (HRP1000), any object will carry key fields: the client where it is residing, object type, plan version etc. This means when you need to retrieve a particular object, you need to make sure the key fields used are right. If you really want to distinguish object type with object id, then you need to define in your IMG the correct number range. This normally is done during the implementation. This means Object 'S' will have certain number range, 'O' will have different number range than 'S', etc. But if your system is already 'live' system it will be difficult to rearrange these number ranges. From the value that you provided, your system is using the default number range '$$$$'. There is no problem with this as long as when you are writing your report, you specify the correct keys when reading HRP1000.
|
|
|
|
|
