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.  Segmenting the incoming file.

    Posted 08/06/10 04:28 AM

    Originally posted by: SailajaChaganti


    Hi,

    I have a requirement wherein I have to segment a part of the incoming file and pass it to the output without any transformation.

    To be accurate, input file structure is

    File
    FileName
    FileType
    SubmissionTs
    InsuredDetails
    InsuredPersonalDtls
    CvgDetails
    EmploymentDtls

    The InsuredDetails may come in 2 different formats - fixed length or delimited.
    Whatever format it may be, I need to pass the Insured Details block as such to the output to store the raw data in DB.

    I have tried creating a group (RecordData) in the output TT with only one element, for name sake, and tried passing the Insured Details group from input to RecordData in output.

    But it throws me type mismatch error when compiling the map.

    Could anyone please help me out in this?
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange


  • 2.  Re: Segmenting the incoming file.

    Posted 08/06/10 05:20 AM

    Originally posted by: SystemAdmin


    >But it throws me type mismatch error when compiling the map.
    unless the input and output tree are the same, you cannot map a group to another group - you need to use a functional map.
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 3.  Re: Segmenting the incoming file.

    Posted 08/10/10 02:45 PM

    Originally posted by: jvanboga


    Not sure I understand this issue but if you have delimited and non-delimited (fixed length) records you need to use two record groups an either unordered or choice groups.
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender


  • 4.  Re: Segmenting the incoming file.

    Posted 08/11/10 11:19 AM

    Originally posted by: TarunB


    Can't say I've seen a "mismatch error" during map compilation... only during system startup when the msd hasn't been updated to reflect the number of cards changing in the map.

    Anyway, if you're looking to store the raw data, and are not parsing/validating the data, then there's no reason why you can't just read the InsuredDetails group as a TEXT(blob) and pass it to a TEXT(blob) output for loading into an open ended clob field in your database.

    Your message is somewhat ambiguous though so feel free to clarify if you need more help.
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 5.  Re: Segmenting the incoming file.

    Posted 11/17/10 11:16 PM

    Originally posted by: Hugo.Thornton


    TarunB wrote:
    Can't say I've seen a "mismatch error" during map compilation... only during system startup when the msd hasn't been updated to reflect the number of cards changing in the map.

    Anyway, if you're looking to store the raw data, and are not parsing/validating the data, then there's no reason why you can't just read the InsuredDetails group as a TEXT(blob) and pass it to a TEXT(blob) output for loading into an open ended clob field in your database.

    Your message is somewhat ambiguous though so feel free to clarify if you need more help.

    I understand this part, Thanks for your explanation! It's helpful to me.
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 6.  Re: Segmenting the incoming file.

    Posted 11/18/10 11:07 AM

    Originally posted by: TarunB


    You're welcome Hugo, and I'm happy to see that you've used the Search function to find an answer to your question.
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender