Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PY-DE (Application Component) Germany⤷
P01C (Package) HR Customizing: Germany
IMG Activity
| ID | OHADOEC52 | Maintain Notification Fields |
| Transaction Code | S_AHR_61006022 | IMG Activity: OHADOEC52 |
| Created on | 19981221 | |
| Customizing Attributes | OHADOEC52 | Maintain Notification Fields |
| Customizing Activity | OHADOEC52 | Maintain Notification Fields |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHADOEC52 |
In this step, you define the notification fields for your notifications to supplementary pension funds. You do this in the notification field table which includes records of all notifications as per the general standards governing automatic data transfer (DATUEV). Each field holds the following information:
- Notification key
- Notification table type
- Table field name
- Description
- Position of notification field on data carrier (from/to)
- Admissibility of notification field for a notification reason
The admissibility of a notification field for a notification reason is defined in the notification field table. In Structure of notification fields, you define the notification, correction and cancellation reasons valid for the notification field. Input values for the first field include:
- All notification reasons in the notification reason table (the chosen notification field is valid for the notification reasons listed)
- Value *** (the chosen notification field is always empty)
- Blank (the chosen notification field is valid for all notification reasons)
Example
When registering, you have to specify the employee's name at birth. To do this, you assign notification key 01 and table type 10 (registration) to notification field GBNAM. On the data carrier, the field starts at position 126 and ends on position 145 (20 positions). The following entries describe the admissibility of the notification field:
- Notification: blank
With notifications, the GBNAM field is valid for each notification reason.
- Correction: 105
With corrections, the GBNAM field is only valid for notification reason 105 (Correction of name/name at birth).
- Cancellation: ***
With cancellations, the GBNAM field always remains empty.
Standard settings
In the standard system, all notification fields required by supplementary pension funds have been preset accordingly. The permissibility is modified to the requirements of the supplementary insurance funds under notification key 01. Notification key 03 contains 'blank' entries whereby all fields are permitted for all notification types.
Activities
Action: Copy Notification Key to Customer Entry
Before you change the table of notification fields, you should copy the model entries to your own notification key in the customer name range. This means that your entries cannot be overwritten by SAP.
- You are in the initial screen for the supplementary pension (transaction PU11). Under Tables, choose Notification fields and then choose Copy entries.
- The default Source key is 01. Enter the notification key for one of the model entries (01 or 03). Enter a notification key of your choice from the customer name range as the Target key.
- If you want to transport the copies to a different system at a later point, flag the Generate transport request field.
- Choose Execute.
Action: Maintain Notification Fields
- On the overview screen for the table of notification fields, select an entry for your notification key.
- To make a change, choose Detail. To create a new entry using a template, choose Copy.
You access the detail view of the table of notification fields.
- Change the contents of at least one field.
- Choose Save.
Action: Assign Notification Key to a SPF
When you have maintained the notification fields for a notification key, you must specify which SPF will use this notification key.
- In the SPF table, select the entry for the appropriate supplementary pension fund.
- Choose Detail.
- In the Notification key field, enter the notification key you are using.
- Choose Save.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHADOEC52 | DE | Germany |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHADOEC52 | 0 | HLA0003773 | Public Sector |
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 |
| PU11 | T - Individual transaction object | PU11 | 02HR | Copy Notification Key to Customer Entry | ||
| T5D5D | S - Table (with text table) | SM30 | Maintain Notification Fields | |||
| T5D5Z | S - Table (with text table) | SM30 | Assign Notification Key to an SPF |
History
| Last changed by/on | SAP | 19981221 |
| SAP Release Created in |
