NCPDP Repetitive fields issue

Hello IBM, 
There are a few repetitive fields in NCPDP type tree (We are using v51 HISTORY) that when client sends data but skips the first fields and sends data in subsequent fields, ITX typetree treats it as coming in order thus we are not able to throw an error at the correct occurrence of data.

To explain with an example:
This field, 
SUBMISSION_TYPE_CODE Field(5:5):PROD_CAT Group:PA_HISTORY_DETAIL Record:H_DETAIL PACDR CopyBook

This is a two byte field, that repeats 5 times and comes in edi from position 2469 to 2478.

If we get a data something like this "    AB    ", this would mean that SUBMISSION_TYPE_CODE[1] is null
SUBMISSION_TYPE_CODE[2] is null
SUBMISSION_TYPE_CODE[3] is "AB"
SUBMISSION_TYPE_CODE[4] is null
SUBMISSION_TYPE_CODE[5] is null.

But because this field is set to Apply Pad as "Any Context" , when mapping in the output, it derives it as follows.
SUBMISSION_TYPE_CODE[1] is "AB"
SUBMISSION_TYPE_CODE[2] is null
SUBMISSION_TYPE_CODE[3] is null
SUBMISSION_TYPE_CODE[4] is null
SUBMISSION_TYPE_CODE[5] is null.

We see that if we change the type tree for these kind of fields to either, 
1) Give them unique names like SUBMISSION_TYPE_CODE_1, SUBMISSION_TYPE_CODE_2 ..and so on, then  it works fine.. 
OR 
2) Change the Apply Pad to Fixed Group for this field, then it works too. (And we take care of trimming the data in Map Rules)..

Here is the list of such fields I found in the typetree:
Under PA_HISTORY_DETAIL Record:H_DETAIL PACDR CopyBook:

NON_POS_CLAIM_OVER_CODE Field(3:3):BENEFIT_CAT Group
REJECT_CODE Field(5:5):CLAIM_CAT Group
SUB_CLAR_CODE Field(9:9):PROD_CAT Group
SUBMISSION_TYPE_CODE Field(5:5):PROD_CAT Group
BENEFIT_STAGE_INDICATOR Field(4:4):FIELDS_ADDED_IN_VERSIONS_CAT Group
MEMBER_SUBT_CLAIM_REJECT_CODE Field(5:5):FIELDS_ADDED_IN_VERSIONS_CAT Group

We are hoping you could provide us a fix pack for this change.
Thanks
Afaque Khan