Ansicht
Dokumentation
HR_PBS_00_WB_INIT_0 - BAdI: Process Workbench Engine Control (PWE)
TXBHW - Original Tax Base Amount in Local Currency BAL Application Log DocumentationThis documentation is copyright by SAP AG.
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
- Use the transaction as a display transaction only
- Use the infotype framework to save the infotypes (more information is available in the SAP Help Portal documentation Decoupling Infotypes)
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.
Method IS_DISPLAY_ONLY
| Exporting parameter: | ||
| E_IS_DISPLAY_ONLY | TYPE | ABAP_BOOL |
You use this method to determine if the transaction should only be used as a display transaction. If this is the case, set parameter E_IS_DISPLAY_ONLY to 'X'.
Method IS_ITF_ACTIVE
| Exporting parameter: | ||
| E_ IS_ITF_ACTIVE | TYPE | ABAP_BOOL |
If the infotype framework should be used for reading and saving the infotypes, parameter E_IS_ITF_ACTIVE should be set to 'X'. If it is not a display transaction only (method IS_DISPLAY_ONLY), when using the infotype framework, you are also required to implement methods UPDATE_P0716, INSERT_P0716, and DELETE_P0716. These methods are called for changing, creating, and deleting infotype Process Scenario (0716).
Methods UPDATE_P0716, INSERT_P0716, DELETE_P0716
These methods are used within PWE to save infotype Process Scenario (0716), to create a new process scenario, or to delete an existing process scenario. The methods are only called if the infotype framework is used (method IS_ITF_ACTIVE). In the implementation of the methods, the infotype framework is also used to carry out the infotype operations. In addition, when deleting a process scenario, for example, you can check if there is data that depends on the process scenario, which has to be deleted first.
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.
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.
General Data in Customer Master ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 8135 Date: 20240523 Time: 184829 sap01-206 ( 113 ms )
