Solved: Dump Error in Tcode:PA30/ PA20 after Version Upgra...

former_member311223 · ‎2013 Sep 19

Dear Experts,

I am facing a issue after upgrading the SAP System from EHP5 to EHP6 in Tcode: PA30/PA20.

I am getting Dump Error when I am double clicking on the Personal Numbers from the Hit List in PA30/PA20 for certain employees.It seems dumps are occurring for Chinese users. I searched SAP Notes for the same but could not find a proper SAP Note to solve this issue. I tried the SAP Notes: 1052552 and 1303276. But the Status of the SAP Notes are : “Cannot be Implemented”.

Unable to solve this issue Kindly suggest. I am attaching the error details below.

Category ABAP Programming Error

Runtime Errors UNCAUGHT_EXCEPTION

Except. CX_HRPA_INVALID_INFOTYPE_DB

ABAP Program CL_HRPA_SAPUP50R_ADAPTER======CP

Application Component PA-PA-XX

Date and Time 18.09.2013 15:40:31

----------------------------------------------------------------------------------------------------

|Short text |

| An exception occurred that was not caught. |

----------------------------------------------------------------------------------------------------

|What happened? |

| The exception 'CX_HRPA_INVALID_INFOTYPE_DB' 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_INFOTYPE_DB', was |

| not caught in |

| procedure "READ" "(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: |

| Inconsistent data exists in the database for infotype 0002 A for 28000035 |

| |

----------------------------------------------------------------------------------------------------

|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_INFOTYPE_DB" |

| "CL_HRPA_INFOTYPE_CONTAINER====CP" or "CL_HRPA_INFOTYPE_CONTAINER====CM005" |

| "IF_HRPA_INFOTYPE_CONTAINER~READ" |

|

| 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 "READ" "(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..... 731 |

| SAP Basis Level. 0007 |

| |

| Application server... "r3ca5" |

| Network address...... "10.255.179.17" |

| Operating system..... "AIX" |

| Release.............. "6.1" |

| Hardware type........ "00F66B934C00" |

| Character length.... 16 Bits |

| Pointer length....... 64 Bits |

| Work process number.. 3 |

| Shortdump setting.... "full" |

| |

| Database server... "gotsvu4010.got.volvo" |

| Database type..... "ORACLE" |

| Database name..... "CA5" |

| Database user ID.. "SAPSR3" |

| |

| Terminal.......... "GNL100J5SMGT1" |

| |

| Char.set.... "C" |

| |

| SAP kernel....... 721 |

| created (date)... "Feb 28 2013 11:44:44" |

| create on........ "AIX 1 6 00CFADC14C00" |

| Database version. "OCI_112, 11.2.0.3.0, V1, default" |

| |

| Patch level. 100 |

| Patch text.. " " |

|

| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |

| SAP database version. 721 |

| Operating system..... "AIX 1 6, AIX 1 7" |

| |

| Memory consumption |

| Roll.... 0 |

| EM...... 12569376 |

| Heap.... 0 |

| Page.... 90112 |

| MM Used. 4453872 |

| MM Free. 3922816 |

----------------------------------------------------------------------------------------------------

|User and Transaction |

| Client.............. 002 |

| User................ "WDESANGH" |

| Language key........ "E" |

| Transaction......... "PA30 " |

| Transaction ID...... "523918EB76004BC0E10080000AFFB320" |

| |

| EPP Whole Context ID.... "5239182876004BC0E10080000AFFB320" |

| EPP Connection ID....... 00000000000000000000000000000000 |

| EPP Caller Counter...... 0 |

| |

| Program............. "CL_HRPA_INFOTYPE_CONTAINER====CP" |

| Screen.............. "SAPMP50A 0120" |

| Screen Line......... 12 |

| Debugger Active..... "none" |

----------------------------------------------------------------------------------------------------

|Chain of Exception Objects |

----------------------------------------------------------------------------------------------------

|Attrib. Name |Value |

----------------------------------------------------------------------------------------------------

|Level 1 Class CX_HRPA_INVALID_INFOTYPE_DB |

|Program CL_HRPA_INFOTYPE_CONTAINER====CP Include CL_HRPA_INFOTYPE_CONTAINER====CM005 Row 140 |

|Short Te Inconsistent data exists in the database for infotype 0002 A for 28000035 |

|Long Tex |

----------------------------------------------------------------------------------------------------

|INFTY |0002 |

|IS_RESUMABLE | |

|KERNEL_ERRID | |

|KEY |280000359999123119781215000 |

|MSG |&MSG:aStructure& |

|PERNR |28000035 |

|TABLE |PA3527 |

|TCLAS |A |

----------------------------------------------------------------------------------------------------

|Information on where terminated |

| Termination occurred in the ABAP program "CL_HRPA_INFOTYPE_CONTAINER====CP" - |

| in "IF_HRPA_INFOTYPE_CONTAINER~READ". |

| The main program was "SAPMP50A ". |

| |

| In the source code you have the termination point in line 140 |

