SAP USS_GET_STAKEHOLDER_HEADER Function Module for
USS_GET_STAKEHOLDER_HEADER is a standard uss get stakeholder header 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 uss get stakeholder header FM, simply by entering the name USS_GET_STAKEHOLDER_HEADER into the relevant SAP transaction such as SE37 or SE38.
Function Group: USS_SERV_BP
Program Name: SAPLUSS_SERV_BP
Main Program: SAPLUSS_SERV_BP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function USS_GET_STAKEHOLDER_HEADER 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 'USS_GET_STAKEHOLDER_HEADER'".
EXPORTING
I_SRM_PARTNER = "
IMPORTING
E_STRING1 = "
E_STRING2 = "
EXCEPTIONS
STAKEHOLDER_NOT_EXIST = 1
IMPORTING Parameters details for USS_GET_STAKEHOLDER_HEADER
I_SRM_PARTNER -
Data type: USS_Y_SRM_PARTNEROptional: No
Call by Reference: Yes
EXPORTING Parameters details for USS_GET_STAKEHOLDER_HEADER
E_STRING1 -
Data type: BUS000FLDS-DESCRIP_LONGOptional: No
Call by Reference: Yes
E_STRING2 -
Data type: BUS000FLDS-DESCRIP_LONGOptional: No
Call by Reference: Yes
EXCEPTIONS details
STAKEHOLDER_NOT_EXIST -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for USS_GET_STAKEHOLDER_HEADER 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_string1 | TYPE BUS000FLDS-DESCRIP_LONG, " | |||
| lv_i_srm_partner | TYPE USS_Y_SRM_PARTNER, " | |||
| lv_stakeholder_not_exist | TYPE USS_Y_SRM_PARTNER, " | |||
| lv_e_string2 | TYPE BUS000FLDS-DESCRIP_LONG. " |
|   CALL FUNCTION 'USS_GET_STAKEHOLDER_HEADER' " |
| EXPORTING | ||
| I_SRM_PARTNER | = lv_i_srm_partner | |
| IMPORTING | ||
| E_STRING1 | = lv_e_string1 | |
| E_STRING2 | = lv_e_string2 | |
| EXCEPTIONS | ||
| STAKEHOLDER_NOT_EXIST = 1 | ||
| . " USS_GET_STAKEHOLDER_HEADER | ||
ABAP code using 7.40 inline data declarations to call FM USS_GET_STAKEHOLDER_HEADER
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 DESCRIP_LONG FROM BUS000FLDS INTO @DATA(ld_e_string1). | ||||
| "SELECT single DESCRIP_LONG FROM BUS000FLDS INTO @DATA(ld_e_string2). | ||||
Search for further information about these or an SAP related objects