E­FIS Project Interface Specification Document for 014­-I-1, Construction Administration System (CAS)

greasyservantInternet and Web Development

Jul 30, 2012 (5 years and 18 days ago)

573 views





California Department of
Transportation

E
-
FIS Project

Interface

Specification

Document

for
014
-
I
-
1
,
Construction
Administration System
(CAS)



Author:

Chris Pettit

Creation Date:

March

10
,
200
9

Last Updated:

March 10
,
200
9

Control Number:


XXXXX

Version:

0.01







Document Control



Version Control

Date

Author

Version

Change Reference





03
/
09
/
0
9

Chris Pettit

0.01

No previous document























Reviewers

Name

Position





















Distribution Control

Copy No

Name

Location




1


Library Master

Project Library

2


Reviewers

Various

3




4








greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
i


Table of Contents

1

Introduction

1
-
1

1.1

Overview

1
-
1

1.2

Definitions, Acronyms, and Abbreviations

1
-
6

1.3

References

1
-
6

2

Interface Specifications

2
-
7

2.1

General Interface Information

2
-
7

2.1.1

Interface
Id

2
-
7

2.1.2

Interface Name

2
-
7

2.1.3

Business Contact(s)

2
-
7

2.
1.4

Technical Contact(s)

2
-
7

2.1.5

Requirement #’s

2
-
7

2.2

Current Interface Detailed Information

2
-
8

2.2.1

Application Description

2
-
8

2.2.2

Source System

2
-
8

2.2.3

Target System

2
-
8

2.2.4

Frequency

2
-
8

2.2.5

Interface Contents

2
-
8

2.2.6

Interface Volume

2
-
8

2.2.7

Transmission Method and Tools

2
-
8

2.2.8

Data Format

2
-
8

2.2.9

Types of Data Records

2
-
9

2.3

E
-
FIS Interface Specification

2
-
10

2.3.1

Data to be Interfaced

2
-
10

2.3.2

Interface Categorization

2
-
10

2.3.3

Frequency of Interface

2
-
10

2.3.4

Estimate o
f Volume of Data

2
-
10

2.3.5

Source Data Location

2
-
10

2.3.6

Source Data Format

2
-
10

2.3.7

Source Data Availability

2
-
10

2.3.8

Inbound Interface Details

2
-
10

2.3.9

Outbound Interface Details

2
-
11

2.3.10

Loading/Processing Order

2
-
12

2.3.11

Error Handling

2
-
12

2.3.12

Restart Procedures

2
-
12

2.3.13

Timing Constraints and Dependencies

2
-
13

2.3.14

Security Considerations

2
-
13

2.3.15

Operational Considerations

2
-
13

2.3.16

Testing Approach

2
-
13

2.3.17

Middleware Specifications

2
-
13

Appendix A


Data Layout

2
-
15




greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
1
-
1


1

Introduction

1.1

Overview


The Interface Specification Document

provide
s

the detail rules for each
in
terface
. Each
interface

specification provides the following information:





greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
1
-
2


S
ECTION
#

S
ECTION
T
ITLE

C
ONTENT
D
ESCRIPTION

2.
1

General Interface Information

This section describes high
-
level information about the
interface

2.1.1

Interface Id # (tech)

Unique

id to identify each interface

2.1.2

Interface Name (tech)

Descriptive name for the interface

2.1.3

Business Contact(s) (func)

Name, telephone and email address of
functional/business person who is knowledgeable about
the interface

2.1.4

Technical Conta
ct(s) (tech)

Name, telephone and email address of
programmer/analyst who is knowledgeable about the
interface

2.1.5

Requirement #(s) (tech)

Requirement #(s) in the RFP specifying this interface

2.2

Current Interface Information

Information about the curr
ent interface will be in this
section

2.2.1

Application Description
(func)

Describes the system interfacing with E
-
FIS and what
its data represents (e.g., receivables, collections, budget,
encumbrances, expenditures, etc.)

2.2.2

Source System (tech)

Desc
riptive name for the source system

2.2.3

Target System (tech)

Descriptive name for the destination system

2.2.4

Frequency (func)

Describes how often the interface is run

2.2.5

Interface Contents (func)

Describe in business terms what data will be interf
aced
(e.g., open receivables, open encumbrances, etc.)

2.2.6

Interface Volume (tech)

Describes how many records are interfaced

2.2.7

Transmission Method and
Tools (tech)

Describes how data is moved between platforms and the
tool used

2.2.8

Data Format

D
escribes the platform or file type that the source data is
in when it enters the interface process.

2.2.9

Types of Data Records

Describes the order of records, identifying important
characteristics such as header or trailer records present
in the interfac
e file

2.3

E
-
FIS Interface Specification

This section describes the new interface from and to E
-
FIS

2.3.1

Data to be Interfaced

Describes, in business terms, what data is being
interfaced.

2.3.2

Interface Categorization

Describes the interface based on
the criteria in Exhibit



greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
1
-
3


4
-
122 of the System Architecture Design Document.

Data Exchange Synchronicity


Near
-
real Time or
Offline/Batch

Data Exchange Protocol


FTP, Services, Database,
RMI/IIOP/Host Calls

Data Flow Direction


Outbound or Inbound

Message
Exchange Patterns


Reque
st
-
R
esponse,
Request
-
Callback, Publish
-
Subscribe

2.3.3

Frequency of Interface (func)

Frequency of the interface include:



Real Time



Daily



Weekly



Monthly



On Demand



Other frequency


2.3.4

Estimate of volume of data
(tech)

Desc
ribes how much data will be interfaced: low,
average and high volumes

2.3.5

Source Data Location (tech)

Specify where the source data is located.


This would
include: media data is stored on, location, file/table
name, platform, etc.

2.3.6

Source Data Fo
rmat (tech)

Specifies the format of the data from which the extract
will occur (e.g.


flat file, Oracle database, XML)

2.3.7

Source Data Availability

Specifies times that the source data file will be made
available by the external system.

2.3.8

Inbound
Interface Details

Provide data that is specific to an inbound interface.

Do
not complete this section for an outbound interface.

2.3.8.1

Interaction Profile


External
system to WebSphere
Message Broker

Specifies which interface profile is being used, as

well
as any details about it. Choices of profiles are:



File Drop



Web Services



Message
-
based

2.3.8.2

Method(s) of Loading (func)

Methods of loading include:



Utilize Advantage Document to load
operational database and data warehouse



Utilize a new Advanta
ge Document to load new



greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
1
-
4


tables in operation database and data warehouse



Load directly to data warehouse



Other

An interface may use one or more of these methods

Describe the method of loading to the

FIS data
warehouse.

2.3.8.3

Advantage Document (func)

If an Advantage Document is used to load, then species
the Document, Event Type, and Posting Pair

2.3.8.4

Data Warehouse Location
(tech)

If loaded directly to the data warehouse then specifies
where the data will be loaded

2.3.8.5

Summarization (func)

S
pecifies how the source data will be summarized in
order to create loading documents, table records, etc.

2.3.8.6

Interaction Profile


WebSphere Message Broker
to E
-
FIS

Specifies which interface profile is being used, as well
as any details about it. Ch
oices of profiles are:



File Drop



Web Services



Message
-
based


2.3.9

Outbound Interface Details

Provide data that is specific to an outbound interface.

Do not complete this section for an inbound interface.

2.3.9.1

Extract Method (tech)

Describes how the
data will be extracted from the
source system.

2.3.9.2

Extract Date and Constraints
(tech)

Specifies when the data must be extracted from the
source system.

Specifies any constraints such as “at end of calendar
year”, a specific date, etc.

2.3.9.3

Intera
ction Profile


E
-
FIS to
WebSphere Message Broker

Specifies which interface profile is being used, as well
as any details about it. Choices of profiles are:



File Drop



Web Services



Message
-
based


2.3.9.4

Interaction Profile


WebSphere Message Broker
to E
xternal System

Specifies which interface profile is being used, as well
as any details about it. Choices of profiles are:



File Drop



Web Services



Message
-
based





greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
1
-
5


2.3.10

