SAP ISH_BUP_API_AUTH Function Module for IS-H: API Authorization Check for Addnl HC-Specific BP Data
ISH_BUP_API_AUTH is a standard ish bup api auth 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 Authorization Check for Addnl HC-Specific BP Data 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 auth FM, simply by entering the name ISH_BUP_API_AUTH 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_AUTH 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_AUTH'"IS-H: API Authorization Check for Addnl HC-Specific BP Data.
EXPORTING
I_AUTH = "Business Partner Number
I_ACTVT = "Activity
IMPORTING
E_RC = "Return Value of ABAP Statements
IMPORTING Parameters details for ISH_BUP_API_AUTH
I_AUTH - Business Partner Number
Data type: RNBP_AUTHOptional: No
Call by Reference: Yes
I_ACTVT - Activity
Data type: TACT-ACTVTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISH_BUP_API_AUTH
E_RC - Return Value of ABAP Statements
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISH_BUP_API_AUTH 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_rc | TYPE BAPIRET2, " | |||
| lv_i_auth | TYPE RNBP_AUTH, " | |||
| lv_i_actvt | TYPE TACT-ACTVT. " |
|   CALL FUNCTION 'ISH_BUP_API_AUTH' "IS-H: API Authorization Check for Addnl HC-Specific BP Data |
| EXPORTING | ||
| I_AUTH | = lv_i_auth | |
| I_ACTVT | = lv_i_actvt | |
| IMPORTING | ||
| E_RC | = lv_e_rc | |
| . " ISH_BUP_API_AUTH | ||
ABAP code using 7.40 inline data declarations to call FM ISH_BUP_API_AUTH
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.| "SELECT single ACTVT FROM TACT INTO @DATA(ld_i_actvt). | ||||
Search for further information about these or an SAP related objects