|
|
==============================
README for GEX 5.0 Map Update
Version 13
26 August 2016
==============================
----------------
Changes
----------------
============
ADS-DAI2 v4
Enhancement: Modified the ADS-DAI2 U2X map to examine the existence of all RunID
values within the Automated Disbursing System (ADS) Postpay User Defined Format
(UDF) file and parse data entries based on different values. Also, record counts
as received in the ADS Postpay UDF file will now be re-computed to associate the
proper count with the associated RunID values. The structure of the corresponding
Defense Agencies Initiative (DAI) eXtensible Markup Language (XML) remains
unchanged.
=============
DAI-WAWF4 v2
Enhancement: Modified the DAI-WAWF4 map family to provide for translation of DAI
Acknowledgment XMLs to be passed back to Invoicing, Receipt, Acceptance and
Property Transfer (iRAPT). Going forward this will make DAI-WAWF4 traffic
two-way, vice one-way. Please refer to the forthcoming DAI IDG addendum for
details regarding new channels/routes that must be configured.
=============
DAI2-DTS2 v3
Enhancement: Modified DAI2-DTS2 U2X map to translate Centrally Billed Account
(CBA) Advice of Payment (AOP) XMLs from Defense Agencies Initiative (DAI)
Enterprise Resource Planning (ERP) into X12 820 transactions to support Treasury
Direct Disbursements of Defense Travel System (DTS) Centrally Billed Account
(CBA) Invoice 810 transactions that are entitled by DAI ERP. This effort will
initially be limited to DTS CBA Invoices belonging to the Uniformed Services
University of the Health Sciences (USUHS). Please refer to the forthcoming DAI
IDG addendum for details regarding new channels/routes that must be configured.
==============
DCAS2-DAI3 v1
Enhancement: Added DCAS2-DAI3 map family (WebSphere TX 8.4), which is identical
to existing DCAS2-DAI2 map family, with the exception of the U2X map, which adds
logic to map value provided in the Subtrans Code field in the DCAS New Cash UDF
to the <subTransCode> element of the XxintfArReceipt complex type 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.
================
DEAMS-SPS-FC v2
Enhancement: Modified U2X map to support front-end processing for the Defense
Enterprise Accounting and Management System (DEAMS) xProcurement XML with Foreign
Currency (FC) into Standard Procurement System (SPS) SR15 xProcurement to SPS.
==================
DEAMS-SPS13-FC v1
Enhancement: This new map family will support back-end processing and convert
DEAMS SPS SR15 xProcurement into SPS SR13 xProcurement to SPS. Please refer to
forthcoming guidance for details regarding CONOPS and channels to be modified.
==========
DPS-PT v1
Enhancement: Added DPS-PT map family (WebSphere TX 8.0) for the Defense Personal
Property System (DPS) interface with Syncada (PowerTrack) to produce additional
segments and loops in X12 858C transactions using data provided in the input
file from DPS. Please refer to forthcoming guidance for details regarding
CONOPS and channel/route configuration.
============
DTS-XML v11
Enhancement: Per CP160004, in order to support the DAI FY17 migration, modified
logic in DTS-XML U2X map to change the existing edit for DTSAuth transactions
that identifies DAI-related 821-00 and 821-31 transactions citing legacy LOAs on
or after the migration date that are no longer viable, fail translation on these,
and send a Negative Acknowledgment (Reject) back to DTS citing the reason for the
failure, such that it will now continue to only apply this edit to 821-00
transactions and no longer apply it to 821-31 transactions.
Enhancement: In order to support the DAI FY17 migration of Defense Security
Cooperation Agency (DSCA), accounted by the General Accounting and Finance System
(GAFS) 380100) to DAI, modified the logic in the DTS-XML U2X map for DTSAuth
transactions such that if TransactionType is "SUPPLEMENT" (821-31) and the first
Line of Accounting LOA cited is a GAFS LOA, based on SYSTEM being "IPC-GAFS", as
determined from a lookup of the Fiscal Station Number (FSN) in the 821 routing
table:
Map TotalAmount to AMT02 when AMT01="TX"
Map AccountAmount to AMT02 when AMT01="J1"
Map PreviousAmount to AMT02 when AMT01="J2"
since DAI requires all the amounts that DTS furnishes on an 821-31 transaction.
==============
EBIZ-WAWF4 v1
Enhancement: Added EBIZ-WAWF4 map family (WebSphere TX 8.0) to accept iRAPT
Standard Acceptance (861), Standard Pay (810C, 810V) transactions translated by
the front-end WAWF4 and WAWF4-INV maps. The EBIZ-WAWF4 map family translates X12
861, 810C, and 810V X12 transactions into the EBIZ UDF. The decision to deploy
an actual interface between GEX and EBIZ that will use this map family to support
iRAPT processing has yet to be made.
===========
EDA-SYN v9
1. Enhancement: Added logic to map the inbound xProcurement < ContractAcrn> tag
to the <Acrn> tag in the Electronic Document Access (EDA) Synopsis XML for
Standard Financial Information Structure (SFIS) systems.
2. Enhancement: Added logic to map the inbound xProcurement < Cin> tag to the
<Cin> tag in the EDA Synopsis XML for SFIS systems.
3. Enhancement: Added logic to map the inbound xProcurement
<Document/Award/LineItem/Funding/FundingAmount> tag to the <Obligated> tag in the
EDA Synopsis XML for SFIS systems.
=================
MSC-WAWF4-OTA v3
Problem: The sizes of some recent production XML invoices mapped by WAWF4-INV
cause a block element of data in the MSC-WAWF4-OTA X2U map to exceed the 128KB
element size default.
Solution: Increased paging to P512:16 in MSC-WAWF4-OTA's message descript file
and modified X2U map to allow for multiple text components to span each input XML
file to permit larger XML files to be processed without overflowing the size
limit.
===============
SABRS-WAWF4 v2
Enhancement: Added the capability to process Naval Construction (NAVCON) and
Naval Shipbuilding Invoices (NSI). This adds to the existing WAWF Standard
Acceptance and Invoice capability already supported in the X12 to UDF mapping.
The NAVCON and NSI invoices are mapped from WAWF iRAPT extracts via the
WAWF3-INV map, which generates X12 transactions for each invoice and routes
them based on the GS03 value to the SABRS-WAWF4 channel for translation into
the SABRS UDF file. Channel/route configuration details have been provided
separately.
===========
TGET-PT v2
Enhancement: The majority of LOA and TAC records in TGET are used for paying
shipping costs of either Freight or Household Goods shipments. A new identifier
is being introduced within the LOA and TAC records to support Non-Temp Storage
LOA and TAC records. In addition to X12 814s for Freight and Household Goods,
this interface will also generate X12 814s supporting Non-Temp Storage for
ingestion at US Bank.
|
