SAP LOG_CHECK_ENRICHMENT Function Module for NOTRANSL: Prüfen ob/welche Branche angereichert werden soll
LOG_CHECK_ENRICHMENT is a standard log check enrichment SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Prüfen ob/welche Branche angereichert werden soll 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 log check enrichment FM, simply by entering the name LOG_CHECK_ENRICHMENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCRS
Program Name: SAPLMCRS
Main Program: SAPLMCRS
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LOG_CHECK_ENRICHMENT 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 'LOG_CHECK_ENRICHMENT'"NOTRANSL: Prüfen ob/welche Branche angereichert werden soll.
IMPORTING
E_BW_APPL = "Industry Sector to be Enhanced
EXCEPTIONS
NO_APPL_ACTIVE = 1
EXPORTING Parameters details for LOG_CHECK_ENRICHMENT
E_BW_APPL - Industry Sector to be Enhanced
Data type: MCBW_ZUSA-BWINDUSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_APPL_ACTIVE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LOG_CHECK_ENRICHMENT 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_e_bw_appl | TYPE MCBW_ZUSA-BWINDUS, " | |||
| lv_no_appl_active | TYPE MCBW_ZUSA. " |
|   CALL FUNCTION 'LOG_CHECK_ENRICHMENT' "NOTRANSL: Prüfen ob/welche Branche angereichert werden soll |
| IMPORTING | ||
| E_BW_APPL | = lv_e_bw_appl | |
| EXCEPTIONS | ||
| NO_APPL_ACTIVE = 1 | ||
| . " LOG_CHECK_ENRICHMENT | ||
ABAP code using 7.40 inline data declarations to call FM LOG_CHECK_ENRICHMENT
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 BWINDUS FROM MCBW_ZUSA INTO @DATA(ld_e_bw_appl). | ||||
Search for further information about these or an SAP related objects