Loading/Processing Order
(func)

Specifies the order in which data will be interfaced.


For
example, specifies the reference tables that must be
loaded prior to processing an Advantage Document


2.3.11

Error Handling (func)

Describes how errors during transformation and loading
will be handled

2.3.12

Restart Procedures (tech)

Describes if t
he interface has restart/recovery
capabilities

2.3.13

Timing Constraints and
Dependencies (tech)

Describes if the interface must be run before or after
other jobs, interfaces, etc.

2.3.14

Security Considerations
(tech)

Describes if there are security req
uirements which must
be addressed during the interface

2.3.15

Operational Considerations
(tech)

Describes other operational considerations

2.3.16

Testing Approach (func)

Specifies how the interface will be tested and validated.

Discusses procedures to en
sure appropriate legacy data
has been correctly interfaced.

2.4.

Middleware Specification

This section describes middleware tasks.


2.4.1

Data Field Mapping
Specification (func)

Specifies the mapping of source data elements to E
-
FIS
loading transaction d
ata elements or the mapping of E
-
FIS source data to the data fields needed by a legacy
system.

2.4.2

Conversion/Transformation
Specification (func)

Specifies the required transformations (e.g.


reverse
field mappings, reverse chart of account crosswalks)

from E
-
FIS elements to source data elements.


List
specific crosswalk maps/tables that will be utilized.

2.4.3

Message Exchange Patterns

When applicable, describe

the Message Exchange
Pattern

used:



Request
-
Response



R
equest
-
Callback



Publish
-
Subscribe










greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
1
-
6


1.2

Definitions, Acronyms, and Abbreviations


Caltrans

California Department of Transportation

CAS

Construction Administration System

EAI

Enterprise Application Integration, the use of software and computer
systems architectural principles to integrate a se
t of enterprise computer
applications.

E
-
FIS

ERP Financial InfraStructure, central to this is the CGI application,
Advantage Financial

ERP

Enterprise Resource Planning

ESB

Enterprise Service Bus, a construct that acts as a mechanism to allow
communication
between multiple systems without point to point
connections

Inbound

E
-
FIS imports data from external source

Middleware

A generic term to refer to
software used as part of the EAI solution

Outbound

E
-
FIS exports data to external source

PISA

Project Informat
ion System Administration

WebSphere Message Broker

The specific middleware used on the E
-
FIS project

for the EAI solution,
created by IBM


1.3

References


SRS docu
ment “I
-
014 V2.0 200810
10.doc”





greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
2
-
7


2

Interface

Specifications

2.1

General Interface Information


2.1.1

Interface

Id

014
-
I
-
1


2.1.2

Interface

Name

CAS to E
-
FIS
-

AP Transactions (Warrants)


2.1.3

Business Contact
(s)

Teresa Naraval

Office:
Accounting

Phone:
916 227
-
9199

Email:
teresa_naraval@dot.ca.gov


2.1.4

Technical Contact
(s)

Mike Creed

Office: IT Solutions Division
, Programmer

Analyst

Phone: 916 440
-
0521

E
-
mail:
mike_creed
@dot.ca.gov


Tracey Donnelly

Office: IT Solutions Division, Supervisor

Phone: 916 440
-
0501

E
-
mail:
tracey_donnelly@dot.ca.gov


2.1.5

Requirement #’s

N/A





greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
2
-
8


2.2

Current Interface
Detailed
Information


2.2.1

Application Des
cription

The Construction Administration System is a sub
-
system of Project Information System Administration
(PISA) that processes and controls the information needed to generate payments. The CAS/EFIS
interfaces will ensure that EFIS will receive the app
ropriate data to support accurate and controlled
payments to the contractors awarded Caltrans construction projects.

The CAS system controls payments
so that projects are completed before all allocated funds are exhausted and it also automates the contrac
t
administration functions.


2.2.2

Source System

CAS

(mainframe
-
based)


2.2.3

Target System

TRAMS


2.2.4

Frequency

Weekly and Monthly
,
5pm & 6pm


2.2.5

Interface Contents

TRAMS INRECORD file
. Contains the following transaction codes:



