SAP BAPI_BUS2177_STAFF_DIST_GET Function Module for BAPI Role: Determine Demand Distribution
BAPI_BUS2177_STAFF_DIST_GET is a standard bapi bus2177 staff dist 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 BAPI Role: Determine Demand Distribution 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 bapi bus2177 staff dist get FM, simply by entering the name BAPI_BUS2177_STAFF_DIST_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: DPR_BUS2177
Program Name: SAPLDPR_BUS2177
Main Program: SAPLDPR_BUS2177
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_BUS2177_STAFF_DIST_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 'BAPI_BUS2177_STAFF_DIST_GET'"BAPI Role: Determine Demand Distribution.
EXPORTING
PROJECTROLE_GUID = "GUID for Project Role
IV_STAFFINGLINK_GUID = "GUID for Linking Role to Business Partner in BAPIs
IMPORTING
ES_DIST_ADMIN_DATA = "Distribution administration data
EV_DIST_GUID = "Application Object GUID
EV_ENTITY_GUID = "Application Object GUID
TABLES
ET_DISTRIBUTION = "Distribution data
* RETURN = "Return Parameters
IMPORTING Parameters details for BAPI_BUS2177_STAFF_DIST_GET
PROJECTROLE_GUID - GUID for Project Role
Data type: BAPI_TS_GUID-ROLE_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_STAFFINGLINK_GUID - GUID for Linking Role to Business Partner in BAPIs
Data type: BAPI_TS_GUID-STAFFING_LINK_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_BUS2177_STAFF_DIST_GET
ES_DIST_ADMIN_DATA - Distribution administration data
Data type: BAPI_TS_DIST_ADMIN_DATAOptional: No
Call by Reference: No ( called with pass by value option)
EV_DIST_GUID - Application Object GUID
Data type: DPR_TV_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
EV_ENTITY_GUID - Application Object GUID
Data type: DPR_TV_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_BUS2177_STAFF_DIST_GET
ET_DISTRIBUTION - Distribution data
Data type: BAPI_TS_DIST_DATAOptional: No
Call by Reference: No ( called with pass by value option)
RETURN - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_BUS2177_STAFF_DIST_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: | ||||
lt_et_distribution | TYPE STANDARD TABLE OF BAPI_TS_DIST_DATA, " | |||
lv_projectrole_guid | TYPE BAPI_TS_GUID-ROLE_GUID, " | |||
lv_es_dist_admin_data | TYPE BAPI_TS_DIST_ADMIN_DATA, " | |||
lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
lv_ev_dist_guid | TYPE DPR_TV_GUID, " | |||
lv_iv_staffinglink_guid | TYPE BAPI_TS_GUID-STAFFING_LINK_GUID, " | |||
lv_ev_entity_guid | TYPE DPR_TV_GUID. " |
  CALL FUNCTION 'BAPI_BUS2177_STAFF_DIST_GET' "BAPI Role: Determine Demand Distribution |
EXPORTING | ||
PROJECTROLE_GUID | = lv_projectrole_guid | |
IV_STAFFINGLINK_GUID | = lv_iv_staffinglink_guid | |
IMPORTING | ||
ES_DIST_ADMIN_DATA | = lv_es_dist_admin_data | |
EV_DIST_GUID | = lv_ev_dist_guid | |
EV_ENTITY_GUID | = lv_ev_entity_guid | |
TABLES | ||
ET_DISTRIBUTION | = lt_et_distribution | |
RETURN | = lt_return | |
. " BAPI_BUS2177_STAFF_DIST_GET |
ABAP code using 7.40 inline data declarations to call FM BAPI_BUS2177_STAFF_DIST_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."SELECT single ROLE_GUID FROM BAPI_TS_GUID INTO @DATA(ld_projectrole_guid). | ||||
"SELECT single STAFFING_LINK_GUID FROM BAPI_TS_GUID INTO @DATA(ld_iv_staffinglink_guid). | ||||
Search for further information about these or an SAP related objects