SAP SD_CAS_CHANGE_DOCUMENT_CREATE Function Module for NOTRANSL: Änderungsbelege für CAS-Belege anlegen
SD_CAS_CHANGE_DOCUMENT_CREATE is a standard sd cas change document create 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: Änderungsbelege für CAS-Belege anlegen 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 sd cas change document create FM, simply by entering the name SD_CAS_CHANGE_DOCUMENT_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: V43B
Program Name: SAPLV43B
Main Program:
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SD_CAS_CHANGE_DOCUMENT_CREATE 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 'SD_CAS_CHANGE_DOCUMENT_CREATE'"NOTRANSL: Änderungsbelege für CAS-Belege anlegen.
TABLES
FT_XVBKA = "Sales Activities ( Data Base and Dynamic Part )
* FT_YVBKA = "Sales Activities ( Data Base and Dynamic Part )
* FT_XVBPA = "Reference structure for XVBPA/YVBPA
* FT_YVBPA = "Reference structure for XVBPA/YVBPA
* FT_XVBUK = "Reference structure for XVBUK/YVBUK
* FT_YVBUK = "Reference structure for XVBUK/YVBUK
* FT_XTHEAD = "SAPscript Programming Interface: Structure CATALOG
* FT_XVBADR = "Reference structure for XSADR/YSADR
* FT_YVBADR = "Reference structure for XSADR/YSADR
TABLES Parameters details for SD_CAS_CHANGE_DOCUMENT_CREATE
FT_XVBKA - Sales Activities ( Data Base and Dynamic Part )
Data type: VBKAVBOptional: No
Call by Reference: No ( called with pass by value option)
FT_YVBKA - Sales Activities ( Data Base and Dynamic Part )
Data type: VBKAVBOptional: Yes
Call by Reference: No ( called with pass by value option)
FT_XVBPA - Reference structure for XVBPA/YVBPA
Data type: VBPAVBOptional: Yes
Call by Reference: No ( called with pass by value option)
FT_YVBPA - Reference structure for XVBPA/YVBPA
Data type: VBPAVBOptional: Yes
Call by Reference: No ( called with pass by value option)
FT_XVBUK - Reference structure for XVBUK/YVBUK
Data type: VBUKVBOptional: Yes
Call by Reference: No ( called with pass by value option)
FT_YVBUK - Reference structure for XVBUK/YVBUK
Data type: VBUKVBOptional: Yes
Call by Reference: No ( called with pass by value option)
FT_XTHEAD - SAPscript Programming Interface: Structure CATALOG
Data type: TCATALOGOptional: Yes
Call by Reference: No ( called with pass by value option)
FT_XVBADR - Reference structure for XSADR/YSADR
Data type: SADRVBOptional: Yes
Call by Reference: No ( called with pass by value option)
FT_YVBADR - Reference structure for XSADR/YSADR
Data type: SADRVBOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_CAS_CHANGE_DOCUMENT_CREATE 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_ft_xvbka | TYPE STANDARD TABLE OF VBKAVB, " | |||
| lt_ft_yvbka | TYPE STANDARD TABLE OF VBKAVB, " | |||
| lt_ft_xvbpa | TYPE STANDARD TABLE OF VBPAVB, " | |||
| lt_ft_yvbpa | TYPE STANDARD TABLE OF VBPAVB, " | |||
| lt_ft_xvbuk | TYPE STANDARD TABLE OF VBUKVB, " | |||
| lt_ft_yvbuk | TYPE STANDARD TABLE OF VBUKVB, " | |||
| lt_ft_xthead | TYPE STANDARD TABLE OF TCATALOG, " | |||
| lt_ft_xvbadr | TYPE STANDARD TABLE OF SADRVB, " | |||
| lt_ft_yvbadr | TYPE STANDARD TABLE OF SADRVB. " |
|   CALL FUNCTION 'SD_CAS_CHANGE_DOCUMENT_CREATE' "NOTRANSL: Änderungsbelege für CAS-Belege anlegen |
| TABLES | ||
| FT_XVBKA | = lt_ft_xvbka | |
| FT_YVBKA | = lt_ft_yvbka | |
| FT_XVBPA | = lt_ft_xvbpa | |
| FT_YVBPA | = lt_ft_yvbpa | |
| FT_XVBUK | = lt_ft_xvbuk | |
| FT_YVBUK | = lt_ft_yvbuk | |
| FT_XTHEAD | = lt_ft_xthead | |
| FT_XVBADR | = lt_ft_xvbadr | |
| FT_YVBADR | = lt_ft_yvbadr | |
| . " SD_CAS_CHANGE_DOCUMENT_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM SD_CAS_CHANGE_DOCUMENT_CREATE
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