SAP META_CFOLDER_VENDOR_WA_CLOSE Function Module for









META_CFOLDER_VENDOR_WA_CLOSE is a standard meta cfolder vendor wa close SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 meta cfolder vendor wa close FM, simply by entering the name META_CFOLDER_VENDOR_WA_CLOSE into the relevant SAP transaction such as SE37 or SE38.

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



Function META_CFOLDER_VENDOR_WA_CLOSE 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 'META_CFOLDER_VENDOR_WA_CLOSE'"
EXPORTING
IV_LOGICAL_SYSTEM = "
* IV_CFX_AREA_URL = "SAP System, User Logon Name
* IV_CFX_AREA_GUID = "Globally Unique Identifier
* IV_USERNAME = SY-UNAME "

TABLES
RETURN = "Returnparameter
.



IMPORTING Parameters details for META_CFOLDER_VENDOR_WA_CLOSE

IV_LOGICAL_SYSTEM -

Data type: BBP_BACKEND_DEST-LOG_SYS
Optional: No
Call by Reference: Yes

IV_CFX_AREA_URL - SAP System, User Logon Name

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

IV_CFX_AREA_GUID - Globally Unique Identifier

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

IV_USERNAME -

Data type: SY-UNAME
Default: SY-UNAME
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for META_CFOLDER_VENDOR_WA_CLOSE

RETURN - Returnparameter

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

Copy and paste ABAP code example for META_CFOLDER_VENDOR_WA_CLOSE 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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_logical_system  TYPE BBP_BACKEND_DEST-LOG_SYS, "   
lv_iv_cfx_area_url  TYPE STRING, "   
lv_iv_cfx_area_guid  TYPE BBP_GUID, "   
lv_iv_username  TYPE SY-UNAME. "   SY-UNAME

  CALL FUNCTION 'META_CFOLDER_VENDOR_WA_CLOSE'  "
    EXPORTING
         IV_LOGICAL_SYSTEM = lv_iv_logical_system
         IV_CFX_AREA_URL = lv_iv_cfx_area_url
         IV_CFX_AREA_GUID = lv_iv_cfx_area_guid
         IV_USERNAME = lv_iv_username
    TABLES
         RETURN = lt_return
. " META_CFOLDER_VENDOR_WA_CLOSE




ABAP code using 7.40 inline data declarations to call FM META_CFOLDER_VENDOR_WA_CLOSE

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 LOG_SYS FROM BBP_BACKEND_DEST INTO @DATA(ld_iv_logical_system).
 
 
 
"SELECT single UNAME FROM SY INTO @DATA(ld_iv_username).
DATA(ld_iv_username) = SY-UNAME.
 


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!