Runtime error while executing Tcode FAGLL03

Hello experts
we have 2 clients in PRD
100,200
In 100 if i execute the tcode FAGLL03 it is showing the line items within 100 sec.
where as in 200 if i execute FAGLL03 it is showing runtime error.
if this executed in background it takes 1300 sec and finished successfully.
From basis perspective what would be the issue.
Regards
Ravi

Hello srini
Thanks for ur input
Details
Recording at local and central time........................ 06.05.2009 14:03:30
Task................ 07522  /  Dialog work process No. 00
User................ DEVAKUMAR
Client.............. 200
Terminal............ H2SBASIS
Session............. 1
Transaction code.... FAGLL03
Program name........ FAGL_ACCOUNT_ITEMS_GL
Problem class....... T    Transaction Problem
Development class... SABP
Further details for this message type
Module name......... abinit
Line................ 1890
Error text.......... ab_chstat
Documentation for system log message AB 0 :
The specified runtime error has occurred in the system.
Parameter
  a.. TIME_OUT
Technical details
File................ 000989
Position............ 0000261540
Entry type.......... l      ( Error (Module, Row)            )
Message ID.......... AB 0
Variable parts...... ab_chstat                                           abinit  1890
this is the log got from SM21.
The runtime error is time out error
Regards
Ravi

