SAP CACS_CSC_WRITE_BUCAGR Function Module for NOTRANSL: Prov.: Schreibe Daten zu Vereinbarungsbündel
CACS_CSC_WRITE_BUCAGR is a standard cacs csc write bucagr 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: Prov.: Schreibe Daten zu Vereinbarungsbündel 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 csc write bucagr FM, simply by entering the name CACS_CSC_WRITE_BUCAGR into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_CONTRACTC_AT
Program Name: SAPLCACS_CONTRACTC_AT
Main Program: SAPLCACS_CONTRACTC_AT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function CACS_CSC_WRITE_BUCAGR 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_CSC_WRITE_BUCAGR'"NOTRANSL: Prov.: Schreibe Daten zu Vereinbarungsbündel.
TABLES
T_CACS_BUCAGR = "Like CACS_BUCAGR table plus status information
T_BUCAGR_PRE = "Commission: Agreement Bundle
TABLES Parameters details for CACS_CSC_WRITE_BUCAGR
T_CACS_BUCAGR - Like CACS_BUCAGR table plus status information
Data type: CACS_S_BUCAGR_UPDTOptional: No
Call by Reference: Yes
T_BUCAGR_PRE - Commission: Agreement Bundle
Data type: CACS_BUCAGROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS_CSC_WRITE_BUCAGR 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_cacs_bucagr | TYPE STANDARD TABLE OF CACS_S_BUCAGR_UPDT, " | |||
| lt_t_bucagr_pre | TYPE STANDARD TABLE OF CACS_BUCAGR. " |
|   CALL FUNCTION 'CACS_CSC_WRITE_BUCAGR' "NOTRANSL: Prov.: Schreibe Daten zu Vereinbarungsbündel |
| TABLES | ||
| T_CACS_BUCAGR | = lt_t_cacs_bucagr | |
| T_BUCAGR_PRE | = lt_t_bucagr_pre | |
| . " CACS_CSC_WRITE_BUCAGR | ||
ABAP code using 7.40 inline data declarations to call FM CACS_CSC_WRITE_BUCAGR
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