2008 May 01 9:44 PM
We recently implemented the latest support stacks for SAP ERP 4.7.
We are getting the following runtime message for transactions:
FB50, FB60, TBB1, MIRO.
We need help.
Thanks.
Runtime Error PERFORM_TOO_MANY_PARAMETERS
Exception CX_SY_DYN_CALL_PARAM_NOT_FOUND
Occurred on 04/30/2008 at 08:57:22
-
Too many parameters specified with PERFORM.
-
What happened?
-
In a subroutine call, there were more parameters than in the
routine definition.
Error in ABAP application program.
The current ABAP program "SAPLGLIN" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
-
Error analysis
-
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was neither
caught nor passed along using a RAISING clause, in the procedure "G_RWIN_CHECK"
"(FUNCTION)"
.
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
A PERFORM was used to call the routine "G_RWIN_CHECK" of the program
"SAPLGLIN".
This routine contains exactly 3 formal parameters, but the current
call contains 4 actual parameters.
parameters.
-
How to correct the error
-
The exception must either be prevented, caught within the procedure
"G_RWIN_CHECK"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Correct the PERFORM call. You can find out where the call
occurs in the section "Active calls / events".
-
"PERFORM_TOO_MANY_PARAMETERS" CX_SY_DYN_CALL_PARAM_NOT_FOUNDC
"SAPLGLIN" or "LGLINU26"
"G_RWIN_CHECK"
-
We recently implemented the latest support stacks for SAP ERP 4.7.
We are getting the following runtime message for transactions:
FB50, FB60, TBB1, MIRO.
We need help.
Thanks.
Runtime Error PERFORM_TOO_MANY_PARAMETERS
Exception CX_SY_DYN_CALL_PARAM_NOT_FOUND
Occurred on 04/30/2008 at 08:57:22
-
Too many parameters specified with PERFORM.
-
What happened?
-
In a subroutine call, there were more parameters than in the
routine definition.
Error in ABAP application program.
The current ABAP program "SAPLGLIN" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
-
Error analysis
-
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was neither
caught nor passed along using a RAISING clause, in the procedure "G_RWIN_CHECK"
"(FUNCTION)"
.
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
A PERFORM was used to call the routine "G_RWIN_CHECK" of the program
"SAPLGLIN".
This routine contains exactly 3 formal parameters, but the current
call contains 4 actual parameters.
parameters.
-
How to correct the error
-
The exception must either be prevented, caught within the procedure
"G_RWIN_CHECK"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Correct the PERFORM call. You can find out where the call
occurs in the section "Active calls / events".
-
"PERFORM_TOO_MANY_PARAMETERS" CX_SY_DYN_CALL_PARAM_NOT_FOUNDC
"SAPLGLIN" or "LGLINU26"
"G_RWIN_CHECK"
-
2008 May 01 10:08 PM
Check where this perform is called in the program of given Tcodes.
the subroutine definition.
u should either add one parameter to the form G_RWIN_CHECK.... endform
or u should remove one parameter from the perform G_RWIN_CHECK, but as they are sap provided program u cant change i hope
u can find if there is any note available to solve this probelm..
gud luck