‎2007 Mar 12 8:34 AM
i am having a problem when posting debit balances to any expense account for a particular year but credit balances are being posted without any problem. debit balances posting to any account which is not an expense account are going through for that particular year. what is hapening is after saving the system is saying "DOCUMENT XXXXXXXX HAS BEEN SAVED" but if try anything after that, that is when i am getting an update termination message and the a short dump.
Below is an extraxt of the short dump:
ABAP/4 runtime error DBIF_RSQL_SQL_ERROR
Occurred on 26.02.2007 at 08:26:04
>> Short dump has not been completely stored. It is too big.
SQL error 1438 occurred when accessing table "GLT0 ".
What happened?
When writing a data record to the database (i.e. when
updating the database), only part of the data field was
written (updated). The rest was truncated.
What can you do?
If the error occurred in Open SQL, there is probably an inconsistency
between the NAMETAB and the ABAP/4 Dictionary.
Compare the length specifications of the fields in the NAMETAB with
those in the ABAP/4 Dictionary and contact someone who is able to
perform a consistency check and eliminate the problem.
In most cases, this person will be your SAP consultant.
Please make a note of the actions and input which caused the error.
-
To resolve the problem, contact your
SAP system administrator.
Select the "Print" function to obtain a hardcopy of the
current termination message.
Error analysis
The problem has arisen because, within the database interface,
one of the data buffers made available for the INSERT (UPDATE)
is longer than the maximum defined in the database.
On the other hand, it may be that the length in the NAMETAB
does not match the maximum length defined in the database.
(In this case, the length in the NAMETAB is longer.)
How to correct the error
Database error text........: "ORA-01438: value larger than specified precision
allows for this column?"
Internal call code.........: "[RSQL/UPDT/GLT0 ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem in the
SAP note system. If you have access to the SAP note system yourself,
please use the following search criteria:
"DBIF_RSQL_SQL_ERROR"
"SAPLGIVA" or "LGIVAF10"
"UPDATE_TT_GLT0"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
-
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "31H"
Application server....... "umprod"
Network address.......... "10.1.1.9"
Operating system......... "Windows NT"
Release.................. "0"
Hardware type............ "PENTIUM"
Database server.......... "UMPROD"
Database type............ "ORACLE"
Database name............ "UMP"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "31I"
Created on............... "Jun 21 1999 04:44:28"
Created in............... "NT 4.0 1381 Service Pack 3 x86"
Database version......... "ora OCI_73211"
Patch level.............. "315"
Patch text............... " "
Supported environment....
Database................. "ORACLE 7.2..., ORACLE 7.3..., ORACLE
8.0...*"
SAP database version..... "31I"
Operating system......... "Windows NT 51 3, Windows NT 0 4"
User, transaction...
Client.............. 600
User................ "HAVIREO"
Language key........ "E"
Transaction......... "FB01"
Program............. "SAPLGIVA"
Screen.............. "RSM130003000"
Screen line......... 2
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLGIVA" in
"UPDATE_TT_GLT0".
The main program was "RSM13000".
The termination occurred in line 542
of the source code of program "LGIVAF10" (when calling the editor 5420).
The program "SAPLGIVA" was started in the update system.
Source code extract
005120 HSL10 = HSL10 + TAB_GLT0-HSL10
005130 KSL10 = KSL10 + TAB_GLT0-KSL10
005140 TSL11 = TSL11 + TAB_GLT0-TSL11
005150 HSL11 = HSL11 + TAB_GLT0-HSL11
005160 KSL11 = KSL11 + TAB_GLT0-KSL11
005170 TSL12 = TSL12 + TAB_GLT0-TSL12
005180 HSL12 = HSL12 + TAB_GLT0-HSL12
005190 KSL12 = KSL12 + TAB_GLT0-KSL12
005200 TSL13 = TSL13 + TAB_GLT0-TSL13
005210 HSL13 = HSL13 + TAB_GLT0-HSL13
005220 KSL13 = KSL13 + TAB_GLT0-KSL13
005230 TSL14 = TSL14 + TAB_GLT0-TSL14
005240 HSL14 = HSL14 + TAB_GLT0-HSL14
005250 KSL14 = KSL14 + TAB_GLT0-KSL14
005260 TSL15 = TSL15 + TAB_GLT0-TSL15
005270 HSL15 = HSL15 + TAB_GLT0-HSL15
005280 KSL15 = KSL15 + TAB_GLT0-KSL15
005290 TSL16 = TSL16 + TAB_GLT0-TSL16
005300 HSL16 = HSL16 + TAB_GLT0-HSL16
005310 KSL16 = KSL16 + TAB_GLT0-KSL16
005320 WHERE
005330 RLDNR = TAB_GLT0-RLDNR AND
005340 RRCTY = TAB_GLT0-RRCTY AND
005350 RVERS = TAB_GLT0-RVERS AND
005360 BUKRS = TAB_GLT0-BUKRS AND
005370 RYEAR = TAB_GLT0-RYEAR AND
005380 RACCT = TAB_GLT0-RACCT AND
005390 RBUSA = TAB_GLT0-RBUSA AND
005400 RTCUR = TAB_GLT0-RTCUR AND
005410 DRCRK = TAB_GLT0-DRCRK AND
> RPMAX = TAB_GLT0-RPMAX .
005430 ENDFORM.
005440 *eject
005450 * *
005460 *
005470 * *
005480 * FORM UPDATE_TT USING UTP_TAB.
005490 * Diese Form fuehrt die Tabellenupdates durch
005500 * Dabei wird die optimierte Form von UPDATE
005510 * verwendet
005520 * *
005530
005540 FORM UPDATE_TT_GLT3 .
005550 DATA: W_0 LIKE GLU1-TSL VALUE 0.
005560 UPDATE GLT3
005570 SET TSLVT = TSLVT + TAB_GLT3-TSLVT
005580 HSLVT = HSLVT + TAB_GLT3-HSLVT
005590 KSLVT = KSLVT + TAB_GLT3-KSLVT
005600 TSL01 = TSL01 + TAB_GLT3-TSL01
005610 HSL01 = HSL01 + TAB_GLT3-HSL01
‎2007 Mar 12 8:38 AM
Hi,
Because its problem in standard program try to find out a relavent OSS note in SAP service market place with his "SAPLGIVA" or "LGIVAF10" key words and apply that. May be it will solve your problem.
Regards,
Jayaram...