cancel
Showing results for 
Search instead for 
Did you mean: 

Problems creating hrp1000/1001 infotypes with HR function RH_INSERT_INFTY

Former Member
0 Kudos

Hi,

I'm trying to use fm <b>RH_INSERT_INFTY</b> in an rfc to create Personnel Planning infotypes 1000 and 1001. (I.e. to create a position.) They are linked, so I've tried creating using update type (vtask) of 'D' (Dialog) as well as 'B' (Buffer update) to just update the buffer with the 1000 and 1001 before applying the update. Whichever way I try I get the error "Creation of object ID 00000000 is not allowed" when I call fm RH_INSERT_INFTY.

Any ideas what I'm doing wrong please.

Can you create an infotype 1000 and 1001 in one call to the fm ? Or do you have to call it twice, once for each infotype ?

Thanks,

Craig.

Accepted Solutions (0)

Answers (2)

Answers (2)

ssimsekler
Active Contributor
0 Kudos

Hi Craig

To create an HR object, try the FM <b>"RH_CREATE_OBJECT"</b>. To create relation data you can use <b>"RH_INSERT_INFTY_1001".</b>

Or you can make use of the HR BAPI written for this.

For HR objects (comprising also PD) you can use the Business Object <b>"HRMasterDataReplica"</b>. It has a class method as <b>"SaveReplicaMultiple"</b> where you can pass your data to the interface.

You fill <b>"BAPIHROBJ" and "BAPIHRINF"</b> mainly and other infotype-related parameters. e.g. for infotype 1000 <b>"PdObject"</b> (structure like p1000) and for 1001 <b>"PdObjectRelationships"</b> (structure like p1001).

These are BO names, you can use the transaction code <b>"BAPI"</b> for more information.

The BAPI for this method is discussed also at .

<i>And as a last thing, let me introduce you the SDN forums pointing system: You can assign points to posts you find helpful while solving your question. You can reward points by clicking the yellow star icon at header of each reply post. You can reward;

- one 10 points (solved)

- two 6 points (very helpful answer)

- many 2 points (helpful answer)</i>

Kind Regards...

*--Serdar

Former Member
0 Kudos

Craig,

I don't think creating HRP1000 and 1001 within the same FM is a good idea. First SAP would have to generate that unique position# -- which it does after HRP1000 is filled and then using the STEXT field of HRP1000 you will have to get that position# and then populate the HRP1001 table for different relationships.

Kshitij.