Transaction Code F.50 Runtime Error

Dear Friends,
While executing T.code F.50, I am getting the following Error
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC                                                 
Exceptn                CX_SY_OPEN_SQL_DB                                                          
Date and Time          25.06.2009 11:27:31                                                                               
ShrtText                                                                               
The ABAP/4 Open SQL array insert results in duplicate database records.                                                                               
What happened?                                                                               
Error in ABAP application program.                                                                               
The current ABAP program "SAPLF049" had to be terminated because one of the                  
     statements could not be executed.                                                                               
This is probably due to an error in the ABAP program.                                                                               
Error analysis                                                                               
An exception occurred. This exception is dealt with in more detail below                     
     . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was                     
      neither                                                                               
caught nor passed along using a RAISING clause, in the procedure                             
      "SICHERN_IN_DB" "(FORM)"                                                                    
Since the caller of the procedure could not have expected this exception                     
      to occur, the running program was terminated.                                               
     The reason for the exception is:                                                             
     If you use an ABAP/4 Open SQL array insert to insert a record in                             
     the database and that record already exists with the same key,                               
     this results in a termination.            
      (With an ABAP/4 Open SQL single record insert in the same error      
situation, processing does not terminate, but SY-SUBRC is set to 4.) 
Program                                 SAPLF049                                               
Include                                 LF049F00                                               
Row                                     74                                                     
Module type                             (FORM)                                                 
Module Name                             SICHERN_IN_DB                                                                               
gger Location of Exception                                                                      
Program                                 SAPLF049                                               
Include                                 LF049F00                                               
Row                                     86                                                     
Module type                             (FORM)                                                 
Module Name                             SICHERN_IN_DB                                                                               
rce Code Extract                                                                               
e  SourceCde                                                                               
56 *      Insert von RF048 aus CRF048 (bei Commit Work)                   *                     
57 *----
58 FORM RELATION_SAVE.                                                                          
59                                                                               
60   CHECK NOT CRF048[] IS INITIAL.                                                             
61   INSERT RF048 FROM TABLE CRF048.                                                            
62   REFRESH CRF048.                                                                            
63                                                                               
64 ENDFORM.                    "RELATION_SAVE                                                
65                                                                               
66                                                                               
67                                                                               
68 *eject                                                                               
69 *----
70 *      Form  SICHERN_IN_DB                                             *                  
71 *----
72 *      Masseninsert/update aus Z-Tabellen                              *                  
73 *----
74 FORM SICHERN_IN_DB.                                                                       
75                                                                               
76 * Lokale Daten                                                                            
77 DATA:                                                                               
78       ld_xnetb   TYPE xnetb,                                                              
79       anz_belnr  TYPE i.                                                                  
80                                                                               
81 *------ Aufteilungstabellen -
82                                                                               
83 * Einfügen                                                             *                  
84                                                                               
85 * BFIT_A0                                                                               
>>>   INSERT BFIT_A0 FROM TABLE ZBFIT_A0.                                                     
87   IF SY-SUBRC <> 0.                                                                       
88     MESSAGE A153.                                                                         
89   ENDIF.                                                                               
90                                                                               
91 * BFIT_A                                                                               
92   INSERT BFIT_A FROM TABLE ZBFIT_A.                                                       
93   IF SY-SUBRC <> 0.                                                                       
94     MESSAGE A154.                                                                         
95   ENDIF.                                                                               
96                                                                               
97 * BFOD_A                                                                               
98   INSERT BFOD_A FROM TABLE ZBFOD_A.                                                     
99   IF SY-SUBRC <> 0.                                                                     
100     MESSAGE A155.                                                                       
101   ENDIF.                                                                               
102                                                                               
103 * BFOD_AB                                                                               
104   INSERT BFOD_AB FROM TABLE ZBFOD_AB.                                                   
105   IF SY-SUBRC <> 0.                                                                               
How to reslove the error? Please advise.
Thanks and Regards
Sridhar

Hi,
Well it looks quite difficult to understand.......The only thing it says clearly that this is happening because of duplicate Primary Key insertion.

