SAP CACS_DET_GET_BUSOBJ_TYPE Function Module for NOTRANSL: Eintrag des Geschäftsobjekttyps holen

Search SAP Function Modules

CACS_DET_GET_BUSOBJ_TYPE is a standard cacs det get busobj type 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: Eintrag des Geschäftsobjekttyps holen 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 det get busobj type FM, simply by entering the name CACS_DET_GET_BUSOBJ_TYPE into the relevant SAP transaction such as SE37 or SE38.

Function Group: CACS_DET_VERSIONING_APPL
Program Name: SAPLCACS_DET_VERSIONING_APPL
Main Program: SAPLCACS_DET_VERSIONING_APPL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS_DET_GET_BUSOBJ_TYPE 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_DET_GET_BUSOBJ_TYPE'"NOTRANSL: Eintrag des Geschäftsobjekttyps holen
  EXPORTING
   IV_APPL =  "Commission Application Identification
   IV_BUSOBJ_TYPE =  "Business Object Category that Triggers Commission
   IV_BUSI =  "Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)
   IV_TECH =  "Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss)

 IMPORTING
   ES_BUSOBJ =  "Valid Business Objects of Operational System (incl.BOR Assg)

EXCEPTIONS
   ERROR = 1    NOT_FOUND = 2 

.

IMPORTING Parameters details for CACS_DET_GET_BUSOBJ_TYPE

IV_APPL - Commission Application Identification

Data type: CACSAPPL
Optional: No
Call by Reference: Yes

IV_BUSOBJ_TYPE - Business Object Category that Triggers Commission

Data type: CACSBUSOBJTYP
Optional: No
Call by Reference: Yes

IV_BUSI - Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)

Data type: CACSBUSITIME
Optional: No
Call by Reference: Yes

IV_TECH - Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss)

Data type: CACSTECHTIME
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CACS_DET_GET_BUSOBJ_TYPE

ES_BUSOBJ - Valid Business Objects of Operational System (incl.BOR Assg)

Data type: TCACS_BUSOBJ
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CACS_DET_GET_BUSOBJ_TYPE 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.

ABAP code using 7.40 inline data declarations to call FM CACS_DET_GET_BUSOBJ_TYPE

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