Originally posted by: SystemAdmin
When you're building a map, you first do nothing but define your input card. Then turn on the trace for input. Until you can read your data without generating an .MTR trace file, there is no reason to continue.
What I provided was the export of the type tree for the stated field, DIVISA_TASA. The decimal is formatted under Item Subclass=Number, Presentation=Decimal, Size=Min:0,Max:13, Separators=Yes:Format=####
http://.##,Pad=Yes,Value=<SP>,Padded to=Fixed Size, Length=13, Sized as=Bytes, Justify=Right The forum app messed up the my previous post. The format I used was 4 pound signs, left bracket, decimal point, 2 pound signs, right bracket. There are other formats available via a drop down list and I believe you can define your own.
When I run your map using your map rule, "=TEXTTONUMBER(FILLLEFT(LEAVENUM(NUMBERTOTEXT(DIVISA_TASA Field:entradafuncional)),"0",200))", I get:
<tns:divisa>
<tns:codigoDivisa>ARS</tns:codigoDivisa>
<tns:codigoPais>ARN</tns:codigoPais>
<tns:nombre>NUEVO PESO ARGENTINO</tns:nombre>
<tns:tasa>3837064628</tns:tasa>
<tns:fechaCambio>2012-10-29</tns:fechaCambio>
</tns:divisa>
The following also works. TEXTTONUMBER strips off the zeroes you add by the FILLLEFT.
=TEXTTONUMBER(LEAVENUM(NUMBERTOTEXT(DIVISA_TASA Field:entradafuncional)))
/* =TEXTTONUMBER(FILLLEFT(LEAVENUM(NUMBERTOTEXT(DIVISA_TASA Field:entradafuncional)),"0",200))
#IBM-Websphere-Transformation-Extender#IBMSterlingTransformationExtender#DataExchange