General Description

The EDI Interface is composed of acknowledgment and extraction programs. The actual executable files for the acknowledgment and extraction programs that encompass the EDI Interface are to reside on the primary Support Server machine located at DECC (Defense Enterprise Computing Center) in Ogden, Utah. iRAPT users must prepare EDI files for submission to iRAPT using ANSI X12 EDI Transaction Sets.

Procedure

iRAPT users should prepare EDI files for submission to the iRAPT application using the guidelines and instructions found in the iRAPT EDI Implementation Guides. There are separate guides for each Transaction Set. When the files are ready for submission into iRAPT, the files are forwarded to GEX. The files are then placed in the appropriate directory on the DECC Ogden server.

A batch job is executed at regular intervals for the purpose of collecting these files and processing for submission to the iRAPT Web-based application. The file processing includes validation and error checking of the document information supplied by the user. The initiator of the file should keep copies of all files submitted in the event that errors are encountered triggering the document to be rejected. Rejected documents should be corrected according to the error message received via e-mail and the user will subsequently resubmit. Once the document has been successfully accepted into the Web-based application, the copied files may be deleted.

The document is then available for processing through the iRAPT Web application in the same manner as documents that were originally created using the iRAPT Web application. Users may view the document and the current status by checking their appropriate folder. This allows them to perform the work required to process that document by entering data and digitally signing the document. As previously stated, an e-mail message will be generated to the appropriate user during the processing cycle of the document.

5 EDI – Electronic Data Interchange Interface (Extract)

Introduction

The objective of the iRAPT EDI extract interface is to provide electronic data to external systems programmed to receive information captured within iRAPT. These interfaces have been developed to capture specific information within the iRAPT Web-based application and pass this information electronically to a system that will use this information to both update their records and provide feedback to iRAPT or capture this information for specific business practices. The data captured within iRAPT is transmitted to the appropriate EDI receiver location using standard ANSI X12 Transaction Sets.

The following table contains a list of the EDI Transaction Sets extracted from iRAPT:

Table 7-4: EDI Transactions Sets Extracted From iRAPT

5.2 General Description

The EDI Interface is composed of acknowledgment and extraction programs. The actual executable files for the acknowledgment and extraction programs that encompass the EDI Interface are to reside on the primary Support Server machine located at DECC in Ogden, Utah. For processing the EDI output files from the extraction program, all Transaction Set files are placed within the designated export directory set up by the system administrator.

Procedure

The iRAPT application captures the information relating to a specific document within iRAPT. Once the data has been captured in the specified database, the system will extract the information for EDI transmission. Document extraction is based on the particular type of document and processing requirements. On a periodic basis, the EDI extraction program polls the database and extracts the data that has been identified for conversion to EDI standards and transmission to specified government system. The data is captured in a UDF format and moved to the designated directory. GEX maintains a channel to poll the designated directory and retrieves all files within it. GEX than converts the UDF data submitted by iRAPT to the ANSI X12 Transaction Sets. These X12 transactions are transmitted by the GEX system to a designated receiving activity.

Date: 2016-04-22; view: 961