US Address Cleansing Run time error
Hi ,
I am using Global address cleanse transformation for US address cleanse . while iam running the job getting the error like this
Transform <USA_AddressCleanse>: The directory type GA_DIR_TYPE_REGION for group DEFAULT_CYRL contains an incompatible build id.
Please help me out to resolve this problem . My US address directories are SEP 09 direcotries..
Thanks&Regards,
Ramana.
Hi Ramana,
is that a new issue, or is it the first time you are running your Data Services Job?
The SAP Support Portal offers a SAP Note on this topic:
1384859 - Which files are installed by the software to the reference_data folder? - Data Services XI
Symptom
Which files are installed with the software?
Which files are installed to the reference_data folder?
Reference files are missing from the directories folder
ERROR: File does not exist:D:\BUSOBJ\DIRS\CANADA\ga_directory_db.xml
Installed directories to a new location, but did not copy over the installation files
ERROR: The Directory type GA_DIR_TYPE_REGION for the group DEFAULT_CYRL contains an incompatible build id
How to know which files are directory downloadeds verses installation files to the DataQuality\reference_data directory
Environment
Data Services XI
Resolution
With Data Services XI, some file in the reference_data folder are installed with the software while others are downloaded as Addressing Directories from SAP Service Marketplace (SMP).
The following files are installed with the software to the default location ..\Business Objects\BusinessObjects Data Services\DataQuality\reference_data folder. If the directories which are downloaded from SMP are installed outside the default location, the following files will need to be copied to that location:
AddressServerGlobal.db
dpvw.txt
dpvx.txt
dpvy.dpv
dpvz.dpv
ga_country.dir
ga_directory_db.xml
ga_dirctory_db_emea.xml
lacsw.txt
lacsx.txt
lacsy.ll
lacsz.ll
MultiLineKeywords.db
ga_region_gen.dir (eff. July 2009, this file is also included with the directory downloads, in that case, keep the file with the most recent date)
Note: One workaround is to install all directory data to the ..\Business Objects\BusinessObjects Data Services\DataQuality\reference_data folder whenever new directories are downloaded. This eliminates the need to copy the above files to the respective folders.
Keywords
DS , DSXI , DS XI , ref data , referential , reference data , DQ , international , intl , gac , data cleanse , dpv , lacslink , dirs
SAP Support Portal - Help&Support inlcudes a great SAP xSearch Application, where you can type in some of the content form the Error Message like "DEFAULT_CYRL", that's how I got this SAP Note identified.
Niels
Niels
Similar Messages
-
Run-time error "DDIC_TYPE_INCONSISTENCY" occurred
Hello experts,
SAP version :SAP ECC 6.0
DB : Oracle 10.2.0.2
After a local client copy we had the following error showing in scc3:
Completed w. Dictionary Errors
ICLPART FS-CM DDIC Error (See SE14)
In SE14 when i check the db object all is well but when i check the runtime object i get :
Hdr: Active runtime object and Active source has Inconsistent
and....
Fields: Active runtime object and Active source has Inconsistent
ASSIGN_GUID does not exist
Do you have any idea how to solve this
Thanks for your help.
Regards
DirkHello Visser,
Please find the following link to goto a note which address this, Run-time error "DDIC_TYPE_INCONSISTENCY"
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=491022
Note number is: 491022
If you get the above error in ABAP dump, then it could be due the backgroung job which was showing the status cancelled daily.
Just delete the job from sm37 and it should fix the issue.
Hope it helps.
Cheers,
Satish. -
Dear All,
During the transaction /n/sapapo/ccr (Reconsilation of transaction data) in client SCP 950, system displays the run time error which are attached herewith.
This is the activity a used to execute regularly (Daily) and first time i recieved this message - -
Runtime Errors ASSERTION_FAILED
Date and Time 13.07.2007 10:13:37
ShrtText
The ASSERT condition has been violated.
What happened?
In the current application program, the system recognized a situation
involving the ASSERT statement that should not occur. A runtime error
occurred, either because there was no activation ID entered or because
the ID of the activation mode used was set to "Cancel.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
The following activation ID was used: "No checkpoint group specified"
If the FIELDS addition was used with this ASSERT statement, the content
of the first 8 fields is as follows:
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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,
use the following search criteria:
"ASSERTION_FAILED" C
"/SAPAPO/SAPLTIMESTAMP" or "/SAPAPO/LTIMESTAMPU08"
"/SAPAPO/TIMESTAMP_DIFFERENCE"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"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, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "scmprd"
Network address.......... "172.16.10.47"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "0002BFAAD700"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 0
Short dump setting....... "full"
Database server.......... "scmprd"
Database type............ "ORACLE"
Database name............ "SCP"
Database owner........... "SAPSCP"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Jan 18 2006 20:47:39"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "109"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16192
EM....................... 196923232
Heap..................... 0
Page..................... 98304
MM Used.................. 186636840
MM Free.................. 1895288
SAP Release.............. "640"
User and Transaction
Client.............. 950
User................ "SCMATP"
Language key........ "E"
Transaction......... "/SAPAPO/CCR "
Program............. "/SAPAPO/SAPLTIMESTAMP"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "/SAPAPO/SAPLTIMESTAMP" in
"/SAPAPO/TIMESTAMP_DIFFERENCE".
The main program was "/SAPAPO/CIF_DELTAREPORT3 ".
The termination occurred in line 61 of the source code of the (Include)
program "/SAPAPO/LTIMESTAMPU08"
of the source code of program "/SAPAPO/LTIMESTAMPU08" (when calling the editor
610).
Source Code Extract
Line SourceCde
31 lv_time_int_low TYPE i,
32 lv_timediff_int TYPE i,
33 lv_datediff_int TYPE i,
34 lv_time TYPE t,
35 ls_time TYPE tstr_timestr.
36
37 * check timestamp parameter
38 * ASSERT NOT iv_timestamp_high IS INITIAL.
39 * ASSERT NOT iv_timestamp_low IS INITIAL.
40 * ASSERT iv_timestamp_low <= iv_timestamp_high.
41 IF iv_timestamp_high IS INITIAL
42 OR iv_timestamp_low IS INITIAL.
43 RAISE invalid_parameter.
44 ENDIF.
45 IF iv_timestamp_high < iv_timestamp_low.
46 RAISE invalid_parameter.
47 ENDIF.
48
49 * prepare timestamps
50 * .. split into date and time integers
51 ls_timestamp_high = iv_timestamp_high.
52 lv_date_int_high = ls_timestamp_high-date.
53 lv_time_int_high = ls_timestamp_high-time.
54 ls_timestamp_low = iv_timestamp_low.
55 lv_date_int_low = ls_timestamp_low-date.
56 lv_time_int_low = ls_timestamp_low-time.
57
58 * .. calc date diff
59 * .. check against max. allowed integer difference
60 lv_datediff_int = lv_date_int_high - lv_date_int_low.
>>>>> ASSERT lv_datediff_int <= lc_datediff_intmax.
62
63 * calc time diff
64 lv_timediff_int = lv_time_int_high - lv_time_int_low.
65 IF lv_timediff_int < 0.
66 ADD 86400 TO lv_timediff_int.
67 SUBTRACT 1 FROM lv_datediff_int.
68 ENDIF.
69
70 * calc total duration
71 lv_duration_int = lv_datediff_int * 86400 + lv_timediff_int.
72 lv_time = lv_timediff_int.
73 ls_time = lv_time.
74 ls_duration-hours = lv_duration_int DIV 3600.
75 ls_duration-minutes = ls_time-minute.
76 ls_duration-seconds = ls_time-second.
77
78 ev_duration_packed = ls_duration.
79 ev_duration_integer = lv_duration_int.
80 ENDFUNCTION.
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 1
SY-DBCNT 1
SY-FDPOS 6
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE CIF - Comparison/Reconciliation of Transaction Data
SY-MSGTY
SY-MSGID
SY-MSGNO 000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
5 FUNCTION /SAPAPO/SAPLTIMESTAMP /SAPAPO/LTIMESTAMPU08 61
/SAPAPO/TIMESTAMP_DIFFERENCE
4 FORM /SAPAPO/SAPLCIF_DELTA3 /SAPAPO/LCIF_DELTA3F17 349
COMPARE_ORDER_HEADER
3 FUNCTION /SAPAPO/SAPLCIF_DELTA3 /SAPAPO/LCIF_DELTA3U03 125
/SAPAPO/CIF_DELTA3_COMP_ORDER
2 FUNCTION /SAPAPO/SAPLCIF_DELTA3 /SAPAPO/LCIF_DELTA3U01 871
/SAPAPO/CIF_DELTA3_COMP
1 EVENT /SAPAPO/CIF_DELTAREPORT3 /SAPAPO/CIF_DELTAREPORT3 189
START-OF-SELECTION
Chosen variables
Name
Val.
No. 5 Ty. FUNCTION
Name /SAPAPO/TIMESTAMP_DIFFERENCE
IV_TIMESTAMP_HIGH
#q1###
02073899
2001125C
IV_TIMESTAMP_LOW
##q!####
00720899
2011125C
EV_DURATION_INTEGER
0
0000
0000
EV_DURATION_PACKED
000000
00000C
SYST-REPID
/SAPAPO/SAPLTIMESTAMP
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454254545444554452222222222222222222
F31010FF310C49D5341D00000000000000000000
%_SPACE
0
0
2
0
LS_TIMESTAMP_HIGH
22000713182959
00000000000000
00000000000000
33333333333333
22000713182959
LV_DATE_INT_HIGH
803363
0042
0C23
LS_TIMESTAMP_HIGH-DATE
22000713
00000000
00000000
33333333
22000713
LV_TIME_INT_HIGH
66599
0002
0147
LS_TIMESTAMP_HIGH-TIME
182959
000000
000000
333333
182959
LS_TIMESTAMP_LOW
20071210182959
00000000000000
00000000000000
33333333333333
20071210182959
LV_DATE_INT_LOW
733021
0025
0BFD
LS_TIMESTAMP_LOW-DATE
20071210
00000000
00000000
33333333
20071210
LV_TIME_INT_LOW
66599
0002
0147
LS_TIMESTAMP_LOW-TIME
182959
000000
000000
333333
182959
SY-UNAME
SCMATP
000000000000
000000000000
544455222222
33D140000000
SCREEN-INPUT
1
0
0
3
1
LV_DATEDIFF_INT
70342
001C
0126
LV_TIMEDIFF_INT
0
0000
0000
SYST
#######################################Ō###############################################䵘 C#Ԁ##
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
SY-REPID
/SAPAPO/SAPLTIMESTAMP
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454254545444554452222222222222222222
F31010FF310C49D5341D00000000000000000000
%_DUMMY$$
0000
0000
2222
0000
No. 4 Ty. FORM
Name COMPARE_ORDER_HEADER
SYST-REPID
/SAPAPO/SAPLCIF_DELTA3
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
2545454254544445444543222222222222222222
F31010FF310C396F45C413000000000000000000
GC_APPEND_MODE
3
0
0
3
3
LS_FIELDS_TO_COMPARE-DUEDATE
X
0
0
5
8
SYST
#######################################Ō###############################################䵘 C#Ԁ##
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
LS_APO_ORDER-ORDTYPE
5
0
0
3
5
GC_PLANNED_ORDER
5
0
0
3
5
LS_R3_ORDER-STATUSCNF
0
0
2
0
GC_ORDER_STATUS_NO_CONF
1
0
0
3
1
LS_APO_ORDER-STATUSCNF
0
0
2
0
GC_PRED_OUT_DEL
A
0
0
4
1
GC_TND_DELETE
CN
00
00
44
3EDear Sajit,
Go through the following OSS Notes:
<a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=901957&_NLANG=E">901957</a>, <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1036880&_NLANG=E">1036880</a>, <a href="https://websmp110.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1067414&_NLANG=E">1067414</a>
Regards,
Naveen. -
Run-time error "PXA_NO_SHARED_MEMORY" occurred
Hi All,
My production system is running fine. And when i check SM21 I saw a lot of error message Run-time error "PXA_NO_SHARED_MEMORY" occurred and Run-time error "SYSTEM_NO_ROLL" occurred. However I can't see any error in ST22. I had read sap note 307976. And dont know when I restart the SAP services is it will be fine?
trc file: "dev_w0", trc level: 1, release: "640"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, M
B
B Mon Feb 22 08:13:29 2010
B create_con (con_name=R/3)
B Loading DB library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' ...
B Library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' loaded
B Version of 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' is "640.00", patchlevel (0.58)
B New connection 0 created
M sysno 00
M sid PRD
M systemid 560 (PC with Windows NT)
M relno 6400
M patchlevel 0
M patchno 58
M intno 20020600
M make: multithreaded, ASCII
M pid 2440
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2440) [dpxxdisp.c 1160]
I MtxInit: -2 0 0
M DpSysAdmExtCreate: ABAP is active
M DpShMCreate: sizeof(wp_adm) 11592 (828)
M DpShMCreate: sizeof(tm_adm) 2219848 (11044)
M DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
M DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
M DpShMCreate: sizeof(comm_adm) 192000 (384)
M DpShMCreate: sizeof(vmc_adm) 0 (320)
M DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
M DpShMCreate: SHM_DP_ADM_KEY (addr: 047D0040, size: 2510384)
M DpShMCreate: allocated sys_adm at 047D0040
M DpShMCreate: allocated wp_adm at 047D17A8
M DpShMCreate: allocated tm_adm_list at 047D44F0
M DpShMCreate: allocated tm_adm at 047D4518
M DpShMCreate: allocated wp_ca_adm at 049F2460
M DpShMCreate: allocated appc_ca_adm at 049F6AB0
M DpShMCreate: allocated comm_adm_list at 049F8220
M DpShMCreate: allocated comm_adm at 049F8238
M DpShMCreate: allocated vmc_adm_list at 04A27038
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 04A27060
M DpShMCreate: allocated wall_adm at 04A27068
X EmInit: MmSetImplementation( 2 ).
X <ES> client 0 initializing ....
X Using implementation flat
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M
M Mon Feb 22 08:13:30 2010
M calling db_connect ...
C Thank You for using the SLOLEDB-interface
C Using dynamic link library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll'
C dbmssslib.dll patch info
C patchlevel 0
C patchno 58
C patchcomment MSSQL: Workaround for SQL2005 change in RpcNexecInsert (814383)
C np:(local) connection used on PKG-PRD
C CopyLocalParameters: dbuser is 'prd'
C
C Mon Feb 22 08:13:31 2010
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: MARS property was not set.
C Provider Release:08.50.1022
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: MARS property was not set.
C
C Mon Feb 22 08:13:42 2010
C Cache sizes: header 52 bytes, 20000 names (26720000 bytes), 1000 dynamic statements (5432000 bytes), total 32152052 bytes
C Using shared procedure name cache PKG-PRD_PRDPRD_PRD_MEM initialized by another process.
C Connected to db server : [PKG-PRD] server_used : [np:(local)], dbname: PRD, dbuser: prd
C pn_id:PKG-PRD_PRDPRD_PRD
C Not using MARS (on sql 8.0)
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 20100222 081330 PKG-PRD
C The IRow interface is supported by this OLEDB provider
M db_connect o.k.
I
I Mon Feb 22 08:14:02 2010
I MtxInit: 0 0 0
M SHM_PRES_BUF (addr: 09E50040, size: 4400128)
M SHM_ROLL_AREA (addr: 12510040, size: 262144000)
M SHM_PAGING_AREA (addr: 617B0040, size: 113246208)
M SHM_ROLL_ADM (addr: 0A290040, size: 2616690)
M SHM_PAGING_ADM (addr: 0A510040, size: 525344)
M ThCreateNoBuffer allocated 320144 bytes for 1000 entries at 0A5A0040
M ThCreateNoBuffer index size: 3000 elems
M ThCreateVBAdm allocated 7424 bytes (50 server) at 0A5F0040
X EmInit: MmSetImplementation( 2 ).
X <ES> client 0 initializing ....
X Using implementation flat
X ES initialized.
B db_con_shm_ini: WP_ID = 0, WP_CNT = 14
B dbtbxbuf: Buffer TABL (addr: 103500C8, size: 30000128, end: 11FEC4C8)
B dbtbxbuf: Buffer TABLP (addr: 0E5200C8, size: 10240000, end: 0EEE40C8)
B dbexpbuf: Buffer EIBUF (addr: 0EF000D0, size: 4194304, end: 0F3000D0)
B dbexpbuf: Buffer ESM (addr: 0F3100D0, size: 4194304, end: 0F7100D0)
B dbexpbuf: Buffer CUA (addr: 0F7200D0, size: 3072000, end: 0FA0E0D0)
B dbexpbuf: Buffer OTR (addr: 0FA100D0, size: 4194304, end: 0FE100D0)
M rdisp/reinitialize_code_page -> 0
M icm/accept_remote_trace_level -> 0
M rdisp/no_hooks_for_sqlbreak -> 0
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: MARS property was not set.
S *** init spool environment
S initialize debug system
T Stack direction is downwards.
T debug control: prepare exclude for printer trace
T new memory block 120D8040
S spool kernel/ddic check: Ok
S using table TSP02FX for frontend printing
S 1 spool work process(es) found
S frontend print via spool service enabled
S printer list size is 150
S printer type list size is 50
S queue size (profile) = 300
S hostspool list size = 3000
S option list size is 30
S found processing queue enabled
S found spool memory service RSPO-RCLOCKS at 121F0098
S doing lock recovery
S setting server cache root
S found spool memory service RSPO-SERVERCACHE at 121F03E0
S using messages for server info
S size of spec char cache entry: 165020 bytes (timeout 100 sec)
S size of open spool request entry: 1152 bytes
S immediate print option for implicitely closed spool requests is disabled
A
A -PXA--
A PXA INITIALIZATION
A PXA: Fragment Size too small: 107 MB, reducing # of fragments
A System page size: 4kb, admin_size: 13396kb.
A Attached to PXA (address 21F30040, size 440000K)
A abap/pxa = shared protect gen_remote
A PXA INITIALIZATION FINISHED
A -PXA--
A
C The IRow interface is supported by this OLEDB provider
B dbtran INFO (init_connection '<DEFAULT>' [MSSQL:640.00]):
B max_blocking_factor = 50, max_in_blocking_factor = 255,
B min_blocking_factor = 5, min_in_blocking_factor = 10,
B prefer_union_all = 1, prefer_union_for_select_all = 0,
B prefer_fix_blocking = 0, prefer_in_itab_opt = 0,
B convert AVG = 1, alias table FUPD = 0,
B escape_as_literal = 0, opt GE LE to BETWEEN = 0,
B select * =0x00, character encoding =SBCS / []:X,
B use_hints = abap->1, dbif->0x1, upto->0, rule_in->0,
B rule_fae->0, concat_fae->0, concat_fae_or->0
A
A Mon Feb 22 08:14:03 2010
A ABAP ShmAdm attached (addr=53EC5000 leng=20955136 end=552C1000)
A >> Shm MMADM area (addr=5422D180 leng=134720 end=5424DFC0)
A >> Shm MMDAT area (addr=5424F000 leng=17244160 end=552C1000)
A RFC Destination> destination pkg-prd_PRD_00 host pkg-prd system PRD systnr 0 (pkg-prd_PRD_00)
A RFC Options> H=pkg-prd,S=00
A RFC FRFC> fallback activ but this is not a central instance.
A
A RFC rfc/signon_error_log = -1
A RFC rfc/dump_connection_info = 0
A RFC rfc/dump_client_info = 0
A RFC rfc/cp_convert/ignore_error = 1
A RFC rfc/cp_convert/conversion_char = 23
A RFC rfc/wan_compress/threshold = 251
A RFC rfc/recorder_pcs not set, use defaule value: 1
A RFC rfc/delta_trc_level not set, use default value: 0
A RFC rfc/no_uuid_check not set, use default value: 0
A RFC abap/SIGCHILD_default not set, use default value: 0
A RFC Method> initialize RemObjDriver for ABAP Objects
A Hotpackage version: 49
M ThrCreateShObjects allocated 14604 bytes at 0FFD0040
N
N Mon Feb 22 08:14:05 2010
N SsfSapSecin: putenv(SECUDIR=D:\usr\sap\PRD\DVEBMGS00\sec): ok
N
N =================================================
N === SSF INITIALIZATION:
N ===...SSF Security Toolkit name SAPSECULIB .
N ===...SSF trace level is 0 .
N ===...SSF library is D:\usr\sap\PRD\SYS\exe\run\sapsecu.dll .
N ===...SSF hash algorithm is SHA1 .
N ===...SSF symmetric encryption algorithm is DES-CBC .
N ===...sucessfully completed.
N =================================================
N MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
N MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
W =================================================
W === ipl_Init() called
W ITSP Running against db release 620!
W ITSP Disable Kernel Web GUI functionality
W === ipl_Init() returns 2, ITSPE_DISABLED: Service is disabled (sapparam)
W =================================================
E
E Mon Feb 22 08:14:39 2010
E Replication is disabled
C
C Mon Feb 22 08:15:00 2010
C sloledb.cpp [DoDbcc,line 2930]: Error/Message: (err 2571, sev 0), User 'prd' does not have permission to run DBCC CACHEPROFILE.
C Procname: [No proc]
C
C Mon Feb 22 08:15:01 2010
C statement rerun with user dbo was successful, you can ignore the preceeding message
C
C Mon Feb 22 08:16:27 2010
C Provider SQLNCLI could not be initialized. See note #734034 for more information.
C Using provider SQLOLEDB instead.
C OpenOledbConnection: MARS property was not set.
S
S Mon Feb 22 08:19:23 2010
S found spool memory service RSPO-ACTIONS at 121F4C68
A
A Mon Feb 22 08:19:55 2010
A TH VERBOSE LEVEL FULL
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c 12304]
C Rollback Work (0)
A
A Mon Feb 22 08:19:59 2010
A Mon Feb 22 08:19:59 2010
A
A ABAP/4 Program /SDF/SAPLRI_SQLSERVER .
A Source /SDF/LRI_SQLSERVERU02 Line 264.
A Error Code CALL_FUNCTION_CONFLICT_LENG.
A Module $Id: //bas/640_REL/src/krn/runt/abfunc.c#14 $ SAP.
A Function FuncParams Line 2906.
C Rollback Work (0)
C
C Mon Feb 22 08:20:00 2010
C sloledb.cpp [DoDbcc,line 2930]: Error/Message: (err 2571, sev 0), User 'prd' does not have permission to run DBCC loginfo.
C Procname: [No proc]
C
C Mon Feb 22 08:20:01 2010
C statement rerun with user dbo was successful, you can ignore the preceeding message
C
C Mon Feb 22 08:20:07 2010
C sloledb.cpp [ParamStmtExec,line 12251]: Error/Message: (err 50000, sev 0), Table not found.
C Procname: [##Y3PKG_PRDprd00000024400000003365081342]
C ParamStmtExec failed. HR 80040e14 DBSL retcode 99. stmt: [sap_get_table_size_info 'syscomments', 'prd', 'PRD'
C /* R3:CL_SQL_RESULT_SET=============CP:234 T: */
C ]
C Conn_i:2 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 222194
C dbdsmss: DBSL99 SQL50000
C Table not found.
B ***LOG BY2=> sql error 50000 performing FET [dbds#3 @ 592] [dbds 0592 ]
B ***LOG BY0=> Table not found. [dbds#3 @ 592] [dbds 0592 ]
B ***LOG BY1=> sql error 50000 [dbacds#2 @ 1187] [dbacds 1187 ]
B
B Mon Feb 22 08:26:10 2010
B dbmyclu : info : my major identification is 3232261128, minor one 0.
B dbmyclu : info : Time Reference is 1.12.2001 00:00:00h GMT.
B dbmyclu : info : my uuid is 31B87DDDE43B904B955F2E6B45F604BE.
B dbmyclu : info : current optimistic cluster level: 3
B dbmyclu : info : pessimistic reads set to 2.
N login/password_change_for_SSO : 1 -> 1
B
B Mon Feb 22 08:32:54 2010
B table logging switched off for all clients
M
M Mon Feb 22 08:45:50 2010
M PfHIndInitialize: memory=<60720150>, header=<60720150>, records=<60720180>
S
S Mon Feb 22 08:55:52 2010
S handle memory type is RSTSPROMMM
M
M Mon Feb 22 09:18:08 2010
M *** ERROR => NiProcMsg: rc=-104 (NIEROUT_SNC_FAILURE) from router [nibuf.c 423]
M *** ERROR => MsIAttachEx: NiBufConnect to /H/192.168.100.7/S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001/sapmsOSS failed (rc=NIEROUT_SNC_FAILURE) [msxxi.c 633]
M *** ERROR => LgIAttach: MsAttach (rc=NIEROUT_SNC_FAILURE) [lgxx.c 2984]
M *** ERROR => LgIGroup: LgIAttach(rc=-101) [lgxx.c 3504]
A TH VERBOSE LEVEL FULL
M
M Mon Feb 22 09:18:28 2010
M *** ERROR => NiProcMsg: rc=-104 (NIEROUT_SNC_FAILURE) from router [nibuf.c 423]
M *** ERROR => MsIAttachEx: NiBufConnect to /H/192.168.100.7/S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001/sapmsOSS failed (rc=NIEROUT_SNC_FAILURE) [msxxi.c 633]
M *** ERROR => LgIAttach: MsAttach (rc=NIEROUT_SNC_FAILURE) [lgxx.c 2984]
M *** ERROR => LgIGroup: LgIAttach(rc=-101) [lgxx.c 3504]
A TH VERBOSE LEVEL FULL
C
C Mon Feb 22 10:01:09 2010
C Rollback Work (0)
A
A Mon Feb 22 10:18:24 2010
A TH VERBOSE LEVEL FULL
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c 12304]
C Rollback Work (0)
A
A Mon Feb 22 10:18:26 2010
A Mon Feb 22 10:18:26 2010
A
A ABAP/4 Program /SDF/SAPLRI_SQLSERVER .
A Source /SDF/LRI_SQLSERVERU02 Line 264.
A Error Code CALL_FUNCTION_CONFLICT_LENG.
A Module $Id: //bas/640_REL/src/krn/runt/abfunc.c#14 $ SAP.
A Function FuncParams Line 2906.
C Rollback Work (0)
C sloledb.cpp [DoDbcc,line 2930]: Error/Message: (err 2571, sev 0), User 'prd' does not have permission to run DBCC loginfo.
C Procname: [No proc]
C statement rerun with user dbo was successful, you can ignore the preceeding message
C
C Mon Feb 22 10:18:29 2010
C sloledb.cpp [ParamStmtExec,line 12251]: Error/Message: (err 50000, sev 0), Table not found.
C Procname: [##Y3PKG_PRDprd00000024400000012657081342]
C ParamStmtExec failed. HR 80040e14 DBSL retcode 99. stmt: [sap_get_table_size_info 'syscomments', 'prd', 'PRD'
C /* R3:CL_SQL_RESULT_SET=============CP:234 T: */
C ]
C Conn_i:2 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 222194
C dbdsmss: DBSL99 SQL50000
C Table not found.
B ***LOG BY2=> sql error 50000 performing FET [dbds#3 @ 592] [dbds 0592 ]
B ***LOG BY0=> Table not found. [dbds#3 @ 592] [dbds 0592 ]
B ***LOG BY1=> sql error 50000 [dbacds#2 @ 1187] [dbacds 1187 ]
Could anybody advice me on this
Regards,
ZulHi,
I hope 440000 will not the cause,
this might occur due to many reasons,
1. make sure you have all the components(Applications,OSlevel,DBlevel) are at same level in entire the landscape.
2. you can observe the evenlogs at OSlevel to get the error information pointing to. Also check for the dumps/logs(work direcotry).
3. if not, can open SAP message.
regards
Nagaraju -
While doing SO, im getting run time error - reg;
Hi,
While doing sales order and whenever im doing save its getting runtime error.
Runtime Errors MESSAGE_TYPE_X
Date and Time 14.12.2011 10:55:26
Short dump has not been completely stored (too big)
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
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
Short text of error message:
Maintain the current CRM release (table CRMPAROLTP)
Long text of error message:
Diagnosis
Various transfer errors occur when transferring SAP sales orders to
CRM or there is no status update or the status update has errors
when transferring from CRM to the SAP system. This is caused by an
incorrect entry for the CRM release in the SAP table CRMPAROLTP, or
no entry is maintained at all.
System Response
To avoid data inconsistencies, this message causes a short dump.
Procedure
Maintain table CRMPAROLTP in your SAP system as is described in SAP
Note 691710 and then repeat the process again.
Procedure for System Administration
Technical information about the message:
Message class....... "V3"
Number.............. 302
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
Runtime Errors MESSAGE_TYPE_X
Date and Time 14.12.2011 10:55:26
hort dump has not been completely stored (too big)
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPMV45A" or "MV45AF0B_BAPIDATEN_ERMITTELN"
"BAPIDATEN_ERMITTELN"
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.
System environment
SAP-Release 700
Application server... "personal"
Network address...... "192.168.2.11"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 80686"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "PERSONAL"
Database type..... "ORACLE"
Database name..... "GCU"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 29 2006 00:18:21"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 75
Patch text.. " "
Runtime Errors MESSAGE_TYPE_X
Date and Time 14.12.2011 10:55:26
hort dump has not been completely stored (too big)
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 30311496
Heap.... 0
Page.... 139264
MM Used. 14538320
MM Free. 91952
User and Transaction
Client.............. 100
User................ "INFO_SD"
Language key........ "E"
Transaction......... "VA01 "
Program............. "SAPMV45A"
Screen.............. "SAPMV45A 4001"
Screen line......... 65
Information on where terminated
Termination occurred in the ABAP program "SAPMV45A" - in "BAPIDATEN_ERMITTELN".
The main program was "SAPMV45A ".
In the source code you have the termination point in line 338
of the (Include) program "MV45AF0B_BAPIDATEN_ERMITTELN".
Edited by: kiran35086 on Dec 14, 2011 6:30 AMDear kiran,
This might be many reasons.If you have not done configuration properly system will take you to dump(Run time error).
Try read the diagnosis possibly you may understand the problem.
If not You coordinate with your technical team.
Thanks&Regards
Raghu.k -
ALV issue: when save list using Local File command will get run time error!
help!!!!
report list using ALV method when to save this list using Local File.
i will get GETWA_NOT_ASSIGNED run time error information.
how resolve it?
source code :
REPORT ZIFT0103.
TABLES : MARA,MARC,CDHDR,CDPOS,MAKT.
******DEVK909212****************
****利用工厂来区分不同的SERVER的FTP ADDRESS ,user ,PASSWORD
DATA: FTP_WERKS LIKE MARC-WERKS.
********定义一个RANGE用来抓取MARC的信息
RANGES:R_MATNR FOR MARA-MATNR OCCURS 0.
********定义一个INTERNAL TABLE 来抓取MARC 的信息
DATA:BEGIN OF IT_MARC OCCURS 0,
MATNR LIKE MARC-MATNR,
WERKS LIKE MARC-WERKS,
USERNAME TYPE CDHDR-USERNAME,
UDATE TYPE CDHDR-UDATE,
FLAG_UI TYPE C,
END OF IT_MARC.
*******定义存放北京的数据的变量
DATA : BEGIN OF FTP_BEIJING OCCURS 0 ,
MATNR(25) ,
MATNR1(25) ,
MAKTX(30) ,
END OF FTP_BEIJING .
******定义福清的数据变量
DATA : BEGIN OF FTP_FUQING OCCURS 0 ,
MATNR(25) ,
MATNR1(25) ,
MAKTX(30) ,
END OF FTP_FUQING .
*******DEVK909212*****************
DATA : BEGIN OF FTP_ITEMDOC1 OCCURS 0 ,
MATNR(25) ,
MAKTX(30) ,
END OF FTP_ITEMDOC1 .
DATA : BEGIN OF FTP_ITEMDOC OCCURS 0 ,
MATNR(25) ,
MATNR1(25) ,
MAKTX(30) ,
END OF FTP_ITEMDOC .
DATA: WA_ZMSGTA TYPE ZMSGTA ,
l_ersda like MARA-ERSDA .
***********DEVK909553********************
****用来决定执行FTP还是显示LIST**********
DATA:g_tcode_flag.
***********DEVK909553********************
Error message process ******************************
DEFINE EXPLAIN_MSG.
break soe_richard.
CALL FUNCTION 'BAPI_MESSAGE_GETDETAIL'
EXPORTING
ID = &1 "SY-MSGID
NUMBER = &2 "SY-MSGNO
LANGUAGE = SY-LANGU
TEXTFORMAT = &3
LINKPATTERN =
MESSAGE_V1 = &4 "SY-MSGV1
MESSAGE_V2 = &5 "SY-MSGV2
MESSAGE_V3 = &6 "SY-MSGV3
MESSAGE_V4 = &7 "SY-MSGV4
IMPORTING
MESSAGE = &8 "WA_ZMSGTA-MSE1
RETURN =
TABLES
TEXT =
END-OF-DEFINITION.
DEFINE ERROR_MSG_UPDATA.
CALL FUNCTION 'ZINSERT_MSG' "IN UPDATE TASK
EXPORTING
XZMSGTA = &1 "WA_ZMSGTA
EXCEPTIONS
UPDATE_ERROR = 1
OTHERS = 2.
END-OF-DEFINITION.
IF SY-TCODE = 'ZIFT103' .
g_tcode_flag = 'L'.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
PERCENTAGE = 0
TEXT = '请耐心等候,系统正在抓数据'.
ENDIF.
l_ersda = sy-datum - 1 . "取前一天产生的物料号码。
DATA:BEGIN OF it_change OCCURS 0,
OBJECTID TYPE CDHDR-OBJECTID,
USERNAME TYPE CDHDR-USERNAME,
UDATE TYPE CDHDR-UDATE,
TABKEY TYPE CDPOS-TABKEY,
END OF it_change.
DATA:BEGIN OF it_cDhdr OCCURS 0,
OBJECTID type CDHDR-OBJECTID,
CHANGENR TYPE CDHDR-CHANGENR,
USERNAME TYPE CDHDR-USERNAME,
UDATE TYPE CDHDR-UDATE,
END OF it_cdhdr.
DATA:search_len TYPE I.
DATA:BEGIN of it_insert OCCURS 0,
MATNR TYPE MARA-MATNR,
WERKS TYPE MARC-WERKS,
END OF it_insert.
DATA:BEGIN OF it_MAKT OCCURS 0,
MATNR TYPE MAKT-MATNR,
MAKTX TYPE MAKT-MAKTX,
END OF it_makt.
DATA IT_MARA TYPE TABLE OF MARA WITH HEADER LINE.
DATA:BEGIN OF IT_OUT OCCURS 0,
MATNR TYPE MARA-MATNR,
WERKS TYPE MARC-WERKS,
MTART TYPE MARA-MTART,
MEINS TYPE MARA-MEINS,
MATKL TYPE MARA-MATKL,
MAKTX TYPE MAKT-MAKTX,
PSTAT TYPE MARA-PSTAT,
BRGEW TYPE MARA-BRGEW,
NTGEW TYPE MARA-NTGEW,
GEWEI TYPE MARA-GEWEI,
FERTH TYPE MARA-FERTH,
KZUMW TYPE MARA-KZUMW,
ERNAM TYPE MARA-ERNAM,
ERSDA TYPE MARA-ERSDA,
END OF IT_OUT.
*-- DECLARE DATA FOR ALV
TYPE-POOLS: slis.
DATA : g_variant LIKE disvariant,
g_save(1) TYPE c,
g_exit(1) TYPE c,
gx_variant LIKE disvariant.
DATA: gt_fieldcat TYPE slis_t_fieldcat_alv WITH HEADER LINE, "
gt_events TYPE slis_t_event,
gt_list_top_of_page TYPE slis_t_listheader,
gs_print TYPE slis_print_alv,
gs_layout TYPE slis_layout_alv .
******只能抓出系统有做更改的数据***************
******而第一次INSERT MARA的数据抓不出来********
START-OF-SELECTION.
SELECT AOBJECTID AUSERNAME AUDATE BTABKEY
INTO TABLE it_change
FROM ( CDPOS AS B INNER JOIN CDHDR AS A ON
AOBJECTCLAS = BOBJECTCLAS AND
AOBJECTID = BOBJECTID AND
ACHANGENR = BCHANGENR )
WHERE A~OBJECTCLAS = 'MATERIAL'
AND A~UDATE = l_ersda
AND B~TABNAME = 'MARC'
AND B~CHNGIND = 'I'.
LOOP AT it_change.
search_len = STRLEN( it_change-TABKEY ).
search_len = search_len - 4.
IF search_len > 0.
IT_MARC-WERKS = it_change-TABKEY+search_len(4).
ENDIF.
IT_MARC-MATNR = it_change-objectid+0(18).
IT_MARC-USERNAME = it_change-username.
IT_MARC-UDATE = It_change-udate.
IT_MARC-FLAG_UI = 'U'.
APPEND IT_MARC.
CLEAR IT_MARC.
CLEAR R_MATNR.
R_MATNR-SIGN = 'I'.
R_MATNR-OPTION = 'EQ'.
R_MATNR-LOW = IT_MARC-MATNR.
APPEND R_MATNR.
ENDLOOP.
****CDPOS is Cluster TABLE 所以没有办法用INNER JOIN******
SELECT OBJECTID CHANGENR USERNAME UDATE
INTO TABLE it_cdhdr
FROM CDHDR
WHERE OBJECTCLAS = 'MATERIAL'
AND UDATE = l_ersda.
AND TCODE = 'MM02'.
LOOP AT IT_cdhdr.
SELECT * FROM CDPOS
WHERE OBJECTCLAS = 'MATERIAL'
AND OBJECTID = IT_CDHDR-OBJECTID
AND CHANGENR = IT_CDHDR-CHANGENR
AND TABNAME = 'MARC'
AND CHNGIND = 'I'.
search_len = STRLEN( CDPOS-TABKEY ).
search_len = search_len - 4.
IF search_len > 0.
IT_MARC-WERKS = CDPOS-TABKEY+search_len(4).
ENDIF.
IT_MARC-MATNR = IT_cdhdr-objectid+0(18).
IT_MARC-USERNAME = IT_cdhdr-username.
IT_MARC-UDATE = IT_cdhdr-udate.
IT_MARC-FLAG_UI = 'U'.
APPEND IT_MARC.
CLEAR IT_MARC.
CLEAR R_MATNR.
R_MATNR-SIGN = 'I'.
R_MATNR-OPTION = 'EQ'.
R_MATNR-LOW = IT_MARC-MATNR.
APPEND R_MATNR.
CLEAR IT_MARC.
ENDSELECT.
ENDLOOP.
IF g_tcode_flag = 'L'.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
PERCENTAGE = 20
TEXT = '处理好当天CHANGE的数据'.
ENDIF.
*******抓当天做了INSERT的数据*************
*******不需要***********************
SELECT BMATNR BWERKS INTO TABLE IT_INSERT
FROM MARC AS B JOIN MARA AS A
ON AMATNR = BMATNR
WHERE A~ERSDA = l_ersda.
LOOP AT IT_INSERT.
IT_MARC-MATNR = IT_INSERT-MATNR.
IT_MARC-WERKS = IT_INSERT-WERKS.
IT_MARC-FLAG_UI = 'I'.
APPEND IT_MARC.
CLEAR IT_MARC.
CLEAR R_MATNR.
R_MATNR-SIGN = 'I'.
R_MATNR-OPTION = 'EQ'.
R_MATNR-LOW = IT_MARC-MATNR.
APPEND R_MATNR.
ENDLOOP.
IF g_tcode_flag = 'L'.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
PERCENTAGE = 40
TEXT = '处理好当天INSERT的数据'.
ENDIF.
IF g_tcode_flag = 'L'.
PERFORM get_MAKTX.
PERFORM get_mara.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
PERCENTAGE = 100
TEXT = '处理好数据,并开始显示数据'.
PERFORM do_data.
PERFORM display_alv.
ELSE.
PERFORM get_MAKTX.
PERFORM do_ftp.
ENDIF.
*& Form get_marktx
text
FORM get_maktx.
SELECT MATNR MAKTX INTO TABLE IT_MAKT FROM MAKT
WHERE MATNR IN R_MATNR AND SPRAS = '1'.
ENDFORM. "get_marktx
*& Form get_mara
text
FORM get_mara.
SELECT * INTO TABLE it_mara FROM MARA
WHERE MATNR IN R_MATNR.
ENDFORM. "get_mara
*& Form do_data
text
FORM do_data.
SORT IT_MARC BY MATNR WERKS.
DELETE ADJACENT DUPLICATES FROM IT_MARC COMPARING MATNR WERKS.
LOOP AT IT_MARC.
CLEAR IT_MAKT.
CLEAR IT_MARA.
READ TABLE IT_MAKT WITH KEY MATNR = IT_MARC-MATNR.
READ TABLE IT_MARA WITH KEY MATNR = IT_MARC-MATNR.
MOVE-CORRESPONDING IT_MARA TO IT_OUT.
IT_OUT-MAKTX = IT_MAKT-MAKTX.
IT_OUT-WERKS = IT_MARC-WERKS.
IF IT_MARC-FLAG_UI = 'U'.
IT_OUT-ERNAM = IT_MARC-USERNAME.
ENDIF.
APPEND IT_OUT.
CLEAR IT_OUT.
ENDLOOP.
ENDFORM. "do_data
*SELECT AMATNR BMAKTX INTO CORRESPONDING
*FIELDS OF FTP_ITEMDOC1 FROM MARA AS A JOIN MAKT AS B
*ON AMATNR = BMATNR WHERE A~ERSDA = l_ersda
*AND B~SPRAS = '1' . "代表为中文说明。
APPEND FTP_ITEMDOC1.
*******DEVK909212****************
*******添加RANGE*****************
CLEAR R_MATNR.
R_MATNR-SIGN = 'I'.
R_MATNR-OPTION = 'EQ'.
R_MATNR-LOW = FTP_ITEMDOC1-MATNR.
APPEND R_MATNR.
CLEAR FTP_ITEMDOC1.
*******DEVK909212****************
*ENDSELECT.
*******DEVK909212****************
****get WERKS information from MARC*******
*SELECT MATNR WERKS INTO TABLE IT_MARC
*FROM MARC
*WHERE MATNR IN R_MATNR.
*******DEVK909212****************
******DEVK909212****************
**MARK**************************
*LOOP AT FTP_ITEMDOC1 .
MOVE : FTP_ITEMDOC1-MATNR TO FTP_ITEMDOC-MATNR,
FTP_ITEMDOC1-MATNR TO FTP_ITEMDOC-MATNR1,
FTP_ITEMDOC1-MAKTX TO FTP_ITEMDOC-MAKTX.
APPEND FTP_ITEMDOC.
CLEAR FTP_ITEMDOC.
*ENDLOOP.
******DEVK909212****************
******DEVK909212***********************************
**根据IT_MARC中信息,往北京和福清的TABLE写数据*****
FORM do_ftp.
LOOP AT IT_MARC.
***福清的
IF IT_MARC-WERKS = '1010' OR IT_MARC-WERKS = '1020'
OR IT_MARC-WERKS = '1023' .
READ TABLE FTP_ITEMDOC1 WITH KEY MATNR = IT_MARC-MATNR.
MOVE : FTP_ITEMDOC1-MATNR TO FTP_FUQING-MATNR,
FTP_ITEMDOC1-MATNR TO FTP_FUQING-MATNR1,
FTP_ITEMDOC1-MAKTX TO FTP_FUQING-MAKTX.
CLEAR IT_MAKT.
READ TABLE IT_MAKT WITH KEY = IT_MARC-MATNR.
MOVE : IT_MARC-MATNR TO FTP_FUQING-MATNR,
IT_MARC-MATNR TO FTP_FUQING-MATNR1,
IT_MAKT-MAKTX TO FTP_FUQING-MAKTX.
APPEND FTP_FUQING.
CLEAR FTP_FUQING.
ENDIF.
***北京的
IF IT_MARC-WERKS = '1041' OR IT_MARC-WERKS = '1042'.
READ TABLE FTP_ITEMDOC1 WITH KEY MATNR = IT_MARC-MATNR.
MOVE : FTP_ITEMDOC1-MATNR TO FTP_BEIJING-MATNR,
FTP_ITEMDOC1-MATNR TO FTP_BEIJING-MATNR1,
FTP_ITEMDOC1-MAKTX TO FTP_BEIJING-MAKTX.
CLEAR IT_MAKT.
READ TABLE IT_MAKT WITH KEY = IT_MARC-MATNR.
MOVE : IT_MARC-MATNR TO FTP_BEIJING-MATNR,
IT_MARC-MATNR TO FTP_BEIJING-MATNR1,
IT_MAKT-MAKTX TO FTP_BEIJING-MAKTX.
APPEND FTP_BEIJING.
CLEAR FTP_BEIJING.
ENDIF.
ENDLOOP.
****清楚重复的数据**********
SORT FTP_FUQING.
DELETE ADJACENT DUPLICATES FROM FTP_FUQING.
SORT FTP_BEIJING.
DELETE ADJACENT DUPLICATES FROM FTP_BEIJING.
***传送数据********
REFRESH FTP_ITEMDOC.
FTP_ITEMDOC[] = FTP_FUQING[].
FTP_WERKS = '1010'.
PERFORM ftp_work.
REFRESH FTP_ITEMDOC.
FTP_ITEMDOC[] = FTP_BEIJING[].
FTP_WERKS = '1041'.
PERFORM ftp_work.
******DEVK909212***********************************
ENDFORM. "do_ftp
*& Form ftp_work
把以前FTP的工作做一个FORM
*******DEVK909212**************************
FORM ftp_work.
*******DEVK909212**************************
CHECK FTP_ITEMDOC[] IS NOT INITIAL.
FTP function *****************************************************
DATA : HDL TYPE I,
L_SLEN TYPE I ,
ERROR,
KEY TYPE I VALUE 26101957,
DEST TYPE RFCDES-RFCDEST VALUE 'SAPFTPA'.
DATA: FTP_RESULT TYPE TABLE OF TEXT.
DATA: P_FILE TYPE RLGRAP-FILENAME.
DATA: L_USER(16) TYPE C VALUE 'SFIS',
L_PWD(16) TYPE C VALUE 'SFIS',
L_HOST(16) TYPE C VALUE '172.16.31.17'.
*******DEVK909212**************************
*****根据不同的工厂来抓FTP的信息
CALL FUNCTION 'Z_FTP_SFIS'
EXPORTING
BLART = 'S'
WERKS = FTP_WERKS
IMPORTING
HOST = L_HOST
USER1 = L_USER
PASS1 = L_PWD.
*******DEVK909212**************************
CONCATENATE l_ersda '.KP' INTO P_FILE.
SET EXTENDED CHECK OFF.
ERROR = 0.
CHECK HDL IS INITIAL.
Connect to server
L_SLEN = STRLEN( L_PWD ).
CALL FUNCTION 'HTTP_SCRAMBLE'
EXPORTING
SOURCE = L_PWD
SOURCELEN = L_SLEN
KEY = KEY
IMPORTING
DESTINATION = L_PWD.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
TEXT = 'Connect to FTP Server'.
CALL FUNCTION 'FTP_CONNECT'
EXPORTING
USER = L_USER
PASSWORD = L_PWD
HOST = L_HOST
RFC_DESTINATION = DEST
IMPORTING
HANDLE = HDL
EXCEPTIONS
NOT_CONNECTED = 1
OTHERS = 2.
IF SY-SUBRC <> 0.
MOVE: 'B' TO WA_ZMSGTA-BLART,
l_ersda TO WA_ZMSGTA-REFNUMBER,
SY-MSGTY TO WA_ZMSGTA-MSGTY,
'MARA' TO WA_ZMSGTA-TBMA_VAL.
EXPLAIN_MSG SY-MSGID SY-MSGNO ' ' SY-MSGV1 SY-MSGV2 SY-MSGV3
SY-MSGV4 WA_ZMSGTA-MSE1.
ERROR_MSG_UPDATA WA_ZMSGTA.
EXIT.
ENDIF.
CALL FUNCTION 'FTP_COMMAND'
EXPORTING
HANDLE = HDL
COMMAND = 'ascii'
TABLES
DATA = FTP_RESULT
EXCEPTIONS
TCPIP_ERROR = 1
COMMAND_ERROR = 2
DATA_ERROR = 3.
IF SY-SUBRC <> 0.
EXPLAIN_MSG SY-MSGID SY-MSGNO ' ' SY-MSGV1 SY-MSGV2 SY-MSGV3
SY-MSGV4 WA_ZMSGTA-MSE1.
MOVE: 'B' TO WA_ZMSGTA-BLART,
l_ersda TO WA_ZMSGTA-REFNUMBER,
SY-MSGTY TO WA_ZMSGTA-MSGTY,
'MARA' TO WA_ZMSGTA-TBMA_VAL.
ERROR_MSG_UPDATA WA_ZMSGTA.
EXIT.
ENDIF.
CALL FUNCTION 'FTP_R3_TO_SERVER'
EXPORTING
HANDLE = HDL
FNAME = P_FILE
CHARACTER_MODE = 'X'
TABLES
TEXT = FTP_ITEMDOC
EXCEPTIONS
TCPIP_ERROR = 1
COMMAND_ERROR = 2
DATA_ERROR = 3
OTHERS = 4.
IF SY-SUBRC <> 0.
EXPLAIN_MSG SY-MSGID SY-MSGNO ' ' SY-MSGV1 SY-MSGV2 SY-MSGV3
SY-MSGV4 WA_ZMSGTA-MSE1.
MOVE: 'B' TO WA_ZMSGTA-BLART,
l_ersda TO WA_ZMSGTA-REFNUMBER,
SY-MSGTY TO WA_ZMSGTA-MSGTY,
'MARA' TO WA_ZMSGTA-TBMA_VAL.
ERROR_MSG_UPDATA WA_ZMSGTA.
EXIT.
ENDIF.
*******DEVK909212**************************
*******CLOSE FTP******************
CHECK NOT HDL IS INITIAL.
CALL FUNCTION 'FTP_DISCONNECT'
EXPORTING
HANDLE = HDL.
CALL FUNCTION 'RFC_CONNECTION_CLOSE'
EXPORTING
DESTINATION = DEST
EXCEPTIONS
OTHERS = 1.
CLEAR HDL.
ENDFORM. "ftp_work
*******DEVK909212**************************
FORM DISPLAY_ALV .
*-- PREPARE ALV DATA
PERFORM EVENTTAB_BUILD USING GT_EVENTS[].
PERFORM COMMENT_BUILD USING GT_LIST_TOP_OF_PAGE[].
*-- LAYOUT SETTING
PERFORM PREPARE_ALV_FIELD USING GT_FIELDCAT[].
*-- ALV DISPLAY
PERFORM CALL_REUSE_ALV_GRID_DISPLAY.
ENDFORM. " display_alv
*& Form eventtab_build
text
-->P_GT_EVENTS[] text
FORM EVENTTAB_BUILD USING PT_EVENTS TYPE SLIS_T_EVENT.
DATA: LS_EVENT TYPE SLIS_ALV_EVENT.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
I_LIST_TYPE = 0
IMPORTING
ET_EVENTS = PT_EVENTS.
READ TABLE PT_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
INTO LS_EVENT.
IF SY-SUBRC = 0.
LS_EVENT-FORM = 'TOP_OF_PAGE'.
MODIFY PT_EVENTS FROM LS_EVENT INDEX SY-TABIX.
ENDIF.
ENDFORM. " eventtab_build
*& Form comment_build
text
-->P_GT_LIST_TOP_OF_PAGE[] text
FORM COMMENT_BUILD USING PT_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA: LS_LINE TYPE SLIS_LISTHEADER,
L_DATE(30),
l_v_BWKEY like T001W-BWKEY, "Valuation area
l_v_BUKRS like T001K-BUKRS. "Firm/Company
Listenerschrift: Typ H
CLEAR LS_LINE.
LS_LINE-TYP = 'H'.
LS_LINE-KEY: not used for this type
select single BWKEY
into l_v_BWKEY
from t001w
where WERKS IN s_WERKS.
select single BUKRS
into l_v_BUKRS
from t001k
where BWKEY = l_v_BWKEY.
SELECT SINGLE butxt INTO LS_LINE-INFO
FROM t001
WHERE bukrs = l_v_BUKRS.
APPEND LS_LINE TO PT_TOP_OF_PAGE.
Kopfinfo: Typ S
CLEAR LS_LINE.
LS_LINE-TYP = 'S'.
LS_LINE-KEY = '报表名称:'.
LS_LINE-INFO = SY-TITLE.
APPEND LS_LINE TO PT_TOP_OF_PAGE.
CLEAR LS_LINE.
LS_LINE-TYP = 'S'.
LS_LINE-KEY = '打印日期:'.
WRITE SY-DATUM TO LS_LINE-INFO.
ls_line-info = sy-datum.
APPEND LS_LINE TO PT_TOP_OF_PAGE.
CLEAR LS_LINE.
LS_LINE-TYP = 'S'.
LS_LINE-KEY = '打印時間:'.
WRITE SY-UZEIT TO LS_LINE-INFO.
ls_line-info = sy-uzeit.
APPEND LS_LINE TO PT_TOP_OF_PAGE.
CLEAR LS_LINE.
LS_LINE-TYP = 'S'.
LS_LINE-KEY = '使用者:'.
LS_LINE-INFO = SY-UNAME.
APPEND LS_LINE TO PT_TOP_OF_PAGE.
ENDFORM. " comment_build
*& Form prepare_alv_field
text
-->P_GT_FIELDCAT[] text
FORM PREPARE_ALV_FIELD USING P_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV.
DATA: LS_LINE TYPE SLIS_FIELDCAT_ALV.
*-- DEFINE MARCO
DEFINE APPEND_ALV_FIELD.
CLEAR LS_LINE.
LS_LINE-FIELDNAME = &1.
LS_LINE-TABNAME = &2.
LS_LINE-REPTEXT_DDIC = &3.
LS_LINE-SELTEXT_L = &3.
LS_LINE-SELTEXT_M = &3.
LS_LINE-SELTEXT_S = &3.
LS_LINE-QFIELDNAME = &4.
LS_LINE-QTABNAME = &5.
LS_LINE-NO_OUT = &6.
LS_LINE-NO_ZERO = &7.
LS_LINE-OUTPUTLEN = &8.
APPEND LS_LINE TO P_FIELDCAT.
END-OF-DEFINITION.
APPEND_ALV_FIELD: 'MATNR' 'IT_OUT' '料号'
'O' 'X' ''.
APPEND_ALV_FIELD: 'WERKS' 'IT_OUT' '工厂'
'O' 'X' ''.
APPEND_ALV_FIELD: 'MTART' 'IT_OUT' 'MTyp'
'O' 'X' ''.
APPEND_ALV_FIELD: 'MEINS' 'IT_OUT' 'BUn'
'O' 'X' ''.
APPEND_ALV_FIELD: 'MATKL' 'IT_OUT' '物料组\分群码'
'O' 'X' ''.
APPEND_ALV_FIELD: 'MATKX' 'IT_OUT' '物料描述'
'O' 'X' ''.
APPEND_ALV_FIELD: 'PSTAT' 'IT_OUT' '维护状态'
'O' 'X' ''.
APPEND_ALV_FIELD: 'BRGEW' 'IT_OUT' '毛重'
'O' 'X' ''.
APPEND_ALV_FIELD: 'NTGEW' 'IT_OUT' '净重'
'O' 'X' ''.
APPEND_ALV_FIELD: 'GEWEI' 'IT_OUT' 'WUn'
'O' 'X' ''.
APPEND_ALV_FIELD: 'FERTH' 'IT_OUT' '对外机种名'
'O' 'X' ''.
APPEND_ALV_FIELD: 'KZUMW' 'IT_OUT' '高关税标识'
'O' 'X' ''.
APPEND_ALV_FIELD: 'ERNAM' 'IT_OUT' '创建者'
'O' 'X' ''.
APPEND_ALV_FIELD: 'ERSDA' 'IT_OUT' '创建日期'
'O' 'X' ''.
ENDFORM. " prepare_alv_field
*& Form call_reuse_alv_grid_display
text
--> p1 text
<-- p2 text
FORM CALL_REUSE_ALV_GRID_DISPLAY .
gs_layout-f2code = 'DISPLAY'.
gs_print-no_print_listinfos = 'X'.
gs_layout-colwidth_optimize = 'X'. "列宽度自动根据内容优化
gs_layout-f2code = '&ETA'. "double check弹出详细信息
gs_layout-zebra = 'X'. "清单条纹显示
gs_layout-no_vline = ''. "是否显示列间隔线
gs_layout-box_fieldname = ''. "是否显示checkbox
gs_layout-confirmation_prompt = ''. "推出清单是否提示
gs_layout-detail_titlebar = '详细信息'."详细清单的标题
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = SY-CPROG
I_BACKGROUND_ID = 'ALV_BACKGROUND'
I_CALLBACK_PF_STATUS_SET = 'ALV_PF_STATUS'
I_CALLBACK_USER_COMMAND = 'ALV_USER_COMMAND'
I_CALLBACK_TOP_OF_PAGE = GT_LIST_TOP_OF_PAGE[]
IT_FIELDCAT = GT_FIELDCAT[]
IT_EVENTS = GT_EVENTS[]
I_STRUCTURE_NAME = 'IT_OUT'
I_SAVE = 'A'
IS_LAYOUT = GS_LAYOUT
IS_PRINT = GS_PRINT
TABLES
T_OUTTAB = IT_OUT
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " call_reuse_alv_grid_display
*& Form PREPARE_ALV_FIELD
FORM TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = GT_LIST_TOP_OF_PAGE.
ENDFORM. "TOP_OF_PAGEHi,
Please check your field catalog and refer field names once again.
Check spelling, or Check strucutre properly.
There are something wrong in your catalog definition
aRs. -
Dear ALL,
When we are creating sales order after entering sold-to-party, Material & Quantity when we press ENTER key That time
we are getting following run time error
Hoe to resolve this?
Runtime Errors SAPSQL_INVALID_FIELDNAME
Except. CX_SY_DYNAMIC_OSQL_SEMANTICS
Date and Time 15.01.2009 16:04:19
Short dump has not been completely stored (too big)
Short text
A dynamically specified column name is unknown.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLV61Z" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
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
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was
not caught in
procedure "SEL_KONDTAB" "(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:
An Open SQL clause was specified dynamically. The contained field name
"ALAND" does not exist in any of the database tables from the FROM clause.
How to correct the error
Check the field name in the SELECT clause.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"SAPSQL_INVALID_FIELDNAME" "CX_SY_DYNAMIC_OSQL_SEMANTICS"
"SAPLV61Z" or "LV61ZU01"
"SEL_KONDTAB"
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.
The exception must either be prevented, caught within proedure
"SEL_KONDTAB" "(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 700
Application server... "slgsap-prd"
Network address...... "10.140.1.11"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SLGSAP-PRD"
Database type..... "MSSQL"
Database name..... "PRD"
Database user ID.. "prd"
Terminal................. "SD0123l"
Char.set.... "C"
SAP kernel....... 700
created (date)... "May 6 2008 00:13:21"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 159
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 20949200
Heap.... 0
Page.... 196608
MM Used. 15928048
MM Free. 828016
User and Transaction
Client.............. 900
User................ "ADMIN"
Language key........ "E"
Transaction......... "VA01 "
Transactions ID..... "03F0E2DD6B35F16CBBFF002219897F24"
Program............. "SAPLV61Z"
Screen.............. "SAPMV45A 4900"
Screen line......... 930
Information on where terminated
Termination occurred in the ABAP program "SAPLV61Z" - in "SEL_KONDTAB".
The main program was "SAPMV45A ".
In the source code you have the termination point in line 672
of the (Include) program "LV61ZU01".
The termination is caused because exception "CX_SY_DYNAMIC_OSQL_SEMANTICS"
occurred in
procedure "SEL_KONDTAB" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "SAPLV61Z "; its source code begins in line
260 of the (Include program "LV61ZU01 ".
Source Code Extract
Line SourceCde
642 if se_prestep = yes or
643 se_read_only_one_record = yes.
644 if t681-ksdat is initial.
645 if se_read_all_prestep is initial.
646 select * from (t681-kotab) appending table <cond_tab>
647 up to 1 rows
648 where kappl = se_kappl
649 and kschl = se_kschl
650 and (coding_tab).
651 h_subrc = sy-subrc.
652 else.
653 select * from (t681-kotab) appending table <cond_tab>
654 where kappl = se_kappl
655 and kschl = se_kschl
656 and (coding_tab).
657 endif.
658
659 * it is enough to find one record in prestep
660 * (care must be taken with pool tables - depending on database this
661 * will cost performance instead of saving)
662 if select_split ne 0 and h_subrc ne 0.
663 modify coding_tab from coding_alter index select_split.
664 select * from (t681-kotab) appending table <cond_tab>
665 up to 1 rows
666 where kappl = se_kappl
667 and kschl = se_kschl
668 and (coding_tab).
669 endif.
670 else.
671 if se_read_all_prestep is initial.
>>>>> select * from (t681-kotab) appending table <cond_tab>
673 up to 1 rows
674 where kappl = se_kappl
Regards,
Akshay
Edited by: Akshay Dalal on Jan 17, 2009 6:25 AM
Edited by: Akshay Dalal on Jan 17, 2009 6:30 AMDear Akshay,
We will NOT be able to provide you with a solution on this forum, because we have no clue what configuration do you have in your system and what user exits or other custom development may have been done in your specific system.
Lakshmipathi has already correctly pointed to a similar post. You might want to get an ABAPer to set a breakpoint just before the error occurs, then he/she might provide you with more information, which may (or may not) be helpful.
There is obviously something wrong in the pricing condition either on configuration level or in a user exit. If you write to SAP (which you should, because it's a standard program), they will ask to connect to your system, because they don't have any chrystal balls over there either.
Just in case - before going any further, try running the program RV80HGEN (in the test system, of course), which re-generates requirements and formulas. Sometimes it helps, although I doubt that it is the case here.
Also if you've used some custom (Z...) fields in the pricing configuration, that's where the problem is most likely. -
Package failed with run time error: " GETWA_NOT_ASSIGNED".
Hi,
One of our custom package is failing with run time error " GETWA_NOT_ASSIGNED". We are getting this error after refresh. Infact this package is working fine both in production and Dev, but in QA system it giving runtime error.
Here with I am pasting run time error details. Please see...If any one have any idea or clue or if you have faced this kind of error.
Thanks is advance.
Error Details.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_UJK_CUSTOM_LOGIC===========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
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
You attempted to access an unassigned field symbol
(data segment 32774).
This error may occur if
- You address a typed field symbol before it has been set with
ASSIGN
- You address a field symbol that pointed to the line of an
internal table that was deleted
- You address a field symbol that was previously reset using
UNASSIGN or that pointed to a local field that no
longer exists
- You address a global function interface, although the
respective function module is not active - that is, is
not in the list of active calls. The list of active calls
can be taken from this short dump.
Regards, TrineHi Trine,
the error is about some field you are trying to map using field-simbols, that is diferent in the other system.
Go to the code program in the st22, there you will see when the erros occurs e what field gives the error.
Best Regards,
António -
We are geting following run time error when executeing QA32 t-code of QM , error as follows ,
Error analysis
After a specific time, the program is terminated to make the work area
available to other users who may be waiting.
This is to prevent a work area being blocked unnecessarily long by, for
example:
- Endless loops (DO, WHILE, ...),
- Database accesses with a large result set
- Database accesses without a suitable index (full table scan)
The maximum runtime of a program is limited by the system profile
parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this
time limit is
exceeded, the system attempts to cancel any running SQL statement or
signals the ABAP processor to stop the running program. Then the system
waits another 60 seconds maximum. If the program is then still active,
the work process is restarted.
How to correct the error
Programs with long runtime should generally be started as background
jobs. If this is not possible, you can increase the system profile
parameter "rdisp/max_wprun_time".
Depending on the cause of the error, you may have to take one of the
following measures:
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
(for example);
- Database has unsuitable index: Check index generation.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
Runtime Errors TIME_OUT
Date and Time 30.06.2009 10:17:31
Short dump has not been completely stored (too big)
If you have access to SAP Notes, carry out a search with the following
keywords:
"TIME_OUT" " "
"SAPLBSVA" or "LBSVAU14"
"STATUS_PRE_READ"
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.
System environment
SAP-Release 700
Application server... "GALT"
Network address...... "202.54.13.238"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 80686"
Character length.... 8 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "GALT"
Database type..... "ORACLE"
Database name..... "PRD"
Database user ID.. "SAPSR3"
Char.set.... "English_United State"
SAP kernel....... 700
created (date)... "Oct 13 2006 00:08:41"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 80
Patch text.. " "
Runtime Errors TIME_OUT
Date and Time 30.06.2009 10:17:31
Short dump has not been completely stored (too big)
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8112
EM...... 16724736
Heap.... 0
Page.... 450560
MM Used. 6688784
MM Free. 626280
User and Transaction
Client.............. 400
User................ "MGMTSER"
Language key........ "E"
Transaction......... "QA11 "
Program............. "SAPLBSVA"
Screen.............. "SAPMQEVA 0200"
Screen line......... 41
Information on where terminated
Termination occurred in the ABAP program "SAPLBSVA" - in "STATUS_PRE_READ".
The main program was "SAPMQEVA ".
In the source code you have the termination point in line 61
of the (Include) program "LBSVAU14".
Source Code Extract
Line SourceCde
31
32 OBJNR_TAB[] = JSTO_PRE_TAB[].
33
34 * Merken: jeweils bisherige Anzahl Einträge im Puffer
35 DESCRIBE TABLE JSTO_BUF LINES JSTO_BUF_LINES.
36 DESCRIBE TABLE JEST_BUF LINES JEST_BUF_LINES.
37 DESCRIBE TABLE OBJNR_TAB LINES OBJNR_TAB_LINES. "Note978655
38 ADD 1 TO JSTO_BUF_LINES.
39
40 l_percentage = OBJNR_TAB_LINES * 100 / JSTO_BUF_LINES. "Note978655
41 * Small number of object numbers to be read, insert records "Note978655
42 * sequentially to avoid expensive SORT on JSTO_BUF,JEST_BUF "Note978655
43 IF ( l_percentage <= 1 OR OBJNR_TAB_LINES < 20 ) AND "Note978655
44 get_change_documents IS INITIAL. "Note978655
45 LOOP AT objnr_tab. "Note978655
46 SELECT * FROM JSTO CLIENT SPECIFIED "Note978655
47 FOR ALL ENTRIES IN OBJNR_TAB "Note978655
48 WHERE MANDT EQ CLIENT "Note978655
49 AND OBJNR = OBJNR_TAB-OBJNR. "Note978655
50 READ TABLE JSTO_BUF WITH KEY MANDT = JSTO-MANDT "Note978655
51 OBJNR = JSTO-OBJNR "Note978655
52 BINARY SEARCH. "Note978655
53 IF SY-SUBRC <> 0. "Note978655
Runtime Errors TIME_OUT
Date and Time 30.06.2009 10:17:31
Short dump has not been completely stored (too big)
54 JSTO_BUF = JSTO. "Note978655
55 CLEAR JSTO_BUF-MOD. "Note978655
56 JSTO_BUF-STSMA_OLD = JSTO_BUF-STSMA. "Note978655
57 INSERT JSTO_BUF INDEX SY-TABIX. "Note978655
58 ENDIF. "Note978655
59 ENDSELECT. "Note978655
60 "Note978655
>>>>> SELECT * FROM JEST CLIENT SPECIFIED "Note978655
62 FOR ALL ENTRIES IN OBJNR_TAB "Note978655
63 WHERE MANDT EQ CLIENT "Note978655
64 AND OBJNR = OBJNR_TAB-OBJNR. "Note978655
65 READ TABLE JEST_BUF WITH KEY MANDT = JEST-MANDT "Note978655
66 OBJNR = JEST-OBJNR "Note978655
67 STAT = JEST-STAT "Note978655
68 BINARY SEARCH. "Note978655
69 IF SY-SUBRC <> 0. "Note978655
70 JEST_BUF = JEST. "Note978655
71 CLEAR JEST_BUF-MOD. "Note978655
72 JEST_BUF-INACT_OLD = JEST_BUF-INACT. "Note978655
73 INSERT JEST_BUF INDEX SY-TABIX. "Note978655
74 ENDIF. "Note978655
75 ENDSELECT. "Note978655
76 ENDLOOP. "Note978655
77 CLEAR: JSTO_BUF,JEST_BUF. "Note978655
78 EXIT. "Note978655
79 ENDIF. "Note978655
80
Contents of system fields
Name Val.
SY-SUBRC0
SY-INDEX0
SY-TABIX15
SY-DBCNT15
SY-FDPOS1
SY-LSIND0
SY-PAGNO0
SY-LINNO1
SY-COLNO1
SY-PFKEYA101
SY-UCOMMBU
SY-TITLE Record Usage Decision: Characteristic Overview
SY-MSGTY
SY-MSGID
SY-MSGNO000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO0
SY-DATUM20090630
SY-UZEIT101723
SY-XPROGSAPLQAMB
SY-XFORMCONVERSION_EXIT
Edited by: Raghavendra Balegar on Jul 3, 2009 12:21 PMNo Dear,
Not at all. I think it should work for atleast one month period.
But sometimes depending on the database size and hardware, this criteria can vary.
Regds,
Anil -
Frequent run-time errors during audio recording
While recording audio voice-over for a slide, I'll often do
several "takes" before finding the best one. All too frequently,
when I click OK, I encounter a run-time error that terminates the
Captivate 2 software. I've done the default installation on two
machines and encountered the same problem on both. Are other users
running into this problem as well? Any fixes / workarounds to
suggest? Is this problem fixed with Captivate 3?
Below is the message that appears.
Title Bar: Microsoft Visual C++ Runtime Library
Messaqe Text: Program: C:\Program Files\Adobe\Adobe Captivate
2\AdobeCaptivate.exe
This application has requested the Runtime to terminate it in
an unusual way. Please contact the application's support team for
more information.
Any input would be greatly appreciated. Thanks!Hi folks,
The first thing I would do is to remove the .dat file that
can be found via the following path:
C:\Document and Settings\Username\Application
Data\Adobe\Adobe Captivate\
Rename the captivate_v20.dat to something like
Old_captivate_v20.dat and then start up Adobe Captivate.
If this doesn't address the problem then report this as a bug
using the
Adobe
Captivate Feature Request/Bug Report Form
Let us know how you get on.
Best - Mark -
Run time error CONVT_OVERFLOW
dear Sir
we have window 7 for new oc as soon runned teh program cv01n i got run time error msg CX_SY_CONVERSION_OVERFLOW,plese guide
Runtime Errors CONVT_OVERFLOW
Except. CX_SY_CONVERSION_OVERFLOW
Date and Time 03.05.2010 14:26:31
Short text
Overflow when converting from "-1"
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLCV120" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
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
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
caught in
procedure "SYS_GET_WINDOW_SYSTEM" "(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:
When attempting to convert the value "-1", an overflow occurred.
How to correct the error
If the error occurred in your own ABAP program or in an SAP
program you modified, try to remove the error.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"CONVT_OVERFLOW" "CX_SY_CONVERSION_OVERFLOW"
"SAPLCV120" or "LCV120F28"
"SYS_GET_WINDOW_SYSTEM"
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.
The exception must either be prevented, caught within proedure
"SYS_GET_WINDOW_SYSTEM" "(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 700
Application server... "APP2"
Network address...... "132.147.166.13"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x IA64 Level 3"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "DB"
Database type..... "MSSQL"
Database name..... "ELP"
Database user ID.. "elp"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 23 2009 22:38:30"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 221
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 29328880
Heap.... 0
Page.... 655360
MM Used. 3095760
MM Free. 1091456
User and Transaction
Client.............. 900
User................ "CPTN_SAPC5"
Language key........ "E"
Transaction......... "CV03N "
Transactions ID..... "C29156DF1F2DF180BE040017A4AB426D"
Program............. "SAPLCV120"
Screen.............. "SAPLCV110 0101"
Screen line......... 3
regards
kunalHi Kunal,
you can display both type of document 2003 and 2007 also. You need to configure these applications in define workstation application by using t-code DC30.
then you can display these files.
Regards,
Ravindra -
Run time error (short dump) executing program SCAN_BW_REFERENCES in SE80
Hi experts,
I am not an ABAPer, or Basis person, rather a hybrid functional/technical Key User for our Business Warehouse system (BW 3.5, Netweaver 2004). We have a user who cannot save BW reports to his favorites and he is getting a number of error messages. OSS note 887002 seems to address this and indicates that I should run program SCAN_BW_REFERENCES from transaction SE80. The program is supposed to perform the checks for BW objects assigned to the Favorites and identify situations causing terminations in BW frontend applications. I have attempted to execute this program on several occassions and always get run-time errors (short dumps). Here is the error:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 2008.09.17 19:00:49
ShrtText
No storage space available for extending an internal table.
What happened?
You attempted to extend an internal table, but the required space was
not available.
I have been informed by our Basis group that I have reached a memory limit, but they will not extend the memory paramters. Any ideas on a work-a-round or a way to minimize the number of records this program is pulling in, in an attempt to get it to run?
Thanks,
HCHi,
The only response I got from Basis was that they would not extend the memory parameters because they are for all users in the system. Not sure what that means.
The full dump is too large to paste here. I think what I will do is to see if our ABAPers can create a modified version of this program to include selection by user. Typically it is for only one user that I need to run the program, and that surely would fall within the space requirements.
Thanks for your answer.
//HC -
ABAP/4 run time error with error code SNAP_NO_NEW_ENTRY
Dear All,
I've installed SAP R/3 IDES on Oracle on Windows 2003 server.After clicking Log on button , I should be asked to enter client,user and password.But, my system does not display such details.Instead I get ABAP/4 run time error with error code SNAP_NO_NEW_ENTRY that too after a long time.
Can you please address what is the reason for this problem and how to over ride it?
Regards,
S.SureshHi,
the most probable reason is an archiver stuck. Backup the archived redo log files and delete them afterwards.
The database will archive some more logs after this. Handle them in the same manor. For complete explanation search for brtools.
Regards
Ralph Ganszky -
ORACLE Forms Run Time error FRM -92050 failed to connect to server
server name:
osfsun.oklaXXX:9000
Details:
Java Exception
Java.netNoRouteToHostException: operation timed out
at java.net.plainsocketImpl.doConnect(Compiled Code)
at java.net.plainsocketImpl.connectToAddress(plainsocketImpl:124)
There is more....
I have opened the port 9000 in my LAN firewall, I have checked Jinitiator control panel, I'm able to resolve web address but receive this web run time error,.anyhelp would be appreaciated.
thanksI resolved this issue. It was related to the firewall using port 9000/ The issue was not related to Oracle.
-
'CONVT_NO_NUMBER' run time error in custom program of upgraded ECC system.
Hi,
I am getting a run time error in custom program and st22 shows 'CONVT_NO_NUMBER' as the cause.
We have just upgraded system to ECC6 and with 4.7 we were not getting this error.
Can you please let me know if there is any SAP note to address this ?
Thanks,
AvinashHi Avinash,
Please see the below link for Sap Notes:
[Program is giving a Short Dump u201CCONVT_NO_NUMBERu201D.;
Regards,
Md Ziauddin
Maybe you are looking for
-
does win 8.1 media player 12 have an equalizer in the audio area?
-
Sql statement hanging in prod. fast in dev.
Hi, Sql statement is hanging in production. In development it is executing in 2 secs. From explainplan , noticed that taking different indexes. I have posted the staement and explain plan (prod and dev) below. Statement: SELECT REP_V_SERVICE_REQUEST.
-
Hello experts, please check this code. CHECK NOT T_DELIVERIES[] IS INITIAL. SELECT MANDT VBELV POSNV VBELN POSNN INTO TABLE T_VBFA FROM VBFA FOR ALL ENTRIES IN T_DELIVERIES WHERE VBELN EQ T_DELIVERIES-VBELN AND POSNN EQ T_DELIVERIES-P
-
Default settlement rule with settlement type as FUL for service orders
Hi Folks, Could you please advise me on the below issue? Requirement: setting up of default settlement rule with default settlement receiver as u201CCOST CENTREu201D and settlement type as u201CFULu201D for the maintenance orders (Order category u201
-
Possible to assign apps to one device?
I have an Iphone 4S and a Ipad 2 on the same account. Is it possible in iTunes to assign each app I have to either only my iPhone, or my iPad or both. I am tired of seeing apps I got for my Ipad end up also on my Iphone, and vice versa. btw, just not