Error Codes

Error Codes

All Error Codes are assigned a code value which has the format: XXX-YYY-ZZZ

Where:

• XXX is the product code - a three letter alpha-numeric code identifying the product that has caused the error
• YYY is the module code - a three digit numeric
• ZZZ is the identifying error code - a three digit numeric which identifies the error for the particular module

Some typical examples:

REG-201-140
EDG-004-123
000-201-140

Product Code

A three letter alpha-numeric code which identifies the product.

• REG - Fusion Registry
• EDG - Fusion Edge Server
• 000 - Un-named product

Module Code

A three digit numeric which identifies the module that caused the error. The module codes defined so far are:

• 100 - Structural Errors
• 200 - Data Errors
• 201 - Data Validation

Identifying Code

A three-digit number which identifies a unique error code in a module. No further inference of meaning need necessarily be obtainable from the identifying code i.e. It is not necessary to split a modules codes into further divisions in the identifying code, but code assigners will ensure that related codes are close to one another as far as possible.

Data Validation Errors Code

The following is the list of error codes that can be produced during Data Validation.

• 201-001 - Component '<id>' does not exist in Data Structure
• 201-002 - Data Structure Definition attribute '<id>' is not attached to the dataset, it is attached to the: <attachment level>
• 201-003 - Data Structure Definition does not define a Group with id '<id>'
• 201-004 - Observation does not report a TIME_PERIOD
• 201-005 - Syntax error in reported Time Period: '<obsTime>'
• 201-006 - Measure Dimension '<id>' is reporting value '<conceptId>' which is not a valid representation in referenced Concept Scheme
• 201-007 - The reported value '<id>' for '<conceptId>' is not valid for time period '<obsTime>'
• 201-008 - Date type not recognised : <dateType name>
• 201-051 - Missing mandatory attribute '<id>'
• 201-101 - Multiple observation values missing from reported time range '<startPeriod>' to '<endPeriod>'
• 201-131 - Observation value has been specified but OBS_STATUS enforces that this is not valid. OBS_STATUS: <obsStatusValue>
• 201-132 - Observation value has not been specified but OBS_STATUS enforces that a value must be specified. OBS_STATUS: <obsStatusValue>
• 201-161 - Invalid Date Format `<obsTime>`
• 201-162 - The Observation Date does not match the expected format for the frequency Dimension: '<freqDimensionId>'. Expected frequency format: '<format>'. Observation Date is: '<obsTime>'
• 201-181 - Component '<id>' does not exist in Data Structure
• 201-182 - Data Structure Definition does not define an Attribute with Id '<id>'
• 201-183 - Data Structure Definition component '<id>' is not an attribute it is a <structureType>
• 201-184 - Data Structure Definition attribute '<id>' is not attached to the dataset, it is attached to the: <attachmentLevel>
• 201-185 - Data Structure Definition does not define a Group with id '<groupName>'
• 201-186 - Data Structure Definition does not define Component '<id>' in Group '<groupId>'
• 201-187 - Missing value for Dimension <id>
• 201-188 - <conceptid>' does not exist in Data Structure
• 201-189 - Observation Attribute '<id>' is not defined by Data Structure: <dsdUrn>
• 201-200 - Output could not be calculated. Inputs to the calculation are '<inputs>'
• 201-201 - Output could not be calculated due to error '<errorMsg>'. Inputs to the calculation are '<inputs>'
• 201-202 - Calculation result [ is greater than or equal to | is greater than | is less than or equal to | is less than | is equal to | does not match expected output of | ] '<expectedValue>'. Inputs to the calculation are '<reportedValues>'. Inputs to the calculation are '<inputs>'