Procedure run time error
create or replace
PROCEDURE proc1
AS
v_ename CHAR(20);
v_salary NUMBER(10,0);
BEGIN
SELECT ename , sal
INTO v_ename,
v_salary
FROM emp
WHERE sal > 1000;
END;
run time error:
Connecting to the database scott.
ORA-20001: Exact Fetch Returned Too many Rows
ORA-06512: at "SCOTT.PROC1", line 14
ORA-06512: at line 2
Process exited.
Disconnecting from the database scott.
what is the solution for this one?
99922255599 wrote:
i think these upper suggestions are right ,
IF NOT then What is your suggestion??You have not said whether you want to fetch a single row or fetch multiple rows. The reasons will differ. The method used will differ.
For example, you have a parameter table for an application. The application needs a call that returns a specific parameter value from the table. Or you have an Invoicing Shipping and Billing process that needs all invoices with the same shipping zip code in order to create the most cost effective shipping orders for the goods. It needs a call that will return a non-processed invoice data set with the same zip code.
Both are very different business needs. One does a single row fetch always. The other does anything from fetching a single invoice to 1000's of invoices.
These will be implemented very differently. There is not single processing and cursor approach for all problems in PL/SQL. The HOW it is done depends on the WHAT needs to be done.
As for fetching multiple rows - that is best done using bulk fetching. This provides the least amount of context switches between the PL/SQL and SQL engines. The basic sample template for bulk fetching is demonstrated in {message:id=9651210}.
Similar Messages
-
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 -
Run time Error while Creating Expense request
Dear Friends ,
In E-Payment ( Expense Claim ) creation , While clicking on Enter Receipts application is going to run time error for only one user.
Run time Error Info :
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED
Exception CX_SY_REF_IS_INITIAL
Short text
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_WDR_P13N_UTILITIES=========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "PRESET" "(METHOD)", 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:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: "LR_CONTEXT_ELEMENT").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
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.
If you have access to SAP Notes, carry out a search with the following
keywords:
"OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
"CL_WDR_P13N_UTILITIES=========CP" or "CL_WDR_P13N_UTILITIES=========CM002"
"PRESET"
Information on where terminated
Termination occurred in the ABAP program "CL_WDR_P13N_UTILITIES=========CP" -
in "PRESET".
The main program was "SAPMHTTP ".
In the source code you have the termination point in line 60
of the (Include) program "CL_WDR_P13N_UTILITIES=========CM002".
The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
procedure "PRESET" "(METHOD)", but it was neither handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "CL_WDR_P13N_UTILITIES=========CP "; its source
code begins in line
1 of the (Include program "CL_WDR_P13N_UTILITIES=========CM002 ".
Regards,
Suresh .Hi Agrawal
As you are getting run-time error after entering the sold to party and material and the error is in SAPLV61Z ,
close the session for sometime and open again and then create sales order and then enter sold to party and material and then check wheather you are getting or not. If you are still facing the problem then take the help of the ABAP & BASIS consultant's.
Regards
Srinath -
Run time error while closing the CRM Order using BAPI
Hi Experts,
Need your invaluable suggestions here.Apologies for the lengthy mail, intention is to give clear idea of the issue.
I am facing an issue while closing the CRM orders. According to our business process, when an issue is solved we will keep the order in resolved status only. We will not directly close the order from the CRM tool, instead we have created a custom program for the same purpose.
For the custom program we will give input as the order number and execute it, this will close the order.
Here close the order means assigning it to Close status as well assign the reason code.
We have created some reason codes for closed status.
So when the program is run the Order moves from resolved status to closed status along with reason code.
But of late we are facing some problems with this program, it is giving run time error for some CRM orders.
Run time error message : The ABAP/4 Open SQL array insert results in duplicate database records.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught in procedure "CRM_SERVICE_OS_UPD_OST_DU" "(FUNCTION)", nor was it propagated by a RAISING clause.
Please find my code which have used in the custom program
Closing the resolved SOs in the system
CALL FUNCTION 'CRM_STATUS_CHANGE_EXTERN_OW'
EXPORTING
objnr = iv_guid
user_status = lc_status_closed
EXCEPTIONS
object_not_found = 1
status_inconsistent = 2
status_not_allowed = 3
OTHERS = 4.
IF sy-subrc <> 0.
WRITE : 'Error at maintaining status'.
ENDIF.
Set reason code
build lt_subject
ls_subject-ref_guid = iv_guid.
ls_subject-katalogart = 'A2'.
ls_subject-codegruppe = 'ZR000003'.
ls_subject-code = 'ZR33'. " Reason code
ls_subject-mode = 'A'.
APPEND ls_subject TO lt_subject.
build lt_ossset
ls_osset-ref_guid = iv_guid.
ls_osset-subject_profile = 'ZREASON03'.
ls_osset-profile_type = 'G'.
ls_osset-subject = lt_subject.
APPEND ls_osset TO lt_osset.
build lt_service_os
ls_service_os-ref_guid = iv_guid.
ls_service_os-ref_kind = 'A'.
ls_service_os-osset = lt_osset.
APPEND ls_service_os TO lt_service_os.
build lt_input_fields
REFRESH: lt_input_fields, lt_field_names.
CLEAR : ls_input_fields, ls_field_names.
ls_field_names-fieldname = 'CODE'.
APPEND ls_field_names TO lt_field_names.
ls_field_names-fieldname = 'CODEGRUPPE'.
APPEND ls_field_names TO lt_field_names.
ls_field_names-fieldname = 'KATALOGART'.
APPEND ls_field_names TO lt_field_names.
ls_field_names-fieldname = 'SERVICE_PROFILE'.
APPEND ls_field_names TO lt_field_names.
ls_input_fields-ref_guid = iv_guid.
ls_input_fields-ref_kind = 'A'.
ls_input_fields-objectname = 'SERVICE_OS'.
ls_input_fields-field_names = lt_field_names.
APPEND ls_input_fields TO lt_input_fields.
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
EXPORTING
it_service_os = lt_service_os
CHANGING
ct_input_fields = lt_input_fields
EXCEPTIONS
error_occurred = 1
document_locked = 2
no_change_allowed = 3
no_authority = 4
OTHERS = 5.
IF sy-subrc <> 0.
WRITE : 'Error at maintaining reason'.
ENDIF.
CALL FUNCTION 'CRM_ORDER_SAVE'
EXPORTING
it_objects_to_save = lt_header_guid
iv_update_task_local = lv_update_task_local
IMPORTING
et_saved_objects = lt_saved_objects
EXCEPTIONS
document_not_saved = 1
OTHERS = 2.
IF sy-subrc <> 0.
WRITE : 'Error at saving'.
ELSE.
WRITE : 'Successfully Closed'.
COMMIT WORK AND WAIT.
ENDIF.
Run time error is coming at COMMIT WORK AND WAIT statement.
Please let me know any corrections are required in the above program.
When I analyzed the run time error I have found that it trying to insert the record in CRMD_SRV_OSSET for that CRM order, but already one record is present in the table for the same CRM order number.
For most of the CRM orders there is no entry in this table so they are closing successfully but for a few orders for which there is an entry we are getting the above run time error.
There is nothing wrong with the orders which have an entry already in the table CRMD_SRV_OSSET, I need to close these kind of orders with out run time error.
Kindly provide your feedback.Hi Dinakar,
You posted this in APO PPDS forum. This question should go to PP forum where someone could answer it.
Please close this thread and open a new thread in PP forum so that you could get help quickly from the relevant experts.
Regards - Pawan -
Run-time error while executing alv grid report
Hi everyone
I m trying to run a alv grid report it is giving a run time error while executing the statement CALL METHOD V_ALV->SET_TOOLBAR_INTERACTIVE.
Actually i added 2 buttons in the toolbar.after that when i execute the report i m getting errors.
<b>Error Analysis</b>
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "TOOLBAR_MENUS_INIT" "(METHOD)", 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:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component (variable: "ME->M_CL_MENU_BUTTON_VARIANT").
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.Hi Dinesh,
Seems you have not initialised ( Instantiated in OO ) the object and / or the parent container.
Check if you have create object for both the parent as well as the alv object.
So when you instatntiate the object of ALV you pass the object ( instantiated before hand ) in the parent container position.
Also you would have to register the events to the object using method. Then only the buttons will finction.
eg :
IF G_CUSTOM_CONTAINER IS INITIAL.
CREATE OBJECT CUSTOM_CONTAINER_1
EXPORTING CONTAINER_NAME = CONTAINER_1.
CREATE OBJECT GRID1
EXPORTING I_PARENT = CUSTOM_CONTAINER_1.
CALL METHOD ALV_GRID1->SET_TABLE_FOR_FIRST_DISPLAY
EXPORTING I_STRUCTURE_NAME = 'VBAK
CHANGING IT_OUTTAB = IT_VBAK.
Reward points if useful. -
Run-time error SAPSQL_ARRAY_INSERT_DUPREC occurred
When creating a new SyncBo (T51) instance after syncing eventually MI Clients shows the following message:
[20070315 01:28:14:343] E [MI/Sync ] Received exception info code 10 and detailed message "Exception while callSync: The ABAP/4 Open SQL arrayinsert results in duplicate database records. records in the data base."
In sm21 shows message:
AB0 Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
AB1 > Short dump "070316 205056 sapnw ELDA " generated
Looking for SAPSQL_ARRAY_INSERT_DUPREC error in SAP Note we found the note 817849 (Runtime error SAPSQL_ARRAY_INSERT_DUPREC occurs during sync).
We have downloaded and applied this note in Backend as note requires and ALL prerequisites of this note. Also we have upgraded to SP19 and Kernel to 155 (part 1 and 2). But problem continues and the client that happened this problem does not work any more, all new SyncBO instances created goes to MEREP_MON as Waiting status.
The dump on duplicate record is happening when the user is synchronizing and when a record is getting inserted to table merep_10100.
The solution /workaround could be to do a client reset for those devicesand test again and see if it is happening, but error returns happening after this.
When this happen SyncBo instance keeps on Waiting status (MEREP_MON). We couldn't understand why this happen suddenly and then no more new SyncBo could be created, all goes to Waiting status. Reprocess (ShiftF5) or start handler (Shift10) does not take any effect.
Best Regards,
RogérioHi Ajith
I am getting the same error and below is the error message from ST22. The only change is I am using for MTR application and the sync fails for the 2nd time when synched for patches for the MTR application. As it is generic sync, could you please advice to get rid of the problem.
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"LOG_INSERT_DB" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
Thanks, Raj -
Run time error while doing VL10B transaction for STO
Dear All,
We are facing problem of run time error while creating Delivery (VL10B) for STO .We have two company codes .For one company code its working fine .But we are trying for another company code ,this error coming.error detals
Error in the ABAP Application Program
The current ABAP program "SAPLV05I" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
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 cau
in
procedure "SD_PARTNER_UPDATE" "(FUNCTION)", nor was it propagated by a RAI
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:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
Kindly suggest as to how to resolve this asap.
regards
umeshThese Kind of Errors Generally Occor for the wrong maitnaince of the partner functions. If you are using any user exits to detremine the partner functions. check the logic in that routine.
Because we do frequently get this error, but only if we hae not maintained as per the rule written in the user exit..
The USer exits for partner Determiantion to check is Function Module EXIT_SAPLV09A_003. THis gets activated, if you have give the source parner function as "X/Y/Z" in your partenr determiantion procedures. -
Run time error while saving sales order
Hi all,
i am working on IDES ECC 6.0, when i am saving an sales order(OR) i am getting run time error in the table CRMPAROLTP, program SAPMV45A.
i am using 4 GB RAM, still having a space of 30 GB for only IDES to save the data.
so, how to solve it.Hello,
I doubt the runtime error (I am assuming you mean that you got a short dump) you mentioned in your original post has anything to do with the warning messages you see when doing a check (Ctrl+F2) on table CRMPAROLTP and program SAPMV45A. These warnings should not cause a short dump or runtime error.
The warning message for the table has the following long text:
Table CRMPAROLTP: Key length > 120 (Restricted functionality)
Message no. DT214
Diagnosis
The key length, i.e. the sum of the field lengths of all the key fields of the table, is more than 120 bytes.
System response
This is a warning.
Procedure
Note the following restricted fuctionality for this table:
- Table contents cannot be transported by specifying key values, at
best by specifying generic key values with a maximum length of 120
bytes.
- The table may not be used as the base table of a lock object.
The warnings in SE38 for program SAPMV45A are mostly related to Unicode and have no reference to the table CRMPAROLTP.
If you haven't already done so, please check the SAP Note referenced in my first reply since this does provide a solution for short dumps related to table CRMPAROLTP.
Of course, since I don't know specifically what the short dump message is that you received, I could be basing my assessment on false assumptions. If you have those details it is better for the SDN community as a whole if you include the information in this thread instead of sending it to me offline.
Best Regards,
Jamie -
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 -
Run Time Error in Account Determination
Dear Friends
In my system using std one for account det then it posting to FI.
Now I created my own Table, Access Seq, Condition Type and Procedures after all assignment when I assign my procedures to F2 .
Then I done sales cycle upto billing, but when I am trying to save it it shows Run time Error. if assigning the Std Procedure KOFI00 to F2 then it is ok.
give me solution
Thanking You
ArunDear Arun,
Can you provide in detail !!
What is the error you are getting when you save the invoice
Check the settings at all these steps with compare to the standard setings.
SPRO>IMG>Sales and Distribution>Basic Functions>Account Assignment/Costing-->Revenue Account Determination.
-->Check Master Data Relevant For Account Assignment
-->Define Dependencies Of Revenue Account Determination
-->Define Access Sequences And Account Determination Types
-->Define And Assign Account Determination Procedures
-->Define And Assign Account Keys
-->Assign G/L Accounts.
I hope this will help you,
Regards,
Murali. -
Run time error while installing Labview 8.6.1 in Vista x64
hai friends,
i got an error( Run time error) while installing Labview 8.6 software. this software has bought from NI. it shows the error path as setup.exe. this software i had tried to install in vista x64. but when i am installing the same software in windows xp, it is installing fine...so what was the problem for this error. how to solve it, please help me....Thank You Mr.Jason Daming,
Same error what post Mr.muks referred in the last reply....
When the installation begins an error occurs (after the acceptance of licence step in the installation procedure) with the title on the error window "Microsoft Visual C ++ Runtime Library " and displays the program set up path with these statements " This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."
while installing the same Labview in windows XP..... it is installing fine... but in vistax64 only i am facing this kind of problem... -
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. -
Hi,
while runing t,code FBZ5 , i am getting this run time error.
Runtime Errors CALL_FUNCTION_NOT_FOUND
Except. CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time 30.05.2009 13:12:34
Short text
Function module "OTF_LIST" not found.
What happened?
The function module "OTF_LIST" is called,
but cannot be found in the library.
Error in the ABAP Application Program
The current ABAP program "SAPLSTXC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
not caught in
procedure "OTF_SEND_SPOOL" "(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:
The program "SAPLSTXC" contains the CALL FUNCTION statement.
The name of the function module to be called is "OTF_LIST".
No function module exists with the name "OTF_LIST".
All function modules are listed in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Pay particular attention to
upper/lower case and underscores ("_").
or
b) Transport error
c) In the case of an enqueue/dequeue module,
the lock object may not have been activated
(ABAP/4 Dictionary).
Line SourceCde
241 unknown_font = 2
242 others = 3.
243 if sy-subrc <> 0.
244 perform internal using 'OTF_SOFT_FONT_GET' sy-subrc.
245 endif.
246
247 * insert in otf table before(!) font call, i. e. append
248 check not otf[] is initial.
249 append lines of l_sfont to otf[].
250
251 endform.
252
253
254 form otf_send_spool tables otfdata structure itcoo
255 using param structure itcpp.
256 data: l_parlen type i,
257 l_dummy(1) type c,
258 l_mult type i,
259 l_actmult type i,
260 l_cp type tcp00-cpcodepage.
261
262 * right-to-left conversion
263 if itcpp-tdrtl = true. "RTL
264 if spool_external_print <> true. "RTL
265 perform otf_rtl_layout tables otf. "RTL
266 endif. "RTL
267 endif. "RTL
268 * use old 2.0 ABAP driver or spooler c-routines
269 if param-tdotfcall <> space.
270 check param-tddest <> c_dest_null.
>>>>> call function param-tdotfcall
272 tables otf = otfdata
273 exceptions others = 1.
274 if sy-subrc ne 0.
275 perform fatal.
276 call function 'SAPSCRIPT_MESSAGE'
277 exporting typ = 'A'.
278 endif.
279 else.
280 check param-tddest <> c_dest_null.
281
282 describe field l_dummy length l_mult in byte mode.
283 l_actmult = l_mult.
284
285 loop at otfdata.
286 case otfdata-tdprintcom.
287 when pc_id_string.
288 if c_unicode = false.
289 l_parlen = 7 + otfdata-tdprintpar+5(2).
290 else.
Regards,
baluHi,
Kindly check in debug wht the non existent FM 'OTF_LIST' is getting called?
Probably this seems to be a dynamic call to some FM and the FM name is not getting generated properly.
Regards,
Ankur Parab -
ABAP Run time Error whle executing the Balance sheet report in FGI0
Hi,
I am getting the below ABAP Run time error while executing the Balance Sheet report in FGI0.It was working before but now it is giving the error.Kindly help me in solving this.
Runtime Errors MESSAGE_TYPE_X
Date and Time 06/12/2009 15:17:17
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).
Error analysis
Short text of error message:
RAISE RKD_CONDITION_READ (internal error)
Long text of error message:
Diagnosis
The program was terminated because a situation occurred which
should not have arisen.
Procedure
Analyze the situation and contact SAP.
Technical information about the message:
Message class....... "KH"
Number.............. 299
Variable 1.......... "RKD_CONDITION_READ"
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Trigger Location of Runtime Error
Program SAPLKYPR
Include LKYPRU31
Row 36
Module type (FUNCTION)
Module Name RKD_CONDITION_READ
Thanks
SupriyaHello,
Please refer SAP
Note 971535 - dump when deleting characteristic with hierarchy
Regards,
Ravi -
Reg:Run time error in cjv4
Hi,
I am getting run time error during transfer of project from
a)version --->version
b)Version--->operative
Can anybody suggest some notes to resolve this issue.
With Regards
Rohit PrakashHi,
I have found following error type:-
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 "CO_LA_OPER_SEQ_PRE_READ_DB_VER" "(FUNCTION)", 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
"TPLNR" does not exist in any of the database tables from the FROM clause.
With Regards
Rohit Prakash
Maybe you are looking for
-
Theses a bug in the Nokia 3110c version 7.21, related to log. My phone's log showed 'Data recieved in last session' is 114256785kb, and 'All recieved data' is just 5865427kb, how can that be possible? All recieved data is always greater or equal to d
-
Can we pass Reference cursor using dblink
Can we pass reference cursor from one DB to another DB using DBlink? I feel like it is not possible because the memory structure of same will be available in other DB. Could you please let me know whether we can give a work around which will solve th
-
OSB 10g Offline Endpoint URI is not working
We are facing an issue with marking Endpoint URI to offline on unavailability. Have tried all possible ways to check this issue in environments by making all necessary configurations but somehow the URI's are not being marked out offline. Please conf
-
My House is Sinking-Please Help
Well, I am an Apple nut, and wish I had an Apple house, but alas, I do not. I am an old, retired teacher trying to help someone at the other end of the spectrum, a Zagg employee who is working, studenting (-B and parenting. He has a Passport extern
-
Spotify won't save Albums anymore
Hey Guys, i hope that the problem hasn't been asked yet and if so, please don't crucify me :) So i came across a problem that first appeared two weeks ago on my vacation to denmark. i saved some albums into my library (some Batman audiobooks and anot