SAP ISH_BP_API_PARTNER_GET Function Module for IS-H: Check Status of the Switch and Map GPART to PARTNER









ISH_BP_API_PARTNER_GET is a standard ish bp api partner get 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: Check Status of the Switch and Map GPART to PARTNER 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 bp api partner get FM, simply by entering the name ISH_BP_API_PARTNER_GET 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_BP_API_PARTNER_GET 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_BP_API_PARTNER_GET'"IS-H: Check Status of the Switch and Map GPART to PARTNER
  EXPORTING
*  I_GPARTNER =  "GPART Field for Addnl HC Business Partner
*  IT_GPARTNER =  "Table of Old Business Partner
*  IT_GPARTNER_RNG =  "IS-H: Range Table for Business Partners
*  I_MAP_IND = '1' "Mapping Indicator From GPART to PARTNER

 IMPORTING
   E_BPK =  "Key Fields of Addnl HC Business Partner
   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
   E_STATUS =  "Status of BP Switch
   ET_RC =  "IS-H: Table Type for Structure BAPIRET2
.



IMPORTING Parameters details for ISH_BP_API_PARTNER_GET

I_GPARTNER - GPART Field for Addnl HC Business Partner

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

IT_GPARTNER - Table of Old Business Partner

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

IT_GPARTNER_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_BP_API_PARTNER_GET

E_BPK - Key Fields of Addnl HC Business Partner

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

E_STATUS - Status of BP Switch

Data type: ISH_ON_OFF
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_BP_API_PARTNER_GET 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_bpk  TYPE RNBUP_PK, "   
lv_i_gpartner  TYPE RNBUP_GPART, "   
lv_et_partner  TYPE ISH_T_BUP_PK, "   
lv_it_gpartner  TYPE ISH_T_GPART, "   
lv_it_gpartner_rng  TYPE ISH_YT_GPARTNER, "   
lv_et_part_mult_key  TYPE ISH_T_BUP, "   
lv_e_status  TYPE ISH_ON_OFF, "   
lv_i_map_ind  TYPE CHAR1, "   '1'
lv_et_rc  TYPE ISH_BAPIRET2_TAB_TYPE. "   

  CALL FUNCTION 'ISH_BP_API_PARTNER_GET'  "IS-H: Check Status of the Switch and Map GPART to PARTNER
    EXPORTING
         I_GPARTNER = lv_i_gpartner
         IT_GPARTNER = lv_it_gpartner
         IT_GPARTNER_RNG = lv_it_gpartner_rng
         I_MAP_IND = lv_i_map_ind
    IMPORTING
         E_BPK = lv_e_bpk
         ET_PARTNER = lv_et_partner
         ET_PART_MULT_KEY = lv_et_part_mult_key
         E_STATUS = lv_e_status
         ET_RC = lv_et_rc
. " ISH_BP_API_PARTNER_GET




ABAP code using 7.40 inline data declarations to call FM ISH_BP_API_PARTNER_GET

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!