Similar Messages

  • Runtime error while executing rule

    Hello All,
      While executing the DTP for a cube, im facing the error as Runtime error while executing rule -> see long text .
      For this source is another Cube, where im loading the data from Cube to Cube.
    Error Description are as follows:-
    Error Location: Object Type    TRFN
    Error Location: Object Name    0T9SCR6Q4VWS1SOPNRRBOY1YD51XJ7PX
    Error Location: Operation Type ROUTINE
    Error Location: Operation Name
    Error Location: Operation ID   00034 0000
    Error Severity                 100
    Original Record: Segment       0001
    Original Record: Number        557
    and Also descripton is :-
    Diagnosis
        An error occurred while executing a transformation rule:
        The exact error message is:
        Division by zero
        The error was triggered at the following point in the program
        GP4H0CW3MLPOTR3E8Y93QZT2YHA 4476
    System Response
        Processing the data record has been terminated.
    Procedure
    The following additional information is included in the higher-level
    node of the monitor:
       Transformation ID
       Data record number of the source record
       Number and name of the rule which produced the error
    Let me know ur valuable suggestions on these error...
    thanks.

    Hello,
    I have checked all the transformation and End Routines.All are working fine.Yesterday i have loaded some data into it, but today its gettting errored out.
    Checked completely in the forum for threads related to this, but couldnt find proper thread which had solutions....
    thanks,
    srinivas.

  • Runtime error while executing rule - see long text RSTRAN 301

    Hi BW Gurus,
    When I executing the DTP, the following error occured.
    Runtime error while executing rule -> see long text     RSTRAN     301
    Diagnosis
        An error occurred while executing a transformation rule:
        The exact error message is:
        The argument 'GBP' cannot be interpreted as a number
        The error was triggered at the following point in the program:
        GP46DQFOYRZTUS0QITMO07IFTS0 1137
    Appreciate any useful suggestions.
    Thanks in advance.
    Maruthi

    Guess you are doing some calculation in your routines ..based on Currency Key i.e USD or INR , GBP..etc ..it should be currency value..rather than currency key. Check your field caluclation

  • Diadem runtime error while executing command "SchemeMeasStar"

    Hello:
    I used DIAdem9.0 and DAQCard6062E to acquire 16 channel data. I collected 65536 data for every channel. Whereas After the data acquisition stopped, an Error Message would poped up, but the data is still stored in data portal. the Error is like follows:
    -Error- DIAdem
    Runtime Error While Executing Command "SchemeMeasStar"
    Error Type: UNKNOWN
    Error Address:00001720
    Module Name:GFSBase.Dll
    Would you like to give me some suggestions?
    thanks very much
    jing

    Dear MarcusP:
    Thank you very much.
    your solution really works. The attached is the detailed information of the problem. Would you like to tell me more about the prolem and how to solve the problem thoroughly.
    Thank you very much.
    yours
    Jing
    Attachments:
    DIAdem_Error.doc ‏305 KB

  • Runtime Error While executing the WebDynpro Application

    I am getting the Runtime Error While executing the WebDynpro Application. The error message is "TSV_TNEW_OCCURS_NO_ROLL_MEMORY".
    It says like "
    Short text
        No roll storage space of length 9728 available for OCCURS area.
    What happened?
        Each transaction requires some main memory space to process
        application data. If the operating system cannot provide any more
        space, the transaction is terminated.
    But while executing some other Web Dynpro Applications, i am not facing this problem.

    Generally this error is a result of an infinite loop on internal table or select endselect statement where by severs  temporary memory gets full. With no memory to insert new records in temporary memory system generates the dump.
    Check your application or ask basis consultant to look at the memory parameters in instance profile.
    Regards
    Rohit Chowdhary

  • Runtime Error While in Tcode KES1

    Hello Team,
    We are using ECC6 EhP6.
    I am getting a Runtime error while working with Tcode KES1:
    Short text
              Syntax error in program "SAPL0KEA ".
         What happened?
              Error in the ABAP Application Program
              The current ABAP program "SAPLSVIM" had to be terminated because it has
              come across a statement that unfortunately cannot be executed.
              The following syntax error occurred in program "SAPL0KEA " in include "L0KEAT00
    " in
              line 225:
              "The Dictionary structure or table "*T2580" is either not active or doe"
              "s not exist."
              The include has been created and last changed by:
              Created by: "GAURILAD "
              Last changed by: "SAP* "
              Error in the ABAP Application Program
              The current ABAP program "SAPLSVIM" had to be terminated because it has
              come across a statement that unfortunately cannot be executed.
         Error analysis
              The following syntax error was found in the program SAPL0KEA :
              "The Dictionary structure or table "*T2580" is either not active or doe"
              "s not exist."
         Please help me resolve this issue
    Thanks
    Saheli

    Hi Dnyaneshwar,
       Please execute report RKEAGENV  and regenerate operating concern and check if the issue is resolved.
       If not run report RKEAGENF with your operating concern, type of COPA = 1 (costing based) and flag the 'Refill' option. Regenerate the operating concern.
    If running report RKEAGENV will cause another error concerning   operating concern E_B1,then please follow the steps in KBA note  1514122
    Operating concern should be E_B1 even though you may not be using this operating concern.
    regards
    Waman

  • Runtime error while executing SE30 Tcode as CREATE_DATA_ILLEGAL_LENGTH

    Hi Guys,
    when I am executing a TCode SE30 I am getting following Runtime error .
    Runtime Errors         CREATE_DATA_ILLEGAL_LENGTH
    Except.                CX_SY_CREATE_DATA_ERROR
    Date and Time          23.07.2010 12:28:30
    Short text
         CREATE DATA: Illegal value for the length of an object of the type "X"
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "CL_ABAP_TRACE_FILE============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_CREATE_DATA_ERROR', was not
          caught in
         procedure "READ_INFO" "(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:
         A data object of the type "X" with length 0 was to be created using
         CREATE DATA. The value 0 is not within the allowed range.
         Allowed range for the length specification:
         Typ C, N, X: 1 .. 65535
         TYP P:       1 .. 16
    Missing RAISING Clause in Interface
    Please suggest me the solution .

    You have to check that in the object(source code) which you are analysing via SE30 .

  • Runtime error while executing New Hire action in PA40

    Hi All,i am getting short dump while executing PA40 for new hire action typecan anyone look into this and guide as i am new to HCMNote: getting dump only for one user id for rest all other user id i am not getting dump.
    Category               ABAP Programming Error                                                      
    Runtime Errors         SYNTAX_ERROR                                                                
    ABAP Program           /1PAPAXX/HDR_21000A                                                         
    Application Component  Not Assigned                                                                
    Date and Time          21.08.2014 14:07:03                                                         
    Short text                                                                                       
        Syntax error in program "/1PAPAXX/HDR_21000A ".                                              
    What happened?                                                                                   
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
        The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in                     
        include "/1PAPAXX/HDR_21000AO01 " in                                                        
        line 52:                                                                                     
        ""LV_LENGTH" has already been declared"                                                      
        The include has been created and last changed by:                                            
        Created by: "HCM04 "                                                                         
        Last changed by: "HCM03 "                                                                    
        Error in the ABAP Application Program                                                        
        The current ABAP program "SAPFP50M" had to be terminated because it has                      
        come across a statement that unfortunately cannot be executed.                               
    What can you do?                                                                                 
        Please eliminate the error by performing a syntax check                                      
        (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".                        
        You can also perform the syntax check from the ABAP Editor.                                  
        If the problem persists, proceed as follows:                                                 
        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                                                                                   
        The following syntax error was found in the program /1PAPAXX/HDR_21000A :                    
        ""LV_LENGTH" has already been declared"                                                      
    How to correct the error                                                                         
        Probably the only way to eliminate the error is to correct the program.                      
        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..... 731                                                                         
        SAP Basis Level. 0007                                                                        
        Application server... "dc-ds-erp"                                                            
        Network address...... "172.16.23.111"                                                        
        Operating system..... "Linux"                                                                
        Release.............. "3.0.13-0.27-default"                                                  
        Hardware type........ "x86_64"                                                               
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 1                                                                      
        Shortdump setting.... "full"                                                                 
        Database server... "dc-ds-erp"                                                               
        Database type..... "ORACLE"                                                                  
        Database name..... "ECD"                                                                     
        Database user ID.. "SAPSR3"                                                                  
        Terminal.......... "NLC-HP"                                                                  
        Char.set.... "C"                                                                             
        SAP kernel....... 720                                                                        
        created (date)... "Sep 14 2013 06:16:24"                                                     
        create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"                            
        Database version. "OCI_112, 11.2.0.3.0, V1, default"                                         
        Patch level. 500                                                                             
        Patch text.. " "                                                                             
        Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"              
        SAP database version. 720                                                                    
        Operating system..... "Linux 2.6, Linux 3"                                                   
        Memory consumption                                                                           
        Roll.... 0                                                                                   
        EM...... 37708200                                                                            
        Heap.... 0                                                                                   
        Page.... 106496                                                                              
        MM Used. 4666776                                                                             
        MM Free. 3709976                                                                             
    User and Transaction                                                                             
        Client.............. 210                                                                     
        User................ "HCM03"                                                                 
        Language key........ "E"                                                                     
        Transaction......... "PA40 "                                                                 
        Transaction ID...... "53EF470299AB5D67E1000000AC10176F"                                      
        EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"                                  
        EPP Connection ID....... 00000000000000000000000000000000                                    
        EPP Caller Counter...... 0                                                                   
        Program............. "SAPFP50M"                                                              
        Screen.............. "MP000000 1000"                                                         
        Screen Line......... 3                                                                       
        Debugger Active..... "none"                                                                  
    Information on where terminated                                                                  
        Termination occurred in the ABAP program "SAPFP50M" - in                                     
        "GET_HEADER_WITH_TCLAS".                                                                    
        The main program was "MP000000 ".                                                            
        In the source code you have the termination point in line 146                                
        of the (Include) program "FP50MDHD".                                                         
    Source Code Extract                                                                              
    Line
    SourceCde                                                                                  
      116
      CALL FUNCTION 'HR_HEADER_GET'                                                            
      117
          EXPORTING                                                                            
      118
               DHDID                    = FHD_HID                                              
      119
               BEGDA                    = BEGDA                                                
      120
               TCLAS                    = TCLAS                                                
      121
    * Es wird nur einer der folgenden 3 Parameter benutzt.                                     
      122
    * Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.                                 
      123
    * Der erste der nicht initial ist wird ausgewertet.                                        
      124
    *           MOLGA                   =                                                      
      125
               P0001                    = P0001                                                
      126
               PERNR                    = PSPAR-PERNR                                          
      127
          IMPORTING                                                                            
      128
               PROG                     = HEADER_PROG                                          
      129
               DNUM                     = HEADER_DYNNR                                         
      130
           EXCEPTIONS                                                                          
      131
                HEADER_DEACTIVATED          = 1                                                
      132
                HEADER_UNKNOWN              = 2                                                
      133
                HEADER_GENERATE_DEACTIVATED = 3                                                
      134
                HEADER_GENERATE_FAILED      = 4                                                
      135
                INTERNAL_ERROR              = 5                                                
      136
                OTHERS                      = 6.                                               
      137
      138
      IF NOT SY-SUBRC IS INITIAL.                                                              
      139
    * Bei Problemen gibt's eben ein leeres Dynpro.                                             
      140
        HEADER_PROG = 'SAPMP50A'.                                                              
      141
        HEADER_DYNNR = '0090'.                                                                 
      142
      ELSE.  " NOT sy-subrc IS INITIAL.                                   "                    
      143
    * Dann setzen wir jetzt auch noch das Datum fest.                                          
      144
        PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.                         
      145
    * Und schalten auf Uebergabe der PERNR mit globalen Variablen.                             
    >>>>>
        PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).                                       
      147
      ENDIF.  " (ELSE) NOT sy-subrc IS INITIAL.                           "                    
      148
    * Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.                         
      149
    * Wird mit Einfuehrung des Headerobjekts obsolet.                                          
      150
      PERFORM REMEMBER_HEADER  "                             "XYVPH4K015649                    
      151
        USING HEADER_PROG HEADER_DYNNR 'S'.  "               "XYVPH4K015649                    
      152
    ENDFORM.                                                                                   
      153
      154
    *       FORM RE588I                                                   *                    
      155
      156
      157
      158
    *  -->  T588I_DHDID                                                   *                    
      159
    *  -->  T588I_MOLGA                                                   *                    
      160
    *  -->  T588I_TCLAS                         

    Implement SAP Note 1004280.. your issue if fixed
    If your issue is resolved request you to close the thread or else free feel to touch base
    BR
    Anil

  • Portal runtime error while executing BI report through BEx Query designer

    I want to execute a query from query designer but when I execute it the following error occurs -
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 04:30_30/04/11_0008_35740651
    Refer to the log file for details about this exception.
    I have checked log, the error displayig in log is,
    ACCESS ERROR: Authorization check for caller assignment to J2EE security role SAP_J2EE_Engine:administrator
    Kindly help me.
    regards
    nk

    Dear Friends
    I have the same with this problem
    Please help us to resolve this problem
    Thanks and best regards

  • ABAP runtime error while executing T.code : PC00_M40_CALC

    Hi,
    I have applied SAP note 1568264 - Budget Changes 2011 as released by
    SAP and i also applied the pre-requiste SAP notes mentioned in the
    above SAP note
    1) SAP Note 1558475- Amendments to IT calculation notified under
    circular:08/2010.
    2) SAP Note 1572614- Tax calculations inconsistent for emp. without a
    vaild PAN.
    3) SAP Note 1575366- HINCALC0:Tax calculation inconsistent in case of
    invalid PAN.
    After applying the SAP notes, when i am trying to execute the T.Code :
    PC00_M40_CALC, i am getting an "Abap runtime error"
    "  Error in the ABAP Application Program
    The current ABAP program "????????????????????????????????????????" had to be
      terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "HINCALC0 " in include "PCTAXIN0
      " in
    line 905:
    ""ENDUZ-" expected, not "EDU_""
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "S2K_BASIS "
    Error in the ABAP Application Program
    The current ABAP program "????????????????????????????????????????" had to be
      terminated because it has
    come across a statement that unfortunately cannot be executed.   "
    Kindly suggest me what has to be done on priority basis.
    Regards
    Vish

    The dump error is generally encountered if your system is at a lower Support Pack level. For implementing Note 1568264 (Budget Changes 2011), you need to be at the below mentioned pre-requisite level corresponding to your Release:
    Prerequisites:
       Release     Support Package
         604         HRSP29
         600         HRSP63
         500         HRSP80
         470         HRSPB4
         46C         HRSPG9
    The correct sequence to implement the Notes is:
    SAP Note 1558475- Amendments to IT calculation notified under
    circular:08/2010.
    SAP Note 1572614- Tax calculations inconsistent for emp. without a
    vaild PAN.
    SAP Note 1575366- HINCALC0:Tax calculation inconsistent in case of
    invalid PAN.
    SAP Note 1568264- Budget Changes 2011
    This should solve the issue unless there is some problem while implementing the Notes.
    Regards,
    Nishtha

  • RSIMPCURR: Runtime error while executing

    Hi Everyone,
    I want to create a process chain to transfer global settings from my ECC system to the BI system. For this purpose I was checking the ABAP program RSIMPCURR which is used to transfer the currecny exchange rates. But when this program is executed, it throws a runtime error and ends with a dump.
    Here's a snippet of the ABAP dump:
      151   CALL FUNCTION 'RSAR_DESTINATION_GET'                                                      
      152     EXPORTING                                                                               
    153       i_logsys      = l_source                                                              
      154     IMPORTING                                                                               
    155       e_destination = l_destination                                                         
      156     EXCEPTIONS                                                                               
    157       not_exist     = 1                                                                     
      158       OTHERS        = 2.                                                                    
      159   IF sy-subrc <> 0.                                                                         
    ' >>>>>     MESSAGE x000(rh).                                                                       
      161   ENDIF.                                                                               
    162                      
    The thing is, when I manually transfer the currencies from the RSA1 > Source system screen, I'm not facing any issues. Its only while executing the program that I get the dump.
    Any suggestions?
    Thanks,
    Ram

    Hi,
    I don't think this is a resource issue, because the global settings get transferred when I do it from RSA1 > Source system.
    Also the FM 'RSAR_DESTINATION_GET' is the one that throws the exception 'Cannot find destination'. I think this is because I cannot enter the Source System in the program parameters because it is disabled. The other parameters (like 'Exchange Rate type' and 'Changes since') are not disabled and I'm able to enter the selections into those.
    Is there anyway that I can enable the source-system box and provide my source system as a location extract the currencies?

  • Runtime Error while executing Assignment

    Hi Experts,
    I have 3 fields at 1) ValidStartDate 2) ValidEndDate 3) Item Status.
    I have written assignment to check if my current system date and time falls between validstartdate and validenddate, then my Itemstatus field should be active else inactive.
    Logic:
    If(SYSTIME(0)>=validstartdate AND SYSTIME(0)<=validenddate, Active, Inactive).
    SYSTIME(0) Is current system date and time
    and my validstartdate and validenddate fields data type is Literal Date
    Assignment Field: ItemStatus
    Error Message: "A runtime error occurred while evaluating an assignment, validation or calculated field".
    Could any one please suggest where went wrong, The same logic is executing sucessfully in validation with TRUE, FALSE.. in place of Active and Inactive.
    Thanks in advanced.
    Thanks
    Bharat

    Hi,
    we have the same problem:
    A runtime error occurred while evaluating an assignment
    What is the solution ?
    Thank you.
    Petr.

  • Runtime error while executing VA01

    Hi All,
    I'm getting ABAP dump while executing VA01. Especially while doing variant configurations. 
    Please have a look into following dump.
    Category               ABAP Programming Error
    Runtime Errors         SYNTAX_ERROR
    ABAP Program           SAPMV45A
    Application Component  SD-SLS
    Date and Time          15.12.2011 00:37:01
         Short text
              Syntax error in program "SAPMV45A ".
         What happened?
              Error in the ABAP Application Program
              The current ABAP program "????????????????????????????????????????" had to be
               terminated because it has
              come across a statement that unfortunately cannot be executed.
              The following syntax error occurred in program "SAPMV45A " in include
               "DI_ESD_SAPMV45A===============E " in
              line 184:
              ""TEXT" has already been declared"
              The include has been created and last changed by:
              Created by: "SAP "
              Last changed by: "SANJAY "
              Error in the ABAP Application Program
              The current ABAP program "????????????????????????????????????????" had to be
               terminated because it has
              come across a statement that unfortunately cannot be executed.
         What can you do?
              Please eliminate the error by performing a syntax check
              (or an extended program check) on the program "SAPMV45A ".
              You can also perform the syntax check from the ABAP Editor.
              If the problem persists, proceed as follows:
              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
              The following syntax error was found in the program SAPMV45A :
              ""TEXT" has already been declared"
         How to correct the error
              Probably the only way to eliminate the error is to correct the program.
              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..... 702
              SAP Basis Level. 0003
              Application server... "SANDERP"
              Network address...... "172.16.1.12"
              Operating system..... "Windows NT"
              Release.............. "6.0"
              Hardware type........ "4x AMD64 Level"
              Character length.... 16 Bits
              Pointer length....... 64 Bits
              Work process number.. 3
              Shortdump setting.... "full"
              Database server... "SANDERP"
              Database type..... "DB6"
              Database name..... "OLS"
              Database user ID.. "SAPOLS"
    Thanks in Advance,
    Uday

    Hi
    there is a syntax error in the user exit SAPMV45A created for VA01. Last change was done by sanjay.
    Request your abap team to correct the syntax to resolve the issue.
    Hope this is useful.
    Regards,
    Deepak Kori

  • Runtime error while executing transaction BDLS

    Hello,
    While executing BDLS transaction for converting logical system names I am getting following error
    Runtime Errors         CONVT_NO_NUMBER
    Except.                CX_SY_CONVERSION_NO_NUMBER
    Short text
         Unable to interpret "7,160 " as a number.
    How to resolve the above problem?

    Hi Rachel,
    BDLS creates an ABAP program SBDLS* which includes all the tables possibly including logical system names as of the domain behind the table fields. This program firstly    
    lives in runtime only and is checked by syntax checker.                 
    Now, sometimes tables have inconsistencies associated with them and you 
    will get this dump when a syntax check is performed on them.            
    So please check this and regenerate the culprit tables.                                                                               
    So please redo the steps for BDLS and check. There are     
    probably some tables which could be determined by you (syntax           
    check - in case program has already been saved only)                                                                               
    An easy way to check this is to run RBDLS2LS program (old BDLS) and     
    afterwards performing a syntax check on generated RBDLS*** (RBDLS<(>    
    <<)>(>                                                                  
    <<(><<)>)>ClientName>) program. 
    Known tables which caused such dumps in the past are:
    DFKKCOLFILE_P_W
    DFKKKO         
    DFKKMKO        
    DFKKREP06      
    DFKKREP06_S    
    DFKKREP07      
    DFKKREV06      
    DFKKREV07 
    Simply reactivate the tables you find out in SE11.                                                                               
    Another thing which has lead to this dump in the past is                
    in your R/3-System the value ' x ' is                                   
    additionally added to the value of your current release in the basis    
    release table SVERS.                                                    
    The table RSBASIDOC takes the release value from the table SVERS.       
    If you change value 'x' to your release in both tables (SVERS and       
    RSBASIDOC) and                                                          
    and activate again your source system connection. This could solve the 
    dump too.   
    I hope, this helps-if not, pls open a message with SAP.(component: BC-MID-ALE)
    b.rgds, Bernhard

  • Error while executing  tcode FSE2 "Internal error in program SAPLFIBS no 5"

    I am getting below error which while trying to execute tcode FSE2 (Financial statement version). Can't able even go inside the tcode.  Please tell how to solve this.
    "Internal error in program SAPLFIBS number 5"

    Hi Dsr,
    Use transaction code <b>OB58</b>->Highlight the Fin. Stmt. version you want to Change and click on the <b>Display</b> icon.->Next, click on the "<b>Fin.Statement items</b>" icon on the application tool bar. You can then expand and carry out your update as appropriate.
    If you do not have the prerequisite authorisations, you wouldn't be able to do this.
    I hope the above helps.
    Do not forget to award the points please.
    Regards,
    Jacob

Maybe you are looking for

  • How do I update my Nvidia graphics drivers on Bootcamp using Windows 8.1

    Hey all, I have been running bootcamp with my MacBook Pro with retina display, mid 2013 model for quite some time, but only recently did the windows 8.1 update from windows 8. I have been prompted by some games, namely Fifa 15, to update to the lates

  • How to batch print different orientations or print sizes?

    How do I batch print several exposures at one time that differ in orientation (Landscape, Portrait) or print size (4X6 - 8 X10) or both orientation and print size?  I currently have Lightroom 2.3 installed on a XP SP3 machine. I have been unable to f

  • Render link depending on calculated value of another field

    I am using jdeveloper 11.1.2 I have table with many columns, and the last column contains commandLink I want to render this command link depending on calculated function (FileExport.getTranslateFileName) using another fields in the table (row.SciId)

  • Change Hierarchy without erase data historical

    Hi! I have a dimension hierarchy, but sometimes we have to change some members or introduce new members in the hierarchy. So if we change the hierarchy we will lose the historical vision. pe: Initial Situation P1     - A1       -A2      -A3 P2      -

  • Cannot open hotmail inbox messages

    i cannot open my hotmail in box messages, i can in windows explorer