SAP SAVE_VENDOR_CUP_CIG_IT Function Module for save vendor cup/cig
SAVE_VENDOR_CUP_CIG_IT is a standard save vendor cup cig it SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for save vendor cup/cig 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 save vendor cup cig it FM, simply by entering the name SAVE_VENDOR_CUP_CIG_IT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUG_IT
Program Name: SAPLCUG_IT
Main Program: SAPLCUG_IT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SAVE_VENDOR_CUP_CIG_IT 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 'SAVE_VENDOR_CUP_CIG_IT'"save vendor cup/cig.
EXPORTING
I_LFA1 = "Vendor Master (General Section)
I_LFB1 = "Vendor Master (Company Code)
T_LFBK = "Vendor Master (Bank Details)
IM_AKTYP = "Activity category in SAP transaction
IMPORTING Parameters details for SAVE_VENDOR_CUP_CIG_IT
I_LFA1 - Vendor Master (General Section)
Data type: LFA1Optional: No
Call by Reference: Yes
I_LFB1 - Vendor Master (Company Code)
Data type: LFB1Optional: No
Call by Reference: Yes
T_LFBK - Vendor Master (Bank Details)
Data type: FLFBK_TABOptional: No
Call by Reference: Yes
IM_AKTYP - Activity category in SAP transaction
Data type: AKTYPOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SAVE_VENDOR_CUP_CIG_IT 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_i_lfa1 | TYPE LFA1, " | |||
| lv_i_lfb1 | TYPE LFB1, " | |||
| lv_t_lfbk | TYPE FLFBK_TAB, " | |||
| lv_im_aktyp | TYPE AKTYP. " |
|   CALL FUNCTION 'SAVE_VENDOR_CUP_CIG_IT' "save vendor cup/cig |
| EXPORTING | ||
| I_LFA1 | = lv_i_lfa1 | |
| I_LFB1 | = lv_i_lfb1 | |
| T_LFBK | = lv_t_lfbk | |
| IM_AKTYP | = lv_im_aktyp | |
| . " SAVE_VENDOR_CUP_CIG_IT | ||
ABAP code using 7.40 inline data declarations to call FM SAVE_VENDOR_CUP_CIG_IT
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