IBM Sterling Transformation Extender

Sterling Transformation Extender

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


#Sterling
#Supplychain
 View Only
  • 1.  Component rule

    Posted 02/24/12 02:42 AM

    Originally posted by: maddysam


    Can any one let me know what it means by $=$ in an component rule ?
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 2.  Re: Component rule

    Posted 02/24/12 01:13 PM

    Originally posted by: TarunB


    Not sure if that rule makes sense but it means that this cell is equal to, well... this cell.

    Normally would be used at group or field level, say for control breaks or as a validation rule.

    Example:

    CustomerPO_Number Field:$ = OurDelivery_Number:$
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender


  • 3.  Re: Component rule

    Posted 02/24/12 01:13 PM

    Originally posted by: TarunB


    Not sure if that rule makes sense but it means that this cell is equal to, well... this cell.

    Normally would be used at group or field level, say for control breaks or as a validation rule.

    Example:

    CustomerPO_Number Field:$ = OurDelivery_Number:$
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 4.  Re: Component rule

    Posted 02/27/12 04:28 PM

    Originally posted by: thorstenhirsch


    By that rule you can "resolve" warnings in a typetree like "Component #2 can not be distinguished from Component #3". Anyway, I also doubt, that it makes any sense.
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender