SAP Knowledge Base Article - Preview

3129979 - PCC Sorry, a technical error occurred! MESSAGE_TYPE_X /BOBF/CX_FRW_FATAL============CP BO PYC_POLICY_MAINT_REQ

Symptom

  • You run Payroll Control Center / Payroll Control Centre
  • You are running Policy Configuration
  • You are adding a policy: 
  • Sorry, a technical error occurred! Please try again later. 

    \{
    "message": "HTTP request failed",
    "headers": [],
    "statusCode": 500,
    "statusText": "Internal Server Error",
    "responseText": "MESSAGE_TYPE_XRuntime Error: 'MESSAGE_TYPE_X'. The OData request processing has been abnormal terminated. If \"Runtime Error\" is not initial, launch transaction ST22 for details and analysis. Otherwise, launch transaction SM21 for system log analysis."
    }

  • A Dump is raised at the same time in the back end system as follows:

Category ABAP programming error
Runtime Errors MESSAGE_TYPE_X
ABAP Program /BOBF/CX_FRW_FATAL============CP
Application Component BC-ESI-BOF

Error analysis
Short text of the error message:
Internal application error of BO PYC_POLICY_MAINT_REQ of component PY-XX
-PYP; see application info
Long text of the error message:
Technical information about the message:
Message class....... /BOBF/FRW
Number.............. 013
Variable 1.......... PYC_POLICY_MAINT_REQ
Variable 2.......... PY-XX-PYP

"MESSAGE_TYPE_X"
"/BOBF/CX_FRW_FATAL============CP" bzw. /BOBF/CX_FRW_FATAL============CM005
"MESSAGE_TYPE_X"
If you cannot solve the problem yourself, please send the following
information to SAP:

Information on where terminated
The termination occurred in ABAP program or include
"/BOBF/CX_FRW_FATAL============CP", in "MESSAGE_TYPE_X". The
main program was "SAPMHTTP".

In the source code, the termination point is in line 27 of program or
include "/BOBF/CX_FRW_FATAL============CM005".

Line SourceCde

1 METHOD message_type_x.
2 "Check if we are within an AUnit test execution. In that case, gracefully
3 "abort the test class, but do not dump. Thus, it is easier to locate the
4 "test triggering the failure.
5 DATA lt_callstack TYPE abap_callstack.
6 DATA ls_callstack_entry TYPE abap_callstack_line ##needed.
7 DATA lv_error_detail TYPE string.
8
9 CALL FUNCTION 'SYSTEM_CALLSTACK' IMPORTING callstack = lt_callstack.
10 LOOP AT lt_callstack INTO ls_callstack_entry WHERE mainprogram CP 'CL_AUNIT_TEST_CLASS*'
11 IF application_information IS NOT INITIAL.
12 lv_error_detail = application_information.
13 ELSEIF previous IS BOUND.
14 DATA(lo_previous) = previous.
15 WHILE lo_previous->previous IS BOUND.
16 lo_previous = lo_previous->previous.
17 ENDWHILE.
18 lv_error_detail = lo_previous->get_text( ).
19 ENDIF.
20 cl_abap_unit_assert=>fail( level = if_aunit_constants=>fatal
21 quit = if_aunit_constants=>class
22 msg = get_text( )
23 detail = lv_error_detail ).
24 ENDLOOP.
25
26 "if we reach this point, we are NOT called from a unit test
>>>>> MESSAGE me TYPE 'X'.
28 ENDMETHOD.

Environment

  • Human Capital Management (HCM)
  • SAP enhancement package for SAP ERP
  • SAP enhancement package for SAP ERP, version for SAP HANA


Read more...

Product

SAP ERP 6.0 ; SAP ERP Central Component 6.0 ; SAP SuccessFactors HXM Core 2005 ; SAP enhancement package 8 for SAP ERP 6.0 ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

Keywords

/IWFND/CM_CONSUMER/101 "No authorization to access" "payroll control center" , KBA , PY-XX-PYP , Payroll Control Center , PY-XX , Payroll: General Parts , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.