247



PISA SCHEDULE FOR OTHER LIABILITY PAYME
NTS



29
4



RECORD PAYMENTS TO CONTRACTORS


PISA



299



REDUCE PROJ EXP
-
CONTRACTOR OVERPAY
-
PISA


2.2.6

Interface Volume

LRECL
:
500
,
ROWS
:
600


2.2.7

Transmission Method and Tools

Data file is created on the mainframe.

The transaction processor reads the mainframe file
.


2.2.8

Data Format

Fixed length flat

file.
File name:
TR.CAS.ACC.TRAMS.&DATE&HOUR
.


Layout is contained in the

COBOL copybook


INREC.cpy
”, which is include
d

in Appendix A.




greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
2
-
9



2.2.9

Types of Data Records

The interface will receive a 500 byte record, which contains bat
ched transactions that use a batch header
record that contains batch information, total batch count (number of records in batch) as well as total
batch amount (summarized total of all records in the batch).





greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
2
-
10


2.3

E
-
FIS Interface Specification


2.3.1

Data to be
Inte
rface
d

E
-
FIS (inbound from CAS) receives payment data and Accounts Payable transactions needed to pay
contractors for construction projects awarded by Caltrans.


2.3.2

Interface Categorization

Characteristics:



Data Exchange Synchronicity


Offline/Batch



Data Exc
hange Protocol


FTP



Data Flow Direction


Inbound



Message Exchange Patterns


N/A.



Interaction Profile


File Drop


2.3.3

Frequency of Interface

Weekly and Monthly
,
5pm & 6pm


2.3.4

Estimate of Volume of Data

LRECL
:
500
,
ROWS
:
600
, approximately

3
00KB


2.3.5

Source

Data

Lo
cation

Original data is on DTS Mainframe, and then is sent (using FTP) to the EAI server.


2.3.6

Source Data

Format

Flat file in the
TRAMS IN
RECORD layout.

The layout is contained in a COBOL copybook
, and is in
Appendix A
. The file contains one or more batches
. Each batch consists of one or more detail records
followed by a footer.


2.3.7

Source Data Availability

The data will be made available by
7
pm. It must be processed prior to 6am the following day.


2.3.8

Inbound Interface Details

Provide data that is specific to a
n inbound interface.

Do not complete this section for an outbound
interface.

2.3.8.1

Interaction Profile


External System to WebSphere Message Broker

File Drop



TBD

will drop the file in
to the location
TBD
.





greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
2
-
11


2.3.8.2

Method(s) of Loading

XML for Advantage Financial docu
ments will be built
dropped into a pre
-
defined location, and will be
picked up

and processed

during the nightly cycle

using the AMS JobInteractionClient.


2.3.8.3

Advantage Document

T
-
Code

Advantage Financial Document

Event Type

Posting Pair

247

TBD



GAX?

TBD

DR



3790

CR


3020

247R

TBD



GAX?

TBD

DR


3020

CR


3790

294

TBD



GAX?

TBD

DR
-
1


9000

CR
-
1


7971

DR
-
2


5350

CR
-
2


6150

299

TBD



GAX?

TBD

DR
-
1


7971

CR
-
1


9000

DR
-
2


6150

CR
-
2


5350



2.3.8.4

Data Warehouse Location

N/A


2.3.8.5

Summarization

Data will not
be summarized for this interface.


2.3.8.6

Interaction Profile


WebSphere Message Broker to E
-
FIS

File Drop



The FileOutput node of the message flow for this interface will place the file into the location
TBD
.


2.3.9

Outbound Interface Details

Provid
e data that is sp
ecific to an out
bound interface.

Do not
complete this section for an in
bound
interface.




greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
2
-
12


2.3.9.1

Extract Method

N/A


this is an inbound interface


2.3.9.2

Extract Date

and Constraints

N/A


this is an inbound interface


2.3.9.3

Interaction Profile


E
-
FIS to WebSphere Message Br
oker

N/A


this is an inbound interface


2.3.9.4

Interaction Profile


WebSphere Message Broker to External System

N/A


this is an inbound interface