| of the (Include) program "CL_HRPA_INFOTYPE_CONTAINER====CM005". |

| The termination is caused because exception "CX_HRPA_INVALID_INFOTYPE_DB" |

| occurred in |

| procedure "READ" "(METHOD)", but it was neither handled locally nor declared

| in the RAISING clause of its signature.

| |

| The procedure is in program "CL_HRPA_SAPUP50R_ADAPTER======CP "; its source

| code begins in line

| 1 of the (Include program "CL_HRPA_SAPUP50R_ADAPTER======CM004 ".

----------------------------------------------------------------------------------------------------

|Source Code Extract |

----------------------------------------------------------------------------------------------------

|Line |SourceCde |

----------------------------------------------------------------------------------------------------

| 110| ASSIGN pnnnn2_ref->* TO <pnnnn2>.

| 111| ASSIGN db_table_ref->* TO <db_nnnn2>.

| 112| ASSIGN <pnnnn2> TO <pshdr2> CASTING.

| 113|

| 114|* read data from secondary database table

| 115| SELECT SINGLE * FROM (dbname) INTO <db_nnnn2>

| 116| WHERE

| 117| pernr = <pshdr>-pernr AND

| 118| subty = <pshdr>-subty AND

| 119| objps = <pshdr>-objps AND

| 120| sprps = <pshdr>-sprps AND

| 121| endda = <pshdr>-endda AND

| 122| begda = <pshdr>-begda AND

| 123| seqnr = <pshdr>-seqnr.

| 124| IF sy-subrc IS INITIAL.

| 125| MOVE-CORRESPONDING <db_nnnn2> TO <pnnnn2>.

| 126| <pshdr2>-infty = secondary_infty.

| 127| ELSE.

| 128| IF 1 = 0.

| 129|* 049 Fehlender Sekundärsatz zu Infotyp &1 Schlüssel &3

| 130| MESSAGE ID 'PBAS_SERVICE' TYPE 'E' NUMBER '049' WITH '' '' ''.

| 131| ENDIF.

| 132| CONCATENATE <pshdr>-pernr <pshdr>-subty <pshdr>-objps <pshdr>-sprps <pshdr>-endda <p|

| 133| INTO invalid_key.

| 134| msg-msgty = 'E'.

| 135| msg-msgid = 'PBAS_SERVICE'.

| 136| msg-msgno = '049'.

| 137| msg-msgv1 = infty.

| 138| msg-msgv2 = secondary_infty.

| 139| msg-msgv3 = invalid_key.

|>>>>>| RAISE EXCEPTION TYPE cx_hrpa_invalid_infotype_db

| 141| EXPORTING

| 142| tclas = tclas

| 143| infty = infty

| 144| pernr = pernr

| 145| table = dbname

| 146| key = invalid_key

| 147| msg = msg.

| 148| ENDIF.

| 149| ENDIF.

| 150|

| 151|* read cost assignment data if necessary

| 152| CASE <pshdr>-refex.

| 153| WHEN false.

| 154| CLEAR pref.

| 155| WHEN true.

| 156| SELECT * FROM assob_hr INTO assob_hr

| 157| UP TO 1 ROWS

| 158| WHERE

| 159| pernr = <pshdr>-pernr AND

----------------------------------------------------------------------------------------------------

Former Member · ‎2013 Sep 23

Hi Gopa,

Please execute the report RPUPAV00 (Regeneration of Additional ITs for Views). This will fix the issue.

Regards

Kumarpal

gouravkumar64 · ‎2013 Sep 20

Hi,

These 3 notes or Knowledge based articles also not helpful?

Note 576290 - Termination with exception CX_HRPA_INVALID_CUSTOMIZATION

Note 1692479 - Infotype view: Exception CX_HRPA_INVALID_PARAMETER

1834536 - New secondary view 3346 in infotype 0002 causes PA20, PA30, ESS and MSS WDJ and WDA to dum...

Thanks

Gourav.

Former Member · ‎2013 Sep 23

Hi Gopa,

Please execute the report RPUPAV00 (Regeneration of Additional ITs for Views). This will fix the issue.

Regards

Kumarpal

former_member311223 · ‎2013 Sep 25

Hi Experts,

Thanks for the reply,

The issue seems to be on the configuration side.

The table settings for tables T582V and T582W were changed. However, existing data was not updated.

The Fix is to execute a report: RPUPAV00 (Regeneration of Additional ITs for Views).

Former Member · ‎2013 Dec 31

Hi Gopa,

I am experiencing a similar issue. Therefore, what 'Delimitation Date' did you use when you executed the report? Did you run it open ended or did you run it only for the PERNR in question from the short dump?

Thanks!

By Category

Related Content

Activity Groups

Industry Groups

Influence and Feedback Groups

Interest Groups

Location Groups

Customer Only Groups

Forums

Related Resources

Products

Learning and Support

About

My SAP Profile

My SAP Profile

Dump Error in Tcode:PA30/ PA20 after Version Upgrade