SAP HCM_WRITE_BP Function Module for









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

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



Function HCM_WRITE_BP 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 'HCM_WRITE_BP'"
  EXPORTING
   IV_BP_NUMBER =  "
   IS_BP_FAX =  "
   IS_BP_FAX_X =  "
   IS_BP_SMTP =  "
   IS_BP_SMTP_X =  "
   IS_BP_CENTRAL =  "
   IS_BP_CENTRAL_X =  "
   IS_BP_PERSON =  "
   IS_BP_PERSON_X =  "
   IS_BP_ADDRESS =  "
   IS_BP_ADDRESS_X =  "
   IS_BP_TEL =  "
   IS_BP_TEL_X =  "

 IMPORTING
   EV_BP_NUMBER =  "
   EV_BP_GUID =  "
   ET_ERRORS =  "
.



IMPORTING Parameters details for HCM_WRITE_BP

IV_BP_NUMBER -

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

IS_BP_FAX -

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

IS_BP_FAX_X -

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

IS_BP_SMTP -

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

IS_BP_SMTP_X -

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

IS_BP_CENTRAL -

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

IS_BP_CENTRAL_X -

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

IS_BP_PERSON -

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

IS_BP_PERSON_X -

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

IS_BP_ADDRESS -

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

IS_BP_ADDRESS_X -

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

IS_BP_TEL -

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

IS_BP_TEL_X -

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

EXPORTING Parameters details for HCM_WRITE_BP

EV_BP_NUMBER -

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

EV_BP_GUID -

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

ET_ERRORS -

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

Copy and paste ABAP code example for HCM_WRITE_BP 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_bp_number  TYPE BU_PARTNER, "   
lv_iv_bp_number  TYPE BU_PARTNER, "   
lv_is_bp_fax  TYPE BAPIADFAX, "   
lv_is_bp_fax_x  TYPE BAPIADFAXX, "   
lv_is_bp_smtp  TYPE BAPIADSMTP, "   
lv_is_bp_smtp_x  TYPE BAPIADSMTX, "   
lv_ev_bp_guid  TYPE BU_PARTNER_GUID, "   
lv_is_bp_central  TYPE BAPIBUS1006_CENTRAL, "   
lv_et_errors  TYPE BAPIRET2_T, "   
lv_is_bp_central_x  TYPE BAPIBUS1006_CENTRAL_X, "   
lv_is_bp_person  TYPE BAPIBUS1006_CENTRAL_PERSON, "   
lv_is_bp_person_x  TYPE BAPIBUS1006_CENTRAL_PERSON_X, "   
lv_is_bp_address  TYPE BAPIBUS1006_ADDRESS, "   
lv_is_bp_address_x  TYPE BAPIBUS1006_ADDRESS_X, "   
lv_is_bp_tel  TYPE BAPIADTEL, "   
lv_is_bp_tel_x  TYPE BAPIADTELX. "   

  CALL FUNCTION 'HCM_WRITE_BP'  "
    EXPORTING
         IV_BP_NUMBER = lv_iv_bp_number
         IS_BP_FAX = lv_is_bp_fax
         IS_BP_FAX_X = lv_is_bp_fax_x
         IS_BP_SMTP = lv_is_bp_smtp
         IS_BP_SMTP_X = lv_is_bp_smtp_x
         IS_BP_CENTRAL = lv_is_bp_central
         IS_BP_CENTRAL_X = lv_is_bp_central_x
         IS_BP_PERSON = lv_is_bp_person
         IS_BP_PERSON_X = lv_is_bp_person_x
         IS_BP_ADDRESS = lv_is_bp_address
         IS_BP_ADDRESS_X = lv_is_bp_address_x
         IS_BP_TEL = lv_is_bp_tel
         IS_BP_TEL_X = lv_is_bp_tel_x
    IMPORTING
         EV_BP_NUMBER = lv_ev_bp_number
         EV_BP_GUID = lv_ev_bp_guid
         ET_ERRORS = lv_et_errors
. " HCM_WRITE_BP




ABAP code using 7.40 inline data declarations to call FM HCM_WRITE_BP

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!