Data Compatibility - Revision history

User at 19:27, 14 March 2023

2023-03-14T19:27:25Z

User at 19:09, 14 March 2023

2023-03-14T19:09:15Z

User at 18:03, 12 January 2023

2023-01-12T18:03:15Z

User at 15:30, 26 October 2022

2022-10-26T15:30:12Z

User at 15:50, 5 May 2021

2021-05-05T15:50:46Z

User at 17:40, 7 April 2021

2021-04-07T17:40:56Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T15:07:52Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User at 19:59, 18 December 2019

2019-12-18T19:59:16Z

User at 19:58, 18 December 2019

2019-12-18T19:58:50Z

User at 17:39, 16 December 2019

2019-12-16T17:39:16Z

@@ Line 34: / Line 34: @@
 **Data reference variables can be compared with all data reference variables and object reference variables can be compared with all object reference variables.
 As a rule, data reference variables can only be used with data reference variables and object reference variables can be used only with object reference variables. No conversions take place between reference variables. They are either passed as unconverted reference variables, assigned to each other, compared with each other, or no action at all takes place.
@@ Line 42: / Line 60: @@
 == References ==
 <references/>

@@ Line 1: / Line 1: @@
-'''Data Compatibility''' is an IT innovation that provides [[Data Integration|integrated data]] throughout an organization, among organizations and across industries. Data compatibility is so superior to traditional data integration methods that data compatibility is the inevitable replacement for data integration methods. Compatible data is integrated data. Data is automatically integrated from the time it’s initially stored and it will remain integrated until it's deleted. Any data from a compatible data system is integrated with data from any other compatible data system. Unlike traditional data integration methods, there is no need to spend exorbitant amounts of money, time and effort moving and transforming data. Data compatibility creates untold opportunities for collaboration, both within and outside your organization.<ref>Defining Data Compatibility [https://maxxphase.com/data-compatibility/what-is-data-compatibility/ Maxxphase]</ref>
+== What is Data Compatibility? ==
-All data arise within a particular context and often as a result of a specific question being asked. That is all well and good until we attempt to use that same data to answer a different question within a different context. When you match an existing dataset with a new question, you have to ask if the original context in which the data were collected is compatible with the new question and the new context. If there is context compatibility, then it is often reasonable to move forward. If not, then you either have to stop or come up with some statistical principle or assumption that makes the two contexts compatible. Good data analysts will often do this in their heads quickly and may not even realize they are doing it. Understanding context compatibility is increasingly important as data science and the analysis of existing datasets continues to take off. Existing datasets all come from somewhere and it’s important to the analyst to know where that is and whether it’s compatible with where they’re going. If there is an incompatibility between the two contexts, which in my experience is almost always the case, then any assumption or statistical principle invoked will likely introduce uncertainty into the final results. That uncertainty should at least be communicated to the audience, if not formally considered in the analysis. In some cases, the original context of the data and the context of the new analysis will be so incompatible that it’s not worth using the data to answer the new question. Explicit recognition of this problem can save a lot of wasted time analyzing a dataset that is ultimately a poor fit for answering a given question.<ref>Compatible Data in Context [https://simplystatistics.org/2018/05/24/context-compatibility-in-data-analysis/ Simply Stats]</ref>
+All data arise within a particular context and often as a result of a specific question being asked. That is all well and good until we attempt to use that same data to answer a different question within a different context. When you match an existing dataset with a new question, you have to ask if the original context in which the data were collected is compatible with the new question and the new context. If there is context compatibility, then it is often reasonable to move forward. If not, then you either have to stop or come up with some statistical principle or assumption that makes the two contexts compatible. Good data analysts will often do this in their heads quickly and may not even realize they are doing it. Understanding context compatibility is increasingly important as data science and the analysis of existing datasets continue to take off. Existing datasets all come from somewhere and it’s important to the analyst to know where that is and whether it’s compatible with where they’re going. If there is an incompatibility between the two contexts, which in my experience is almost always the case, then any assumption or statistical principle invoked will likely introduce uncertainty into the final results. That uncertainty should at least be communicated to the audience, if not formally considered in the analysis. In some cases, the original context of the data and the context of the new analysis will be so incompatible that it’s not worth using the data to answer the new question. Explicit recognition of this problem can save a lot of wasted time analyzing a dataset that is ultimately a poor fit for answering a given question.<ref>[https://simplystatistics.org/2018/05/24/context-compatibility-in-data-analysis/ Compatible Data in Context]</ref>
-'''Compatible Data Types<ref>Compatible Data Types [https://help.sap.com/doc/abapdocu_751_index_htm/7.51/en-us/abencompatibility.htm SAP]</ref>'''<br />
+== Compatible Data Types<ref>[https://help.sap.com/doc/abapdocu_751_index_htm/7.51/en-us/abencompatibility.htm Compatible Data Types]</ref> ==
 The compatibility of two data types (except reference types) is based on their technical type attributes. It is the basis for type checking in assignments to field symbols or when assigning actual parameters to formal parameters.
 In the case of value assignments and comparisons between data objects (except reference variables), compatibility also determines whether a conversion has to be performed or not. In the case of reference types with data objects (reference variables) that have a dynamic type as well as the static type, then compatibility, which is based entirely on technical type attributes, is not sufficient.
@@ Line 13: / Line 14: @@
 ***The number of decimal places (in the case of the type p)
 **In the case of structured types, the technical type attribute is as follows:
-**The layout of components: The layout of structured types does not only refer to the sequence of elementary components in memory, but also to the combination of components with substructures and whether a substructure is a boxed component. The names of the components and of the semantic attributes defined in ABAP Dictionary, such as conversion routines or documentation, however, are not important. In the case of compatible structures, all components are compatible in pairs. This applies recursively down to the level of elementary data types.
+**The layout of components: The layout of structured types does not only refer to the sequence of elementary components in memory but also to the combination of components with substructures and whether a substructure is a boxed component. The names of the components and of the semantic attributes defined in ABAP Dictionary, such as conversion routines or documentation, however, are not important. In the case of compatible structures, all components are compatible in pairs. This applies recursively down to the level of elementary data types.
 If two structures are both constructed identically but different substructures are declared as boxed components, the structures are not compatible.
 **In the case of table types, the technical type attributes are as follows: (In the case of compatible internal tables, the row types are compatible and the table category and table key match. Other attributes, such as the initial memory requirement, are not important.)
@@ Line 26: / Line 27: @@
 Note: The types specified here are not compatible with one another. For example, an elementary data type is never compatible with a structure, even if the structure has only one component. Statement TYPES cannot be used to define different enumerated types with the same technical type properties. Even data types constructed with RTTC methods exactly like an existing enumerated type are not compatible with it. An enumerated type defined by direct or indirect reference (including RTTI) to an existing enumerated type, is compatible with it however.
 *Generic Data Types: A non-generic data type (not a reference type) is compatible with a generic data type if its technical attributes are covered by the generic data type.
-*Reference Types: A reference type is the static type of reference variables and determines to which objects they can point. At runtime, reference variables also have a dynamic type determined by the type of the object pointed to by a reference variable. The dynamic type may be more specialized than the static type. For this reason, the rules for typing checks, assignments, and comparisons cannot be covered by a compatibility concept based entirely on the technical attributes of the static type. Instead, the following three points show how reference types can be used together:
+*Reference Types: A reference type is the static type of reference variable and determines to which objects they can point. At runtime, reference variables also have a dynamic type determined by the type of object pointed to by a reference variable. The dynamic type may be more specialized than the static type. For this reason, the rules for typing checks, assignments, and comparisons cannot be covered by a compatibility concept based entirely on the technical attributes of the static type. Instead, the following three points show how reference types can be used together:
 **When typings are checked, the following is possible:
-***A reference variable can be passed to a formal parameter typed as a reference variable, provided that the type of the formal parameter is more general or equal to the type of the reference variable (known as an up cast) and the formal parameter cannot be changed within the procedure.
+***A reference variable can be passed to a formal parameter typed as a reference variable, provided that the type of the formal parameter is more general or equal to the type of the reference variable (known as an upcast) and the formal parameter cannot be changed within the procedure.
 ***A reference variable can be assigned to a field symbol typed as a reference variable, provided that the reference types are identical.
-**Assignments between reference variables can be carried out by using an up cast or a down cast.
+**Assignments between reference variables can be carried out by using an upcast or a downcast.
 **Data reference variables can be compared with all data reference variables and object reference variables can be compared with all object reference variables.
 As a rule, data reference variables can only be used with data reference variables and object reference variables can be used only with object reference variables. No conversions take place between reference variables. They are either passed as unconverted reference variables, assigned to each other, compared with each other, or no action at all takes place.
-===See Also===
+== See Also ==
-<div style="column-count:2;-moz-column-count:4;-webkit-column-count:4">
+[[Data]]
 == References ==
 <references/>

@@ Line 1: / Line 1: @@
-'''Data Compatibility''' is an IT [[Innovation|innovation]] that provides [[Data Integration|integrated data]] throughout an [[Organization|organization]], among organizations and across [[Industry|industries]]. Data compatibility is so superior to traditional data integration methods that data compatibility is the inevitable replacement for [[Data Integration|data integration]] methods. Compatible data is integrated data. Data is automatically integrated from the time it’s initially stored and it will remain integrated until it's deleted. Any [[Data|data]] from a compatible data [[system]] is integrated with data from any other compatible data system. Unlike traditional data integration methods, there is no need to spend exorbitant amounts of money, time and effort moving and transforming data. Data compatibility creates untold opportunities for [[collaboration]], both within and outside your [[organization]].<ref>Defining Data Compatibility [https://maxxphase.com/data-compatibility/what-is-data-compatibility/ Maxxphase]</ref>
+'''Data Compatibility''' is an IT innovation that provides [[Data Integration|integrated data]] throughout an organization, among organizations and across industries. Data compatibility is so superior to traditional data integration methods that data compatibility is the inevitable replacement for data integration methods. Compatible data is integrated data. Data is automatically integrated from the time it’s initially stored and it will remain integrated until it's deleted. Any data from a compatible data system is integrated with data from any other compatible data system. Unlike traditional data integration methods, there is no need to spend exorbitant amounts of money, time and effort moving and transforming data. Data compatibility creates untold opportunities for collaboration, both within and outside your organization.<ref>Defining Data Compatibility [https://maxxphase.com/data-compatibility/what-is-data-compatibility/ Maxxphase]</ref>
-All data arise within a particular context and often as a result of a specific question being asked. That is all well and good until we attempt to use that same data to answer a different question within a different context. When you match an existing dataset with a new question, you have to ask if the original context in which the data were collected is compatible with the new question and the new context. If there is context compatibility, then it is often reasonable to move forward. If not, then you either have to stop or come up with some statistical [[principle]] or assumption that makes the two contexts compatible. Good data analysts will often do this in their heads quickly and may not even realize they are doing it. Understanding context compatibility is increasingly important as data science and the analysis of existing datasets continues to take off. Existing datasets all come from somewhere and it’s important to the analyst to know where that is and whether it’s compatible with where they’re going. If there is an incompatibility between the two contexts, which in my experience is almost always the case, then any assumption or statistical principle invoked will likely introduce uncertainty into the final results. That uncertainty should at least be communicated to the audience, if not formally considered in the analysis. In some cases, the original context of the data and the context of the new analysis will be so incompatible that it’s not worth using the data to answer the new question. Explicit recognition of this problem can save a lot of wasted time analyzing a dataset that is ultimately a poor fit for answering a given question.<ref>Compatible Data in Context [https://simplystatistics.org/2018/05/24/context-compatibility-in-data-analysis/ Simply Stats]</ref>
+All data arise within a particular context and often as a result of a specific question being asked. That is all well and good until we attempt to use that same data to answer a different question within a different context. When you match an existing dataset with a new question, you have to ask if the original context in which the data were collected is compatible with the new question and the new context. If there is context compatibility, then it is often reasonable to move forward. If not, then you either have to stop or come up with some statistical principle or assumption that makes the two contexts compatible. Good data analysts will often do this in their heads quickly and may not even realize they are doing it. Understanding context compatibility is increasingly important as data science and the analysis of existing datasets continues to take off. Existing datasets all come from somewhere and it’s important to the analyst to know where that is and whether it’s compatible with where they’re going. If there is an incompatibility between the two contexts, which in my experience is almost always the case, then any assumption or statistical principle invoked will likely introduce uncertainty into the final results. That uncertainty should at least be communicated to the audience, if not formally considered in the analysis. In some cases, the original context of the data and the context of the new analysis will be so incompatible that it’s not worth using the data to answer the new question. Explicit recognition of this problem can save a lot of wasted time analyzing a dataset that is ultimately a poor fit for answering a given question.<ref>Compatible Data in Context [https://simplystatistics.org/2018/05/24/context-compatibility-in-data-analysis/ Simply Stats]</ref>
 '''Compatible Data Types<ref>Compatible Data Types [https://help.sap.com/doc/abapdocu_751_index_htm/7.51/en-us/abencompatibility.htm SAP]</ref>'''<br />
 The compatibility of two data types (except reference types) is based on their technical type attributes. It is the basis for type checking in assignments to field symbols or when assigning actual parameters to formal parameters.
-In the case of [[value]] assignments and comparisons between data objects (except reference variables), compatibility also determines whether a conversion has to be performed or not. In the case of reference types with data objects (reference variables) that have a dynamic type as well as the static type, then compatibility, which is based entirely on technical type attributes, is not sufficient.
+In the case of value assignments and comparisons between data objects (except reference variables), compatibility also determines whether a conversion has to be performed or not. In the case of reference types with data objects (reference variables) that have a dynamic type as well as the static type, then compatibility, which is based entirely on technical type attributes, is not sufficient.
 *Non-Generic Data Types (Except Reference Types): Two non-generic data types (not reference types) and data types that contain reference types as components are compatible if all their technical type attributes match.
 **In the case of elementary data type all technical type attributes match. The technical type attributes are as follows:
@@ Line 15: / Line 15: @@
 **The layout of components: The layout of structured types does not only refer to the sequence of elementary components in memory, but also to the combination of components with substructures and whether a substructure is a boxed component. The names of the components and of the semantic attributes defined in ABAP Dictionary, such as conversion routines or documentation, however, are not important. In the case of compatible structures, all components are compatible in pairs. This applies recursively down to the level of elementary data types.
 If two structures are both constructed identically but different substructures are declared as boxed components, the structures are not compatible.
-**In the case of table types, the technical type attributes are as follows: (In the case of compatible internal tables, the row types are compatible and the table category and table key match. Other attributes, such as the initial memory [[requirement]], are not important.)
+**In the case of table types, the technical type attributes are as follows: (In the case of compatible internal tables, the row types are compatible and the table category and table key match. Other attributes, such as the initial memory requirement, are not important.)
 ***The row type
 ***Table category
@@ Line 37: / Line 37: @@
 ===See Also===
 <div style="column-count:2;-moz-column-count:4;-webkit-column-count:4">
-*[[Data]]
 </div>

@@ Line 37: / Line 37: @@
 ===See Also===
 <div style="column-count:2;-moz-column-count:4;-webkit-column-count:4">
-[[Data]]<br />
+*[[Data]]
-[[Data Access]]<br />
+*[[Data Access]]
-[[Data Analysis]]<br />
+*[[Data Analysis]]
-[[Data Analytics]]<br />
+*[[Data Analytics]]
-[[Data Architecture]]<br />
+*[[Data Architecture]]
-[[Data Asset Framework (DAF)]]<br />
+*[[Data Asset Framework (DAF)]]
-[[Data Buffer]]<br />
+*[[Data Buffer]]
-[[Data Center]]<br />
+*[[Data Center]]
-[[Data Center Infrastructure]]<br />
+*[[Data Center Infrastructure]]
-[[Data Center Infrastructure Management (DCIM)]]<br />
+*[[Data Center Infrastructure Management (DCIM)]]
-[[Data Cleansing]]<br />
+*[[Data Cleansing]]
-[[Big Data]]<br />
+*[[Data Governance]]
-[[Big Data Integration]]<br />
+*[[Data Integration]]
-[[Big Data Maturity Model (BDMM)]]<br />
+*[[Data Management]]
-[[Metadata]]<br />
+*[[Data Mining]]
-[[Data Collection]]<br />
+*[[Data Monitoring]]
-[[Data Compatibility]]<br />
+*[[Data Munging]]
-[[Data Consolidation]]<br />
+*[[Data Portability]]
-[[Data Deduplication]]<br />
+*[[Data Quality]]
-[[Data Delivery Platform (DDP)]]<br />
+*[[Data Reference Model (DRM)]]
-[[Data Description (Definition) Language (DDL)]]<br />
+*[[Data Security]]
-[[Data Dictionary]]<br />
+*[[Data Transformation]]
-[[Data Discovery]]<br />
+*[[Data Visualization]]
-[[Data Driven Organization]]<br />
+*[[Data Warehouse]]
 </div>

← Older revision		Revision as of 15:50, 5 May 2021
Line 1:		Line 1:
	'''Data Compatibility''' is an IT [[Innovation\|innovation]] that provides [[Data Integration\|integrated data]] throughout an [[Organization\|organization]], among organizations and across [[Industry\|industries]]. Data compatibility is so superior to traditional data integration methods that data compatibility is the inevitable replacement for [[Data Integration\|data integration]] methods. Compatible data is integrated data. Data is automatically integrated from the time it’s initially stored and it will remain integrated until it's deleted. Any [[Data\|data]] from a compatible data [[system]] is integrated with data from any other compatible data system. Unlike traditional data integration methods, there is no need to spend exorbitant amounts of money, time and effort moving and transforming data. Data compatibility creates untold opportunities for [[collaboration]], both within and outside your [[organization]].<ref>Defining Data Compatibility [https://maxxphase.com/data-compatibility/what-is-data-compatibility/ Maxxphase]</ref>		'''Data Compatibility''' is an IT [[Innovation\|innovation]] that provides [[Data Integration\|integrated data]] throughout an [[Organization\|organization]], among organizations and across [[Industry\|industries]]. Data compatibility is so superior to traditional data integration methods that data compatibility is the inevitable replacement for [[Data Integration\|data integration]] methods. Compatible data is integrated data. Data is automatically integrated from the time it’s initially stored and it will remain integrated until it's deleted. Any [[Data\|data]] from a compatible data [[system]] is integrated with data from any other compatible data system. Unlike traditional data integration methods, there is no need to spend exorbitant amounts of money, time and effort moving and transforming data. Data compatibility creates untold opportunities for [[collaboration]], both within and outside your [[organization]].<ref>Defining Data Compatibility [https://maxxphase.com/data-compatibility/what-is-data-compatibility/ Maxxphase]</ref>

−	All data arise within a particular context and often as a result of a specific question being asked. That is all well and good until we attempt to use that same data to answer a different question within a different context. When you match an existing dataset with a new question, you have to ask if the original context in which the data were collected is compatible with the new question and the new context. If there is context compatibility, then it is often reasonable to move forward. If not, then you either have to stop or come up with some statistical [[principle]] or assumption that makes the two contexts compatible. Good data analysts will often do this in their heads quickly and may not even realize they are doing it. Understanding context compatibility is increasingly important as data science and the analysis of existing datasets continues to take off. Existing datasets all come from somewhere and it’s important to the analyst to know where that is and whether it’s compatible with where they’re going. If there is an ~~imcompatibility~~ between the two contexts, which in my experience is almost always the case, then any assumption or statistical principle invoked will likely introduce uncertainty into the final results. That uncertainty should at least be communicated to the audience, if not formally considered in the analysis. In some cases, the original context of the data and the context of the new analysis will be so incompatible that it’s not worth using the data to answer the new question. Explicit recognition of this problem can save a lot of wasted time analyzing a dataset that is ultimately a poor fit for answering a given question.<ref>Compatible Data in Context [https://simplystatistics.org/2018/05/24/context-compatibility-in-data-analysis/ Simply Stats]</ref>	+	All data arise within a particular context and often as a result of a specific question being asked. That is all well and good until we attempt to use that same data to answer a different question within a different context. When you match an existing dataset with a new question, you have to ask if the original context in which the data were collected is compatible with the new question and the new context. If there is context compatibility, then it is often reasonable to move forward. If not, then you either have to stop or come up with some statistical [[principle]] or assumption that makes the two contexts compatible. Good data analysts will often do this in their heads quickly and may not even realize they are doing it. Understanding context compatibility is increasingly important as data science and the analysis of existing datasets continues to take off. Existing datasets all come from somewhere and it’s important to the analyst to know where that is and whether it’s compatible with where they’re going. If there is an incompatibility between the two contexts, which in my experience is almost always the case, then any assumption or statistical principle invoked will likely introduce uncertainty into the final results. That uncertainty should at least be communicated to the audience, if not formally considered in the analysis. In some cases, the original context of the data and the context of the new analysis will be so incompatible that it’s not worth using the data to answer the new question. Explicit recognition of this problem can save a lot of wasted time analyzing a dataset that is ultimately a poor fit for answering a given question.<ref>Compatible Data in Context [https://simplystatistics.org/2018/05/24/context-compatibility-in-data-analysis/ Simply Stats]</ref>

← Older revision		Revision as of 19:59, 18 December 2019
Line 2:		Line 2:

	All data arise within a particular context and often as a result of a specific question being asked. That is all well and good until we attempt to use that same data to answer a different question within a different context. When you match an existing dataset with a new question, you have to ask if the original context in which the data were collected is compatible with the new question and the new context. If there is context compatibility, then it is often reasonable to move forward. If not, then you either have to stop or come up with some statistical principle or assumption that makes the two contexts compatible. Good data analysts will often do this in their heads quickly and may not even realize they are doing it. Understanding context compatibility is increasingly important as data science and the analysis of existing datasets continues to take off. Existing datasets all come from somewhere and it’s important to the analyst to know where that is and whether it’s compatible with where they’re going. If there is an imcompatibility between the two contexts, which in my experience is almost always the case, then any assumption or statistical principle invoked will likely introduce uncertainty into the final results. That uncertainty should at least be communicated to the audience, if not formally considered in the analysis. In some cases, the original context of the data and the context of the new analysis will be so incompatible that it’s not worth using the data to answer the new question. Explicit recognition of this problem can save a lot of wasted time analyzing a dataset that is ultimately a poor fit for answering a given question.<ref>Compatible Data in Context [https://simplystatistics.org/2018/05/24/context-compatibility-in-data-analysis/ Simply Stats]</ref>		All data arise within a particular context and often as a result of a specific question being asked. That is all well and good until we attempt to use that same data to answer a different question within a different context. When you match an existing dataset with a new question, you have to ask if the original context in which the data were collected is compatible with the new question and the new context. If there is context compatibility, then it is often reasonable to move forward. If not, then you either have to stop or come up with some statistical principle or assumption that makes the two contexts compatible. Good data analysts will often do this in their heads quickly and may not even realize they are doing it. Understanding context compatibility is increasingly important as data science and the analysis of existing datasets continues to take off. Existing datasets all come from somewhere and it’s important to the analyst to know where that is and whether it’s compatible with where they’re going. If there is an imcompatibility between the two contexts, which in my experience is almost always the case, then any assumption or statistical principle invoked will likely introduce uncertainty into the final results. That uncertainty should at least be communicated to the audience, if not formally considered in the analysis. In some cases, the original context of the data and the context of the new analysis will be so incompatible that it’s not worth using the data to answer the new question. Explicit recognition of this problem can save a lot of wasted time analyzing a dataset that is ultimately a poor fit for answering a given question.<ref>Compatible Data in Context [https://simplystatistics.org/2018/05/24/context-compatibility-in-data-analysis/ Simply Stats]</ref>
		+

	'''Compatible Data Types<ref>Compatible Data Types [https://help.sap.com/doc/abapdocu_751_index_htm/7.51/en-us/abencompatibility.htm SAP]</ref>'''<br />		'''Compatible Data Types<ref>Compatible Data Types [https://help.sap.com/doc/abapdocu_751_index_htm/7.51/en-us/abencompatibility.htm SAP]</ref>'''<br />

@@ Line 35: / Line 35: @@
 ===See Also===
 [[Data Access]]<br />
 [[Data Analysis]]<br />
@@ Line 117: / Line 118: @@
 [[Database Marketing]]<br />
 [[Database Schema]]<br />
-[[Database System]]
+[[Database System]]<br />
 ===References===

← Older revision		Revision as of 17:39, 16 December 2019
Line 1:		Line 1:
	'''Data Compatibility''' is an IT [[Innovation\|innovation]] that provides [[Data Integration\|integrated data]] throughout an [[Organization\|organization]], among organizations and across [[Industry\|industries]]. Data compatibility is so superior to traditional data integration methods that data compatibility is the inevitable replacement for [[Data Integration\|data integration]] methods. Compatible data is integrated data. Data is automatically integrated from the time it’s initially stored and it will remain integrated until it's deleted. Any data from a compatible data system is integrated with data from any other compatible data system. Unlike traditional data integration methods, there is no need to spend exorbitant amounts of money, time and effort moving and transforming data. Data compatibility creates untold opportunities for collaboration, both within and outside your organization.<ref>Defining Data Compatibility [https://maxxphase.com/data-compatibility/what-is-data-compatibility/ Maxxphase]</ref>		'''Data Compatibility''' is an IT [[Innovation\|innovation]] that provides [[Data Integration\|integrated data]] throughout an [[Organization\|organization]], among organizations and across [[Industry\|industries]]. Data compatibility is so superior to traditional data integration methods that data compatibility is the inevitable replacement for [[Data Integration\|data integration]] methods. Compatible data is integrated data. Data is automatically integrated from the time it’s initially stored and it will remain integrated until it's deleted. Any data from a compatible data system is integrated with data from any other compatible data system. Unlike traditional data integration methods, there is no need to spend exorbitant amounts of money, time and effort moving and transforming data. Data compatibility creates untold opportunities for collaboration, both within and outside your organization.<ref>Defining Data Compatibility [https://maxxphase.com/data-compatibility/what-is-data-compatibility/ Maxxphase]</ref>
		+
		+	All data arise within a particular context and often as a result of a specific question being asked. That is all well and good until we attempt to use that same data to answer a different question within a different context. When you match an existing dataset with a new question, you have to ask if the original context in which the data were collected is compatible with the new question and the new context. If there is context compatibility, then it is often reasonable to move forward. If not, then you either have to stop or come up with some statistical principle or assumption that makes the two contexts compatible. Good data analysts will often do this in their heads quickly and may not even realize they are doing it. Understanding context compatibility is increasingly important as data science and the analysis of existing datasets continues to take off. Existing datasets all come from somewhere and it’s important to the analyst to know where that is and whether it’s compatible with where they’re going. If there is an imcompatibility between the two contexts, which in my experience is almost always the case, then any assumption or statistical principle invoked will likely introduce uncertainty into the final results. That uncertainty should at least be communicated to the audience, if not formally considered in the analysis. In some cases, the original context of the data and the context of the new analysis will be so incompatible that it’s not worth using the data to answer the new question. Explicit recognition of this problem can save a lot of wasted time analyzing a dataset that is ultimately a poor fit for answering a given question.<ref>Compatible Data in Context [https://simplystatistics.org/2018/05/24/context-compatibility-in-data-analysis/ Simply Stats]</ref>
		+
		+	'''Compatible Data Types<ref>Compatible Data Types [https://help.sap.com/doc/abapdocu_751_index_htm/7.51/en-us/abencompatibility.htm SAP]</ref>'''<br />
		+	The compatibility of two data types (except reference types) is based on their technical type attributes. It is the basis for type checking in assignments to field symbols or when assigning actual parameters to formal parameters.
		+	In the case of value assignments and comparisons between data objects (except reference variables), compatibility also determines whether a conversion has to be performed or not. In the case of reference types with data objects (reference variables) that have a dynamic type as well as the static type, then compatibility, which is based entirely on technical type attributes, is not sufficient.
		+	*Non-Generic Data Types (Except Reference Types): Two non-generic data types (not reference types) and data types that contain reference types as components are compatible if all their technical type attributes match.
		+	**In the case of elementary data type all technical type attributes match. The technical type attributes are as follows:
		+	***The predefined ABAP type
		+	***The length (in the case of the types c, n, p, and x)
		+	***The number of decimal places (in the case of the type p)
		+	**In the case of structured types, the technical type attribute is as follows:
		+	**The layout of components: The layout of structured types does not only refer to the sequence of elementary components in memory, but also to the combination of components with substructures and whether a substructure is a boxed component. The names of the components and of the semantic attributes defined in ABAP Dictionary, such as conversion routines or documentation, however, are not important. In the case of compatible structures, all components are compatible in pairs. This applies recursively down to the level of elementary data types.
		+	If two structures are both constructed identically but different substructures are declared as boxed components, the structures are not compatible.
		+	**In the case of table types, the technical type attributes are as follows: (In the case of compatible internal tables, the row types are compatible and the table category and table key match. Other attributes, such as the initial memory requirement, are not important.)
		+	***The row type
		+	***Table category
		+	***Table key
		+	**In the case of mesh types, the technical type attributes are as follows:
		+	***The layout of nodes (including the node names)
		+	***The associations (defined by ON conditions) of every component, including names and the table key used
		+	**In the case of enumerated types, the technical type attributes are as follows:
		+	***All properties of the enumerated type: Every enumerated type is unique and only compatible with itself.
		+	Note: The types specified here are not compatible with one another. For example, an elementary data type is never compatible with a structure, even if the structure has only one component. Statement TYPES cannot be used to define different enumerated types with the same technical type properties. Even data types constructed with RTTC methods exactly like an existing enumerated type are not compatible with it. An enumerated type defined by direct or indirect reference (including RTTI) to an existing enumerated type, is compatible with it however.
		+	*Generic Data Types: A non-generic data type (not a reference type) is compatible with a generic data type if its technical attributes are covered by the generic data type.
		+	*Reference Types: A reference type is the static type of reference variables and determines to which objects they can point. At runtime, reference variables also have a dynamic type determined by the type of the object pointed to by a reference variable. The dynamic type may be more specialized than the static type. For this reason, the rules for typing checks, assignments, and comparisons cannot be covered by a compatibility concept based entirely on the technical attributes of the static type. Instead, the following three points show how reference types can be used together:
		+	**When typings are checked, the following is possible:
		+	***A reference variable can be passed to a formal parameter typed as a reference variable, provided that the type of the formal parameter is more general or equal to the type of the reference variable (known as an up cast) and the formal parameter cannot be changed within the procedure.
		+	***A reference variable can be assigned to a field symbol typed as a reference variable, provided that the reference types are identical.
		+	**Assignments between reference variables can be carried out by using an up cast or a down cast.
		+	**Data reference variables can be compared with all data reference variables and object reference variables can be compared with all object reference variables.
		+	As a rule, data reference variables can only be used with data reference variables and object reference variables can be used only with object reference variables. No conversions take place between reference variables. They are either passed as unconverted reference variables, assigned to each other, compared with each other, or no action at all takes place.
		+
		+
		+	===See Also===
		+	[[Data Access]]<br />
		+	[[Data Analysis]]<br />
		+	[[Data Analytics]]<br />
		+	[[Data Architecture]]<br />
		+	[[Data Asset Framework (DAF)]]<br />
		+	[[Data Buffer]]<br />
		+	[[Data Center]]<br />
		+	[[Data Center Infrastructure]]<br />
		+	[[Data Center Infrastructure Management (DCIM)]]<br />
		+	[[Data Cleansing]]<br />
		+	[[Data Collection]]<br />
		+	[[Data Compatibility]]<br />
		+	[[Data Consolidation]]<br />
		+	[[Data Deduplication]]<br />
		+	[[Data Delivery Platform (DDP)]]<br />
		+	[[Data Description (Definition) Language (DDL)]]<br />
		+	[[Data Dictionary]]<br />
		+	[[Data Discovery]]<br />
		+	[[Data Driven Organization]]<br />
		+	[[Data Element]]<br />
		+	[[Data Enrichment]]<br />
		+	[[Data Entry]]<br />
		+	[[Data Federation]]<br />
		+	[[Data Flow Diagram]]<br />
		+	[[Data Governance]]<br />
		+	[[Data Health Check]]<br />
		+	[[Data Hierarchy]]<br />
		+	[[Data Independence]]<br />
		+	[[Data Integration]]<br />
		+	[[Data Integration Framework (DIF)]]<br />
		+	[[Data Integrity]]<br />
		+	[[Data Island]]<br />
		+	[[Data Item]]<br />
		+	[[Data Lake]]<br />
		+	[[Data Life Cycle]]<br />
		+	[[Data Lineage]]<br />
		+	[[Data Loss Prevention (DLP)]]<br />
		+	[[Data Management]]<br />
		+	[[Data Migration]]<br />
		+	[[Data Minimization]]<br />
		+	[[Data Mining]]<br />
		+	[[Data Model]]<br />
		+	[[Data Modeling]]<br />
		+	[[Data Monitoring]]<br />
		+	[[Data Munging]]<br />
		+	[[Data Portability]]<br />
		+	[[Data Preparation]]<br />
		+	[[Data Presentation Architecture]]<br />
		+	[[Data Processing]]<br />
		+	[[Data Profiling]]<br />
		+	[[Data Proliferation]]<br />
		+	[[Data Propagation]]<br />
		+	[[Data Protection Act]]<br />
		+	[[Data Prototyping]]<br />
		+	[[Data Quality]]<br />
		+	[[Data Quality Assessment (DQA)]]<br />
		+	[[Data Quality Dimension]]<br />
		+	[[Data Quality Standard]]<br />
		+	[[Data Reconciliation]]<br />
		+	[[Data Reference Model (DRM)]]<br />
		+	[[Data Science]]<br />
		+	[[Data Security]]<br />
		+	[[Data Stewardship]]<br />
		+	[[Data Structure]]<br />
		+	[[Data Structure Diagram]]<br />
		+	[[Data Suppression]]<br />
		+	[[Data Transformation]]<br />
		+	[[Data Validation]]<br />
		+	[[Data Value Chain]]<br />
		+	[[Data Vault Modeling]]<br />
		+	[[Data Virtualization]]<br />
		+	[[Data Visualization]]<br />
		+	[[Data Warehouse]]<br />
		+	[[Data Wrangling]]<br />
		+	[[Data and Information Reference Model (DRM)]]<br />
		+	[[Data as a Service (DaaS)]]<br />
		+	[[Database (DB)]]<br />
		+	[[Database Design]]<br />
		+	[[Database Design Methodology]]<br />
		+	[[Database Management System (DBMS)]]<br />
		+	[[Database Marketing]]<br />
		+	[[Database Schema]]<br />
		+	[[Database System]]
		+
		+
		+	===References===