on 02-24-2014 2:20 PM
Occasionally in our Test environment we get the following error for our outbound 850's and 860's that use the B2B x12 converter.
Message processing failed. Cause: com.sap.aii.converter.x12.xml2x12.XML2X12Exception: XML-Parser error occured while parsing: Cannot process close tag S_GS: Message ID 829823066T###01###123456789###12###000000452 already exists in database: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SAPSR4DB.I_XI_ID_MAP_ID1) violated OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
Exception caught by adapter framework: XML-Parser error occured while parsing: Cannot process close tag S_GS: Message ID 829823066T###01###123456789###12###000000452 already exists in database: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SAPSR4DB.I_XI_ID_MAP_ID1) violated OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
Transmitting the message to endpoint <local> using connection IDoc_AAE_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.converter.x12.xml2x12.XML2X12Exception: XML-Parser error occured while parsing: Cannot process close tag S_GS: Message ID 829823066T###01###123456789###12###000000452 already exists in database: com.sap.sql.exception.OpenSQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SAPSR4DB.I_XI_ID_MAP_ID1) violated OpenSQLExceptionCategories: [NON_TRANSIENT, INTEGRITY_CONSTRAINT_VIOLATION]
If we resend the message it works. This isn't a consistent error - just happens occasionally. I'd like to save us the trouble of doing resends when we go live in production with these changes.
Can someone explain?
Best,
Diane
There seems to be a note addressing this issue by now http://service.sap.com/sap/support/notes/2010227
Just in case anyone comes here with the same problem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Diane,
Could you please explain the configuration? I guess you have IDoc sender and an outbound channel. What modules do you have on these sender and receiver channels?
Also, please let me know which SP and patch level of PIB2BTOOLKIT software component.
Regards,
Prashantha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry guys - we were in the middle of a big test cycle.
We are 7.31 SPS 9 - PIB2BTOOLKIT - Version 1000.1.00.2.4.2013.1113103900
Our scenario is an 850 outbound
Sender - IDOC using IDoc_AAE adapter with module CallSapAdapter
Receiver - SFTP using SFTP Adaper 1.0 with module 1- localejbs/X12ConverterModule 2-localejbs/ModuleProcessorExitBean
It is the module X12ConverterModule that is tossing the error. If we do a resend it fixes itself. Issue for me is - why? I don't want to add to our on-call responsibility of the random failures this interfaces has. It's not consistent enough for us to be able to create the error as needed. But it happens 25-30% of the time.
Diane
Hi Diane - Please check if the below note is applicable to you
1721113 - Duplicate IDoc numbers and transaction ids generated
1742705 - JCA Sample Adapter Fails with INTEGRITY_CONSTRAINT_VIOLATION
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.