PM46412: NOT GETTING 999 REJECTS WHEN HL04 HAS INCORRECT VALUE FOR 278 5010X217 TRANSACTION

APAR status

• Closed as program error.

Error description

• We are not getting rejects in 999 when HL04 has an incorrect
  value for a 278  5010X217 transaction
  
  There are 4 scenarios where a 999 with reject is not reported
  when HL04 has incorrect values as below:
  
  1.) 278 - 13 transaction where HL04 in Loop 2000E is a value of
  ' 0 ', but there was a subsequent Loop 2000F in the transaction,
  which means that a 999 reject should have been generated by WTX.
  (Correct value would be ' 1 ')
  
  2.) 278 - 13 transaction where the Loop 2000E HL segment is the
  last HL segment in the transaction but the HL04 element has a
  value of  ' 1 ' indicating that there is Additional Subordinate
  HL Data Segment in This Hierarchical Structure.  Therefore a 999
  reject should have been generated by WTX.  (Correct value would
  be ' 0 ')
  
  3.)  278 - 11 transaction where all loops (2000A - 2000F) are
  populated and if any of the HL04 elements above the 2000F loop
  are populated with a value of ' 0 ' a 999 reject should have
  been generated by WTX. (Correct value would be ' 1 '.)
  Further, in this case the Subscriber Loop (2000C) has the HL04
  element populated as ' 0 '.  This value is not even a valid
  value for this HL segment / HL04 element.  The only valid value,
  according to the TR3, is ' 1 '.
  
  4.) 278 - 11 transaction where the Loop 2000E HL segment is the
  last HL segment in the transaction but the HL04 element has a
  value of  ' 1 ' indicating that there is Additional Subordinate
  HL Data Segment in This Hierarchical Structure.  Therefore a 999
  reject should have been generated by WTX.  (Correct value would
  be ' 0 '.)
  

Local fix

• WTXCQ - WTX00038488
  AR / AR
  Circumvention: None
  

Problem summary

• Users affected:
  Websphere Transformation Extender Pack for HIPAA
  
  Problem Description:
  Not getting 999 rejects when HL04 has incorrect value for 278
  5010X217 transaction
  
  Platforms affected:
  ALL
  

Problem conclusion

• The parent/child relationship rules for the 5010X217 278
  transactions have been added to the Pack for HIPAA
  
  Delivered in:
  HCIP 4.3.2.1 and future HCIP
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE HIPAA

• Fixed component ID

  5724M6100

Applicable component levels

• R431 PSY

     UP

• R440 PSY

     UP