SAP GCC_PS_WBS_ELEMENT_CHG Function Module for NOTRANSL: Ermitteln eines Namens für ein PSP-Element









GCC_PS_WBS_ELEMENT_CHG is a standard gcc ps wbs element chg SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Ermitteln eines Namens für ein PSP-Element 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 gcc ps wbs element chg FM, simply by entering the name GCC_PS_WBS_ELEMENT_CHG into the relevant SAP transaction such as SE37 or SE38.

Function Group: GCC_PS
Program Name: SAPLGCC_PS
Main Program: SAPLGCC_PS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function GCC_PS_WBS_ELEMENT_CHG 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 'GCC_PS_WBS_ELEMENT_CHG'"NOTRANSL: Ermitteln eines Namens für ein PSP-Element
EXPORTING
I_BUS_SCENARIO_ID = "Business Scenario for which Controlling Is Performed
I_PROJECT_DEFINITION = "Project Definition
I_ATTRIBUTES_OF_EXT_OBJ = "Table of Controlling Object Attributes
I_BUS_SCENARIO = "Business Scenario
I_AUTOMATIC_PROJECT_MODEL = "Automatic Project Model
I_WBS_ELEMENT = "Work Breakdown Structure Element (WBS Element)

CHANGING
C_WBS_DESCRIPTION = "PS: Short Description (First Text Line)
C_WBS_BILLING_ELEMENT = "Indicator: Billing element
C_WBS_ACCOUNT_ASSIGNMNT_ELEMNT = "Indicator: Account assignment element
C_WBS_PLANNING_ELEMENT = "Indicator: Planning element
C_WBS_RESULTS_ANALYSIS_KEY = "Results Analysis Key

EXCEPTIONS
ERROR_OCCURRED = 1
.



IMPORTING Parameters details for GCC_PS_WBS_ELEMENT_CHG

I_BUS_SCENARIO_ID - Business Scenario for which Controlling Is Performed

Data type: IAOM_BS_IDENTIFICATION
Optional: No
Call by Reference: Yes

I_PROJECT_DEFINITION - Project Definition

Data type: PS_PSPID
Optional: No
Call by Reference: Yes

I_ATTRIBUTES_OF_EXT_OBJ - Table of Controlling Object Attributes

Data type: IAOM_OBJECT_ATTRIBUTES
Optional: No
Call by Reference: Yes

I_BUS_SCENARIO - Business Scenario

Data type: CL_IAOM_BUSINESS_SCENARIO
Optional: No
Call by Reference: Yes

I_AUTOMATIC_PROJECT_MODEL - Automatic Project Model

Data type: IAOM_AUTO_PROJECT_MODEL
Optional: No
Call by Reference: Yes

I_WBS_ELEMENT - Work Breakdown Structure Element (WBS Element)

Data type: PS_POSID
Optional: No
Call by Reference: Yes

CHANGING Parameters details for GCC_PS_WBS_ELEMENT_CHG

C_WBS_DESCRIPTION - PS: Short Description (First Text Line)

Data type: PS_POST1
Optional: No
Call by Reference: Yes

C_WBS_BILLING_ELEMENT - Indicator: Billing element

Data type: PS_FAKKZ
Optional: No
Call by Reference: Yes

C_WBS_ACCOUNT_ASSIGNMNT_ELEMNT - Indicator: Account assignment element

Data type: PS_BELKZ
Optional: No
Call by Reference: Yes

C_WBS_PLANNING_ELEMENT - Indicator: Planning element

Data type: PS_PLAKZ
Optional: No
Call by Reference: Yes

C_WBS_RESULTS_ANALYSIS_KEY - Results Analysis Key

Data type: ABGR_SCHL
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ERROR_OCCURRED - Errors

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for GCC_PS_WBS_ELEMENT_CHG 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_error_occurred  TYPE STRING, "   
lv_c_wbs_description  TYPE PS_POST1, "   
lv_i_bus_scenario_id  TYPE IAOM_BS_IDENTIFICATION, "   
lv_i_project_definition  TYPE PS_PSPID, "   
lv_c_wbs_billing_element  TYPE PS_FAKKZ, "   
lv_i_attributes_of_ext_obj  TYPE IAOM_OBJECT_ATTRIBUTES, "   
lv_c_wbs_account_assignmnt_elemnt  TYPE PS_BELKZ, "   
lv_i_bus_scenario  TYPE CL_IAOM_BUSINESS_SCENARIO, "   
lv_c_wbs_planning_element  TYPE PS_PLAKZ, "   
lv_i_automatic_project_model  TYPE IAOM_AUTO_PROJECT_MODEL, "   
lv_c_wbs_results_analysis_key  TYPE ABGR_SCHL, "   
lv_i_wbs_element  TYPE PS_POSID. "   

  CALL FUNCTION 'GCC_PS_WBS_ELEMENT_CHG'  "NOTRANSL: Ermitteln eines Namens für ein PSP-Element
    EXPORTING
         I_BUS_SCENARIO_ID = lv_i_bus_scenario_id
         I_PROJECT_DEFINITION = lv_i_project_definition
         I_ATTRIBUTES_OF_EXT_OBJ = lv_i_attributes_of_ext_obj
         I_BUS_SCENARIO = lv_i_bus_scenario
         I_AUTOMATIC_PROJECT_MODEL = lv_i_automatic_project_model
         I_WBS_ELEMENT = lv_i_wbs_element
    CHANGING
         C_WBS_DESCRIPTION = lv_c_wbs_description
         C_WBS_BILLING_ELEMENT = lv_c_wbs_billing_element
         C_WBS_ACCOUNT_ASSIGNMNT_ELEMNT = lv_c_wbs_account_assignmnt_elemnt
         C_WBS_PLANNING_ELEMENT = lv_c_wbs_planning_element
         C_WBS_RESULTS_ANALYSIS_KEY = lv_c_wbs_results_analysis_key
    EXCEPTIONS
        ERROR_OCCURRED = 1
. " GCC_PS_WBS_ELEMENT_CHG




ABAP code using 7.40 inline data declarations to call FM GCC_PS_WBS_ELEMENT_CHG

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.

 
 
 
 
 
 
 
 
 
 
 
 


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!