|
|
================================
Read Me for GEX 5.0 Map Update
Version 06
4 March 2016
================================
----------------
Changes
----------------
============
DJMS-DED v2
Problem: The GS03 value in the Audit X12 824 transactions generated by the
x824 map is mapped from the source channel name. If the source channel name is
greater than 15 positions, the GS03 value exceeds the maximum length permitted
by the built-in X12 validation performed by GEX core and the Audit X12 824
transactions end up in the GEX error queue.
Solution: Modified the x824 map so that the first 15 positions of the source
channel name is mapped to GS03 in the Audit X12 824.
============
DRAS-DED v2
Problem: The GS03 value in the Audit X12 824 transactions generated by the
x824 map is mapped from the source channel name. If the source channel name is
greater than 15 positions, the GS03 value exceeds the maximum length permitted
by the built-in X12 validation performed by GEX core and the Audit X12 824
transactions end up in the GEX error queue.
Solution: Modified the x824 map so that the first 15 positions of the source
channel name is mapped to GS03 in the Audit X12 824.
===========
DTS-XML v9
Problem: DAI ERP recently received accounts receivable transactions with
DODEA lines of accounting (LOAs), but since these transactions were missing the
traveler's address information, DAI ERP rejected them. Since DODEA elected to
continue using its legacy FSN 049451 when it migrated its accounting to DAI ERP
in FY2016, the corresponding entry in DTS-XML's 821 routing table had to retain
SYSTEM="WAAS" to support processing of transactions citing legacy DODEA LOAs in
the WAAS 10x20 format, such that the logic that maps traveler's address
information is not being applied to such transactions.
Solution: Modified logic in DTS-XML U2X map for DTSAuth and DTSAR transactions
so that if first LOA cited is DODEA LOA (based on value of SYSTEM="WAAS" in 821
routing table lookup), Address, City, StateOrProvince, and ZipOrPostalCode are
mapped to REF03 and Address2 is mapped to REF02 all when REF01="MBX".
=======
IPC v3
Problem (EDR: 1602112141): When an incoming IPC 820 User Defined Format (UDF)
transaction failed U2X translation because the Vendor ID it cited was not found
in the tpdb.tbl and vendor.tbl lookup tables, the error message provided in the
MSN Action Summary Page did not include the specific Vendor ID that failed the
lookup.
Solution (EDR: 1602112141): Modified the U2X map so that when a Vendor ID is
not found in the tpdb.tbl and vendor.tbl lookup tables, the Vendor ID is
included in the resulting error message.
|