2.3.10

Loading/Processing Order

This interface does not have special loading/processing needs.


2.3.11

Error Handling


The stan
dard framework will be used for audit and error handling:



Database tables in the Advantage Financial database will record audit information at the file and
batch level.



Logs will be used to store error information for research purposes. Either the log fil
es, or a
hyperlink to the log files, will be sent to the designated E
-
FIS staff.



A minimal amount of business logic will be implemented within the interface. This includes
batch, document ID. and t
-
code validation. Records that fail this logic will not b
e written to E
-
FIS.


2.3.12

Restart Procedures

The restart procedures depend on the nature of the error.



Errors with the data file prior to entering the WMB are the responsibility of the sender.



Batch level errors must be fixed by the sender. The batch will then

be rerun through the WMB.



Errors within the WMB must be researched independently to determine the restart procedure.



Errors that appear in E
-
FIS do not require a restart.





greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
2
-
13


2.3.13

Timing Constraints and Dependencies

The current system requires this interface grab

the data file prior to 6:00am the following morning.


2.3.14

Security Considerations

This interface does not have special security considerations.


2.3.15

Operational Considerations

Files sent by
CA
S must be archived for 6 months.


2.3.16

Testing Approach

Testing will occur i
n three phases:



Unit testing, done during interface development, will follow the unit testing template provided by
CGI.



System/Integration testing, which encompasses the entire E
-
FIS system, will include interface
testing.



User Acceptance Testing will be p
erformed by Caltrans prior to the cutoff to production.


2.3.17

Middleware Specifications

This section describes middleware tasks.


2.3.17.1

Transformation Specification


Message Flow Node

Required?

Comments

Pre
-
processing

Yes

This interface will be processed by the same

message flow used for all interfaces in INREC
format.

Transform from Current Layout
to Canonical

Yes

This interface will be processed by the same
message flow used for all interfaces in INREC
format.

Transform from Canonical
Layout to AFIN XML

Yes

This
interface will be processed by the same
message flow used for all interfaces in INREC
format.

Audit Subflows

Yes

The standard audit subflow will be used.

Error Subflows

Yes

The standard error subflow will be used.




greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
2
-
14



Element Requiring Crosswalk

Direction
of Crosswalk

TBD

Generate E
-
FIS Values



2.3.17.2

Message Exchange Patterns

N/A




greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
2
-
15


Appendix A


Data Layout

* * * * * * * * * * 00001000

000070 00002000

000080 01 IN
-
RECORD.

00003000

000090 05 IN
-
DATA
-
TYPE PIC X. 00004000

000100 05 IN
-
TRANS
-
ID
-
SEGMENT. 00005000

000110 10 IN
-
BATCH
-
ID.

00006000

000120 15 IN
-
BATCH
-
DISTRICT PIC X(2). 00007000

000140 15 IN
-
BATCH
-
DATE PIC X(6). 00008000

000150 15 IN
-
BATCH
-
TYPE PIC X. 0
0009000

000160 15 IN
-
BATCH
-
NO PIC X(3). 00010000

000170 10 IN
-
BATCH
-
SEQ
-
NO PIC X(5). 00011000

000170 10 IN
-
FUND
-
SPLIT
-
SEQ
-
NO PIC X(2). 00012000

00018
0 10 IN
-
DUP
-
REC
-
IND PIC X. 00013000

000190 05 IN
-
BATCH
-
REC
-
1. 00014000

000200 10 IN
-
BATCH
-
REC
-
DATA. 00015000

000210

15 IN
-
FISCAL
-
MONTH PIC X(2). 00016000

000220 15 IN
-
BATCH
-
CLAIM
-
SCHED
-
NO PIC X(8). 00017000


15 FILLER PIC X(6). 00018000


15 IN
-
BATCH
-
DISB
-
METHOD
-
IND PIC X(1). 00019000


15 IN
-
BATCH
-
OPERATOR
-
ID PIC X(5). 00020000

000240 15 IN
-
ENTERED
-
BATCH
-
COUNT PIC X(5). 00021000

