Namespace issue in a B2B scenario

[Former Member]

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.

[STALANKI]

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

Go through the blog for sample.

[Former Member]

Hi,

I'm sorry, my mistake for not pointing out my problem more clearly.

I have indeed imported the xsd as an external definition, but when configuring the interface scenario, I have a problem of defining the receiver and interface determination.

The outbound interface is a user defined message interface based on the external definition message type, while the actual message received in the pipeline is defined by the standard iDoc interface, so the IE cannot find a receiver.

Thanks,

Elad.

[Former Member]

Hi,

I found out the problem, all I had to do is to import the WSDL file indstead of the XSD.

Elad.

[STALANKI]

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.

[Former Member]

Hi,

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

Elad.

[udo_martens]

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

[Former Member]

Dear Udo,

I guess you didn't understand me, the differences are between R/3 versions, and SWCV definition will not help beacause I can only import iDoc from my local R/3 (I have no connection to the remote R/3).

I didn't understand the part about the mapping issue.

Thanks,

Elad.

[udo_martens]

Hi Elad (or Ofir?),

my idea was to change temporary connection data for import from SAP system of SWKV. The question is, if you dont have connection to that system, how do you want to connect with XI and how do you want to test?

2. idea was: instead of imported idoc you just create a dummy interface in repository. The interfaces itselfes (and so the imported idocs) will not be validated by integration engine. Only if you use message mapping you really NEED a correct XSD schema.

So something like R/3 idoc -> own interface -> any mapping except message mapping -> loaded idoc interface -> other R/3

Regards,

Udo

[Former Member]

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.