SAP /ACCGO/CAS_SAVE_DPQS_NEGO_DATA Function Module for Update DPQS Negotiate Data
/ACCGO/CAS_SAVE_DPQS_NEGO_DATA is a standard /accgo/cas save dpqs nego data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update DPQS Negotiate Data 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 save dpqs nego data FM, simply by entering the name /ACCGO/CAS_SAVE_DPQS_NEGO_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: /ACCGO/CAS_SETTLEMENT_UI
Program Name: /ACCGO/SAPLCAS_SETTLEMENT_UI
Main Program: /ACCGO/SAPLCAS_SETTLEMENT_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1
Function /ACCGO/CAS_SAVE_DPQS_NEGO_DATA 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_SAVE_DPQS_NEGO_DATA'"Update DPQS Negotiate Data.
EXPORTING
* IM_QREP_MAIN_DATA = "
* IM_QREP_NEGOTIATE = "
IMPORTING Parameters details for /ACCGO/CAS_SAVE_DPQS_NEGO_DATA
IM_QREP_MAIN_DATA -
Data type: /ACCGO/CAS_TT_QR_AP_MAINOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_QREP_NEGOTIATE -
Data type: /ACCGO/CAS_TT_T_QR_AP_NOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /ACCGO/CAS_SAVE_DPQS_NEGO_DATA 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_qrep_main_data | TYPE /ACCGO/CAS_TT_QR_AP_MAIN, " | |||
lv_im_qrep_negotiate | TYPE /ACCGO/CAS_TT_T_QR_AP_N. " |
  CALL FUNCTION '/ACCGO/CAS_SAVE_DPQS_NEGO_DATA' "Update DPQS Negotiate Data |
EXPORTING | ||
IM_QREP_MAIN_DATA | = lv_im_qrep_main_data | |
IM_QREP_NEGOTIATE | = lv_im_qrep_negotiate | |
. " /ACCGO/CAS_SAVE_DPQS_NEGO_DATA |
ABAP code using 7.40 inline data declarations to call FM /ACCGO/CAS_SAVE_DPQS_NEGO_DATA
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