SAP CACSSL_GET_SETTLE_DATA Function Module for Get settlement data from the DB

Search SAP Function Modules

CACSSL_GET_SETTLE_DATA is a standard cacssl get settle data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get settlement data from the DB 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 cacssl get settle data FM, simply by entering the name CACSSL_GET_SETTLE_DATA into the relevant SAP transaction such as SE37 or SE38.

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

Function CACSSL_GET_SETTLE_DATA 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 'CACSSL_GET_SETTLE_DATA'"Get settlement data from the DB
  EXPORTING
   I_R_PARTNER =  "Ranges for Partner
   I_R_STMTYPE =  "Ranges for Settlement Type for Fast Track approval
   I_R_CONTRACT =  "Ranges for Commission Contract
   I_R_DUEDATES =  "Business Object ID Selection Option
*  I_APPROVED_LCK =  "Indicator: Item Waiting for Subsequent Process

 IMPORTING
   OT_DETAILS =  "Table Type for FT approval; Settlement Item line
   E_PREV_CHANGE =  "Prior changes are not being displayed

EXCEPTIONS
   ERROR_OCCURRED_IN_SELECTION = 1    SETTLEMENT_TYPE_NOT_FOUND = 2    REM_AGG_NOT_DETERMINED = 3    INVALID_DATA_COMBINATION = 4    SYSTEM_FAILURE = 5 

.

IMPORTING Parameters details for CACSSL_GET_SETTLE_DATA

I_R_PARTNER - Ranges for Partner

Data type: CACSSL_CL_SETT_LCK_TTYPES=>TT_PARTNER_NEW
Optional: No
Call by Reference: No ( called with pass by value option)

I_R_STMTYPE - Ranges for Settlement Type for Fast Track approval

Data type: CACSSL_CL_SETT_LCK_TTYPES=>TT_FTA_STLTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

I_R_CONTRACT - Ranges for Commission Contract

Data type: CACSSL_CL_SETT_LCK_TTYPES=>TT_CONTRACT
Optional: No
Call by Reference: No ( called with pass by value option)

I_R_DUEDATES - Business Object ID Selection Option

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

I_APPROVED_LCK - Indicator: Item Waiting for Subsequent Process

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CACSSL_GET_SETTLE_DATA

OT_DETAILS - Table Type for FT approval; Settlement Item line

Data type: CACSSL_CL_SETT_LCK_TTYPES=>TT_ITM
Optional: No
Call by Reference: Yes

E_PREV_CHANGE - Prior changes are not being displayed

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

EXCEPTIONS details

ERROR_OCCURRED_IN_SELECTION - Error Occurred during selection

Data type:
Optional: No
Call by Reference: Yes

SETTLEMENT_TYPE_NOT_FOUND - Error with settlement type supplied

Data type:
Optional: No
Call by Reference: Yes

REM_AGG_NOT_DETERMINED - could not determine Remuneration Agreeement

Data type:
Optional: No
Call by Reference: Yes

INVALID_DATA_COMBINATION - Invalid Contract Settlement type combination

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_FAILURE - could not determine time stamp

Data type:
Optional: No
Call by Reference: Yes

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

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