Batch Session Errors Notification Program

Does SAP provide a program which will notify users if a batch session has errors? I am looking for something which would send an e-mail or something, if I gave it the session name and the users to notify.
I guess it would be some kind of Batch Session Monitor Program.
thanks

I dont think a standard program is available .
the log details you can get from apql table, build a custom program for your requirement.
Check the where used list of apql table for any Fm's available.
For getting the log refer link:[Program To Download Batch Session Log|http://www.sap-basis-abap.com/abap/program-to-download-batch-session-log-into-excel.htm]

Similar Messages

Batch session error message

hi expert,
when we run the batch sesion we met the below message
Field BSEG-LZBKZ. does not exist in the screen SAPMF05A 0332 FB01 10 SAPMF05A 0332
Transaction error the invoice didn't post to the sap . But when is checked the screen we have the value to the filed bseg-lzbkz, it's makes me confuse on this. Appreciate throw you lights on this.
thansk in advance

Hi,
Please go through TCODE SHDB , do recording of the tcode and create program from that ( by selecting the recording and clicking on PROGRAM button).
CHECK whether the ORDER of OK_CODES match with your program OK_CODES.
Thanks and regards.

Error While Processing Batch Session in Background Mode

Hi,
I am creating batch input sessions for Transaction FB01. Each Batch Session will have multiple transactions for FB01. My Batch Session is getting created. But when i am trying to process that batch session in backgroung mode ( thru SM35 ), it is failing. The Error says "Transaction Error". And when i process the same session in foreground mode, it is getting successfully processed. Any suggestion in this will be very helpful.

Hi,
Check in your program if you have properly handled the OK codes.after every transaction is complete the 'Back' button has to be triggered.That could be the reason it's working in FG mode and not BG mode.Generally,OK Code is '/EBCK'.This should work.

Error in batch session processing in background mode

Hi ,
I am trying to do data transfer using batch session for transaction FD32.
Here the batch session is executing when I am processing the session in foreground.
Whereas in background mode it is failing.
Please check and assit.
Regards
Kishore

Hi Kishore,
Probably it will be some information or warning message which is coming in the background execution of the session.
That is the reason your session is going into error. Run the errored out session once again in foreground mode. You will get to know the reason of failure.
Please let us know of any doubts.
Cheers
VJ

No batch session created for forex run error

Hello
We have run the forex run on 31st may and have included the reversal as well(1st June).This got completed sucessfully with revaluation and its reversal the first day of next month.After a week we reset the forex run,then it should reverse both the revaluation on 31st May and reversal posting on 1st June.However when the reset was run ,the period 31st may was closed which was noticed after the forex reset run was .We selected create postings with the batch session and also checked to create batch session if any errors.
During the reset ,the reversal postings on 1st June got reversed but the forex revaluation on 31st may didnt get reversed(as period was closed).But there is no batch session created.
Please let us know why the session hasnt got created or what could be the reason why batch session in SM35 is not found,if the period was closed for reversal during reset it should have created batch session.
Please advice.

Hi
If your reversal posting have been generated for 1st June, check also in SM35 if there is a batch session in error under Incorrect Tab/In Process/In Background Tab of SM35
Thanks & Regards
Sanil Bhandari

(SCM-APO ) - LiveCache error - tp error : operable program or batch file

Dear Gurus,
On one our APO systems, I cannot administer liveCache, using database connection LCA, LDA, or LEA. Using LCA as an example, with
tcode LC10> liveCache Monitoring, I get this error:
Name and Server :    QDP - ntsapsc001
DBMRFC Function : DBM_CONNECT
Error : DBM Error
Return Code : -11
Error Message : tp error: operable program or batch file
Using tcode /sapapo/om13, I get these results:
liveCache connection to LCA      (GREEN)
liveCache Stat. from LCA     ???    (RED)
liveCache Initialization          001   (RED)
Using tcode SE38> program RSLVCINIT > database connection LCA, I get this error:
Error in DBMSERVER or DBMCLI
What is wrong ?
Thanks and regards,
cjperk90

In the syslog (tcode sm21), and on the NT server's syslog,
I also get these errors:
Database error -10709 at CON
> Connection failed (RTE:database not running)
Please advise.
Thanks,
cjperk90

Batch input session ERROR

hi FRNDS
at the time of processing Batch session in T-Code SM35, i am getting following error
1.. GL Accnt <102200.EXPEN> whr as it is just supposed to be 102200, so it can run automatically, but here i have to delet .EXPEN part and process the session
which is taking lot of time.
please suggest possible answer
thanks

Hi Matthew,
You must have selected the Alternative Account Number in transaction code F.05. To resolve the error, go back to transaction code F.05, click on the tab "Other" and uncheck the field "Alternative Account Number". This should solve the problem. Then, you can regenerate your batch input and re-process.
The effect of setting this parameter is that, the G/L account number would be replaced by the alternative account number (from the company code-specific G/L account master record).
I hope the above helps.
Do not forget to award the points please.
Regards,
Jacob

How to stop the internal batch session

Hi ,
How to stop the internal batch session, which is triggered from the program.
When I execute the program, there is an batch session, which starts processing in parallel with the program, and causes an error message for the program, so the further process is affected.
I tried finding the session through the Transactions - SM35, SM37. However, I could find any session in my name.
However, when I try thro SM04, I could find an session with the same error message. But I am not able to end the session.
Pleas advise.
Thanks,
cartesian.

Go through transaction SM50. In case you have more than one application server (transaction SM51 will show) you can also use SM66 which will show all running processes on all application servers.
With SM50 you will only see the process running if it is running on the same application server you are logged on to.
Mark the process and use menu 'Program/Session - End Session' or 'Process - End with or without Core'
Hope that helps,
Michael

Please tell me the cases when I will use Call transaction/ Batch Session.

Can you please tell me when I will use Call transaction or Batch Session in the time of uploading data through BDC.
Regards,
Subhasish

Hi subhasish,
1. One of the main criteria is
2. If error handling facility is required, then batch session is the best,
otherwise if we use call transaction, then error handling code,
has to be written in the program itself.
3. Batch session provides lot of facilities to the user.
regards,
amit m.

Syntax error in program "SAPLHTTPTREE " during application of SAPKB70012

Hi everyone,
I am applying support pack SAPKB70012 when it stopped in the XPRA_EXECUTION phase. Anybody encountered this error "Syntax error in program "SAPLHTTPTREE "? Been looking for any notes on this but haven't found anything. I already created message to SAP but even though its high, nobody's picking it up. We're using Windows NT and database MSSQL.
Below is part of the import queue log:
The following details help you to analyze the problem:
 - Error in phase: XPRA_EXECUTION
 - Reason for error: TP_STEP_FAILURE
 - Return code: 0012
 - Error message: OCS Package SAPKB70012, tp step R, return code
 0012
Notes on phase XPRA_EXECUTION
The XPRAs and after-import methods are executed in this phase. This
phase can terminate due to the following reasons:
o TP_INTERFACE_FAILURE: The system was unable to call the tp
 interface.
o TP_FAILURE: The system was unable to execute the tp program. For
 more information, see the SLOG or ALOG log file.
When I check SM37, I found this ABAP runtime error:
*job: RDDEXEC
Runtime Errors SYNTAX_ERROR
Date and Time 16.01.2008 19:13:09
Short text
Syntax error in program "SAPLHTTPTREE ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSCTS_EXE_EXP" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLHTTPTREE " in include
"LHTTPTREETOP " in
line 9:
""ICFALIAS" must be a flat structure. You cannot use internal tables, s"
"trings, references, or structures as components ."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "SAPLHTTPTREE ".
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
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
The following syntax error was found in the program SAPLHTTPTREE :
""ICFALIAS" must be a flat structure. You cannot use internal tables, s"
"trings, references, or structures as components ."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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.
User and Transaction
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Transactions ID..... "0224C4DC1741F1C28D9D001A4BDB2C98"
Program............. "SAPLSCTS_EXE_EXP"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "SAPLSCTS_EXE_EXP" - in
"CALL_IMP_METHODS_IN_CLIENT".
The main program was "RDDEXECU ".
In the source code you have the termination point in line 351
of the (Include) program "LSCTS_EXE_EXPF02".
The program "SAPLSCTS_EXE_EXP" was started as a background job.
Job Name....... "RDDEXECL"
Job Initiator.. "DDIC"
Job Number..... 19130500
Source Code Extract
Line
SourceCde
321
CLEAR: sy-msgid, sy-msgty, sy-msgno.
322
323
IF ps_spec_pars-with_data_file EQ 'X'.
324
CALL FUNCTION ps_method_call-method_fb
325
EXPORTING
326
iv_tarclient = ps_client-client
327
iv_is_upgrade = pv_is_upgrade
328
iv_datafile = ps_spec_pars-data_file
329
TABLES
330
tt_e071 = lt_e071
331
tt_e071k = lt_e071k.
332
ELSEIF ps_spec_pars-with_asynch_mode EQ 'X'.
333
CALL FUNCTION ps_method_call-method_fb
334
EXPORTING
335
iv_tarclient = ps_client-client
336
iv_is_upgrade = pv_is_upgrade
337
iv_asynchronous = ps_spec_pars-asynch_mode
338
TABLES
339
tt_e071 = lt_e071
340
tt_e071k = lt_e071k.
341
ELSEIF ps_spec_pars-with_cl_results EQ 'X'.
342
CALL FUNCTION ps_method_call-method_fb
343
EXPORTING
344
iv_trkorr = pv_trkorr
345
iv_is_upgrade = pv_is_upgrade
346
it_e071 = lt_e071
347
it_e071k = lt_e071k
348
CHANGING
349
it_client = ps_spec_pars-clients.
350
ELSE.
>>>>>
CALL FUNCTION ps_method_call-method_fb
352
EXPORTING
353
iv_tarclient = ps_client-client
354
iv_is_upgrade = pv_is_upgrade
355
TABLES
356
tt_e071 = lt_e071
357
tt_e071k = lt_e071k.
358
ENDIF.
359
360
361
reset info on called method in memory.
362
CALL FUNCTION 'TRINT_RESET_STACK_KILLER'.
363
check if method call has deleted variables in global memory
364
and set those variables again
365
CALL FUNCTION 'TRINT_CHECK_VARS_IN_MEMORY'
366
IMPORTING
367
ev_ok = lv_ok.
368
IF lv_ok = ' '.
369
memory destroyed: set all clients to errornous for security
370
for methods of switch framework
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
2
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Execute Post-Import Methods and XPRAs for Transport Request
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
ASYNCH_IAC_PUBLISH
SY-MSGV2
0011
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080116
SY-UZEIT
191309
SY-XPROG
SAPLSYST
SY-XFORM
SYSTEM_HOOK_OPEN_DATASET
Active Calls/Events
No. Ty. Program Include Line
Name
5 FUNCTION SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 351
CALL_IMP_METHODS_IN_CLIENT
4 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 351
CALL_IMP_METHODS_IN_CLIENT
3 FORM SAPLSCTS_EXE_EXP LSCTS_EXE_EXPF02 87
CALL_IMP_METHODS
2 FUNCTION SAPLSCTS_EXE_EXP LSCTS_EXE_EXPU02 103
TRINT_CALL_AFTER_IMP_METHOD
1 EVENT RDDEXECU RDDEXECU 171
START-OF-SELECTION
Chosen variables
Name
Val.
No. 5 Ty. FUNCTION
Name CALL_IMP_METHODS_IN_CLIENT
GC_GNS_NO_DIFF
/0*/
2322222222
F0AF000000
0000000000
0000000000
LT_E071
Table IT_137[21x360]
FUNCTION-POOL=SCTS_EXE_EXPFORM=CALL_IMP_METHODS_IN_CLIENTDATA=LT_E071
Table reference: 46
TABH+ 0(20) = B0A6D957FE07000050C8D957FE07000000000000
TABH+ 20(20) = 2E000000890000001500000068010000FFFFFFFF
TABH+ 40(16) = 044D0000F00B000015000000C9248001
store = 0xB0A6D957FE070000
ext1 = 0x50C8D957FE070000
shmId = 0 (0x00000000)
id = 46 (0x2E000000)
label = 137 (0x89000000)
fill = 21 (0x15000000)
leng = 360 (0x68010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000049
occu = 21 (0x15000000)
access = 1 (ItAccessStandard)
idxKind = 1 (ItIndexLinear)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xF0C0E257FE070000
pgHook = 0x0000000000000000
idxPtr = 0x10A7D957FE070000
shmTabhSet = 0x0000000000000000
id = 111 (0x6F000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 21 (0x15000000)
lineAlloc = 21 (0x15000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
>>>>> 1st level extension part <<<<<
regHook = 0x90C4D957FE070000
collHook = 0x0000000000000000
ext2 = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
GC_GNS_NO_SPECIFIC
2222222222
FAF0000000
0000000000
0000000000
LT_E071K
Table[initial]
RELSET
RNO
544
2EF
000
000
PS_SPEC_PARS-WITH_CL_RESULTS
2
0
0
0
SY-XPROG
SAPLSYST
5454555522222222222222222222222222222222
310C393400000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PS_METHOD_CALL-METHOD_FB
SICF_AFTER_IMPORT
544454454554454552222222222222
3936F16452F9D0F240000000000000
000000000000000000000000000000
000000000000000000000000000000
GC_PARTNRPR_BACK_TO_STNDRD
1A&1B&1H&1I&2I&3R
34234234234234235
11612618619629632
00000000000000000
00000000000000000
PV_IS_UPGRADE
2
0
0
0
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PV_TRKORR
SAPKB70012
54544333332222222222
310B2700120000000000
00000000000000000000
00000000000000000000
SYST-REPID
SAPLSCTS_EXE_EXP
5454545554545455222222222222222222222222
310C3343F585F580000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
DEVC_PREFIXNS
N
4
E
0
0
PS_SPEC_PARS-CLIENTS
Table[initial]
%_PRINT
000 0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PS_CLIENT-CLIENT
222
000
000
000
%_DUMMY$$
2222
0000
0000
0000
No. 4 Ty. FORM
Name CALL_IMP_METHODS_IN_CLIENT
LT_E071
Table IT_137[21x360]
LT_E071K
Table[initial]
PS_SPEC_PARS-WITH_CL_RESULTS
2
0
0
0
PS_METHOD_CALL-METHOD_FB
SICF_AFTER_IMPORT
544454454554454552222222222222
3936F16452F9D0F240000000000000
000000000000000000000000000000
000000000000000000000000000000
PV_IS_UPGRADE
2
0
0
0
PV_TRKORR
SAPKB70012
54544333332222222222
310B2700120000000000
00000000000000000000
00000000000000000000
PS_SPEC_PARS-CLIENTS
Table[initial]
PS_CLIENT-CLIENT
222
000
000
000
No. 3 Ty. FORM
Name CALL_IMP_METHODS
PV_TRKORR
SAPKB70012
54544333332222222222
310B2700120000000000
00000000000000000000
00000000000000000000
PV_NO_WORK_FOUND
2
0
0
0
PT_CLIENT
Table IT_21[1x8]
PROGRAM=RDDEXECUDATA=GT_CLIENT
Table reference: 16
TABH+ 0(20) = B0311757FE070000000000000000000000000000
TABH+ 20(20) = 10000000150000000100000008000000FFFFFFFF
TABH+ 40(16) = 040000009008000010000000C1248001
store = 0xB0311757FE070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 16 (0x10000000)
label = 21 (0x15000000)
fill = 1 (0x01000000)
leng = 8 (0x08000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000031
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x10311757FE070000
pgHook = 0x0000000000000000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 20 (0x14000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x10000000)
lineAlloc = 16 (0x10000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
collHook = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
LS_CLIENT_H
2222
0000
0000
0000
TTRA
T
5
4
0
0
SY
######################################f#######################################T######### ####
0000000000000000000000000000000000000060000000000000000000000000000000000000105000000080220000
0000104000000000000010201000100000000060000000000000000000000000000000000000604000000000000300
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000070000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
PV_UPDATE_LOCKFLAG
X
5
8
0
0
PV_CTC
2
0
0
0
PV_STATLOG_FILE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PS_METHOD_CALL
AFTER_IMP SICF_AFTER_IMPORT ###Á#>#À#?###@#
44545544525444544545544545522222222222222000C030C0309040
16452F9D003936F16452F9D0F240000000000000000010E000F0F000
00000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000
PV_IS_UPGRADE
2
0
0
0
PV_TOP_LEVEL
2
3
2
0
0
PS_SPEC_PARS
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PS_METHOD_CALL-CLIDEP
2
0
0
0
PS_SPEC_PARS-WITH_CL_RESULTS
2
0
0
0
%_VIASELSCR
0
4
No. 2 Ty. FUNCTION
Name TRINT_CALL_AFTER_IMP_METHOD
IS_E070
SAPKB70012 DRSAP SYSTSAPUSER 20080116185743
5454433333222222222245545222222255555455545222223333333333333322222222222222222222
310B270012000000000042310000000039343105352000002008011618574300000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
IT_E071
Table IT_15[23207x360]
PROGRAM=RDDEXECUDATA=E071_TAB[]
Table reference: 10
TABH+ 0(20) = C0841857FE070000B0611757FE07000000000000
TABH+ 20(20) = 0A0000000F000000A75A000068010000FFFFFFFF
TABH+ 40(16) = 04000000C005000010000000C1248001
store = 0xC0841857FE070000
ext1 = 0xB0611757FE070000
shmId = 0 (0x00000000)
id = 10 (0x0A000000)
label = 15 (0x0F000000)
fill = 23207 (0xA75A0000)
leng = 360 (0x68010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000016
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x206E1857FE070000
pgHook = 0x30047F57FE070000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 14 (0x0E000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 32752 (0xF07F0000)
lineAlloc = 23216 (0xB05A0000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
collHook = 0x0000000000000000
ext2 = 0x40611757FE070000
>>>>> 2nd level extension part <<<<<
tabhBack = 0xD0C31F57FE070000
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
IT_E071K
Table IT_16[6045x564]
PROGRAM=RDDEXECUDATA=E071K_TAB[]
Table reference: 11
TABH+ 0(20) = 20851857FE070000F0611757FE07000000000000
TABH+ 20(20) = 0B000000100000009D17000034020000FFFFFFFF
TABH+ 40(16) = 040000005006000010000000C1248001
store = 0x20851857FE070000
ext1 = 0xF0611757FE070000
shmId = 0 (0x00000000)
id = 11 (0x0B000000)
label = 16 (0x10000000)
fill = 6045 (0x9D170000)
leng = 564 (0x34020000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000019
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x00C49357FE070000
pgHook = 0x60E75357FE070000
idxPtr = 0x0000000000000000
shmTabhSet = 0x0000000000000000
id = 15 (0x0F000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 8192 (0x00200000)
lineAlloc = 6048 (0xA0170000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
collHook = 0x0000000000000000
ext2 = 0xE06F1757FE070000
>>>>> 2nd level extension part <<<<<
tabhBack = 0x806F1757FE070000
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x0000000000000000
pb_handle = 0x0000000000000000
IV_CTC
2
0
0
0
IV_DATNAME
:D:T:S:data:F:IB70012.SAP
3435353667634344333332545222222222222222222222222222222222222222222222222222222222222222222222
A4A4A3A4141A6A9270012E310000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IV_SFW_CALL
2
0
0
0
IV_STATLOG_FILE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IV_TRKORR
SAPKB70012
54544333332222222222
310B2700120000000000
00000000000000000000
00000000000000000000
IV_UPDATE_LOCKFLAG
X
5
8
0
0
IT_CLIENT
Table IT_21[1x8]
LS_SPEC_PARS-NOT_DURING_UPGRADE
2
0
0
0
ALLSTAT
RNODL
54444222222222222222222222
2EF4C000000000000000000000
00000000000000000000000000
00000000000000000000000000
LV_UPGRADE_IS_RUNNING
2
0
0
0
TMVD
E
4
5
0
0
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
<LS_METHOD_CALL>
AFTER_IMP SICF_AFTER_IMPORT ###Á#>#À#?###@#
44545544525444544545544545522222222222222000C030C0309040
16452F9D003936F16452F9D0F240000000000000000010E000F0F000
00000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000
LV_IS_UPGRADE
2
0
0
0
LV_TOP_LEVEL
2
3
2
0
0
LV_NO_WORK_FOUND
2
0
0
0
LS_SPEC_PARS
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
0
0
No. 1 Ty. EVENT
Name START-OF-SELECTION
SCREEN
%_17NNS0000691660_%_%_%_%_%_%_
2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F17EE30000691660F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST
######################################f#######################################T######### ####
0000000000000000000000000000000000000060000000000000000000000000000000000000105000000080220000
0000104000000000000010201000100000000060000000000000000000000000000000000000604000000000000300
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000070000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
GT_CLIENT
Table IT_21[1x8]
GS_CLIENT
2222
0000
0000
0000
DATNAME
:D:T:S:data:F:IB70012.SAP
3435353667634344333332545222222222222222222222222222222222222222222222222222222222222222222222
A4A4A3A4141A6A9270012E310000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DATNAME_%_APP_%
Data File Name (from TRBAT)
467624666246662267662554452222
4141069C50E1D50862FD0422149000
000000000000000000000000000000
000000000000000000000000000000
E071_TAB[]
Table IT_15[23207x360]
E071K_TAB[]
Table IT_16[6045x564]
SY-SUBRC
0
0000
0000
GV_CTC
2
0
0
0
GV_TRBAT_DATNAME
:D:T:S:data:F:IB70012.SAP
3435353667634344333332545222222222222222222222222222222222222222222222222222222222222222222222
A4A4A3A4141A6A9270012E310000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
<%_TABLE_E071>
<%_TABLE_E071K>
GV_STATLOG_FILE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
COMFILE
SAPKB70012
54544333332222222222
310B2700120000000000
00000000000000000000
00000000000000000000
SY-LANGU
E
4
5
0
0
SY
######################################f#######################################T######### ####
0000000000000000000000000000000000000060000000000000000000000000000000000000105000000080220000
0000104000000000000010201000100000000060000000000000000000000000000000000000604000000000000300
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000070000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
SPACE
2
0
0
0
Internal notes
The termination was triggered in function "ab_genprog"
of the SAP kernel, in line 1476 of the module
"//bas/700_REL/src/krn/runt/abgen.c#5".
The internal operation just processed is "FUNC".

Good Morning
Did you ever get this working without restoring ?
Kind Regards
Marius

Short dump error in program SAPMV50A after modification

Dear gurus
i have done some modification in vl02n through Badi and it is working fine in Development server.
when i transport it to quality server and test it
it giving a short dump in vl02n while vl01n is working perfectly fine and showing my modification too..
below is the error mentioned
Database error text........: "Unsupported database type in parameter/column
    (168)."
   Internal call code.........: "[RSQL/READ/LIKP ]"
   Please check the entries in the system log (Transaction SM21).
   If the error occures in a non-modified SAP program, you may be able t
   find an interim solution in an SAP Note.
   If you have access to SAP Notes, carry out a search with the followin
   keywords:
   "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
   "SAPMV50A" or "MV50AFDB"
   "LIKP_SELECT"
   If you cannot solve the problem yourself and want to send an error
   notification to SAP, include the following information:
Please help
Regards
Saad Nisar

i have created two append structure in standard tables of LIKP & LIPS which are activated and so as LIKP and LIPS
my Badi is also activated and my customized program is also activated.
While making outbound delivery in Quality server it works fine but when i want to make changes in that created delivery it throws dump error
short text
   SQL error in the database when accessing a table.
issing RAISING Clause in Interface
   Program                                 SAPMV50A
   Include                                 MV50AFDB
   Row                                     14
   Module type                             (FORM)
   Module Name                             LIKP_SELECT
rigger Location of Exception
   Program                                 SAPMV50A
   Include                                 MV50AFDB
   Row                                     20
   Module type                             (FORM)
   Module Name                             LIKP_SELECT

Urgent help required : Batch processing error of an inbound idoc

hi,
i have a problem while posting an idoc to the GL(FB01).
i'm using an Inbound idoc message type : ACC_GL_POSTING
idoc type : ACC_GL_POSTING01.
Process code : BAPI.
In the transaction code OBA7 i have enabled a particular document type as BATCH INPUT ONLY.
i have set the option " Trigger by background program" in the partner profile (we20).
while testing the process i'm getting the error "Document type -- is only defined for batch input".
how can i overcome this error? can idocs be used to post for transaction that are batch enabled . plz help me.
with regards.
T.Jeyagopi.

Jeyagopi,
There are different types of Data loading into SAP.
BATCH INPUT / BDC / IDOC / BAPI etc. BATCH INPUT are standard programs that take the data and update SAP. I don't think that is same as batch processing of IDOC.
You might want to remove the setting of batch input, retain the batch processing in WE20 and try it out.
In my opinion it should work.
Regards,
Ravi
Note : Please reward points for the posts that help you.

With the new seession in IE gives session error for new user

Hi,
In new opened IE if i tries to login with new user. It is switching b/w the files in the status bar(ie., Header1.jsp and ListServicecall.jsp simultaneously) and at end the session error result will arise.
But for the second time if i login with the same username/password the page is displaying properly. please Can any one help out.
Thanks,
Satish R

First time if the user logins to IE in the HP Service Desk(SD) page. Some of the pages will iteratively loops and give a session expires error. After that the user logins to the page with no error.
If i create a new copy of the data from the existing folder and if i try to run then the result will be error for that folder also.
ie., Assume folder 123 where, first time for every new login user the session expire error occurs. later they'll login without any problem.
If i rename the folder 123 to xyz/create new copy and rename then, the same problem repeats. First time for the new user it will give session expire error and later he can login to the HPSD page with no error.
Is it require cookies to be programmed in that program.
Regards,
Satish R

How to send the Error notification

Hi,
Hi,
I am having the one scenario like , i send the one record to destination using outbound that time i stored in one table sent time and date and they are send the ACK to me that time i update the table with receiving time and date using inbound program but now this enhancement is to check the receiving time and sent time if it more than 5 hrs i need to send the Error notification this process is doing every 15minst in background mode please suggest in this issue.
Thanks,
Harinath

Hey
please have a look at the following
How to trigger alert in XI from a connected SAP R/3 4.7 system
Thanx
Aamir

How to read the messages from the processed Batch session log

Hi All,
I am posting an accounting document through FB01 by submitting the report RFBIBL00 along with the file through which a Batch session gets generated in SM35.The Batch session is then processed by submitting the report RSBDCSUB. My code is as shown below:
SUBMIT rfbibl00 WITH ds_name = co_file_output
                  WITH callmode = co_batch AND RETURN.
Process Batch session
SUBMIT rsbdcsub
    WITH mappe = gv_name_jd
    WITH von   = sy-datlo
    WITH bis   = sy-datlo
     AND RETURN
My requirement is to capture the document number from the log of the processed batch session. Can anyone suggest me how to go about this.
Thanks in Advance,
Vinay B

Hi,
check the routine read_bdc_log_plain in program rsbdc_protocol.
get the data from table APQL and then use the logic.
        bapiret2-id = logtable-logmessage+74(16).
        bapiret2-number = logtable-logmessage+94(3).
        bapiret2-message_v1 = logtable-logmessage+100(20).
        CALL FUNCTION 'BAPI_MESSAGE_GETDETAIL'
          EXPORTING
            id         = bapiret2-id
            number     = bapiret2-number
            textformat = 'ASC'
            message_v1 = bapiret2-message_v1
          IMPORTING
            message    = bapiret2-message.
        WRITE: (60) bapiret2-message.
Edited by: Keshav.T on Apr 7, 2010 4:23 PM

Batch Session Errors Notification Program

Similar Messages

Maybe you are looking for