Entering content frameBackground documentation OPC Data Access Servers (DA Servers) Locate the document in its SAP Library structure

OPC Data Access servers (DA servers) provide data from different data sources (for example, process control systems) that an OPC client (for example, SAP ODA) can read. At the same time, DA servers can receive data from an OPC client and process it. Thus, OPC servers enable accessing a large number of items from a large number of data sources (for example, process control systems).

Together with a DA server, an SAP R/3 System can use the following functions:

See also:

Item Structuring

All data sources that a DA server provides are organized in a namespace, which can be flat or hierarchical.

In a flat namespace, the items are all on one level. In a hierarchical namespace, the nodes can, for example, represent the machines and devices in a production line. Below the nodes are the leaves that represent temperature sensors or regulators. The leaves are called items. Every item has an item ID and can provide values.

This graphic is explained in the accompanying text

Data Transfer for Value Changes

In order that the DA server knows which values it is to transfer to SAP ODA in a Data Access subscription, certain engineering units (for example, temperature) must be defined in the DA server for every process unit. The DA server uses the following data to determine an absolute range within which the value of the OPC item must at least change to be transferred to SAP ODA.

The following data must be defined:

Calculation Formula:

Absolute deadband = (upper limit – lower limit) * percentage deadband

Example

A temperature sensor has a range from -100°C to +900°C. A percentage deadband of 0.1% has been set up in the OPC client.

The absolute deadband is calculated as follows:

(900 - (-100)) * 0.1% = 1

This means that the temperature must change at least by ±1°C in order that the value is reported to the SAP R/3 System.

 

 

 

 

 

 

 

Leaving content frame