Kontakt

Ansicht
Dokumentation

RNOTIFUPDATE01 - Program RNOTIFUPDATE01

RNOTIFUPDATE01 - Program RNOTIFUPDATE01

Addresses (Business Address Services)   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report deals with the synchronization of notifications in Solution Manager with SAP messages, when you process notifications or service processes in Solution Manager service desk in a local system and forward them to SAP as messages as required.

Once you have scheduled a periodic job for a variant of this report, notifications are regularly synchronized with SAP messages. This means that, at the intervals defined in the job, all changes made at SAP are transferred to the local system.

Integration

Prerequisites

  • In the local system you are running the Solution Manager Service Desk, or the Support Desk with general notifications, or Support Desk on a system that is based on 4.6C (Support Line Feedback).
  • You have defined RFC connections SAP-OSS and SAP-OSS-LIST-O01, or you use the relevant BAdI to transfer problem notifications (customer messages).
    You must copy the settings for RFC destination SAPOSS. Make sure that you use group 1_PUBLIC to log on, instead of EWA. Use one of your S users and its password. In the user parameters of the user that starts the job (user in job step), enter another S user with the necessary authorizations within SAP. Make sure that both S users belong to the same customer or concern. The user must also have the authorizations for changing general notifications and CRM operations in the local system.
  • You may want to transfer notifications from different customers that do not belong to the same concern. This is only possible if you enhance this report with an active implementation of BAdI DNO_RFC_DATA. The enhancements enable repeated logon to SAP in the name of the different customers (RFC connections with different S users, at the same time transferring an S user of the same customer, as in the user parameters - see above). In this case, processing takes the form of the repeated execution of this report for the various different customers.

Features

You can use this report to find all the messages (notifications) that have been changed since the last synchronization with SAP. To avoid any gaps due to the replication of data between systems at SAP, the header data of all messages that have been changed since the last synchronization and in the 24 hours before that are transferred by RFC destination SAP-OSS-LIST-O01. In addition, all the notifications (messages) that could not be updated during the last synchronization run are added, whether this is due to a block in the local system or problems with the connection to SAP. After this, the messages (notifications) are read individually and changes to the notifications are copied to the local system via the RFC destination SAP-OSS.

If there are problems when reading data at SAP or writing data to the local system, the affected messages (notifications) are saved to table dnod_update, so that they can be synchronized successfully when the next synchronization runs. If the report finds that the changes from SAP have already been transferred successfully, the data is not written to the local system again. The time of synchronization is recorded in table dnod_update.

Selection

  • Unconfirmed Messages,,
    If this parameter is selected, confirmed messages are not transferred. This option is only for initial setup, when you may not need to copy older confirmed messages (notifications). Do not select this parameter for day-to-day use, because when messages have been confirmed at SAP you want the corresponding notifications to be confirmed in your system.
  • Create New Notifications
    You use this parameter to define whether the creation of notifications is allowed within the synchronization process with SAP. If you initiate SAP messages by telephone or create them on the SAP Service Marketplace, this option allows these messages to be processed subsequently as notifications in your system. Note that not all attributes assigned to notifications in your Service Desk can be inferred from SAP messages, so you may need to postprocess such messages.
  • Source System
    The values for the 'Source System' field have the following meanings:
  • ' All Systems'

All notifications are updated, regardless of which system they were created in (SAP Support Portal, SAP Service Marketplace, SAP Solution Manager system, or SAP R/3 Helpdesk system). Use this value if you want to process messages that were created in the SAP Support Portal as notifications in Solution Manager. You also need to use this value to edit the preconfiguration of service provider after migration from the SAP Support Portal to Solution Manager.
  • 'X All Systems (Without SAP Support Portal)'

All notifications that were not created in the SAP Support Portal, SAP Service Marketplace, or directly at SAP are updated.
  • 'W Workplace'

Only notifications that were originally created as general notifications are updated.
  • 'S $$ Notifications'

All notifications that were created in an R/3 Helpdesk system as $$ notifications are updated.
  • 'C CRM Notifications'

All notifications that were created in Solution Manager as CRM notifications are updated. (This includes notifications that were sent to Solution Manager from a satellite system.)
  • 'D CRM Notifications and Migrated $$ Notifications'

Includes the notifications that are updated under the values 'C' or 'S'.
  • 'E CRM Notifications and Migrated Workplace Notifications'

CRM notifications and migrated general notifications from Solution Manager Release 2.1/2.2 are updated.
  • Installations to be Processed
    Here you can select the individual installations for which you want notifications to be updated.

Standard Variants

In standard variant SAP&WORKPLACE, only notifications that were created as general notifications are updated. This is not enough if you use Solution Manager. Create a new variant according to your requirements. If you also want to process new messages as notifications in your Service Desk, SAP recommends the following parameters for your regular synchronization:

pa_conf  = SPACE ,,(Unconfirmed Messages = blank)
pa_creat = 'X',,(Create New Notifications = 'X')
pa_msg   = SPACE ,,(Source System = 'All Systems')
so_instn = empty ,,(Installations to be Processed = blank)

Output

The resulting list first shows all the notifications to be updated, before recording the processing of individual notifications. Errors are also shown here.

Activities

This report is written in such a way that it checks when starting whether a job of the same report is currently running actively. If a job is running, this report does not start a second time. Check why the earlier job has not yet finished.

See the current SAP Notes on this subject.

Example






BAL Application Log Documentation   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 8386 Date: 20240531 Time: 061903     sap01-206 ( 157 ms )