Skip to Content
avatar image
Former Member

Namespace issue in a B2B scenario

Hi all,

I have an iDoc to iDoc B2B scenario (R/3<->XI<->XI<->R/3),

My partner has defined an iDoc extention and sent me the xsd.

Now I have a problem in defining the interface because I don't have the same iDoc definition(different R/3 version) so I cannot import it into the IR, and I cannot define the message type and message interface as an external definition because the MI is in the iDoc reserved namespace.

How can I solve this conflict ?

Thanks,

Elad.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Mar 22, 2006 at 02:28 PM

    Hi Elad,

    you can change temporary your SWKV to load IDocs from other R/3.

    If you use any other mapping than message mapping just ignore the situation and define only a dummy datatype/messagetype/interface. It will not be validated. But i'm not shure if IDoc adapter will work with that. Assumedly the will work only for the outbound idoc.

    Regards,

    Udo

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Udo Martens

      Hi Udo,

      The last one was accidently posted on a different username 😊

      Anyway...

      The only systems I have connection to, are the remote XI and my local R/3.

      Partner's R/3 is either 4.7 or ECC 5.0 (in case they finished upgrading), my local R/3 is 4.6 .

      Remote system sends iDoc CREMAS04, local R/3 has only CREMAS03.

      It doesn't matter if I use a dummy interface or my own loaded iDoc definition, either way I cannot configure a receiver determination.

      Any other ideas ? or maybe a way to apply your solution ?

      Thanks,

      Elad.

  • Mar 23, 2006 at 04:47 AM

    You can definetly import the XSD as an external definition and use it.

    though BELOW BLOG doesnot deal with the same problem.

    /people/michal.krawczyk2/blog/2005/05/25/xi-how-to-add-authorizations-to-repository-objects

    It helps you in understanding how to import the idoc XSD as an external definition and use it as just any idoc that is imported into IR.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      I am sorry, but I can't understand the connectoion, maybe you could point me a bit more...

      Elad.

  • Mar 23, 2006 at 06:56 AM

    you can definetly import the XSD as external definition and use it.

    Go through the blog for sample.

    Add comment
    10|10000 characters needed characters exceeded