Invalid parameter SECONDARY_RECORD-PSKEY Error in Dependent/Family Member Screen

[Former Member]

Hi All,

We are in EHP6. The Family Member and Dependent iview is throwing an error while trying Edit something. I am able to add a new Beneficiary/Dependent but getting the following dump while trying to Edit/Save any existing dependent information.

I looked through SAP Note-1815863 - Dump in Class CL_HRPA_INFOTYPE_CONTAINER Method. However all the tables mentioned in that Note seemed to be configured properly.

Any help will be appreciated.

Short Dump

Error while processing your query What has happened? The URL call sap/bc/webdynpro/sap/HRESS_A_PERSINFO was terminated because of an error.

Note The following error occurred in system DEV : Invalid parameter SECONDARY_RECORD-PSKEY , value 1008119301067 9999123120130621000 The error occurred on application server HRE_05 and in work process. 8 The termination type was: RABAX_STATE The ABAP call stack was: Method: IF_HRPA_INFTY_CONTAINER_DATA~MODIFY_SECONDARY_RECORD of program CL_HRPA_INFOTYPE_CONTAINER====CP

What can I do? If the termination type was RABAX_STATE, you will find more information on the cause of termination in system HRE in transaction ST22. If the termination type was ABORT_MESSAGE_STATE, you will find more information on the cause of termination on the application server HRE_05 in transaction SM21. If the termination type was ERROR_MESSAGE_STATE, you can search for further information in the trace file for the work process 8 in transaction ST11 on the application server HRE_05 . You may also need to analyze the trace files of other work processes. If you do not yet have a user ID, contact your system adminmistrator.

[VJ22]

Hi ,

Any one can please let me know how do you resolve this error. I am also getting same error.

Regards,

Vijay

[Former Member]

There could be several possible causes

Usually this error occurs if a secondary infotype functionality has been delivered via SP or SNOTE for infotype 0002 but the PERNR you are using does not have secondary infotype record

Tables V_T582V & V_T582W determine if a secondary infotype will be used - if you remove entries here this will deactivate the secondary infotype useage - this might be one way to resolve the issue - but perhaps you wish to use the secondary infotype - in some cases it might be required- for example ESS might expects a secondary infotype and throw an error if there is an issue

If you wish to use the secondary infotype you need the delivered entries in V_T582V & V_T582W and you need to run RPUPAV00 for any PERNR that has a 0002 record existing prior to the new secondary infotype being introduced to ensure they have a secondary infotype record key that matches the primary infotype key

Regards

[former_member284828]

Hi All,

Even I am stuck at the same problem, has anyone got the solution regarding this ? It will be of great help.

Thanks,

Nikhil

[jayaprakash_thanadavaraya]

Hi sanghamitra,

  i checked through the debugging the classes cl_hrpa_infptype_conatiner  and cx_hrpa_invalid_parameter.when you are execute the hress_a_perinfo these class holding the texts of mandatory fields like position,employee group,department,employee subgroup.you just check debugg whether these classes returing texts or not?

Regards

Jayaprakash T

[Former Member]

Hi Sanghamitra,

I am facing similar error in my project. Did you found any resolution to this ?

In my case, looks like SAP code compares 2 structures PSKEY and A_PSKEY for infotypes with secondary views (to check key uniqueness). But some where along the code, the Start Date of the primary infotype is changed to System date (and not the Database BEGDA value) and hence the key comparision fails and dumps, still no luck finding where this is changing.

Thanks!

Karthik Kumaaravel.

[Former Member]

Hi Shankar,

as pe sap note: 1815863, i updated table V_T582V & V_T582W. as per sapnote: 1542198, i maintained tcode-GENIL_MODEL_BROWSER.

here i am giving ST22 dump.

Category

ABAP Programming Error

Runtime Errors

UNCAUGHT_EXCEPTION

Except.

CX_HRPA_INVALID_PARAMETER

ABAP Program

