SAP /ACCGO/ACM_RECON_UPD_KONVD_PAD Function Module for Recon Report: KONVD update for Third Party Purchase
/ACCGO/ACM_RECON_UPD_KONVD_PAD is a standard /accgo/acm recon upd konvd pad SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Recon Report: KONVD update for Third Party Purchase 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/acm recon upd konvd pad FM, simply by entering the name /ACCGO/ACM_RECON_UPD_KONVD_PAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: /ACCGO/ACM_RECON_UPDATE
Program Name: /ACCGO/SAPLACM_RECON_UPDATE
Main Program: /ACCGO/SAPLACM_RECON_UPDATE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function /ACCGO/ACM_RECON_UPD_KONVD_PAD 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/ACM_RECON_UPD_KONVD_PAD'"Recon Report: KONVD update for Third Party Purchase.
EXPORTING
IT_STAT_STL = "Individual Object Status
IT_STAT_APPDOC = "Individual Object Status
IT_APPDOC_ITEMS = "Table Type for RECON for Appdoc & Contract information
IT_CAS_CAI = "Contract application items
IT_APPDATA = "Table type for application details
IT_KONVD = "Table Type for CMM_VLOGP_KONVD
IV_TIMESTAMP = "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
IMPORTING
ET_MESSAGES = "Application Log: Table with Messages
EV_UNASSIGNED_APPDOC_COUNT = "
IMPORTING Parameters details for /ACCGO/ACM_RECON_UPD_KONVD_PAD
IT_STAT_STL - Individual Object Status
Data type: JEST_TTYOptional: No
Call by Reference: No ( called with pass by value option)
IT_STAT_APPDOC - Individual Object Status
Data type: JEST_TTYOptional: No
Call by Reference: No ( called with pass by value option)
IT_APPDOC_ITEMS - Table Type for RECON for Appdoc & Contract information
Data type: /ACCGO/TT_RECON_APP_CONTROptional: No
Call by Reference: No ( called with pass by value option)
IT_CAS_CAI - Contract application items
Data type: /ACCGO/CAS_TT_CAIOptional: No
Call by Reference: No ( called with pass by value option)
IT_APPDATA - Table type for application details
Data type: /ACCGO/CAS_TT_APPLDOC_DETAILOptional: No
Call by Reference: No ( called with pass by value option)
IT_KONVD - Table Type for CMM_VLOGP_KONVD
Data type: CMM_VLOGP_KONVD_TOptional: No
Call by Reference: No ( called with pass by value option)
IV_TIMESTAMP - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
Data type: TZNTSTMPSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for /ACCGO/ACM_RECON_UPD_KONVD_PAD
ET_MESSAGES - Application Log: Table with Messages
Data type: BAL_T_MSGOptional: No
Call by Reference: No ( called with pass by value option)
EV_UNASSIGNED_APPDOC_COUNT -
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for /ACCGO/ACM_RECON_UPD_KONVD_PAD 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_et_messages | TYPE BAL_T_MSG, " | |||
lv_it_stat_stl | TYPE JEST_TTY, " | |||
lv_it_stat_appdoc | TYPE JEST_TTY, " | |||
lv_ev_unassigned_appdoc_count | TYPE I, " | |||
lv_it_appdoc_items | TYPE /ACCGO/TT_RECON_APP_CONTR, " | |||
lv_it_cas_cai | TYPE /ACCGO/CAS_TT_CAI, " | |||
lv_it_appdata | TYPE /ACCGO/CAS_TT_APPLDOC_DETAIL, " | |||
lv_it_konvd | TYPE CMM_VLOGP_KONVD_T, " | |||
lv_iv_timestamp | TYPE TZNTSTMPS. " |
  CALL FUNCTION '/ACCGO/ACM_RECON_UPD_KONVD_PAD' "Recon Report: KONVD update for Third Party Purchase |
EXPORTING | ||
IT_STAT_STL | = lv_it_stat_stl | |
IT_STAT_APPDOC | = lv_it_stat_appdoc | |
IT_APPDOC_ITEMS | = lv_it_appdoc_items | |
IT_CAS_CAI | = lv_it_cas_cai | |
IT_APPDATA | = lv_it_appdata | |
IT_KONVD | = lv_it_konvd | |
IV_TIMESTAMP | = lv_iv_timestamp | |
IMPORTING | ||
ET_MESSAGES | = lv_et_messages | |
EV_UNASSIGNED_APPDOC_COUNT | = lv_ev_unassigned_appdoc_count | |
. " /ACCGO/ACM_RECON_UPD_KONVD_PAD |
ABAP code using 7.40 inline data declarations to call FM /ACCGO/ACM_RECON_UPD_KONVD_PAD
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