SAP ESFM_GVA_TRANSACTIONS Function Module for ESFM: GVA transactions by calling FM









ESFM_GVA_TRANSACTIONS is a standard esfm gva transactions SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ESFM: GVA transactions by calling FM 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 esfm gva transactions FM, simply by entering the name ESFM_GVA_TRANSACTIONS into the relevant SAP transaction such as SE37 or SE38.

Function Group: ESFM_GVA_WF
Program Name: SAPLESFM_GVA_WF
Main Program: SAPLESFM_GVA_WF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ESFM_GVA_TRANSACTIONS 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 'ESFM_GVA_TRANSACTIONS'"ESFM: GVA transactions by calling FM
  EXPORTING
   IP_GVANR =  "ESFM: Grouped value adjustment Document number
   IP_ACTIVITY =  "Activities for funds reservations
*  IP_FLG_MULTIPLE =  "Boolean variable
*  IP_SETLOCK =  "Document Block for Value Adjustment Document
*  IP_STATUS =  "Authorization Status (Refused, Confirmed)
*  IP_FLG_BO_CALL =  "Boolean variable

CHANGING
*  CP_REASON =  "Value adjustment: Decision reason for Workflow
*  CP_APPROVE =  "Authorization Status (Refused, Confirmed)
*  CP_FLG_FINAL =  "Final decision indicator

EXCEPTIONS
   DOCUMENT_NOT_FOUND = 1    ACTIVITY_NOT_FOUND = 2    CANCELLED = 3    UPDATE_FAILED = 4
.



IMPORTING Parameters details for ESFM_GVA_TRANSACTIONS

IP_GVANR - ESFM: Grouped value adjustment Document number

Data type: ESFM_GVANR
Optional: No
Call by Reference: Yes

IP_ACTIVITY - Activities for funds reservations

Data type: FMRE_AUTH
Optional: No
Call by Reference: Yes

IP_FLG_MULTIPLE - Boolean variable

Data type: BOOLE
Optional: Yes
Call by Reference: Yes

IP_SETLOCK - Document Block for Value Adjustment Document

Data type: FMRPMLOCK
Optional: Yes
Call by Reference: Yes

IP_STATUS - Authorization Status (Refused, Confirmed)

Data type: FMRAPPSTATUS
Optional: Yes
Call by Reference: Yes

IP_FLG_BO_CALL - Boolean variable

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for ESFM_GVA_TRANSACTIONS

CP_REASON - Value adjustment: Decision reason for Workflow

Data type: FMRSUPPREASON
Optional: Yes
Call by Reference: Yes

CP_APPROVE - Authorization Status (Refused, Confirmed)

Data type: APP_RCODE
Optional: Yes
Call by Reference: Yes

CP_FLG_FINAL - Final decision indicator

Data type: WFTRIGGER
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

DOCUMENT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ACTIVITY_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CANCELLED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

UPDATE_FAILED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ESFM_GVA_TRANSACTIONS 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_ip_gvanr  TYPE ESFM_GVANR, "   
lv_cp_reason  TYPE FMRSUPPREASON, "   
lv_document_not_found  TYPE FMRSUPPREASON, "   
lv_cp_approve  TYPE APP_RCODE, "   
lv_ip_activity  TYPE FMRE_AUTH, "   
lv_activity_not_found  TYPE FMRE_AUTH, "   
lv_cancelled  TYPE FMRE_AUTH, "   
lv_cp_flg_final  TYPE WFTRIGGER, "   
lv_ip_flg_multiple  TYPE BOOLE, "   
lv_ip_setlock  TYPE FMRPMLOCK, "   
lv_update_failed  TYPE FMRPMLOCK, "   
lv_ip_status  TYPE FMRAPPSTATUS, "   
lv_ip_flg_bo_call  TYPE CHAR1. "   

  CALL FUNCTION 'ESFM_GVA_TRANSACTIONS'  "ESFM: GVA transactions by calling FM
    EXPORTING
         IP_GVANR = lv_ip_gvanr
         IP_ACTIVITY = lv_ip_activity
         IP_FLG_MULTIPLE = lv_ip_flg_multiple
         IP_SETLOCK = lv_ip_setlock
         IP_STATUS = lv_ip_status
         IP_FLG_BO_CALL = lv_ip_flg_bo_call
    CHANGING
         CP_REASON = lv_cp_reason
         CP_APPROVE = lv_cp_approve
         CP_FLG_FINAL = lv_cp_flg_final
    EXCEPTIONS
        DOCUMENT_NOT_FOUND = 1
        ACTIVITY_NOT_FOUND = 2
        CANCELLED = 3
        UPDATE_FAILED = 4
. " ESFM_GVA_TRANSACTIONS




ABAP code using 7.40 inline data declarations to call FM ESFM_GVA_TRANSACTIONS

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!