SAP FVD_CHK_PARTNER_CONFIRMATION Function Module for Check if the partner is to be released









FVD_CHK_PARTNER_CONFIRMATION is a standard fvd chk partner confirmation SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if the partner is to be released 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 fvd chk partner confirmation FM, simply by entering the name FVD_CHK_PARTNER_CONFIRMATION into the relevant SAP transaction such as SE37 or SE38.

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



Function FVD_CHK_PARTNER_CONFIRMATION 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 'FVD_CHK_PARTNER_CONFIRMATION'"Check if the partner is to be released
EXPORTING
I_PARTNR = "Business Partner Number
I_MSG_ID = "Message Class
I_MSG_NO = "Message number
I_MSG_TYPE = "Active message type

IMPORTING
E_MSG_TYPE = "Active message type
.



IMPORTING Parameters details for FVD_CHK_PARTNER_CONFIRMATION

I_PARTNR - Business Partner Number

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

I_MSG_ID - Message Class

Data type: BAL_S_MSG-MSGID
Optional: No
Call by Reference: Yes

I_MSG_NO - Message number

Data type: T100C-MSGNR
Optional: No
Call by Reference: Yes

I_MSG_TYPE - Active message type

Data type: T100C-MSGTS
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FVD_CHK_PARTNER_CONFIRMATION

E_MSG_TYPE - Active message type

Data type: T100C-MSGTS
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVD_CHK_PARTNER_CONFIRMATION 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_partnr  TYPE BU_PARTNER, "   
lv_e_msg_type  TYPE T100C-MSGTS, "   
lv_i_msg_id  TYPE BAL_S_MSG-MSGID, "   
lv_i_msg_no  TYPE T100C-MSGNR, "   
lv_i_msg_type  TYPE T100C-MSGTS. "   

  CALL FUNCTION 'FVD_CHK_PARTNER_CONFIRMATION'  "Check if the partner is to be released
    EXPORTING
         I_PARTNR = lv_i_partnr
         I_MSG_ID = lv_i_msg_id
         I_MSG_NO = lv_i_msg_no
         I_MSG_TYPE = lv_i_msg_type
    IMPORTING
         E_MSG_TYPE = lv_e_msg_type
. " FVD_CHK_PARTNER_CONFIRMATION




ABAP code using 7.40 inline data declarations to call FM FVD_CHK_PARTNER_CONFIRMATION

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.

 
"SELECT single MSGTS FROM T100C INTO @DATA(ld_e_msg_type).
 
"SELECT single MSGID FROM BAL_S_MSG INTO @DATA(ld_i_msg_id).
 
"SELECT single MSGNR FROM T100C INTO @DATA(ld_i_msg_no).
 
"SELECT single MSGTS FROM T100C INTO @DATA(ld_i_msg_type).
 


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!