Error Exception when posting IT0008

[Former Member]

Hi guru all,

i'm having problem in creating infotype 0008, it shows error message CX_HRPA_INVALID_PARAMETER, i already read the topic with same problem, but somehow i don't get the solution for my problem, can u give me a hand? Thanks

for the code, the example like this :

CALL FUNCTION 'HR_INFOTYPE_OPERATION'

EXPORTING

infty = '0008'

number = wa_basic-pernr

subtype = wa_basic-subty

• OBJECTID =

• LOCKINDICATOR =

validityend = wa_basic-endda

validitybegin = wa_basic-begda

• RECORDNUMBER =

record = wa_basic

operation = 'INS'

tclas = 'A'

dialog_mode = '0'

• NOCOMMIT =

• VIEW_IDENTIFIER =

• SECONDARY_RECORD =

IMPORTING

return = v_return

key = l_key

EXCEPTIONS

OTHERS = 1.

[Former Member]

Hi julius,

1. make sure your wa_basic

is defined as :

data : wa_basis like p0008.

2. Also check out the definitions of

the variables

v_return

l_key

regards,

amit m.

[Former Member]

Thanks for the reply,

1. my wa_basic already defined like ur answer

2. the definition of v_return LIKE bapireturn1

l_key LIKE bapipakey,

Didn't solve my problem, the error still occured, thanks

Regards,

Julius

[suresh_datti]

How abput the date format of wa_basic-begda & wa_basic-endda? I would suggest to change the DIALOG_MODE = '2' & execute it.. this way, you can see if the correct values are getting passed onto the infotype screen.

Regards,

Suresh Datti

[Former Member]

hi

can u show the declarations for the parameters

as per the FM the foll r the parameter data types

VALUE(INFTY) LIKE PRELP-INFTY

*" VALUE(NUMBER) LIKE P0001-PERNR

*" VALUE(SUBTYPE) LIKE P0001-SUBTY OPTIONAL

*" VALUE(OBJECTID) LIKE P0001-OBJPS OPTIONAL

*" VALUE(LOCKINDICATOR) LIKE P0001-SPRPS OPTIONAL

*" VALUE(VALIDITYEND) LIKE P0001-ENDDA OPTIONAL

*" VALUE(VALIDITYBEGIN) LIKE P0001-BEGDA OPTIONAL

*" VALUE(RECORDNUMBER) LIKE P0001-SEQNR OPTIONAL

*" VALUE(RECORD)

*" VALUE(OPERATION) LIKE PSPAR-ACTIO

*" VALUE(TCLAS) LIKE PSPAR-TCLAS DEFAULT 'A'

*" VALUE(DIALOG_MODE) TYPE C DEFAULT '0'

*" VALUE(NOCOMMIT) LIKE BAPI_STAND-NO_COMMIT OPTIONAL

*" VALUE(VIEW_IDENTIFIER) LIKE P0003-VIEKN OPTIONAL

*" VALUE(SECONDARY_RECORD) OPTIONAL

*" EXPORTING

*" VALUE(RETURN) LIKE BAPIRETURN1 STRUCTURE BAPIRETURN1

*" VALUE(KEY) LIKE BAPIPAKEY STRUCTURE BAPIPAKEY

[Former Member]

hi

can u show the declarations for the parameters

as per the FM the foll r the parameter data types

VALUE(INFTY) LIKE PRELP-INFTY -> '0008'

*" VALUE(NUMBER) LIKE P0001-PERNR ->wa_basic-pernr like p0008-pernr

*" VALUE(SUBTYPE) LIKE P0001-SUBTY OPTIONAL-> wa_basic-subty like p0008-subty

*" VALUE(OBJECTID) LIKE P0001-OBJPS OPTIONAL ->not filled

*" VALUE(LOCKINDICATOR) LIKE P0001-SPRPS OPTIONAL->not filled

*" VALUE(VALIDITYEND) LIKE P0001-ENDDA OPTIONAL ->wa_basic-endda like p0008-endda

*" VALUE(VALIDITYBEGIN) LIKE P0001-BEGDA OPTIONAL ->

->wa_basic-begda like p0008-begda

