Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PY-DE-PS-VA (Application Component) Pension Administration⤷
P00PBSWB_CONTROL_IMG (Package) Workbench Control Modules (IMG)
IMG Activity
| ID | HR_PBS_00_WB_INIT_0 | BAdI: Process Workbench Engine Control (PWE) |
| Transaction Code | S_L7D_24001648 | (empty) |
| Created on | 20080812 | |
| Customizing Attributes | HR_PBS_00_WB_2_2 | Process Ctrl for Process Workbench Engine (Optional Activity/Non-Critical) |
| Customizing Activity | HR_PBS_00_WB_INIT_0 | BAdI: Process Workbench Engine (PWE) Control |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HRPBS00PWE_CONTROL |
Use
This BAdI is used to control and change the behavior of the Process Workbench Engine as follows:
- Show the existing process scenarios on a separate overview-screen
- Display additional or less information on the overview screen for the existing process scenarios
- Option of using a sortable ALV grid instead of an ALV tree to display the overview screen for the existing process scenarios
- Set default values when creating a new process scenario
Therefore it is possible to implement the following methods:
Method GET_HEADER_DEFAULTS
Exporting parameters:
E_SEPARATE_OVERVIEW_PROC_SCEN
E_DEFAULT_LIST
E_TOGGLE_LIST_TREE
With this method three flags could be set by the customer. If he does not set any flag (or even does not implement the BadI), there will be no changes visible to the old behaviour of the PWE.
With this method three flags can be set by the customer. If he does not set any flag (or does not even implement the BAdI), there will be no visible changes to the old behaviour of the PWE.
The parameter E_SEPARATE_OVERVIEW_PROC_SCEN controls the type of overview screen. If it is set to 'X', the overview screen for the existing process scenarios is not displayed anymore in the small header area of the main screen. Instead the overview screen is displayed in the lower area (in place of the tabstrips for the sub-process scenarios). The detail information for the person will always be in the header area. After a process scenario is selected, the overview screen is closed and the sub-process scenarios are shown.
If the parameter E_DEFAULT_LIST is set to 'X', the user will see the header in the ALV Grid display by default. If E_TOGGLE_LIST_TREE is set to 'X', a toggle button to switch between the ALV Grid and the ALV Tree display will be shown in the ALV Grid or ALV Tree.
Method MODIFY_OUTPUT_TABLE
Importing parameter:
IS_ACT_PWE_HDR TYPE HRPS_PWE_HDR
Changing parameter:
CT_BSCEN TYPE HRPSPWE_REQ_TREE_TAB
In the overview screen for the existing process scenarios the table HRPSPWE_REQ_TREE_TAB is filled with all process scenarios which belong to the process.
By creating customer-include CI_HRPSPWE_REQ_TREE, which is included in the structure of this table, customer-specific fields can be added. These fields are not filled by the standard implementation. Therefore it is possible to change the output table of the ALV Grid / Tree in this method.
Method MODIFY_FIELDCATALOG
Importing parameter:
IS_ACT_PWE_HDR TYPE HRPS_PWE_HDR
Changing parameter:
CT_FCAT TYPE LVC_T_FCAT
The ALV Grid / Tree uses a fieldcatalog to define the fields to be displayed on the overview screen for the existing process scenarios. In this method the customer is able to change the display options for SAP standard fields and for fields he added by using the method above.
Method SET_DEFAULTS_FOR_NEW_PRSCEN
Importing parameter:
IS_ACT_PWE_HDR TYPE HRPS_PWE_HDR
Changing parameter:
CS_Q0716 TYPE Q0716
Within this method you can change the structure CS_Q0716 and set default values to create a new process scenario within the Process Workbench Engine.
Requirements
Standard settings
In general it is not a requirement to implement this BAdI. If it is not implemented the overview screen for the existing process scenarios is displayed in the header area of the screen. The overview screen can be closed with the header-toggle button and the detail information for the person can be displayed.
Activities
To use one of the described functions of this BAdI create your own implementation in the customer namespace.
As a filter value the BAdI uses the transaction code. You therefore have to add the transaction names for which your implementation should be valid.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20080812 |
| SAP Release Created in |
