Duplicate key errors table T7KR5CT occured during SHADOW_IMPORT_INC

Hi,
We are getting the following error during EHP4 upgrade :- 
Checks after phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC were negative!
Last error code set: Unresolved requests in buffer SRD
Check logfiles 'SHDALLIMP.ELG' and '/EHPI/EHPI/abap/log/SAPehpi.ECO'
A trouble ticket and an archive with all relevant log files have been
generated.
Trouble ticket: "/EHPI/EHPI/abap/log/SAPehpi_troubleticket.log"
Log archive: "/EHPI/EHPI/abap/log/SAPehpi_troubleticket_logs.sar"
01)  *  Repeat phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC to continue at the point it stopped
02)  -  Initialize phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC to restart it from the beginning
03)  -  Exit this program
Choose action: Repeat phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC to continue at the point it stopped
Log file shows the following information :-
  LIST OF ERRORS AND RETURN CODES  *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPK-70105INPIBASIS.SRD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 import portion 000000 - 000022 not imported because the child processes died for unknown reason
2EETW000 import portion 000023 - 000026 not imported because the child processes died for unknown reason
2EETW000 import portion 000027 - 000185 not imported because the child processes died for unknown reason
2EETW000 import portion 000186 - 000191 not imported because the child processes died for unknown reason
2EETW000 import portion 000192 - 000218 not imported because the child processes died for unknown reason
2EETW000 import portion 000219 - 999999 not imported because the child processes died for unknown reason
1 ETP111 exit code           : "4"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPKE60416.SRD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 child process 745784 terminated -> setting rc=12 for this import portion
2EETW000 sap_dext called with msgnr "4":
2EETW000 -
db call info -
2EETW000 function:   db_docu
2EETW000 fcode:      CI_WRITE_LINE
2EETW000 len (char): 68
2EETW000 key:        NAHRPAYDEST601                                                EE0012
2EETW000 ok fetches: 0
2EETW000 retcode:    4
1 ETP111 exit code           : "0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPKE60425.SRD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 12 duplicate key errors during insert into table T7KR5CT occured
2EETW000 12 duplicate key errors during insert into table T7KR5CT occured
1 ETP111 exit code           : "8"
/EHPI/EHPI/abap/exenew/R3trans finished (0000).
/EHPI/EHPI/abap/exenew/R3trans finished (0000).
/EHPI/EHPI/abap/exenew/R3trans finished (0004).
2EETW000 12 duplicate key errors during insert into table T7KR5CT occured
/EHPI/EHPI/abap/exenew/R3trans finished (0000).
/EHPI/EHPI/abap/exenew/R3trans finished (0004).
2EETW000 12 duplicate key errors during insert into table T7KR5CT occured
/EHPI/EHPI/abap/exenew/R3trans finished (0008).
ERROR: stopping on error 8 during SHADOW IMPORT
Warning: Parameter INTERRUPT is no longer used.
Warning: unknown parameter MAX_SEMAPHORE_WAIT in parameter file (line 9).
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: unknown parameter MAX_SEMAPHORE_WAIT in parameter file (line 9).
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
stopping on error 8 during SHADOW IMPORT
tp returncode summary:
TOOLS: Highest return code of single steps was: 8
SWARNS: Highest tp internal severe warning was: 0151
tp finished with return code: 151
meaning:
  Some warning regarding buffer entries
Process with ID 807096 terminated with status 151
We tried to replace the R3trans with a latest version of R3trans and repeat the SHADOW_IMPORT_INC phase but still the same error is reported.
Can you please help us on this ?
Thanks in adavnce.
Regards,
SS

Hello,
I got the same problem in RPH EHP5 Upgrade Phase SHADOW_IMPORT_INC with table TWUF_CHECK~. After reading some notes (1074030, ...) I decided to restart the phase without any modifications and it worked and I'm  happy!
Jörg
./R3trans -v
This is ./R3trans version 6.22 (release 720 - 02.05.11 - 15:56:00).
ALOG702:
SAPK-603DTINEAGLTRAD SID.ALL K 0012 20110901110222 EAGLTRADUSER sidadm       hostname 2011090109242911d001
SAPK-603DTINEAGLTRAD SID.ALL K 0004 20110901114000 EAGLTRADUSER sidadm       hostname 20110901113956128006
SHDALLIMP.ELG:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SHADOW IMPORT ERRORS and RETURN CODE in SAPK-603DTINEAGLTRAD.DE8
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW000 1 duplicate key error during insert into table TWUF_EVENT~ occured
2EETW000 sap_dext called with msgnr "16":
2EETW000 -
db call info -
2EETW000 function:   db_setget
2EETW000 fcode:      RT_GET (0)
2EETW000 tabname:    TWUF_CHECK~
2EETW000 len (char): 65
2EETW000 key:        CL_WB2_ANLYTLTRDGVWINVCIDQR   INPUT                         00002
2EETW000 ok fetches: 0
2EETW000 last entry:
2EETW000 retcode:    16
1 ETP111 exit code           : "12"

Similar Messages

  • 1 duplicate key error during insert into table

    Dear Guru's
    While upgrading the SAP_HR patch, I am facing this issue
    Current level is SAPKE60455
    Trying to apply patch - SAPKE60456
    This is seen in the import log
    Start import R3TRVDATV_512W_O ...
    client 000:   1
    client 001:   1
    client 070:   1
    client 080:   1
    client 100:   1
    client 320:   1
    1 duplicate key error during insert into table T512T occured
    End import R3TRVDATV_512W_O (with warnings)
    Please help, thank in advance
    R3trans is at version 6.19
    Regards,
    Omkar

    Hello,
    Issue was resolved after upgrading the R3trans
    Regards,
    Omkar

  • Error code 82 occurs during installation...how to overcome?

    Error code 82 occurs during installation...how to overcome?

    Hi Sameer,
    You can follow the article: Error downloading, installing, or updating Creative Cloud applications which might help you to get your issue fixed.
    If you still face any issues I would recommend you to paste a screenshot of the error message you are getting.
    Thanks,
    Ratandeep Arora

  • Classic duplicate key error when processing dimensions

     I have a dimension attribute that has a list of values below
    atlanta
    atlanta
    Atlanta
    Atlanta
    Atlanta
    ATLANTA
    it has caused the duplicate key errors. I've checked the colloation property of AS server and it's set to Latin1_general with case-sensitive UNCHECKED.... I wonder why I still get this type of errors? 
    thanks
    --Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

    You would need to use a case-sensitive collation for these not to be considered duplicates and even then, on closer inspection, I still see duplicates in your data.  There are only three distinct case-sensitive values out of the six examples you've
    provided: atlanta, Atlanta, and ATLANTA.
    Jason

  • The selected signed file could not be authenticated. The file might have been tampered with or an error might have occured during download. Please verify the MD5 hash value against the Cisco Systems web site

    I am trying to load any 9.0.3 firmware on my UCM 5.0.4.2000-1 server. Every newer firmware I load throws the following error. I have verified the MD5 is correct and also downloaded the file several times with the same result. I can load the same firmware file on another UCM server and it loads fine. Any ideas?
    Thanks in advance!
    Error Message:
    The selected signed file could not be authenticated. The file might have been  tampered with or an error might have occured during download. Please verify the  MD5 hash value against the Cisco Systems web site:  9b:b6:31:09:18:15:e7:c0:97:9f:e6:fe:9a:19:94:99
    Firmware File: cmterm-7970_7971-sccp.9-0-3.cop.sgn
    UCM version: 5.0.4.2000-1

    Thanks for your reply. We have a lab environment where I maintain  UCM 5.0, 5.1, 6.0, 6.1, 7.0, 7.1 and 8.0 servers each running the latest released firmware for our QA testing team. I have downloaded and installed the latest device packages but find that if I try to install any firmware newer then 8.3.1 on either 5.0.4 or 6.0 i start getting MD5 hash authentication errors. It looks like 9.0.3 firmware should work on UCM 5.0 and 6.0 so I am lost as to why I can't seem to update any firmware for any model phone if it is newer then version 8.3.1 on either 5.0 or 6.0. while 5.1 and 6.1 work without issues. Maybe it is just a bug. I mostly wanted to see if anyone else has experienced this or if it is just me.

  • My iphone is a 3g and I was updating it's sofware from 4.1 to 4.2 when an error called 1604 occured during the restoration. what should i do?

    my iphone is a 3g and I was updating it's sofware from 4.1 to 4.2 when an error called 1604 occured during the restoration. what should i do?

    Shifaau wrote:
    now an error code by 1015 comes up.
    Again...Search the forums or Google for the error message appearing and follow the troubleshooting steps provided.

  • Duplicate message and Duplicate key error in Moni and RWB

    Hi,
    I am getting very frequent issues of Duplicate messages in production system moni and RWB.
    Moni error: (IDOC to JMS) Errors are coming in call adapter step:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not insert message 005056aa-730e-1ed4-a6c9-a01ee2b86cb3(INBOUND) into duplicate check table. Reason: com.sap.sql.exception.OpenSQLException: Connection reset by peer: socket write error OpenSQLExceptionCategories: [RECOVERABLE]
    RWB error: (File toIdoc) Errors are coming in sender channel.
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id a6d559cf-b00c-11e4-b786-00000daf354a(OUTBOUND) already exists in duplicate check table: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: Violation of PRIMARY KEY constraint 'PK__BC_MSG_D__99C1915D3DE9247A'. Cannot insert duplicate key in object 'SAPPGXDB.BC_MSG_DUP_CHECK'. The duplicate key value is (a6d559cf-b00c-11e4-b786-00000daf354a, OUTBOUND). OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION
    Moni errors are manually reprocessed and RWB are automatic.
    Can you please let me know if there is any solution available for these issues?
    Thanks
    Navneet.

    I'm getting the same issue at my current client:-
    Putting message into send queue failed, due to: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id e1d4a31b-f0cc-11e4-c7fb-0000029706f7(OUTBOUND) already exists in duplicate check table: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00188646) violated OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
    I've tried restarting the SOAP channel but this has not resolved the problem.
    Just read on another thread that this may be a misleading error message (see last post on the link). It may be an idea to increase the trace level temporarily and look for any other issues that may be the cause.
    So far I've not seen any post that describes the error on the SOAP channel - only seeing it for JDBC & File. However it seems to be a common problem across a number of sender channels.

  • Duplicate keys error

    Hello All,
    I am trying to create a B2B export to migrate to 11g. I am getting the following error - how to fix it?
    Tried the following - but no effect: java oracle.tip.adapter.b2b.data.B2BSchemaUpdate
    Thanks.
    RosettaNet ...
    oracle.xml.parser.v2.XMLParseException: Identity constraint validation error: 'duplicate keys'
    at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
    at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:312)
    at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291)
    at oracle.tip.repos.export.Export11g.validate(Export11g.java:2998)
    at oracle.tip.repos.export.Export11g.write(Export11g.java:2891)
    at oracle.tip.repos.export.Export11g.createDoc(Export11g.java:670)
    at oracle.tip.repos.export.Export11g.export(Export11g.java:211)
    at oracle.tip.repos.export.Export.main(Export.java:1024)

    Hi,
    If you want to export 10g metadata to 11g, please refer -
    http://blogs.oracle.com/oracleb2bgurus/2009/10/export_the_metadata_from_10g_t.html
    Make sure to validate the metadata in 10g before exporting. In your case there is some key duplication problem but from the provided log it is not very clear that where exactly could be the problem. I will sugesst you to validate the entire repository of 10g and delete everything which is not required. After that take the export as mentioned on the above link.
    Make sure to be on the latest patch (MLR -13). Let us know if still problem persists.
    Regards,
    Anuj

  • Strange duplicate key error on doing remove/create

    Hi,
    I am trying to delete a bunch of entities and then re-use the primary keys to
    insert a bunch of new ones, all within the same transaction. I am using WL6.1
    (EJB2.0), sp1 on NT.
    I use the home.ejbRemove (pk) method to remove the beans, and then the appropriate
    create method to create the new instances. 98% of the time this seems to work;
    I see the delete statements issued to the database and the assocaited create statements.
    Every now and then I get the following error:
    javax.ejb.DuplicateKeyException: Bean with primary key: 'AssociateActivity Primary
    Keycom.Timesheets.domainBean.AssociateActivityPK@962f6d6f
    AssocaiteId : 130.00
    AssociateActivityId : 204841.00' already exists.
    Yet I still see the delete statement for the PK in question issued to the db,
    and everything looks the same as it does when the TX succeeds - but in this case
    its as if somehow the entity isnt getting deleted from the WL cache in a timely
    fashion. I see that the 'delay_updates_until_end_of_tx' could be set to false,
    but isnt this a database-related parameter? I have set this up and am re-testing,
    but it is hard to produce this error, so I am not comfortable testing a while
    and saying its gone. Does anyone know why I might be seeing this error, and shed
    some insight as to whether this parameter will fix it for me?
    Thanks in advance !
    Caroline.

    Hi Rob,
    thanks for your reply. The beans are CMP. I agree, updating makes more sense -
    this is (now) legacy code written by another engineer, and they didnt want to
    deal with updates. It doesnt sound as thought this problem should be happening,
    though, and that is concerning. I will keep an eye on if - if I see this intermittent
    problem again, maybe I wll bite the bullet and change the algorithms to do just
    that. Of course, we are in test mode and getting software out is our primary goal
    right now. If you have any other suggestions, I would appreciate them.
    Thanks,
    Caroline.
    Rob Woollen <[email protected]> wrote:
    WLS doesn't currently delay deletes so it should have removed the entry
    from the cache
    before you called create.
    Are these BMP or CMP beans?
    Our of curiousity, why not just update the beans instead of deleting
    and re-creating?
    -- Rob
    Caroline Day wrote:
    Hi,
    I am trying to delete a bunch of entities and then re-use the primarykeys to
    insert a bunch of new ones, all within the same transaction. I am usingWL6.1
    (EJB2.0), sp1 on NT.
    I use the home.ejbRemove (pk) method to remove the beans, and thenthe appropriate
    create method to create the new instances. 98% of the time this seemsto work;
    I see the delete statements issued to the database and the assocaitedcreate statements.
    Every now and then I get the following error:
    javax.ejb.DuplicateKeyException: Bean with primary key: 'AssociateActivityPrimary
    Keycom.Timesheets.domainBean.AssociateActivityPK@962f6d6f
    AssocaiteId : 130.00
    AssociateActivityId : 204841.00' already exists.
    Yet I still see the delete statement for the PK in question issuedto the db,
    and everything looks the same as it does when the TX succeeds - butin this case
    its as if somehow the entity isnt getting deleted from the WL cachein a timely
    fashion. I see that the 'delay_updates_until_end_of_tx' could be setto false,
    but isnt this a database-related parameter? I have set this up andam re-testing,
    but it is hard to produce this error, so I am not comfortable testinga while
    and saying its gone. Does anyone know why I might be seeing this error,and shed
    some insight as to whether this parameter will fix it for me?
    Thanks in advance !
    Caroline.

  • Inbound IDOC processing, error duplicate key

    We want to retrieve certain order-idocs in our system, before they are processed, to change AND insert segment data.
    Flow we use in our current program
    - DOC_STATUS_WRITE_TO_DATABASE
    to change the status of the idoc (ok) (status 69)
    - EDI_DOCUMENT_OPEN_FOR_EDIT (ok)
    - EDI_CHANGE_DATA_SEGMENTS (ok)
    - EDI_DOCUMENT_CLOSE_EDIT => not ok
    This program gives SAPSQL error
    Via debugging, we see that a new idoc number is
    called (save as backup idoc ?), but we want the
    current IDOC to be processed.
    The system wants to insert in EDID4 => dump :
    "Use an ABAP/4 Open SQL array insert only if you
    are sure that none of the records passed already
    exists in the database."
    ( I prefer to use these standard functions, in stead of just deleting and inserting into "EDID4" )
    regards,
    answers will be rewarded.
    code extract
    INCLUDE ZBE01458_TOP.
    INITIALIZATION.
    V_EDIT_STATUS = '69'.
    V_PROCESSED_STATUS = '32'.
    start-of-selection.
    clear t_edidc. refresh t_edidc.
    SELECT * FROM EDIDC into table t_edidc
    WHERE DOCNUM in S_docnum
    and mestyp in S_mestyp
    and idoctp in S_idoctp
    and credat in S_credat
    and rcvpor in S_rcvpor
    and rcvprt in S_rcvprt
    and rcvprn in S_rcvprn
    and sndpor in S_sndpor
    and sndprt in S_sndprt
    and sndprn in S_sndprn
    and status in S_status.
    loop at t_edidc.
    move t_edidc-docnum to v_docnum.
    refresh v_status.
    V_STATUS-docnum = V_DOCNUM.
    V_STATUS-status = V_EDIT_STATUS.
    clear EDIDS.
    select single * from EDIDS where docnum = v_docnum.
    if sy-subrc = 0.
    MOVE EDIDS-STACOD to V_STATUS-STACOD.
    endif .
    APPEND V_STATUS.
    PERFORM CHANGE_IDOC_STATUS tables V_STATUS USING V_DOCNUM.
    changing part for DEDIDD "idoc data
    PERFORM OPEN_IDOC_FOR_CHANGE.
    PERFORM CHANGE_IDOC.
    PERFORM CLOSE_IDOC_FOR_CHANGE.
    refresh v_status.
    V_STATUS-docnum = V_DOCNUM.
    V_STATUS-status = V_PROCESSED_STATUS.
    APPEND V_STATUS.
    PERFORM CHANGE_IDOC_STATUS tables V_STATUS
    USING V_DOCNUM.
    endloop.
    *& Form OPEN_IDOC_FOR_CHANGE
    text
    --> p1 text
    <-- p2 text
    FORM OPEN_IDOC_FOR_CHANGE.
    CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
    EXPORTING
    DOCUMENT_NUMBER = V_DOCNUM
    ALREADY_OPEN = 'N'
    IMPORTING
    IDOC_CONTROL =
    TABLES
    IDOC_DATA = DEDIDD
    EXCEPTIONS
    DOCUMENT_FOREIGN_LOCK = 1
    DOCUMENT_NOT_EXIST = 2
    DOCUMENT_NOT_OPEN = 3
    STATUS_IS_UNABLE_FOR_CHANGING = 4
    OTHERS = 5
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDFORM. " OPEN_IDOC_FOR_CHANGE
    *& Form CHANGE_IDOC
    text
    --> p1 text
    <-- p2 text
    FORM CHANGE_IDOC.
    CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
    TABLES
    IDOC_CHANGED_DATA_RANGE = DEDIDD
    EXCEPTIONS
    IDOC_NOT_OPEN = 1
    DATA_RECORD_NOT_EXIST = 2
    OTHERS = 3.
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDFORM. " CHANGE_IDOC
    *& Form CLOSE_IDOC_FOR_CHANGE
    text
    --> p1 text
    <-- p2 text
    FORM CLOSE_IDOC_FOR_CHANGE.
    CLEAR t_EDI_DS40.
    t_edi_ds40-docnum = v_docnum.
    t_edi_ds40-status = '51'.
    t_edi_ds40-repid = sy-repid.
    t_edi_ds40-tabnam = 'EDI_DS'.
    t_edi_ds40-mandt = sy-mandt.
    t_edi_ds40-stamqu = 'SAP'.
    t_edi_ds40-stamid = 'B1'.
    t_edi_ds40-stamno = '999'.
    t_edi_ds40-stapa1 = 'Changes made to idoc ...'.
    t_edi_ds40-stapa2 = t_new_kunnr.
    t_edi_ds40-logdat = sy-datum.
    t_edi_ds40-logtim = sy-uzeit.
    APPEND t_edi_ds40.
    CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
    EXPORTING
    DOCUMENT_NUMBER = V_DOCNUM
    DO_COMMIT = 'X'
    DO_UPDATE = 'X'
    WRITE_ALL_STATUS = 'X'
    TABLES
    STATUS_RECORDS = t_EDI_DS40
    EXCEPTIONS
    IDOC_NOT_OPEN = 1
    DB_ERROR = 2
    OTHERS = 3
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDFORM. " CLOSE_IDOC_FOR_CHANGE
    *& Form CHANGE_IDOC_STATUS
    text
    --> p1 text
    <-- p2 text
    FORM CHANGE_IDOC_STATUS tables P_IDOC_STATUS structure V_IDOC_STATUS
    USING P_DOCNUM.
    CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
    EXPORTING
    IDOC_NUMBER = p_docnum
    IDOC_OPENED_FLAG = ' '
    NO_DEQUEUE_FLAG = 'X'
    IMPORTING
    IDOC_CONTROL =
    TABLES
    IDOC_STATUS = P_IDOC_STATUS
    EXCEPTIONS
    IDOC_FOREIGN_LOCK = 1
    IDOC_NOT_FOUND = 2
    IDOC_STATUS_RECORDS_EMPTY = 3
    IDOC_STATUS_INVALID = 4
    DB_ERROR = 5
    OTHERS = 6
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    else.
    commit work.
    ENDIF.
    ENDFORM. " CHANGE_IDOC_STATUS

    Urmila,
    I tried this sequence : code extract follows...
    I got the duplicate key errors again.
    what about delete first and then insert again in EDID4 table ?
    source code extract:
    INCLUDE ZBE01458_TOP.
    INITIALIZATION.
      V_EDIT_STATUS = '69'.
      V_PROCESSED_STATUS = '32'.
      V_SAPCODE = 'SAPE0184'.
    start-of-selection.
      clear t_edidc. refresh t_edidc.
      SELECT  * FROM  EDIDC into table t_edidc
             WHERE  DOCNUM  in S_docnum
               and  mestyp  in S_mestyp
               and  idoctp  in S_idoctp
               and  credat  in S_credat
               and  rcvpor  in S_rcvpor
               and  rcvprt  in S_rcvprt
               and  rcvprn  in S_rcvprn
               and  sndpor  in S_sndpor
               and  sndprt  in S_sndprt
               and  sndprn  in S_sndprn
               and  status  in S_status.
      loop at t_edidc.
        move t_edidc-docnum to v_docnum.
        move-corresponding T_EDIDC to WA_EDIDC.
        V_STA-docnum      = v_docnum.
        V_STA-status      = '51'.
        V_STA-repid       = sy-repid.
        V_STA-tabnam      = 'EDI_DS'.
        V_STA-mandt       = sy-mandt.
        V_STA-stamqu      = 'SAP'.
        V_STA-stamid      = 'B1'.
        V_STA-stamno      = '999'.
        V_STA-stapa1      = 'Changes made to idoc ...'.
    t_edi_ds40-stapa2      = t_new_kunnr.
        V_STA-logdat      = sy-datum.
        V_STA-logtim      = sy-uzeit.
        V_STA-STACOD       =  V_SAPCODE.
        PERFORM OPEN_FOR_PROCESS.
        PERFORM SET_IDOC_STATUS USING V_DOCNUM V_STA.
        PERFORM CLOSE_IDOC_FOR_PROCESS.
        PERFORM OPEN_IDOC_FOR_CHANGE.
        PERFORM PROCESS_IDOC_STRUCTURE.
        PERFORM CHANGE_IDOC.
        PERFORM CLOSE_IDOC_FOR_CHANGE.
       refresh v_status.
       V_STATUS-docnum = V_DOCNUM.
       V_STATUS-status = V_EDIT_STATUS.
       V_STATUS-STACOD = V_SAPCODE.
       clear EDIDS.
       select single * from EDIDS where docnum = v_docnum.
       if sy-subrc = 0.
        MOVE EDIDS-STACOD to V_STATUS-STACOD.
       endif .
       APPEND V_STATUS.
       PERFORM CHANGE_IDOC_STATUS tables V_STATUS USING  V_DOCNUM.
      endloop.
    *&      Form  OPEN_IDOC_FOR_CHANGE
          text
    -->  p1        text
    <--  p2        text
    FORM OPEN_IDOC_FOR_CHANGE.
      CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
       EXPORTING
         DOCUMENT_NUMBER                     = V_DOCNUM
      ALREADY_OPEN                        = 'N'
    IMPORTING
       IDOC_CONTROL                        = WA_EDIDC
       TABLES
         IDOC_DATA                           = DEDIDD
      EXCEPTIONS
        DOCUMENT_FOREIGN_LOCK               = 1
        DOCUMENT_NOT_EXIST                  = 2
        DOCUMENT_NOT_OPEN                   = 3
        STATUS_IS_UNABLE_FOR_CHANGING       = 4
        OTHERS                              = 5
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " OPEN_IDOC_FOR_CHANGE
    *&      Form  CHANGE_IDOC
          text
    -->  p1        text
    <--  p2        text
    FORM CHANGE_IDOC.
      CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
           TABLES
                IDOC_CHANGED_DATA_RANGE = DEDIDD
           EXCEPTIONS
                IDOC_NOT_OPEN           = 1
                DATA_RECORD_NOT_EXIST   = 2
                OTHERS                  = 3.
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " CHANGE_IDOC
    *&      Form  CLOSE_IDOC_FOR_CHANGE
          text
    -->  p1        text
    <--  p2        text
    FORM CLOSE_IDOC_FOR_CHANGE.
      CLEAR t_EDI_DS40.
      t_edi_ds40-docnum      = v_docnum.
      t_edi_ds40-status      = '69'.
      t_edi_ds40-repid       = sy-repid.
      t_edi_ds40-tabnam      = 'EDI_DS'.
      t_edi_ds40-mandt       = sy-mandt.
      t_edi_ds40-stamqu      = 'SAP'.
      t_edi_ds40-stamid      = 'B1'.
      t_edi_ds40-stamno      = '999'.
      t_edi_ds40-stapa1      = 'Changes made to idoc ...'.
    t_edi_ds40-stapa2      = t_new_kunnr.
      t_edi_ds40-logdat      = sy-datum.
      t_edi_ds40-logtim      = sy-uzeit.
      APPEND t_edi_ds40.
      CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
           EXPORTING
                DOCUMENT_NUMBER  = V_DOCNUM
                DO_COMMIT        = 'X'
                DO_UPDATE        = 'X'
                WRITE_ALL_STATUS = 'X'
           TABLES
                STATUS_RECORDS   = t_EDI_DS40
           EXCEPTIONS
                IDOC_NOT_OPEN    = 1
                DB_ERROR         = 2
                OTHERS           = 3.
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " CLOSE_IDOC_FOR_CHANGE
    *&      Form  CHANGE_IDOC_STATUS
          text
    -->  p1        text
    <--  p2        text
    FORM CHANGE_IDOC_STATUS tables P_IDOC_STATUS structure V_IDOC_STATUS
    USING P_DOCNUM.
      CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
    EXPORTING
      IDOC_NUMBER                     = p_docnum
            IDOC_OPENED_FLAG                = ' '
            NO_DEQUEUE_FLAG                 = 'X'
          IMPORTING
            IDOC_CONTROL                    =
    TABLES
      IDOC_STATUS                     = P_IDOC_STATUS
          EXCEPTIONS
            IDOC_FOREIGN_LOCK               = 1
            IDOC_NOT_FOUND                  = 2
            IDOC_STATUS_RECORDS_EMPTY       = 3
            IDOC_STATUS_INVALID             = 4
            DB_ERROR                        = 5
            OTHERS                          = 6
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      else.
        commit work.
      ENDIF.
    ENDFORM.                    " CHANGE_IDOC_STATUS
    *&      Form  OPEN_FOR_PROCESS
          text
    -->  p1        text
    <--  p2        text
    FORM OPEN_FOR_PROCESS.
      CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_PROCESS'
        EXPORTING
      DB_READ_OPTION                 = DB_READ
          DOCUMENT_NUMBER                = V_DOCNUM
      ENQUEUE_OPTION                 = SYNCHRONOUS
    IMPORTING
       IDOC_CONTROL                   = WA_EDIDC
    EXCEPTIONS
      DOCUMENT_FOREIGN_LOCK          = 1
      DOCUMENT_NOT_EXIST             = 2
      DOCUMENT_NUMBER_INVALID        = 3
      DOCUMENT_IS_ALREADY_OPEN       = 4
      OTHERS                         = 5
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " OPEN_FOR_PROCESS
    *&      Form  SET_IDOC_STATUS
          text
    -->  p1        text
    <--  p2        text
    FORM SET_IDOC_STATUS USING P_DOCNUM P_STA.
      CALL FUNCTION 'EDI_DOCUMENT_STATUS_SET'
        EXPORTING
          DOCUMENT_NUMBER               = P_DOCNUM
          IDOC_STATUS                   = P_STA
    IMPORTING
       IDOC_CONTROL                  = WA_EDIDC
    EXCEPTIONS
      DOCUMENT_NUMBER_INVALID       = 1
      OTHER_FIELDS_INVALID          = 2
      STATUS_INVALID                = 3
      OTHERS                        = 4
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " SET_IDOC_STATUS
    *&      Form  CLOSE_IDOC_FOR_PROCESS
          text
    -->  p1        text
    <--  p2        text
    FORM CLOSE_IDOC_FOR_PROCESS.
      CALL FUNCTION 'EDI_DOCUMENT_CLOSE_PROCESS'
        EXPORTING
          DOCUMENT_NUMBER           = V_DOCNUM
      BACKGROUND                = NO_BACKGROUND
      NO_DEQUEUE                = ' '
    IMPORTING
       IDOC_CONTROL              = WA_EDIDC
    EXCEPTIONS
      DOCUMENT_NOT_OPEN         = 1
      FAILURE_IN_DB_WRITE       = 2
      PARAMETER_ERROR           = 3
      STATUS_SET_MISSING        = 4
      OTHERS                    = 5
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " CLOSE_IDOC_FOR_PROCESS

  • System error occur during lock managment?

    Hi all !
    When I open the adminstrator  workbench I am gettting the error " System lock occured during lock managment.
    I can open other sessions such as RSPC, RRMX etc.
    Can anyone help in this regard?
    Regards
    Durai

    Hi,
    I can suggest how to access administratoe workbench without using T.code:RSA1.
    Go to T.code RSD1 then in Menu >Environment>Object Browser via AWB.
    Try this for time being to access RSA1 and inform to BASIS guy he will solve the problem.
    Assign points if helpful
    Thanks & Regards,
    Bala

  • Db adaptor for insert- SQLException: [SQL0803] Duplicate key value specified

    While invoking db adaptor for insert on table 1 selecting values form another table, i am gtting error ; before3 insert i am updating table 2nd using db adaptor
    QUERY insert into CRPDTA.F5504579 (SELECT * FROM CRPDTA.F5504571 WHERE PAHDC=#v_updatedRecord_HDC)
    Error :
    Non Recoverable System Fault :
    <bpelFault><faultType>0</faultType><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert_Ledger_F5504579' failed due to: Pure SQL Exception. Pure SQL Execute of insert into CRPDTA.F5504579 (SELECT * FROM CRPDTA.F5504571 WHERE PAHDC=?) failed. Caused by java.sql.SQLException: [SQL0803] Duplicate key value specified.. The Pure SQL option is for border use cases only and provides simple yet minimal functionality. Possibly try the "Perform an operation on a table" option instead. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "--803" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>[SQL0803] Duplicate key value specified.</detail></part><part name="code"><code>-803</code></part></bindingFault></bpelFault>
    Please suggest....

    Easter1976 wrote:
    Hi please can you help me. I think I am having problems with tranactions. I am deleting from a table and then inserting in the same table with the same key that I have just deleted. Simple then - don't do that. It suggests a flaw in the design. Either use a new key or do an update.
    Note that you would get a duplicate key error if the table is set up such that it doesn't
    actually delete but doesn't something such as creating a log entry with a delete flag set.

  • PT 8.51 Upgrade - How to find duplicate keys for Portal Registry Structure?

    I am upgrading peopletools for two applications (CRM 9.00 and FDM 9.00) from the 8.48.10 to 8.51.11 versions.
    For CRM, Task 4-15-9 Completing the Peopletools Conversion ran app engine PTUPGCONVERT ran smoothly.
    For FDM, I have the following error messages:
    The Navigation Pagelet does not exist. Portal = EMPLOYEE. Object = PT_SC_PGT_MAIN_MENU. Collection = PT_PTPP_PORTAL_ROOT (219,2083)
    Message Set Number: 219
    Message Number: 2083
    Message Reason: The Navigation Pagelet does not exist. Portal = EMPLOYEE. Object = PT_SC_PGT_MAIN_MENU. Collection = PT_PTPP_PORTAL_ROOT (219,2083)
    Duplicate key. Portal: EMPLOYEE, Obj Name: PT_SC_PGT_MAIN_MENU, Nodename: LOCAL_NODE, URL: s/WEBLIB_PTPP_SC.HOMEPAGE.FieldFormula.IScript_SCP (133,4)
    PT_SC_PGT_MAIN_MENU already exists. (96,3)
    Copy of the Main Menu Pagelet From PS_SITETEMPLATE to Portal: EMPLOYEE failed. (219,2111)
    Message Set Number: 219
    Message Number: 2111
    Message Reason: Copy of the Main Menu Pagelet From PS_SITETEMPLATE to Portal: EMPLOYEE failed. (219,2111)
    I checked table PSPRSMDEFN which does not have an entry for PT_SC_PGT_MAIN_MENU, under the Employee Portal. I tried to migrate the missing Portal Registry object using App Designer but again receive the "duplicate key" error.
    So it seems that I have to find the duplicate key and resolve it before I can migrate the missing object.
    Anyone know a quick way to figure out what the duplicate keys are?
    Thanks

    I tried several things to find the duplicates with no success.
    A couple of workarounds were attempted that resulted in the same "duplicate key" error, including:
    a) Re-copying file project PPLTLS84CUR
    b) Copy object 'PT_SC_PGT_MAIN_MENU" from Demo
    After opening an SR, the successful workaround was to use Data Mover to export from Demo the "EMPLOYEE" portal entries for "PT_SC_PGT_MAIN_MENU" from tables PSPRSMDEFN, PSPRSMSYSATTR and PSPRSMSYSATTRVL. The import to the target upgrade environment was successful. A re-run of PTUPGCONVERT finished successfully.
    The upgrade is progressing but where the duplicate keys are is still a mystery.
    Cheers

  • SQL exception occurred during PL/SQL upload  (Web ADI)

    Hi,
    I am having issue loading data using Web ADI, I am getting "SQL exception occurred during PL/SQL upload" error, I tried to restart Apache, also looked into the BNE.log file for the exact error but I am still not sure about this exception, can anyone please help?
    bne:text="SQL exception occurred during PL/SQL upload."
    bne:cause="Database insert error"
    RDBMS: 11.2.0.3.0
    Oracle Applications: 12.0.6
    Thanks,
    Bharat

    I am having issue loading data using Web ADI, I am getting "SQL exception occurred during PL/SQL upload" error, I tried to restart Apache, also looked into the BNE.log file for the exact error but I am still not sure about this exception, can anyone please help?Please rename the log file, reproduce the issue and check the log file then.
    bne:text="SQL exception occurred during PL/SQL upload."
    bne:cause="Database insert error"Please see these docs.
    R12 Uploading Intercompany Transactions Shows SQL Exception Occurred During PL/SQL Upload [ID 1234063.1]
    Batch Element Entry (BEE) Spreadsheet Interface > 10 Rows Fails with Error: 'SQL exception occured during PL/SQL Upload.' [ID 388012.1]
    How Do You Setup An AGIS Transaction That Has Several Transaction Lines For The Same Transaction [ID 946499.1]
    FCH: Error: "The upload process has completed with errors. Please Close to return to the document and fix the errors. - No rows uploaded - <999> rows were invalid" During WebADI Data Upload [ID 553025.1]
    R12: Legal Entity Name must be < 31 characters. [ID 472505.1]
    Oracle Payroll 'Batch Element Entry ( BEE )' Frequently Asked Questions ( FAQ ) [ID 1353021.1]
    Thanks,
    Hussein

  • Runtime exception occurred during application mapping in SAP PI

    Hi Team,
    Please help me regarding this issue is very urgent:
    Runtime Error in configuration part:
    Here i test the XML message in Receiver Determintion:
    Below i am getting error:
    Runtime exception occurred during application mapping com/sap/xi/tf/_MaterialStockUpdate_Multi_AllPlant~; com.sap.aii.utilxi.misc.api.BaseRuntimeException:The processing instruction target matching "[xX][mM][lL]" is not allowed
    SXMB_MONI:
    I am getting below error:
    Runtime exception occurred during application mapping

    Hi,
    Actually my problem is what i am getting,I am trying to test the data in runtime workbench and configuration part copied from inbound payload XML structure .
    I already sent the screenshots of above errors,
    Configuartion:
    Runtime workbench:
    This the error i am getting below in "Runtime Workbench"
    Error While Sending Message: Additional error text from response: com.sap.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=MHEPL_Sandbox_100;TS=;AN=MaterialStockUpdate_Multi_AllPlants_N;ANS=http://www.manipalhospitals.com/his/mm; in the current context [Unknown].

Maybe you are looking for

  • Why can't i download itunes on my windows 8 computer?

    Every time I attempt to download iTunes onto my computer, it tells me an error has occurred before iTunes could be configured. Then it tells me that that my system has not been modified and to finish the installation, I need to re run the installer..

  • Photoshop CS6 Crashing multiple times

    My config: Windows 7 Professional 64Bit Intel Core i7 -3820 CPU @3.6Ghz Ram 16GB Photoshop CS6 13.0.1.34 Photoshop crashing 5-7 times per day. This is the error: Faulting application name: Photoshop.exe, version: 13.0.1.34, time stamp: 0x5269b25c Fau

  • Access to WD 500 GB HD connected to Time Capsule on Windows PC

    I have a 500 GB WD My Book hard drive connected to 500 GB Time Capsule via USB. I am able to view both hard drives on my MacBook, but I can't view the attached My Book on my Windows PC. Can anyone help? Is it possible to view the My Book on my Window

  • Standard Reports Functionality

    Hi Experts, Reference: SAP B1 8.81 PL 04 I wanted to bring here to notice that during the time of implementation there are a lot of UDF's that will be created on documents and some vital information will be captured in them. It so happens that when t

  • Popup_to_inform in Web Dynpro for ABAP

    Hi everybody, exists a method like the funtion "popup_to_inform" in Web Dynpro or did I really have to create a view / window and call it like a normal popup? Thanks a lot. Dirk