000260 15 IN
-
ENTERED
-
BATCH
-
COUN
T
-
N REDEFINES 00022000

000270 IN
-
ENTERED
-
BATCH
-
COUNT PIC 9(5). 00023000

000290 15 IN
-
ENTERED
-
BATCH
-
AMT PIC X(13). 00024000

000310 15 IN
-
ENTERED
-
BATCH
-
AMT
-
N R
EDEFINES 00025000

000320 IN
-
ENTERED
-
BATCH
-
AMT PIC 9(11)V99. 00026000

000290 15 IN
-
ENTERED
-
BATCH
-
HOURS PIC X(13). 00027000

000310 15 IN
-
ENTERED
-
BATCH
-
HOURS
-
N REDEFINES

00028000

000320 IN
-
ENTERED
-
BATCH
-
HOURS PIC 9(11)V99. 00029000

000340 15 IN
-
COMPUTED
-
BATCH
-
COUNT PIC X(5). 00030000

000360 15 IN
-
COMPUTED
-
BATCH
-
COUNT
-
N REDEFINES 00031000

00
0370 IN
-
COMPUTED
-
BATCH
-
COUNT PIC 9(5). 00032000

000390 15 IN
-
COMPUTED
-
BATCH
-
AMT PIC X(13). 00033000

000410 15 IN
-
COMPUTED
-
BATCH
-
AMT
-
N REDEFINES 00034000

000420

IN
-
COMPUTED
-
BATCH
-
AMT PIC 9(11)V99. 00035000

000390 15 IN
-
COMPUTED
-
BATCH
-
HOURS PIC X(13). 00036000

000410 15 IN
-
COMPUTED
-
BATCH
-
HOURS
-
N REDEFINES 00037000

000420 IN
-
CO
MPUTED
-
BATCH
-
HOURS PIC 9(11)V99. 00038000

000440 15 IN
-
BATCH
-
STATUS PIC X. 00039000

000450 88 TRANSMIT
-
AFTER
-
DATE VALUE ' '. 00040000

000460 88 DO
-
NOT
-
TRANSMI
T
-
HOLD VALUE 'H'. 00041000

000470 88 TRANSMIT
-
OVERRIDE VALUE 'O'. 00042000

000480 88 TRANSMIT
-
RELEASE VALUE 'R'. 00043000

000490 15 IN
-
BATCH
-
HDR
-
CNT
-
SW PIC
X. 00044000

000500 88 BATCH
-
HDR
-
CNTS
-
NOT
-
CORRECT VALUE 'N'. 00045000

000510 88 BATCH
-
HDR
-
CNTS
-
ARE
-
CORRECT VALUE 'Y'. 00046000

000520 15 IN
-
LAST
-
SEQ
-
NO
-
USED PIC X(5).

00047000

000530 15 IN
-
SYSTEM
-
DATE PIC 9(5). 00048000

000540 15 FILLER PIC X(383). 00049000

000550 00050000

000560 05 IN
-
BATCH
-
REC
-
2 REDEFINES 00051000

000570 IN
-
BATCH
-
REC
-
1. 00052000

000580 10 IN
-
INPUT
-
DATA
-
SEGMENT. 00053000

000280

15 IN
-
FM PIC X(2). 00054000

000580 15 IN
-
CLAIM
-
SCHED
-
NO PIC X(8). 00055000

000570 15 IN
-
CHECK
-
DATE PIC X(6). 00056000


15 IN
-
DISB
-
METHOD
-
IND PIC X(1). 00057000


15 IN
-
OPERATOR
-
ID PIC X(5). 00058000

000240 15 IN
-
TRANS
-
CODE PIC X(3). 00059000




greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
2
-
16


000250 15 IN
-
MODIFIER

PIC X. 00060000

000260 15 IN
-
REVERSE PIC X. 00061000

000270 15 IN
-
FFY PIC X(2). 00062000


15 IN
-
CHARGE
-
DISTRICT

PIC X(2). 00063000


15 IN
-
SOURCE
-
DISTRICT PIC X(2). 00064000


15 IN
-
SOURCE
-
UNIT PIC X(4). 00065000


