Mapping Query - More Fields on Inbound than Outbound

[Former Member]

Hi,

Is it possible to have the following:

1. Outbound Message:

<OBrecord>

  <f1>aaa</f1>

  <f2>bbb</f2>

  <f4>ddd</f4>

</OBrecord>

(i.e. f3 is not present as it is not a mandatory field)

2. All 4 fields mapped and mandatory on the Inbound side. Giving:

3. Inbound Message

<IBrecord>

  <f1>aaa</f1>

  <f2>bbb</f2>

  <f3></f3>

  <f4>ddd</f4>

</IBrecord>

I didn't think this was possible as to have f3 on the inbound side as a mandatory field would mean that f3 would need to exist on the outbound message or the mapping would fail. However, is there some feature of the mapping which allows a field to be present on the inbound side even when there wasn't an element on the outbound side to map into it i.e. an inbound  default value if no outbound element present ?

Cheers,

PaulC.

[Former Member · Accepted solution]

Hi Paul,

You can use mapwithdefault function to achive ur requirement.

Sourcefield-->mapwithdefault-->Targetfield.

Thanks,

Satish.

[Former Member]

Hello Paul,

I think you can just drop the field f3 in your mapping.

If this field is not available in your outbound structure,

you can just skip it.

The fact that it is a mandatory field in your source structure

does not impact your target structure.

(assuming that you use different data types in source an target)

That's what message mapping is good for...;-)

Regards,

Jürgen

[Former Member]

Juregn,

In my example f3 is mandatory on the inbound side but isn't always present on the outbound. Satish's solution worked perfectly.

Thanks for taking the time to reply.

Cheers,

PaulC.