2008 Jul 04 7:08 AM
How much maximum time we should wait when we run the bdc in the background job, whether it is success or failure?
can we record the transaction with table control data in shdb.?
when we run the bdc using session method , how can we findout whether it is successfull or not...................................................
How can we trace the runtime error in the bdc?
How the ctu_params is usefull in the bdc .........................................................................
How to overcome the table control in the bdc program?
Can we create the more than one session in the BDC?
How much maximum time we should wait when we run the bdc in the background job, whether it is success or failure?
can we record the transaction with table control data in shdb.?
when we run the bdc using session method , how can we findout whether it is successfull or not...................................................
How can we trace the runtime error in the bdc?
How the ctu_params is usefull in the bdc .........................................................................
How to overcome the table control in the bdc program?
Can we create the more than one session in the BDC?
2008 Jul 04 9:34 AM
How much maximum time we should wait when we run the bdc in the background job, whether it is success or failure?
The maximum time depends upon the number of records.If you want to show the message EXECUTED SUCCESSFULLY means u have to write coding for that.
can we record the transaction with table control data in shdb.?
Table control data is for line items.After recording while coding u have to have to use for table control.
when we run the bdc using session method , how can we findout whether it is successfull or not...................................................
After runing the BDC in session method u can see the error log .
How can we trace the runtime error in the bdc?
For tracing the runtime error u have to see the transaction st22.
Runtime Error MESSAGE_TYPE_X
Date and Time 11.01.2007 09:58:26
-
-
ShrtText
The current application triggered a termination with a short dump.
-
-
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
-
-
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.
-
-
Error analysis
Short text of error message:
Programm error: RKE_CHECK_GENERATION called recursively
Technical information about the message:
Diagnosis
A program error has occurred. Function module RKE_CHECK_GENERATION
is carried out recursively. This is not allowed.
Procedure
Contact the SAP hotline. Include a copy of the dump in your problem
message, since this is needed to analyze the problem.
Message classe...... "KE"
Number.............. 008
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Variable 3.......... " "
Variable 4.......... " "
Hope this helps you.
Reward points if helpfull.
Thanks & Regards,
Y.R.Prem Kumar
2008 Jul 04 11:09 AM
there is no big time difference between the bdc process and the normal report.
i hope it is possible to record the table control data
hi the session method we will generally process foreground if the value is wrong it will show an error..in that screen..
the ctuparameters can be passed in the submit condition...means when we will process the data from other program..
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |