Screen dump when posting debit balances to an expense account

dear experts.
A screen dump is produced when saving or posting debit balances to expense accounts for only certain periods and for a certain fiscal year in this case year 2006. what might be the problem. can the problem be solved form the ABAP side or FI side?
its urgent

below is part of the screen 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

Similar Messages

Error when posting debit balances to expense accounts

dear experts.
A screen dump is produced when saving or posting debit balances to expense accounts for only certain periods and for a certain fiscal year in this case year 2006. credit balances are being posted without any problem to the same accounts, same periods and fiscal year. what might be the problem. can the problem be solved form the ABAP side or FI side?
its urgent

Hi Willard,
Karthik is right, we need more input to resolve this issue. ST22 can give it to you.
This issue as far as I understand has nothing to do with ABAP. It has to be resolved by functional / basis people.
Is there any internal order / cost center assignment when posting to these expense a/c's?
Regards,
Siva

Error in posting debit balances to expense accounts

When trying to post debit balances to expense accounts for a particular fiscal year, we are getting a short dump. Credit balances are being posted without a problem. Debit balances for other classes of accounts are posting without a problem for that particular year.

Hi,
Can you provide the error details. what transaction are you using for posting etc.
Regards
Mahendra

ERP EHP4 causing dump when posting invoice in MIRO

I originally posted this in the MM forum but was advised to move it here.
We just implemented ERP EhP4 w/SAPAPPL603 and are now getting a dump when using MIRO to posting a vendor invoice against a PO. The error seems to involve new logic for multiple account assignment introduced with this EHP. The dump is in include LMRMBWF02 of SAPLMRMBM, and indicates that data object S_MCRBPO does not contain component XHISTMA. The lines in LMRMBWF02 are (starting at 772):
FORM bw_read_co_history_dyn_sub USING event TYPE bwmode
s_index_mcrbpo TYPE eval_iv_index_key_s
s_mcrbpo TYPE mcrbitm
CHANGING s_mcrbco TYPE mcrbco.
DATA: s_ekbe LIKE ekbe,
s_ekbz LIKE ekbz,
s_ekbz_ma TYPE ekbz_ma, "MAA EhP4
s_ekbe_ma TYPE ekbe_ma, "MAA EhP4
f_arewr TYPE ekbz-arewr, "MAA EhP4
f_areww TYPE ekbz-areww. "MAA EhP4
CASE event.
WHEN c_recompilation.
IF s_mcrbco-xunpl = space.
Not for unplanned account assignments
IF ( s_mcrbpo-exkbe = 'X' ).
Read PO history for goods item
IF s_mcrbpo-xhistma = space. "MAA EhP4
...with the last line being the culprit. The actual break in execution occurs at line 119 of SAPLMRMP, BESTELLUNG_BUCHEN where function MRM_BW_PO_HISTORY is called.
Had some other errors where tables weren't properly activated after the EHP installation, but here most everything seems to be activated properly. The exception is table EKBE, which activates but with warnings about missing enhancement categories of tables or includes/subtypes for four active dependent tables. That's the only lead I've got.
Can't find any notes or other posts about this error, any ideas would be greatly appreciated!

Hi,
the only thing i´ve found is this OSS Note:
https://service.sap.com/sap/support/notes/1105679
Best regards.

CATS Screen dumps when navigating between prev and foll weeks in ESS portal

The medical leave absence type MEDICAL LEAVE @1/2 PAY(13) is the only allowed by time administrators to enter through transaction CAT2 and not through ESS. Once entered,this appears in your time entry in ESS as a disabled entry. However once you navigate between the previous or the following weeks, after this entry appears in your screen, the screen dumps.
SAP allows this functionality where time entries can be maintained for an employee through CAT2 on ERP side with an absence type not available in ESS portal.
The following is the dump analysis from ST22.
An exception occurred that is explained in detail below. |
The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
caught in
procedure "PROCESS_TIMESHEET" "(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:
In the running program "CL_XSS_CAT_RFC_COMMAND_TOOLS==CP", part of a string was
about to be accessed
with an explicitly specified length.
However, this length (4) exceeded the current length of the string
(3).
| This kind of access is illegal.
Kindly suggest.

