Please enable JavaScript to view this site.

Data Dictionary Data Model Data Dictionary Forums

Navigation: Catalog: DataDictionary > Schemas > Schema: Invantive > Tables

SYSTEMDOMAINCODES: Data Dictionary Code/value Domains

Domain maps of code/values.

Catalog: DataDictionary

Schema: Invantive

Alias: dmn

Label: Code/value Domains

This is a read-only view. The Data Dictionary API may not support changing the data or the Invantive UniversalSQL driver for Data Dictionary does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Data Dictionary API.

View Columns

The columns of the view SYSTEMDOMAINCODES are shown below. Each column has an SQL data type.

Name

Data Type

Label

Required

Documentation

CATALOG_NAME

string

Catalog Name

 

Catalog where the tables are contained in.

CODE

string

Code

 

Code of the domain.

ID

int32

ID

 

Unique ID of the code domain.

PROVIDER_DATA_CONTAINER_ALIAS

string(4000)

Data Container Alias

☐

Data container alias.

PROVIDER_DATA_CONTAINER_ID

string(4000)

Data Container ID

☐

Data container ID.

PROVIDER_DESCRIPTION

string(16000)

Provider Description

☑

Provider description.

PROVIDER_INSTANCE_UID

guid

Provider Instance UID

☑

Unique ID of the provider instance.

PROVIDER_NAME

string(240)

Provider Name

☑

Name of the provider.

PROVIDER_SHORT_NAME

string(240)

Provider Short Name

☑

Provider short name.

SCHEMA_NAME

string

Schema

 

Schema within the catalog where the table is contained in.

TABLE_DESCRIPTION

string

Table Description

 

Description of the contents.

TABLE_EXAMPLE

string

Table Example

 

Example of the contents.

TABLE_LABEL_PLURAL

string

Table Label Plural

 

Label of the table contents in plural form.

TABLE_NAME

string

Table Name

 

Name of the table or view.

 

18-10-2024 06:49 Version 24.0.345-PROD+4945

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer