SAP ABAP IMG Activity OHADOE_ZVMP06_035 (SPI Group: Assign Reasons for Notification and Record Types)
Hierarchy
☛ SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR
   ⤷ PY-DE-PS (Application Component) Public Sector
     ⤷ P01O_ZV (Package) SP Notification Program for Public Sector Germany
IMG Activity
ID OHADOE_ZVMP06_035 SPI Group: Assign Reasons for Notification and Record Types  
Transaction Code S_L7D_24000071   (empty) 
Created on 20051118    
Customizing Attributes OHADOE_ZVMP06_01   SP Notification Program 2006 (Mandatory/Critical) 
Customizing Activity OHADOE_ZVMP06_035   SPI Group: Assign Reasons for Notification and Record Types 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OHADOE_ZVMP06_035    

Use

In this IMG activity, you assign notification reasons and record types to an SPI group (see also: SIMG.OHADOE_ZVMP06_030 Define SPI Group).

You define the assignment between a notification-relevant event and the notification type for the record type for each SPI group you created

Note:
The assignment is heavily based on sections 9.2.1 and 9.2.2 of the DATUEV-ZVE.
However, in addition to the #x# indicator (record type must be part of the notification) and #-# (notification records of this record type cannot be part of the notification), you can also specify the #o# indicator (notification records of this record type can be part of the notification) to mark a variety of record types as optional records.

Since this assignment is mapped using checkboxes in the SAP system (corresponding to must or cannot), you set up the additional #o# indicator in the system as follows:

  • For record types 80 (name) and 81 (address), there are separate notification-relevant events (AA and BB) used to map changes to names and addresses. If your company requires, for example, an address record for the annual report (as is the case for the BVK#s ZKdbG), you must select record type 81 for the annual report.
  • Record type 70 (differences) is optional for members of the AKA. If your SPI requires difference records, you must specify this in a checkbox later on when you set up the SPI.
  • Record types 30 (registration), 40 (deregistration), and 60 (section) are mandatory records for the registration notification (notification reasons 30 to 32), deregistration notification (40 to 42), and annual report notification (60 to 62).

    Comments about notification-relevant events AA and BB (change of name and/or address):
    These events cannot be derived directly from DATUEV-ZVE. They are therefore mapped via registration correction (notification reason 31) in the Customizing example.

Activities

Complete the following steps to make assignments for each created SPI group (see also: Define SPI Group):

  1. Select an SPI group in the Define SPI Group table.
  2. Double-click on Notification Reasons, Assign Record Types in the dialog structure to call the assignment table for the selected SPI group.
  3. In the table, maintain the desired assignments for the selected SPI group.
  4. Choose Save.

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency I   Valid for countries specified 
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
VC_T5DPBSZVZG C - View cluster SM34  
History
Last changed by/on SAP  20051118 
SAP Release Created in