FBCJ - CASH JOURNAL POSTING - ABAP RUN TIME ERROR.

Hai,
My problem is, while FBCJ cash journal posting, Error message comes as Programme terminated, short dump is beeing formatted. The screen is quitting out to ABAP RUN TIME ERRORS. Short text of error message- For object, CAJO_DOC2 101, numer range interval 01 does not exist.( I have given the number range, but result is same.) - Pls advice, document type for cash journal is DZ ?.expecting valued support- Iam working on SAP R/3 4.7 enterprise.- TITUS GEORGE.

Hi,
GOto SNUM, Input CAJO_DOC2...
Click on change and click on document number ranges.
Maintain the document number ranges for your company code..
That should solve the problem.
Good Luck
Cheers,
Redoxcube

Similar Messages

ABAP run time error while perform LT06 or create TO with respect to posting

Hi SAP WM Gurus,
System is giving ABAP run time error while perform LT06 or create TO with respect to posting change notice, below are runtime analysis details.
>> Short dump has not been completely stored. It is too big.
>       P_MENGA = P_MENGE.
007940       P_UMREZ = 1.
007950       P_UMREN = 1.
Can you give any idea on this issue.
Thanks and Regards,
SHARAN.

This part is just the place in the program where the error occured, but why the error occured is mentioned earlier in the dump.
Maybe you have a too big number in the field and hence a field overflow, maybe you have a character instead of a number in the field.
Read the dump from the beginning. if you dont know how to read a dump,then try to get help from any local Abaper.

Internal Order abap run time error

hi,
I am using sap ecc 6.00 ides i have not authoroty to access oss notes.
I newly configurated internal order. But when i tried to post a document in fb50, an abap run time error happen like following
Run time error message type x
error analysis
rror analysis
   Short text of error message:
   Error GENERAL_ERROR MESSAGES_ACTIVE_REQUIRED
   Long text of error message:
    Diagnosis
        The following program error or handling error has occurred.
        Error information:
        GENERAL_ERROR
        MESSAGES_ACTIVE_REQUIRED
    System Response
        Processing is terminated.
    Procedure
        If you cannot solve the problem yourself using the error
        information, note down this information and the entries which led
        to the error. Contact your system administrator for further
        assistance.
   Technical information about the message:
   Message class....... "K5"
   Number.............. 011
please help

Hi,
   Please apply note 1361352 and check if the issue is resolved
regards
Waman

Reg : SDCCN / USMM tcode abap run time error

Dear Friends,
Runtime Errors : DBIF_RSQL_SQL_ERROR
Exception : CX_SY_OPEN_SQL_DB
When I run a T.Code SDCCN and USMM, got abap run time error
"SQL error in the database when accessing a table" that errors are below.
Internal Call code is ..........[RSQL/OPEN/TBTCO]
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"SAPLBTCH" or "LBTCHF19"
"EXECUTE_BP_JOB_SELECT"
The exception must either be prevented, caught within proedure
"EXECUTE_BP_JOB_SELECT" "(FORM)", or its possible occurrence must be declared
in the RAISING clause of the procedure.
This kind of errors found.
what can i do ? Pls give me solution

No cross posting
Read the "Rules of Engagement"
Regards
Juan

System is giving ABAP run time error while perform LT06 or create TO with r

Hi SAP WM Gurus,
System is giving ABAP run time error while perform LT06 or create TO with respect to posting change notice, below are runtime analysis details.
Short dump has not been completely stored. It is too big.
P_MENGA = P_MENGE.
007940 P_UMREZ = 1.
007950 P_UMREN = 1.
Can you give any idea on this issue.
Thanks and Regards,
SHARAN.

