Hi
Fund Management - Issues
The configurations of Fund Management have been completed in test system. When we allocate the Budget through transaction code FMBCC, the budgets have been allocated to whole year and no issues. All the related Budget Report - FMRP_RW_BUDGET is populated the current year budgets against Fund /commitment items. When we try to consume the budget through transaction FB60, we will not be able to post the document. Got the following error
Program "RFMATGRNEP9000001 " not found
Category ABAP Programming Error
Runtime Errors LOAD_PROGRAM_NOT_FOUND
Except. CX_SY_PROGRAM_NOT_FOUND
ABAP Program SAPLABADR
Application Component CA-GTF
Date and Time 17.07.2013 10:56:32
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Short text
| Program "RFMATGRNEP9000001 " not found.
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|What happened?
| There are several possibilities:
|
| Error in the ABAP Application Program
|
| The current ABAP program "SAPLABADR" had to be terminated because it has
| come across a statement that unfortunately cannot be executed.
| or
| Error in the SAP kernel.
|
| The current ABAP "SAPLABADR" program had to be terminated because the
| ABAP processor detected an internal system error.
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|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_SY_PROGRAM_NOT_FOUND', was not
| caught in
| procedure "STEP--METHOD_DRULE" "(FORM)", 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:
| On account of a branch in the program
| (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
| or a transaction call, another ABAP/4 program
| is to be loaded, namely "RFMATGRNEP9000001 ".
|
| However, program "RFMATGRNEP9000001 " does not exist in the library.
|
| Possible reasons:
| a) Wrong program name specified in an external PERFORM or
| SUBMIT or, when defining a new transaction, a new
| dialog module or a new function module.
| b) Transport error
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|How to correct the error
| Check the last transports to the R/3 System.
|
| Are changes currently being made to the program "SAPLABADR"?
|
| Has the correct program been entered in table TSTC for Transaction "FB60 "?
| -
|
|
| 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:
|
| "LOAD_PROGRAM_NOT_FOUND" "CX_SY_PROGRAM_NOT_FOUND"
| "SAPLABADR" or "LABADRF01"
| "STEP--METHOD_DRULE"
|
| 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
| "STEP--METHOD_DRULE" "(FORM)", 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. 0010
|
| Application server... "hoerp06ides"
| Network address...... "172.16.0.36"
| Operating system..... "Windows NT"
| Release.............. "5.2"
| Hardware type........ "4x AMD64 Level"
| Character length.... 16 Bits
| Pointer length....... 64 Bits
| Work process number.. 16
| Shortdump setting.... "full"
|
| Database server... "HOERP06IDES"
| Database type..... "ORACLE"
| Database name..... "NEI"
| Database user ID.. "SAPSR3" |
| Terminal.......... "Dev-03"
|
| Char.set.... "C"
|
| SAP kernel....... 720
| created (date)... "Jul 8 2012 23:15:28"
| create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
| Database version. "OCI_10201_SHARE, 10.2.0.2.0 "
|
| Patch level. 300
| Patch text.. " "
|
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
| SAP database version. 720
| Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
| NT 6.0, Windows NT 6.1, Windows NT 6.2"
|
| Memory consumption
| Roll.... 0
| EM...... 20948960
| Heap.... 0
| Page.... 2605056
| MM Used. 14905600
| MM Free. 1850224
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|User and Transaction
| Client.............. 900
| User................ "NATIBR"
| Language key........ "E"
| Transaction......... "FB60 "
| Transaction ID...... "89B5EEE284BAF1A88E3500215A45D1C4"
|
| EPP Whole Context ID.... "00215A45D1C41ED2BBD607E08F008E35"
| EPP Connection ID....... 00000000000000000000000000000000
| EPP Caller Counter...... 0
|
| Program............. "SAPLABADR"
| Screen.............. "SAPMF05A 0300"
| Screen Line......... 98
| Debugger Active..... "none"
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Information on where terminated
| Termination occurred in the ABAP program "SAPLABADR" - in "STEP--METHOD_DRULE".
| The main program was "SAPMF05A ".
|
| In the source code you have the termination point in line 1062
| of the (Include) program "LABADRF01".
| The termination is caused because exception "CX_SY_PROGRAM_NOT_FOUND" occurred
| in |
| procedure "STEP--METHOD_DRULE" "(FORM)", but it was neither handled locally nor
| declared in the RAISING clause of its signature.
| |
| The procedure is in program "SAPLABADR "; its source code begins in line
| 941 of the (Include program "LABADRF01 ".
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Source Code Extract (Source code has changed)
----------------------------------------------------------------------------------------------------
|Line |SourceCde
----------------------------------------------------------------------------------------------------
| 1032| e_failed valid_from
| 1033| <value1> <value2> <value3> <value4> <value5> <value6>
| 1034| l_temp
| 1035| delflag
| 1036| request_handled.
| 1037| ELSE.
| 1038| PERFORM exit--entry_from_table
| 1039| IN PROGRAM (<strategy>-callback_report)
| 1040| IF FOUND
| 1041| USING x_step-param_1 "name of the table
| 1042| global-call-date
| 1043| <source1> <source2> <source3> <source4> <source5> <source6>
| 1044| <version>
| 1045| CHANGING
| 1046| e_failed valid_from
| 1047| <value1> <value2> <value3> <value4> <value5> <value6>
| 1048| <guid>
| 1049| delflag
| 1050| request_handled.
| 1051| ENDIF.
| 1052|
| 1053| IF request_handled IS INITIAL.
| 1054|
| 1055| IF <strategy>-uses_guid_version IS INITIAL.
| 1056| PERFORM get_entry_from_table IN PROGRAM (x_step-param_2)
| 1057| USING global-call-date
| 1058| <source1> <source2> <source3> <source4> <source5> <source6>
| 1059| e_failed
| 1060| <value1> <value2> <value3> <value4> <value5> <value6>
| 1061| delflag.
|>>>>>| ELSE.
| 1063|* version and guid are used by strategy -> further params for generated
| 1064|* routines. guid is only used for reference purposes and not returned at
| 1065|* the moment
| 1066| PERFORM get_entry_from_table IN PROGRAM (x_step-param_2)
| 1067| USING global-call-date
| 1068| <source1> <source2> <source3> <source4> <source5> <source6>
| 1069| <version>
| 1070| CHANGING
| 1071| e_failed valid_from
| 1072| <value1> <value2> <value3> <value4> <value5> <value6>
| 1073| <guid>
| 1074| delflag.
| 1075|
| 1076|* the call-back should be notified, if any entry has been read
| 1077| IF delflag IS INITIAL AND
| 1078| e_failed IS INITIAL.
| 1079|
| 1080| PERFORM exit--entry--read
| 1081| IN PROGRAM (<strategy>-callback_report)
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
|Active Calls/Events
----------------------------------------------------------------------------------------------------
|No. Ty. Program Include Line
| Name
----------------------------------------------------------------------------------------------------
| 24 FORM SAPLABADR LABADRF01 1062
| STEP--METHOD_DRULE
| 23 FORM SAPLABADR LABADRF01 340
| STEP--PROCESS
| 22 FORM SAPLABADR LABADRF01 132
| STRATEGY--STEP--PROCESS
| 21 FORM SAPLABADR LABADRF01 44
| STRATEGY--PROCESS
| 20 FUNCTION SAPLABADR LABADRU03 150
| ABADR_DERIVE_CHARACTERISTICS
| 19 FUNCTION SAPLFMAVC_DERI_TOOLS LFMAVC_DERI_TOOLSU12 100
| FMAVC_DERI_ACTGRP_FMUPDATE |
| 18 METHOD CL_FMAVC_ENTRY================CP CL_FMAVC_ENTRY================CM006 4
| CL_FMAVC_ENTRY=>ACTIVITY_GROUP_GET_FOR_UPD
| 17 METHOD CL_FMAVC_ENTRY================CP CL_FMAVC_ENTRY================CM004 156
| CL_FMAVC_ENTRY=>IF_FMAVC_ENTRY~COLLECT_UPD
| 16 METHOD CL_IM_FMAVC_DECO_ISPS=========CP CL_IM_FMAVC_DECO_ISPS=========CM001 462
| CL_IM_FMAVC_DECO_ISPS=>IF_EX_FMAVC_DECO~CHECK_FUNDS_FM
| 15 METHOD CL_EX_FMAVC_DECO==============CP CL_EX_FMAVC_DECO==============CM001 159
| CL_EX_FMAVC_DECO=>IF_EX_FMAVC_DECO~CHECK_FUNDS_FM
| 14 FUNCTION SAPLBPFC LBPFCU16 87
| BP_CHECK_FUNDS_FM
| 13 FUNCTION SAPLFMFC LFMFCU01 93
| FM_FUNDS_CHECK
| 12 FUNCTION SAPLFMFC LFMFCU02 57
| FM_FUNDS_CHECK_FI
| 11 FORM SAPLFMRI LFMRIF0S 29
| CHECK_AVAIL
| 10 FUNCTION SAPLFMRI LFMRIU03 143
| FM_DOCUMENT_CLOSE
| 9 FORM SAPLFACG LFACGU03 356
| PROCESS_TCOMP
| 8 FORM SAPLFACG LFACGU03 196
| PROCESS_PROJECT
| 7 FUNCTION SAPLFACG LFACGU03 43
| FI_DOCUMENT_PROCESS
| 6 FORM SAPMF05A MF05AFF0_FCODE_BEARBEITUNG 1186
| FCODE_BEARBEITUNG
| 5 FORM SAPMF05A MF05AFF0_FUSSZEILE_VERARBEITEN 149
| FUSSZEILE_VERARBEITEN
| 4 FORM SAPMF05A MF05AFF0_FCODE_BEARBEITUNG 174
| FCODE_BEARBEITUNG
| 3 FORM SAPMF05A MF05AFF0_FCODE_BEARBEITUNG 3371
| FCODE_BEARBEITUNG
| 2 FORM SAPMF05A MF05AFF0_FUSSZEILE_VERARBEITEN 14
| FUSSZEILE_VERARBEITEN
| 1 MODULE (PAI) SAPMF05A MF05AI00_FUSSZEILE_BEARBEITEN 46
| FUSSZEILE_BEARBEITEN
----------------------------------------------------------------------------------------------------
Finallay we are not able toexecute FB60 nor PO om the test system. Not sure what exactly causes this issue. Your help would highly appreciated on this issue
Thanks & Regards
IBrahim N