The market operator would like to point out that in the next phase of optimizing automatic communication with market participants (probably at the end of May 2025) the production OTE system will switch to "idocless" communication for the following messages: 112,114,115,117,118,120,138,141,146,147,148,150,158,178,179,180,182,183,185,186,188,189,191,246,248,250,254,256,257,259,274,276,521,511,GTP (replaces 531).

Please note that after the transition to "idocless" communication, namespace prefixes (n0:, n1:, etc.) will be newly used in output messages for the above msgcodes and market participants need to prepare for this change.

In the Sandbox testing environment, this functionality for the above messages is ready for testing from May 5, 2025.

We would like to remind you that in previous phases  (last on April 2, 2025), the use of namespaces in output messages from OTE system was implemented, e.g. for messages with codes: 111, 151, 153, 154, 156, 165, 166, 167, 168, 170, 171, 172, 174, 192, 193, 194, 195, 196, 197, 199, 212, 245, 249, 277, 279, 280, 282, 351, 353, 354, 356, 357, 359, 367, 369, 371, 373, 381, 383.  For messages with msgcodes 121, 232, this is already used from February 1, 2024.

This processing uses the standard SAP PROXY to generate output XML. To prevent conflicts between namespaces, their prefixes are used for individual elements (n0:, n1: etc.) in accordance with the XML format specification so that each element is uniquely identified. The digital signature namespace http://www.w3.org/2000/09/xmldsig#  has been added, which is currently not used. The element xmlns:prx="urn:sap.com:proxy:CDP:/1SAI/TAS8EE367C9C7DF015F1B9B:740" can be ignored, it serves only for information on which version of SAP proxy the given message was generated with.

Although the same "idocless" communication format has been used for selected messages in CS OTE since February 1, 2024, we recommend that market participants check the reception and processing of messages newly affected by this change.

In the Sandbox testing environment, this functionality for the above messages is ready for testing from May 5, 2025.

Thank you for your understanding.