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.  ERROR related to type tree

    Posted 08/08/07 12:38 PM

    Originally posted by: SystemAdmin


    Level 2: Offset 3, len 1, comp 1 of 2, #1, DI 00000001:)
    Data at offset 3 ('|') was found to be of TYPE
    X'000A' (Field Separator Message Control HL7).

    (Level 4: Offset 4, len 1, comp 1 of 4, #1, DI 00000002:)
    Data at offset 4 ('^') was found to be of TYPE
    X'000D' (Comp Separator Message Control HL7).

    (Level 4: Offset 5, len 1, comp 2 of 4, #1, DI 00000003:)
    Data at offset 5 ('~') was found to be of TYPE
    X'000E' (Repetition Separator Message Control HL7).

    (Level 4: Offset 6, len 1, comp 3 of 4, #1, DI 00000004:)
    Data at offset 6 ('\') was found to be of TYPE
    X'000F' (EscapeCharacter Separator Message Control HL7).

    (Level 4: Offset 7, len 1, comp 4 of 4, #1, DI 00000005:)
    Data at offset 7 ('&') was found to be of TYPE
    X'0010' (SubComponent Separator Message Control HL7).

    (Level 3: Offset 4, len 4, comp 1 of 18, #1, DI 00000006:)
    Data at offset 4 ('^~\&') was found to be of TYPE
    X'000C' (Encoding Message Control HL7).

    (Level 4: Offset 9, len 4, comp 1 of 4, #1, DI 00000007:)
    Data at offset 9 ('LAB3') was found to be of TYPE
    X'0017' (EntityIdentifier ST Element Field HL7).

    (Level 3: Offset 9, len 4, comp 2 of 18, #1, DI 00000008:)
    Data at offset 9 ('LAB3') was found to be of TYPE
    X'0014' (SendingApplication EI Composite Field HL7).

    (Level 4: Offset 14, len 3, comp 1 of 4, #1, DI 00000009:)
    Data at offset 14 ('MNL') was found to be of TYPE
    X'0017' (EntityIdentifier ST Element Field HL7).

    (Level 3: Offset 14, len 3, comp 3 of 18, #1, DI 0000000A:)
    Data at offset 14 ('MNL') was found to be of TYPE
    X'001D' (SendingFacility EI Composite Field HL7).

    (Level 4: Offset 18, len 3, comp 1 of 4, #1, DI 0000000B:)
    Data at offset 18 ('SAP') was found to be of TYPE
    X'0017' (EntityIdentifier ST Element Field HL7).

    (Level 3: Offset 18, len 3, comp 4 of 18, #1, DI 0000000C:)
    Data at offset 18 ('SAP') was found to be of TYPE
    X'001E' (ReceivingApplication EI Composite Field HL7).

    (Level 4: Offset 22, len 3, comp 1 of 4, #1, DI 0000000D:)
    Data at offset 22 ('MNL') was found to be of TYPE
    X'0017' (EntityIdentifier ST Element Field HL7).

    (Level 3: Offset 22, len 3, comp 5 of 18, #1, DI 0000000E:)
    Data at offset 22 ('MNL') was found to be of TYPE
    X'001F' (ReceivingFacility EI Composite Field HL7).

    (Level 4: Offset 26, len 11, comp 1 of 2, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11...') failed item presentation test for TYPE
    X'0024' (CCYYMMDDTIME DateTime TS Element Field HL7).

    (Level 4: Offset 26, len 11, comp 1 of 2, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11...') fails maximum size requirements
    TYPE X'0025' (CCYYMMDD DateTime TS Element Field HL7).

    (Level 4: Offset 26, len 0, comp 1 of 2, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11||ORU...') failed PARTITIONing for TYPE
    X'0023' (DateTime TS Element Field HL7).

    (Level 4: Offset 26, len 0, comp 1 of 2, #1, DI 0000000F:)
    COMPONENT number 1 of TYPE X'0021' (DateTimeOfMessage TS Composite Field HL7):
    occurrence 1 is optional and has no content.

    (Level 4: Offset 26, len 0, comp 2 of 2, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11||ORU...') does not match DELIMITER '^'
    of TYPE X'0021' (DateTimeOfMessage TS Composite Field HL7).

    (Level 4: Offset 26, len 0, comp 2 of 2, #1, DI 0000000F:)
    COMPONENT number 2 of TYPE X'0021' (DateTimeOfMessage TS Composite Field HL7):
    occurrence 1 is optional and has no content.

    (Level 3: Offset 26, len 0, comp 6 of 18, #1, DI 0000000F:)
    COMPONENT number 6 of TYPE X'000B' (Data_In_MSH Message Control HL7):
    occurrence 1 is optional and has no content.

    (Level 3: Offset 26, len 0, comp 7 of 18, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11||ORU...') does not match DELIMITER '|'
    of TYPE X'000B' (Data_In_MSH Message Control HL7).

    (Level 3: Offset 26, len 0, comp 7 of 18, #1, DI 0000000F:)
    COMPONENT number 7 of TYPE X'000B' (Data_In_MSH Message Control HL7):
    occurrence 1 is optional and has no content.

    (Level 3: Offset 26, len 0, comp 8 of 18, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11||ORU...') does not match DELIMITER '|'
    of TYPE X'000B' (Data_In_MSH Message Control HL7).

    (Level 3: Offset 26, len 0, comp 8 of 18, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11||ORU') was found to be of TYPE
    X'0029' (MessageType CM Composite Field HL7).

    (Level 3: Offset 26, len 0, comp 9 of 18, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11||ORU...') does not match DELIMITER '|'
    of TYPE X'000B' (Data_In_MSH Message Control HL7).

    (Level 3: Offset 26, len 0, comp 9 of 18, #1, DI 0000000F:)
    COMPONENT number 9 of TYPE X'000B' (Data_In_MSH Message Control HL7)
    is required, but does not exist.

    (Level 2: Offset 4, len 0, comp 2 of 2, #1, DI 00000002:)
    COMPONENT number 2 of TYPE X'0006' (MSH Segment HL7)
    is required, but does not exist.

    (Level 1: Offset 0, len 0, comp 1 of 3, #1, DI 00000001:)
    Data at offset 0 ('MSH|^~\&|LAB3|MN...') failed COMPONENT RULE test
    for component number 1, TYPE X'0004' (O01 ORU Message HL7).

    (Level 1: Offset 0, len 0, comp 1 of 3, #1, DI 00000001:)
    COMPONENT number 1 of TYPE X'0004' (O01 ORU Message HL7)
    is required, but does not exist.

    INPUT 1 exists, but its type is in error.

    End of Validation messages for INPUT CARD 1.
    End of Execution messages.

    This is the error i am getting when i am trying to add an input card to the mapsource.I am new to this field please help meeee thanks in advance.Attache dis the message type HL7
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 2.  Re: ERROR related to type tree

    Posted 08/08/07 12:45 PM

    Originally posted by: john.gibby


    (Level 4: Offset 26, len 11, comp 1 of 2, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11...') failed item presentation test for TYPE
    X'0024' (CCYYMMDDTIME DateTime TS Element Field HL7).

    (Level 4: Offset 26, len 11, comp 1 of 2, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11...') fails maximum size requirements
    TYPE X'0025' (CCYYMMDD DateTime TS Element Field HL7).
    Welcome to Datastage TX.
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 3.  Re: ERROR related to type tree

    Posted 08/08/07 03:58 PM

    Originally posted by: SystemAdmin


    Thanks john for inviting me but you havent explained me the error.could you please let me know about it.thanks
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 4.  Re: ERROR related to type tree

    Posted 08/08/07 05:03 PM

    Originally posted by: john.gibby


    (Level 4: Offset 26, len 11, comp 1 of 2, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11...') failed item presentation test for TYPE
    X'0024' (CCYYMMDDTIME DateTime TS Element Field HL7).

    (Level 4: Offset 26, len 11, comp 1 of 2, #1, DI 0000000F:)
    Data at offset 26 ('2.00104E+11...') fails maximum size requirements
    TYPE X'0025' (CCYYMMDD DateTime TS Element Field HL7).

    The trace indicates that you have what appears to be a number that fails to meet the size requirements and presentation requirements of the field.

    2.00104E+11 does not meet the format requirements of a Date or DateTime.

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


  • 5.  Re: ERROR related to type tree

    Posted 08/08/07 06:53 PM
      |   view attached

    Originally posted by: SystemAdmin


    Hi john,Thank you soo much for yr earlier reply.I really appreciate that.I am new to TX and have very less knowledge in this.I am attaching the type tree and input message.this is the next part of the error in bold.
    (Level 2: Offset 3, len 1, comp 1 of 2, #1, DI 00000001:)
    Data at offset 3 ('|') was found to be of TYPE
    X'000A' (Field Separator Message Control HL7).

    (Level 4: Offset 4, len 1, comp 1 of 4, #1, DI 00000002:)
    Data at offset 4 ('^') was found to be of TYPE
    X'000D' (Comp Separator Message Control HL7).

    (Level 4: Offset 5, len 1, comp 2 of 4, #1, DI 00000003:)
    Data at offset 5 ('~') was found to be of TYPE
    X'000E' (Repetition Separator Message Control HL7).

    (Level 4: Offset 6, len 1, comp 3 of 4, #1, DI 00000004:)
    Data at offset 6 ('\') was found to be of TYPE
    X'000F' (EscapeCharacter Separator Message Control HL7).

    (Level 4: Offset 7, len 1, comp 4 of 4, #1, DI 00000005:)
    Data at offset 7 ('&') was found to be of TYPE
    X'0010' (SubComponent Separator Message Control HL7).

    (Level 3: Offset 4, len 4, comp 1 of 18, #1, DI 00000006:)
    Data at offset 4 ('^~\&') was found to be of TYPE
    X'000C' (Encoding Message Control HL7).

    (Level 4: Offset 9, len 4, comp 1 of 4, #1, DI 00000007:)
    Data at offset 9 ('LAB3') was found to be of TYPE
    X'0017' (EntityIdentifier ST Element Field HL7).

    (Level 3: Offset 9, len 4, comp 2 of 18, #1, DI 00000008:)
    Data at offset 9 ('LAB3') was found to be of TYPE
    X'0014' (SendingApplication EI Composite Field HL7).

    (Level 4: Offset 14, len 3, comp 1 of 4, #1, DI 00000009:)
    Data at offset 14 ('MNL') was found to be of TYPE
    X'0017' (EntityIdentifier ST Element Field HL7).

    (Level 3: Offset 14, len 3, comp 3 of 18, #1, DI 0000000A:)
    Data at offset 14 ('MNL') was found to be of TYPE
    X'001D' (SendingFacility EI Composite Field HL7).

    (Level 4: Offset 18, len 3, comp 1 of 4, #1, DI 0000000B:)
    Data at offset 18 ('SAP') was found to be of TYPE
    X'0017' (EntityIdentifier ST Element Field HL7).

    (Level 3: Offset 18, len 3, comp 4 of 18, #1, DI 0000000C:)
    Data at offset 18 ('SAP') was found to be of TYPE
    X'001E' (ReceivingApplication EI Composite Field HL7).

    (Level 4: Offset 22, len 3, comp 1 of 4, #1, DI 0000000D:)
    Data at offset 22 ('MNL') was found to be of TYPE
    X'0017' (EntityIdentifier ST Element Field HL7).

    (Level 3: Offset 22, len 3, comp 5 of 18, #1, DI 0000000E:)
    Data at offset 22 ('MNL') was found to be of TYPE
    X'001F' (ReceivingFacility EI Composite Field HL7).

    (Level 4: Offset 26, len 12, comp 1 of 2, #1, DI 0000000F:)
    Data at offset 26 ('200708011447') was found to be of TYPE
    X'0024' (CCYYMMDDTIME DateTime TS Element Field HL7).

    (Level 4: Offset 26, len 12, comp 1 of 2, #1, DI 00000010:)
    Data at offset 26 ('200708011447') was found to be of TYPE
    X'0023' (DateTime TS Element Field HL7).

    (Level 3: Offset 26, len 12, comp 6 of 18, #1, DI 00000011:)
    Data at offset 26 ('200708011447') was found to be of TYPE
    X'0021' (DateTimeOfMessage TS Composite Field HL7).

    (Level 3: Offset 39, len 0, comp 7 of 18, #1, DI 00000012:)
    COMPONENT number 7 of TYPE X'000B' (Data_In_MSH Message Control HL7):
    occurrence 1 is optional and has no content.

    (Level 4: Offset 40, len 3, comp 1 of 2, #1, DI 00000012:)
    Data at offset 40 ('ORU') was found to be of TYPE
    X'002A' (MessageType ID Element Field HL7).

    (Level 4: Offset 44, len 3, comp 2 of 2, #1, DI 00000013:)
    Data at offset 44 ('R01') was found to be of TYPE
    X'002B' (TriggerEvent ID Element Field HL7).

    (Level 3: Offset 40, len 7, comp 8 of 18, #1, DI 00000014:)
    Data at offset 40 ('ORU^R01') was found to be of TYPE
    X'0029' (MessageType CM Composite Field HL7).

    (Level 3: Offset 48, len 14, comp 9 of 18, #1, DI 00000015:)
    Data at offset 48 ('20010427070901') was found to be of TYPE
    X'002C' (MessageControlID ST Element Field HL7).

    (Level 4: Offset 63, len 1, comp 1 of 2, #1, DI 00000016:)
    Data at offset 63 ('P') was found to be of TYPE
    X'002F' (ProcessingID ID Element Field HL7).

    (Level 3: Offset 63, len 1, comp 10 of 18, #1, DI 00000017:)
    Data at offset 63 ('P') was found to be of TYPE
    X'002E' (ProcessingID PT Composite Field HL7).

    (Level 3: Offset 65, len 3, comp 11 of 18, #1, DI 00000018:)
    Data at offset 65 ('2.3') was found to be of TYPE
    X'0031' (VersionID ID Element Field HL7).

    (Level 3: Offset 69, len 0, comp 12 of 18, #1, DI 00000019:)
    COMPONENT number 12 of TYPE X'000B' (Data_In_MSH Message Control HL7):
    occurrence 1 is optional and has no content.

    (Level 3: Offset 70, len 0, comp 13 of 18, #1, DI 00000019:)
    COMPONENT number 13 of TYPE X'000B' (Data_In_MSH Message Control HL7):
    occurrence 1 is optional and has no content.

    (Level 3: Offset 71, len 0, comp 14 of 18, #1, DI 00000019:)
    COMPONENT number 14 of TYPE X'000B' (Data_In_MSH Message Control HL7):
    occurrence 1 is optional and has no content.

    (Level 3: Offset 72, len 0, comp 15 of 18, #1, DI 00000019:)
    COMPONENT number 15 of TYPE X'000B' (Data_In_MSH Message Control HL7):
    occurrence 1 is optional and has no content.

    (Level 3: Offset 73, len 0, comp 16 of 18, #1, DI 00000019:)
    COMPONENT number 16 of TYPE X'000B' (Data_In_MSH Message Control HL7):
    occurrence 1 is optional and has no content.

    (Level 3: Offset 74, len 0, comp 17 of 18, #1, DI 00000019:)
    COMPONENT number 17 of TYPE X'000B' (Data_In_MSH Message Control HL7):
    occurrence 1 is optional and has no content.

    [b](Level 4: Offset 75, len 0, comp 1 of 6, #1, DI 00000019:)
    Data at offset 75 ('<CR>PID||125436987|...') fails minimum size requirements
    TYPE X'003E' (Identifier ST Element Field HL7).

    (Level 4: Offset 75, len 0, comp 1 of 6, #1, DI 00000019:)
    COMPONENT number 1 of TYPE X'003D' (PrincipalLanguageOfMessage CE Composite Field HL7):
    occurrence 1 is optional and has no content.

    (Level 4: Offset 75, len 0, comp 2 of 6, #1, DI 00000019:)
    Data at offset 75 ('<CR>PID||125436987|...') does not match DELIMITER '^'
    of TYPE X'003D' (PrincipalLanguageOfMessage CE Composite Field HL7).

    (Level 4: Offset 75, len 0, comp 2 of 6, #1, DI 00000019:)
    COMPONENT number 2 of TYPE X'003D' (PrincipalLanguageOfMessage CE Composite Field HL7):
    occurrence 1 is optional and has no content.

    (Level 4: Offset 75, len 0, comp 3 of 6, #1, DI 00000019:)
    Data at offset 75 ('<CR>PID||125436987|...') does not match DELIMITER '^'
    of TYPE X'003D' (PrincipalLanguageOfMessage CE Composite Field HL7).

    (Level 4: Offset 75, len 0, comp 3 of 6, #1, DI 00000019:)
    COMPONENT number 3 of TYPE X'003D' (PrincipalLanguageOfMessage CE Composite Field HL7):
    occurrence 1 is optional and has no content.

    (Level 4: Offset 75, len 0, comp 4 of 6, #1, DI 00000019:)
    Data at offset 75 ('<CR>PID||125436987|...') does not match DELIMITER '^'
    of TYPE X'003D' (PrincipalLanguageOfMessage CE Composite Field HL7).

    (Level 4: Offset 75, len 0, comp 4 of 6, #1, DI 00000019:)
    COMPONENT number 4 of TYPE X'003D' (PrincipalLanguageOfMessage CE Composite Field HL7):
    occurrence 1 is optional and has no content.

    (Level 4: Offset 75, len 0, comp 5 of 6, #1, DI 00000019:)
    Data at offset 75 ('<CR>PID||125436987|...') does not match DELIMITER '^'
    of TYPE X'003D' (PrincipalLanguageOfMessage CE Composite Field HL7).

    (Level 4: Offset 75, len 0, comp 5 of 6, #1, DI 00000019:)
    COMPONENT number 5 of TYPE X'003D' (PrincipalLanguageOfMessage CE Composite Field HL7):
    occurrence 1 is optional and has no content.

    (Level 4: Offset 75, len 0, comp 6 of 6, #1, DI 00000019:)
    Data at offset 75 ('<CR>PID||125436987|...') does not match DELIMITER '^'
    of TYPE X'003D' (PrincipalLanguageOfMessage CE Composite Field HL7).

    (Level 4: Offset 75, len 0, comp 6 of 6, #1, DI 00000019:)
    COMPONENT number 6 of TYPE X'003D' (PrincipalLanguageOfMessage CE Composite Field HL7):
    occurrence 1 is optional and has no content.

    (Level 3: Offset 75, len 0, comp 18 of 18, #1, DI 00000019:)
    COMPONENT number 18 of TYPE X'000B' (Data_In_MSH Message Control HL7):
    occurrence 1 is optional and has no content.

    (Level 2: Offset 4, len 71, comp 2 of 2, #1, DI 00000019:)
    Data at offset 4 ('^~\&|LAB3|MNL|SA') was found to be of TYPE
    X'000B' (Data_In_MSH Message Control HL7).

    (Level 2: Offset 75, len 1, comp 3 of 2, #2, DI 0000001A:)
    TERMINATOR ('SegmentTerminator Separator Message Control HL7') found; has value '<CR>'.

    (Level 2: Offset 75, len 1, comp 3 of 2, #2, DI 0000001A:)
    Data at offset 75 ('<CR>') was found to be of TYPE
    X'0044' (SegmentTerminator Separator Message Control HL7).

    (Level 1: Offset 3, len 72, comp 1 of 2, #1, DI 0000001B:)
    Data at offset 3 ('|^~\&|LAB3|MNL|S') was found to be of TYPE
    X'0006' (MSH Segment HL7).

    (Level 1: Offset 3, len 72, comp 1 of 2, #1, DI 0000001C:)
    Data at offset 3 ('|^~\&|LAB3|MNL|S') was found to be of TYPE
    X'0005' (Segment HL7).

    (Level 1: Offset 3, len 72, comp 1 of 2, #1, DI 0000001C:)
    Data at offset 3 ('|^~\&|LAB3|MNL|S...') failed COMPONENT RULE test
    for component number 1, TYPE X'0004' (O01 ORU Message HL7).

    (Level 1: Offset 0, len 0, comp 1 of 2, #1, DI 00000001:)
    COMPONENT number 1 of TYPE X'0004' (O01 ORU Message HL7)
    is required, but does not exist.

    INPUT 1 exists, but its type is in error.

    End of Validation messages for INPUT CARD 1.
    End of Execution messages.\b

    I deeply appreciate in yr replies.I am still stuck in adding the input card.
    Reply ASAP.once i can figure out this i hope I can role better.

    thanks,
    Raj
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender

    Attachment(s)



  • 6.  Re: ERROR related to type tree

    Posted 08/09/07 04:30 AM

    Originally posted by: janhess


    You need to check your type tree definition against your data. They don't match as your trace file shows.

    (Level 4: Offset 75, len 0, comp 1 of 6, #1, DI 00000019:)
    Data at offset 75 ('<CR>PID||125436987|...') fails minimum size requirements
    TYPE X'003E' (Identifier ST Element Field HL7).
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 7.  Re: ERROR related to type tree

    Posted 08/09/07 04:22 PM
      |   view attached

    Originally posted by: SystemAdmin


    Hi janhess,
    Where can i learn how to match(check the data against the data) the data.Can we find any documentation or website where i can learn from.I am new to this so need to learn.Please let me know.If u can match this one tree for me then i can understand based on what you changed.That will be a g8 help
    thanks,
    Rag
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender

    Attachment(s)