SAP UKM_BP_BUPA_WC Function Module for









UKM_BP_BUPA_WC is a standard ukm bp bupa wc 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 ukm bp bupa wc FM, simply by entering the name UKM_BP_BUPA_WC into the relevant SAP transaction such as SE37 or SE38.

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



Function UKM_BP_BUPA_WC 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 'UKM_BP_BUPA_WC'"
  EXPORTING
   IV_BP_NUMBER =  "Business Partner Number
*  IV_SWITCH_PARTNER =  "Single-Character Indicator
   IV_ROLE =  "Business Partner Role
   IV_SUB_HEADER_ID =  "Private: Key of Additional Header Data
   IV_SCREEN =  "Screen
*  IV_ACTIVITY =  "Activity Category
*  IV_LOCATOR_VISIBLE =  "Single-Character Indicator
*  IV_SAVE_ENABLE =  "Single-Character Indicator
*  IV_SWITCH_ACTIVITY =  "Single-Character Indicator
*  IV_SWITCH_ROLE =  "Single-Character Indicator

 IMPORTING
   ET_MESSAGES =  "Table with BAPI Return Information

EXCEPTIONS
   OTHERS = 1
.



IMPORTING Parameters details for UKM_BP_BUPA_WC

IV_BP_NUMBER - Business Partner Number

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

IV_SWITCH_PARTNER - Single-Character Indicator

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

IV_ROLE - Business Partner Role

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

IV_SUB_HEADER_ID - Private: Key of Additional Header Data

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

IV_SCREEN - Screen

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

IV_ACTIVITY - Activity Category

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

IV_LOCATOR_VISIBLE - Single-Character Indicator

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

IV_SAVE_ENABLE - Single-Character Indicator

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

IV_SWITCH_ACTIVITY - Single-Character Indicator

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

IV_SWITCH_ROLE - Single-Character Indicator

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

EXPORTING Parameters details for UKM_BP_BUPA_WC

ET_MESSAGES - Table with BAPI Return Information

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

EXCEPTIONS details

OTHERS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UKM_BP_BUPA_WC 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_others  TYPE STRING, "   
lv_et_messages  TYPE BAPIRETTAB, "   
lv_iv_bp_number  TYPE BU_PARTNER, "   
lv_iv_switch_partner  TYPE CHAR1, "   
lv_iv_role  TYPE BU_ROLE, "   
lv_iv_sub_header_id  TYPE BU_SUB_HEADER_ID, "   
lv_iv_screen  TYPE BU_DYNID, "   
lv_iv_activity  TYPE BU_AKTYP, "   
lv_iv_locator_visible  TYPE CHAR1, "   
lv_iv_save_enable  TYPE CHAR1, "   
lv_iv_switch_activity  TYPE CHAR1, "   
lv_iv_switch_role  TYPE CHAR1. "   

  CALL FUNCTION 'UKM_BP_BUPA_WC'  "
    EXPORTING
         IV_BP_NUMBER = lv_iv_bp_number
         IV_SWITCH_PARTNER = lv_iv_switch_partner
         IV_ROLE = lv_iv_role
         IV_SUB_HEADER_ID = lv_iv_sub_header_id
         IV_SCREEN = lv_iv_screen
         IV_ACTIVITY = lv_iv_activity
         IV_LOCATOR_VISIBLE = lv_iv_locator_visible
         IV_SAVE_ENABLE = lv_iv_save_enable
         IV_SWITCH_ACTIVITY = lv_iv_switch_activity
         IV_SWITCH_ROLE = lv_iv_switch_role
    IMPORTING
         ET_MESSAGES = lv_et_messages
    EXCEPTIONS
        OTHERS = 1
. " UKM_BP_BUPA_WC




ABAP code using 7.40 inline data declarations to call FM UKM_BP_BUPA_WC

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!