Run Time Errors : Raise_Exception, Exception condition "WRONG_PARAMETERS" r

Hi SAP Gurus,
I have activated Document splitting & when iam trying to post the document then iam getting the following Run Time Error.
Iam using SAP ECC 6.0
Short text                                                                               
Exception condition "WRONG_PARAMETERS" raised.                                                                               
What happened?                                                                        
    The current ABAP/4 program encountered an unexpected                              
    situation.                                                                               
Error analysis                                                                        
    A RAISE statement in the program "SAPLGLT2" raised the exception                  
    condition "WRONG_PARAMETERS".                                                     
    Since the exception was not intercepted by a superior                             
    program, processing was terminated.                                                                               
Short description of exception condition:                                                                               
For detailed documentation of the exception condition, use                        
    Transaction SE37 (Function Library). You can take the called                      
    function module from the display of active calls.                                 
Trigger Location of Runtime Error                                                     
    Program                                 SAPLGLT2                                  
    Include                                 LGLT2F07                                  
    Row                                     12                                        
    Module type                             (FUNCTION)                                
    Module Name                             G_BEB_MOVE_ACCIT_TO_STRING                                                                               
Source Code Extract                                                                               
Line  SourceCde                                                                               
1 ----         
    2 *         Created by     :  SAP*                                      *         
    3 *         Date           :  13.09.2007                                *         
    4 *         Time           :  16:57.56                                  *         
    5 ----         
    6 *    This Report is generated by Report RGUGGLT0                      *         
    7 ----         
    8                                                                               
9   IF I_LEDGER = SPACE.                                                                               
10     RAISE WRONG_PARAMETERS.                                                       
   11   ELSE.                                                                           
>>>>>     RAISE WRONG_PARAMETERS.                                                       
   13   ENDIF.
Kindly help me for the above.
Regards,
Amitabh

Hi Amitabh,
check this out:
1) Start transaction: SA38
2) Execute program: RGUGGLT0 (# to generate includes for flexible G/L)
3) Go back & repeat your posting transaction
4) Tell us if transaction worked fine
5) Reward me with points
Cheers!
B

