cancel
Showing results for 
Search instead for 
Did you mean: 

7.1 SP14, SP15 SAP closed mapping loophole

former_member775562
Discoverer
0 Kudos

Dear All,

The XI graphical mapping is using the queue mechanism. In XI7.0 SP<14 there was a bug that some functions apply single values to multiple target nodes. This was corrected, so only the constant function is now returning one value to many target elements. For all other standard functions (e.g. fixValue, mapWithDefault,u2026) additionally the copyValue function has to be used.

Please consider that with SP15 the mapping behaviour changes (According to SAP it is a fix to the behaviour described above). To avoid changes in the development, please consider that you have to handle all values (except constant function) as queue.

Hermann

Accepted Solutions (0)

Answers (1)

Answers (1)

prateek
Active Contributor
0 Kudos

U may edit ur Subject from 7.1 to 7.0. I think u r talking about the PI 7.0 version only.

Suggestion: U may add this content to Wiki and get some points

Regards,

Prateek

Former Member
0 Kudos

Can you please give some more details on what exactly the change is between SP13 and SP 14 in terms of Message Mapping?

XIer

Edited by: XIer on Sep 16, 2008 12:04 AM

former_member775562
Discoverer
0 Kudos

With the new service pack SP15 the behavior of the mapping function FixValue and mapWithDefault changed

Example FixValue:

Input u201CAu201D -> FixValue(Output u201CBu201D) -> TargetField (Occurrence 1..n)

ACTCD->FixValues->TRANSAC...

Example mapWithDefault:

Input u201CAu201D -> mapWithDefault(Output u201CBu201D) ->TargetField (Occurrence 1..n)

ACTCD->MapWithDefault->TRANSAC...

Behavior prior SP15:

The output (single value) of the FixValue / mapWithDefault function (which worked as the constant function) was applied to all fields TRANSACTION.

Behavior with SP15:

FixValue / mapWithDefault is building up a queue, which means that the (single) value only can be applied for the first target field. For the second occurrence of TRANSACTION the mapping is throwing the following error (if the target field is mandatory):

"Cannot produce Target element,....."

If the target field would be optional (Occurrence 0..n), it would only map the first value, but not build up the further values as expected.