SAP CACS00_INDIVIDUAL_PART Function Module for Determine Constellations
CACS00_INDIVIDUAL_PART is a standard cacs00 individual part SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Constellations 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 cacs00 individual part FM, simply by entering the name CACS00_INDIVIDUAL_PART into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS00_INVOLVED
Program Name: SAPLCACS00_INVOLVED
Main Program: SAPLCACS00_INVOLVED
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS00_INDIVIDUAL_PART 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 'CACS00_INDIVIDUAL_PART'"Determine Constellations.
EXPORTING
I_APPL = "Commission Application Identification
I_CLC_TIMESTAMP = "Effective From
I_KNW_TIMESTAMP = "Technically Valid from
* I_SEARCH_PATH = "Evaluation Path for Commission Contracts
* I_CALC_DEPTH = "Evaluation depth
I_ROLETYPE = "Entitlement Category
I_CLAIM_OBJTYPE = "Entitlement Object Type
* I_NEXT_POS = "Participant Position in a Participation
TABLES
I_META_PARTICIPATION = "Commission Case Participation (Meta Object)
I_META_INVESTIGATION = "Commission Case Participant (Meta Object)
E_CUST_INVESTIGATION = "Commission Case Participant (Meta Object)
I_META_RELATION = "Participant Relations (Meta Object)
E_CUST_RELATION = "Participant Relations (Meta Object)
IMPORTING Parameters details for CACS00_INDIVIDUAL_PART
I_APPL - Commission Application Identification
Data type: CACSAPPLOptional: No
Call by Reference: No ( called with pass by value option)
I_CLC_TIMESTAMP - Effective From
Data type: CACS_BUSITIME_BOptional: No
Call by Reference: No ( called with pass by value option)
I_KNW_TIMESTAMP - Technically Valid from
Data type: CACS_TECHTIME_BOptional: No
Call by Reference: No ( called with pass by value option)
I_SEARCH_PATH - Evaluation Path for Commission Contracts
Data type: CACSCALCPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CALC_DEPTH - Evaluation depth
Data type: CACSDEPTHOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ROLETYPE - Entitlement Category
Data type: CACSCLAIMTYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_CLAIM_OBJTYPE - Entitlement Object Type
Data type: CACSCLAIMOBJTYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_NEXT_POS - Participant Position in a Participation
Data type: CACSINVPOSOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CACS00_INDIVIDUAL_PART
I_META_PARTICIPATION - Commission Case Participation (Meta Object)
Data type: CACS00_S_PARMOptional: No
Call by Reference: Yes
I_META_INVESTIGATION - Commission Case Participant (Meta Object)
Data type: CACS00_S_INVMOptional: No
Call by Reference: Yes
E_CUST_INVESTIGATION - Commission Case Participant (Meta Object)
Data type: CACS00_S_INVMOptional: No
Call by Reference: Yes
I_META_RELATION - Participant Relations (Meta Object)
Data type: CACS00_S_RELMOptional: No
Call by Reference: Yes
E_CUST_RELATION - Participant Relations (Meta Object)
Data type: CACS00_S_RELMOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS00_INDIVIDUAL_PART 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_i_appl | TYPE CACSAPPL, " | |||
| lt_i_meta_participation | TYPE STANDARD TABLE OF CACS00_S_PARM, " | |||
| lv_i_clc_timestamp | TYPE CACS_BUSITIME_B, " | |||
| lt_i_meta_investigation | TYPE STANDARD TABLE OF CACS00_S_INVM, " | |||
| lv_i_knw_timestamp | TYPE CACS_TECHTIME_B, " | |||
| lt_e_cust_investigation | TYPE STANDARD TABLE OF CACS00_S_INVM, " | |||
| lv_i_search_path | TYPE CACSCALCP, " | |||
| lt_i_meta_relation | TYPE STANDARD TABLE OF CACS00_S_RELM, " | |||
| lv_i_calc_depth | TYPE CACSDEPTH, " | |||
| lt_e_cust_relation | TYPE STANDARD TABLE OF CACS00_S_RELM, " | |||
| lv_i_roletype | TYPE CACSCLAIMTYPE, " | |||
| lv_i_claim_objtype | TYPE CACSCLAIMOBJTYPE, " | |||
| lv_i_next_pos | TYPE CACSINVPOS. " |
|   CALL FUNCTION 'CACS00_INDIVIDUAL_PART' "Determine Constellations |
| EXPORTING | ||
| I_APPL | = lv_i_appl | |
| I_CLC_TIMESTAMP | = lv_i_clc_timestamp | |
| I_KNW_TIMESTAMP | = lv_i_knw_timestamp | |
| I_SEARCH_PATH | = lv_i_search_path | |
| I_CALC_DEPTH | = lv_i_calc_depth | |
| I_ROLETYPE | = lv_i_roletype | |
| I_CLAIM_OBJTYPE | = lv_i_claim_objtype | |
| I_NEXT_POS | = lv_i_next_pos | |
| TABLES | ||
| I_META_PARTICIPATION | = lt_i_meta_participation | |
| I_META_INVESTIGATION | = lt_i_meta_investigation | |
| E_CUST_INVESTIGATION | = lt_e_cust_investigation | |
| I_META_RELATION | = lt_i_meta_relation | |
| E_CUST_RELATION | = lt_e_cust_relation | |
| . " CACS00_INDIVIDUAL_PART | ||
ABAP code using 7.40 inline data declarations to call FM CACS00_INDIVIDUAL_PART
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