Hi,
Go to Tcode ST22 and mentione the dump code there and check.
Also take help[ of Abapers to fix it.
Thanks
Utsav

While creating a student through piqstc getting abap run time error

Hi Experts,
I am new to SLCM,
By following Micheal Fan's Basic configuration document,
I have done the basic configuration required for creating a student & maintaining the student file,
But while trying to create a student through PIQST00/PIQSTC getting abap run time error,
Attaching the txt file for complete view of abap error.
Please guide how to resolve this error.
Regards,
Prashanti Swain

Hi Rob,
Thanks a ton, for your quick reply,
But I have not understood the reason of the issue.
As i said I followed Micheal Fan's Document for configuration,
in that document there is no configuration step is defined for Vendor master data.
Could you please explain it in a more detail way.
Regards,
Prashanti Swain

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
Supriya

Hello,
Please refer SAP
Note 971535 - dump when deleting characteristic with hierarchy
Regards,
Ravi

ABAP run time error in Plant Maintenanace

hi experts,
i am creating order for external service with control key PM03,
I've done all required configuration and 12 orders were created also,but now ABAP run time error occurs,
Short text
with short text description
Exception condition "RECORD_NOT_FOUND_TCK01" raised.
i called up ABAP consultant,he told me to check all field and configuration,and am not able to pin point sources of error,
please guide for this,
thanks
Edited by: Pravin on Oct 20, 2008 11:58 AM

Dear Praveen,
I think your problem may be space of hard disk.11 records created succesfully and 12 record was creation problem.in thease reasons may be problem is table space in hard disk.
you ask first basis guys to check the data storage space and kindly run the sgen
Hope this may helps you
Prem.

DTP-ABAP run time error- Urgent

Hi All
I had put Sales order as the key in my COPA DSO,due to which i was getting summarised records, nw i removed this key and put the Lowest granular detail key and i.e BW doc # (0doc_num) & then i have activated my DSO.Now when i do the DTP frm COPA Datasource to my DSO, the Records get updated but in DTP run i get ABAP run time Error as 'ASSIGN_TYPE_CONFLICT'
Short Text: Type Conflict with ASSIGN in program "GP493C06NEDFLBYD3SN1KJR3EDX"Can any1 please advice on this as this is quiet urgent.
Points are assured
Thanks

Hi Noor,
Regarding your problem, p/s do this:
1. Go to tx: RSSGPCLA
2. Highlight the RSTRAN_MASTER_TMPL then click set status button
3. Re-execute the DTP.
Or you can see it : Notes: 908427
As your references.
Hopefully it can help you a lot.
Best regards,
Niel.
thanks for the points you choose to assign.

ABAP Run time error when display the Customs Export declarations

Hi,
I'm receiving ABAP Run time error when display the Customs Exp. Declarations Under SAP Customs Processing -> Customs Processing - Import / Export -> Monitoring.
Error messaging point to Function Module - /SAPSLL/CUHD_LOAD_SELECTION.
While debugging we found that Primary Key of the below structures are not the same
lt_corpar                              type      /sapsll/corpar_t
lt_corpar_ht      type      /sapsll/corpar_k02_ht
Does anyone has the SAP Notes or solution to this issue other than changing the structures manually. I'm not sure about the impact if i change manually
Error message short details
Termination occurred in the ABAP program "/SAPSLL/SAPLCUHD_SELECTION" - in
     "/SAPSLL/CUHD_LOAD_SELECTION".
    The main program was "/SAPSLL/CULO_DISPLAY_CUS_EXP ".
    In the source code you have the termination point in line 144
    of the (Include) program "/SAPSLL/LCUHD_SELECTIONU01".
We are on GTS Release 8.0 and Support Package SAPK-80014INSAPSLL (Support pack level 14).
Regards,
Pradeep Maddi

Hi,
I have implemented SAP Note 1531799, but it hasn't resolved the current issue.
For Our GTS instance, there are 2 Feeder Systems (ECC) attached, but document transfer in one of the system has not been activated. Both having the same partner functions ( We copied the sandbox into 2 different instances for different business Testings and now these 2 instances attached to GTS for testing). These feeder systems have different Logical system names and Logical system groups.
Recently i have implemented SAP Corrections manually for one the issue, Please see below thread for the detail information
Proforma Invoice not transferred to GTS
After implementing the corrections, i have created Pro-forma invoice in ECC system. When i tried to display, i'm facing the ABAP Dump issues.
Error details
Runtime Errors         ITAB_DUPLICATE_KEY
ABAP Program           /SAPSLL/SAPLCUHD_SELECTION
Application Component SLL-LEG
You tried to insert an entry into table "\FUNCTION=/SAPSLL/CUHD_LOAD_SELECTION\DATA=LT_CORPAR_HT". However, updating the unique table key "PRIMARY_KEY" resulted in a duplicate entry. The key concerned may be either the primary key or a secondary key.
Regards,
Pradeep

Abap run time error at the time of GR

I am facing a ABAP run time error at the time of GR of STO through MIGO_GR, then abap run time error is generated, details are given as per the Tcode:- ST22;
Runtime Error          MESSAGE_TYPE_X
ShrtText
   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).