*" VALUE(RECORDNUMBER) LIKE P0001-SEQNR OPTIONAL->not filled

*" VALUE(RECORD) -> wa_basic, structure p0008

*" VALUE(OPERATION) LIKE PSPAR-ACTIO ->INS

*" VALUE(TCLAS) LIKE PSPAR-TCLAS DEFAULT 'A' ->A

*" VALUE(DIALOG_MODE) TYPE C DEFAULT '0' ->'0'

*" VALUE(NOCOMMIT) LIKE BAPI_STAND-NO_COMMIT OPTIONAL ->not filled

*" VALUE(VIEW_IDENTIFIER) LIKE P0003-VIEKN OPTIONAL ->not filled

*" VALUE(SECONDARY_RECORD) OPTIONAL ->not filled

*" EXPORTING

*" VALUE(RETURN) LIKE BAPIRETURN1 STRUCTURE BAPIRETURN1->same like my previous answer

*" VALUE(KEY) LIKE BAPIPAKEY STRUCTURE BAPIPAKEY ->same like my previous answer

[Former Member]

Hi again,

1. U can try by passing some extra parameters also.

2. like this (note, the variable names in mycase are different)

3.

CALL FUNCTION 'HR_INFOTYPE_OPERATION'

EXPORTING

infty = '0008'

number = ptab-pernr

subtype = np0008-subty

recordnumber = np0008-seqnr

objectid = np0008-objps

lockindicator = np0008-sprps

record = np0008

operation = operation

validityend = np0008-endda

validitybegin = np0008-begda

dialog_mode = '0'

nocommit = nocommit

IMPORTING

return = ret

key = k.

regards,

amit m.

[Former Member]

I already tried it, by adding some extra parameters, but it didn't work either. Thanks

Regards,

Julius

[suresh_datti]

Did you change teh DIALOG_MODE to '2'? Does the Infotype 0008 screen get displayed with your values?

Regards,

Suresh Datti

[Former Member]

Hi again,

1. If everything is tried, and still error,

then probably it must have to do with

the data in p0008.

2. Just check out if the wage types and other fields

are ok or not in the data.

regards,

amit m.

[Former Member]

Try removing the 'subtype' parameter, IT0008 doesn't have subtypes.

What happened when you changed dialog mode to 2?

[Former Member]

I already change it to dialog mode 2, it's okay but there is an error message like this : there is no range value min or max for position 30000011. for ur consideration, subtype 0 is exist which is basic contract

[Former Member]

Hi again,

1. It seems this is not an FM error,

but error while posting the transaction.

2. The same data,

if entered manually using PA30 tcode

for the same pernr,

should also give this error.

3. If possible, manual entry should be tried,

to know if its the error message given

by the transaction (for data consistency)

.

regards,

amit m.

[suresh_datti]

Yes.. I agree with Amit..the erro is not related to the function call but lies with the data..You can maintain the Planned Compensation in PP01 for the Position in question.

Regards,

Suresh Datti

[Former Member]

I see.... but after dialog mode 2 executed, and entered the infotype window. after i finished saved it, after that it triggered error like this CL_HRPA_MASTERDATA_FACTORY====CP.

IF a_is_initialized = true.

• This indicates some complex problem which often can be easily

• fixed. For details see NOTE 493984 (2003).

RAISE EXCEPTION TYPE cx_hrpa_violated_precondition.

and the program returns to error message

[Former Member]

Hi again,

I'm done with tcode PP01, and it still showed the same error like i said before. CL_HRPA_MASTERDATA_FACTORY====CP. I was also posting basic pay manual, with the same data. When the input data is done, and the button saved is clicked, it didn't give any error exception. But when i'm using the program to upload basic pay, after the dialog mode 2 then clicked save button mode, it gave error exception.

[Former Member]

Hi Memeo

I get the same exception.

Did you fix it?

Regards,

Jacob Vennervald

[Former Member]

I'm done fixing it.

I add the code at the top of the program with this code

LOAD-OF-PROGRAM.

PERFORM do_nothing(sapfp50p).

This error occured because it dealed with some kind of frame works, so we must use this subroutine to disable or stop the frame work, so the error exception didn't occur.

Thanks