SAPSQL_ARRAY_INSERT_DUPREC CX_SY_OPEN_SQL_DB

Question

I am getting the below short dump continuously in my solution manager 704.
User name                 Runtime error                                      Exception                             
SMD_BI_RFC     041  C SAPSQL_ARRAY_INSERT_DUPREC CX_SY_OPEN_SQL_DB 4CFECFB1BE000230E10080000A3E5C0F
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
Date and Time          08.12.2010 06:39:55
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 "GP4G94DANQ8OS4VDXW3RMPR1QTP" 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 "WRITE_ICFACT" "(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"
  "GP4G94DANQ8OS4VDXW3RMPR1QTP" or "GP4G94DANQ8OS4VDXW3RMPR1QTP"
  "WRITE_ICFACT"
  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
  "WRITE_ICFACT" "(FORM)", or its possible occurrence must be declared in the
  RAISING clause of the procedure.
  To prevent the exception, note the following:
Information on where terminated
    Termination occurred in the ABAP program "GP4G94DANQ8OS4VDXW3RMPR1QTP" - in
     "WRITE_ICFACT".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 5062
    of the (Include) program "GP4G94DANQ8OS4VDXW3RMPR1QTP".
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "WRITE_ICFACT" "(FORM)", but it was neither handled locally nor
     declared
    in the RAISING clause of its signature.
    The procedure is in program "GP4G94DANQ8OS4VDXW3RMPR1QTP "; its source code
     begins in line
    5028 of the (Include program "GP4G94DANQ8OS4VDXW3RMPR1QTP ".

Answer 1

some more information :
User and Transaction
    Client.............. 041
    User................ "SMD_BI_RFC"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "4CFECFB1BE000230E10080000A3E5C0F"
    Program............. "GP4G94DANQ8OS4VDXW3RMPR1QTP"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "NSP"
    Database Release.... 701
    Kernel Release...... 701
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. 061
    User................ "SMD_RFC"
    Transaction......... " "
    Call Program........."SAPLE2E_FUNC"
    Function Module..... "SMD_DATA_LOADER100"
    Call Destination.... "BI_CLNT041"
    Source Server....... "nbcsaprtv015_NSP_09"
    Source IP Address... "10.62.92.15"
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0
    Note: For releases < 4.0, information on the RFC caller are often
    only partially available.