Similar Messages

  • Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised

    Hi All,
    I am facing a runtime error, while using transaction DSWP --> Set-up System Monitoring --> Copy Customizing -->
    At that time we are getting "Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised
    ===========================================
    Runtime Errors RAISE_EXCEPTION
    Date and Time 25.07.2008 08:31:11
    Short text 
    Exception condition "METADATA_MISSING" raised. 
    What happened? 
    The current ABAP/4 program encountered an unexpected 
    situation. 
    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 
    A RAISE statement in the program "SAPLDSVAS_SERV" raised the exception 
    condition "METADATA_MISSING". 
    Since the exception was not intercepted by a superior 
    program, processing was terminated. 
    Short description of exception condition: 
    For detailed documentation of the exception condition, use 
    Transaction SE37 (Function Library). You can take the called 
    function module from the display of active calls. 
    How to correct the error 
    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: 
    "RAISE_EXCEPTION" " " 
    "SAPLDSVAS_SERV" or "LDSVAS_SERVC7I" 
    "MAP_DSVAS_TT_DATA_TO_TT_25" 
    or 
    "SAPLDSVAS_SERV" "METADATA_MISSING" 
    or 
    "RDSMOP_MAIN " "METADATA_MISSING" 
    If you cannot solve the problem yourself and want to send an error 
    notification to SAP, include the following information: 
    1. The description of the current problem (short dump) 
    To save the description, choose "System->List->Save->Local File 
    (Unconverted)". 
    2. Corresponding system log 
    Display the system log by calling transaction SM21. 
    Restrict the time interval to 10 minutes before and five minutes 
    after the short dump. Then choose "System->List->Save->Local File 
    (Unconverted)". 
    3. If the problem occurs in a problem of your own or a modified SAP 
    program: The source code of the program 
    In the editor, choose "Utilities->More 
    Utilities->Upload/Download->Download". 
    4. Details about the conditions under which the error occurred or which 
    actions and input led to the error. 
    System environment 
    SAP-Release 700 
    Application server... "terra" 
    Network address...... "172.16.1.198" 
    Operating system..... "Windows NT" 
    Release.............. "5.2" 
    Hardware type........ "4x Intel 801586" 
    Character length.... 16 Bits 
    Pointer length....... 32 Bits 
    Work process number.. 2 
    Shortdump setting.... "full" 
    Database server... "TERRA" 
    Database type..... "ORACLE" 
    Database name..... "DSM" 
    Database user ID.. "SAPSR3" 
    Char.set.... "C" 
    SAP kernel....... 700 
    created (date)... "Oct 23 2007 01:07:18" 
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10" 
    Database version. "OCI_10201_SHARE (10.2.0.1.0) " 
    Patch level. 133 
    Patch text.. " " 
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.." 
    SAP database version. 700 
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows 
    NT 6.0" 
    Memory consumption 
    Roll.... 8176 
    EM...... 37628064 
    Heap.... 0 
    Page.... 65536 
    MM Used. 31785376 
    | MM Free. 1656912
    =============================================
    Configuration:
    OS :Windows 2003 server.
    Solution Manager 7.0 SP15
    Oracle 10.2
    RAM - 2 GB
    Its bit urgent, Please help out us.
    Thanks in advance.
    Best Regards,
    Pratyusha

    Hi
    Check the SP level for ABAP and Basis. Download the latest SP level from SWDC and apply it on the system
    This error is related to ABAP program.
    Currently the latest available patch level is 16. Please download both ABAP and BASIS SP 16 and apply them on the system.

  • Run time error with exception 'EXTRACT_RESOURCEHANDLER_FAILED'

    Runtime Errors        EXTRACT_RESOURCEHANDLER_FAILED
    Short text
         Internal error: Error when logging on to delete the extract file.
    What happened?
         Error in the SAP kernel.
         The current ABAP "RAKOPL02" program had to be terminated because the
         ABAP processor detected an internal system error.
    What can you do?
         Note which actions and input led to the error.
         For further help in handling the problem, contact your SAP administrator
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    Error analysis
         An external file is required for the extracts. This can only be deleted
         at the end of the transaction. The logon for the deletion failed with
         the return code: "-4".
    How to correct the error
         The internal system error cannot be fixed by ABAP means only.
         You may be able to find a solution in the SAP note system. If you have
         access to the SAP note system, try searching for the following terms:
          "EXTRACT_RESOURCEHANDLER_FAILED" " "
          "RAKOPL02" or "RAKOPL02_FORM"
          "EXTRACT_DATEN"
         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:
         "EXTRACT_RESOURCEHANDLER_FAILED" " "
         "RAKOPL02" or "RAKOPL02_FORM"
        "RAKOPL02" or "RAKOPL02_FORM"
        "EXTRACT_DATEN"
        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.
    Hi All,
    There was a run time error due to the 'EXTRACT' statement in the code in the standard program 'RAKOPL02'.
      EXTRACT daten.
    Can you please let me know the possible causes and necessary corrections to the system (at basis level) if any?
    Thanks in advance,
    RAVI
    Edited by: Maruvada Ravi Kishore on Jun 4, 2009 6:01 AM
    Edited by: Maruvada Ravi Kishore on Jun 4, 2009 6:01 AM

    Hello,
    Refer this link
    https://www.sdn.sap.com/irj/scn/advancedsearch?query=extract_resourcehandler_failed&cat=sdn_all

  • Runtime error raise_exception (Exception condition "NOT_EXIST" raised)

    Hi,
    I tried to ran a DTP to load data in a Standard DSO. Once I run the DTP ,instantly it is showing me short dump.I tried to ran it 2 times. Every time it shows me dump
    Runtime Errors         RAISE_EXCEPTION
    Short Text : Exception condition "NOT_EXIST" raised.
    Error Analysis : A RAISE statement in the program "SAPLRSSM" raised the exception
    condition "NOT_EXIST".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    Thanks in advance,
    Regards,
    Snehasish

    Hi,
    This kind of issues occur in BI7.0, the cause is not clear.
    You can once again delete the Data in the DSO using SE14(If Production system, make sure you contact your Basis team for this).
    You will have to use the table names(check the Delete data option & click on Activate and adjust databas)
    Thanks,

  • Run time error in RFC

    Hi,
         run time error occur in RFC when i try  to create,change and opening  the  rfc connections(like abap connections).its showing run time error : RAISE_EXCEPTION. SHORT DECCRIPTION :EXCEPTION CONDITION  DP _ERROR RAISED.
    PLEASE HELP ME TO SOLVE THIS PROBLEM.

    Information on where terminated
        Termination occurred in the ABAP program "CL_ALV_TREE_BASE==========
         in "GET_FRONTEND_FIELDCATALOG".
        The main program was "SAPMCRFC ".
        In the source code you have the termination point in line 23
        of the (Include) program "CL_ALV_TREE_BASE==============CM00D".
    Trigger Location of Runtime Error
        Program                                 CL_ALV_TREE_BASE==============CP
        Include                                 CL_ALV_TREE_BASE==============CM00D
        Row                                     23
        Module type                             (METHOD)
        Module Name                             GET_FRONTEND_FIELDCATALOG
    Source Code Extract
    Line  SourceCde
        1
        2 method get_frontend_fieldcatalog.
        3
        4 * exit in batch mode
        5   if not m_batch_mode is initial.
        6     et_fieldcatalog[] = mt_fieldcatalog[].
        7     exit.
      8   endif.
    9
    10 * get column orders
    11   data l_columns type treev_cona.
    12   call method mr_column_tree->get_column_order
    13               changing
    14                   columns = l_columns
    15               exceptions
    16                   cntl_system_error = 1
    17                   dp_error          = 2
    18                   failed            = 3.
    19   case sy-subrc.
    20     when 1.
    21       raise cntl_system_error.
    22     when 2.
    >>       raise dp_error.
    24     when 3.
    25       raise failed.
    26   endcase.
    27
    28 * get columns
    29   types: begin of lt_width_type,
    30            h_col_key type lvc_s_fcat-h_col_key,
    31            width type i,
    32          end of lt_width_type.
    33   data: lt_width type table of lt_width_type,
    34         l_width type lt_width_type.
    35   field-symbols: <ls_fieldcatalog_wa> type lvc_s_fcat.
    36   l_width-width = 0.
       37   loop at mt_fieldcatalog assigning <ls_fieldcatalog_wa>
       38                           where no_out <> 'X' and
       39                                 tech is initial.
       40     l_width-h_col_key = <ls_fieldcatalog_wa>-h_col_key.
       41     append l_width to lt_width.
       42   endloop.

  • Run Time error in MIGO Posting

    Dear Friends,
    While Posting MIGO against a import PO system throws run time error for a particular plant. I have created 2 plants for the same company code. But first plant does not have any problem. Pl help me and let me know what may be the cause and its solution. No conditions maintained for the Vendor. After PO directly user creating MIGO.
    Regards,
    Ashok

    Pl find the Run Time error of Exception while posting. Before posting Document was OK while checking.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          11.01.2011 10:34:16
    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:
         Operation QM14 not available for this lot
         Long text of error message:
          Diagnosis
              The desired operation does not fit the inspection lot (object
              type).
          System Response
              The operation is not permitted and can therefore not be carried
              out.
          Procedure
         Technical information about the message:
         Message class....... "QV"
         Number.............. 224
         Variable 1.......... "QM14"
         Variable 2.......... " "
         Variable 3.......... " "
         Variable 4.......... " "
    Trigger Location of Runtime Error
        Program                                 SAPLMBWL
        Include                                 LMBWLU21
        Row                                     62
        Module type                             (FUNCTION)
        Module Name                             MB_POST_GOODS_MOVEMENT
    Source Code Extract
    Line  SourceCde
       32 *    BKPF as well. There is no other way to forward XBLNR to FI as not
       33 *    every document is posted by MB_CREATE -> a new function module in
       34 *    MBWL for transferring the information, called by FI, meant to load
       35 *    the complete function group for all MBxx postings when this isn't
       36 *    required (Performance). Would be the better way to transport the
       37 *    information after switching off MBxx in later release.
       38 *    corresponding IMPORT ... FROM MEMORY ... can be found in
       39 *    AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
       40      l_mem_id = 'MKPF-XBLNR'.                                   " 641365
       41      EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
       42    ELSE.                                                        "1245374
       43      l_mem_id = 'MKPF-XBLNR'.                                   "1245374
       44      FREE MEMORY ID l_mem_id.                                   "1245374
       45    ENDIF.
       46    IF xmkpf-xabln IS INITIAL.                               "note 434093
       47        CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
       48    ENDIF.                                                   "note 434093
       49
       50 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
       CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
            EXCEPTIONS
              error_message = 4.
    As soon as we have started to put things into UPDATE TASK, w
    ensure that errors definitely terminate the transaction.
    MESSAGE A is not sufficient because it can be catched from
    external callers which COMMIT WORK afterwards, resulting in
    incomplete updates. Read note 385830 for the full story.
       IF NOT sy-subrc IS INITIAL.
          MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH
                     sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        MESSAGE A263.
       ENDIF.
    Optische Archivierung
    Spaete Erfassung mit Barcode
    Redesign of barcode handling -> note 780365
      PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
                                             xmkpf-mjahr
                                             barcode.
      MOVE-CORRESPONDING xmkpf TO emkpf.
      CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
        EXCEPTIONS
          error_message = 4.
       MOVE-CORRESPONDING xmkpf TO emkpf.
       CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
            EXCEPTIONS
              error_message = 4.
       IF NOT sy-subrc IS INITIAL.
    Regards,
    Ashok

  • RUN TIME error - Error code: system level exception -17502

    1. During running of my sequence in a TestStand Operator Interface   i got following run-time error:
        Details: Error executing substep 'Post'.Parameter 'Input cluster 6 [OUT]': System Level Exception.
        Location: Step 'sequence 'SequenceFilePostStep' in 'Sequence X.seq'
        In my SequenceFilePostStep i transfer some information between the LabVIEW 8.0 and TestStand 3.5.
        In my xxx.vi I have 6 clusters and every cluster from 14 to 20 variables.
       The  cluster #6 has 70 variables.
       Perhaps, the error that i got is from cluster #6 due to 70 variables? is it to much for cluster?
    2. What can i check? How i can fix it?
    Please ask questions if you do not understand something, i am want to resolve it!
       Thank you to all!
    Message Edited by Yuri_IL on 07-30-2006 10:54 AM
    Thank you & Best Regards
    *I use LabVIEW 8.X & TestStand 3.5/4.0.1 versions only

    Thank you Sam R,
    I think that error caused due the overflowing of some string that i have in my cluster.
    Because i also get I/O open file error and the name of that file i hold at my cluster.
    Do you think that the incorrect string can caused to that system level exception error?
    p.s. screenshot is attached
    Thank you & Best Regards
    *I use LabVIEW 8.X & TestStand 3.5/4.0.1 versions only
    Attachments:
    io_error.JPG ‏11 KB

  • Run TIme Error Message- Array Out of Bounds Exception

    Good evening all,
    I seem to have a run time error with the below segment of code. I've changed the (args[0]) a variety of ways but still get the same message.
    I have a few questions regarding my methodology. First, am I headed down the right path (no spoonfeeding allowed please! I need to grasp and learn this myself). Second, would it be something causing error that is on another line and I'm not seeing it. Third, should I have added the entire class file?
    public static void main(String [] args) throws IOException
       Inventory store = new Inventory ( 15);  // Sets store inventory
       Scanner inFile = new Scanner(new File(args [0])); // _Line 27 in the program_
       PrintWriter outfile = new PrintWriter(args [1]); 
       String temp; .
       double price; 
       int quantity; .
       inFile.next();
       int x = 0; Run time error received:
    java.lang.ArrayIndexOutOfBoundsException: 0
         at StoreBusiness.main(StoreBusiness.java:27)
    Thank you in advance everyone.

    WarriorGeek wrote:
    Thanks Flounder,
    I feel pretty dumb after posting my answer.
    I read the arrays tutorial and understand all that's described there but with what I've learned you have to start your array out at zero like I did. Should I use the variable name that I gave it in lieu of zero?No. The point is that since you didn't provide any arguments when you started your program, there is no arr[0] or arr[anything else]. It doesn't matter if you put an int literal between the brackets or a variable or a method that returns int. You can't access elements that don't exist.
    So instead of java MyClass you need to do java MyClass something The "something" becomes args[0]. If you're using an IDE instead of the command line, there will be a place to configure what arguments you want to pass when you run your program.

  • Exception vs run-time error.

    In C# there is no any difference between the folowing two lines of code:
    int d = 0; int i = 1/d;
    throw new DivideByZeroException();
    However, in T-SQL world, it seems that the following two lines are not the same:
    SELECT 1/0;
    RAISERROR ('Divide by zero error encountered.', 16, 1);
    even though they generate similar messages:
    Msg 8134, Level 16, State 1, Line 1
    Divide by zero error encountered.
    Msg 50000, Level 16, State 1, Line 1
    Divide by zero error encountered.
    Extract from
    MSDN:
    RAISERROR Generates an error message and initiates error processing for the session.
    Another
    extract:
    SET XACT_ABORT Specifies whether SQL Server automatically rolls back the current transaction when a Transact-SQL statement raises a run-time error.
    When I run the following two SPs, I get different behaviour:
    CREATE PROCEDURE dbo.USP_PROCEDURE_1
    AS
    BEGIN
    SET XACT_ABORT, NOCOUNT ON;
    BEGIN TRAN;
    select 1/0;
    PRINT 'I did not reach that point.'
    END
    GO
    CREATE PROCEDURE dbo.USP_PROCEDURE_2
    AS
    BEGIN
    SET XACT_ABORT, NOCOUNT ON;
    BEGIN TRAN;
    RAISERROR ('Divide by zero error encountered.', 16, 1);
    PRINT 'Why did I reach that point?'
    END
    GO
    The first SP rollbacks transaction and returns the following message:
    Msg 8134, Level 16, State 1, Procedure USP_PROCEDURE_1, Line 7
    Divide by zero error encountered.
    The second SP leaves transaction open:
    Msg 50000, Level 16, State 1, Procedure USP_PROCEDURE_2, Line 7
    Divide by zero error encountered.
    Why did I reach that point?
    Msg 266, Level 16, State 2, Procedure USP_PROCEDURE_2, Line 0
    Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.
    Is it by design? Why? What is the point?
    Alexey

    Sometimes I'm tempted to say that a driving design goal in SQL Server for error handling has always been maximum confusion.
    The true story more likely t obe is that through the years, too little attention has been paid to this area, and once some funny behaviour has made it into the product, they are very anxious to change it, as it could break existing applications.
    With SET XACT_ABORT ON, most errors abort the batch and roll back the transaction, but there is a small class of errors that do not:
    * Syntax errors.
    * RAISERROR.
    * Error 266 (trancount mismatch).
    * Dropping a non-existing table and a few more.
    Once can note that in SQL 2000, binding errors (e.g. missing table) were also unaffected by XACT_ABORT, but luckily they did have the guts to change that in SQL 2005.
    To muddle the waters even further, in SQL 2012 they introduced the ;THROW statement which serves the same purpose as RAISERROR, but ;THROW aborts the batch. However, if XACT_ABORT is OFF, ;THROW does not roll back the transaction, a behaviour not seen before
    SQL 2012. As I said, confusion is a driving design goal for error handling in SQL Server.
    Erland Sommarskog, SQL Server MVP, [email protected]

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

  • Run time error CONVT_OVERFLOW

    dear Sir
    we have window 7 for new oc as soon runned teh program cv01n i got run time error msg  CX_SY_CONVERSION_OVERFLOW,plese guide
    Runtime Errors         CONVT_OVERFLOW                                                              
    Except.                CX_SY_CONVERSION_OVERFLOW                                                   
    Date and Time          03.05.2010 14:26:31                                                                               
    Short text                                                                               
    Overflow when converting from "-1"                                                           
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLCV120" 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_CONVERSION_OVERFLOW', was not               
         caught in                                                                               
    procedure "SYS_GET_WINDOW_SYSTEM" "(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:                                                             
        When attempting to convert the value "-1", an overflow occurred.                             
    How to correct the error                                                                         
        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 to                       
        find an interim solution in an SAP Note.                                                     
        If you have access to SAP Notes, carry out a search with the following                       
        keywords:                                                                               
    "CONVT_OVERFLOW" "CX_SY_CONVERSION_OVERFLOW"                                                 
        "SAPLCV120" or "LCV120F28"                                                                   
        "SYS_GET_WINDOW_SYSTEM"                                                                               
    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                               
        "SYS_GET_WINDOW_SYSTEM" "(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... "APP2"                                                                 
        Network address...... "132.147.166.13"                                                       
        Operating system..... "Windows NT"                                                           
        Release.............. "5.2"                                                                  
        Hardware type........ "2x IA64 Level 3"                                                      
        Character length.... 16 Bits                                                                 
        Pointer length....... 64 Bits                                                                
        Work process number.. 0                                                                      
        Shortdump setting.... "full"                                                                               
    Database server... "DB"                                                                      
        Database type..... "MSSQL"                                                                   
        Database name..... "ELP"                                                                     
        Database user ID.. "elp"                                                                               
    Char.set.... "C"                                                                               
    SAP kernel....... 700                                                                        
        created (date)... "Aug 23 2009 22:38:30"                                                     
        create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"                             
        Database version. "SQL_Server_8.00 "                                                                               
    Patch level. 221                                                                               
    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...... 29328880                                                                               
    Heap.... 0                                                                               
    Page.... 655360                                                                               
    MM Used. 3095760                                                                               
    MM Free. 1091456                                                                               
    User and Transaction                                                                               
    Client.............. 900                                                                     
        User................ "CPTN_SAPC5"                                                            
        Language key........ "E"                                                                     
        Transaction......... "CV03N "                                                                
        Transactions ID..... "C29156DF1F2DF180BE040017A4AB426D"                                                                               
    Program............. "SAPLCV120"                                                             
        Screen.............. "SAPLCV110 0101"                                                        
        Screen line......... 3  
    regards
    kunal

    Hi Kunal,
    you can display both type of document 2003 and 2007 also. You need to configure these applications in define workstation application by using t-code DC30.
    then you can display these files.
    Regards,
    Ravindra

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

  • Run time error in me22n and me 23n

    Hi,
    first time in me22n if i edit something and press save,changes are getting saved perfectly and i am getting success message.so now its in display mode.if i press display<-> change icon,and do some changes and press save  i am getting run time error."Raise-EXCEPTION'.
    EXCEPTION CONDITION 'fAILURE' RAISED..
    if i open me23n po in display mode.after make it change mode and after making some changes and press save i am getting same error..
    which badi-method or user exit i have to check for this?
    Regards,
    Kavitha

    Short text
    Exception condition "FAILURE" raised.
    What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
    Error analysis
    A RAISE statement in the program "CL_HANDLE_MANAGER_MM==========CP" raised the
    exception
    condition "FAILURE".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
    Short description of exception condition:
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    Trigger Location of Runtime Error
    Program CL_HANDLE_MANAGER_MM==========CP
    Include CL_HANDLE_MANAGER_MM==========CM005
    Row 13
    Module type (METHOD)
    Module Name GET
    Source Code Extract
    Line SourceCde
    1
    2 METHOD get.
    3
    4 IF my_manager is initial.
    5 CALL METHOD get_manager.
    6 ENDIF.
    7
    8 CALL METHOD my_manager->search EXPORTING im_id = im_id
    9 IMPORTING ex_handle = ex_handle
    10 EXCEPTIONS failure = 01.
    11
    12 IF sy-subrc ne 0.
    >>>>> RAISE failure.
    14 ENDIF.
    15
    16 ENDMETHOD.

  • Explanation of run time error & its process of elimination

    what is the following runtime errors .When does it occur & how can we eliminates these-
    1. SYSTEM_NO_SHM_MEMORY
    2. RAISE_EXCEPTION
    3. UNCAUGHT_EXCEPTION
    With Regards
    Amit Singh

    Hi Amit,
    I am not sure about the run time error SYSTEM_NO_SHM_MEMORY, however the other two I know a little about.
    RAISE_EXCEPTION can be the cause of the run time dump UNCAUGHT_EXCEPTION. In ABAP program, you might have a function module or method which raises an exception using the command RAISE <exception>. Now if in your calling application you do not "handle" the exception, then the dump UNCAUGHT_EXCEPTION occurs.
    The solution to this is to always handle the SY-SUBRC after a function module call and also using the TRY - CATCH <exception> - ENTRY for catching and handling exceptions in classes in your program.
    Please use F1 on CATCH/TRY command for more on this.
    A dump shows you the reason for the dump in quite a bit of detail in "Error Analysis" section and also gives a solution.
    Check ST22.
    Regards,
    Aditya

  • Run time error

    Dear All,
    During the transaction /n/sapapo/ccr (Reconsilation of transaction data) in client SCP 950, system displays the run time error which are attached herewith.
    This is the activity a used to execute regularly (Daily) and first time i recieved this message - -
    Runtime Errors         ASSERTION_FAILED                                                            
    Date and Time          13.07.2007 10:13:37                                                         
    ShrtText                                                                               
    The ASSERT condition has been violated.                                                       
    What happened?                                                                               
    In the current application program, the system recognized a situation                         
        involving the ASSERT statement that should not occur. A runtime error                         
        occurred, either because there was no activation ID entered or because                        
        the ID of the activation mode used was set to "Cancel.                                        
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                      
        and make a note of the actions and input that caused the                                      
        error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                
        You can use transaction ST22 (ABAP Dump Analysis) to view and administer                      
         termination messages, especially those beyond their normal deletion                          
        date.                                                                               
    is especially useful if you want to keep a particular message.                                                                               
    Error analysis                                                                               
    The following activation ID was used: "No checkpoint group specified"                                                                               
    If the FIELDS addition was used with this ASSERT statement, the content                       
        of the first 8 fields is as follows:                                                          
        " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    How to correct the error                                                                               
    Probably the only way to eliminate the error is to correct the program.                                                                               
    You may able to find an interim solution to the problem                                       
        in the SAP note system. If you have access to the note system yourself,                       
        use the following search criteria:                                                                               
    "ASSERTION_FAILED" C                                                                               
    "/SAPAPO/SAPLTIMESTAMP" or "/SAPAPO/LTIMESTAMPU08"                                            
        "/SAPAPO/TIMESTAMP_DIFFERENCE"                                                                
        If you cannot solve the problem yourself and you wish to send                                 
        an error message to SAP, include the following documents:                                                                               
    1. A printout of the problem description (short dump)                                         
           To obtain this, select in the current display "System->List->                              
           Save->Local File (unconverted)".                                                                               
    2. A suitable printout of the system log                                                      
           To obtain this, call the system log through transaction SM21.                              
           Limit the time interval to 10 minutes before and 5 minutes                                 
           after the short dump. In the display, then select the function                             
           "System->List->Save->Local File (unconverted)".                                                                               
    3. If the programs are your own programs or modified SAP programs,                            
           supply the source code.                                                                    
           To do this, select the Editor function "Further Utilities->                                
           Upload/Download->Download".                                                                               
    4. Details regarding the conditions under which the error occurred                            
           or which actions and input led to the error.                                               
    System environment                                                                               
    SAP Release.............. "640"                                                                               
    Application server....... "scmprd"                                                            
        Network address.......... "172.16.10.47"                                                      
        Operating system......... "AIX"                                                               
        Release.................. "5.3"                                                               
        Hardware type............ "0002BFAAD700"                                                      
        Character length......... 16 Bits                                                             
        Pointer length........... 64 Bits                                                             
        Work process number...... 0                                                                   
        Short dump setting....... "full"                                                                               
    Database server.......... "scmprd"                                                            
        Database type............ "ORACLE"                                                            
        Database name............ "SCP"                                                               
        Database owner........... "SAPSCP"                                                                               
    Character set............ "C"                                                                               
    SAP kernel............... "640"                                                               
        Created on............... "Jan 18 2006 20:47:39"                                              
        Created in............... "AIX 1 5 00538A4A4C00"                                              
        Database version......... "OCI_920 "                                                                               
    Patch level.............. "109"                                                               
        Patch text............... " "                                                                               
    Supported environment....                                                                     
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE                        
         10.2.0.."                                                                               
    SAP database version..... "640"                                                               
        Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"                                                                               
    Memory usage.............                                                                     
        Roll..................... 16192                                                               
        EM....................... 196923232                                                           
        Heap..................... 0                                                                   
        Page..................... 98304                                                               
        MM Used.................. 186636840                                                           
        MM Free.................. 1895288                                                             
        SAP Release.............. "640"                                                                               
    User and Transaction                                                                               
    Client.............. 950                                                                      
        User................ "SCMATP"                                                                 
        Language key........ "E"                                                                      
        Transaction......... "/SAPAPO/CCR "                                                           
        Program............. "/SAPAPO/SAPLTIMESTAMP"                                                  
        Screen.............. "SAPMSSY0 1000"                                                          
        Screen line......... 6                                                                        
    Information on where terminated                                                                   
        The termination occurred in the ABAP program "/SAPAPO/SAPLTIMESTAMP" in                       
         "/SAPAPO/TIMESTAMP_DIFFERENCE".                                                              
        The main program was "/SAPAPO/CIF_DELTAREPORT3 ".                                                                               
    The termination occurred in line 61 of the source code of the (Include)                       
         program "/SAPAPO/LTIMESTAMPU08"                                                              
        of the source code of program "/SAPAPO/LTIMESTAMPU08" (when calling the editor                
         610).                                                                               
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    31     lv_time_int_low      TYPE i,                                                            
       32     lv_timediff_int      TYPE i,                                                            
       33     lv_datediff_int      TYPE i,                                                            
       34     lv_time              TYPE t,                                                            
       35     ls_time              TYPE tstr_timestr.                                                 
       36                                                                               
    37 * check timestamp parameter                                                                 
       38 * ASSERT NOT iv_timestamp_high IS INITIAL.                                                  
       39 * ASSERT NOT iv_timestamp_low  IS INITIAL.                                                  
       40 * ASSERT iv_timestamp_low <= iv_timestamp_high.                                             
       41   IF iv_timestamp_high IS INITIAL                                                           
       42   OR iv_timestamp_low  IS INITIAL.                                                          
       43     RAISE invalid_parameter.                                                                
       44   ENDIF.                                                                               
    45   IF iv_timestamp_high < iv_timestamp_low.                                                  
       46     RAISE invalid_parameter.                                                                
       47   ENDIF.                                                                               
    48                                                                               
    49 * prepare timestamps                                                                        
       50 * .. split into date and time integers                                                      
       51   ls_timestamp_high = iv_timestamp_high.                                                    
       52   lv_date_int_high  = ls_timestamp_high-date.                                               
       53   lv_time_int_high  = ls_timestamp_high-time.                                               
       54   ls_timestamp_low  = iv_timestamp_low.                                                     
       55   lv_date_int_low   = ls_timestamp_low-date.                                                
       56   lv_time_int_low   = ls_timestamp_low-time.                                                
       57                                                                               
    58 * .. calc date diff                                                                         
       59 * .. check against max. allowed integer difference                                          
       60   lv_datediff_int = lv_date_int_high - lv_date_int_low.                                     
    >>>>>   ASSERT lv_datediff_int <= lc_datediff_intmax.                                             
       62                                                                               
    63 * calc time diff                                                                               
    64   lv_timediff_int = lv_time_int_high - lv_time_int_low.                                     
       65   IF lv_timediff_int < 0.                                                                   
       66     ADD 86400 TO lv_timediff_int.                                                           
       67     SUBTRACT 1 FROM lv_datediff_int.                                                        
       68   ENDIF.                                                                               
    69                                                                               
    70 * calc total duration                                                                       
       71   lv_duration_int = lv_datediff_int * 86400 + lv_timediff_int.                              
       72   lv_time = lv_timediff_int.                                                                
       73   ls_time = lv_time.                                                                        
       74   ls_duration-hours   = lv_duration_int DIV 3600.                                           
       75   ls_duration-minutes = ls_time-minute.                                                     
       76   ls_duration-seconds = ls_time-second.                                                     
       77                                                                               
    78   ev_duration_packed  = ls_duration.                                                        
       79   ev_duration_integer = lv_duration_int.                                                    
       80 ENDFUNCTION.                                                                               
    Contents of system fields                                                                         
    Name     Val.                                                                               
    SY-SUBRC 0                                                                               
    SY-INDEX 0                                                                               
    SY-TABIX 1                                                                               
    SY-DBCNT 1                                                                               
    SY-FDPOS 6                                                                               
    SY-LSIND 0                                                                               
    SY-PAGNO 0                                                                               
    SY-LINNO 1                                                                               
    SY-COLNO 1                                                                               
    SY-PFKEY                                                                               
    SY-UCOMM                                                                               
    SY-TITLE CIF - Comparison/Reconciliation of Transaction Data                                      
    SY-MSGTY                                                                               
    SY-MSGID                                                                               
    SY-MSGNO 000                                                                               
    SY-MSGV1                                                                               
    SY-MSGV2                                                                               
    SY-MSGV3                                                                               
    SY-MSGV4                                                                               
    Active Calls/Events                                                                               
    No.   Ty.          Program                             Include                             Line   
          Name                                                                               
    5 FUNCTION     /SAPAPO/SAPLTIMESTAMP               /SAPAPO/LTIMESTAMPU08                  61  
          /SAPAPO/TIMESTAMP_DIFFERENCE                                                                
        4 FORM         /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3F17                349  
          COMPARE_ORDER_HEADER                                                                        
        3 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U03                125  
          /SAPAPO/CIF_DELTA3_COMP_ORDER                                                               
        2 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U01                871  
          /SAPAPO/CIF_DELTA3_COMP                                                                     
        1 EVENT        /SAPAPO/CIF_DELTAREPORT3            /SAPAPO/CIF_DELTAREPORT3              189  
          START-OF-SELECTION                                                                          
    Chosen variables                                                                               
    Name                                                                               
    Val.                                                                               
    No.       5 Ty.          FUNCTION                                                                 
    Name  /SAPAPO/TIMESTAMP_DIFFERENCE                                                                
    IV_TIMESTAMP_HIGH                                                                               
    #q1###                                                                               
    02073899                                                                               
    2001125C                                                                               
    IV_TIMESTAMP_LOW                                                                               
    ##q!####                                                                               
    00720899                                                                               
    2011125C                                                                               
    EV_DURATION_INTEGER                                                                               
    0                                                                               
    0000                                                                               
    0000                                                                               
    EV_DURATION_PACKED                                                                               
    000000                                                                               
    00000C                                                                               
    SYST-REPID                                                                               
    /SAPAPO/SAPLTIMESTAMP                                                                         
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254545444554452222222222222222222                                                      
        F31010FF310C49D5341D00000000000000000000                                                      
    %_SPACE                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    LS_TIMESTAMP_HIGH                                                                               
    22000713182959                                                                               
    00000000000000                                                                               
    00000000000000                                                                               
    33333333333333                                                                               
    22000713182959                                                                               
    LV_DATE_INT_HIGH                                                                               
    803363                                                                               
    0042                                                                               
    0C23                                                                               
    LS_TIMESTAMP_HIGH-DATE                                                                               
    22000713                                                                               
    00000000                                                                               
    00000000                                                                               
    33333333                                                                               
    22000713                                                                               
    LV_TIME_INT_HIGH                                                                               
    66599                                                                               
    0002                                                                               
    0147                                                                               
    LS_TIMESTAMP_HIGH-TIME                                                                               
    182959                                                                               
    000000                                                                               
    000000                                                                               
    333333                                                                               
    182959                                                                               
    LS_TIMESTAMP_LOW                                                                               
    20071210182959                                                                               
    00000000000000                                                                               
    00000000000000                                                                               
    33333333333333                                                                               
    20071210182959                                                                               
    LV_DATE_INT_LOW                                                                               
    733021                                                                               
    0025                                                                               
    0BFD                                                                               
    LS_TIMESTAMP_LOW-DATE                                                                               
    20071210                                                                               
    00000000                                                                               
    00000000                                                                               
    33333333                                                                               
    20071210                                                                               
    LV_TIME_INT_LOW                                                                               
    66599                                                                               
    0002                                                                               
    0147                                                                               
    LS_TIMESTAMP_LOW-TIME                                                                               
    182959                                                                               
    000000                                                                               
    000000                                                                               
    333333                                                                               
    182959                                                                               
    SY-UNAME                                                                               
    SCMATP                                                                               
    000000000000                                                                               
    000000000000                                                                               
    544455222222                                                                               
    33D140000000                                                                               
    SCREEN-INPUT                                                                               
    1                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    1                                                                               
    LV_DATEDIFF_INT                                                                               
    70342                                                                               
    001C                                                                               
    0126                                                                               
    LV_TIMEDIFF_INT                                                                               
    0                                                                               
    0000                                                                               
    0000                                                                               
    SYST                                                                               
    #######################################&#332;###############################################&#19800; C#&#1280;##
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
        000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
        0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
        0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
    SY-REPID                                                                               
    /SAPAPO/SAPLTIMESTAMP                                                                         
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254545444554452222222222222222222                                                      
        F31010FF310C49D5341D00000000000000000000                                                      
    %_DUMMY$$                                                                               
    0000                                                                               
    0000                                                                               
    2222                                                                               
    0000                                                                               
    No.       4 Ty.          FORM                                                                     
    Name  COMPARE_ORDER_HEADER                                                                        
    SYST-REPID                                                                               
    /SAPAPO/SAPLCIF_DELTA3                                                                        
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254544445444543222222222222222222                                                      
        F31010FF310C396F45C413000000000000000000                                                      
    GC_APPEND_MODE                                                                               
    3                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    3                                                                               
    LS_FIELDS_TO_COMPARE-DUEDATE                                                                      
        X                                                                               
    0                                                                               
    0                                                                               
    5                                                                               
    8                                                                               
    SYST                                                                               
    #######################################&#332;###############################################&#19800; C#&#1280;##
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
        000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
        0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
        0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
    LS_APO_ORDER-ORDTYPE                                                                               
    5                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    5                                                                               
    GC_PLANNED_ORDER                                                                               
    5                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    5                                                                               
    LS_R3_ORDER-STATUSCNF                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    GC_ORDER_STATUS_NO_CONF                                                                               
    1                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    1                                                                               
    LS_APO_ORDER-STATUSCNF                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    GC_PRED_OUT_DEL                                                                               
    A                                                                               
    0                                                                               
    0                                                                               
    4                                                                               
    1                                                                               
    GC_TND_DELETE                                                                               
    CN                                                                               
    00                                                                               
    00                                                                               
    44                                                                               
    3E                                                

    Dear Sajit,
    Go through the following OSS Notes:
    <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=901957&_NLANG=E">901957</a>, <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1036880&_NLANG=E">1036880</a>, <a href="https://websmp110.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1067414&_NLANG=E">1067414</a>
    Regards,
    Naveen.

