SAP CRM_ISU_ERMS_GET_BO Function Module for Returns the Number of an Business Object
CRM_ISU_ERMS_GET_BO is a standard crm isu erms get bo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Returns the Number of an Business Object 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 crm isu erms get bo FM, simply by entering the name CRM_ISU_ERMS_GET_BO into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_ISU_ERMS_FG_UTIL_BO
Program Name: SAPLCRM_ISU_ERMS_FG_UTIL_BO
Main Program: SAPLCRM_ISU_ERMS_FG_UTIL_BO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CRM_ISU_ERMS_GET_BO 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 'CRM_ISU_ERMS_GET_BO'"Returns the Number of an Business Object.
EXPORTING
IV_MAIL_CONTENT = "MeilContent
IV_KEYWORD = "Key Word
IMPORTING
EV_RESULT_ID = "ID according to the Key Word
TABLES
CT_RESULT_ID = "Table containing Strings
IMPORTING Parameters details for CRM_ISU_ERMS_GET_BO
IV_MAIL_CONTENT - MeilContent
Data type: STRINGOptional: No
Call by Reference: Yes
IV_KEYWORD - Key Word
Data type: STRINGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CRM_ISU_ERMS_GET_BO
EV_RESULT_ID - ID according to the Key Word
Data type: STRINGOptional: No
Call by Reference: Yes
TABLES Parameters details for CRM_ISU_ERMS_GET_BO
CT_RESULT_ID - Table containing Strings
Data type: CRM_ISU_ERMS_STRING_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_ISU_ERMS_GET_BO 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_ct_result_id | TYPE STANDARD TABLE OF CRM_ISU_ERMS_STRING_TAB, " | |||
lv_ev_result_id | TYPE STRING, " | |||
lv_iv_mail_content | TYPE STRING, " | |||
lv_iv_keyword | TYPE STRING. " |
  CALL FUNCTION 'CRM_ISU_ERMS_GET_BO' "Returns the Number of an Business Object |
EXPORTING | ||
IV_MAIL_CONTENT | = lv_iv_mail_content | |
IV_KEYWORD | = lv_iv_keyword | |
IMPORTING | ||
EV_RESULT_ID | = lv_ev_result_id | |
TABLES | ||
CT_RESULT_ID | = lt_ct_result_id | |
. " CRM_ISU_ERMS_GET_BO |
ABAP code using 7.40 inline data declarations to call FM CRM_ISU_ERMS_GET_BO
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