Transaction
   Transaction......... "MIGO "
   Program............. "SAPLMBWL"
   Screen.............. "SAPLMIGO 0001"
   Screen line......... 15
Information on where terminated
     The termination occurred in the ABAP program "SAPLMBWL" in
     "MB_POST_GOODS_MOVEMENT".
     The main program was "SAPLMIGO ".
     The termination occurred in line 56 of the source code of the (Include)
     program "LMBWLU21"
     of the source code of program "LMBWLU21" (when calling the editor 560).
Source Code Extract
     55    IF NOT sy-subrc IS INITIAL.
>>>>>       MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
     57                  sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

Hi Tiwari,
The error seems to be triggered by note 385830. Pls refer to 'Note 556000 - Short dump due to note 385830' in www.service.sap.com
Btw, which version are you in?
Best Regards
Sathees Gopalan

ABAP run time error

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 AM

Dear 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.

ABAP Run time error while doing MIR6

Hi,
We are processing posting parked invoice & system did not displays the document & after then it throws long run time error.
regards,
mahesh

Hi,
Such run time errors occur if you are trying to process huge data or if the system is being accessed by too many users and if there are any foreground jobs run in the sap for huge data. Infact go to /tcode ST22 and check for the detailed error message and try executing the tcode after some time and also check if there are any jobs which have been scheduled in the foreground.
hope this helps
regards,
radhika

F110 ABAP Run time Error

Hi Friends,
My user has run F110 payment program
payment proposal and payment run also created. open vendor invoices also cleared with cleared doucments. But Run Time ABAP Error occured. the job was cancelled.
the bank payments are not happend. below description is the Error analysis.
Runtime Errors         CONVT_NO_NUMBER
Date and Time          17.02.2009 09:27:31
Short text
     Unable to interpret "CSE " as a number.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLFPAYM_NO" 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.
     This exception cannot be caught in the context of the current statement.
The reason for the exception is:
The program attempted to interpret the value "CSE " as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
How to correct the error
    Whole numbers are represented in ABAP as a sequence of numbers, poss
     with an algebraic sign.
    The following are the possibilities for the representation of floati
    point numbers:
      [algebraic sign][mantissa]E[algebraic sign][exponent]
      [algebraic sign][whole number part].[fraction part]
    For example, -12E+34, +12E-34, 12E34, 12.34
    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
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the followi
    keywords:
    "CONVT_NO_NUMBER" " "
    "SAPLFPAYM_NO" or "LFPAYM_NOU01"
    "FI_PAYMEDIUM_DMEE_PAYMULNO_05"
    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
please give me some inputs, should I suggest to user to reset the clear invoices and run again the
F110.
Points will be awarded.

hi
ru using any kind of BAPi here
check following
/message/3794598#3794598 [original link is broken]
Re: Sdccn Runtime error CONVT_NO_NUMBER
plz do the analysis in ST22 with ur ABAper
regards
KI

ABAP Run time error in SD

Hi
I am Belongs to SD. In my home PC i am getting following ABAP Runtime error.
Plaese help me ABAP Guys.
<b>DBIF_RSQL_INVALID_REQUEST</b>
This error i am getting in most transanctions.
Please give me the solution for this.
Regards,
Ravi Chandra

Hello Ravi,
I was talking about the details of the dump, there is much more than just the header line. It tells you what happened and where it happened. Could you please post that information?
Also do you only get that error when connecting remotely with your home PC or also when you are directly connected to the R/3 system?
Regards,
Michael

*FBCJ - CASH JOURNAL POSTING - ABAP RUN TIME ERROR*.

Similar Messages

Maybe you are looking for

FBCJ - CASH JOURNAL POSTING - ABAP RUN TIME ERROR.