Ansicht
Dokumentation
OHADOEC53 - Maintain Notification Reasons
PERFORM Short Reference Vendor Master (General Section)This documentation is copyright by SAP AG.
In this step, you define notification reasons. The notification program will only process a notification, if a notification reason has been specified in the notification reason table. The notification program will not run, if the notification reason has been deactivated by a deletion indicator. The notification reason table includes the following information:
- Notification reason
- Description of notification reason
- Reason for notification
- Record type
- Notification reason difference
- Reason for notification difference
- Notification table type
- Deletion indicator
Most of these fields are technical fields and you do not need to maintain them. However, it is important to know whether or not a notification reason exists (some functions in the notification program are dependent on this), and whether or not the deletion indicator is set (a notification reason with an active deletion indicator is regarded as 'not existing').
Registration without an insurance number (notification reason 001) takes place in notification table 10 with the reason for notification field set to 30 and the record type field set to 30. You can not create a notification difference the first time you register, hence both notification difference fields remain empty.
Most notification reasons have been preset with notification key 01 in the standard system.
Action: Copy Notification Reason Key to a Customer Entry
Before you change the table of notification reasons, you should copy the model entries to your own notification reason key in the customer name range. This ensures that your changes cannot be overwritten by SAP.
- You are in the inial screen of the supplementary pension fund program (transaction PU11). Under Tables, choose Notification reasons and then choose Copy entries.
- The default source key is 01. Enter a notification key of your choice from the customer name range as the target key.
- Choose Execute.
Action: Define Notification Reasons
To adapt SAP notification reasons to your company's requirements, proceed as follows:
- Enter notification key 01 as your selection criterion.
- You access the first page of the table of notification reasons.
- Select an entry in the table.
- Choose Copy or Detail.
- You are now in the detail screen of the Notification Reason table.
- Modify the contents of at least one table.
- Choose Save.
Notification reasons 980 to 984 apply to address records, additional records, initial records, and subsequent records. They must not be deleted or deactivated by a deletion indicator.
Action: Assign a Notification Reason Key to a Supplementary Pension Fund
In the SPF table, assign your notification fields keys, notification reason keys and combination keys to the relevant supplementary pension funds. To do this, proceed as follows:
- On the initial screen of the SPF table, select the relevant supplementary pension funds.
- Choose Details.
- You are now in the detail screen of the SPF table.
- In the Technical control group, enter the notification key that you want to assign to the SPF in the Notification reason key field.
- Choose Save.
Vendor Master (General Section) rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 4242 Date: 20240523 Time: 231204 sap01-206 ( 65 ms )