The latest note released by SAP to solve this issue is 1559416 CATS WD: Dump if Attendance/Absence type is deactivated .It works !

F110 Debit Balance Check auto block account

Hi:
on F110 , I run debit balance check and execute the and put block.
Is this really block vendor account or not? I go to FK05 but it not put the block there.
pls advise.

Hi Mandy,
BTE 1820 is used for debit balance check in F110. But after executing it won't put any block in vendor account but it does so in run time when you execute proposal.
At the stage of proposal, it will analyze as per the logic that you have specified in the BTE and will propose you the payment list. If you run again the second time, it will analyze afresh based on entries posted in the system at that point of time..so it won't put any permanent block on any Vendor. It is for the scheme of entries posted at that point of time when you are running proposal.
Hope it helps..
Regards,
Kavita

Use Tax Posting To Tax Payable and Expense Account

Hello Experts,
I am trying to post tax, code 03, to an expense account instead of the customer account at the time of billing. This is for use tax posting based on the costs of our materials and should be paid by company and not passed to the customer. Currently The percentages will base from the cost of material instead of sale price but this is posting to our tax payable account and to customer account as below:
Dr Customer Account 1.27
       Cr Revenue -1.20
       Cr Use Tax Payable -.07
The desired outcome would be as below:
Dr Customer Account 1.20
     Cr Revenue -1.20
     Cr Use Tax Payable -.07
Dr Use Tax Expense .07
Thanks in advance for help.

Hi
Welcome to SDN Forum
As you want to post to separate Tax payable and expense account ,so maintain a separate account key and assign it to the tax condition type in Pricing procedure .In VKOA assign the G/L accounts to that account key.So you have to take your FI Team members help to get the G/L accounts.and its assignment to the tax code.
Regards
Srinath

Vendor Maintenance screen display when posting in FB01

Hi All,
I would like to ask your idea if ever you have encountered this issue.
In FB01 I post a document using the vendor 999999 after entering the posting key and press the enter. Another screen displayed..that screen looks like the transaction FK01. It seems that you need to recreate again the vendor. But my question is why did that screen appears though that vendor is already created..What are instances that this screen will appear..
Regards,
Ekitzv

Hi,
That vendor must be One-time vendor.
The concept of one time vendor is that, there is a single transaction with that vendor, like Fly-Ins.. and which are not regular.
So, SAP has given you the facility to create a Vendor in the Account Group One time vendor, which will have one vendor Account No., in your case it is 999999, and whenever you post entry with this vendor Account No., then, at the time of posting entries, a pop up screen will come for you to enter the name, city etc..
The balance vendor master data, like pmt terms, Recon account remains same for all, but only the name & city changes..
So, instead of creating many such one time vendor code in the system, you create just one code and then on a case to case basis, you post liability in this vendor, and enter name ,city etc.. at the time of Invoice booking.
=========
When you go to FK01 to create a vendor, press F4 on Account Group, and you will see that there is a check mark for OTA(One time acount), with this tick, you can identify that whether your vendor 999999, is in the account Group OTA.
Hope it helps..
Regards,
SAPFICO

ABAP short dump when posting to FICO

We are testing payroll on a upgraded version of our live system and recieving an abap error stating an issue with object "COSTS" . This is only occuring when trying to post the results to FICO and only for one particular employee. On searching we have found SAP note 890828 which seems a rather larger problem than just affecting one employee.
Anyone have any idea's?

Hi
The ABAP dump should be as follows:
Runtime errors CONNE_IMPORT_WRONG_STRUCTURE
Exception CX_SY_IMPORT_MISMATCH_ERROR
Error when importing object "COSTS".
You need to follow the instructions in note 890828.
The CLASS CL_HR_PAY_RESULT_GB is used by RPCIPE00 in release your upgrade release
You have two choices in the note.
1) a modification in SAP standard to "ignore structure boundaries".
2) run the conversion program RPUSTRCL_COSTS.
Regards

Vendor Debit balances in balance sheet

Dear all,
In blancesheet (t- Code F.01), some of Vendors are having the debit balances my client is asking to show those balances in superate GL account,
i got an idea about this, that is transafering the all debit balances to one more account at year we have to reverse these balances to original..
for this i am not getting any idea if u have any please send me ,
Regards

Hi Sudheer,
When ever you receive advance from Vendor generally it should debit the vendor account and later when we receive invoice we will adjust the advance with invoice.
so at the year end you might be having advances in your vendor account , so you are getting debit balance for vendor.
Now you want to treat advances sepereately and to another GL account.
SAP has given business process to map the above sccenario
YOu need to configure one GL account named Adavance to Vendor Account, It should be reconcillation ac, it should be asset account.
You need to do the config setting in SPRO>FA>AR & AP>Business transactions>Down payment made>Define reconcillation account for Vendor down payments
Double click on A and give the GL account
Use the special Gl indicator A and give the alternate GL account which created earlier.
Now you have to post vendor adavance using F-47
then invoice F-43
Clearing downpayment f-54
payment F-53
Best Regards
Ashish Jain
Message was edited by:
Ashish Bohara

Vendor debit balance should come in sundry debtor balance

Hi, Gurus
My problem is that my client wants that if a vendor has debit balance than it should be treated as sundry debtor (Current Asset) and balance should come in sundry debtor reco. GL, similarly if a Customer has credit balance than it should be treated as sundry creditor (Current liability) and it should come in to sundry creditor balance.SAP provides overall debit/credit balance of Reco. Gl, my requirement is per vendor/customer wise i,e if Mr. X is a vendor and he has credit balance of say Rs.1000/- than its ok but another vendor say Mr. Y has debit balance of Rs. 7000/- than it should come in sundry debtor GL, what SAP is doing it will show debit balance in sundry creditor Reco. GL.
Please help me and provide appropriate solution.
Thanks & Regards
Anuraj

Hi ,
you need to perform closing operations for Accounts Recievable /Payable to achieve your client requirement.
Please read below SAP help.
Customers in Credit and Vendors in Debit
A credit balance on a customer account should be displayed as a payable; conversely, a debit balance on a vendor account should be displayed as a receivable. If such a situation arises, the program makes the appropriate adjustment postings automatically.
To do this, the system determines the total for each account and reconciliation account. This guarantees that special G/L transactions, for example down payments and bills of exchange are displayed separately from the payables and receivables. Accounts with the same consolidation company ID are considered together.
The receivables account in the figure above identifies a credit balance of $2000 for Customer 3. This payable is to be displayed in the balance sheet under the item "Other payables". You therefore transfer the amount to the account of that name. The receivables account is adjusted by a posting to the adjustment account.
Prerequisites
Since you cannot post to the reconciliation accounts directly, the system makes adjustment postings for you. You should display the reconciliation account and the adjustment account under the same balance sheet item. The system posts the offsetting entry to a G/L account, under which the payable (or receivable) is now displayed in the balance sheet. You must have defined the account numbers for the adjustment accounts and the accounts for the offsetting entries in the system already. The posting keys are already defined in the standard system.
To define the account numbers, select the activity Define adjustment acts for reclassifying payabl./receivables in the Accounts Receivable and Accounts Payable Implementation Guide.
Regards,
Lakshmu

When posting GI for Non valuated material in Delivery geting error (M8147)

Hi Experts
We have a problem that we are trying to send a material from one plant in one company code to another plant in another company code (Inter Company Stock Transfer Order). The material is of type Non Valuated (So it has no valuation class). The PO Order type used and the PO account assignment category is of type saying GR Non Valuated.
Problem is in the outbound delivery (movement type 645 determined) when posting GI do we get a account determination error (M8147 = Account determination for entry 1000 GBB Z001 not possible), saying that no account could be determined.
Our understanding is that the GI for the delivery demands a Valuation, which we can not do as the material is NON Valuated.
How to set the GI non valuated for the outbound delivery, so we can avoid this error? please help
BR

