Skip to Content
0
Former Member
Feb 25, 2009 at 03:56 PM

3 SWCV Strategy Design Recommendation

62 Views

All,

At my company we've been trying to establish our modelling standard around the 3 SWCV technique and we've currently got a request that's presenting a problem to us. Was wondering if anyone here could help. Here's the scenario.

I've got 1 ERP system which sends an IDoc to XI which will then have to take the data and route it to one of two legacy systems using the file adapter. Now the data types, message types and message interface for both legacy files are identical. So following the 3 SWCV technique I've really got 4 SWCVs lets say we're calling them SWCV_ERP_1, SWCV_XI_1, SWCV_Legacy_1, SWCV_Legacy_2.

We have our send idoc action and our imported IDoc definition defined in SWCV_ERP_1. We had defined seperate receive file actions (1 for each of the legacy SWCVs) and again seperate dt, mt and mi definitions even though they're identical in structure (1 for each of the legacy SWCVs).

In the SWCV_XI_1 we were going to build our integration scenario (using each of the 3 actions defined in our other SWCVs), our message mapping and our interface mapping. Originally we defined it with 1 source interface (the IDoc) with 2 target interfaces (1 message interface from each of my legacy SWCVs). This resulted in us having in our interface mapping 1 source message with 2 mapping programs (one each to map the source to each of the seperately defined message types from the legacy SWCVs).

Our goal was to then in the Integration Directory (we're on XI 3.0) to receive 2 seperate message that we could then use a content filter for each of the messages. For legacy system 1 if a field in the message was a certain value we either sent it or not. Since we received an identical message we would have another filter for legacy system 2 that if that field had a different value then we forwarded it to system 2 (or not).

We haven't got to the ID yet as we're getting a failure when we test the IM we get the message:

"Cannot produce target element /ns0:MT_BLAHBLAHBLAH/YADAYADAYADA. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd"

Any guidance would be appreciated.