671 ABAP/4 processor: SAP SQL_ARRAY_INSERT_DUPREC

Question

i'm getting this message everytime i try to post something(f-02, vendor/ miro/migo) any type of entry.
can someone please explain this to me? the message is too technicalfor me to comprehend. so i hope the solution isnt that technical..
points will be gratitiously rewarded. thanks

Answer 1

The program ran fine without problems but it didnt fix anything.  This is the message you wanted. Do you also want the source code extract?
error analysis
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
Date and Time          06.02.2012 20:48:12
     Short text
          The ABAP/4 Open SQL array insert results in duplicate database records.
     What happened?
          Error in the ABAP Application Program
          The current ABAP program "SAPLGLIU" 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_OPEN_SQL_DB', was not caught
           in
          procedure "INS_FAGLFLEXA" "(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:
          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
          Use an ABAP/4 Open SQL array insert only if you are sure that none of
          the records passed already exists in the database.
          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_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
          "SAPLGLIU" or "LGLIUF1A"
          "INS_FAGLFLEXA"
          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
          "INS_FAGLFLEXA" "(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... "gcecc62"
          Network address...... "192.168.10.1"
          Operating system..... "Windows NT"
          Release.............. "5.2"
          Hardware type........ "Intel 80686 (Mo"
          Character length.... 16 Bits
          Pointer length....... 32 Bits
          Work process number.. 6
          Shortdump setting.... "full"
          Database server... "GCECC62"
          Database type..... "ORACLE"
          Database name..... "ECC"
          Database user ID.. "SAPSR3"
          Char.set.... "C"
          SAP kernel....... 700
          created (date)... "Aug 29 2006 00:18:21"
          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. 75
          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"
          Memory consumption
          Roll.... 8176
          EM...... 3135672
          Heap.... 0
          Page.... 0
          MM Used. 2660632
          MM Free. 473408
     User and Transaction
          Client.............. 800
          User................ "SAPUSER"
          Language key........ "E"
          Transaction......... "FB01 "
          Program............. "SAPLGLIU"
          Screen.............. "RSM13000 3000"
          Screen line......... 2
     Information on where terminated
          Termination occurred in the ABAP program "SAPLGLIU" - in "INS_FAGLFLEXA".
          The main program was "RSM13000 ".
          In the source code you have the termination point in line 1199
          of the (Include) program "LGLIUF1A".
          The program "SAPLGLIU" was started in the update system.
          The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
          procedure "INS_FAGLFLEXA" "(FORM)", but it was neither handled locally nor
           declared
          in the RAISING clause of its signature.
          The procedure is in program "SAPLGLIU "; its source code begins in line
          1184 of the (Include program "LGLIUF1A ".