| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | document identifier(+) | 0;1 | FREE TEXT | B | This field is used to store the FMS document identifier. The form of the document identifier is tt-sta123456 -sta789 where: tt - is the 2 alpha transaction type (ex: IV); sta - is the three digit station number (ex: 460); 123456 - is the FMS obligation/reference number (ex: I40001); 789 - is the FMS batch number (ex: 001). | |
| 1 | system | 0;2 | SET OF CODES | F:FMS | This field is used to store the system which created the code sheet. Currently the only system which interfaces to the stack file is the FMS code sheets. | |
| 2 | date@time created | 0;3 | DATE-TIME | This field is used to store the date and time the code sheet was entered into the stack file for transmission. | ||
| 3 | status | 0;4 | SET OF CODES | Q:QUEUED FOR TRANSMISSION M:MARKED FOR IMMEDIATE TRANSMISSION BY EVENT T:TRANSMITTED E:ERROR DURING TRANSMISSION A:ACCEPTED BY FMS R:REJECTED BY FMS F:FINAL - NO FURTHER ACTIVITY ALLOWED | AS | This is the status of the stack file entry. Status's range from: Q: queued for transmission M: marked for immediate transmission T: transmitted to Austin E: error in transmission A: accepted by FMS R: rejected by FMS F: final - no further activity allowed |
| 4 | description of event | 1;1 | FREE TEXT | This field is used to store the description of the event which caused the code sheet to be created. The description is for informational purposes and will appear on the Stack Status Report. | ||
| 4.1 | user comments | 1;3 | FREE TEXT | This field is used to store free text comments which can be entered by the user and will appear on the Stack Status Report. | ||
| 5 | segment (entry in file 2101.2) | 0;5 | FREE TEXT | This field is used to store the free text segment entry from file 2101.2 which was used to create the code sheet. | ||
| 6 | errors | 1;2 | FREE TEXT | This field is used to store any errors which occurred during the transmission of the code sheet. If an error occurs the stack status will be set to 'E'rror and the ERRORS field will store the description of the error. The user can use the Stack Status Report to display code sheets which resulted in errors during transmission. Examples of errors would be no code sheets to transmit, unable to create a mailman message, etc. | ||
| 7 | manual or automatic | 0;6 | SET OF CODES | M:MANUAL A:AUTOMATIC | This field is used to indicate if the stack file code sheet was manually created or automatically created. For the accept/reject processing, only code sheets which have been automatically created and rejected should be regenerated and retransmitted by the event code. | |
| 8 | document lookup key | 0;7 | FREE TEXT | KEY | This field stores an option document lookup key that can be used to find a specific document in generic code sheets. For example, if a package sends a monthly code sheet, it could enter the key as SV-3001200 for SV documents sent for the month 12/2000. | |
| 10 | code sheet | 10;0 | WORD-PROCESSING | This field is used to store the actual code sheet which will be transmitted. | ||
| 11 | size of code sheet | 11;1 | NUMERIC | This field is used to store the size of the code sheet. The field is used internally by the Generic Code Sheet Package during transmission. When the code sheets are transmitted from the stack file, the code sheets are grouped into mail messages depending on the size of the code sheet. | ||
| 11.2 | checksum | 11;2 | NUMERIC | This field is used to store the checksum of the automatically created code sheet. | ||
| 11.3 | hold date | 11;3 | DATE-TIME | This field stores the date the code sheet will be transmitted on. | ||
| 20 | transmitted mail messages | 20;0 | MULTIPLE | 2100.12 | This field is used to store the mail message number which was used for the transmission of the code sheet. This field is multiple for large code sheets (greater then 30K) which require more than one mail message for transmission. | |
| 21 | old transmitted mail messages | 21;0 | MULTIPLE | 2100.121 | This field is used to store the old mail messages which were used to transmit the stack file entry. When the stack entry is retransmitted, this field is used to keep a history of previous mail messages used for transmission. | |
| 25 | event accept/reject code | 25;E1,245 | FREE TEXT | This field stores the mumps code which is executed when processing accept or reject messages. This field is not editable through VA FileMan. It is set in the routine GECSSDCT. | ||
| 26 | special parameters | 26;1 | FREE TEXT | This field is used to store any special parameters required to rebuild the code sheet. |
Not Referenced