Deleting SAP System in STMS
Hi there,
I want to delete a SAP system in TMS but Im unable to do so because the Delete Option is disabled. My navigation is as follows: STMS -> Overview -> Systems -> < choose the system I want to delete> -> SAP Systems -> Delete. I thought that Im in a Display Mode but I cant find any Display/Change Button here. Has anybody encountered this one? Im logged on as SAP* in client 000.
Thanks in advance
Hi Sohel,
Thank you for the response. Anyway, I did it by doing the following:
1. Log on to this SAP System.
2. Enter Transaction STMS.
3. Choose Overview Systems. The system overview appears.
4. Choose Extras Delete TMS configuration.
Thank you very much. This problem is solved now
Similar Messages
-
How to delete the list of employee on SAP system?
Dear all,
I want to delete the list of employee on my SAp system but I don't know how to do this, What's the transaction code that use to delete mutil employee on SAp system?
Please help me to do this.
Thanks and Best Regards,
Huyen NguyenPU00 is the tocde for Single PERNR
and check RPUDELPN report for mass deletion of PERNR
but dont do in production system
Edited by: Sikindar on Aug 14, 2009 8:18 AM -
Unable to change the data source of SAP system
Dear all,
We have install SAP netweaver EHP1 standalone java on oracle 10.2.0.5 on windows 2008 R2.
while installation i have given the central SLD system as solman,
By mistake i have deleted the system from SMSY.. now when i createed the system manually i am unable to change the data resource as SLD due to this i can start my SMD configuration
Request please let me know how to resolve this issue.
Thanks
PareshHi Paresh,
You can proceed with deleting your SAP system from SMSY (along with connected technical content such as AS Java definition) and the run the LANDSCAPE FETCH through transaction SMSY_SETUP to have the correct definition of your SAP system in SMSY.
Following this, you could use the addon Landscape Verification (a new thing I learnt today!!!) to check the correctness of transaction SMSY. The following link details the Landscape verification 1.0 for SolMan:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e093b3ce-c034-2d10-01bc-b51f1691d3da?quicklink=index&overridelayout=true
Hope this helps sort out your issue. -
Resoring prodution database into new installed sap system
have installed ecc 6.0 with sql server 2008 (sp 1) on windows 2003
server with 64 bit.
My installtion was done sussfully and also i started sap system.It
was working fine. then i took backup from my standalone system .
I restored prodution server database in standalone system and restore
was done successfully.
Then iam trying to login to sap system then it was saying that
dispature was stopped.
first dispatur was in yellow and status running message server
connection ok,dialuge que time 0;00sec,j2ee status info unavailable.
Iam sending screen shots and also related error log files attatched.
Please can you get help from those documents.
I also checked r3trans -d.
C:\Documents and Settings\Administrator>r3trans -d
This is r3trans version 6.14 (release 700 - 12.06.09 - 15:20:00).
unicode enabled version
2EETW169 no connect possible: "DBMS = MSS --- SERER = 'SHURJO' DBNAME = 'PRD'"
r3trans finished (0012).
before doing prodution database restore is compulsary to i have to increase the patch levels of my new installed system
because my prodution server abap& basis patch levels are 19 and my installed system it is only 14.
Please can any body give right way to resolve this problem,
Regards,
Krishna> before doing prodution database restore is compulsary to i have to increase the patch levels of my new installed system
> because my prodution server abap& basis patch levels are 19 and my installed system it is only 14.
First: It's pointless to first install a full system and then try to overwrite the database with another one.
I would INSTALL the system using the database copy.
This procedure is call "homogeneous system copy" and there's a guide for that available at http://service.sap.com/instguides and also in "Note 151603 - Copying an SQL Server database".
The error message is coming because the database has not the proper users, you'd need to run the STM tool to adapt the users and the environment. Those steps are all described in detail in the guide.
Markus -
Dear all,
Our DB Instance always run very slowly and update process
responding time is very long during month end.
I think this maybe due to it runs the database and application.
So I want to delete the DB Instance from Logon Group, and then users
will just access other else three Dialog Instances, is it Ok or what
impact will have ?
How to check PI system connected to SAP ECC Logon Group's IP , but not only
connected to the DB Instance ?
Users always need run many Background Jobs at the day,but I heard other
company almost only allow users run Background Jobs at the night.
Generally, how many background jobs running on one Instance is normal?
Do we have any good ways to control or limit users' background job
setting at the day ?
The dialog and update process numbers of DB Instance are respectively 80 and 6(Update & Update2) , other Dialog Instance is 50:4(Batch:Update)
How is the general ratio between dialog and update process numbers ?
what's the difference between update and update2 process ?
Thanks,
MichaelHi Michael,
Your company basis team searching why SAP system run slowly.
But don't have your company basis team check your system transactions.
ST01 - Operating system monitor
ST02 - Tune Summary
ST04 - SQL Server performance analysis
SM21 - System Log
SM50 - Process Overview
SM13 - Update Requests.
SM12 - Lock Entries
Maybe long time background working process see u overview tcode SM50 and SM12 kill procees after system speed normaly.
Regards.
Cem ATES -
Problem in SAP system after ECC 6.0 installation
Hi SAP Gurus,
I have been installing ECC 6.0 with database as ORACLE on Sun Solaris SPARC 64-bit.
I m currently stuck at the phase 27,when the SAP instance is started.
My SAP system is not coming up.
I have checked all profiles with sappfpar pf=<profile> check and none of them are giving errors.they are giving only warnings.
I am hereby pasting the dev_ms,dev_disp & dev_w0 files:
dev_ms:
trc file: "dev_ms", trc level: 1, release: "700"
[Thr 1] Wed Oct 22 14:28:09 2008
[Thr 1] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid 370 (Solaris on SPARCV9 CPU)
relno 7000
patchlevel 0
patchno 110
intno 20050900
make: multithreaded, Unicode, 64 bit, optimized
pid 19059
[Thr 1] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 19059) [msxxserv_mt. 1824]
[Thr 1] SigISetDefaultAction : default handling for signal 18
[Thr 1] load acl file = /usr/sap/DBM/SYS/global/ms_acl_info
[Thr 1] MsGetOwnIpAddr: my host addresses are :
[Thr 1] 1 : [10.48.152.173] gmsc2 (HOSTNAME)
[Thr 1] 2 : [127.0.0.1] localhost (LOCALHOST)
[Thr 1] MsHttpInit: full qualified hostname = gmsc2.in.capgemini.com
[Thr 1] HTTP logging is switch off
[Thr 1] set HTTP state to LISTEN
[Thr 1] MsHttpOwnDomain: own domain[1] = in.capgemini.com
[Thr 1] ms/icf_info_server : deleted
[Thr 1] *** I listen to port sapmsDBM (3600) ***
[Thr 1] *** I listen to internal port 3900 (3900) ***
[Thr 1] *** HTTP port 8100 state LISTEN ***
[Thr 1] CUSTOMER KEY: >T1454016479<
[Thr 1] Wed Oct 22 14:28:49 2008
[Thr 1] *** ERROR => MsSClientHandle: no server provides service ENQ (4), requested from gmsc2_DBM_00 [msxxserv_mt. 4669]
[Thr 1] Wed Oct 22 14:39:02 2008
[Thr 1] *** ERROR => MsSCheckConnections: no response from client C1 (127.0.0.1) after 300 secs received [msxxserv_mt. 3158]
[Thr 1] *** ERROR => MsSCheckConnections: disconnect now [127.0.0.1] [msxxserv_mt. 3162]
dev_disp:
trc file: "dev_disp.new", trc level: 1, release: "700"
sysno 00
sid DBM
systemid 370 (Solaris on SPARCV9 CPU)
relno 7000
patchlevel 0
patchno 111
intno 20050900
make: single threaded, Unicode, 64 bit, optimized
pid 19060
Wed Oct 22 14:28:11 2008
kernel runs with dp version 229000(ext=109000) (@(#) DPLIB-INT-VERSION-229000-UC)
length of sys_adm_ext is 576 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 19060) [dpxxdisp.c 1239]
shared lib "dw_xml.so" version 111 successfully loaded
shared lib "dw_xtc.so" version 111 successfully loaded
shared lib "dw_stl.so" version 111 successfully loaded
shared lib "dw_gui.so" version 111 successfully loaded
shared lib "dw_mdm.so" version 111 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >gmsc2_DBM_00 <
DpShMCreate: sizeof(wp_adm) 19344 (1488)
DpShMCreate: sizeof(tm_adm) 5710008 (28408)
DpShMCreate: sizeof(wp_ca_adm) 31200 (104)
DpShMCreate: sizeof(appc_ca_adm) 10400 (104)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/548056/548064
DpShMCreate: sizeof(comm_adm) 548064 (1088)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (104)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (72)
DpShMCreate: sizeof(vmc_adm) 0 (2080)
DpShMCreate: sizeof(wall_adm) (40056/36728/88/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 0xffffffff6e400000, size: 6404896)
DpShMCreate: allocated sys_adm at 0xffffffff6e400000
DpShMCreate: allocated wp_adm at 0xffffffff6e402218
DpShMCreate: allocated tm_adm_list at 0xffffffff6e406da8
DpShMCreate: allocated tm_adm at 0xffffffff6e406e08
DpShMCreate: allocated wp_ca_adm at 0xffffffff6e978ec0
DpShMCreate: allocated appc_ca_adm at 0xffffffff6e9808a0
DpShMCreate: allocated comm_adm at 0xffffffff6e983140
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 0xffffffff6ea08e20
DpShMCreate: allocated gw_adm at 0xffffffff6ea08ea0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 0xffffffff6ea08ed0
DpShMCreate: allocated wall_adm at 0xffffffff6ea08ed8
MBUF state OFF
DpCommInitTable: init table for 500 entries
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
Using implementation std
<ES> Info: use normal pages (no huge table support available)EsStdUnamFileMapInit: ES base = 0x0xfffffffe60000000
EsStdInit: Extended Memory 4092 MB allocated
<ES> 1022 blocks reserved for free list.
ES initialized.
Wed Oct 22 14:28:13 2008
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1629]
***LOG Q0K=> DpMsAttach, mscon ( gmsc2) [dpxxdisp.c 11753]
DpStartStopMsg: send start message (myname is >gmsc2_DBM_00 <)
DpStartStopMsg: start msg sent
Wed Oct 22 14:28:14 2008
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 111
Release check o.K.
Wed Oct 22 14:28:21 2008
ERROR => W0 (pid 19071) died [dpxxdisp.c 14441]
ERROR => W2 (pid 19073) died [dpxxdisp.c 14441]
ERROR => W3 (pid 19074) died [dpxxdisp.c 14441]
ERROR => W4 (pid 19075) died [dpxxdisp.c 14441]
ERROR => W5 (pid 19076) died [dpxxdisp.c 14441]
ERROR => W7 (pid 19078) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xbf --> 0xbb
ERROR => W8 (pid 19079) died [dpxxdisp.c 14441]
ERROR => W1 (pid 19072) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xbb --> 0xba
ERROR => W6 (pid 19077) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xba --> 0xb8
ERROR => W9 (pid 19080) died [dpxxdisp.c 14441]
ERROR => W10 (pid 19082) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xb8 --> 0xb0
ERROR => W11 (pid 19085) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xb0 --> 0xa0
ERROR => W12 (pid 19087) died [dpxxdisp.c 14441]
my types changed after wp death/restart 0xa0 --> 0x80
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=14
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Wed Oct 22 14:28:31 2008
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long) Wed Oct 22 08:58:31 2008
========================
No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table
0 DIA 19071 Ended no 1 0 0
1 DIA 19072 Ended no 1 0 0
2 DIA 19073 Ended no 1 0 0
3 DIA 19074 Ended no 1 0 0
4 DIA 19075 Ended no 1 0 0
5 DIA 19076 Ended no 1 0 0
6 UPD 19077 Ended no 1 0 0
7 ENQ 19078 Ended no 1 0 0
8 BTC 19079 Ended no 1 0 0
9 BTC 19080 Ended no 1 0 0
10 BTC 19082 Ended no 1 0 0
11 SPO 19085 Ended no 1 0 0
12 UP2 19087 Ended no 1 0 0
Dispatcher Queue Statistics Wed Oct 22 08:58:31 2008
===========================
--------++++--
+
Typ
now
high
max
writes
reads
--------++++--
+
NOWP
2
2
2000
4
2
--------++++--
+
DIA
3
3
2000
3
0
--------++++--
+
UPD
0
0
2000
0
0
--------++++--
+
ENQ
0
0
2000
0
0
--------++++--
+
BTC
0
0
2000
0
0
--------++++--
+
SPO
0
0
2000
0
0
--------++++--
+
UP2
0
0
2000
0
0
--------++++--
+
this is only a part of dev_disp file.
dev_w0:
trc file: "dev_w0", trc level: 1, release: "700"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, MJ
M sysno 00
M sid DBM
M systemid 370 (Solaris on SPARCV9 CPU)
M relno 7000
M patchlevel 0
M patchno 111
M intno 20050900
M make: single threaded, Unicode, 64 bit, optimized
M pid 19071
M
M
M Wed Oct 22 14:28:12 2008
M kernel runs with dp version 229000(ext=109000) (@(#) DPLIB-INT-VERSION-229000-UC)
M length of sys_adm_ext is 576 bytes
M ***LOG Q01=> ThInit, WPStart (Workproc 0 1 19071) [thxxhead.c 1267]
M ThInit: running on host gmsc2
M calling db_connect ...
C Oracle Client Version: '10.2.0.2.0'
C Client NLS settings: AMERICAN_AMERICA.UTF8
C Logon as OPS$-user to get SAPSR3's password
C Connecting as /@DBM on connection 0 (nls_hdl 0) ... (dbsl 700 250407)
C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
C 0 UTF8 1 0x106ab1350 0x106ab8e10 0x106ac95a8
C Attaching to DB Server DBM (con_hdl=0,svchp=0x106ac94d8,srvhp=0x106acb828)
C
C Wed Oct 22 14:28:13 2008
C Starting user session (con_hdl=0,svchp=0x106ac94d8,srvhp=0x106acb828,usrhp=0x106ab9628)
C Now '/@DBM' is connected (con_hdl 0, nls_hdl 0).
C Got SAPSR3's password from OPS$-user
C Disconnecting from connection 0 ...
C Closing user session (con_hdl=0,svchp=0x106ac94d8,usrhp=0x106ab9628)
C Now I'm disconnected from ORACLE
C Connecting as SAPSR3/<pwd>@DBM on connection 0 (nls_hdl 0) ... (dbsl 700 250407)
C Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
C 0 UTF8 1 0x106ab1350 0x106ab8e10 0x106ac95a8
C Starting user session (con_hdl=0,svchp=0x106ac94d8,srvhp=0x106acb828,usrhp=0x106ab9628)
C
C Wed Oct 22 14:28:14 2008
C Now 'SAPSR3/<pwd>@DBM' is connected (con_hdl 0, nls_hdl 0).
C Database NLS settings: AMERICAN_AMERICA.UTF8
C DB instance DBM is running on gmsc2 with ORACLE version 10.2.0.2.0 since OCT 21, 2008, 06:23:58
B Connection 0 opened (DBSL handle 0)
B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost
B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20081022 142812 gmsc2
M db_connect o.k.
M ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,
.sar,.gif
I MtxInit: 0 0 0
M SHM_PRES_BUF (addr: 0xffffffff7397a000, size: 4400000)
M SHM_ROLL_AREA (addr: 0xfffffffe56000000, size: 134217728)
M SHM_PAGING_AREA (addr: 0xfffffffe50000000, size: 67108864)
M SHM_ROLL_ADM (addr: 0xffffffff73db0000, size: 2672386)
M SHM_PAGING_ADM (addr: 0xffffffff77c00000, size: 656416)
M ThCreateNoBuffer allocated 572152 bytes for 1000 entries at 0xfffffffe48004000
M ThCreateNoBuffer index size: 3000 elems
M ThCreateVBAdm allocated 12176 bytes (50 server) at 0xffffffff77e00000
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation std
X <ES> Info: use normal pages (no huge table support available)ES initialized.
B
B Wed Oct 22 14:28:15 2008
B db_con_shm_ini: WP_ID = 0, WP_CNT = 13, CON_ID = -1
I
I Wed Oct 22 14:28:17 2008
I *** ERROR => shmget(10019,29999888,2016) (22: Invalid argument) [shmux.c 1556]
B dbtbxbuf: Shm Segment 19: Cannot attach
B ***LOG BBB=> ADM message TBX buffer: function shmcreate0 returns RC = 256 [dbtbxbuf#2 @ 16094] [dbtbxbuf1609 4]
B ***LOG BZL=> internal error in table buffer: table buf init fail [dbtbxbuf#2 @ 1701] [dbtbxbuf1701 ]
B dbtbxbuf: return code (sap_rc): 2, Buffer TBX_GENERIC will not be available
B db_tblinit failed
M *** ERROR => ThCallHooks: event handler db_init for event CREATE_SHM failed [thxxtool3.c 260]
M *** ERROR => ThIPCInit: hook failed [thxxhead.c 2067]
M ***LOG R19=> ThInit, ThIPCInit ( TSKH-IPC-000001) [thxxhead.c 1509]
M in_ThErrHandle: 1
M *** ERROR => ThInit: ThIPCInit (step 1, th_errno 17, action 3, level 1) [thxxhead.c 10283]
M
M Info for wp 0
M
M stat = WP_RUN
M waiting_for = NO_WAITING
M reqtype = DP_RQ_DIAWP
M act_reqtype = NO_REQTYPE
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source =
M last_tid = 0
M last_mode = 0
M semaphore = 0
M act_cs_count = 0
M csTrack = 0
M csTrackRwExcl = 0
M csTrackRwShrd = 0
M control_flag = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M req.vm = no VM
M attachedVm = no VM
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 720]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 260]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 19071) [dpuxtool.c 260]
Quick help would be appreciated since installation it held up.
Regards,
Santosh BhatHi,
I am finding following error in your log:
MsSClientHandle: no server provides service ENQ (4), requested from gmsc2_DBM_00 http://msxxserv_mt. 4669
UPD 0 0 2000 0 0
--------++++--
+
ENQ 0 0 2000 0 0
--------++++--
+
BTC 0 0 2000 0 0
--------++++--
+
SPO 0 0 2000 0 0
--------++++--
+
UP2 0 0 2000 0 0
Please assign no. of work processes to at least 1 for above mentioned type of work process. -
PSA no deletion SAP BW on HANA Rev 61
Hi,
PSAs are not getting deleted for some of the datasources due to error loads and multiple runs. System is SAP BW on HANA Rev 61.
The previous job failure was not corrected and the subsequent job was started based on the process chain schedule and that one as well failed. This has happened 2 times. Now the PSA table says it has duplicate entries and it is not dropping when we try to delete manually or through program.
Whenever we try to delete the PSA, the SAPLSDB2 program runs and is stuck in SM51. St22 error log says
SQL error "-10807" while accessing table "/BIC/B0000674001".
65 l_s_data TYPE /BIC/B0000674001.
66 *---1363526 Increasing the security to check the number of records inserted in PSA table
67 *---is actually equal to data in l_t_data or p_t_data.
68 DATA: l_rollback TYPE rs_bool,
69 l_count TYPE i.
70 l_rollback = RS_C_FALSE.
71 *---1363526
72
73 APPEND LINES OF p_t_data TO l_t_data.
74
75 CLEAR: l_s_data.
76 l_s_data-partno = p_partno.
77
78 MODIFY l_t_data
79 FROM l_s_data
80 TRANSPORTING partno
81 WHERE request = p_requestid.
82
83
>>> INSERT /BIC/B0000674001
85 FROM TABLE l_t_data
86 ACCEPTING DUPLICATE KEYS.
87 *---1363526
88 DESCRIBE TABLE l_t_data LINES l_count.
89 IF l_count NE sy-dbcnt.
90 l_rollback = RS_C_TRUE.
91 ENDIF.
92 *---1363526
Category ABAP Server Resource Shortage
Runtime Errors DBIF_RSQL_SQL_ERROR
Except. CX_SY_OPEN_SQL_DB
Date and Time 10.08.2014 11:28:01
|Short text |
| SQL error "-10807" while accessing table "/BIC/B0000674001". |
|What happened? |
| Database error text: "System call 'recv' failed, rc=145:Connection timed out" |
|What can you do? |
| Please make a note of the actions and input which caused the error. |
| - |
| |
| To resolve the problem, contact your |
| SAP system administrator. |
| |
| Using transaction ST22 for ABAP dump analysis you can see and |
| administrate termination messages and retain them for longer periods. |
| Please make a note of the actions and input which caused the error. |
| - |
| |
| To resolve the problem, contact your |
| SAP system administrator. |
| |
| Using transaction ST22 for ABAP dump analysis you can see and |
| administrate termination messages and retain them for longer periods. |
|Error analysis |
| An exception occurred that is explained in detail below. |
| The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught |
| in |
| procedure "INSERT_ODS" "(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: |
| Database error text: "System call 'recv' failed, rc=145:Connection timed out" |
|How to correct the error |
| Internal call code.........: "[RSQL/INSR//BIC/B0000674001 ]" |
| Please check the entries in the system log (Transaction SM21). |
| You may able to find an interim solution to the problem |
| in the SAP note system. If you have access to the note system yourself, |
| please use the following search criteria: |
| |
| "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB" |
| "GP4PWAW7JG4VX23SSK75NF4776C" bzw. "GP4PWAW7JG4VX23SSK75NF4776C" |
| "INSERT_ODS" |
| If you cannot solve the problem yourself, please send the |
| following documents to SAP: |
| |
| 1. A hard copy print describing the problem (short dump). |
| To obtain this, select "System->List->Save->Local File (unconverted)" |
| on the current screen. |
| |
| 2. A suitable hardcopy printout of the system log. |
| To obtain this, call the system log with Transaction SM21 |
| and set the time interval to 10 minutes before and 5 minutes after |
| the short dump. In the display choose "System->List->Save-> |
| Local File (unconverted)" |
| |
| 3. If the programs are your own programs or modified SAP programs, |
| supply the source code. |
| To do this, choose "More Utilities->Upload/Download->Download" in the |
| Editor. |
| |
| 4. Details regarding the conditions under which the error occurred |
| or which actions and input led to the error. |
| You may able to find an interim solution to the problem |
| in the SAP note system. If you have access to the note system yourself, |
| please use the following search criteria: |
| |
| "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB" |
| "GP4PWAW7JG4VX23SSK75NF4776C" bzw. "GP4PWAW7JG4VX23SSK75NF4776C" |
| "INSERT_ODS" |
| If you cannot solve the problem yourself, please send the |
| following documents to SAP: |
| |
| 1. A hard copy print describing the problem (short dump). |
| To obtain this, select "System->List->Save->Local File (unconverted)" |
| on the current screen. |
| |
| 2. A suitable hardcopy printout of the system log. |
| To obtain this, call the system log with Transaction SM21 |
| and set the time interval to 10 minutes before and 5 minutes after |
| the short dump. In the display choose "System->List->Save-> |
| Local File (unconverted)" |
| |
| 3. If the programs are your own programs or modified SAP programs, |
| supply the source code. |
| To do this, choose "More Utilities->Upload/Download->Download" in the |
| Editor. |
| |
| 4. Details regarding 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 |
| "INSERT_ODS" "(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..... 730 |
| SAP Basis Level. 0006 |
| |
| Application server... "pkghnp" |
| Network address...... "10.83.240.20" |
| Operating system..... "SunOS" |
| Release.............. "5.10" |
| Hardware type........ "sun4u" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 4 |
| Shortdump setting.... "full" |
| |
| Database server... "vsyexhann01" |
| Database type..... "HDB" |
| Database name..... "HNP" |
| Database user ID.. "SAPHNP" |
| |
| Terminal.......... " " |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 720 |
| created (date)... "Mar 21 2012 09:58:29" |
| create on........ "SunOS 5.10 Generic_141444-09 sun4us" |
| Database version. "SQLDBC 1.00.61.0380109 " |
| |
| Patch level. 201 |
| Patch text.. " " |
| |
| Database............. "HDB 1.0" |
| SAP database version. 720 |
| Operating system..... "SunOS 5.10, SunOS 5.11" |
| |
| Memory consumption |
| Roll.... 0 |
| EM...... 100555392 |
| Heap.... 0 |
| Page.... 0 |
| MM Used. 75424248 |
| MM Free. 25123904 |
|User and Transaction |
| Client.............. 330 |
| User................ "BIREMOTE" |
| Language key........ "E" |
| Transaction......... " " |
| Transaction ID...... "53E66CC9405502F9E10000000A53F03E" |
| |
| EPP Whole Context ID.... "CEED21FC7C3EC04FA3C0D0912FE05A37" |
| EPP Connection ID....... 00000000000000000000000000000000 |
| EPP Caller Counter...... 0 |
| |
| Program............. "GP4PWAW7JG4VX23SSK75NF4776C" |
| Screen.............. "SAPMSSY1 3004" |
| Screen Line......... 2 |
| Debugger Active..... "none" |
|Server-Side Connection Information |
| Information on caller of Remote Function Call (RFC): |
| System.............. "SP1" |
| Installation number " " |
| Database release... 620 |
| Kernel release...... 640 |
| Connection type 3 (2=R/2, 3=ABAP system, E=external, R=reg. external) |
| Call type.......... "synchronous and transactional type T (emode 0, imode 0)" |
| Inbound TID.........." " |
| Inbound queue name..." " |
| Outbound TID........."0A53F03E141153E6C6641A65" |
| Outbound queue name.." " |
| |
| Client#............. 330 |
| User................."BIWREMOTE" |
| Transaction......... " " |
| Call program........."SAPLERFC" |
| Function module "ARFC_DEST_SHIP" |
| Call destination.. "HNP330" |
| Source server....... "pkgapp2_SP1_03" |
| Source IP address "10.83.240.59" |
| |
| Additional information on RFC logon: |
| Trusted relationship." " |
| Logon return code....0 |
| Trusted teturn code..0 |
| |
| Note: |
| - For Releases < 4.0, information on the RFC caller is not available. |
| - The installation number is provided from Release > 700 |
| Transaction......... " " |
| Call Program........."SAPLERFC" |
| Function Module..... "ARFC_DEST_SHIP" |
| Call Destination.... "HNP330" |
| Source Server....... "pkgapp2_SP1_03" |
| Source IP Address... "10.83.240.59" |
| |
| Additional information on RFC logon: |
| Trusted Relationship " " |
| Logon Return Code... 0 |
| Trusted Return Code. 0 |
| |
| Note: |
| - For Releases < 4.0, information on the RFC caller not available. |
| - The installation number is available from caller Release > 700 |
|Information on where terminated |
| Termination occurred in the ABAP program "GP4PWAW7JG4VX23SSK75NF4776C" - in |
| "INSERT_ODS". |
| The main program was "SAPMSSY1 ". |
| |
| In the source code you have the termination point in line 84 |
| of the (Include) program "GP4PWAW7JG4VX23SSK75NF4776C". |
| The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in |
| procedure "INSERT_ODS" "(FORM)", but it was neither handled locally nor |
| declared |
| in the RAISING clause of its signature. |
| |
| The procedure is in program "GP4PWAW7JG4VX23SSK75NF4776C "; its source code |
| begins in line |
| 23 of the (Include program "GP4PWAW7JG4VX23SSK75NF4776C ". |
|Source Code Extract |
|Line |SourceCde |
| 54|* leave further processing because data is not consistent |
| 55| |
| 56| IF l_inconsistency_found = rs_c_true. |
| 57| p_subrc = 77. |
| 58| EXIT. |
| 59| ENDIF. |
| 60| |
| 61| |
| 62| |
| 63| |
| 64| DATA: l_t_data TYPE ty_t_data, |
| 65| l_s_data TYPE /BIC/B0000674001. |
| 66|*---1363526 Increasing the security to check the number of records inserted in PSA table |
| 67|*---is actually equal to data in l_t_data or p_t_data. |
| 68| DATA: l_rollback TYPE rs_bool, |
| 69| l_count TYPE i. |
| 70| l_rollback = RS_C_FALSE. |
| 71|*---1363526 |
| 72| |
| 73| APPEND LINES OF p_t_data TO l_t_data. |
| 74| |
| 75| CLEAR: l_s_data. |
| 76| l_s_data-partno = p_partno. |
| 77| |
| 78| MODIFY l_t_data |
| 79| FROM l_s_data |
| 80| TRANSPORTING partno |
| 81| WHERE request = p_requestid. |
| 82| |
| 83| |
|>>>>>| INSERT /BIC/B0000674001 |
| 85| FROM TABLE l_t_data |
| 86| ACCEPTING DUPLICATE KEYS. |
| 87|*---1363526 |
| 88| DESCRIBE TABLE l_t_data LINES l_count. |
| 89| IF l_count NE sy-dbcnt. |
| 90| l_rollback = RS_C_TRUE. |
| 91| ENDIF. |
| 92|*---1363526 |
| 93| |
| 94| |
| 95|*---1363526 |
| 96| IF sy-subrc NE 0 OR l_rollback = RS_C_TRUE. |
| 97|* Insert not successful - rollback changes |
| 98| CALL FUNCTION 'DB_ROLLBACK'. |
| 99|*---1363526 |
| 100| p_subrc = 13. |
| 101| ENDIF. |
| 102| |
| 103|ENDFORM. "INSERT_ODS |
| isShmLockId = 0 |
| isUsed = 1 |
| isCtfyAble = 1 |
| hasScndKeys = 0 |
| hasRowId = 0 |
| scndKeysOutdated = 0 |
| scndUniKeysOutdated = 0 |
| ----- Shareable Table Header Data ----- |
| tabi = 0xFFFFFFF1DD5E8E58 |
| pgHook = 0x0000000000000000 |
| idxPtr = 0x0000000000000000 |
| id = 11 (0x0000000B) |
| shmTabhSet = 0x0000000000000000 |
| refCount = 0 (0x00000000) |
| tstRefCount = 0 (0x00000000) |
| lineAdmin = 4 (0x00000004) |
| lineAlloc = 4 (0x00000004) |
| shmVersId = 0 (0x00000000) |
| shmRefCount = 1 (0x00000001) |
| rowId = 18446744073709551615 |
| scndKeyAdmin = 0x0000000000000000 |
| 0A53F03E141153E6C6641A65HNP330 00000001SENDED RSAR_TRFC_DATA_RECEIVE|
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 3433433433333343433334334453332222222222222222222222222233333333544444225545555445445455444454|
| 0153603514115356366411658E0330000000000000000000000000000000000135E454002312F4263F4141F2535965|
| 0030004100350033004600300033004500310034003100310035003300450036004300360036003400310041003600|
|PROG |
| SAPLERFC |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 5454454422222222222222222222222222222222 |
| 310C526300000000000000000000000000000000 |
| 005300410050004C004500520046004300200020002000200020002000200020002000200020002000200020002000|
|%_DUMMY$$ |
| |
| 0000 |
| 0000 |
| 2222 |
| 0000 |
| 0020002000200020 |
|NUMBER_OF_FUNCTION_MODULES |
| 1 |
| 0000 |
| 0001 |
| 00000001 |
|SUPPORTABILITY_INFO-DEBUG_CONTEXT_ID |
| |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0020002000200020002000200020002000200020002000200020002000200020002000200020002000200020002000|
|SPACE |
| |
| 0 |
| 0 |
| 2 |
| 0 |
| 0020 |
|SCREEN |
| |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222|
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 0020002000200020002000200020002000200020002000200020002000200020002000200020002000200020002000|
|No. 4 Ty. FUNCTION |
|Name ARFC_DEST_SHIP |
|SENDER_ID |
| pkgapp2_SP1_03 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| 76667735553533222222222222222222 |
| 0B71002F301F03000000000000000000 |
| 0070006B00670061007000700032005F005300500031005F0030003300200020002000200020002000200020002000|
|SUPPORTABILITY_INFO |
| ######## ## # |
| 000000000000000000000000000000000000000000000000000000 |
| 000000000000000000000000000000000000000000000000000000 |
| 000000002222222222222222222222222222222222222222002220 |
| 000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000200020002000200020002000200020002000200020002000200020002000|
|UNIT_ID |
| ################Hi Siddartha,
That option is not working.
Thanks -
ERROR MESSAGE sap system manager:work process restarted, session terminated
Hi,
i am a beginer in SAP administration, users are getting this error message and i have done all my research and not able to resolve this issue. Here are the details
SAP Version :ideas 4.7
Database :Oracle
OS : windows 2003
Module user is working on MM
user working on it is a Super user with all the permissions
SAP is configure to run under the European date and decimal format.
I have never done any database administration on it, it is a new install and has been rarely used.
User creates a RFQ and when he tries saving it , seems like for the first time after either restarting the macine or restarting the service it might work and at time it might not, this is a very sporadic error and most of the times it crashes out with the message "sap system manager:work process restarted, session terminated" and kicks the user out of the session.
Below are the details of the error message from ST22 :
name of the runtime error : system_core_dumped
below are the details of the error message and its resoltion as suggested by sap help :
========
Runtime Errors SYSTEM_CORE_DUMPED
Occurred on 01.02.2008 at 07:52:19
Process terminated by signal " ".
What happened?
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "SAPLCLSC" had to be terminated because the ABAP
processor discovered an invalid system state.
What can you do?
Make a note of the actions and input which 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.
Error analysis
An SAP System process was terminated by an operating system signal.
Possible reasons for this are:
1. Internal SAP System error.
2. Process was terminated externally (by the system administrator).
Last error logged in SAP kernel
Component............ "Taskhandler"
Place................ "SAP-Server server1_DEV_00 on host server1 (wp 1)"
Version.............. 1
Error code........... 11
Error text........... "ThSigHandler: signal"
Description.......... " "
System call.......... " "
Module............... "thxxhead.c"
Line................. 9555
How to correct the error
The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
contains a file called 'core'.
Save this file under another name.
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. " "
Application server....... " "
Network address.......... " "
Operating system......... " "
Release.................. " "
Hardware type............ " "
Character length......... " " Bits
Pointer length........... " " Bits
Work process number...... " "
Short dump setting....... " "
Database server.......... " "
Database type............ " "
Database name............ " "
Database owner........... " "
Character set............ " "
SAP kernel............... " "
Created on............... " "
Created in............... " "
Database version......... " "
Patch level.............. " "
Patch text............... " "
Supported environment....
Database................. " "
SAP database version..... " "
Operating system......... " "
User, transaction...
Client.............. " "
User................ " "
Language key........ " "
Transaction......... "ME41 "
Program............. "SAPLCLSC"
Screen.............. "SAPMM06E 0320"
Screen line......... 71
Information on where termination occurred
The termination occurred in the ABAP program "SAPLCLSC" in "EXECUTE_SELECT".
The main program was "SAPMM06E ".
The termination occurred in line 131 of the source code of the (Include)
program "LCLSCF2G"
of the source code of program "LCLSCF2G" (when calling the editor 1310).
=============
i even tried increasing the dialog processes but with no use.The same error occurs.
I appreciate every one of help i can get, i am working on a deadline which is tomorrow evening to resovle this issue, any kind of help is highly appreciated.
thanks
mudessir.Hi
follow correction method suggested in this dump,
" The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
contains a file called 'core'. Save this file under another name."
have you done this?
with regards,
raj.
<i>pls, award points</i> -
How to change the hostname was set/defined in SAP system?
Dear Expert,
My customer met a problem about that:
he defined his host name with small characters(lower case) "abc" when he installed the SAP system (Windows2003(x64)-Solman70SR4).
But in SM21, the title of sm21, the hostname was recognize as upper case "ABC".
in SM51, the hostname was also recognized as upper case "ABC"
in STMS, the tab of 'transport tool', it is recognized as lower case "abc" in TRANSDIR.
in SM59, it is recognized as upper case "ABC" in internal connections, but recognized as lower case "abc" in ABAP connections, such as TMSADM@<DB>.DOMAIN.<sid>
While in Java URL, it is recognized as lower case "abc". With my test, the Java URL is not case sensitive for the HOSTNAME part in HTTP link as I tested to change the hostname both in upper case and lower case in etc\hostname file, the URL both are working. (not sure if this is due to the test is with intranet or not).
Based on SAP note 611361, it seems that:
"Hostnames must be considered "case sensitive". That means
hostnames shall be used in the same case (upper or lower) in all
SAP configurations as well as in the network configuration (DNS
or etc/hosts). You must ensure consistent name resolving of the
hostname from hostname to IP address and back from the IP address
to the the same hostname (case sensitive match). See also note
129997."
Please help to suggest.
Many thanks in advance,
Perry SongSection 4.13 "Checking the Consistency of the Host Name" in [This Upgrade Guide|https://websmp208.sap-ag.de/~sapidb/011000358700000353422008E] has a good explaination of what & how to check your hostname / parameter configuration.
on a windows box, another way to get the TCP/IP name is to type 'hostname' from a CMD window. -
What are the major process to transfer the data from legacy to sap system.
What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?
hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null -
Inconsistencies data between ODS and RSA3 in SAP system (delta problem??)
Hi everyone,
I have a problem in my SAP BW production system. There is inconsistencies data between ODS (using tcode LISTCUBE) and Datasource in SAP system (tcode RSA3).
I'm using Datasource: 0FI_GL_10 and ODS: 0FIGL_O10.
In SAP system (using RSA3):
GL Account: 1202012091
Comp Code : 5400
Bus Area: 5401
Fiscal Year :2008
Period: 07
Accum Balance : $0
Credit Total: $350
Debit Total: $350
Sales : $0
And in ODS (using ListCube):
GL Account: 1202012091
Comp Code : 5400
Bus Area: 5401
Fiscal Year :2008
Period: 07
0BALANCE : $350 (it should be $0,shouldn't it? )
0CREDIT: $0 (it should be $350,shouldn't it? )
0DEBIT: $350
0SALES: $350 (it should be $0,shouldn't it?)
I have tried these :
1. Check if there is a start routine / routine or not in transfer or update rules....and...i get nothing
2. Check the data using tcode FBL3N..but the data is ok
And then i tried to trace the process chain and find error on delta infopackage which pull these data
Date
07.30.2008 : 231141 records --> error (ODS activation) --> request has deleted forever
07.31.2008 : 2848 records --> error (ODS activation) --> request has deleted forever
08.01.2008 : 135679 records --> error (ODS activation) --> request has deleted forever
08.02.2008 : 135679 records --> successfull repeat delta action
From 30 July until 1 August there is an error on delta infopackage because
fail to activate ODS (No SID found for value 'RIM' of characteristic 0UNIT). On 2 August someone delete the red requests and repeat the delta and success. Is there any possibilities that this problem arise because of this? If this the cause, how to bring back 2848 and 231141 records which has deleted?
Thank you and Regards,
-Satria-Hi everyone,
I have solved my problem. I executed my infopackage again (selection condition using GL Account which have wrong amount) with update mode 'Full update' and choose Scheduler > Repair Full Request and tick the checkbox.Thank you.
Regards,
-Satria- -
Problem in moving object from one SAP system to another....
Hi,
I have created a transport request in System A client 800.
I am trying to move the Transport request to System B client 900.
(Note: A and B are different SAP systems)
I first release the object going in system A client 800 using transaction se09.
Now I go to System B client 900 and then to transaction STMS. After this I click on display import queue for System A inside transaction STMS in System B. Then I go to EXTRAS ->Other Requests Add. The import queue name is defaulted by System A and then I add the Transport Request number. Then the system asks me to login in Sytem A client 800. I login successfully. But I get an error message:
"Transport control program tp ended with error code 0247
Errors: addtobuffer has problems with data- and/or cofile"
Can someone tell me how to solve this error ? What is the issue ?
Regards,
Rajesh.Hi Rajesh,
Check this link:
tp ended with error code 0247
http://www-1.ibm.com/support/docview.wss?rs=2366&context=SSZ8F3&dc=DB520&uid=swg21243429&loc=en_US&cs=UTF-8&lang=en&rss=ct2366tivoli
Solar_migration to different sid
http://www.sapfans.com/forums/viewtopic.php?p=790715&sid=3528f52126b6764d5cb28acb67f752fe
http://www.sapfans.com/forums/viewtopic.php?t=221340&view=next&sid=0e5e06508287d3f738bc97ce7aea8426
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/transport-request-to-import-queue-with-error-740676
Hope any of this link helps you out.
Regards,
Vivek -
How to import the transports from the SAP Integration Kit into SAP system
Hi expert,
I read the forum "Re: Integration with SAP R/3 to realise i have not done the import of transport but i don't quite understand the statement give by "Sebastian Li".
"Unpack the SAP Integration Kit zip-file. It contains a transport-folder. Here you'll find a short manual which files you should import.
Copy the needed files on your sap-system in the correct folders:
- usr\sap\trans\cofiles
- usr\sap\trans\data
Use the transaction STMS.
Also take care of the sequence of importing. See the manual for details."
Can some one explain it in more details to me. I have unzip the SAP Integration Kit n in the transport folder got 2 more folder "ansi" and "unicode_compatible". How do i know which 1 to use? Where i should copy this files to?
Please advice.
thank youHi Rajesh,
check this : logon failed. you do not have the necessary rights to design reports
@Sri -
Manually delete Transport system - Sandbox system
Hi All
I am have a problem with our transport system on or sandbox system and basically what I want to do it get rid of it and set it up locally.
As our system is a copy of our PRD it still has all the old config, what I would like to do is remove it in the database. Does any one know how to do this?
It is a bit of a 'fudge' but seems the easiest way to do it.
Many Thanks in advance
Philhello,
Just delete (if necessary) the STMS configuration and describe your transport planning so that we can help you.
Manoj -
How to import a transport from one SAP system to another SAP System?
We have a requirement where the same security report needs to be made avialble across the whole SAP landscape - comprising of ECC6, PI7, BW, HR , SRM, CRM etc.
To reduce the time and effort, is it possible to create the report in ECC6 attach it to a transport request and import it into SRM, CRM etc?
If so, what is the procedure?
Thanks,
BhaskarHi
Yes it is possible. Attach the report to the request and release the request. It will create cofile and datafile for the request in folder /usr/sap/trans/data and /usr/sap/trans/cofiles.
Copy these two files and paste them into the target system in the respective folders i.e the above mentioned directory structure.
The data file should look like Rxxxxxx.SID and cofile should look like Kxxxxxx.SID where xxxxxx is your request number.
Once these are copied in the target system, logon to target system goto STMS, goto the import queue of the system, then extras --> Other requests --> Add, enter the request number as in original system <SID>Kxxxxxx, and enter.
Then you should be able to import it.
Hope this clarifies.
Regards
Rahul
Maybe you are looking for
-
I am not being able to add contacts to my skype,how can I?
after I enter a e-mail address on the new contacts line and click find, it does not add it. What do I need to do to add a new contact, from my address book?
-
My iPod touch 5th generation says: iPod is disabled, connect to iTunes. When I try to connect to iTunes it says: cannot connect, please put pass code in iPod... Please help!!!!
-
Tracking of Material Movement between two customers
Dear All, We have already sold product to customer using SD Cycle.Being Non Moving at Customer end , Is it possible to trannfer to other customer? We don't want any accounting entry in SAP , But want to track serial number base material transfer.Also
-
I created a Web Photo Gallery in Adobe Bridge. I want to save my presets, cause I changed the background color etc? It this possible? Cause I want to use the same presets in the future. Thanks, Ief
-
FB beta 2 PHP services genretated code
looking for some doco on this - the new version has the old doco Accessing data with Flex / Implementing services for data-centric applications section rgds martin