Run time error while saving a sales order

After CIn configuration when i raise the sales order i cannot save it. when i click on the save icon the following runtime error message x302 (v3) with the short dump.. pls guide..
thanks...

Hi sanjitdutta,
Please get in touch with your ABAP team to know wat exactly is teh cause for the short dump. Please post the error description completely.
Thanks
Arun
Edited by: arun subramani on May 16, 2011 7:06 AM

Similar Messages

  • Run time error while creating a sales order by va01

    hi ,
         while  i am creating a sales order a runtime error occurs as i fill entry for sole to party and then material and quantity and as i press enter. the run time error is:
    error in current abap program "saplv61z"  had to be terminated because it has come across the statement that unfortunately can not be executed.
    kindly solve my problem.
    thanks.

    Hi Agrawal
    As you are getting run-time error after entering the sold to party and material and the error is in SAPLV61Z ,
    close the session for sometime and open again and then create sales order and then enter sold to party and material and then check wheather you are getting or not. If you are still facing the problem then take the help of the ABAP & BASIS consultant's.
    Regards
    Srinath

  • Run time error while saving the production order in CO02

    HI Experts,
    While i am releasing and saving the production order the system is giving the runtime error. Please help.
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SLD_API_EXCEPTION
    Error analysis is
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SLD_API_EXCEPTION', was not
    caught in
    procedure "GET_ACCESS_DATA" "(METHOD)", nor was it propagated by a RAISING
    clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    Internal error in method
    A Quick response is required.
    Regards
    Dinakar Sarma

    Hi,
    Please check below  link for your issue , it may useful
    http://forums.sdn.sap.com/thread.jspa?messageID=10815298#10815298
    Regards,
    Ram

  • RunTime Error while saving a Sales Order

    Hi All,
    When i am saving a Sales Order, the system is throwing a Runtime Error.
    The ABAP Code in the Runtime Error screen as follows.
              select * from (t681-kotab) appending table <cond_tab>
                     up to 1 rows
                     where kappl  = se_kappl
                     and   kschl  = se_kschl
                     and   datbi >= se_date
                     and   datab <= se_date
                     and   (coding_tab).
    Till these days, there was no such error while saving a Sales Order.
    How to resolve this issue?
    Regards
    Pavan

    Hi,
    The below piece of code is trying to get the contents of the table mentioned in T681-KOTAB.
    select * from (t681-kotab) appending table <cond_tab>
    up to 1 rows
    where kappl = se_kappl
    and kschl = se_kschl
    and datbi >= se_date
    and datab <= se_date
    and (coding_tab).
    The reason could be is someone has screwed up the entries in T681 table. Check that out.
    Try to put a break point on this SELECT query and see what the value of T681-KOTAB holds before the SELECT query. Check whether such a table entry exists in DB.
    Let me know if you are still stuck up.
    If you can send me the ST22 dump of the run time error, i might be able to help you more  on this.
    Hope this helps.
    Thanks,
    Balaji

  • Error while saving the Sales Order

    Hi experts,
        i am getting a runtime error while saving a sales order stating: SAPSQL_EMPTY_TABNAME. It says the field T681-KOTAB could be empty. I would give in more inputs. Someone plz help.
    Thanks.

    I would expect that KOTN521 would be a Database table defined in the ABAP Dictionary that relates to the condition implemented in 521 for the usage specified in that record.
    You should be able to go into the info system, SE84, and search under ABAP Dictionary / Database Tables to see what KOTN521 is.
    Also, since the only Keys to T681 are KVEWE and KOTABNR, and there are two KOTABNR entries with a value of 521, then there must be two different usages (KVEWE) associated with that table.
    If you see what they are, you can check to see what the usages represent.   Based on a lookup, it appears that a usage of N is for Free Goods, A is for Pricing etc.   In our system, we only have A entries.
    What are the usages for the 521 entries?  Do they relate to Free Goods/Pricing???
    Does the table KOTN521 exist in the ABAP Dictionary?
    Answering these questions may get you closer to the answer.
    Can you compare the values in these entries to what you have in different SIDs?
    Is this problem happening in Production, or is it still in a development or Quality Assurance client?
    If it is still in development or Q, then it may be that a recent customization change was made.
    Compare the entries across your systems, if possible.
    Good luck
    Brian

  • Error while saving a Sales Order in the CRM Mobile Application

    Hi,
    I am facing issues while saving a Sales Order in the CRM Mobile Application. I am getting the error message "Value Field KvLangu is not valid (Error: 236 / 1102)".
    I would be very grateful if somebody had faced this issue before and this way could help me with some information.
    Best Regards,
    Rogerio Prado.

    Hi Rogerio,
    You should put mobile sales related messages in the forum "CRM Mobile applications"
    This error message is coming because the language table SMOT002 might be empty in your mobile client OR it does not have all the values which have been customized in the system.
    You need to have subscription based on publication "customizing objects" assigned to your site.
    Regards
    Vivek

  • Error while Saving Service Sales order.

    Hi..
    Please help me for resolving below error..
    While saving service sales order error is coming as-
    Invalid account assignment category...
    Detailed Error-
    "Assign components to a/c assignment category & Account Assigmnet Category not defined.
    In customisining a/c assgnment cate for ser & mainta order .In standard define the following values for the order category 30.A/c Asd type general F,
    A/c *** type Project Q,A/c assigment type Sales Order E,Sales Doc Project D".
    Awaiting for your inputs....
    Thanks
    Manoj Mahajan

    Hi Manoj,
    Account Key assigned to the pricing condition hasn't been configured completely.
    Please check the appropriate account key and speak to your FI team.
    Pl award me points if it is helpful.
    Let me know if you need more details.
    Thanks,
    Ramesh

  • Run time error while saving sales order

    Hi all,
    i am working on IDES ECC 6.0, when i am saving an sales order(OR) i am getting run time error in the table CRMPAROLTP, program SAPMV45A.
    i am using 4 GB RAM, still having a space of 30 GB for only IDES to save the data.
    so, how to solve it.

    Hello,
    I doubt the runtime error (I am assuming you mean that you got a short dump) you mentioned in your original post has anything to do with the warning messages you see when doing a check (Ctrl+F2) on table CRMPAROLTP and program SAPMV45A.  These warnings should not cause a short dump or runtime error.
    The warning message for the table has the following long text:
    Table CRMPAROLTP: Key length > 120 (Restricted functionality)
    Message no. DT214
    Diagnosis
    The key length, i.e. the sum of the field lengths of all the key fields of the table, is more than 120 bytes.
    System response
    This is a warning.
    Procedure
    Note the following restricted fuctionality for this table:
    - Table contents cannot be transported by specifying key values, at
      best by specifying generic key values with a maximum length of 120
      bytes.
    - The table may not be used as the base table of a lock object.
    The warnings in SE38 for program SAPMV45A are mostly related to Unicode and have no reference to the table CRMPAROLTP.
    If you haven't already done so, please check the SAP Note referenced in my first reply since this does provide a solution for short dumps related to table CRMPAROLTP.
    Of course, since I don't know specifically what the short dump message is that you received, I could be basing my assessment on false assumptions.  If you have those details it is better for the SDN community as a whole if you include the information in this thread instead of sending it to me offline.
    Best Regards,
    Jamie

  • Run time error while closing the CRM Order using BAPI

    Hi Experts,
    Need your invaluable suggestions here.Apologies for the lengthy mail, intention is to give clear idea of the issue.
    I am facing an issue while closing the CRM orders. According to our business process, when an issue is solved we will keep the order in resolved status only. We will not directly close the order from the CRM tool, instead we have created a custom program for the same purpose.
    For the custom program we will give input as the order number and execute it, this will close the order.
    Here close the order means assigning it to Close status as well assign the reason code.
    We have created some reason codes for closed status.
    So when the program is run the Order moves from resolved status to closed status along with reason code.
    But of late we are facing some problems with this program, it is giving run time error for some CRM orders.
    Run time error message : The ABAP/4 Open SQL array insert results in duplicate database records.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught in procedure "CRM_SERVICE_OS_UPD_OST_DU" "(FUNCTION)", nor was it propagated by a RAISING clause.
    Please find my code which have used in the custom program
    Closing the resolved SOs in the system
        CALL FUNCTION 'CRM_STATUS_CHANGE_EXTERN_OW'
            EXPORTING
              objnr                     = iv_guid
              user_status          = lc_status_closed
           EXCEPTIONS
             object_not_found          = 1
             status_inconsistent       = 2
             status_not_allowed       = 3
             OTHERS                        = 4.
        IF sy-subrc <> 0.
          WRITE :  'Error at maintaining status'.
        ENDIF.
    Set reason code
    build lt_subject
        ls_subject-ref_guid = iv_guid.
        ls_subject-katalogart = 'A2'.
        ls_subject-codegruppe = 'ZR000003'.
        ls_subject-code       = 'ZR33'.                      " Reason code
        ls_subject-mode       = 'A'.
        APPEND ls_subject TO lt_subject.
    build lt_ossset
        ls_osset-ref_guid        = iv_guid.
        ls_osset-subject_profile = 'ZREASON03'.
        ls_osset-profile_type    = 'G'.
        ls_osset-subject         = lt_subject.
        APPEND ls_osset TO lt_osset.
    build lt_service_os
        ls_service_os-ref_guid  = iv_guid.
        ls_service_os-ref_kind  = 'A'.
        ls_service_os-osset     = lt_osset.
        APPEND ls_service_os TO lt_service_os.
    build lt_input_fields
        REFRESH: lt_input_fields, lt_field_names.
        CLEAR  : ls_input_fields, ls_field_names.
        ls_field_names-fieldname    = 'CODE'.
        APPEND ls_field_names TO lt_field_names.
        ls_field_names-fieldname    = 'CODEGRUPPE'.
        APPEND ls_field_names TO lt_field_names.
        ls_field_names-fieldname    = 'KATALOGART'.
        APPEND ls_field_names TO lt_field_names.
        ls_field_names-fieldname    = 'SERVICE_PROFILE'.
        APPEND ls_field_names TO lt_field_names.
        ls_input_fields-ref_guid    = iv_guid.
        ls_input_fields-ref_kind    = 'A'.
        ls_input_fields-objectname  = 'SERVICE_OS'.
        ls_input_fields-field_names = lt_field_names.
        APPEND ls_input_fields TO lt_input_fields.
         CALL FUNCTION 'CRM_ORDER_MAINTAIN'
          EXPORTING
            it_service_os     = lt_service_os
          CHANGING
            ct_input_fields   = lt_input_fields
          EXCEPTIONS
            error_occurred    = 1
            document_locked   = 2
            no_change_allowed = 3
            no_authority      = 4
            OTHERS            = 5.
        IF sy-subrc <> 0.
          WRITE :  'Error at maintaining reason'.
        ENDIF.
        CALL FUNCTION 'CRM_ORDER_SAVE'
          EXPORTING
            it_objects_to_save   = lt_header_guid
            iv_update_task_local = lv_update_task_local
          IMPORTING
            et_saved_objects     = lt_saved_objects
          EXCEPTIONS
            document_not_saved   = 1
            OTHERS               = 2.
        IF sy-subrc <> 0.
          WRITE : 'Error at saving'.
        ELSE.
          WRITE : 'Successfully Closed'.
          COMMIT WORK AND WAIT.
        ENDIF.
    Run time error is coming at COMMIT WORK AND WAIT statement.
    Please let me know any corrections are required in the above program.
    When I analyzed the run time error I have found that it trying to insert the record in CRMD_SRV_OSSET for that CRM order, but already one record is present in the table for the same CRM order number.
    For most of the CRM orders there is no entry in this table so they are closing successfully but for a few orders for which there is an entry we are getting the above run time error.
    There is nothing wrong with the orders which have an entry already in the table CRMD_SRV_OSSET, I need to close these kind of orders with out run time error.
    Kindly provide your feedback.

    Hi Dinakar,
    You posted this in APO PPDS forum. This question should go to PP forum where someone could answer it.
    Please close this thread and open a new thread in PP forum so that you could get help quickly from the relevant experts.
    Regards - Pawan

  • RUn time error while  saving po    Field symbol has not yet been assigned.

    Hi Experts,
    I am getting abap dump while saving PO in ME21N  plz seee the below dump  plzzzzzzzzzzzzzzzzzzzzz help me
    Runtime Errors         GETWA_NOT_ASSIGNED
    Date and Time          19.06.2009 11:24:46
    Short dump has not been completely stored (too big)
    Short text
         Field symbol has not yet been assigned.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLKKBL" 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
         You attempted to access an unassigned field symbol
         (data segment 106).
         This error may occur if
         - You address a typed field symbol before it has been set with
           ASSIGN
         - You address a field symbol that pointed to the line of an
           internal table that was deleted
        - You address a field symbol that was previously reset using
          UNASSIGN or that pointed to a local field that no
          longer exists
        - You address a global function interface, although the
          respective function module is not active - that is, is
          not in the list of active calls. The list of active calls
          can be taken from this short dump.
    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:
        "GETWA_NOT_ASSIGNED" " "
        "SAPLKKBL" or "LKKBLF99"
        "GEN_FIELD_OUT2"
        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.
    em environment
    SAP-Release 700
    Application server... "gplqty"
    Network address...... "128.12.0.19"
    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... "GPLQTY"
    Database type..... "MSSQL"
    Database name..... "GPQ"
    Database user ID.. "gpq"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Aug 4 2008 02:33:25"
      create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
      Database version. "SQL_Server_8.00 "
      Patch level. 172
      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...... 16759360
      Heap.... 0
      Page.... 237568
      MM Used. 12036016
      MM Free. 530432
    er and Transaction
      Client.............. 410
      User................ "SAP_SUPPORT"
      Language key........ "E"
      Transaction......... "ME21N "
      Transactions ID..... "9E955CDE97CBF1648B4C001A64C7B85A"
      Program............. "SAPLKKBL"
      Screen.............. "SAPLKKBL 0500"
      Screen line......... 3
    Information on where terminated
        Termination occurred in the ABAP program "SAPLKKBL" - in "GEN_FIELD_OUT2".
        The main program was "RM_MEPO_GUI ".
        In the source code you have the termination point in line 2908
        of the (Include) program "LKKBLF99".
    Source Code Extract
    Line  SourceCde
    2878       else.
    2879         assign <fs11> to <field>.
    2880         gs_fc = gs_sfc11.
    2881       endif.
    2882     when 012.
    2883       if gs_out_flags-slave ne 'X'.
    2884         assign <fm12> to <field>.
    2885         gs_fc = gs_mfc12.
    2886       else.
    2887         assign <fs12> to <field>.
    2888         gs_fc = gs_sfc12.
    2889       endif.
    2890     when 013.
    2891       if gs_out_flags-slave ne 'X'.
    2892         assign <fm13> to <field>.
    2893         gs_fc = gs_mfc13.
    2894       else.
    2895         assign <fs13> to <field>.
    2896         gs_fc = gs_sfc13.
    2897       endif.
    2898     when 014.
    2899       if gs_out_flags-slave ne 'X'.

    Hi,
    this error occurs when you try to address a field-symbol before it has been assigned to a field or
    the assignment has failed.
    Use following code to remove this dump
    Assign <mara-matnr> to <fs>.
    if sy-subrc <> 0.
      Error Message.
    Endif.
    Hope it helps,
    Raj

  • Run time error while saving migo

    Dear All,
    I am doing the subcontracting process. and while saving the MIGO it shows Runtime Error.
    Error analysis
        Short text of error message:
        No taxes on sales/purch.are allowed for account 428304 BS70, V0 is not a
        llowed
        Technical information about the message:
        Message classe...... "FS"
        Number.............. 217
        Variable 1.......... 428304
        Variable 2.......... "BS70"
        Variable 3.......... "V0"
        Variable 4.......... " "
    Trigger Location of Runtime Error
        Program                                 SAPLMBWL
        Include                                 LMBWLU21
        Row                                     59
        Module type                             (FUNCTION)
        Module Name                             MB_POST_GOODS_MOVEMENT
    BS70 is a company code.
    Please help me out.
    Thanks & Regards,
    Sandeep Patil.

    Dear All,
    i have done that but now another error is coming as
    Error analysis
        Short text of error message:
        Balance in transaction currency
        Technical information about the message:
        Message classe...... "F5"
        Number.............. 702
        Variable 1.......... 00
        Variable 2.......... " 5.000,000"
        Variable 3.......... "INR"
        Variable 4.......... " "
    5.000,000 is my po value.
    Thanks & Regards,
    Sandeep.

  • Run time error while saving values in File (Tcode)

    Hi,
    I am using FM   call function 'FILE_GET_NAME'
           exporting
                logical_filename = logical_filename
                parameter_1      = program_name
                parameter_2      = file_id_param
           importing
                file_name        = physical_filename
           exceptions
                file_not_found   = 1
                others           = 2.
    for this I am trying to maintain dynamic values(field symbols) in Tcode FILE Logical file name definition , physical path as.
    Physical file   =<PARAM_1>.<PARAM_2>
    But while saving it dumps, saying filed symbol assinment to substring is not allowed.
    Physical path for the same is /<V=Z_DIR_MAIN>/<SYSID>/<V=Z_DIR_OUT>/<FILENAME>.<CLIENT>.<DATE><TIME>.
    Regards
    Mohinder Singh Chauhan

    Hello Mohinder,
    the better way to analyse these kind of things is by entering the function module in se37 and providing the required test data.
    In your scenarion as you say its throwing a runtime dump related to field symbols better you concatenate the data param1 and param2 into a new variable and then pass that value into the function module.
    Thanks,
    M.Naveen kumar

  • Error while saving the Sales Order details in EBS R12 Instance

    Hi all,
    After specifying the details of sales order. We are cant save the changes.
    It gives the error like :
    ERROR: AN UNEXPECTED ERROR HAS OCCURRED. PLEASE CONTACT YOUR SYSTEM ADMINISTRATOR.
    Actually system admin was not aware of these error. So can you please advice us to proceed this error.
    Regards,
    Thanvir A

    Wrong thread. This is the Data Guard thread and your problem has nothing to do with Data Guard. Either find the right thread or open a Service Request.
    Larry

  • Run Time Error when go to sales order change tcode :va02

    Hi All,
    I am functional guy and  i am facing the following situation
    1.System is allowing to create the sales order through VA01 and also saved it
    2.When i want to see the same sales order throug Va02 i am getting runtime error

    Attach at least a download of the dump (ST22) or post  to your post, as you clearly didn't give enough information to get correct answers. (Asking Good Questions in the SCN Discussion Spaces will help you get Good Answers and similar documents.)
    Regards,
    Raymond

  • Run Time Error while Entering Quantity in Sales Order

    Dear All,
    Iam getting Run time Error while iam entering material quantity in sales order.Please  find the screenshot of the same.
    kindly Help Me.Me. Plz note that we had done a system copy two days back to our new server.
    Rgds
    Thomson
    ST22 Screenshot

    Dear All
    Its Resolved Thanks For your Valuable time Support
    INCLUDE LV03VFB4 inside below code trigger error.
    PERFORM VVBBD_AUFBAUEN USING WA_AVBBD
                                        WA_AVBBD-APOMOBILE
                                        DA_SUBRC
                                        DA_UPDKZ
                                        DA_VVBBD_TABIX
                                        0.
    This Was the Error some how 0 was there we are removed the 0 now it is working fine
    Rgds
    Thomson

Maybe you are looking for