Valid Compartments
Multiple occurrencesNoRequiredYes
Comprises a list of valid compartments and their subcompartments.
NameFieldIDSpoldID,
version 1
OptionsTypeSizeMultiple
Occurrence
ReqMulti
Language
Redundant
Master Data
@originalSource5300newanyURINoNoNoNo
Reference to the location of the original document. Can be used to verify the data and/or to check for updates in the future.
@majorRelease5301newintegerNoYesNoNo
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.).
@minorRelease5302newintegerNoYesNoNo
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.
@majorRevision5303newintegerNoNoNoNo
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.
@minorRevision5304newintegerNoNoNoNo
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.
@contextId5305newTUuid36NoNoNoNo
Reference to the context of the master data file.
contextName5306newTString8080NoNoYesYes
The name of the context referenced by field 3880.
compartment5310newTValidCompartmentYesYesNoNo
Compartments are used as the first database structuring element for activities (only structuring function) and elementary flows. This element provides hierarchical grouping only and contains no information on its own. See details in complex data type TValidCompartment.

Top

TValidCompartment
NameFieldIDSpoldID,
version 1
OptionsTypeSizeMultiple
Occurrence
ReqMulti
Language
Redundant
Master Data
@id5315newTUuid36NoYesNoNo
Unique identifier for this compartment.
name5320newTCompartmentName40NoYesYesNo
The name of the compartment.
subcompartment5330newTValidSubcompartmentYesYesNoNo
A list of subcompartments of the current compartment defined above.
comment5340newTString3200032000NoNoYesNo
Description of the compartment

Top

TValidSubcompartment
Multiple occurrencesYesRequiredYes
Subcompartments are used to further structure the compartments they are defined within.
NameFieldIDSpoldID,
version 1
OptionsTypeSizeMultiple
Occurrence
ReqMulti
Language
Redundant
Master Data
@id5350newTUuid36NoYesNoNo
Unique identifier for this subcompartment.
name5360newTCompartmentName40NoYesYesNo
Subcompartments are used as a substructure (below the database structuring element 'compartment') for activities (only structuring function) and elementary flows.
comment5370newTString3200032000NoNoYesNo
Description of the subcompartment

Top