IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
 View Only
  • 1.  X12 type tree for N2 segment different than guide?

    Posted Wed May 28, 2014 08:15 AM

    Originally posted by: edi1999


    In the X12 guide, the N2 & N3 segments (4060 259 trans) have both an 01 and 02 element.  But in the WTX type tree, there is only an 01 element that can occur twice.  How do you map both instances if the second one is present since you can't index an input card field?

     


    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 2.  Re: X12 type tree for N2 segment different than guide?

    Posted Thu May 29, 2014 04:26 PM

    Originally posted by: Arun Ramamurthy


    I think the 2 elements would be separated by a element delimiter in the input

    example:

    ABC*123

     

    And I think you may be able to map them using the Indexes like  -  Name[1] and Name[2]


    #IBM-Websphere-Transformation-Extender
    #DataExchange
    #IBMSterlingTransformationExtender


  • 3.  Re: X12 type tree for N2 segment different than guide?

    Posted Thu May 29, 2014 06:58 PM

    Originally posted by: RichMcFate


    Arun has it right.  You can map either of the two elements by indexing them.

    It would look something like this:

    Name Element[1]:N2 Segment:LoopN1:LoopIT1

    Name Element[2]:N2 Segment:LoopN1:LoopIT1

    or

    Name Element[1]:.:CardName


    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 4.  Re: X12 type tree for N2 segment different than guide?

    Posted Fri May 30, 2014 09:31 AM

    Originally posted by: edi1999


    Ah yes...thank you.  That worked.  I tried parens but didn't think to try brackets.


    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender