| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | change number | 0;1 | NUMERIC | B | This number represents the order that each field within this amendment was changed. | |
| 1 | amendment type | 0;2 | NUMERIC | This is the numeric value for the kind of amendment the user requested. | ||
| 2 | field & file | 0;3 | FREE TEXT | In this field will be the field number follwed by a ';' then by the file number of the changed entry then separated with a : is the field number of the next level up that created this multiple. If the field is located in a subfile then the file number will become the subfile number. For example, if the BOC field in the ITEM multiple in the AMENDMENTS file - this file - is changed the data entered in this field will be '3.5;443.61:40'. | ||
| 3 | old data value | 1;0 | WORD-PROCESSING | This is the orginal value of the field found in the FIELD & FILE entry within this CHANGES subrecord. | ||
| 4 | subrecord entry | 0;4 | FREE TEXT | Even though an entry is made into the FIELD & FILE field, to find the correct entry in any subfiles any subfile internal entry numbers needs to be entered in this field. Since all CHANGES refer to this record there is no need to enter D0. For the example listed in the FIELD & FILE field only the internal number of the LINE ITEM NUMBER that the SUBACCOUNT belongs to needs to be entered here. The SUBACCOUNT field is only one level deep so there will be only one internal subrecord number needed. | ||
| 5 | date & time entered | 0;5 | DATE-TIME | This will be the date and time the user changed the entry listed in the FIELD & FILE and SUBRECORD ENTRY fields. | ||
| 6 | user | 0;6 | POINTER | 200 | This field will point to VA(200, showing the user who made this change. | |
| 7 | other file number | 0;7 | NUMERIC | This field contains the internal record number for file 441.7, the copy of the DELIVERY SCHEDULE (ORDER) file. |
Error: Invalid Global File Type: 443.6714