SAP ISH_BUP_API_MAP_PARTNER Function Module for IS-H: API layer to Map IS-H to SAP BP Part. No. for Addnl. HC-Specific BP









ISH_BUP_API_MAP_PARTNER is a standard ish bup api map partner SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-H: API layer to Map IS-H to SAP BP Part. No. for Addnl. HC-Specific BP 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 ish bup api map partner FM, simply by entering the name ISH_BUP_API_MAP_PARTNER into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_BUP_API_MAP_PARTNER 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 'ISH_BUP_API_MAP_PARTNER'"IS-H: API layer to Map IS-H to SAP BP Part. No. for Addnl. HC-Specific BP
EXPORTING
* I_OLD_PARTNER = "IS-H: Old Business Partner Number
* IT_OLD_PARTNER = "Table of Old Business Partner
* IT_OLD_PARTNER_RNG = "IS-H: Range Table for Business Partners
* I_MAP_IND = '1' "Mapping Indicator From GPART to PARTNER

IMPORTING
E_PARTNER = "Business Partner Number
ET_PARTNER = "Table of Business Partner Numbers for Addnl. HC-Specific BP
ET_PART_MULT_KEY = "Table of Business Partners for Partial Key DB Access
ET_RC = "IS-H: Table Type for Structure BAPIRET2
.



IMPORTING Parameters details for ISH_BUP_API_MAP_PARTNER

I_OLD_PARTNER - IS-H: Old Business Partner Number

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

IT_OLD_PARTNER - Table of Old Business Partner

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

IT_OLD_PARTNER_RNG - IS-H: Range Table for Business Partners

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

I_MAP_IND - Mapping Indicator From GPART to PARTNER

Data type: CHAR1
Default: '1'
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ISH_BUP_API_MAP_PARTNER

E_PARTNER - Business Partner Number

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

ET_PARTNER - Table of Business Partner Numbers for Addnl. HC-Specific BP

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

ET_PART_MULT_KEY - Table of Business Partners for Partial Key DB Access

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

ET_RC - IS-H: Table Type for Structure BAPIRET2

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

Copy and paste ABAP code example for ISH_BUP_API_MAP_PARTNER 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_e_partner  TYPE RNBUP_PK, "   
lv_i_old_partner  TYPE GPARTNER, "   
lv_et_partner  TYPE ISH_T_BUP_PK, "   
lv_it_old_partner  TYPE ISH_T_GPART, "   
lv_et_part_mult_key  TYPE ISH_T_BUP, "   
lv_it_old_partner_rng  TYPE ISH_YT_GPARTNER, "   
lv_et_rc  TYPE ISH_BAPIRET2_TAB_TYPE, "   
lv_i_map_ind  TYPE CHAR1. "   '1'

  CALL FUNCTION 'ISH_BUP_API_MAP_PARTNER'  "IS-H: API layer to Map IS-H to SAP BP Part. No. for Addnl. HC-Specific BP
    EXPORTING
         I_OLD_PARTNER = lv_i_old_partner
         IT_OLD_PARTNER = lv_it_old_partner
         IT_OLD_PARTNER_RNG = lv_it_old_partner_rng
         I_MAP_IND = lv_i_map_ind
    IMPORTING
         E_PARTNER = lv_e_partner
         ET_PARTNER = lv_et_partner
         ET_PART_MULT_KEY = lv_et_part_mult_key
         ET_RC = lv_et_rc
. " ISH_BUP_API_MAP_PARTNER




ABAP code using 7.40 inline data declarations to call FM ISH_BUP_API_MAP_PARTNER

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.

 
 
 
 
 
 
 
DATA(ld_i_map_ind) = '1'.
 


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!