Destination System

Definition

A destination system is the system or the server to which notification messages are to be sent. You can use the maintenance tab of the destination system to configure the data flow from PCo to the connected destination system. You only need to create and configure destination systems if you want to use the notification process.

You can assign multiple destination systems to a single agent instance. This means that a single action that is triggered by a tag value change on a tag-based server, or a method call via PCo OPC UA and a Web server, can lead to more than one destination system being called.

The following SAP Business Suite systems can be connected to PCo as a destination system:

SAP MII
SAP ME
SAP EWM
Other SAP Business Suite systems with SAP NetWeaver, such as SAP ERP or S/4 HANA.

The NetWeaver systems with the software component SAP_BASIS of the following releases are supported:
- Release 7.00, as of support package SAPKB70208
- Release 7.01, as of support package SAPKB70109
- Release 7.02, as of support package SAPKB70024
- Release 7.31
- Release 7.40
- Release 7.50
- Release 7.5x
Databases, for example, the SAP HANA database
MQTT server
Calling Web services

If the available destination system types are not sufficient for you, you can create additional destination system types as part of a customer-specific development. SAP Note 2470588 Information published on SAP site describes how you can develop a customer-specific destination system based on the template CustomDestination provided by SAP.

Configuration of Destination Systems

Destination Systems
Destination System	Description
Universal Web Service Destination System	The universal Web service destination system is a destination system type with which you can send notification messages to a Web service. The following types of Web services are possible: Web service RESTful Web service OData service See also: Universal Web Service Destination System.
RFC Destination System	If you want to define a Business Suite system (for example, SAP ERP, SAP SCM, SAP EWM) as a destination system, you need to create a destination system of the type RFC destination system. See also: RFC Client Settings Tab.
OPC UA Destination System	You can use this destination system type to enable the call of a method of an OPC UA server. This OPC UA server may be configured on a remote system or on an agent instance of your own PCo installation. See also: OPC UA Destination System
Multiple Call Destination System	The multiple call destination system is a destination system type that you can use to call other destination systems in a configurable sequence from a notification. This destination system type also provides functions for calculations and conversions of variables that are returned from a destination system or that are used to call a destination system. Multiple call destination systems also allow the modularization of functions, similar to functions or static methods in programming languages. You can bundle frequently used sequences of destination system calls in a multiple call destination system and reuse this multiple call destination system in various places, such as in other multiple call destination systems. See also: Multiple Call Destination System
Query Destination System	The query destination system allows you to read tag values from the source system of an agent instance or to write tag values to the source system of an agent instance. The agent instance can be the same agent instance from which the query destination system is called or another agent instance that is running on the same PCo computer. See also: Query Destination System
MQTT Destination System	You use the MQTT destination system to be able to send MQTT messages to an MQTT server. This allows you to forward data, which has been transferred to PCo, to an MQTT server. See also: MQTT Destination System.
ODBC Destination System	You use the ODBC destination system to be able to send notification messages to an ODBC database. With each notification message, the tag values and metadata of the selected tags are stored as table entries in a table (for example, a history table) in the connected database. You can use the values stored in the database table for evaluations later. See also: ODBC Destination System
Simulation Destination System	The simulation destination system is a folder in a directory you have specified on your computer. You can use this destination system type to test the sending of notification messages very quickly. See also: Simulation Destination System: Configuration Tab.

Deprecated Destination Systems and Recommended Alternatives

The following destination systems are still part of the PCo solution for reasons of compatibility with earlier PCo releases. You can continue to use existing configurations. However, SAP does not recommend creating new instances of the following destination systems, since there are alternatives that continue to be developed by SAP from a functional point of view, but also with regard to security standards. If possible, use one of the available alternatives.

Deprecated Destination Systems and Their Alternatives
Destination System	Description	Alternatives
MII Destination System (Deprecated)	Until now, if you wanted to connect an SAP MII system to be able, for example, to call a transaction there, you could create a destination system of the type MII destination system. See also: MII Destination System	SAP recommends that, for new configurations, you use a universal Web service destination system to call MII transactions. For more information about calling MII transactions using Web services, see Calling MII Transactions Using Web Services.
Web Service Destination System (Deprecated)	Until now, if you wanted to connect to a third-party system, for example, an SAP ME system, you could create a destination system of the type Web service destination system. See also: Web Service Destination System	SAP recommends that you use a universal Web service destination system for new configurations.