SAP EHSB_LBDOC_TEXTCAT_CHECK Function Module for
EHSB_LBDOC_TEXTCAT_CHECK is a standard ehsb lbdoc textcat check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ehsb lbdoc textcat check FM, simply by entering the name EHSB_LBDOC_TEXTCAT_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: EHSB_LBDOC
Program Name: SAPLEHSB_LBDOC
Main Program: SAPLEHSB_LBDOC
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EHSB_LBDOC_TEXTCAT_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 'EHSB_LBDOC_TEXTCAT_CHECK'".
TABLES
X_APIDF_TAB = "
EXCEPTIONS
ILLEGAL_INPUT = 1 INTERNAL_ERROR = 2
TABLES Parameters details for EHSB_LBDOC_TEXTCAT_CHECK
X_APIDF_TAB -
Data type: CIH01_DFTAPI_TAB_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ILLEGAL_INPUT - Invalid Entry
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR - Internal System Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EHSB_LBDOC_TEXTCAT_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: | ||||
| lt_x_apidf_tab | TYPE STANDARD TABLE OF CIH01_DFTAPI_TAB_TYPE, " | |||
| lv_illegal_input | TYPE CIH01_DFTAPI_TAB_TYPE, " | |||
| lv_internal_error | TYPE CIH01_DFTAPI_TAB_TYPE. " |
|   CALL FUNCTION 'EHSB_LBDOC_TEXTCAT_CHECK' " |
| TABLES | ||
| X_APIDF_TAB | = lt_x_apidf_tab | |
| EXCEPTIONS | ||
| ILLEGAL_INPUT = 1 | ||
| INTERNAL_ERROR = 2 | ||
| . " EHSB_LBDOC_TEXTCAT_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM EHSB_LBDOC_TEXTCAT_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