Skip to Content

Value Mappings with multiple source values

Hello,

The built-in value mapping tool is adequate for mapping a single source field to a single target field. There are, however, many situations where it would be necessary to map a combination of source fields to one or more target fields. To give an example, we transfer some PS time registration data from SAP to another system. We need to use both the Network Number (NW_AUFNR) and Operation Number (VORNR) to derive the corresponding value in the target system.

One simple way to do this is to concatenate the two source values together (possibly with a separator character) and use the result as if it were a single source value. Several objections to this can be raised, the most important of which is that it cannot be adequately represented - calling the scheme e.g. "NW_AUFNR|VORNR" is like putting a square peg in a round hole.

Does anyone have experience with such multi-source-value mappings? How have you solved this?

Best regards,

Thorsten

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Jul 20, 2004 at 01:50 PM

    Hi!!!

    You can write your own java mapping to archive multi-source-value mapping. In your code you can take mapping data from tables in the database or xml files.

    As far as I know XI 2.0 reloads jar file with java mapping during transformation of every message, so you have to also take under consideration the performance issue.

    Fortunately XI 3.0 doesn't behave like this.

    Regards,

    Andrzej Filusz

    Add comment
    10|10000 characters needed characters exceeded

    • Thanks Andrzej.

      I realise this is an option. Another possibility is to use the Business Process Engine to load the data from somewhere into an XML message and then use XPath to do the actual mappings.

      The real problem, I suppose, is that neither of these solutions is very elegant. And you loose the transparency that the built-in tool provides. I was just hoping someone has come up with a good solution that we had somehow overlooked.

      Best regards,

      Thorsten