SAP MILL_SE_GET_CHAR_AND_VALUE Function Module for Read Characteristics and Characteristic Values for an Object (MATNR)
MILL_SE_GET_CHAR_AND_VALUE is a standard mill se get char and value SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Characteristics and Characteristic Values for an Object (MATNR) 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 mill se get char and value FM, simply by entering the name MILL_SE_GET_CHAR_AND_VALUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MILL_SE
Program Name: SAPLMILL_SE
Main Program: SAPLMILL_SE
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MILL_SE_GET_CHAR_AND_VALUE 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 'MILL_SE_GET_CHAR_AND_VALUE'"Read Characteristics and Characteristic Values for an Object (MATNR).
EXPORTING
* INSTANCE = "Configuration (Internal Object Number)
* IF_RECALC_FATTR = 'X' "Single-Character Indicator
* IF_CREATION_MODE = ' ' "Single-Character Indicator
* IF_ACTIVE_AND_ERROR = "Single-Character Indicator
IMPORTING
NEW_INSTANCE = "Configuration
CHANGING
* CF_ANZEIGEN = ' ' "Single-Character Indicator
* CX_FATTR = "MILL_SE_X_FIELD_ATTR
TABLES
* ET_VALUE = "Characteristic Value Assignments for Several Configurations
EXCEPTIONS
MATERIAL_HAS_NO_PROFIL = 1 NO_CONFIGURATION_PARAMS = 2 FATAL_ERROR = 3
IMPORTING Parameters details for MILL_SE_GET_CHAR_AND_VALUE
INSTANCE - Configuration (Internal Object Number)
Data type: INOB-CUOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
IF_RECALC_FATTR - Single-Character Indicator
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: Yes
IF_CREATION_MODE - Single-Character Indicator
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: Yes
IF_ACTIVE_AND_ERROR - Single-Character Indicator
Data type: CHAR1Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for MILL_SE_GET_CHAR_AND_VALUE
NEW_INSTANCE - Configuration
Data type: VBAP-CUOBJOptional: No
Call by Reference: Yes
CHANGING Parameters details for MILL_SE_GET_CHAR_AND_VALUE
CF_ANZEIGEN - Single-Character Indicator
Data type: CHAR1Default: ' '
Optional: Yes
Call by Reference: Yes
CX_FATTR - MILL_SE_X_FIELD_ATTR
Data type: MILL_SE_X_FIELD_ATTROptional: Yes
Call by Reference: Yes
TABLES Parameters details for MILL_SE_GET_CHAR_AND_VALUE
ET_VALUE - Characteristic Value Assignments for Several Configurations
Data type: CUXE1CUVALOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
MATERIAL_HAS_NO_PROFIL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_CONFIGURATION_PARAMS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FATAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MILL_SE_GET_CHAR_AND_VALUE 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: | ||||
| lt_et_value | TYPE STANDARD TABLE OF CUXE1CUVAL, " | |||
| lv_instance | TYPE INOB-CUOBJ, " | |||
| lv_cf_anzeigen | TYPE CHAR1, " ' ' | |||
| lv_new_instance | TYPE VBAP-CUOBJ, " | |||
| lv_material_has_no_profil | TYPE VBAP, " | |||
| lv_cx_fattr | TYPE MILL_SE_X_FIELD_ATTR, " | |||
| lv_if_recalc_fattr | TYPE CHAR1, " 'X' | |||
| lv_no_configuration_params | TYPE CHAR1, " | |||
| lv_fatal_error | TYPE CHAR1, " | |||
| lv_if_creation_mode | TYPE CHAR1, " ' ' | |||
| lv_if_active_and_error | TYPE CHAR1. " |
|   CALL FUNCTION 'MILL_SE_GET_CHAR_AND_VALUE' "Read Characteristics and Characteristic Values for an Object (MATNR) |
| EXPORTING | ||
| INSTANCE | = lv_instance | |
| IF_RECALC_FATTR | = lv_if_recalc_fattr | |
| IF_CREATION_MODE | = lv_if_creation_mode | |
| IF_ACTIVE_AND_ERROR | = lv_if_active_and_error | |
| IMPORTING | ||
| NEW_INSTANCE | = lv_new_instance | |
| CHANGING | ||
| CF_ANZEIGEN | = lv_cf_anzeigen | |
| CX_FATTR | = lv_cx_fattr | |
| TABLES | ||
| ET_VALUE | = lt_et_value | |
| EXCEPTIONS | ||
| MATERIAL_HAS_NO_PROFIL = 1 | ||
| NO_CONFIGURATION_PARAMS = 2 | ||
| FATAL_ERROR = 3 | ||
| . " MILL_SE_GET_CHAR_AND_VALUE | ||
ABAP code using 7.40 inline data declarations to call FM MILL_SE_GET_CHAR_AND_VALUE
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.| "SELECT single CUOBJ FROM INOB INTO @DATA(ld_instance). | ||||
| DATA(ld_cf_anzeigen) | = ' '. | |||
| "SELECT single CUOBJ FROM VBAP INTO @DATA(ld_new_instance). | ||||
| DATA(ld_if_recalc_fattr) | = 'X'. | |||
| DATA(ld_if_creation_mode) | = ' '. | |||
Search for further information about these or an SAP related objects