SAP /ACCGO/CAS_SETTLEMENT_APPROVE Function Module for Approve the Settlement
/ACCGO/CAS_SETTLEMENT_APPROVE is a standard /accgo/cas settlement approve SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Approve the Settlement 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 /accgo/cas settlement approve FM, simply by entering the name /ACCGO/CAS_SETTLEMENT_APPROVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: /ACCGO/CAS_SETTLEMENT_API
Program Name: /ACCGO/SAPLCAS_SETTLEMENT_API
Main Program: /ACCGO/SAPLCAS_SETTLEMENT_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function /ACCGO/CAS_SETTLEMENT_APPROVE 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 '/ACCGO/CAS_SETTLEMENT_APPROVE'"Approve the Settlement.
EXPORTING
* IM_T_GROUP_IDS = "Table type for Group ID
* IM_T_GROUP_GUIDS = "Settlment group GUIDs
* IM_V_RCODE = "Settlement Reason Codes
* IM_T_RCODE_TEXT = "Text Lines (132 Characters)
* IM_V_NO_COMMIT = 'X' "Boolean: True/False
* IM_V_UI_FLAG = "Boolean: True/False
IMPORTING
EX_T_MESSAGES = "Settlement Messages
EXCEPTIONS
ERROR_SETTING_QUEUE_IN_ARETRY = 1
IMPORTING Parameters details for /ACCGO/CAS_SETTLEMENT_APPROVE
IM_T_GROUP_IDS - Table type for Group ID
Data type: /ACCGO/CAS_TT_STLCTNR_KEYOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_T_GROUP_GUIDS - Settlment group GUIDs
Data type: /ACCGO/CAS_TT_STLGRP_GUIDSOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_V_RCODE - Settlement Reason Codes
Data type: /ACCGO/E_REASON_CODEOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_T_RCODE_TEXT - Text Lines (132 Characters)
Data type: /ACCGO/CAS_TT_STL_TEXT_LINESOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_V_NO_COMMIT - Boolean: True/False
Data type: /ACCGO/E_BOOLEANDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IM_V_UI_FLAG - Boolean: True/False
Data type: /ACCGO/E_BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for /ACCGO/CAS_SETTLEMENT_APPROVE
EX_T_MESSAGES - Settlement Messages
Data type: /ACCGO/CAS_TT_STL_MESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_SETTING_QUEUE_IN_ARETRY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /ACCGO/CAS_SETTLEMENT_APPROVE 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_ex_t_messages | TYPE /ACCGO/CAS_TT_STL_MESSAGE, " | |||
lv_im_t_group_ids | TYPE /ACCGO/CAS_TT_STLCTNR_KEY, " | |||
lv_error_setting_queue_in_aretry | TYPE /ACCGO/CAS_TT_STLCTNR_KEY, " | |||
lv_im_t_group_guids | TYPE /ACCGO/CAS_TT_STLGRP_GUIDS, " | |||
lv_im_v_rcode | TYPE /ACCGO/E_REASON_CODE, " | |||
lv_im_t_rcode_text | TYPE /ACCGO/CAS_TT_STL_TEXT_LINES, " | |||
lv_im_v_no_commit | TYPE /ACCGO/E_BOOLEAN, " 'X' | |||
lv_im_v_ui_flag | TYPE /ACCGO/E_BOOLEAN. " |
  CALL FUNCTION '/ACCGO/CAS_SETTLEMENT_APPROVE' "Approve the Settlement |
EXPORTING | ||
IM_T_GROUP_IDS | = lv_im_t_group_ids | |
IM_T_GROUP_GUIDS | = lv_im_t_group_guids | |
IM_V_RCODE | = lv_im_v_rcode | |
IM_T_RCODE_TEXT | = lv_im_t_rcode_text | |
IM_V_NO_COMMIT | = lv_im_v_no_commit | |
IM_V_UI_FLAG | = lv_im_v_ui_flag | |
IMPORTING | ||
EX_T_MESSAGES | = lv_ex_t_messages | |
EXCEPTIONS | ||
ERROR_SETTING_QUEUE_IN_ARETRY = 1 | ||
. " /ACCGO/CAS_SETTLEMENT_APPROVE |
ABAP code using 7.40 inline data declarations to call FM /ACCGO/CAS_SETTLEMENT_APPROVE
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.DATA(ld_im_v_no_commit) | = 'X'. | |||
Search for further information about these or an SAP related objects