15 IN
-
EA PIC X(6).

00066000


15 IN
-
SUBJOB PIC X(5). 00067000


15 IN
-
PROG PIC X(2). 00068000


15 IN
-
ELEM PIC X(2). 00069
000


15 IN
-
COMPONENT PIC X(3). 00070000


15 IN
-
TASK PIC X(3). 00071000


15 IN
-
COE PIC X(6). 00072000



15 IN
-
BUDGET
-
CODE PIC X(1). 00073000

000310 15 IN
-
APPN
-
SYM PIC X(3). 00074000

000320 15 IN
-
FUND PIC X(3). 00075000

000350 15

IN
-
FUND
-
DETAIL PIC X(2). 00076000

000330 15 IN
-
FUND
-
SOURCE PIC X. 00077000


15 IN
-
STAT
-
REPORT
-
ACCT PIC X(3). 00078000


15 IN
-
CONTRIBUT
OR PIC X(5). 00079000


15 FILLER PIC X(3). 00080000


15 IN
-
COUNTY PIC X(4). 00081000


15 IN
-
GRANT
-
CODE

PIC X(6). 00082000


15 IN
-
GRANT
-
PHASE PIC X(2). 00083000


15 IN
-
INT
-
DIST
-
CLEAR
-
NO PIC X(5). 00084000


15 IN
-
PRIVATE
-
CAR
-
MILES PIC X(4)
. 00085000


15 IN
-
ORIGINAL
-
FY PIC X. 00086000


15 IN
-
FED
-
AID
-
ELIG PIC X. 00087000

000380 15 IN
-
OBJ
-
DETAIL PIC X(3). 00
088000


15 IN
-
AGCY
-
OBJ PIC X(3). 00089000

000400 15 IN
-
SOURCE PIC X(6). 00090000

000410 15 IN
-
AGCY
-
SOURCE PIC X(2). 00091000

000450

15 IN
-
SUBSIDIARY
-
ACCT
-
NO PIC X(8). 00092000


15 IN
-
SPECIAL
-
DESIGNATION
-
CODE PIC X(12). 00093000

000470 15 IN
-
GL
-
ACCT
-
NO PIC X(4). 00094000


15 IN
-
ORIGINAL
-
FM PIC X(2). 00095000

000480 15 IN
-
VENDOR
-
NO PIC X(10). 00096000

000490 15 IN
-
VENDOR
-
SUFFIX PIC X(2). 00097000

000500 15 IN
-
REPORT
ABLE
-
PAYMENTS
-
IND PIC X. 00098000

000510 15 IN
-
INV
-
NO PIC X(14). 00099000

000520 15 IN
-
DOC
-
DATE PIC X(6). 00100000

000530 15 IN
-
CUR
-
DOC
-
NO

PIC X(8). 00101000

000540 15 IN
-
CUR
-
DOC
-
NO
-
SUFFIX PIC X(2). 00102000

000550 15 IN
-
REF
-
DOC
-
NO PIC X(8). 00103000

000560 15 IN
-
REF
-
DOC
-
NO
-
SUFFIX PIC X
(2). 00104000

000590 15 IN
-
CHECK
-
NO PIC X(9). 00105000

000600 15 IN
-
FUND
-
CTL
-
ORD PIC X. 00106000

000610 15 IN
-
TRANS
-
AMOUNT PIC 9(11)V99.

00107000


15 IN
-
TRANS
-
HOURS PIC 9(11)V99. 00108000


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 00109000


* * * EVENTHOUGH IN
-
TRANS
-
HOURS IS DEFINED AS A FIELD WITH 2 00110000



* * * DECIMAL PLACES, IT SHOULD BE TREATED AS A FIELD WITH ONLY 00111000


* * * 1 DECIMAL PLACE. THE SECOND DECIMAL WILL BE ZERO FILLED. 00112000


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 00113000



15 IN
-
TYPE
-
PAYMENT
-
DESCRIPTION PIC X(10). 00114000


15 IN
-
MSA PIC X(9). 00115000

000660 10 IN
-
NAME
-
ADDRESS
-
SEGMENT. 00116000

