SAP /XLSO/DMTYPE_CHECK_CONSISTENCY Function Module for Consistency Check for Mix-and-Match Type Elements
/XLSO/DMTYPE_CHECK_CONSISTENCY is a standard /xlso/dmtype check consistency SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Consistency Check for Mix-and-Match Type Elements processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for /xlso/dmtype check consistency FM, simply by entering the name /XLSO/DMTYPE_CHECK_CONSISTENCY into the relevant SAP transaction such as SE37 or SE38.
Function Group: /XLSO/MIX_MATCH_BUNDLE_TYP
Program Name: /XLSO/SAPLMIX_MATCH_BUNDLE_TYP
Main Program: /XLSO/SAPLMIX_MATCH_BUNDLE_TYP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /XLSO/DMTYPE_CHECK_CONSISTENCY pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION '/XLSO/DMTYPE_CHECK_CONSISTENCY'"Consistency Check for Mix-and-Match Type Elements.
EXPORTING
* IV_PLANVERSION = "
* IV_MIXNMTYPETYPE = "
IV_MIXNMTYPEID = "
IMPORTING
ET_OUT_RESULT = "Curriculum Type: Result of Consistency Check
EXCEPTIONS
EX_MIXNMTYPE_NOT_FOUND = 1 EX_UNKNOWN_ERROR = 2
IMPORTING Parameters details for /XLSO/DMTYPE_CHECK_CONSISTENCY
IV_PLANVERSION -
Data type: PLVAROptional: Yes
Call by Reference: Yes
IV_MIXNMTYPETYPE -
Data type: OTYPEOptional: Yes
Call by Reference: Yes
IV_MIXNMTYPEID -
Data type: HROBJIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for /XLSO/DMTYPE_CHECK_CONSISTENCY
ET_OUT_RESULT - Curriculum Type: Result of Consistency Check
Data type: LSO_CURR_CHECKRESULT_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
EX_MIXNMTYPE_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
EX_UNKNOWN_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for /XLSO/DMTYPE_CHECK_CONSISTENCY Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_et_out_result | TYPE LSO_CURR_CHECKRESULT_TAB, " | |||
| lv_iv_planversion | TYPE PLVAR, " | |||
| lv_ex_mixnmtype_not_found | TYPE PLVAR, " | |||
| lv_ex_unknown_error | TYPE PLVAR, " | |||
| lv_iv_mixnmtypetype | TYPE OTYPE, " | |||
| lv_iv_mixnmtypeid | TYPE HROBJID. " |
|   CALL FUNCTION '/XLSO/DMTYPE_CHECK_CONSISTENCY' "Consistency Check for Mix-and-Match Type Elements |
| EXPORTING | ||
| IV_PLANVERSION | = lv_iv_planversion | |
| IV_MIXNMTYPETYPE | = lv_iv_mixnmtypetype | |
| IV_MIXNMTYPEID | = lv_iv_mixnmtypeid | |
| IMPORTING | ||
| ET_OUT_RESULT | = lv_et_out_result | |
| EXCEPTIONS | ||
| EX_MIXNMTYPE_NOT_FOUND = 1 | ||
| EX_UNKNOWN_ERROR = 2 | ||
| . " /XLSO/DMTYPE_CHECK_CONSISTENCY | ||
ABAP code using 7.40 inline data declarations to call FM /XLSO/DMTYPE_CHECK_CONSISTENCY
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects