Hierarchy
SAP_HRCUS (Software Component) Sub component SAP_HRCUS of SAP_HR⤷
PY-US-PS (Application Component) Öffentlicher Dienst⤷
P10PA (Package) HR master data: Development Personnel Actions
IMG Activity
| ID | OHPSUSNOA002 | Actions Configuration |
| Transaction Code | S_AL0_96000845 | IMG Activity: OHPSUSNOA002 |
| Created on | 20001103 | |
| Customizing Attributes | OHPSUSNOA002 | Actions Configuration |
| Customizing Activity | OHPSUSNOA002 | Actions Configuration |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHPSUSNOA47002 |
The Nature of Action Configuration is used to configure the Actions used in the Nature of Action Processing tool. The Nature of Action Processing tool allows the user to edit multiple infotype fields on a single screen, and to verify that the data conforms to customer defined rules. The configuration transaction allows the definition of the infotype fields that will be used in a given Action, and the definition of the rules to which the data must conform.
An Action is a group of infotype fields that are to be maintained all on the same screen. The main benefit is that one will not have to page through many screens to change all of the needed data. A validation is a set of customer-defined rules that the data will be checked against to minimize entry errors. An Action does not need to have customer-defined validations associated with it. The standard infotype checks that occur when saving will still occur.
Note that this is a very powerful tool that will allow the user to perform actions that are not allowed in the Maintain HR Master Data transaction. With this tool you can see, and even edit, fields that are read-only in the normal infotype maintenance. The same is true for infotype fields that are hidden in the infotype maintenance transaction. Great care must be exercised by anyone who configures the fields of an Action. They must ensure that the safeguards that are in place normally are also followed when using this transaction. In particular, activating PA/PD integration will make some fields read-only, and using this tool it is possible to alter that data if it is configured to allow that.
Example
You wish to create an action that has the following fields:
Infotype 0001 Fields PLANS (Position), STELL (Job);
Infotype 0656 Subtype 0001 Fields NOA (Nature of Action Code), LEGAL_AUTH (Legal Authority Code);
All of the fields should be editable, except for PLANS. You wish to call this My Action.
1. Enter Nature of Actions configuration, and select the correct country code and usergroup.
2. Highlight the folder in which you would like to create the Action. You will be taken to the details screen.
3. Choose an Action Number, Name, Long Text, Subscreen, Report, and set the CPDF Status. Note that the CPDF flag is relevant only to US Federal customers. In this case, we choose:
a. Action Number: 000001
b. Name: My Action
c. Long Text: My Sample Action
d. Subscreen: 0500 (default)
e. Report: SAPMPBS0ACTIONS (default)
f. CPDF Reportable: Unchecked
4. Add fields and set the display attribute of the fields as described below.
5. If you would like to create validations for the Action, you may do so at this time. It must be done after the selection of the fields that are to be included in the Action. See the application help for the validations functionality for more information.
6. Save your work.
Requirements
For each action that is to be configured, determine the following:
1. Determine an Action Number (6 digits), Action Text, and Country (each action can be used for employees in one country code). If the user is to create their own subscreen for the action, the name of the report and the screen number should be noted. For Federal users, there is a flag to indicate if an action is CPDF (Central Personnel Data File) reportable.
2. The infotype fields that are to be edited. (These fields are restricted to infotypes with numbers in the ranges 0000-0999 and 9000-9999, inclusive. Country restrictions are accounted for in the allowed choice of infotypes for any given action.)
3. Any infotype fields that should be included in a read-only or hidden mode.
If a validation is to be defined for the Action, the following further steps should be followed:
4. Determine any extra data that may be needed for use in validating the information that is to be edited. (Note that if any data is to be used in the validations, it must be included in the Action. It is recommended that the data be read-only if it should not be edited.)
5. Write down the rules that the data needs to satisfy in terms of Boolean logic (using AND, OR, <, >, =, etc). If there are rules that are needed that cannot be furnished from the employees infotype data, a customer-defined infotype #Additional Field# can be defined and used in the Action and validation.
6. Create any extra #Additional Fields# that are necessary. More information can be found in the IMG under the path Personnel Management -> Human Resources Information System -> HR Settings for SAP Query -> Additional Information for Maintaining Functional Areas -> Define Additional Fields.
Note that due to technical limitations, time constraint 3 infotype records sharing the same infotype and subtype cannot be compared against each other.
Standard settings
Recommendation
Activities
1. On entering the configuration, the user is prompted for the country code and user group. For each different set of country codes and user groups, a different action tree display is generated. Your initial view is the overview.
2. In Display mode
a. Overview
i) All Actions are displayed in a tree. The infotype fields that are in the Action may be viewed by expanding the nodes below the action. The Action will have a node icon of ICON_MODIFICATION_ORIGINAL if it has a Pre-validation defined for it, and it has an icon ICON_MODIFICATION_CREATE next to that if it has a Post-validation defined for it.
ii) The user may view the details of the Action by highlighting the Action node and selecting the #Details# button from the application toolbar.
iii) The user may display the Pre-validations by highlighting the Action node and selecting the #Pre-validations# button from the application toolbar.
iv) The user may display the Post-validations by highlighting the Action node and selecting the #Post-validations# button from the application toolbar.
v) To view actions in a different Country code/User group combination, use the menu path Goto -> Change Area. You will be prompted for the new Country code/User group combination, and given a display of the new area.
b. Detail view
i) This is the view you have if you have selected to view the details of an Action. The view shows the folder hierarchy that the Action is in, and expands all of the fields in the Action. Also, the details subscreen is displayed with the Action Number, Action Texts, Subscreen, Report, and CPDF Reportable Flag.
ii) From the detail view you may perform all of the actions described above except for changing to the detail screen. Instead, you may return to the overview by selecting the #Overview# button from the application toolbar.
3. In Edit mode
a. Overview
i) All Actions are displayed in a tree. The nodes may be expanded only to the Action level. In the overview, there are several operations that can be performed.
ii) Create a new folder. A new folder may be created under any existing folder. To do this, use the context menu under a folder node and select #Create Folder# and the level on which you wish to create the folder. You will be prompted for the name of the folder.
iii) Move Actions and folders. You may move Actions and folders using Drag and Drop functionality.
iv) Copy Actions. Highlight the Action and select the #Copy# function from the application toolbar. You will be prompted for the Country Code, User group, and the new Action number. After entering these values, you will be taken to the detail view for that Action.
v) Delete Actions. Highlight an Action or Folder. Select the #Delete# button from the application toolbar. You will be asked if you want to delete the node and all of the sub-nodes of the selected node. If you select an Action, this will delete the entire Action, including any associated validations. If you select a folder, it will delete all Actions and folders that are within that folder. If you should delete an action in error, exit the configuration without saving. Unfortunately, any validations are lost as soon as the deletion is performed, so it is important that you only delete Actions and folders that you do not need.
vi) Create or Edit Initial Validations/Substitutions and Post-Validations. Highlight an Action and select either #Initial Validations# or #Post-entry Validations# from the application toolbar. If a validation exists, you will go to the edit mode of your existing validation. If it does not exist, you will be taken to a blank validation page for you
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHPSUSNOA002 | US | USA |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| DWBDUMMY | D - Dummy object | HRPBSUSACTIONCONFIG | Nature of Action Configuration |
History
| Last changed by/on | SAP | 20020514 |
| SAP Release Created in | 462A |
