SAP /ACCGO/CAS_SO_CHECK_VBKD Function Module for Check Line Item Of Sales Order
/ACCGO/CAS_SO_CHECK_VBKD is a standard /accgo/cas so check vbkd SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Line Item Of Sales Order 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 so check vbkd FM, simply by entering the name /ACCGO/CAS_SO_CHECK_VBKD into the relevant SAP transaction such as SE37 or SE38.
Function Group: /ACCGO/CAS_SO_PLUGIN
Program Name: /ACCGO/SAPLCAS_SO_PLUGIN
Main Program: /ACCGO/SAPLCAS_SO_PLUGIN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /ACCGO/CAS_SO_CHECK_VBKD 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_SO_CHECK_VBKD'"Check Line Item Of Sales Order.
EXPORTING
FT180 = "Screen Sequence Control: Transaction Default Values
FXVBEP = "Table for structure VBAPVB
FVBEP = "Sales Document: Item Data
FTVAK = "Sales Document Types
FTVAP = "Sales Document: Item Categories
FDIALOG = "
FXVBAP = "Table for structure VBAPVB
FVBAK = "Sales Document: Header Data
FVBAP = "Sales Document: Item Data
FXVBKD = "Sales Document: Business Data
FXVBPA = "Sales Document: Partner
CHANGING
F_VBUV_LAST = "Table type for VBUVVB
F_VBUV_TAB = "Table type for VBUVVB
F_VBUV_DIA = "Table type for VBUVVB
FVBKD = "Sales Document: Business Data
IMPORTING Parameters details for /ACCGO/CAS_SO_CHECK_VBKD
FT180 - Screen Sequence Control: Transaction Default Values
Data type: T180Optional: No
Call by Reference: Yes
FXVBEP - Table for structure VBAPVB
Data type: VA_VBEPVB_TOptional: No
Call by Reference: Yes
FVBEP - Sales Document: Item Data
Data type: VBEPOptional: No
Call by Reference: Yes
FTVAK - Sales Document Types
Data type: TVAKOptional: No
Call by Reference: Yes
FTVAP - Sales Document: Item Categories
Data type: TVAPOptional: No
Call by Reference: Yes
FDIALOG -
Data type: COptional: No
Call by Reference: Yes
FXVBAP - Table for structure VBAPVB
Data type: VA_VBAPVB_TOptional: No
Call by Reference: Yes
FVBAK - Sales Document: Header Data
Data type: VBAKOptional: No
Call by Reference: Yes
FVBAP - Sales Document: Item Data
Data type: VBAPOptional: No
Call by Reference: Yes
FXVBKD - Sales Document: Business Data
Data type: VA_VBKDVB_TOptional: No
Call by Reference: Yes
FXVBPA - Sales Document: Partner
Data type: VBPA_TABOptional: No
Call by Reference: Yes
CHANGING Parameters details for /ACCGO/CAS_SO_CHECK_VBKD
F_VBUV_LAST - Table type for VBUVVB
Data type: VA_VBUVVB_TOptional: No
Call by Reference: Yes
F_VBUV_TAB - Table type for VBUVVB
Data type: VA_VBUVVB_TOptional: No
Call by Reference: Yes
F_VBUV_DIA - Table type for VBUVVB
Data type: VA_VBUVVB_TOptional: No
Call by Reference: Yes
FVBKD - Sales Document: Business Data
Data type: VBKDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for /ACCGO/CAS_SO_CHECK_VBKD 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_ft180 | TYPE T180, " | |||
lv_f_vbuv_last | TYPE VA_VBUVVB_T, " | |||
lv_fxvbep | TYPE VA_VBEPVB_T, " | |||
lv_fvbep | TYPE VBEP, " | |||
lv_ftvak | TYPE TVAK, " | |||
lv_f_vbuv_tab | TYPE VA_VBUVVB_T, " | |||
lv_ftvap | TYPE TVAP, " | |||
lv_f_vbuv_dia | TYPE VA_VBUVVB_T, " | |||
lv_fvbkd | TYPE VBKD, " | |||
lv_fdialog | TYPE C, " | |||
lv_fxvbap | TYPE VA_VBAPVB_T, " | |||
lv_fvbak | TYPE VBAK, " | |||
lv_fvbap | TYPE VBAP, " | |||
lv_fxvbkd | TYPE VA_VBKDVB_T, " | |||
lv_fxvbpa | TYPE VBPA_TAB. " |
  CALL FUNCTION '/ACCGO/CAS_SO_CHECK_VBKD' "Check Line Item Of Sales Order |
EXPORTING | ||
FT180 | = lv_ft180 | |
FXVBEP | = lv_fxvbep | |
FVBEP | = lv_fvbep | |
FTVAK | = lv_ftvak | |
FTVAP | = lv_ftvap | |
FDIALOG | = lv_fdialog | |
FXVBAP | = lv_fxvbap | |
FVBAK | = lv_fvbak | |
FVBAP | = lv_fvbap | |
FXVBKD | = lv_fxvbkd | |
FXVBPA | = lv_fxvbpa | |
CHANGING | ||
F_VBUV_LAST | = lv_f_vbuv_last | |
F_VBUV_TAB | = lv_f_vbuv_tab | |
F_VBUV_DIA | = lv_f_vbuv_dia | |
FVBKD | = lv_fvbkd | |
. " /ACCGO/CAS_SO_CHECK_VBKD |
ABAP code using 7.40 inline data declarations to call FM /ACCGO/CAS_SO_CHECK_VBKD
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