SAP BAPI_BUS2177_STAFFING_CHANGE Function Module for BAPI Role: Change Staffing
BAPI_BUS2177_STAFFING_CHANGE is a standard bapi bus2177 staffing change 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: Change Staffing 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 staffing change FM, simply by entering the name BAPI_BUS2177_STAFFING_CHANGE 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: 10-Jan-2005
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_BUS2177_STAFFING_CHANGE 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_STAFFING_CHANGE'"BAPI Role: Change Staffing.
EXPORTING
PROJECTROLE_GUID = "GUID for Role (Approval) in BAPI Interface
IV_STAFFINGLINK_GUID = "GUID for Linking Role to Business Partner in BAPIs
IS_STAFFINGLINK = "Attributes of a Project Assignment of Role to Task
IS_STAFFINGLINK_X = "Update Information for Staffing
* IV_IGNORE_WFMCORE = ' ' "Switch for Deactivating Connection to WFM Core
TABLES
* IT_COMMENT = "cProjects BAPI: RAW Line of Length 255
* RETURN = "Return Parameters
IMPORTING Parameters details for BAPI_BUS2177_STAFFING_CHANGE
PROJECTROLE_GUID - GUID for Role (Approval) in BAPI Interface
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)
IS_STAFFINGLINK - Attributes of a Project Assignment of Role to Task
Data type: BAPI_TS_PRP_STAFFINGOptional: No
Call by Reference: No ( called with pass by value option)
IS_STAFFINGLINK_X - Update Information for Staffing
Data type: BAPI_TS_PRP_STAFFING_XOptional: No
Call by Reference: No ( called with pass by value option)
IV_IGNORE_WFMCORE - Switch for Deactivating Connection to WFM Core
Data type: BAPI_H99_GEN-FLAGXDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_BUS2177_STAFFING_CHANGE
IT_COMMENT - cProjects BAPI: RAW Line of Length 255
Data type: BAPI_TS_RAW_LINEOptional: Yes
Call by Reference: Yes
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_STAFFING_CHANGE 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_it_comment | TYPE STANDARD TABLE OF BAPI_TS_RAW_LINE, " | |||
lv_projectrole_guid | TYPE BAPI_TS_GUID-ROLE_GUID, " | |||
lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
lv_iv_staffinglink_guid | TYPE BAPI_TS_GUID-STAFFING_LINK_GUID, " | |||
lv_is_staffinglink | TYPE BAPI_TS_PRP_STAFFING, " | |||
lv_is_staffinglink_x | TYPE BAPI_TS_PRP_STAFFING_X, " | |||
lv_iv_ignore_wfmcore | TYPE BAPI_H99_GEN-FLAGX. " ' ' |
  CALL FUNCTION 'BAPI_BUS2177_STAFFING_CHANGE' "BAPI Role: Change Staffing |
EXPORTING | ||
PROJECTROLE_GUID | = lv_projectrole_guid | |
IV_STAFFINGLINK_GUID | = lv_iv_staffinglink_guid | |
IS_STAFFINGLINK | = lv_is_staffinglink | |
IS_STAFFINGLINK_X | = lv_is_staffinglink_x | |
IV_IGNORE_WFMCORE | = lv_iv_ignore_wfmcore | |
TABLES | ||
IT_COMMENT | = lt_it_comment | |
RETURN | = lt_return | |
. " BAPI_BUS2177_STAFFING_CHANGE |
ABAP code using 7.40 inline data declarations to call FM BAPI_BUS2177_STAFFING_CHANGE
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). | ||||
"SELECT single FLAGX FROM BAPI_H99_GEN INTO @DATA(ld_iv_ignore_wfmcore). | ||||
DATA(ld_iv_ignore_wfmcore) | = ' '. | |||
Search for further information about these or an SAP related objects