MERS to SCO Interface

Document Sample
MERS to SCO Interface Powered By Docstoc
					     ERP Financial InfraStructure (E-FIS)

     Software Requirements Specifications




Construction Administration System (CAS)/E-FIS
                  Interface
                     I-014




          Developed by: Rajive Dsouza, Analyst

            Last modified: October 10, 2008
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008



1.0 Introduction _________________________________________________________ 4
  1.1      Purpose of the Software Requirements Specification (SRS) __________________________________ 4
  1.2      Scope of the Software Requirements Specification _________________________________________ 4
  1.3      Definitions, Acronyms, and Abbreviations ________________________________________________ 4
  1.4      References ___________________________________________________________________________ 4
  1.5      Overview ____________________________________________________________________________ 5
2.0     General Description __________________________________________________ 5
  2.1     Product Perspective ___________________________________________________________________ 5
  2.1.1 System Interfaces _______________________________________________________________________ 6
      2.1.1.1 The Accounts Payable transaction Interface ______________________________________________________ 6
      2.1.1.2 The Progress Estimates tracking System Interface _________________________________________________ 6
      2.1.1.3 The Document File Interface ___________________________________________________________________ 6
  2.1.2 User Interfaces _________________________________________________________________________ 6
  2.1.3 Hardware Interfaces ____________________________________________________________________ 6
  2.1.4 Software Interfaces _____________________________________________________________________ 6
  2.1.5 Communication interface ________________________________________________________________ 6
  2.1.6 Memory Constraints ____________________________________________________________________ 6
  2.1.7 Operations ____________________________________________________________________________ 7
  2.2     Product Functions ____________________________________________________________________ 7
  2.2.1 Software Functions _____________________________________________________________________ 7
  2.2.2 Transmission Verification ________________________________________________________________ 7
  2.2.3 Process Transactions ____________________________________________________________________ 7
  2.3     User Characteristics __________________________________________________________________ 7
  2.4     General Constraints ___________________________________________________________________ 8
  2.5     Assumptions and Dependencies _________________________________________________________ 8
  2.5.1 Assumptions ___________________________________________________________________________ 8
  2.5.2 Dependencies __________________________________________________________________________ 8
3.0     Specific Requirements ________________________________________________ 8
  3.1     External Interface Requirements ________________________________________________________ 8
  3.1.0 Accounts Payable transaction Interface ____________________________________________________ 8
  3.1.0.1 Progress Estimate Tracking System Interface _____________________________________________ 12
  3.1.0.2 Document File Interface _______________________________________________________________ 12
  3.1.1 User interfaces ________________________________________________________________________ 13
  3.1.2 Hardware interfaces ___________________________________________________________________ 13
  3.1.3 Software interfaces ____________________________________________________________________ 13
  3.1.4 Communication interfaces ______________________________________________________________ 13
  3.2     Product Detailed Functions____________________________________________________________ 13
  3.2.1 Receive flat file weekly _________________________________________________________________ 13
  3.2.2 Process Transactions ___________________________________________________________________ 13
  3.2.3 Send the VSAM file weekly ______________________________________________________________ 13
  3.3     Performance Requirements ___________________________________________________________ 14
  3.4     Design Constraints ___________________________________________________________________ 14
  3.5     Software System Attributes ___________________________________________________________ 14
  3.5.1 Reliability ____________________________________________________________________________ 14
  3.5.2 Availability ___________________________________________________________________________ 14


                                                             2
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

  3.5.3 Security ______________________________________________________________________________ 14
  3.5.4 Maintainability ________________________________________________________________________ 14
4.0     Supporting Information _____________________________________________ 15
  4.1      Revision History _____________________________________________________________________ 15
  4.2      Appendices _________________________________________________________________________ 15
      4.2.1 Appendix A – Accounts Payable transaction Interface ______________________________________________ 15
      4.2.2 Appendix B – Progress Estimate Tracking System (Contract Data Layout) _____________________________ 21
      4.2.3 Appendix C – Progress Estimate Tracking System Payment Data Layout ______________________________ 22
      4.2.4 Appendix D – Accounts Payable transaction Interface IN Record Copy Member ________________________ 23
      4.2.5 Appendix E – Document File Record Copy Member ________________________________________________ 27
  4.3      Recommendations and Considerations __________________________________________________ 32




                                                             3
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

1.0 Introduction


1.1     Purpose of the Software Requirements Specification (SRS)
        This document describes the specifications for the development of system interfaces, inbound and
        outbound, to the Department’s Enterprise Resource Planning (ERP) – Financial InfraStructure
        System (E-FIS).


1.2     Scope of the Software Requirements Specification
        This document provides the requirements for the interface(s) between the Construction
        Administration System (CAS) and E-FIS. This document is a development tool and design guide for
        developers in selecting a design to exchange data between CAS and E-FIS.



1.3     Definitions, Acronyms, and Abbreviations

Caltrans                          California Department of Transportation
DOA                               Division of Accounting
EAI                               Enterprise Application Integrator
EFIS                              ERP Financial InfraStructure
ERP                               Enterprise Resource Planning
IFMS                              Integrated Financial Management System
Inbound                           E-FIS imports data from external source
Outbound                          E-FIS exports data to external source
BEES                              Basic Engineering Estimating System
PISA                              Project Information System Administration
CUC                               Construction Unit Cost System
PMCS                              Project Management & Control System
BID                               Bid Opening System
CAS                               Construction Administration System
BBA                               Bridge Bid Analysis System
PETS                              Progress Estimate Tracking System

1.4     References
        PISA Business Process Review (2000) – R&G Associates LLC
        Program documentation - IT Solutions Division (ITSD)

        Contacts: Virginia Bolton
        Office: IT Solutions Division
        Phone: 916-440-0591

1.5     Overview

                                                             4
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

        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 appropriate data to support accurate and
        controlled payments to the contractors awarded Caltrans construction projects. This SRS contains the
        specific requirements that will be used to design the CAS to E-FIS Interface.




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



                                                                  E-FIS
                                                                (TRAMS)
                                                                 (PETS)
                            Transactions to TRAMS




                                                                  Payment Data data to




                                                                                             Encumbrance Data
                              (TC 247, 294, 299)
                               Accounts Payable




                                                                                                 TRAMS
                                                                        PETS




                                                    Construction Administration System
                                                                   CAS




2.1 Product Perspective
    The CAS to EFIS interface is designed to transmit Accounts Payable transactions needed to pay
    contractors for work completed on construction contracts awarded by Caltrans. The CAS system controls
    payments so that projects are completed before all allocated funds are exhausted and it also automates
    the contract administration functions.

        2.1.1 System Interfaces

                                                                                         5
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                 2.1.1.1 The Accounts Payable transaction Interface
                 (E-FIS inbound from CAS) provides Accounts Payable transactions for contract payments.


                  2.1.1.2 The Progress Estimates tracking System Interface
                 (E-FIS inbound from CAS) provides payment data for contract payments.

                 2.1.1.3 The Document File Interface
                 (E-FIS outbound to CAS) provides the data for encumbrances (general ledger account 6150).


        2.1.2 User Interfaces
               N/A

        2.1.3 Hardware Interfaces
              CAS: Mainframe (DTS)
              E-FIS: TBD

        2.1.4 Software Interfaces
              URS: TSO
              E-FIS: TBD

        2.1.5 Communication interface
               CAS: Mainframe (FTP) to E-FIS (Server name - TBD)
        2.1.6 Memory Constraints

                 Accounts Payable transaction Interface (E-FIS inbound from CAS)
                         LRECL: 500
                         ROWS: 600

                 The Progress Estimates tracking System Interface (E-FIS inbound from CAS)
                         LRECL: 170
                         ROWS: 300

                 The Document File Interface (E-FIS outbound to CAS)
                        Only for general ledger 6150 - Encumbrances
                         LRECL: 566
                         Key length: 59
                         ROWS: 123,000

        2.1.7 Operations
               Accounts Payable transaction Interface:


                                                             6
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

               Frequency: Weekly and Monthly
               Time: 5pm & 6pm
               Estimated Processing Time: 20 min
               Process: Must be able to re-send files if transmission is unsuccessful
               Backup: File retention - 3 months
               Recovery: Delete file on mainframe and rerun process

               The Progress Estimates tracking System Interface:
               Frequency: Weekly and Monthly and on demand
               Time: 5pm & 6pm
               Estimated Processing Time: 20 min
               Process: Must be able to re-send files if transmission is unsuccessful
               Backup: File retention - 3 months
               Recovery: Delete file on mainframe and rerun process

               The Document File Interface:
               Frequency: Weekly and Monthly
               Time: 5pm & 6pm
               Estimated Processing Time: 20 min
               Process: Must be able to re-send files if transmission is unsuccessful
               Backup: File retention - 3 months
               Recovery: Delete file on mainframe and rerun process


2.2     Product Functions

        2.2.1 Software Functions
              This interface receives sequential files weekly and monthly that contain Accounts Payable
              transactions and payment data. There are separate files for Accounts Payable transactions for
              warrants, payable transactions for Electronic fund transfers, payment data and contract
              information.

        2.2.2 Transmission Verification
               Interface must provide control check to make sure that the file was transferred successfully.

        2.2.3 Process Transactions
              The transactions received need to be formatted and loaded to the ERP/Data Warehouse.

2.3     User Characteristics
        N/A



2.4     General Constraints

                                                             7
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

        The interface will need the ability to run on request in order to process transactions when the file
        transfer fails.


2.5     Assumptions and Dependencies

        2.5.1 Assumptions
              1) E-FIS will receive files in the current “as-is” file layout format, file type and filename.
               The length of the records will be 500 bytes long and also conform to the attached data format
               specification (Appendix A).

               The interface must have the ability to process between 6:00 PM – 7:00AM.


               2) E-FIS will send encumbrances information from Document file in the current “as-is” file
               layout format, file type and filename.
               The length of the records will be 566 bytes long and key length 59 and also conform to the
               attached data format specification (Appendix E).

               The interface must have the ability to process before night net (started at 4:00 pm).

        2.5.2 Dependencies
              The Accounts Payable transactions for electronic fund transfers from CAS will be available
              every Thursday by 5:00PM and the Accounts Payable transactions for warrants will be
              available every Thursday at 6:00PM.


3.0     Specific Requirements

      3.1      External Interface Requirements

        3.1.0 Accounts Payable transaction Interface
                 The interface will receive a 500 byte record, which contains batched transactions that use the
                 following transaction code and 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).




                 TC247 – Record PISA claim Schedules: The purpose of this Transaction Code is to balance
                 UCM GLA 3020 - Claims Filed for PISA contracts when an overpayment to a contractor has
                 occurred. This transaction will require OARPA to bill the contractor or offset against the

                                                             8
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                 next contract payment for the amount of the overpayment. If a bill is prepared, it will also be
                 necessary to prepare and enter it in TRAMS as an accounts receivable entry. The following
                 are required fields for transaction code 247, see Appendix A & D.

                 Source district

                 Charge district

                 Fund

                 Claim Schedule Number

                 DMI

                 TC247 - PISA SCHEDULE FOR OTHER LIABILITY PAYMENTS : The purpose of
                 this Transaction Code is to schedule payments to contractors for amounts withheld from
                 contractors on Transaction Code 247 R. This Transaction Code is computer generated from
                 the PISA Subsystem with a Batch Type P.

                 The following are required fields for transaction code 247, see Appendix A & D.

                 Source District

                 Charge District

                 R-Doc

                 Subsidiary Account

                 Fund

                 Claim Schedule

                 DMI

                 TC 294 - RECORD PAYMENTS TO CONTRACTORS – PISA

                 The following are required fields for transaction code 294, see Appendix A & D.

                 Source District

                 Source Unit

                 Charge District

                 Federal Aid

                 Agency Object

                 R-Doc


                                                             9
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                 Claim Schedule

                 DMI

                 The following are required fields that are currently looked up in TRAMS Tables for
                 transaction code 294:

                 Object Detail

                 Program

                 COE

                 BC

                 APP-SYM

                 Fund

                 Fund Source

                 Method

        TC 299 - REDUCE PROJ EXP-CONTRACTOR OVERPAY-PISA: The purpose of this
        Transaction Code is to reduce expenditures, adjust encumbrances and adjust the amount of the
        claims scheduled to the contractor through the PISA subsystem. All postings are automatically
        generated to the required fields.

        The following are required fields for transaction code 299, see Appendix A & D:

                 Charge Doc

                 Source District

                 Source Unit

                 Charge District

                 Expenditure Authorization

                 Federal Aid

                 Agency Object

                 R-Doc

                 IDC-No

                 Claim Schedule



                                                            10
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                 DMI

        The following are required fields that are currently looked up in TRAMS Tables for
        transaction code 299:

                 Object Detail

                 REVSRC

                 Program

                 COE

                 BC

                 APP-SYM

                 Fund

                 Fund Source

                 Method

        The following are required fields for batch header , See Appendix A & D

                 Batch district

                 Data Type

                 Batch district

                 Batch date

                 Batch type

                 Batch number

                 Batch sequence number

                 Fund split seq no

                 Duplicate record ind

                 Batch count

                 Batch amount

                 Batch hours




                                                            11
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                 The current name of the file is TR.CAS.ACC.TRAMS.&DATE&HOUR Date is the current
                 date. Please see appendix A for file layout.

        3.1.0.1 Progress Estimate Tracking System Interface
                The PETS interface will be replaced by E-FIS (See SRS C-016) and receives two files one
                containing contract data (454 bytes) and the other payment data (170 bytes). This data is used
                to compile a complete history of contract payments. Accounting uses this data to provide
                online payment history, latest payment status, check verification, and to publish work stop
                notices. This history is accessible through the Caltrans internet and can be searched by either
                contract number or contractor name.
                The current names of the files are TR.PETS.PAYMENTS (payment data) and
                TR.PETS.CONTRACTS (contract data). Please see Appendix B & C for file layout.

        3.1.0.2 Document File Interface
                The TRAMS interface will be replaced by E-FIS (See SRS C-016). TRAMS provided only
                encumbrances information (general ledger 6150) from document file for CAS. CAS uses the
                DF file primarily to locate and encumber funds by a given Fiscal Year.

                 The following are required fields from Document file:

                 DF-district
                 DF-gl-acct-no
                 DF-doc-number
                 DF-document-number suffix
                 DF-FFY
                 DF-EA
                 The following balances as of the current date (Project-To-Date – bucket 1):
                 DF-Document-amount
                 DF-Adjustment-amount
                 DF-Liquidation-amount

                 The current names of the files are TRUCAT02.TR.FIS.PROD1.DF (Document File). Please
                 see Appendix E for file layout.




        3.1.1 User interfaces
              N/A

        3.1.2 Hardware interfaces
               CAS – Mainframe

                                                            12
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

               E-FIS – ERP/Data Warehouse

        3.1.3 Software interfaces
                 CAS: COBOL-2LE, CICS, EXEC2, REX, HTML

                 E-FIS: TBD

        3.1.4 Communication interfaces
               The interface will need to be able to receive a file from CAS which is a mainframe application,
               via FTP to the E-FIS (EAI – TBD). An email message sent to the mainframe is required to
               notify of successful data transmission. Email should be sent to E-FIS IT Prod account for the
               E-FIS IT Staff


3.2     Product Detailed Functions

        3.2.1 Receive flat file weekly
               This interface receives two flat files weekly that contains approximately 275 transactions. The
               file is 500 bytes long. The current name of the file is
               TR.CAS.ACC.TRAMS.&DATE.&TIME. Please see appendix A & D for file layout.

        3.2.2 Process Transactions
               The transactions received need to be formatted and loaded to the ERP/Data Warehouse. If an
               error occurs, the transfer has to be rolled back and the data needs to be resubmitted.

        3.2.3 Send the VSAM file weekly
               This interface sends encumbrances data from Document file in VSAM format weekly that
               contains approximately 123,000 records. The file is 566 bytes long with key length 59 (first
               bytes). The current name of the file is TRUCAT02.TR.FIS.PROD1.DF. Please see appendix E
               for file layout.




3.3     Performance Requirements
        The INBOUND interface must have the ability to process and load an average of 275 records
        between 7:00 PM – 6:00AM into the E-FIS ERP (TBD).




                                                            13
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

        The OUTBOUND interface must have the ability to process and load an average of 130,000 records
        before 4:00 PM into the E-FIS ERP (TBD).



3.4     Design Constraints
        Since the data originates from CAS, which is a mainframe based system, the data will be in a
        sequential EDBDIC file. E-FIS needs to send/receive the file from/to CAS in an “as-is” condition.
        The CAS to E-FIS interfaces needs to follow the current schedule for file processing.

3.5     Software System Attributes

        3.5.1 Reliability
              The interface shall execute within the scheduled timeframes and provide accurate data. It is
              critical that the data is available and be processed on a weekly basis. During month end and
              year end cycles, it is important that all outstanding transactions are processed before the end of
              the month or year.

        3.5.2 Availability
              E-FIS EAI (TBD) must be available between 7:00pm – 8:00pm to receive the CAS data on a
              weekly basis, based on the CAS schedule.

               E-FIS EAI (TBD) must be available before 4:00pm (based on current night net schedule) to
               send the encumbrance data from DF file on a weekly basis, based on the CAS schedule.


        3.5.3 Security
              N/A


        3.5.4 Maintainability
               The files received from CAS must be archived for a period of six months
               If a file fails during processing, a log needs to be maintained to record the error, name of
                 the file and the time and date of failure.
               E-FIS must create audit trails of transmissions sent and received.


4.0     Supporting Information

4.1     Revision History

          Version Number              Date                 Author                         Comments
                1.0                01/31/2008        Rajive Dsouza          Initial Release

                                                            14
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                       2.0         10/10/2008       Irina Bruhanski           Added E-FIS outbound interface: DF
                                                                              File




4.2       Appendices

4.2.1 Appendix A – Accounts Payable transaction Interface

          IN Record Batch and Detail File Layouts
          LRECL 500
          Copy member - IINREC
                   Column Name                      Format          Columns                Comments

 BATCH HEADER
                                                CHAR (1                         A - new transaction, C -
 DATA-TYPE                                      Byte)                 01-01     correction transaction
                                                CHAR (20
 TRANSACTION ID                                 bytes)                02-21     TRANSACTION ID.
                                                                                District responsible for a
      Batch District                            char (2 Byte)         02-03     transaction
                                                                                The date on which a batch was
      Batch Date                                char (6 bytes)        04-09     assembled (format yymmdd)
                                                                                Indicates the kinds of transactions
                                                                                in a batch
      Batch type                                char (1 Byte)         10-10     For CAS it is ‘P’
                                                                                uniquely identifies batches within
                                                                                the same batch district, date, and
      Batch number                              char (3 Byte)         11-13     type
                                                                                identifies the batch header and
                                                                                each transaction in the batch; the
                                                                                batch header is identified with
      Batch Sequential number                   char (5 Byte)         14-18     00000.
                                                                                fund split sequence number,
      Fund split seq number                     char (2 Byte)         19-20     value for header is '00'
      Duplicate indicator                       char (1 Byte)         21-21     duplicate record indicator
                                                                                fiscal month (01-13), describes
                                                                                where the month to be posted to
 FISCAL_MONTH_CODE                              NUMBER (2)            22-23     falls in the fiscal year
                                                CHAR (8
 CLAIM_SCHEDULE_NBR                             Byte)                 24-31     claim schedule number



                                                             15
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                                                CHAR (6
 filler                                         Byte)                 32-37
                                                CHAR (1
 DISBURSEMENT_METHOD_IND                        Byte)                 38-38    disbursemet method indicator
                                                                               uniquely identifies the operator
                                                CHAR (5                        who submitted the transaction for
 OPERATOR_ID                                    Byte)                 39-43    CAS it is “SRCAS”
                                                Numberic,                      Count of all detail transactions in
 ENTERED BATCH COUNT                            9(5).                 44-48    a batch
                                                numeric,
                                                9(11)v99,                      Total balance dollars of all
 ENTERED BATCH AMOUNT                           13 bytes              49-61    detailed transactions in a batch
                                                numeric,
                                                9(11)v99,                      Total balance of hours of all
 ENTERED BATCH HOURS                            13 bytes              62-74    detailed transactions in a batch
                                                Numberic,                      Count of all detail transactions in
 COMPUTED BATCH COUNT                           9(5).                 75-79    a batch
                                                numeric,
                                                9(11)v99,                      Total balance dollars of all
 COMPUTED BATCH AMOUNT                          13 bytes              80-92    detailed transactions in a batch
                                                numeric,
                                                9(11)v99,                      Total balance of hours of all
 COMPUTED BATCH HOURS                           13 bytes              93-105   detailed transactions in a batch
 filler                                         char (394)           106-500


 DETAIL RECORD
                                                CHAR (1                        A - new transaction, C -
 DATA-TYPE                                      Byte)                 01-01    correction transaction
                                                CHAR (20
 TRANSACTION ID                                 bytes)                02-21    TRANSACTION ID.
                                                                               District responsible for a
     Batch District                             char (2 Byte)         02-03    transaction
                                                                               The date on which a batch was
     Batch Date                                 char (6 bytes)        04-09    assembled (format yymmdd)
                                                                               Indicates the kinds of transactions
     Batch type                                 char (1 Byte)         10-10    in a batch
                                                                               uniquely identifies batches within
                                                                               the same batch district, date, and
     Batch number                               char (3 Byte)         11-13    type
                                                                               identifies the batch header and
                                                                               each transaction in the batch; the
                                                                               batch header is identified with
                                                                               00000, each transaction is
                                                                               numbered in the order entered
     Batch Sequential number                    char (5 Byte)         14-18    starting with 00001.
     Fund split seq number                      char (2 Byte)         19-20    fund split sequence number
     Duplicate indicator                        char (1 Byte)         21-21    duplicate record indicator
                                                                               fiscal month (01-13), describes
                                                                               where the month to be posted to
 FISCAL_MONTH_CODE                              NUMBER (2)            22-23    falls in the fiscal year


                                                             16
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                                                CHAR (8
 CLAIM_SCHEDULE_NBR                             Byte)                 24-31   claim schedule number
                                                CHAR (6
 CHECK_DATE                                     Byte)                 32-37   check's date (format yymmdd)
                                                CHAR (1
 DISBURSEMENT_METHOD_IND                        Byte)                 38-38   disbursemet method indicator
                                                CHAR (5                       uniquily identifies the operator
 OPERATOR_ID                                    Byte)                 39-43   who submitted the transaction
                                                                              transaction code indicates how a
                                                CHAR (3                       transaction should be posted
 TRANS_CODE                                     Byte)                 44-46   (debit/credit, files posted, etc)
                                                CHAR (1
 MODIFIER_IND                                   Byte)                 47-47   modifier id (if any)
                                                CHAR (1
 REVERSE_IND                                    Byte)                 48-48   reverse indicator (R or blank)
                                                CHAR (2                       Fiscal Year in which appropriated
 FUNDING_FISCAL_YEAR_CODE                       Byte)                 49-50   funds become available
                                                                              The District receiving the specific
                                                CHAR (2                       benefit of the work preformed or
 CHARGE_DISTRICT_CODE                           Byte)                 51-52   from the expenditure
                                                                              The District performing the
                                                CHAR (2                       specific task or making the
 SOURCE_DISTRICT_CODE                           Byte)                 53-54   specific expenditure
                                                                              The Unit performing the specific
                                                CHAR (4                       task or making the specific
 SOURCE_UNIT_CODE                               Byte)                 55-58   expenditure
                                                                              Expenditures Authorization
                                                                              defines the work, establishes the
                                                                              estimated cost, designates the
                                                CHAR (6                       source of funds for financing the
 EXPENDITURE_AUTHORIZATION_CODE                 Byte)                 59-64   work.
                                                CHAR (5                       Subjob further defines the project
 SUBJOB_CODE                                    Byte)                 65-69   expenditures authorization
                                                CHAR (2                       identifies the major program
 *PROGRAM_CODE                                  Byte)                 70-71   activities performed by an agency
                                                                              The second level of standardized
                                                                              departmental programs. The
                                                CHAR (2                       element must be unique within an
 *ELEMENT_CODE                                  Byte)                 72-73   agency program.
                                                                              The third level of departmental
                                                                              programs which further defines
                                                                              the elements of programs. The
                                                CHAR2 (3                      component is unique within an
 *COMPONENT_CODE                                Byte)                 74-76   element.
                                                CHAR2 (3                      A further refinement of
 *TASK_CODE                                     Byte)                 77-79   component.




                                                            17
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                                                                               Further identifies expenditures
                                                                               within an object (object further
                                                                               defines expenditures within a
                                                                               category which is the highest
                                                CHAR (6                        level of an object of expenditure
 *COE_CODE                                      Byte)                 80-85    classification.
                                                CHAR (1                        identifies segregated and
 *BUDGET_CODE                                   Byte)                 86-86    unsegregated funding
                                                CHAR (3                        A code that references (looks up)
 *APPROPRIATION_SYMBOL_CODE                     Byte)                 87-89    expanded appropriation data
                                                CHAR (3                        identifies the particular statutory
 *FUND_CODE                                     Byte)                 90-92    accounting fund
                                                                               A further breakdown of fund for
                                                CHAR (2                        specialized reporting within
 *FUND_DETAIL_CODE                              Byte)                 93-94    department
                                                CHAR (1                        Identifies the resources used to
 *FUND_SOURCE_CODE                              Byte)                 95-95    fiannce a given activity
                                                                               further defines funding of
                                                CHAR (3                        expenditures within an
 *STATUTORY_REPORTING_ACCT_CODE                 Byte)                 96-98    appropriation
                                                                               identifies other governmental
                                                                               units or departments, individuals,
                                                                               or corporations reimbursing
                                                 CHAR (5                       caltrans for work performed for
 *CONTRIBUTOR_ID                                Byte)                 99-103   their benefit.
 filler                                         char                 104-106
                                                                                County is a four-digit code
                                                                               whose first two digits are "59".
                                                                               Each county in California is
                                                                               represented by a unique code.
                                                                               Valid County codes and their
                                                                               descriptions are tabled in
                                                CHAR (4                        TRAMS Descriptor table Number
 COUNTY                                         Byte)                107-110   38.
                                                                               identifies federal grants, projects
                                                                               and other entities not provided for
                                                CHAR (6                        by other trams classification
 GRANT_CODE                                     Byte)                111-116   elements
                                                CHAR (2                        the fiscal year in which a grant is
 GRANT_PHASE_CODE                               Byte)                117-118   obligated
                                                                               a number assigned to a set of
                                                                               interdistrict clearing transactions
                                                                               which is designed to ensure that
                                                CHAR (5                        for each originating transaction
 INTER_DISTRICT_CLEARING_NBR                    Byte)                119-123   the offsetting will be made.
                                                CHAR (4
 PRIVATE_CAR_MILES_AMT                          Byte)                124-127   Private Car Miles Amount
                                                CHAR (1                        The Original Fiscal Year in which
 ORIGINAL_FISCAL_YEAR_CODE                      Byte)                128-128   a transaction was posted.
                                                CHAR (1                        identifies whether the project is
 FEDERAL_AID_ELIGIBILITY_CODE                   Byte)                129-129   eligble for federal aid


                                                            18
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                                                                               further defines expenditures
                                                                               within an object (object further
                                                                               defines expenditures within a
                                                                               category which is the highest
                                                CHAR (3                        level of the object of expenditure
 OBJECT_DETAIL_CODE                             Byte)                130-132   classification)
                                                                               the department's specifics code
                                                CHAR (3                        that further defines expenditures
 AGENCY_OBJECT_CODE                             Byte)                133-135   within an object detail
                                                                                Statewide receipt classification
                                                                               that identifies all funds received
                                                CHAR (6                        that are not considered
 SOURCE                                         bytes)               136-141   abatements
                                                                                The Agency Source code is a
                                                                               further breakdown of Receipt
                                                                               Source code. This provides
                                                CHAR (2                        additional, Caltrans-specific,
 AGENCY_SOURCE                                  bytes)               142-143   detail on the origin of revenues
                                                                               identifies the subsidiary account
                                                                               which provides a further
                                                CHAR (8                        breakdown of a given general
 SUBSIDIARY_ACCT_NBR                            Byte)                144-151   ledger account
                                                CHAR (12
 SPECIAL_DESIGNATION_CODE                       Byte)                152-163   Special Designation code
                                                                                The basic framework provides
                                                                               the control mechanism for the
                                                CHAR (4                        accountability of assets, liabilities
 GENERAL_ACCOUNT_NBR                            bytes)               164-167   and the investments of the State.
                                                CHAR (2                        The original fiscal month that a
 ORIGINAL_FISCAL_MONTH_CODE                     Byte)                168-169   transaction was posted
                                                CHAR (10                       the code that uniquely indentifies
 VENDOR_NBR                                     Byte)                170-179   each vendor
                                                                               further identifies a vendor often
                                                CHAR (2                        used to identify different location
 VENDOR_SUFFIX_CODE                             Byte)                180-181   of a given vendor.
                                                CHAR (1
 REPORTABLE_PAYMENTS_CODE                       Byte)                182-182   Reportable Payments Code
                                                CHAR (14                       number that uniquely identifies
 INVOICE_NBR                                    Byte)                183-196   each vendor
                                                                               identifies the source document
                                                CHAR (6                        from which a given transaction
 DOCUMENT_DATE                                  bytes)               197-202   was posted, YYMMDD
                                                CHAR (8
 CURRENT_DOCUMENT_NBR                           Byte)                203-210   Current Document number
                                                                               a suffix used to differentiate
                                                CHAR (2                        transactions with the same
 CURRENT_DOCUMENT_SUFFIX_NBR                    Byte)                211-212   reference document number
                                                                               a document number that refers
                                                                               back to an earlier (related)
                                                CHAR (8                        document such as an
 REFERENCE_DOCUMENT_NBR                         Byte)                213-220   encumbrance


                                                            19
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                                                                               a suffix used to differentiate
                                                CHAR (2                        transactions with the same
 REFERENCE_DOCUMENT_SUFFIX_NBR                  Byte)                221-222   reference document number
                                                CHAR (9                        the identifying number (if any)
 CHECK_NBR                                      Byte)                223-231   printed on the check
 FUND-CTL-ORD                                   CHAR (1 byte)        232-232
                                                                               the dollar amount of the
                                                NUMBER                         transaction. Format 9(13)v99 (no
 TRANS_D_AMT                                    (13,2)               233-245   sign)
                                                                               the hours amount of the
                                                NUMBER                         transaction, format 9(13)v99 (no
 TRANS_D_HRS_AMT                                (13,2)               246-258   sign).
                                                                               description of the type of
                                                CHAR (10                       payment made with the
 TYPE_PAYMENT_DESC                              Byte)                259-268   transaction
                                                CHAR (9                        Management System Activity
 MSA_CODE                                       Byte)                269-277   Code
                                                CHAR (32
 VENDOR_NAME                                    Byte)                278-309   the name of the vendor
                                                CHAR (1
 FAMILY                                         Byte)                310-310
                                                CHAR (1
 PROBLEM                                        Byte)                311-311
                                                CHAR (1
 METHOD-HOW                                     Byte)                312-312
                                                CHAR (1
 METHOD-WHY                                     Byte)                313-313
                                                CHAR (1
 METHOD-WHEN                                    Byte)                314-314
                                                CHAR (1
 MM-COUNTY                                      Byte)                315-316
                                                CHAR (1
 CBARS-ADJ-TYPE6-IND                            Byte)                317-317
                                                CHAR (39                       1st line of vendor's mailing
 VENDOR-ADDRESS-1                               bytes)               318-356   address
                                                CHAR (39                       2st line of vendor's mailing
 VENDOR-ADDRESS-2                               bytes)               357-395   address
                                                CHAR (39                       3st line of vendor's mailing
 VENDOR-ADDRES-3                                bytes)               396-434   address
                                                CHAR (19                       The city in a vendor's mailing
 VENDOR-CITY                                    bytes)               435-453   address
                                                CHSR (3
 ROUTE                                          Bytes)               454-456
                                                CHAR (5
 POSTMILE-FROM-DATA                             Byte)                457-461
                                                CHAR (5
 POSTMILE-TO-DATA                               Byte)                462-466
                                                CHAR (2                        The state name in a vendor's
 VENDOR-STATE                                   bytes)               467-468   mailing address
                                                CHAR (9                        The zip code in vendor's mailing
 VENDOR_ZIP                                     Byte)                469-477   address



                                                            20
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                                                CHAR (23
 FILLER                                         bytes)               478-500




     * Fields that are looked up currently in EA TABLE in TRAMS




        4.2.2 Appendix B – Progress Estimate Tracking System (Contract Data Layout)

     TR.PETS.CONTRACT

    00171      05 O-CONTRACT        PIC X(8).
    00172      05 FILLER            PIC X      VALUE '                         '.
    00173      05 O-ACCEPT-DATE.
    00174        10 O-ACC-MM        PIC XX.
    00175        10 FILLER          PIC X      VALUE '/'.
    00176        10 O-ACC-DD        PIC XX.
    00177        10 FILLER          PIC X      VALUE '/'.
    00178        10 O-ACC-YY        PIC XX.
    00179      05 FILLER            PIC X      VALUE '                         '.
    00180      05 O-AWARD-DATE.
    00181        10 O-AWD-MM        PIC XX.
    00182        10 FILLER          PIC X      VALUE '/'.
    00183        10 O-AWD-DD        PIC XX.
    00184        10 FILLER          PIC X     VALUE '/'.
    00185        10 O-AWD-YY        PIC XX.
    00186      05 FILLER            PIC X     VALUE '                          '.
    00187      05 O-VOUCHER-NAME-1 PIC X(30).
    00188      05 FILLER           PIC X      VALUE '                          '.
    00189      05 O-VOUCHER-NAME-2 PIC X(30).
    00190      05 FILLER           PIC X      VALUE '                          '.
    00191      05 O-VOUCHER-ADDR   PIC X(29).
    00192      05 FILLER           PIC X      VALUE '                          '.
    00193      05 O-VOUCHER-LOC    PIC X(29).
    00194      05 FILLER           PIC X      VALUE '                          '.
    00195      05 O-TOTAL-ALLOT    PIC ZZZZZZZZZZ9.99.
    00196      05 FILLER           PIC X      VALUE '                          '.
    00197      05 O-WORK-DESC      PIC X(42).
    00198      05 FILLER           PIC X      VALUE '                          '.
    00199      05 O-CONTRACT-DESC1 PIC X(42).
    00200      05 FILLER           PIC X      VALUE '                          '.

                                                            21
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

    00201      05   O-CONTRACT-DESC2               PIC X(42).
    00202      05   FILLER                         PIC X           VALUE '       '.
    00203      05   O-CONTRACT-DESC3                PIC X(42).
    00204      05   FILLER                         PIC X           VALUE '       '.
    00205      05   O-CONTRACT-DESC4                PIC X(42).
    00206      05   FILLER                         PIC X          VALUE '        '.
    00207      05   O-LOCATION-1                   PIC X(18).
    00208      05   FILLER                         PIC X          VALUE '        '.
    00209      05   O-LOCATION-2                   PIC X(18).
    00210      05   FILLER                         PIC X          VALUE '        '.
    00211      05   O-LOCATION-3                   PIC X(18).
    00212      05   FILLER                         PIC X          VALUE '        '.
    00213      05   O-LOCATION-4                   PIC X(18).



        4.2.3 Appendix C – Progress Estimate Tracking System Payment Data Layout

    TR.PETS.PAYMENT
    00197 01 PAYOUT-RECORD.
    00198   05 CONTRACT-OUT                      PIC X(8).
    00199   05 FILLER                            PIC X VALUE '              '.
    00200 05 SCHED-NUM-OUT                       PIC X(7).
    00201   05 FILLER                            PIC X VALUE '0'.
    00202   05 FILLER                            PIC X VALUE '              '.
    00203   05 EST-NUM-OUT                     PIC 9(2).
    00204 05 FILLER                            PIC X VALUE ' '.
    00205 05 PMT-TYPE-OUT                      PIC X.
    00206   05 FILLER                         PIC X VALUE ' '.
    00207   05 AMT-OUT                        PIC +9(9).99.
    00208   05 FILLER                         PIC X VALUE ' '.
    00209 05 RETENTION-OUT                    PIC +9(9).99.
    00210   05 FILLER                         PIC X VALUE ' '.
    00211 05 PER-COMP-OUT                     PIC 999 .
    00212   05 FILLER                         PIC X VALUE ' '.
    00213 05 CLMT-NAME1-OUT                   PIC X(30).
    00214   05 FILLER                         PIC X VALUE ' '.
    00215 05 CLMT-NAME2-OUT                   PIC X(30).
    00216   05 FILLER                         PIC X VALUE ' '.
    00217 05 CLMT-ADDR1-OUT                   PIC X(30).
    00218   05 FILLER                         PIC X VALUE ' '.
    00219 05 CLMT-ADDR2-OUT                   PIC X(30).



                                                            22
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008




        4.2.4 Appendix D – Accounts Payable transaction Interface IN Record Copy Member

         * * * * * * * * * * 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.           00009000
        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
        000180         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-COUNT-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             REDEFINES         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
        000370              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-COMPUTED-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-TRANSMIT-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

                                                            23
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

        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
        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).        00069000
                   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-CONTRIBUTOR            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).        00088000
                   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-REPORTABLE-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


                                                            24
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

        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-VENDOR-NAME                      PIC X(32).         00117000
                    15 FILLER                         REDEFINES 00118000
                       IN-VENDOR-NAME.                                 00119000
                       20 IN-WARRANT-NO-FROM                        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
                       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
           ***VENDOR-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).           00148000
                       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


                                                              25
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                     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-POSTMILE-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* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 00167000
        001160*                                           * 00168000
        001170*           END OF COPY MEMBER IINREC                               * 00169000
        001180*                                           * 00170000
        001190* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 00171000




        4.2.5 Appendix E – Document File Record Copy Member



 Document File (DF)
 Record Format

 Lrecl= 566
 Key Length = 59
 Copymember IDFREC
 The requested fields are
 highlighted in blue
 DF file is used in
 TRCASPAY proc,
 CAS335 program

          Column Name                  Format                 Columns                      Comments


                                                                26
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008



 KEY:                                char (59 bytes)         1-59
   district                          char (2 bytes)           1-2           the district number
                                                                            the general ledger account
     gl-account-no                   char (4 bytes)           3-6           number. Only value ‘6150’.
                                                                            identifies the source document
                                                                            from which a given transaction
     document-no                     char (8 bytes)          7-14           was posted
                                                                            used to differentiate transactions
                                                                            with the same reference
     document-suffix                 char (2 bytes)         15-16           document number
                                                                            The Fiscal year in which
                                                                            appropraited funds become
     ffy                             char (2 bytes)         17-18           available
                                                                            expenditure authorization defines
                                                                            the work, establishes the
                                                                            estimated cost, and designates
                                                                            the source of funds for fianncing
     ea                              char (6 bytes)         19-24           the work.
     subjob                          char (5 bytes)         25-29           further defines the project-ea
     fund                            char (3 bytes)         30-32           Fund
                                                                            a further breakdown of fund for
                                                                            specialized reporting within the
     fund-detail                     char (2 bytes)         33-34           department
                                                                            identifies the resources used to
     fund-source                     char (1 byte)          35-35           finance a given activity
                                                                            classifies appropriations by the
                                                                            mechanism used to make the
     method                          char (1 byte)          36-36           appropriation
                                                                            a code that references expanded
     appn-sym                        char (3 bytes)         37-39           appropriation data
                                                                            identifies the major program
     program                         char (2 bytes)         40-41           activities performed by an agency
                                                                            the 2nd level of standardized
                                                                            departmentsl pograms which
                                                                            defines the major areas within the
                                                                            program. The element must be
     element                         char (2 bytes)         42-43           unique within an agency program
                                                                            the 3rd level of standardized
                                                                            departmentsl pograms which further
                                                                            defines the elements of the
                                                                            programs, component is unique
     component                       char (3 bytes)         44-46           within an element
     task                            char (3 bytes)         47-49           a further refinement of component
                                                                            the first level of expenditure
                                                                            breakdown used to identify general
     category                        char (1 byte)          50-50           types of expenditures
                                                                            the object coded on the original
     object                          char (2 bytes)         51-52           input transaction



                                                            27
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                                                                            the object detail coded on the
     object-detail                   char (3 bytes)         53-55           original input transaction
                                                                            classifies appropriations according
     character                       char (1 byte)          56-56           to their major purpose
                                                                            identifies each appropriation or
                                                                            group of appropriations contained in
                                                                            an appropriation grid (a matrix with
                                                                            programs and funds listed on the
                                                                            axes and appropriation dollars listed
     reference                       char (3 bytes)         57-59           in the body of the matrix
                                     CHAR (213
 INFORMATION-ELEMENTS                bytes)                 60-272
                                                                            the direct/indirect transaction
                                                                            indicator source district coded on the
      i-of-d-i-trans-ind             char (1 byte)          60-60           original input transaction
                                                                            the charge district coded on the
      i-of-charge-district           char (2 bytes)         61-62           original input transaction
                                                                            source district coded on the original
      i-of-source-district           char (2 bytes)         63-64           input transaction
                                                                            source unit coded on the original
      i-of-source-unit               char (4 bytes)         65-68           input transaction
                                                                            the source function coded on the
      i-of-source-function           char (2 bytes)         69-70           original input transaction
                                                                            the source subfunction coded on the
      i-of-source-sub-function       char (2 bytes)         71-72           original input transaction
                                                                            the sourec section coded on the
      i-of-source-section            char (2 bytes)         73-74           original input transaction
                                                                            the source subsection coded on the
      i-of-source-sub-section        char (2 bytes)         75-76           original input transaction
      i-of-source-sub-sub-                                                  the source sub subsection coded on
 section                             char (2 bytes)         77-78           the original input transaction
      i-coe                          char (6 bytes)         79-84           further defines
                                                                            identifies secregated and
      i-budget-code                  char (1 byte)          85-85           unsegragated funding
                                                                            further defines funding of
      i-stat-report-acct             char (3 bytes)         86-88           expenditures within an appropriation
                                                                            the federal aid eligibility coded on
      i-of-fed-aid-elig              char (1 byte)          89-89           the original input transaction
                                                                            the category code on the original
      i-of-category                  char (1 byte)          90-90           input transaction
                                                                            the object code on the original input
      i-of-object                    char (2 bytes)         91-92           transaction
                                                                            the object detail code on the original
      i-of-object-detail             char (3 bytes)         93-95           input transaction
                                                                            the agency object code on the
      i-of-agcy-obj                  char (3 bytes)         96-98           original input transaction
                                                                            the source code on the original input
      i-of-source                    char (6 bytes)         99-104          transaction



                                                            28
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                                                                            the agency source code on the
          i-of-agcy-source              char (2 bytes)     105-106          original input transaction
                                                                            four digit code which identifies the
          i-county                      char (4 bytes)     107-110          county where thework performed
                                                                            identifies federal grants,projecta and
                                                                            other entities not provided for by
                                                                            other TRAMS classification
          i-grant-code                  char (6 bytes)     111-116          elements
                                                                            the fiscal year in which a grant is
          i-grant-phase                 char (2 bytes)     117-118          obligated
                                                                            identifies whether a record is a
                                                                            federal grant, capital project,
                                                                            reimbursable project or internal
          i-pc-grant-type               char (1 byte)      119-119          agency project
                                                                            the level of object data (category,
          i-pc-grant-obj-lvl-ind        char (1 byte)      120-120          object, obj detal, agency object)
          i-pc-cash-ctl-type-ind        char (1 byte)      121-121
          i-pc-gl-grant-level-ind       char (1 byte)      122-122
          i-pc-cc-grant-level-ind       char (1 byte)      123-123
                                                                            the special designation code on the
          i-of-special-desig-code       char (12 bytes)    124-135          original input transaction
                                                                            the federal catalog number coded on
          i-of-fed-catalog-no           char (8 bytes)     136-143          the original input transaction
          i-of-msa                      char (5 bytes)     144-152          management system activity code
                                                                            the date (if any) of the source
                                                                            document from which the
                                                                            transaction was posted , format
          i-doc-date                    char (3 bytes)     153-158          yymmdd
                                                                            the date on which the transaction
          i-create-date                 char (6 bytes)     159-164          was posted, format yymmdd
                                                                            the date on which a record is clsed
                                                                            from further posting and flagged for
                                                                            subsequent deletion from the file,
          i-close-date                  char (6 bytes)     165-170          format yymmdd
                                                                            the date by which a payment is due,
          i-due-date                    char (6 bytes)     171-176          format yymmdd.
                                                                            the date on which the a record is last
          last-process-date             char (6 bytes)     177-182          posted, format yymmdd
                                                                            a code that uniquely identifies each
          vendor-no                     char (10 bytes)    183-192          vendor
                                                                            further identifies a vendor. Often
                                                                            used to identify different location of a
          vendor-no-suffix              char (2 bytes)     193-194          given vendor.
          vendor-name                   char (40 bytes)    195-234          the name of the vendor
 filler                                 char (1 byte)      235-235
                                                                            the special designation level
                                                                            indicator on the original input
          i-d36-of-spec-desig-lvl-ind   char (1 byte)      236-236          transaction
          i-ic-allot-org-level-ind      char (1 byte)      237-237
                                                                            the date on which a batch was
          i-batch-date                  char (6 bytes)     238-243          assembled , format yymmdd

                                                            29
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008

                                                                            indicates the kinds of transaction in
          i-batch-type                     char (1 byte)     244-244        a batch
                                                                            uniquely identifies batches with the
          i-batch-no                       char (3 bytes)    245-247        same batch district, date and type.
                                                                            identifies the batch header and each
          i-batch-seq-no                   char (5 bytes)    248-252        transaction in the batch
                                                                            the subsidiary account which
                                                                            provides a further breakdown of a
          i-subsidiary-acct-no             char (8 bytes)    253-260        given general ledger account
                                                                            identifies other governmenatl units
                                                                            or departments, individuals,or
                                                                            corporations reimbursing caltrans for
          i-contributor                    char (5 bytes)    261-265        work performed for their benefit.
                                                                            the msa level indicator on the
          i-d41-of-msa-level-ind           char (1 byte)     266-266        original input transaction
 filler                                    char (3 bytes)    267-269
          i-batch-district                 char (2 bytes)    270-271        batch district
          i-gl6150-purge-ind               char (1 byte)     272-272
                                           CHAR (294
 FINANCIAL-FIELDS                          bytes)            273-566
                                           numeric,
                                           S9(11)v99
  DOCUMENT-AMOUNTS                         comp-3 (7 * 6 =                  The cumulative balance of this
 occurs 6 times                            42 bytes)         273-314        document by Financial Buckets*
                                           numeric,
                                           S9(11)v99
 ADJUSTMENT-AMOUNTS                        comp-3 (7 * 6 =                  the cumulative adjustment amount
 occurs 6 times                            42 bytes)         315-356        by Financial Buckets*
                                           numeric,
                                           S9(11)v99
 LIQUIDATION-AMOUNTS                       comp-3 (7 * 6 =                  The liquidations made to this
 occurs 6 times                            42 bytes)         357-398        document by Financial Buckets*
                                           numeric,
                                           S9(11)v99                        The cumulative balance of the
 COLLECTION-PAYMENT                        comp-3 (7 * 6 =                  expenditures made from this
 occurs 6 times                            42 bytes)         399-440        document by Financial Buckets*.
                                           numeric,
                                           S9(11)v99
 INTEREST-DISC                             comp-3 (7 * 6 =
 occurs 6 times                            42 bytes)         441-482        RESERVED FOR FUTURE USE
                                           numeric,
                                           S9(11)v99
                                           comp-3 (7 * 6 =
  RETENTION               occurs 6 times   42 bytes)         483-524        RESERVED FOR FUTURE USE
                                           numeric,
                                           S9(11)v99
                                           comp-3 (7 * 6 =
 PLAN-DOC              occurs 6 times      42 bytes)         525-566        RESERVED FOR FUTURE USE



                                                             30
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc
ERP Financial Infrastructure Software Requirements Specifications (I-014)
Version: 2.0 Date: 10/10/2008




                                                                            Project-to-Date (PTD) balance as of
 *Financial Buckets:                                 1       CM0            the current date
                                                                            The cumulative balance as of the
                                                     2       CM1            end of the prior fiscal month
                                                                            The cumulative balance as of the
                                                                            beginning of the prior fiscal
                                                     3       CM2            month.
                                                                            The cumulative balance as of the
                                                                            last prior accounting fiscal year with
                                                                            the prior fiscal year adjustments
                                                     4       PY13           (fiscal month 13 adjustments)
                                                                            The cumulative balance as of the
                                                                            last prior accounting fiscal year
                                                                            without the prior fiscal year
                                                                            adjustments (fiscal month 13
                                                     5        PY            adjustments)
                                                                            The cumualtive balance for all
                                                     6       PY1            completed prior fiscal years.




4.3     Recommendations and Considerations
        N/A




                                                            31
Path: D:\Docstoc\Working\pdf\0426d092-a7aa-49a5-90d4-2a871e3cee3d.doc

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:8
posted:9/22/2011
language:English
pages:31