SAP EXCHANGE INFRASTRUCTURE (XI) BASIS ENGINE

SAP PROCESS INTEGRATION (PI)

MEASUREMENT
Version

Changes

Date

1.9

Note 1943001 added

11.09.2014

1. Short Definition
SAP XI 3.0/PI 7.00 or higher releases can be licensed based on the total volume of messages in gigabytes
(GB) that is processed per month. The size of the payload is determined in the integration server. The
information is then aggregated according to sender and receiver system.
For the evaluation of the measured results for the XI/PI Base Engine, the highest monthly value of the last 12
months will be considered. In case the customer uses XI/PI on more than one installation/system, all monthly
values per metric must be accumulated and the highest value of each metric has to be considered.
2. Description of Metric
The message size is determined by the payload size of each message that is successfully processed by the
Integration Server (IS) and, in synchronous cases, the size of the response. This also includes the
attachments. Mapping steps can cause the message size to vary significantly during the processing of the
message in the integration server.
That is why four measurements are made while processing the message:

Request payload size before mapping

Request payload size after mapping
Response payload size before mapping
Response payload size after mapping

(Pl_Req)
(Pl_Req_Map)
(Pl_Resp)
(Pl_Resp_Map)

The payload size of the message is then calculated as:

Payload size (request) = max [Pl_Req, Pl_Req_Map] + max [Pl_Resp, Pl_Resp_Map]

The result of the calculation in bytes is stored in raw data tables. The raw data is then aggregated according
to

Sender system
Receiver system
Processing mode (synchronous/asynchronous)

The aggregates are then stored in a separate table. The aggregation takes place at different steps, on an
hourly, daily, and monthly basis.
3. Description of Metric
The message size is determined by the payload size of an XI/PI message in the Integration Server at the
time of the measurement. The size of the message is measured four times while the message is processed
in the Integration Server. The measured values are stored in the XI/PI message object. After the message
has been successfully sent using the aforementioned metric, the measured values are combined to give the
total value of the payload size.

-1-

V1.9 (September 2014)

4. Notes on Measurement
ID

Unit

Measurement*

2320

Chargeable data quantity in MB

Relevant1) 3)

2321

Total data quantity in MB

Only relevant for SAP R/3 customers

2322

Non-chargeable data quantity in MB

Not relevant2)

2323

Unclear status in MB

Further investigation required1) 4)

* Measurement options are:

Relevant:
Reliable value
Not Relevant:
Not reliable value
Threshold value: The measurement function described serves only to ascertain whether the product is in use or not. If the
threshold is exceeded, the engine is deemed in use.
1)

There are different licensing models for this product. The licensing model used in your contract determines
how the measured results are evaluated. Only if the measured metric is the same as the licensed metric will
the measured numbers be used for the evaluation. Otherwise we will regard the results merely as an
indicator that the product is in use.
2)

Whether a certain data volume is free of charge or chargeable depends on the scenario in use. Any data
volume that is exchanged between 2 SAP systems (SAP System -> PI Integration Server -> SAP System) is
considered free of charge.
3)

Whenever 1 of the 2 systems (sender or receiver or both) is a non-SAP System the data volume is
chargeable.
4)

Whether or not the payload is chargeable is determined at the time of measurement and when the
message is processed. For example, if a service once existed but had already been deleted by the time the
measurement was carried out, the related information cannot be determined automatically.
Attention: If you use SAP NetWeaver Process Integration as a central integration server and you notice that
data volume that is free of charge is displayed as subject to charge, see note 1672879.
Please implement note 1943001 if the outputs of the report SXMS_XI_AUDIT_DISPLAYand transaction
USMM are offset by one line. If there is no output by transaction USMM for the units 2320-2323. The
measurement is carried out using transaction USMM with a different user than that for the aggregation report
SXMS_PF_AGGREGATE and the two users are assigned to different time zones.
The PI/XI-Adapters will be measured via Unit IDs 2600 - 2662.
5. Information on Measurement Availability
The XI Basis Engine can only be measured with XI 3.0 or later. For technical reasons, earlier releases
cannot be measured.
In PI 7.00 the measurement functionality is available in the standard. If no measurement results are shown
on the measurement log although XI is in use check that the internal XI performance monitoring (see Note
820622) has been set up, as this is the basis for the system measurement.
Component

Release

Shipment

SAP_BASIS (XI 3.0)

6.40

SP 04

SAP_BASIS (PI 7.0)

7.00

Standard

-2-

V1.9 (September 2014)

Copyright/Trademark