Originally posted by: maddysam

What will be the difference in passing the arg to a fmap as ,
i)fmap(XYZLoop IN input) &
ii)fmap(XYZLoop:Transaction#837InboundPartnerSet V5010X220:#837F5010X220Inbound Partner Funct'lGroup ANSI:PartnerX12InboundInterchange:input)

In (i)case Iam getting n objects(say 350)
(ii)case Iam getting more than n objects(say 5400)

Could not able to trace out the exact reason.Can anyone share your experience.

Thanks,
Maddy
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

this:

fmap(XYZLoop IN input)

is saying "look for all instances of XYZLoop regardless of where they are found" - it's useful for counting differnt type of records, e.g. in a EDIFACT UNT segment

this:

fmap(XYZLoop:Transaction#837InboundPartnerSet V5010X220:#837F5010X220Inbound Partner Funct
'lGroup ANSI:PartnerX12InboundInterchange:input)

Is describing a specific instance of XYZLoop - this is the normal way of calling the functional map (although I would switch ellipses on to simplify the path).

I'm surprised that (ii) creates more output than (i) - I would have expected it to be the other way round.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: maddysam

That is what even surprising me.
Anyways, my sincere thanks to you for the clarification/information provided.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: denzer

I would caution against the use of ellipses since they can't be expanded back out. It may temporarily simplify the code but will make your maintenance over time much more difficult. The inability to route back through the path to get to the field in question is not worth it.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender