SAP /ACCGO/CAS_FM_APPDOC_SAVE Function Module for CA Application Document Save to DB









/ACCGO/CAS_FM_APPDOC_SAVE is a standard /accgo/cas fm appdoc save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CA Application Document Save to DB 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 fm appdoc save FM, simply by entering the name /ACCGO/CAS_FM_APPDOC_SAVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: /ACCGO/CAS_FG_DB
Program Name: /ACCGO/SAPLCAS_FG_DB
Main Program: /ACCGO/SAPLCAS_FG_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function /ACCGO/CAS_FM_APPDOC_SAVE 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_FM_APPDOC_SAVE'"CA Application Document Save to DB
  EXPORTING
*  IM_T_APPLDOC_H_I =  "Table Type for Header details of Contract Application Docume
*  IM_T_APPLDOC_I_I =  "Contract application items
*  IM_T_APPLDOC_I_B_I =  "CA Application Document Item Business data DB table
*  IM_T_APPLDOC_H_U =  "Table Type for Header details of Contract Application Docume
*  IM_T_APPLDOC_I_U =  "Contract application items
*  IM_T_APPLDOC_I_B_U =  "CA Application Document Item Business data DB table
*  IM_T_APPLDOC_I_D =  "Contract application items
*  IM_T_APPLDOC_I_B_D =  "CA Application Document Item Business data DB table
.



IMPORTING Parameters details for /ACCGO/CAS_FM_APPDOC_SAVE

IM_T_APPLDOC_H_I - Table Type for Header details of Contract Application Docume

Data type: /ACCGO/CAS_TT_CAH_DB_INT
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_T_APPLDOC_I_I - Contract application items

Data type: /ACCGO/CAS_TT_CAI_DB_INT
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_T_APPLDOC_I_B_I - CA Application Document Item Business data DB table

Data type: /ACCGO/CAS_TT_CAB_DB_INT
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_T_APPLDOC_H_U - Table Type for Header details of Contract Application Docume

Data type: /ACCGO/CAS_TT_CAH_DB_INT
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_T_APPLDOC_I_U - Contract application items

Data type: /ACCGO/CAS_TT_CAI_DB_INT
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_T_APPLDOC_I_B_U - CA Application Document Item Business data DB table

Data type: /ACCGO/CAS_TT_CAB_DB_INT
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_T_APPLDOC_I_D - Contract application items

Data type: /ACCGO/CAS_TT_CAI_DB_INT
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_T_APPLDOC_I_B_D - CA Application Document Item Business data DB table

Data type: /ACCGO/CAS_TT_CAB_DB_INT
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for /ACCGO/CAS_FM_APPDOC_SAVE 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_im_t_appldoc_h_i  TYPE /ACCGO/CAS_TT_CAH_DB_INT, "   
lv_im_t_appldoc_i_i  TYPE /ACCGO/CAS_TT_CAI_DB_INT, "   
lv_im_t_appldoc_i_b_i  TYPE /ACCGO/CAS_TT_CAB_DB_INT, "   
lv_im_t_appldoc_h_u  TYPE /ACCGO/CAS_TT_CAH_DB_INT, "   
lv_im_t_appldoc_i_u  TYPE /ACCGO/CAS_TT_CAI_DB_INT, "   
lv_im_t_appldoc_i_b_u  TYPE /ACCGO/CAS_TT_CAB_DB_INT, "   
lv_im_t_appldoc_i_d  TYPE /ACCGO/CAS_TT_CAI_DB_INT, "   
lv_im_t_appldoc_i_b_d  TYPE /ACCGO/CAS_TT_CAB_DB_INT. "   

  CALL FUNCTION '/ACCGO/CAS_FM_APPDOC_SAVE'  "CA Application Document Save to DB
    EXPORTING
         IM_T_APPLDOC_H_I = lv_im_t_appldoc_h_i
         IM_T_APPLDOC_I_I = lv_im_t_appldoc_i_i
         IM_T_APPLDOC_I_B_I = lv_im_t_appldoc_i_b_i
         IM_T_APPLDOC_H_U = lv_im_t_appldoc_h_u
         IM_T_APPLDOC_I_U = lv_im_t_appldoc_i_u
         IM_T_APPLDOC_I_B_U = lv_im_t_appldoc_i_b_u
         IM_T_APPLDOC_I_D = lv_im_t_appldoc_i_d
         IM_T_APPLDOC_I_B_D = lv_im_t_appldoc_i_b_d
. " /ACCGO/CAS_FM_APPDOC_SAVE




ABAP code using 7.40 inline data declarations to call FM /ACCGO/CAS_FM_APPDOC_SAVE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!