SAP PI_BP_VEND_CHECK_UPLOAD_FLAG Function Module for NOTRANSL: Check Upload Flag









PI_BP_VEND_CHECK_UPLOAD_FLAG is a standard pi bp vend check upload flag SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Check Upload Flag 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 pi bp vend check upload flag FM, simply by entering the name PI_BP_VEND_CHECK_UPLOAD_FLAG into the relevant SAP transaction such as SE37 or SE38.

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



Function PI_BP_VEND_CHECK_UPLOAD_FLAG 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 'PI_BP_VEND_CHECK_UPLOAD_FLAG'"NOTRANSL: Check Upload Flag
IMPORTING
EV_UPLOAD_FLAG = "
EV_UPLOAD_CONSUMER = "User of R/3 Adaptor Functionality
.



EXPORTING Parameters details for PI_BP_VEND_CHECK_UPLOAD_FLAG

EV_UPLOAD_FLAG -

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

EV_UPLOAD_CONSUMER - User of R/3 Adaptor Functionality

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

Copy and paste ABAP code example for PI_BP_VEND_CHECK_UPLOAD_FLAG 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_ev_upload_flag  TYPE C, "   
lv_ev_upload_consumer  TYPE BAPICRMUH1-CONSUMER. "   

  CALL FUNCTION 'PI_BP_VEND_CHECK_UPLOAD_FLAG'  "NOTRANSL: Check Upload Flag
    IMPORTING
         EV_UPLOAD_FLAG = lv_ev_upload_flag
         EV_UPLOAD_CONSUMER = lv_ev_upload_consumer
. " PI_BP_VEND_CHECK_UPLOAD_FLAG




ABAP code using 7.40 inline data declarations to call FM PI_BP_VEND_CHECK_UPLOAD_FLAG

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 CONSUMER FROM BAPICRMUH1 INTO @DATA(ld_ev_upload_consumer).
 


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!