on 05-29-2008 11:41 AM
Hi Friends,
For the last few weeks we have been receiving the same runtime errors when I perform the daily checks
SAPBATCH - CALL_FUNCTION_CONFLICT_LENG
SAPBATCH - CALL_FUNCTION_UC_STRUCT
Please help me if any one have idea and is this something we need to be concerned about?
Best Regards,
Vinod
are you sure the programs name is "SAPBATCH"? Please post the first pages of the dump.
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for the delay in response...I'm sure that program is sap batch only..please find the first page of two dumps.
Dump(1):
*********************************
Runtime Error CALL_FUNCTION_CONFLICT_LENG
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
Date and Time 02.06.2008 04:53:15
ShrtText
Type conflict when calling a function module (field length).
What happened?
Error in ABAP application program.
The current ABAP program "/SDF/SAPLRI_SQLSERVER" had to be terminated because one of the statements could not be executed.
This is probably due to an error in the ABAP program.
A function module was called incorrectly.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator. You can use transaction ST22 (ABAP Dump Analysis) to view and administer termination messages, especially those beyond their normal deletion date.
is especially useful if you want to keep a particular message.
Dump(2) First page:
************************************
Runtime Error CALL_FUNCTION_UC_STRUCT
Except. CX_SY_DYN_CALL_ILLEGAL_TYPE
Date and Time 02.06.2008 04:53:14
ShrtText:
A type conflict occurred when structure parameters were passed in the.
What happened?
Error in ABAP application program.
The current ABAP program "/SDF/SAPLRI_SQLSERVER" had to be terminated because one of the statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator. You can use transaction ST22 (ABAP Dump Analysis) to view and administer termination messages, especially those beyond their normal deletion date.
is especially useful if you want to keep a particular message.
Please let me know if required further information.
Best Regards,
Vinod
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.