Skip to Content
avatar image
Former Member

RNOTIFUPDATE01 termination with DNO_RFC_DATA BAdI

Dear experts,

Looking for help to solve the problem I'm having on Solution Manager (Service Desk for Vars), to run the report RNOTIFUPDATE01 get the error message below;

None of the installations were assigned to a destination in the BAdI

Message no. DNO190

Diagnosis

In your implementation of the BAdI DNO_RFC_DATA (method CHANGE_DESTINATION), a destination was not assigned to an installation. Due to this, no adjustment with the SAP problem notification system could take place.

Procedure

Check that you selected the correct installation numbers on the initial screen and in your implementation of the BAdI DNO_RFC_DATA, check the programming of the method CHANGE_DESTINATION for completeness and correctness.

Discovered that the table AIINSTALLATIONS is empty. But Installation Number can be seen: System -> Status...

Table AISAPCUSTNOS is correct.

What steps should be taken to solve the problem?

Thanks!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Apr 12, 2011 at 05:43 PM

    Hello Dmitriy,

    This message usually is raised when the RFC destination for the customer numbers are missing.

    Please refer to IMG activity:

    "Set-Up SAP Support Connection for Customers" within the folder

    "SAP Solution Manager->Configuration->Basic Settings->

    Standard Configuration of Basic Settings->Solution Manager->

    Connection to SAP->Multiple SAP Customer Numbers"

    The customer RFC destination SM_SP_<customer number> have to be created

    with S-Users of the customer assigned. These RFC destinations are used

    to communicate with the SAP backend.

    Regards,

    Paul

    Add comment
    10|10000 characters needed characters exceeded

    • Hello,

      You do know there is step by step documentation in SPRO for each IMG activitiy?

      ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

      Set-up SAP connection for customers

      You need an RFC connection to SAP for each customer number for which no SAP customer number or CCC/Service Provider SAP customer number is responsible, to send messages for the customer to SAP. The report is in two phases:

      Phase 1: Create file

      In this phase, an Excel file (RFC_VAR.csv) is created for the customer in a frontend. The customer data must have been loaded correctly by SAP. The file has four columns (Destination, Description, User, Password). There should be a destination and description for each customer, after phase 1. You must maintain the User and Password columns manually.

      Phase 2: Create RFCs

      The report reloads the changed Excel file, and creates an RFC for each entry in the file. You create customer RFCs with the naming convention <SM_SP>_ <customer number>, based on the RFC SAP-OSS.

      Prerequisites

      RFC connection SAP-OSS.

      Activities

      Run the report SM_CONFIG_RFC.

      Phase 1:

      1. Download the file to your frontend, in phase 1. You have two alternatives:

      Table AISAPCUSTNOS

      This option creates a template for each customer number in the table. This is the recommended option.

      Template

      You can create the Excel file as a template, from an example. When the file has been created, you must maintain the required data manually (and delete the example).

      2. Open the file and maintain the user and password for each destination and description.

      Phase 2

      3. Load the changed file into your system in phase 2.

      You get a log. If errors occur, check the RFC connections in the transaction SM59.

      Result

      For customer numbers without a person responsible, there must now be an RFC connection of the form <SM_SP_<SAP customer number>.

      ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

      Please refer to the documentation that comes with the system as it will help to guide your through these activities.

      Regards,

      Paul