Similar Messages

  • Finding the transaction of an abap runtime error

    hello,
    is it possible to find out the corresponding transaction to an abap runtime error?
    till now i've got all informations like they are shown in ST22 in my abap program. but i'd also like to have the transaction code, not only the corresponding devclass, subapplication and application.
    does anyone know a function module or any other solution for that problem?
    thanks in advance
    joschi

    When you are analyzing your short dump via ST22, there is a section called "User, transaction..." where the following information is shown:
    Client
    User
    Language key
    Transaction
    Program
    Screen
    That section will show you the transaction code you need.
    I hope that helps,

  • MIR4 transaction is giving ABAP Runtime Error

    Hi Experts,
    When I am trying to display the invoice in MIR4 and/or MIRO the system is generating ABAP runtime error.  DYNPRO_FIELD_CONVERSION.  This is in Version ECC 6.0.
    Short text
        Conversion error
    What happened?
        The current screen processing action was terminated since a situation
        occurred where the application could not continue.
        This is probably due to an error in the ABAP program or in the curren
        screen.
    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 manag
        termination messages, in particular for long term reference.
    Error analysis
        The program has been interrupted and cannot resume.
        Program "SAPLMR1M" attempted to display fields on screen 6310.
        An error occurred during the conversion of this data.
    How to correct the error
        There was a conversion error in the output of fields to the screen.
        The formats of the ABAP output field and the screen field may not match.
        Some field types require more space on the screen than in the ABAP
        program. For example, a date output field on the screen requires two
        more characters than the corresponding field in the ABAP program. When
        the date is displayed on the screen, an error occurs resulting in this
        error message.
                      Screen name.............. "SAPLMR1M"
                      Screen number............ 6310
                      Screen field............. "DRSEG-REMNG"
                      Error text............... "FX015: Sign lost."
        Other data:
        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.
    Please help us to solve this issue.
    Thanks and Regards,
    Havina
    Edited by: Havina Kutty on May 19, 2009 11:54 AM

    Hello,
    Please refer
    Note 503934 - MIRO: Dump DYNPRO_FIELD_CONVERSION -> field 'REMNG'
    Note 445853 - MIR4:more credit memos than invoices for service
    Note 393189 - MIRO: Incorrect update of BPMNG -> DYNPRO_FIELD_CONVERSION
    Regards,
    Ravi

  • Db50 transaction then it says "Runtime error '6': Overflow"

    hi all,
    while start to perform full backup from dbmgui if launch from db50 transaction Tools tree then it says "Runtime error '6': Overflow " kind of pop-up message comes.
    I want to attach screenshot here.
    How can I do that? Is it possible?
    Thanks in advance for any pointers.

    Hi Vikash,
    there's no option to upload any attachments here in the forum.
    Since you're using DB50 you must be a SAP customer. So get something for your maintenance fee and open a support message for this issue.
    regards,
    Lars

  • How to read the long text in Transaction Code : VA02 at runtime??????

    Hi,
    I am undable to find the long text in TC: VA02 at runtime. Actulally my requirement is like how to compare between the item level long text at runtime and existing long text for that item.
    If any body has soluntion, please provide me. I would really be  greatfull if any body provide the solution.
    Deepak Kumar
    E-Mail: [email protected]

    Hi Sudheer,
    Actually my requirement is to read the text at runtime. Example: If saved text is 'ABC' and it is changed by '123'. Now before saving changed text '123', I need to capture it so that I can compare it with saved text 'ABC' whether it is changed or not?
    Couuld you send me some sample code? I would appreciate if you reply at the earliest.
    Deepak Kumar.

  • Error in transaction code MB01

    Hi,
    While doing th goods receipt for a Purchase order in MB01 transaction code ,  I am getting error message as "Inconsistency between a document field and profitability segment number "
    Here account assignment category of PO is - All aux.acct.assgts.
             Item category is : Third party.
    Please help me in this issue.
    Thanks,
    Usha.

    Hi Can you please explain me how to check this inconsistency for G/L account.
    I found the G/L account for that perticular company code and valuation area.
    Please explain me .
    Thanks ,
    Usha.

  • Runtime Errors  DATA_LENGTH_0    Exception   CX_SY_RANGE_OUT_OF_BO

    Hi All,
    While using leave request service we are getting following dump in abap code , please advice
    Runtime Errors         DATA_LENGTH_0
    Exception              CX_SY_RANGE_OUT_OF_BOUNDS
    Date and Time          13.01.2012 10:17:48
         Invalid partial field access: Length 0
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "ZCL_PT_GEN_REQ================CP" 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_RANGE_OUT_OF_BOUNDS', was not
          caught in
         procedure "IF_EX_PT_GEN_REQ~SEARCH_FOR_NEXT_PROCESSOR" "(METHOD)", nor was it
          propagated by a RAISING clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         In the executed program "ZCL_PT_GEN_REQ================CP", the system
    attempted to access the field
    "IM_SEARCHSTRING" using the length 0.
    However, a partial field access with the length specification 0 is not
    allowed.
    How to correct the error
    Use a positive length specification if a part of the field "IM_SEARCHSTRING" is
    to be
    accessed.
    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:
    "DATA_LENGTH_0" "CX_SY_RANGE_OUT_OF_BOUNDS"
    "ZCL_PT_GEN_REQ================CP" or "ZCL_PT_GEN_REQ================CM002"
    "IF_EX_PT_GEN_REQ~SEARCH_FOR_NEXT_PROCESSOR"
    Dump At source code shows as following
    LOOP AT ex_persdata_tab INTO wa_ex_perdata.
            w_str3 = wa_ex_perdata-user.
            IF w_str3 CO im_searchstring.
              w_len2 = sy-fdpos.
              w_len1 = sy-fdpos + 1.
    **Get First name
              w_str2 = im_searchstring+w_len1.
    **Get last name
    ---->>>       w_str1 = im_searchstring(w_len2).       (Point of dump) (Data type String = char25)
              IF w_str2 EQ wa_ex_perdata-name.
                APPEND  wa_ex_perdata TO lt_ex_perdata.
                EXIT.
              ENDIF.
              CLEAR:w_str2,w_str1,w_len2,w_len1.
            ENDIF.
          ENDLOOP.
          CLEAR:wa_ex_perdata.

    attempted to access the field
    "IM_SEARCHSTRING" using the length 0.
    However, a partial field access with the length specification 0 is not
    allowed.
    that w_len2 of yours is having a value 0. you cant access a field with length 0. thats the error

  • Reg the CONVT_NO_NUMBER Runtime Error

    Dear all,
    I have been trying to upload the G/L account information and using BDC. I have reduced my input fields to Header Data, PK, Acct Number, Amount and KOSTL. When I call the transaction I get the runtime Error. I learnt its because of the Number Interpretation, and so did the coding. But still it says the same error.
    I declared a character field and moved the amount, filled the zeros for SAKNR and KOSTL but still throws the error.
    Any help will be appreciated, plss..
    Thanks in advance,
    Leo

    Dear all,
    Here I have pasted the code. Can you please check with amount.... The code is in FM.
    <u><b>INPUT VALUES</b></u>
    ITAB-BSCHL = '40'.
    ITAB-SAKNR = '812070'.
    ITAB-WRBTR = '30881.00'.
    *ITAB-GSBER = '1162 '.
    ITAB-KOSTL = '11620009'.
    <u><b>Date Validations</b></u>
    MOVE P_BUDAT(4)  TO TEM+4(4).
      MOVE P_BUDAT+4(2) TO TEM(2).
      MOVE P_BUDAT6(2) TO TEM2(2).
      MOVE P_BUDAT(4)  TO TEM+4(4).
      MOVE P_BUDAT+4(2) TO TEM(2).
      MOVE P_BUDAT6(2) TO TEM2(2).
      MOVE P_BLDAT(4)  TO TEM1+4(4).
      MOVE P_BLDAT+4(2) TO TEM1(2).
      MOVE P_BLDAT6(2) TO TEM12(2).
      MOVE P_BLDAT(4)  TO TEM1+4(4).
      MOVE P_BLDAT+4(2) TO TEM1(2).
      MOVE P_BLDAT6(2) TO TEM12(2).
    <u><b>AMOUNT</b></u>
    WRBTR IS CHARACTER OF LENGHT 16.
    WRITE ITAB-WRBTR TO WRBTR.
    translate WRBTR USING ','.
    CONDENSE WRBTR NO-GAPS.
    <u><b>SAKNR AND KOSTL Validations</b></u>
      IF ITAB-KOSTL+8(2) EQ SPACE.
        MOVE ITAB-KOSTL       TO  HOLD_KOSTL+2(8).
        MOVE '00'      TO  HOLD_KOSTL(2).
      ELSE.
        MOVE ITAB-KOSTL       TO  HOLD_KOSTL.
      ENDIF.
    FIELD_LENGTH = STRLEN( ITAB-SAKNR ).
      IF FIELD_LENGTH EQ 10.
        MOVE ITAB-SAKNR      TO   HOLD_SAKNR.
      ELSE.
        MOVE ITAB-SAKNR(6)     TO   HOLD_SAKNR+4(6).
        MOVE '0000'      TO   HOLD_SAKNR(4).
      ENDIF.
    <u><b>BDC</b></u>
    PERFORM NEW_DYNPRO USING 'SAPMF05A' '0100'.
    PERFORM NEW_FIELD USING 'BKPF-BUDAT' TEM.
    PERFORM NEW_FIELD USING 'BKPF-BLDAT' TEM1.
    PERFORM NEW_FIELD USING 'BKPF-MONAT' P_MONAT.
    PERFORM NEW_FIELD USING 'BKPF-WAERS' 'USD'.
    PERFORM NEW_FIELD USING 'BKPF-BUKRS' P_BUKRS.
    PERFORM NEW_FIELD USING 'BKPF-BKTXT' P_BKTXT.
    PERFORM NEW_FIELD USING 'RF05A-NEWBS' ITAB-BSCHL.
    PERFORM NEW_FIELD USING 'RF05A-NEWKO' HOLD_SAKNR.
    *PERFORM NEW_FIELD USING 'BDC_OKCODE' '/11'.
    PERFORM NEW_DYNPRO USING 'SAPMF05A' '0300'.
    PERFORM NEW_FIELD USING 'BSEG-WRBTR' WRBTR.
    PERFORM NEW_DYNPRO USING 'SAPLKACB' '0002'.
    PERFORM NEW_FIELD USING 'COBL-KOSTL' HOLD_KOSTL.
    PERFORM NEW_DYNPRO USING 'SAPMF05A' '0300'.
    PERFORM NEW_FIELD USING 'RF05A-NEWKO' '          '.
    PERFORM NEW_FIELD USING 'RF05A-NEWBS' '  '.
    PERFORM NEW_FIELD USING 'BDC_OKCODE' '/11'.
    CALL TRANSACTION 'F-02' USING BDCDATA MODE 'A' UPDATE 'A'.
    It says CONVT_NO_NUMBER occurs.
    Please help me in this, I know its simple but couldnt find the place of the error. Your help will be appreciated.
    Thanks & Regards
    Jay

  • 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

  • Runtime error in enhancement spot-' mereq_topline does  not exists.'

    Hi all,
    I have implemented an implicit enhancement spot in ME53n.
    When i applied break point in enhancement spot and control goes to ebhancement spot in debugging mode, i got purchse requisition number in mereq_topline.
    When i tried to use this structure value in code i get runtime error-
    ' mereq_topline does  not exists.'
    Can you please guide how to resolve  this runtime error.
    thanks.
    Edited by: Sanjay_lnt on Sep 20, 2010 8:52 AM

    Sanjay,
    try to delete the enhancement and recreate it
    Thanks
    Bala Duvvuri

  • Transaction code for SAP query reports

    Hi All,
    I am trying to create transaction code for sap query report but couldn't go further.
    1) Created User group in SQ03
    2) Created infoset in SQ03 and assigned that to the user group
    3) Created query in SQ01 using the infoset.
    I executed the report in SQ01 and it is working fine.
    Now I try to create a transaction code in SE93 using the steps mentioned in the following link:
    Assign transaction code to SAP Query (created via SQ01)
    But when try to execute the report using the transaction code, it is giving error message 'User group xxxxxx is not yet created'
    Could any one advice me if I miss something? Or please help me to create this transaction code and transport to production?
    Thanks in advance

    HI,
    based on the thread you've already mentioned:
    In SE93, Create a Paramter Transaction
    -> Transaction = Start_report
    -> In default values, give the below details:
    D_SREPOVARI-REPORTTYPE = AQ
    D_SREPOVARI-EXTDREPORT = Name of the Query
    D_SREPOVARI-REPORT = User Group
    So check if the user group is typed correct in SE93 and check also if the user group exits in the system where you are trying to run the transaction.
    best regards, Christian

  • Runtime Error in Scrapping of asset ABAVN

    Dear All,
    Runtime Errors         MESSAGE_TYPE_X.
    We are into ECC 6.00. I got following Error while doing Scrapping of asset using T.code ABAVN.
    *Runtime Errors         MESSAGE_TYPE_X
    Date and Time          18.02.2008 04:42:21
    Short dump has not been completely stored (too big)
    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).*
    Point for sure. If problem solved.
    Regards
    Senthamarai kannan

    Hi Mr. Mann
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          19.02.2008 01:46:41
    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:
         System error (termination point SORT_2)
         Long text of error message:
          Diagnosis
              An internal error has occurred.
          System Response
              You cannot continue with processing.
          Procedure
              Contact SAP to establish whether the error can only be rectified by
              a program correction, or whether it can also be rectified by
              changes to the settings. There may also be an error in the updating
              of the data which must be resolved.
              Specify the following parameters when reporting the error:
              o   Message           : GLT0/000
              o   Program           : SAPLGLT0
              o   Termination point : SORT_2
         Technical information about the message:
         Message class....... "GLT0"
         Number.............. 000
         Variable 1.......... "SORT_2"
         Variable 2.......... "SAPLGLT0"
         Variable 3.......... " "
         Variable 4.......... " "
    Trigger Location of Runtime Error
         Program                                 SAPLGLT0
         Include                                 LGLT0FER
         Row                                     38
         Module type                             (FORM)
         Module Name                             INTERNAL_ERROR
    Source Code Extract
    Line  SourceCde
       8 *       text
       9 ----
      10 FORM internal_error USING errorcode.
      11
      12 * Local fields
      13   DATA:
      14       subseq_flag     TYPE glt0_flag.
      15
      16 * Error?
      17   CHECK sy-subrc <> 0.
      18
      19 * Get subsequent posting flag
      20   PERFORM subsequent_posting USING    space
      21                              CHANGING subseq_flag.
      22
      23   IF errorcode = gc_clrbal.
      24     IF subseq_flag = xon.
      25       PERFORM message_send USING 'A000'
      26                            errorcode
      27                            sy-msgv2
      28                            sy-msgv3
      29                            sy-msgv4.
      30     ELSE.
      31       MESSAGE x000 WITH errorcode sy-msgv2 sy-msgv3 sy-msgv4.
      32     ENDIF.
      33   ELSE.
      34 * Subsequent posting -> message handler, else -> dump
      35     IF subseq_flag = xon.
      36       PERFORM message_send USING 'A000' errorcode sy-repid space space.
      37     ELSE.
    >>>>       MESSAGE x000 WITH errorcode sy-repid.
      39     ENDIF.
      40   ENDIF.
      41
      42 ENDFORM.                    " INTERNAL_ERROR
      43
      44 ----
      45 &----
      46 *&      Form  MESSAGE_STORE
      47 &----
      48 *       text
      49 ----
      50 FORM message_store.
      51
      52   CALL FUNCTION 'MESSAGE_STORE'
      53     EXPORTING
      54       exception_if_not_active = space
      55       arbgb                   = sy-msgid
      56       msgty                   = sy-msgty
      57       txtnr                   = sy-msgno
    Warm regards
    kannan

  • Runtime Error: CALL_FUNCTION_OPEN_ERROR

    Hi all,
             we are facing a short dump while executing an RFC Function Module:
             Please note the trace file for the short dump:
             Error analysis
        An error occurred when executing a Remote Function Call.
        "CPIC-CALL: 'ThSAPOCMINIT' : cmRc=20 thRc=497#Unable to determine host add
         NiHostToAddr failed "
        Status of connection.... "CODE=CM_PRODUCT_SPECIFIC_ERROR -1 -1 SAPCODE=497
         CONV= "
        Internal error code.... "RFC_IO5"
        There is an error in the communication system. To clarify
        and resolve the error, contact your system administrator.
        Last error logged in SAP kernel
        Component............ "NI (network interface)"
        Place................ "SAP-Gateway on host GOLITSAPD17 / sapgw01"
        Version.............. 38
        Error code........... "-2"
        Error text........... "hostname 'golitsapd09.go-d01.local' unknown"
        Description.......... "NiHsLGetNodeAddr: hostname cached as unknown"
        System call.......... " "
        Module............... "nixxhsl.cpp"
        Line................. 223
    After doing the initial analysis of this short dump and also doing the  Connection Test using the transaction code SM59, the following error log is generated:
    Logon                     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: hostname 'golitsapd09.go-d01.local' unknown
    Error Details     LOCATION: SAP-Gateway on host GOLITSAPD17 / sapgw01
    Error Details     DETAIL: NiHsLGetNodeAddr: hostname cached as unknown
    Error Details     COMPONENT: NI (network interface)
    Error Details     COUNTER: 2701
    Error Details     MODULE: nixxhsl.cpp
    Error Details     LINE: 223
    Error Details     RETURN CODE: -2
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Wed Mar 25 03:34:07 2009
    Error Details     VERSION: 38
    Please give your valuable inputs in order to solve this problem

    Check note 710920.
    Also check this.
    [Error: CALL_FUNCTION_OPEN_ERROR|https://forums.sdn.sap.com/click.jspa?searchID=24006645&messageID=6319578]

  • While trying to change a BOM with transaction CS02, a runtime error appears

    While trying to change a BOM with transaction CS02, a runtime error appears.
    In intial screen he entered material ,plant BOM usage and date valid from  after executed then id displayed item list in that he wantu2019s delete one item, he has been deleted selected item after that when he was saving he is getting runtime error
    Developer trace
    ABAP Program SAPLKED1_WRITE_CE4_BPS1                 .
    Source LKED1_WRITE_CE4_BPS1U01                  Line 30.
    Error Code SAPSQL_ARRAY_INSERT_DUPREC.
    Module  $Id: //bas/640_REL/src/krn/runt/absapsql.c#17 $ SAP.
    Function HandleRsqlErrors Line 775.
    RABAX: level LEV_RX_STDERR completed.
    RABAX: level LEV_RX_RFC_ERROR entered.
    RABAX: level LEV_RX_RFC_ERROR completed.
    RABAX: level LEV_RX_RFC_CLOSE entered.
    RABAX: level LEV_RX_RFC_CLOSE completed.
    RABAX: level LEV_RX_IMC_ERROR entered.
    RABAX: level LEV_RX_IMC_ERROR completed.
    RABAX: level LEV_RX_DATASET_CLOSE entered.
    RABAX: level LEV_RX_DATASET_CLOSE completed.
    RABAX: level LEV_RX_RESET_SHMLOCKS entered.
    RABAX: level LEV_RX_RESET_SHMLOCKS completed.
    RABAX: level LEV_RX_ERROR_SAVE entered.
    RABAX: level LEV_RX_ERROR_SAVE completed.
    RABAX: level LEV_RX_ERROR_TPDA entered.
    RABAX: level LEV_RX_ERROR_TPDA completed.
    RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    RABAX: level LEV_RX_END entered.
    RABAX: level LEV_RX_END completed.
    RABAX: end RX_RFC
    In sm21
    Perform rollback
    Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
         Short dump "090618 110101 donalda 11557 " generated
    Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
           Occurred on     18.06.2009 at   11:01:01
    The ABAP/4 Open SQL array insert results in duplicate database records.
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLKED1_WRITE_CE4_BPS1" had to be terminated because
    one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    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.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "RKE_WRITE_CE4__BPS1" "(FUNCTION)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "RKE_WRITE_CE4__BPS1"
    "(FUNCTION)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Use an ABAP/4 Open SQL array insert only if you are sure that none of
    the records passed already exists in the database.
    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:
    "SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
    "SAPLKED1_WRITE_CE4_BPS1" or "LKED1_WRITE_CE4_BPS1U01"
    "RKE_WRITE_CE4__BPS1"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.

    Hi ,
    you are getting beacuse u are trying to do mass update to database.
    Please check that below note are applicable to your system.
    Note 453313 - DBIF_RSQL_ERROR_INTERNAL for mass insert
    Note 869534 - AFS MRP doesn't work properly with all BOM item categories
    Thanks Rishi Abrol

  • T-code MDBT runtime error  GETWA_NOT_ASSIGNED

    Hell everyone.
    I copied a client from another client,then I runned MRP in the new client by T-code MDBT.
    It happened an error.
    Can anybody tell me how I can reslove this issue?
    Thanks & Best regards!
    The detail error as below:
    Runtime Errors         GETWA_NOT_ASSIGNED
    Date and Time          2010.06.19 11:01:46
    Kurztext
         Field symbol has not yet been assigned.
    发生了什么?
         Error in ABAP application program.
         The current ABAP program "FCR05205" had to be terminated because one of the
         statements could not be executed.
         This is probably due to an error in the ABAP program.
    你能做什么?
         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.
    错误分析
        You attempted to access an unassigned field symbol
        (data segment 11).
        This error may occur for any of the following reasons:
        - You address a typed field symbol before it is set using ASSIGN
        - You address a field symbol that points to a line in an internal table
          that has been deleted
        - You address a field symbol that had previously been reset using
          UNASSIGN, or that pointed to a local field that no longer exists
        - You address a global function interface parameter, even
          though the relevant function module is not active,
          that is it is not in the list of active calls. You can get the list
          of active calls from the this short dump.
    如何更正此错误
        You may able to find an interim solution to the problem
        in the SAP note system. If you have access to the note system your
        use the following search criteria:
        "GETWA_NOT_ASSIGNED" C
        "FCR05205" or "FCR05F00"
        "PUT_P_VGWXX"
        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.
    Edited by: lzjsdxg on Jun 19, 2010 6:35 AM

    Are there anybody can help me?
    Thanks!

Maybe you are looking for