Hi PI Expert
Could you give me your opinion or advise which one is the best approach to implement for my scenario below :
I already have 1 simple interface to read file and log into abap table and write into different directory.
File --- to -
File scenario. In between i am using graphical mapping with 1 UDF to calling RFC Lookup in PI ABAP stact to do checking and insert into customize table for monitoring purpose.
Sometimes in the high load processing there are a lot of duplicate_message
<SAP:Category>XIProtocol</SAP:Category> <SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code>
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DuplicateMessageException: Message ID 69af7162-346f-435c-042e-8de9d99a40e7(INBOUND) already exists in database: com.sap.sql.DuplicateKeyException:
ORA-00001: unique constraint (SAPSR3DB.SYS_C00275474) violated</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
Base on SAP Note 1016987 - XI message error header: Duplicate detected
Reason and PrerequisitesEither the sending systems sends an XI message with an ID that has already been sent
before, or the Integration Engine resends an XI message because it did not receive
a response that the next system received the message.
It seems like if there is some connection problem or table deadlock the IS keep retry to send the message to Adapter that's why the duplication occurs.
Since the mapping it is not complicated, I have idea to replace the whole mapping to ABAP Mapping for better performance and error handling since both also calling ABAP stack.
Please advise or some suggestion for this.
Thank You In Advance
Edited by: ABAP Team on Jul 27, 2010 11:59 AM
> I have idea to replace the whole mapping to ABAP Mapping for better performance and error handling since both also calling ABAP stack.
SAP recommends Graphical mapping. and it gives better performance than ABAP, so don't go for the ABAP mapping.
In all the mapping the worst performance is ABAP mapping. Maximum no one can use the ABAP mapping.
Try SAP Note - 962578
Also check this thread