000670 15 IN
-
VEN
DOR
-
NAME PIC X(32). 00117000


15 FILLER REDEFINES 00118000


IN
-
VENDOR
-
NAME. 00119000


20 IN
-
WARRANT
-
NO
-
F
ROM PIC X(10). 00120000


20 IN
-
WARRANT
-
NO
-
TO PIC X(10). 00121000


20 FILLER PIC X(12). 00122000


15 IN
-
FAMILY
-
PROBLEM.

00123000


20 IN
-
FAMILY PIC X. 00124000




greasyservant_eca7d5c8
-
3319
-
4ab4
-
9101
-
536c501bf954.doc

3/14/2013

Page
2
-
17



20 IN
-
PROBLEM PIC X. 00125000


20 IN
-
METHOD.

00126000


25 IN
-
METHOD
-
HOW PIC X. 00127000


25 IN
-
METHOD
-
WHY PIC X. 00128000


25 IN
-
METHOD
-
WHEN PIC X. 00129000


15 IN
-
MM
-
COUNTY PIC X(2). 00130000


15 IN
-
CBARS
-
ADJ
-
TYPE6
-
IND PIC X. 00131000

000690 15 IN
-
VENDOR
-
ADDR
-
1 PIC X(39). 00132000


***VEND
OR
-
ADDR
-
1 DISPLAYED AS CONTD 1 ONLINE 00133000


***EFT 00134000


15 FILLER REDEFINES IN
-
VENDOR
-
ADDR
-
1. 00135000


20

IN
-
CONTRACT PIC X(17). 00136000


20 IN
-
CONTRACT
-
AMNT PIC X(13). 00137000


20 IN
-
CONTRACT
-
AMNT
-
N REDEFINES 00138000


IN
-
CONTRACT
-
AMNT PIC 9(11)V99. 00139000


20 IN
-
BATCH
-
EDIT
-
IND PIC X(01). 00140000


20 FILLER PIC X(08). 00141000


***EFT
-

END

00142000

000700 15 IN
-
VENDOR
-
ADDR
-
2 PIC X(39). 00143000

000710 15 IN
-
VENDOR
-
ADDR
-
3 PIC X(39). 00144000


***VENDOR
-
ADDR
-
3 DISPLAYED AS MAIL
-
ADDR ONLINE

00145000


***EFT 00146000


15 FILLER REDEFINES IN
-
VENDOR
-
ADDR
-
3. 00147000


20 IN
-
OCCUP
-
DATE PIC X(06). 001480
00


20 IN
-
LEASE
-
TERMIN
-
DATE PIC X(06). 00149000


20 FILLER PIC X(27). 00150000


***EFT
-

END 00151000

000720

15 IN
-
VENDOR
-
CITY PIC X(19). 00152000


15 IN
-
ROUTE PIC X(3). 00153000


15 IN
-
POSTMILE
-
FROM
-
DATA. 00154000


20 IN
-
POSTMILE
-
FROM
-
PREFIX PIC X. 00155000


20 IN
-
POSTMILE
-
FROM
-
NO PIC X(4). 00156000


20 IN
-
POSTMILE
-
FROM
-
NO
-
N REDEFINES 00157000


IN
-
POSTMI
LE
-
FROM
-
NO PIC 9(3)V9. 00158000


15 IN
-
POSTMILE
-
TO
-
DATA. 00159000


20 IN
-
POSTMILE
-
TO
-
PREFIX PIC X. 00160000


20 IN
-
POSTMILE
-
TO
-
NO

PIC X(4). 00161000


20 IN
-
POSTMILE
-
TO
-
N REDEFINES 00162000


IN
-
POSTMILE
-
TO
-
NO PIC 9(3)V9. 00163000

000730 15 IN
-
VENDOR
-
STATE PIC X(2).

00164000

000740 15 IN
-
VENDOR
-
ZIP PIC X(9). 00165000


10 FILLER PIC X(23). 00166000

001150* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 001
67000

001160* * 00168000

001170* END OF COPY MEMBER IINREC * 00169000

001180* * 00170000

001190*

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 00171000