SAP CACS_IDBUILD_CASE Function Module for NOTRANSL: Baue ID Provisionsfall
CACS_IDBUILD_CASE is a standard cacs idbuild case 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: Baue ID Provisionsfall 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 idbuild case FM, simply by entering the name CACS_IDBUILD_CASE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_IDBUILDER
Program Name: SAPLCACS_IDBUILDER
Main Program: SAPLCACS_IDBUILDER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS_IDBUILD_CASE 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_IDBUILD_CASE'"NOTRANSL: Baue ID Provisionsfall.
EXPORTING
* I_IMPORT_YEAR = "Year Commission Case Reported
* I_CASE_ID = "ID of Commission Case
* I_CASE_VERS = "Commission Case Version
* I_BUSOBJ_TYPE = "Business Object Category that Triggers Commission
* I_BUSOBJ_ID = "Identification of Triggering Business Object
* I_BUSOBJ_VERS = "Version of Master Data or Customizing Object
* I_BUSCASE_TYP = "Commission Triggering Business Case in Operational System
* I_BUSCASE_ID = "Identification of Triggering Bus. Transaction in Op. System
* I_BUSCASE_VERS = "Version of Master Data or Customizing Object
IMPORTING
E_ID_INT = "Character field, length 64
E_ID_BUSOBJ = "128 character
E_ID_BUSCASE = "128 character
E_ID_BUSOBJCASE = "Data element for WWI callback
IMPORTING Parameters details for CACS_IDBUILD_CASE
I_IMPORT_YEAR - Year Commission Case Reported
Data type: CACSIMPYEAROptional: Yes
Call by Reference: No ( called with pass by value option)
I_CASE_ID - ID of Commission Case
Data type: CACSCASEIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CASE_VERS - Commission Case Version
Data type: CACSCASEVERSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUSOBJ_TYPE - Business Object Category that Triggers Commission
Data type: CACSBUSOBJTYPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUSOBJ_ID - Identification of Triggering Business Object
Data type: CACSBUSOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUSOBJ_VERS - Version of Master Data or Customizing Object
Data type: CACSVERSIONLONGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUSCASE_TYP - Commission Triggering Business Case in Operational System
Data type: CACSTRIBUSCASTYPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUSCASE_ID - Identification of Triggering Bus. Transaction in Op. System
Data type: CACSTRIBUSCASEIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUSCASE_VERS - Version of Master Data or Customizing Object
Data type: CACSVERSIONLONGOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CACS_IDBUILD_CASE
E_ID_INT - Character field, length 64
Data type: CHAR64Optional: No
Call by Reference: Yes
E_ID_BUSOBJ - 128 character
Data type: CHAR128Optional: No
Call by Reference: Yes
E_ID_BUSCASE - 128 character
Data type: CHAR128Optional: No
Call by Reference: Yes
E_ID_BUSOBJCASE - Data element for WWI callback
Data type: CHAR256Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS_IDBUILD_CASE 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_id_int | TYPE CHAR64, " | |||
| lv_i_import_year | TYPE CACSIMPYEAR, " | |||
| lv_i_case_id | TYPE CACSCASEID, " | |||
| lv_e_id_busobj | TYPE CHAR128, " | |||
| lv_i_case_vers | TYPE CACSCASEVERS, " | |||
| lv_e_id_buscase | TYPE CHAR128, " | |||
| lv_i_busobj_type | TYPE CACSBUSOBJTYP, " | |||
| lv_e_id_busobjcase | TYPE CHAR256, " | |||
| lv_i_busobj_id | TYPE CACSBUSOBJID, " | |||
| lv_i_busobj_vers | TYPE CACSVERSIONLONG, " | |||
| lv_i_buscase_typ | TYPE CACSTRIBUSCASTYP, " | |||
| lv_i_buscase_id | TYPE CACSTRIBUSCASEID, " | |||
| lv_i_buscase_vers | TYPE CACSVERSIONLONG. " |
|   CALL FUNCTION 'CACS_IDBUILD_CASE' "NOTRANSL: Baue ID Provisionsfall |
| EXPORTING | ||
| I_IMPORT_YEAR | = lv_i_import_year | |
| I_CASE_ID | = lv_i_case_id | |
| I_CASE_VERS | = lv_i_case_vers | |
| I_BUSOBJ_TYPE | = lv_i_busobj_type | |
| I_BUSOBJ_ID | = lv_i_busobj_id | |
| I_BUSOBJ_VERS | = lv_i_busobj_vers | |
| I_BUSCASE_TYP | = lv_i_buscase_typ | |
| I_BUSCASE_ID | = lv_i_buscase_id | |
| I_BUSCASE_VERS | = lv_i_buscase_vers | |
| IMPORTING | ||
| E_ID_INT | = lv_e_id_int | |
| E_ID_BUSOBJ | = lv_e_id_busobj | |
| E_ID_BUSCASE | = lv_e_id_buscase | |
| E_ID_BUSOBJCASE | = lv_e_id_busobjcase | |
| . " CACS_IDBUILD_CASE | ||
ABAP code using 7.40 inline data declarations to call FM CACS_IDBUILD_CASE
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