Kontakt

Ansicht
Dokumentation

RPCBDVD1_OUT - Create Notifications for Company Data Maintenance

RPCBDVD1_OUT - Create Notifications for Company Data Maintenance

Addresses (Business Address Services)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report creates DEUEV notifications for company data maintenance.

Integration

Prerequisites

The data for the company numbers must be maintained in the reporting personnel area for subapplication BDBS(Company Data Maintenance - Data for Place of Work). Execute the necessary Customizing activities under Payroll: Germany -> DEUEV -> DEUEV Notifications for Company Data Maintenance -> Company Data Maintenance - Overview -. The sender for the notifications must be maintained in the reporting personnel area for subapplication BDAB(Company Data Maintenance - Sender Data). Execute the necessary Customizing activities under Payroll: Germany -> Communication with Authorities (B2A) -> Data Exchange with Social Insurance Agencies -> Settings for the Applications -> Settings for DEUEV Notifications for Company Data Maintenance -> Compay Data Maintenance - Overview -.

You must maintain the company numbers for which notifications should be created in view V_T5D0P (Assignment of Company Features) for the individual personnel areas/subareas. Company numbers that should be excluded from notification creation must be marked in view V_5D0P_G. All personnel areas/subareas that have been assigned the relevant company number must be excluded.

Features

If you select parameter Database Update in group box Program Control, the notifications generated are saved. The report creates notifications with the status:

  • Initial
The first notification that is created for a company number is saved with the status initial. This notification is not transferred and reported as it generally contains dataset information that the company number service of the Federal Employment Agency already has.
The initial notification is the starting point of the notification procedure. It is, therefore, important that there is an initial notification for a company number that is free from errors and that has been saved to the database so that any changes to company data can be recognized in the subsequent notification creation runs.
  • New
If it is a notification that is different to an initial notification or transferred notification, it is set to status neu. Report Create Notification Files for Company Data Maintenance (RPCBDHD0_OUT) collects these in a file and reports them.
  • With errors
If errors occur when creating the notification, the notification is set to status With Errors. The errors must be corrected before the notification can be created with status Initial or New.
  • To be decided
If, during the creation of the notification, the report classes the notification as implausible, the notification is created in status To be decided. You can find more information about plausibility checks and dealing with implausible notifications here.

Selection

You can restrict the creation of notifications to personnel area/subarea level (Reporting). Define the individual values you require in group box Selection Criteria. The F4 input help for the Personnel area/subarea field provides a list of the possible restrictions. If necessary, you can also restrict the creation of notifications on the company number level by making the appropriate entries for individual values in the Company No. of Place of Work field. Here, too, an F4 input help is available.

Note that the report excludes inactive personnel areas from notification creation. Tables Validity Period of Personnel Area (T500P_DELIMIT) and Validity Period of Personnel Subarea (T001P_DELIMIT)are evaluated. For inactive personnel areas, you can create another change notification to report the employing company activities as ended. Note that tables T500P_DELIMIT and T001P_DELIMIT are only available as of release 6.04. In earlier releases, no check for inactive personnel areas is carried out.

See the information on recording the Event date.

Standard Variants

Output

Statistics of the processed company numbers are displayed. If the Create Log checkbox is selected, a detailed log is generated.

The report log is divided into the following sections:

  • Parameter
This section displays the run ID, which consists of the date and time. The system assigns this ID to all the notifications that were created in this run. You can use the report Administrator List for Notifications for Company Data Maintenance (RPCBDLD1_OUT) to display all of the notifications that were created in this run by using this run ID to select the notifications.
  • Details of notification creation
The following subpoints are issued in this section:
  • No new notifications
    The notifications for each company number for which no new notifications are created are issued. The reason for this is that there is no difference between the relevant fields of a message that has already been transferred or an initial notification.

  • New notifications
    All new notifications for each company number are issued. These are subdivided into the following points:

  • Notification According to Latest Status
    The data modules of the notifications according to the latest status are logged.

  • Notification According to Old Status
    The data modules of the last notification according to the old status with which the new notification was compared are logged. The new notification is only compared with an old notification that has the status initial, transferred, or manually reported. Notifications with the status With Errors or New are not used for the comparison.

  • Notifications to transfer
    If the data for a company number was changed, this must be reported. The data modules of the notifications to be transferred are logged.

  • Initial notification
    If an initial notification is generated, it is logged.

  • Notifications with errors
    Notifications that were created with errors are displayed.

  • Error messages
    The error notifications are issued in this section.

  • General Messages
In this section, error messages that occur when notifications are being created are issued, for example.
  • Statistics
This section displays information about the processing of company numbers.

Activities

If no notifications were created with the status With Errors, all notifications are collected in one notification file and transferred using report Create Notification Files for Company Data Maintenance (RPCBDHD0_OUT).

Example






BAL_S_LOG - Application Log: Log header data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 8986 Date: 20240520 Time: 101657     sap01-206 ( 148 ms )