SAP CACS_SESJO_UPDATE Function Module for NOTRANSL: OBSOLET Update für das Abrechnungsplanlauf Journal
CACS_SESJO_UPDATE is a standard cacs sesjo update 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: OBSOLET Update für das Abrechnungsplanlauf Journal 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 sesjo update FM, simply by entering the name CACS_SESJO_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_SES_DBIF
Program Name: SAPLCACS_SES_DBIF
Main Program: SAPLCACS_SES_DBIF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1
Function CACS_SESJO_UPDATE 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_SESJO_UPDATE'"NOTRANSL: OBSOLET Update für das Abrechnungsplanlauf Journal.
TABLES
* T_SESJO = "Log for Settlement Schedule Run
EXCEPTIONS
NO_UPDATE_POSSIBLE = 1
TABLES Parameters details for CACS_SESJO_UPDATE
T_SESJO - Log for Settlement Schedule Run
Data type: CACS_S_SESJOOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_UPDATE_POSSIBLE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS_SESJO_UPDATE 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: | ||||
lt_t_sesjo | TYPE STANDARD TABLE OF CACS_S_SESJO, " | |||
lv_no_update_possible | TYPE CACS_S_SESJO. " |
  CALL FUNCTION 'CACS_SESJO_UPDATE' "NOTRANSL: OBSOLET Update für das Abrechnungsplanlauf Journal |
TABLES | ||
T_SESJO | = lt_t_sesjo | |
EXCEPTIONS | ||
NO_UPDATE_POSSIBLE = 1 | ||
. " CACS_SESJO_UPDATE |
ABAP code using 7.40 inline data declarations to call FM CACS_SESJO_UPDATE
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