SAP CACS_GET_BUSOBJ_TYPES_RFC Function Module for NOTRANSL: Ermittelt Geschäftsobjekttypen für Anwendung (RFC)
CACS_GET_BUSOBJ_TYPES_RFC is a standard cacs get busobj types rfc 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: Ermittelt Geschäftsobjekttypen für Anwendung (RFC) 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 cacs get busobj types rfc FM, simply by entering the name CACS_GET_BUSOBJ_TYPES_RFC into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_REMINQ_PORTAL
Program Name: SAPLCACS_REMINQ_PORTAL
Main Program: SAPLCACS_REMINQ_PORTAL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CACS_GET_BUSOBJ_TYPES_RFC 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 'CACS_GET_BUSOBJ_TYPES_RFC'"NOTRANSL: Ermittelt Geschäftsobjekttypen für Anwendung (RFC).
EXPORTING
IV_APPL = "Commission Application (ICM)
IMPORTING
ET_BUSOBJ_TYPE = "Categories of Business Objects
ES_MSG = "Application Log: Structure for a formatted message
IMPORTING Parameters details for CACS_GET_BUSOBJ_TYPES_RFC
IV_APPL - Commission Application (ICM)
Data type: CACSAPPLOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CACS_GET_BUSOBJ_TYPES_RFC
ET_BUSOBJ_TYPE - Categories of Business Objects
Data type: CACS_T_BUSOBJOptional: No
Call by Reference: No ( called with pass by value option)
ES_MSG - Application Log: Structure for a formatted message
Data type: BALMTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CACS_GET_BUSOBJ_TYPES_RFC 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_iv_appl | TYPE CACSAPPL, " | |||
| lv_et_busobj_type | TYPE CACS_T_BUSOBJ, " | |||
| lv_es_msg | TYPE BALMT. " |
|   CALL FUNCTION 'CACS_GET_BUSOBJ_TYPES_RFC' "NOTRANSL: Ermittelt Geschäftsobjekttypen für Anwendung (RFC) |
| EXPORTING | ||
| IV_APPL | = lv_iv_appl | |
| IMPORTING | ||
| ET_BUSOBJ_TYPE | = lv_et_busobj_type | |
| ES_MSG | = lv_es_msg | |
| . " CACS_GET_BUSOBJ_TYPES_RFC | ||
ABAP code using 7.40 inline data declarations to call FM CACS_GET_BUSOBJ_TYPES_RFC
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