CL_HRPAD_IL===================CP

Application Component

PA-ESS-XX-WDA

Date and Time

23.09.2013

18:59:23

    Short text

An exception occurred that was not caught.

    What happened?

	The exception 'CX_HRPA_INVALID_PARAMETER' was raised, but it was not caught
	anywhere along
	the call hierarchy.
	Since exceptions represent error situations and this error was not
	adequately responded to, the running ABAP program
	'CL_HRPA_INFOTYPE_CONTAINER====CP' has to be
	terminated.

    What can you do?

Note down which actions and inputs caused the error.

	To process the problem further, contact you SAP system
	administrator.
	Using Transaction ST22 for ABAP Dump Analysis, you can look
	at and manage termination messages, and you can also
	keep them for a long time.

    Error analysis

	An exception occurred that is explained in detail below.
	The exception, which is assigned to class 'CX_HRPA_INVALID_PARAMETER', was not
	caught in
	procedure "MODIFY_MAIN_RECORDS" "(METHOD)", nor was it propagated by a RAISING
	clause.
	Since the caller of the procedure could not have anticipated that the
	exception would occur, the current program is terminated.
	The reason for the exception is:
	Invalid parameter SECONDARY_RECORD-PSKEY, value 900000010558
	9999123119840403000

    How to correct the error

	If the error occures in a non-modified SAP program, you may be able to
	find an interim solution in an SAP Note.
	If you have access to SAP Notes, carry out a search with the following
	keywords:
	"UNCAUGHT_EXCEPTION" "CX_HRPA_INVALID_PARAMETER"
	"CL_HRPA_INFOTYPE_CONTAINER====CP" or "CL_HRPA_INFOTYPE_CONTAINER====CM019"
	"IF_HRPA_INFTY_CONTAINER_DATA~MODIFY_SECONDARY_RECORD"

	If you cannot solve the problem yourself and want to send an error
	notification to SAP, include the following information:
	1. The description of the current problem (short dump)
		To save the description, choose "System->List->Save->Local File
	(Unconverted)".
	2. Corresponding system log
		Display the system log by calling transaction SM21.
		Restrict the time interval to 10 minutes before and five minutes
	after the short dump. Then choose "System->List->Save->Local File
	(Unconverted)".
	3. If the problem occurs in a problem of your own or a modified SAP
	program: The source code of the program
		In the editor, choose "Utilities->More
	Utilities->Upload/Download->Download".
	4. Details about the conditions under which the error occurred or which
	actions and input led to the error.
	The exception must either be prevented, caught within proedure
	"MODIFY_MAIN_RECORDS" "(METHOD)", or its possible occurrence must be declared
	in the
	RAISING clause of the procedure.
	To prevent the exception, note the following:

    System environment

	SAP Release..... 702
	SAP Basis Level. 0011
	Application server... "RIPDEV01"
	Network address...... "192.168.0.43"
	Operating system..... "HP-UX"
	Release.............. "B.11.31"
	Hardware type........ "ia64"
	Character length.... 16 Bits
	Pointer length....... 64 Bits
	Work process number.. 3
	Shortdump setting.... "full"
	Database server... "RIPDEV01"
	Database type..... "SYBASE"
	Database name..... "RD1"
	Database user ID.. "SAPSR3"
	Terminal.......... "192.168.0.2"
	Char.set.... "C"
	SAP kernel....... 720
	created (date)... "Jul 8 2012 19:47:08"
	create on........ "HP-UX B.11.31 U ia64"
	Database version. "Sybase ASE 15.7.0.105 "
	Patch level. 300
	Patch text.. " "
	Database............. "15.7"
	SAP database version. 720
	Operating system..... "HP-UX B.11.31"
	Memory consumption
	Roll.... 0
	EM...... 25138752
	Heap.... 0
	Page.... 16384
	MM Used. 22052512
	MM Free. 3082448

    User and Transaction

	Client.............. 400
	User................ "RIPL_MGR"
	Language key........ "E"
	Transaction......... " "
	Transaction ID...... "524066483A2437F0E1000000C0A8002B"
	EPP Whole Context ID.... "10604B3532EA1ED3898A7E757B754800"
	EPP Connection ID....... "10604B3532EA1ED3898A7E7579F81806"
	EPP Caller Counter...... 1
	Program............. "CL_HRPA_INFOTYPE_CONTAINER====CP"
	Screen.............. "SAPMHTTP 0010"
	Screen Line......... 2
	Debugger Active..... "none"

    Server-Side Connection Information

	Information on Caller of "HTTP" Connection:
	Plug-in Type.......... "HTTP"
	Caller IP............. "192.168.0.2"
	Caller Port........... 1080
	Universal Resource ID. "/sap/bc/webdynpro/sap/HRESS_A_PERSINFO"
	Program............. "CL_HRPA_INFOTYPE_CONTAINER====CP"
	Screen.............. "SAPMHTTP 0010"
	Screen Line......... 2
	Information on Caller ofr "HTTP" Connection:
	Plug-in Type.......... "HTTP"
	Caller IP............. "192.168.0.2"
	Caller Port........... 1080
	Universal Resource Id. "/sap/bc/webdynpro/sap/HRESS_A_PERSINFO"

    Chain of Exception Objects

Attrib. Name

Value

Level

1

Class

CX_HRPA_INVALID_PARAMETER

Program

CL_HRPA_INFOTYPE_CONTAINER====CP

Include

CL_HRPA_INFOTYPE_CONTAINER====CM019

Row

43

Short Te

Invalid parameter SECONDARY_RECORD-PSKEY, value 900000010558

9999123119840403000

    Long Tex

    IS_RESUMABLE

    KERNEL_ERRID

PARAMETER													SECONDARY_RECORD-PSKEY
VALUE													900000010558	9999123119840403000

    Information on where terminated

	Termination occurred in the ABAP program "CL_HRPA_INFOTYPE_CONTAINER====CP" -
	in "IF_HRPA_INFTY_CONTAINER_DATA~MODIFY_SECONDARY_RECORD".
	The main program was "SAPMHTTP ".
	In the source code you have the termination point in line 43
	of the (Include) program "CL_HRPA_INFOTYPE_CONTAINER====CM019".
	The termination is caused because exception "CX_HRPA_INVALID_PARAMETER"
	occurred in
	procedure "MODIFY_MAIN_RECORDS" "(METHOD)", but it was neither handled locally
	nor declared
	in the RAISING clause of its signature.
	The procedure is in program "CL_HRPAD_IL===================CP "; its source
	code begins in line
	1 of the (Include program "CL_HRPAD_IL===================CM00H ".

    Source Code Extract

Line	SourceCde
	13	CLEAR container.
	14
	15
	16	IF secondary_record IS INITIAL.
	17		CALL METHOD cl_hrpa_infotype_container=>assert_secondary_infty
	18		EXPORTING
	19		tclas	= me->a_tclas
	20		pernr	= me->a_pskey-pernr
	21		primary_infty   = me->a_pskey-infty
	22		itbld	= me->a_pshd1-itbld
	23		secondary_infty = space.
	24	ELSE.
	25		ASSIGN secondary_record TO <secondary_pshdr> CASTING.
	26		secondary_infty = <secondary_pshdr>-infty.
	27
	28		CALL METHOD cl_hrpa_infotype_container=>assert_secondary_infty
	29		EXPORTING
	30		tclas	= me->a_tclas
	31		pernr	= me->a_pskey-pernr
	32		primary_infty   = me->a_pskey-infty
	33		itbld	= me->a_pshd1-itbld
	34		secondary_infty = secondary_infty.
	35
	36	*   check for matching pskey of secondary infotype
	37		pskey	= <secondary_pshdr>-pskey.
	38		pskey-infty = a_pskey-infty.
	39		IF pskey <> a_pskey.
	40		CREATE DATA illegal_parameter_ref.
	41		illegal_parameter_ref->* = <secondary_pshdr>-pskey.
	42
>>>>>		RAISE EXCEPTION TYPE cx_hrpa_invalid_parameter
	44		EXPORTING
	45		parameter = 'SECONDARY_RECORD-PSKEY'
	46		value	= illegal_parameter_ref->*.
	47		ENDIF.
	48	ENDIF.
	49
	50
	51	l_container ?= me->clone( ).
	52
	53	IF secondary_record IS INITIAL.
	54		CLEAR l_container->a_secondary_record.
	55		CLEAR l_container->a_secondary_infty.
	56	ELSE.
	57		l_container->a_secondary_infty = <secondary_pshdr>-infty.
	58		CALL METHOD cl_hrpa_infotype_container=>get_type_nnnn
	59		EXPORTING
	60		tclas	= a_tclas
	61		infty	= <secondary_pshdr>-infty
	62		IMPORTING

    Contents of system fields

Name			Val.
SY-SUBRC			0
SY-INDEX			1
SY-TABIX			0
SY-DBCNT			1
SY-FDPOS			1
SY-LSIND			0
SY-PAGNO			0
SY-LINNO			1
SY-COLNO			1

    SY-PFKEY

    SY-UCOMM

SY-TITLE			HTTP Control
SY-MSGTY			E

    SY-MSGID

SY-MSGNO			000
SY-MSGV1			DATA_SHARING_SPACE
SY-MSGV2			IT0002

    SY-MSGV3

    SY-MSGV4

SY-MODNO			0
SY-DATUM			20130923
SY-UZEIT			185922
SY-XPROG			SAPCNVE
SY-XFORM			CONVERSION_EXIT

Regards,

Anthony Kisku

[former_member182426]

can you place the error log from t-code ST22.

[sahirn]

Hi Sangamitra,

Please generate all the secondary infotypes for the pernr and then retry.

There is a report that can be for the doing the same, but at this moment I am not able to recall its name.

Hope this helps.

Regards,

Sahir.

[Former Member]

Thanks Sahir ! Is there any program or transaction to re-generate the secondary Infotypes ? Its an issue for entire employee population.

[sahirn]

You are welcome Sanhamitra.

Try using report RPUPAV00.

Hope this helps.

With regards,

Sahir.

[Former Member]

Hi Sahir,

Used that and still getting the same error.

[siddharthrajora]

does it work in backend system , I have seen this error earlier, it can be due to multiple reasons like subtype config, inconsistent data

I would recommend you to raise a message, does It occur for all employees?

[Former Member]

Hi Siddarth,

Yes it occurs for all employees. We have raised a OSS note already. However no helpful response yet. Still waiting.

Thanks

Sanghamitra

[sahirn]

Hi Sanghamitra,

We had similar issues after upgrading to EA-HRGXX/RXX 607 SP09.

To resolve we ran the report in a job:

Program name - RPUPAV00

Text                - Regeneration of Additional ITs for Views

Variant - Country Grouping - <releveant country>

             Personnel Number - Blank

             Delimitation Date   - System date

             Test                     -  Not Checked

Try running the report for one of the pernr with correct parameter and see if it works.

Otherwise waiting for SAP's response.

Hope this helps.

Regards,

Sahir.

[Former Member]

Hi Sanghamitra,

How did u resolve your issue, could share it, because we too are getting same error while changing Personal information from portal.

Error attached.

Regards,

Anthony Kisku

[marcin_czarny_nype]

Hi,

have you compared structure PSKEY and A_PSKEY in class CL_HRPA_INFOTYPE_CONTAINER in method MODIFY_SECONDARY_RECORD? During debugging pay attention on begda in both structure and let me know. You can set breakpoint at 39. line in mentioned method.

Regards,

Marcin