>
Krishna Rao wrote:
> We assigned the GL for GBB in OBY. But, still the error is coming. Is there any other setup we need to do for Non Valuated material to post goods issue from delivery?
I cant believe that the same error message is coming up after the maintenance.
you either maintained an entry at a wrong level within GBB or the message must have changed.
Make sure that you take any information of this message into account (even the spaces)
the message is certainly not like you posted here: Account determination for entry 1000 GBB Z001 not possible
the message carries 4 variables , not only 3

Error when posting to profitabilty segments

Dear All
I get the following error when posting poriftabilty segment data in the accounting doument, if i try to enter the same characteristic value even to diffrent G/L Accounts.
Data record already exists
Message no. KE581
Diagnosis
This error should not occur.
Procedure
Contact your system administrator or SAP directly (component CO-PA-ACT).
Has anyone come across this issue... ? Pls let me know how to resolve this?
Thanks
Gayani

Hi,
Please implement the latest version of the note 1321225 into your system in order to solve this problem!
Afterwards please execute the function module RKE_GENERATE_INTERFACE_ACT in transaction SE37 for the operating concern you use - as described in note 1321225 under 'Solution'!
Please enter function module RKE_GENERATE_INTERFACE_ACT in transaction SE37, press F8, enter your operating concern and press F8 again.
Afterwards the described problem with error message KE581 should be solved.
regards
Waman

Dump error when posting through F-02.

Greetings everyone,
When posting G/L act through F-02 we are facing a dump error in QUALITY system and in DEVELOPMENT we are able to post succesfully.
From my primary analysis one standard program is calling and that program has syntax error.
When i checked that program it is saved in local object and generated automaticaly when some thing done is FICO.
Generated Program is Module pool program :GBTV6FI0
Description of that program is below
Generated by report RGUGBR01.
Generated code used by validations substitutions and rules.
!! Do not manually change or transport !!
For reference please find the dump below
    Error in the ABAP Application Program
    The current ABAP program "SAPLGBL5" had to be terminated because
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "GBTV6FI0 " in in
     " in
    line 519:
    "FORM "SEND_CMPLX_DATA_015" does not exist"
    The include has been created and last changed by:
    Created by: "DDIC "
    Last changed by: "****"
    Error in the ABAP Application Program
    The current ABAP program "SAPLGBL5" had to be terminated because
    come across a statement that unfortunately cannot be executed.
Can any one please suggest me how to resolve this issue.
Thanks in Advance.

This looks like you have not transported the code to quality system. This code seems to have been generated when validation, substitution and rules have been defined and is missing in quality system (not transported ?)
Find the form send_cmplx_data_015 in development system and check the version. This is the transport that still needs to be transported to quality system.
I now see that you say it has been saved as local object. In that case assign it to a package and transport in SE80.
And now I see the answer of Klaus, follow the instructions in the note he has supplied first. It seems that note is exactly describing your problem. :-)

Balance in transaction currency F5 702 when posting from SD invoice VF04

When posting message from VF04 or VF02, can not release to accounting.
Balance in transaction currency
Message no. F5 702
Diagnosis
A balance has occurred in transaction currency 'USD' with the following details:
Exchange rate '00', amount ' 1,000-' and currency key 'USD'.
The data in the transaction currency were transferred from the calling application.
4.6c release.
Sales org, company code, customer have currency USD.
In the header of invoice, posting status is "Error in Financials Interface". G.L. account is configured and can be posted.
Any suggestions is appreciated.

Hi,
I am getting same error message problem while releasing billing doc from VF02.
did you resolve the same please let me know how u did it.. i have gone throu user exit u mentioned but in my project those
User exits are not using.. pls give reply ASAP..
Getting below error message..
Balance in transaction currency
Message no. F5702
Diagnosis
A balance has occurred in transaction currency 'USD' with the following details:
Exchange rate '00', amount ' 5,494.00' and currency key 'USD'.
The data in the transaction currency were transferred from the calling application.
System Response
Your data cannot be processed in FI.
Procedure
The error is probably in the calling application.

Screen dump when posting debit balances to an expense account

Similar Messages

Maybe you are looking for