SAP BUPA_PFCT_REMOVEFUNCTION Function Module for SAP BP, BAPI: Delete Partner Function

Search SAP Function Modules

BUPA_PFCT_REMOVEFUNCTION is a standard bupa pfct removefunction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAP BP, BAPI: Delete Partner Function 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 bupa pfct removefunction FM, simply by entering the name BUPA_PFCT_REMOVEFUNCTION into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRM_BUPA_FRG0080_INTERN
Program Name: SAPLCRM_BUPA_FRG0080_INTERN
Main Program: SAPLCRM_BUPA_FRG0080_INTERN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BUPA_PFCT_REMOVEFUNCTION 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 'BUPA_PFCT_REMOVEFUNCTION'"SAP BP, BAPI: Delete Partner Function
  EXPORTING
*  IV_PARTNER1 =  "Business Partner 1
*  IV_PARTNERGUID1 =  "
*  IV_SALES_AREA =  "BAPI Structure for Sales Area
   IV_BPFUNCTION =  "Partner Function
*  IV_PARTNER2 =  "Business Partner Number 2
*  IV_PARTNERGUID2 =  "
*  IV_TESTRUN = ' ' "
*  IV_X_SAVE = 'X' "
*  IV_SHOW_ALL = 'X' "

TABLES
*  ET_RETURN =  "Messages

.

IMPORTING Parameters details for BUPA_PFCT_REMOVEFUNCTION

IV_PARTNER1 - Business Partner 1

Data type: BAPIBUS1006_RELHEAD-BUSINESSPARTNER1
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_PARTNERGUID1 -

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

IV_SALES_AREA - BAPI Structure for Sales Area

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

IV_BPFUNCTION - Partner Function

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

IV_PARTNER2 - Business Partner Number 2

Data type: BAPIBUS1006_RELHEAD-BUSINESSPARTNER2
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_PARTNERGUID2 -

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

IV_TESTRUN -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_X_SAVE -

Data type: BOOLE-BOOLE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SHOW_ALL -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BUPA_PFCT_REMOVEFUNCTION

ET_RETURN - Messages

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

Copy and paste ABAP code example for BUPA_PFCT_REMOVEFUNCTION 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.

ABAP code using 7.40 inline data declarations to call FM BUPA_PFCT_REMOVEFUNCTION

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