==============================
README for GEX 5.0 Map Update
Version 15
7 October 2016
==============================

----------------
Changes
----------------

==================
DAI-AGREEMENTS v2

1. Enhancement:  Modified the DAI-AGREEMENTS U2X map to accommodate two new 
fields, TASK_NUMBER and CUSTOMER_NAME, in the incoming Agreements User Defined 
Format (UDF) and to map those to new corresponding elements, taskNumber and 
customerName, in the outgoing eXtensible Mark Language (XML).

2. Enhancement:  Modified the DAI-AGREEMENTS U2X map such that if the 
CUSTOMER_NAME field is not populated in the Agreements UDF, an empty tag will no 
longer be mapped for customername in the outgoing XML.    

3. Enhancement:  Modified the DAI-AGREEMENTS U2X map such that an empty tag will 
no longer be hardcoded for daiRecordId in the outgoing XML.  


==============
DCAS2-DAI3 v2

Problem:  When the Period of Availability Fiscal Year Date field (positions 
018-025) in the DCAS New Cash UDF contains "    XXXX" (four leading spaces), the 
DCAS2-DAI3 U2X map is mapping a single space to a27BegPOA and "XXXX" to 
a28EndPOA.  The Period of Availability Fiscal Year Date field is in DAI 
Accounts Payable (AP) XMLs and Accounts Receivable (AR) XMLs used with 
Transactions By Others (TBO), Transactions for Self (TFS), and Monthly (MOS) 
transactions, which can yield the following combinations:
TBO AP, TBO AR, TFS AP, TFS AR, MOS AP, and MOS AR
However, the Period of Availability Fiscal Year Date field is not currently being
mapped to the a27BegPOA and a28EndPOA elements for MOS AP and MOS AR 
transactions.
 
Solution:  Modified the DCAS2-DAI3 U2X map so that when the Period of 
Availability Fiscal Year Date field contains "    XXXX", the 27BegPOA and 
a28EndPOA tags will not be mapped, which is in keeping with the DCAS New Cash 
UDF-to-XML logical map.


==========
DPS-PT v2

Enhancement: Modified the DPS-PT U2X map to accommodate NTE segments received in 
X12 858C transactions from the Defense Personal Property System (DPS) and 
perpetuate these segments in the outgoing X12 858C transactions.  


=====================
FACTS-FREIGHT-BOL v1

Enhancement:  Added FACTS-FREIGHT-BOL map family (WebSphere TX 8.0) to translate 
FACTS 858R User Defined Format (UDF) Freight Bill of Lading Shipment transactions 
provided by the Financial and Air Clearance Transportation System (FACTS) to X12 
Transaction Set 858R Shipment Information and transmit to Global Freight 
Management (GFM), US Bank, and the Defense Transportation Tracking System (DTTS).  
FACTS-FREIGHT-BOL provides U2X data transformation, audit functionality, business 
rule logic, and acknowledgment reporting.  Please refer to the forthcoming
Interface Deployment Guide (IDG) for details regarding CONOPS and channel/route 
configuration. 


===============
PAM-DAI-ACK v1

Enhancement:  Added PAM-DAI-ACK map family (WebSphere TX 8.0) to translate 
Treasury UDF files into Defense Agencies Initiative (DAI) XML format, which upon 
delivery and processing by DAI will trigger an email from DAI to the defined user 
who will log in to the Treasury Payment Automation Manager (PAM) system to certify 
payments for disbursement by Treasury.  An IDG for PAM-DAI-ACK and PAM-DAI-SRF 
containing details on CONOPS, channel/route configuration, and deployment strategy 
will be forthcoming pending completion of end-to-end JITC testing.


===============
PAM-DAI-SRF v1

Enhancement:  Added PAM-DAI-SRF map family (WebSphere TX 8.0) to translate 
Treasury UDF files into DAI XML format, which upon delivery and processing by 
DAI will serve to complete the invoice payment process by recording check or 
Electronic Funds Transfer (EFT) Trace number into the DAI invoice.  An IDG for 
PAM-DAI-ACK and PAM-DAI-SRF containing details on CONOPS, channel/route 
configuration, and deployment strategy will be forthcoming pending completion of 
end-to-end JITC testing.


=============
WAWF-CAGE v2

Enhancement:  Additional data element separators, sub-data element separators, 
and terminators allowed in 850 and 860 X12 transactions.


=============
WAWF3-INV v8

Problem:  TT 588, 810V X12 to UDF mapping.  The map only translates every 25 PID 
segments from the X12 to WAWF UDF.

Solution:  The WAWF3-INV map was updated to map all 1000 possible X12 PID 
segments from the 810V X12 to the WAWF UDF.