Maybe you are looking for

  • JBO Exception while running OAF page from Jdev

    Hi All, I am using jdev 10.1.3 on R12 instance. I am trying to customize a standard OAF page. For that I downloaded all the related directories from the server and placed it in the corresponding folders of jdev. When I rebuild the page it is rebuildi

  • Default style for input

    I need a way to change the default style of a textfield. For example, if the textfield is required, I want the set the background color to yellow (FFFFCC) so that when the page containing that textfield loads the background color will already be yell

  • Information about arguments needed to send a mail

    Hi, I am very new to java mail. I am jus trying to send a mail using java mail. Can anyone please tell me wht are the command line arguments, tht i have to give in the following code. import java.util.Properties; import javax.mail.*; import javax.mai

  • Connection Timeout error message - HELP!

    Hi, I am so fed up with my internet connection....so here is my story.... I live above a shop in a rented flat which is owned by the shop owner, he kindly gave me the password for his router so I could use his internet free of charge. This has worked

  • I cant add apps to my kid's iPod Touch. (i have iPhone 4)

    Hey there, thanks in advance for any help soemone can give me. I Have a mac desktop computer (if that matters) & i have an iPhone 4. the kids love to play apps/games on it so for xmas hubby & I got the kids both an iPod Touch. Ive never had an issue