SAP TEM_CUST_ATTRIBUTE_CHECK Function Module for Check if Value Exists for Attribute
TEM_CUST_ATTRIBUTE_CHECK is a standard tem cust attribute check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if Value Exists for Attribute 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 tem cust attribute check FM, simply by entering the name TEM_CUST_ATTRIBUTE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: TEM_CUSTOMIZING_DB
Program Name: SAPLTEM_CUSTOMIZING_DB
Main Program: SAPLTEM_CUSTOMIZING_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TEM_CUST_ATTRIBUTE_CHECK 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 'TEM_CUST_ATTRIBUTE_CHECK'"Check if Value Exists for Attribute.
EXPORTING
IM_NUMBER = "Number of a Free Attribute
IM_VALUE = "Value of a Free Attribute
EXCEPTIONS
NO_ENTRY_FOUND_ERROR = 1 NO_ENTRY_FOUND_WARNING = 2
IMPORTING Parameters details for TEM_CUST_ATTRIBUTE_CHECK
IM_NUMBER - Number of a Free Attribute
Data type: TEM_ATTRIBUTE_NUMBEROptional: No
Call by Reference: Yes
IM_VALUE - Value of a Free Attribute
Data type: TEM_ATTRIBUTE_VALUEOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ENTRY_FOUND_ERROR - kein Eintrag gefunden als Fehlermeldung
Data type:Optional: No
Call by Reference: Yes
NO_ENTRY_FOUND_WARNING - kein Eintrag gefunden als Warnung
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TEM_CUST_ATTRIBUTE_CHECK 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_im_number | TYPE TEM_ATTRIBUTE_NUMBER, " | |||
| lv_no_entry_found_error | TYPE TEM_ATTRIBUTE_NUMBER, " | |||
| lv_im_value | TYPE TEM_ATTRIBUTE_VALUE, " | |||
| lv_no_entry_found_warning | TYPE TEM_ATTRIBUTE_VALUE. " |
|   CALL FUNCTION 'TEM_CUST_ATTRIBUTE_CHECK' "Check if Value Exists for Attribute |
| EXPORTING | ||
| IM_NUMBER | = lv_im_number | |
| IM_VALUE | = lv_im_value | |
| EXCEPTIONS | ||
| NO_ENTRY_FOUND_ERROR = 1 | ||
| NO_ENTRY_FOUND_WARNING = 2 | ||
| . " TEM_CUST_ATTRIBUTE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM TEM_CUST_ATTRIBUTE_CHECK
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