cancel
Showing results for 
Search instead for 
Did you mean: 

Value Mapping Replication Issue in SAP PI 7.31

Former Member
0 Kudos

Hi All,

We are using value mapping replication scenario in SAP PI 7.31.

It was working fine all these days without any issues, but suddenly we are getting the below error in Production system.

Error Details:

        <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

       - <!--

    Call Adapter

        -->

        - <SAP:Error SOAP:mustUnderstand="1" xmlns AP="http://sap.com/xi/XI/Message/30" xmlns OAP="http://schemas.xmlsoap.org/soap/envelope/">

         <SAP:Category>XIProtocol</SAP:Category>

        <SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code>

         <SAP 1 />

         <SAP 2 />

         <SAP 3 />

         <SAP 4 />

         <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 005056bb-5e7a-1ee6-a1c9-469708248936(INBOUND) already exists in duplicate check table: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (UNKNOWN.obj#=59671) violated OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]</SAP:AdditionalText>

           <SAP tack />

           <SAP:Retry>N</SAP:Retry>

      </SAP:Error>

We have tested the same scenario in Development system and it is working fine. I have gone through multiple threads and few are suggesting to go for full cache refresh.But before that I would like to check if there is any other solution.

Please share your thoughts if anyone faced the same issue.

Thanks

Soundarya

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member182412
Active Contributor
0 Kudos

Hi Soundarya,

Check this message with id 005056bb-5e7a-1ee6-a1c9-469708248936 already exist in PI system??

Regards,

Praveen.

Former Member
0 Kudos

Hi Praveen,

Thanks for your reply.

Actually we have deleted all the values in Value Mapping table and re triggered all the values from ECC to PI cache.

Still facing the same error for the values triggered from ECC to SAP PI.

Thanks

Soundarya

former_member182412
Active Contributor
0 Kudos

Hi Soundarya,

Check this sap note is applicable to your PI version.

2048004 - Asynchronous XI 3.0 protocol acknowledgements not processed correctly


  • In case the acknowledgment is already received the SOAP adapter generates SOAP fault with the following exception traces instead of XI 3.0 synchronous system acknowledgment with error code "DUPLICATE_DETECTED"

<SAP:Stack>com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id ... already exists in duplicate check table:

com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: [200]: Duplicate key OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]

at com.sap.engine.messaging.impl.core.store.MessageStore.checkForDuplicate(MessageStore.java:490)

at com.sap.engine.messaging.impl.core.store.MessageStore.putMessage(MessageStore.java:394)

Regards,

Praveen.

Former Member
0 Kudos

Hi Praveen,

I have gone through mentioned SAP notes. Thank you !

But when we tried to replicate same issue in Development system it is working fine, the issue is occurring only in Production system. so I feel that it is not SAP note implementation issue as it is working in Development system.

Please find the End to End Scenario Details below for more clarity.

SAP ECC- to - SAP PI--> No ESR objects- Its a Standard Proxy to Proxy Scenario , we are using XI receiver adapter at SAP PI end.

Values are being updated from ECC to SAP PI Cache in runtime using value mapping replication concept.

Thanks

Soundarya

GauravKant
Contributor
0 Kudos

Hi Soundarya,

This will never happens unless you assign IDs by one of your processes and you do it incorrectly.

Check sm59 JCo and also do a channel restart(hope you have done it if not pls give a try).

Also check the below notes.

#1016987 - XI message error header: Duplicate detected

#1363044 - Guid does not generate unique IDs

If this will not help pls try to restart the J2EE.

Regards,

Gaurav

Former Member
0 Kudos

Thanks Gaurav! I will check the possibilities and get back to you.

Thanks

Soundarya

former_member182412
Active Contributor
0 Kudos

Hi Gourav,

These two notes are not applicable to her current version 7.31 these are for 7.31 below systems.

Check before suggesting in the thread that will save their time.

Regards,

Praveen.