Name | FieldID | SpoldID, version 1 | Options | Type | Size | Multiple Occurrence | Req | Multi Language | Redundant Master Data |
---|
@originalSource | 7500 | new | | anyURI | | No | No | No | No |
| Reference to the location of the original document. Can be used to verify the data and/or to check for updates in the future. |
@majorRelease | 7501 | new | | integer | | No | Yes | No | No |
| This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The release version number is used as follows: with a major update (e.g. every second year) the major release number is increased by one (1.00, 2.00, etc.). |
@minorRelease | 7502 | new | | integer | | No | Yes | No | No |
| This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The release version number is used as follows: minor updates (corrected errors) within the period of two major updates increase the minor release version. |
@majorRevision | 7503 | new | | integer | | No | No | No | No |
| This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The revision version number is used to discern different versions during the working period until the dataset is entered into the database). The revision is generated automatically with each change made in the dataset or related file. |
@minorRevision | 7504 | new | | integer | | No | No | No | No |
| This version number can be used to make sure that the necessary master data entries are present for an activity. They are referenced by the valid... elements of the fileAttributes element in activity datasets. The revision Version number is used to discern different versions during the working period until the dataset is entered into the database). The revision is generated automatically with each change made in the dataset or related file. |
@id | 7515 | new | | TUuid | 36 | No | Yes | No | No |
| Unique identifier of the context. |
name | 7520 | new | | TString80 | 80 | No | Yes | Yes | No |
| The name of the context |
requiredContext | 7535 | new | | TRequiredContextReference | | Yes | No | No | No |
| References to master data files that are needed to open a dataset from this context. |
comment | 7540 | new | | TString32000 | 32000 | No | No | Yes | No |
| A description of the context. |
Name | FieldID | SpoldID, version 1 | Options | Type | Size | Multiple Occurrence | Req | Multi Language | Redundant Master Data |
---|
@majorRelease | 7810 | new | | integer | | No | Yes | No | No |
| This version number can be used to make sure that the necessary master data entries are present for an activity. |
@minorRelease | 7820 | new | | integer | | No | Yes | No | No |
| This version number can be used to make sure that the necessary master data entries are present for an activity. |
@majorRevision | 7830 | new | | integer | | No | No | No | No |
| This version number can be used to make sure that the necessary master data entries are present for an activity. |
@minorRevision | 7840 | new | | integer | | No | No | No | No |
| This version number can be used to make sure that the necessary master data entries are present for an activity. |
@requiredContextId | 7850 | new | | TUuid | 36 | No | Yes | No | No |
| Reference to the context of the master data file. |
| If this attribute is omitted the context of the dataset itself should be used instead. |
requiredContextName | 7855 | new | | TString80 | 80 | No | Yes | Yes | Yes |
| The name of the context referenced by field 7850. |
@requiredContextFileLocation | 7860 | new | | anyURI | | No | No | No | No |
| Optional URI reference to the directory containing the master data files of this context. |