Skip to Content
author's profile photo Former Member
Former Member

File to Idoc scenario

Hi experts,

I have a problem with a file to idoc scenario.

The mapping is done by an XSLT mapping.

We received from external partner a file , XI picks this file up (ftp) and post it via idoc to R/3.

Now the problem is that the last time there are duplicate idocs with the same po number. So to explain me : our client send an order with his order number in our R/3 system we find multiple idocs with the same order number? How can we avoid that. Where should we integrate a duplicate check and how.

How can we monitor this

Kind regards

Gwen

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Posted on Nov 21, 2007 at 10:00 AM

    1. Collect the idoc on time frame and check the duplicated in mapping

    2. in r3 before posting of idoc (in user exit) check if the PO already exists for the same data. If yes u can stop it from posting the PO

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 21, 2007 at 10:01 AM

    Hi Gwen,

    Do you have DELETE option in communication channel configuration?

    if not then do the change.

    This might be due to broken communication channel.

    for your reference

    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34

    *PS:Reward points if useful*

    Regards,

    Sumit Gupta

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 21, 2007 at 10:04 AM

    Hi Gwen,

    you can check the order number only in R/3. So i would use the IDoc acknowledgements to inform the sender about that double order numbers. For that task you would need assumedly a BP.

    If your target is to have only successful processed IDocs than you must implement a look up from the mapping and check for order numbers. Of course you can delete double entries in mapping, but anyway existing order number could be used.

    Regards, Udo

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 21, 2007 at 10:23 AM

    Gwen

    1. PO number can be generated either by internal range or by external range. External range is the number what we give in ME21 or Me21n for creating PO. Internal numbers are created authomatically by the system. If the PO numbers are geting duplicated check the previous idocs. Note that duplicate PO cannot be created in R3 but the entries can be ovewritten

    2. check the payloads and see if the file is having unique PO numbers. Maybe the same file is reconsidered during the transfer

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 21, 2007 at 10:42 AM

    Dear Gwen.

    one more advice to suppress the duplicate idoc

    collect all outbound IDocs in the sending system and to dispatch IDocs using ABAP RSEOUT00. This will assure that only one dialog process in the receiving system is consumed at a time.

    Regards,

    Sumit Gupta

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.