Certificacion ORCA PDF

Certificate
SAP INTEGRATION CERTIFICATION

SAP SE hereby confirms that the interface software Hexing Orca-SAP AMI
Interface for the product Orca@MDC/MDM/Vending V8.0 of the company
Hexing Electrical Co.,Ltd has been certified for integration with SAP
S/4HANA SAP Utility 1809 based on an ICC Integration Assessment via SAP
Utility AMI Use cases.
This certificate confirms the technical compliance of
Orca@MDC/MDM/Vending V8.0 with SAP certification procedures.
The certification test is documented in report no. 15496 and expires on

16.01.2023.
SAP Test System: SAP S/4HANA SAP Utility 1809

Used Integration Tools: SAP PO 7.5
Certified Functions:
Use Case 1 Device Initialization Process
Use Case 2 Change Technical Master Data
Use Case 3 Discrete Meter Reading Process
Use Case 3a SAP Requests Meter Readings from MDUS
Use Case 3b Sending meter reading results from SAP to MDUS
Use Case 4 Reading One Customer's Meter: On Demand Read
Use Case 5 Uploading Usage Data to SAP EDM
Use Case 6a Remotely Disconnecting and Reconnecting a Meter
Use Case 6b Manually Disconnecting and Reconnecting a Smart Meter
Use Case 8 Event Management
Use Case 9 Text messaging to AMI device
For Details, see test report
Forrest Hu
Shawn Yang
Ye Zheng
SAP Labs, Toronto, Shanghai, 16.01.2020
SAP certification focuses on technical integration with SAP solutions. Vendor is responsible for the product
itself, its error-free operation, and adherence to applicable laws.
TEST REPORT FOR INTERFACE CERTIFICATION (BASED ON AN ICC INTEGRATION ASSESSMENT)
Interface Certification: Test Report

based on an ICC Integration Assessment
SAP Integration and Certification Center (SAP ICC)

Interface Certification: 15496
based on an ICC Integration Assessment

SAP Interface incl. Release
via SAP Utility AMI Use Cases
SAP Product incl. Release used for Test SAP S/4 HANA
SAP Solution Version SAP S/4HANA SAP Utility 1809
Hardware used for SAP Test System HPE
Operating System for SAP Test System Linux

Name of Vendor Hexing Electrical Co.,Ltd
Vendor Number 1607242
Vendor Product Name & Release Orca@MDC/MDM/Vending V8.0
Vendor Product Number (SAP internal) 28605

Vendor PI Content Package Name and SAP Enterprise Services of SAP Utility Use
Release Case
Hardware used for Vendor Test System HPE
Operating System of Vendor Test System Linux

Tools used for the Technical Integration SAP PO 7.5
Language Version Tested English
Certification Date 16.01.2020
Expiration Date 16.01.2023

Location Shanghai
Person Present - Vendor Peng Shizhou

Person Present - SAP Shawn Yang
Certified Functions:
Use Case 1 Device Initialization Process

Use Case 2 Change Technical Master Data
Use Case 3 Discrete Meter Reading Process
Use Case 3a SAP Requests Meter Readings from MDUS
Use Case 3b Sending meter reading results from SAP to MDUS
Use Case 4 Reading One Customer's Meter: On Demand Read
Use Case 5 Uploading Usage Data to SAP EDM
Use Case 6a Remotely Disconnecting and Reconnecting a Meter
Use Case 6b Manually Disconnecting and Reconnecting a Smart Meter
Use Case 8 Event Management
Use Case 9 Text messaging to AMI device
For Details, see test report

1. VENDOR COMPANY AND PRODUCT INFORMATION
Product information
Product web page: www.hxgroup.cn
Which releases of the SAP Business Solutions does SAP S/4HANA SAP Utility 1809
the third-party’s software support?
Please name the corresponding version of the corresponding version of vendor product:
software. 8.0
R/3 4.7
corresponding version of vendor product:
Other
corresponding version of vendor product:
For which databases is the software available? Mysql&Oracle
On which server platform(s) does the software run? SUSE Linux
2. FUNCTIONAL OVERVIEW
Supported Functions and Business Processes – General Description

Overview on the Orca@MDC/MDM/Vending will cover various key functions including
functionality and the but not limited to ...
purpose of the 3rd party • Accurate meter reading
product. • Device control and load control
• Device monitoring
• Data archiving and data processing
• Comprehensive reporting.
• Token management
• Vending services
The integration between Orca@MDC/MDM/Vending with SAP Billing
System will provide users with full advantage of smart metering
functionality.
Provide real time & accurate billing information which will reduces billing
errors.
With the help of this integration data accessibility will become easier for
the utility. This leads to better decision making at different levels and
eliminate poor quality data.

3. PERFORMANCE
3.1 PERFORMANCE AND SCALABILITY

Overview on the Main components:
architecture and design of 1.UA unified interface service program, which is used to interface
the product including services between HES low-level services and upper-level application
performance and systems, and can provide real-time command services, data export
scalability. services, and file synchronization services
2.Web Apps, a front-end application WEB interface, which provides
HES files, parameter configuration, data browsing, and equipment
maintenance and other application interfaces
3.MQ refers to the middleware of Apache's Active MQ messages, as a
front-end message server
4.DC, polling and reread process, used to schedule meter reading tasks,
manage meter reading task processes, and ensure data collection
integrity
5.FE, communication program, as a system service for communication
with equipment, supports multiple communication channel plugins and
power communication protocol plugins
Performance:
1. The single machine access point is 500,000, and the multiple
machine access point is 2,000,000;
2. Two load profiles with 30 min interval , our system can handle
2,000,000 meters data in 10 mins.
3. Real-time read single item efficiency of reading 200 meters can
less 5 seconds.
Scalablity:
1.Communication method expansion: The communication service
group is composed of individual communication services. If different
communication methods and different protocol methods are required to
expand, special communication services can be added independently.
These changes are transparent to other subsystems .
2.Communication protocol expansion: Support existing communication
protocol requirements, and also support the expansion of new
communication protocols without changing the existing architecture
and deployment. Each communication protocol is independent of each
other. As a plugin, it uses Java reflection technology to load and
invoke.
3.Service extension: The framework provides a front message bus, as
long as it follows certain specifications, it can easily access the system
and expand the service types of the front system. Such as extended on
demand service, device control service, parameter management
service.
3.2 QUALITY ASSURANCE

Overview on Quality The objectives of the Quality Assurance System are:
Assurance procedures a) To maintain an effective Quality Assurance System complying with
from the vendors to assure International Standard ISO9001 (Quality Systems).

that the interface design b) To achieve and maintain a level of quality which enhances the
and performance Company's reputation with customers.
consistently conform to c) To ensure compliance with relevant statutory and safety
specified requirements. requirements.
d) To endeavor, to make customers’ satisfaction with the service
provided by Hexing Group.
e)To pass technical integration test,business logic test,integrated
department test.
4. SOFTWARE PRODUCT ASSESSMENT
4.1 CHECK DOCUMENTATION

Functional Documentation yes
Installation Documentation yes
Maintenance Documentation yes
End User Documentation yes
Test Plan Documentation yes
Test Report Documentation yes
Benchmark Results Documentation No
4.2 INSTALL AND CONFIGURE PRODUCT FOR SAP INTEGRATION

How is the installation and setup of the good
product integration part done? average
poor
Remarks

5. TEST CASES
5.1 DESCRIBE TEST STEPS TO BE EXECUTED DURING TEST-DRIVE
UseCase
UseCase Step Result
Use Case 1: Device
Initialization
Process
Step 1:
Purcha
se
smart
meter
(No ES
involve
d)
<ns2:UtilitiesDeviceERPSmartMeterRegisterCreateReque
st xmlns:ns2="http://sap.com/xi/IS-U/Global2">
Step 5: <MessageHeader>
Install <UUID>48df37a9-2e10-1eea-87f9-
smart d34cc9dc6408</UUID>
meter
<CreationDateTime>2019-12-
technic
16T06:38:00Z</CreationDateTime>
ally in
SAP
<SenderBusinessSystemID>BS_S4H_100</SenderBusine
for
ssSystemID>
Utilitie
s, </MessageHeader>
which <UtilitiesDevice>
sends a <ID>2017104811</ID>
messag <Register>
e to <StartDate>2019-12-15</StartDate>
MDUS <EndDate>9999-12-31</EndDate>
(Utiliti
esDevi <UtilitiesMeasurementTaskID>000000000000000306</
ceERP UtilitiesMeasurementTaskID>
Smart
MeterR <UtilitiesObjectIdentificationSystemCodeText>101
egister 1</UtilitiesObjectIdentificationSystemCodeText>
Create
Reques <UtiltiesMeasurementTaskCategoryCode>2</Utilties
t_Out) MeasurementTaskCategoryCode>

<UtilitiesDivisionCategoryCode>1</UtilitiesDivis
ionCategoryCode>
<UtilitiesMeasurementRecurrenceCode>15</Utilitie
sMeasurementRecurrenceCode>
<TimeZoneCode>UTC+8</TimeZoneCode>
<Specifications>
<MeasureUnitCode>KWT</MeasureUnitCode>
<DecimalValuePrecision>
<TotalDigitNumberValue>2</TotalDigitNumberValue>
</DecimalValuePrecision>
<MeterReadingResultAdjustmentFactorValue>1.0</Me
terReadingResultAdjustmentFactorValue>
</Specifications>
</Register>
<SmartMeter>
<UtilitiesAdvancedMeteringSystemID>ORCA</Utiliti
esAdvancedMeteringSystemID>
</SmartMeter>
</UtilitiesDevice>
</ns2:UtilitiesDeviceERPSmartMeterRegisterCreate
Request>
<glob:UtilitiesDeviceERPSmartMeterRegisterCreateConf
irmation>
<MessageHeader>
<UUID>b3daf775-036d-4d38-9bdf-
35483d96a7de</UUID>
Step 6:
<ReferenceUUID>48df37a9-2e10-1eea-87f9-
MDUS
sends d34cc9dc6408</ReferenceUUID>
back a <CreationDateTime>2020-01-
confir 03T14:32:23+08:00</CreationDateTime>
mation
messag <SenderBusinessSystemID>BS_UIP</SenderBusinessSy
e stemID>
(Utiliti </MessageHeader>
esDevi <UtilitiesDevice>
ceERP <ID>2017104811</ID>
Smart </UtilitiesDevice>
MeterR <Log>
egister <Item>
Create <SeverityCode>1</SeverityCode>
Confir <Note>Relation save successed!</Note>
mation </Item>
_In) </Log>

</glob:UtilitiesDeviceERPSmartMeterRegisterCreat
eConfirmation>
Step 7:
Discret
e meter
reading
s
(Refer
to Use
Case 3)
Step 8: Set
up
smart
meter
billing
in SAP
for
Utilitie
s
(Smart
Meter
Utilitie
sMeasu
rement
TaskE
RPPoin
tOfDeli
veryAs
signed
Notific
ation_
Out)
Use Case 2: Change
Technical
Master Data
Step 1:
<ns2:UtilitiesDeviceERPSmartMeterRegisterChangeReque
Change
st xmlns:ns2="http://sap.com/xi/IS-U/Global2">
the
number <MessageHeader>
of <UUID>48df37a9-2e10-1eea-87f9-
register d34cc9dc6408</UUID>
s in <CreationDateTime>2019-12-
SAP 16T06:38:00Z</CreationDateTime>
for
Utilitie <SenderBusinessSystemID>BS_S4H_100</SenderBusine
s, ssSystemID>
which </MessageHeader>
then <UtilitiesDevice>
inform <ID>2017104811</ID>

s the <Register>
MDUS <StartDate>2019-12-15</StartDate>
(Utiliti <EndDate>9999-12-31</EndDate>
esDevi
ceERP <UtilitiesMeasurementTaskID>000000000000000306</
Smart UtilitiesMeasurementTaskID>
MeterR
egister <UtilitiesObjectIdentificationSystemCodeText>101
Change 1</UtilitiesObjectIdentificationSystemCodeText>
Reques
t_Out) <UtiltiesMeasurementTaskCategoryCode>2</Utilties
MeasurementTaskCategoryCode>
<UtilitiesDivisionCategoryCode>1</UtilitiesDivis
ionCategoryCode>
<UtilitiesMeasurementRecurrenceCode>15</Utilitie
sMeasurementRecurrenceCode>
<TimeZoneCode>UTC+8</TimeZoneCode>
<Specifications>
<MeasureUnitCode>KWT</MeasureUnitCode>
<DecimalValuePrecision>
<TotalDigitNumberValue>2</TotalDigitNumberValue>
</DecimalValuePrecision>
<MeterReadingResultAdjustmentFactorValue>1.0</Me
terReadingResultAdjustmentFactorValue>
</Specifications>
</Register>
<SmartMeter>
<UtilitiesAdvancedMeteringSystemID>ORCA</Utiliti
esAdvancedMeteringSystemID>
</SmartMeter>
</UtilitiesDevice>
</ns2:UtilitiesDeviceERPSmartMeterRegisterChange
Request>
Step 2: The <glob:UtilitiesDeviceERPSmartMeterRegisterChangeConf

MDUS irmation>
makes <MessageHeader>
the <UUID>026a4967-0bb3-4ef3-83bc-
change 945efb72e9e1</UUID>
in the <ReferenceUUID>48df37a9-2e10-1eea-87f9-
number d34cc9dc6408</ReferenceUUID>
of <CreationDateTime>2020-01-
register 03T14:32:43+08:00</CreationDateTime>
s and
sends <SenderBusinessSystemID>BS_UIP</SenderBusinessSy

back a stemID>
confir </MessageHeader>
mation <UtilitiesDevice>
(Utiliti <ID>2017104811</ID>
esDevi </UtilitiesDevice>
ceERP <Log>
Smart <Item>
MeterR <SeverityCode>1</SeverityCode>
egister <Note>Relation save successed!</Note>
Change </Item>
Confir </Log>
mation </glob:UtilitiesDeviceERPSmartMeterRegisterChang
_In) eConfirmation>
Use Case 3a: SAP

Requests Meter
Readings from
MDUS
<ns2:SmartMeterMeterReadingDocumentERPBulkCreateRe
quest xmlns:ns2="http://sap.com/xi/IS-U/Global2">
<MessageHeader>
<UUID>48df37a9-2e10-1eda-88ac-
Step 1:
75dfc1bdbcef</UUID>
SAP
for <CreationDateTime>2019-12-
Utilitie 18T06:57:41Z</CreationDateTime>
s sends
a <SenderBusinessSystemID>BS_S4H_100</SenderBusin
request essSystemID>
to </MessageHeader>
MDUS
that a <SmartMeterMeterReadingDocumentERPCreateReque
group stMessage>
of <MessageHeader>
meters <UUID>48df37a9-2e10-1eda-88ac-
be read 75dfc1bddcef</UUID>
as of a <CreationDateTime>2019-12-
given 18T06:57:41Z</CreationDateTime>
date,
past or
<SenderBusinessSystemID>BS_S4H_100</SenderBusin
future
essSystemID>
(Smart
Meter </MessageHeader>
MeterR <MeterReadingDocument>
eading <ID>335</ID>
Docum
entERP <MeterReadingReasonCode>9</MeterReadingReason
BulkCr Code>
eateRe <ScheduledMeterReadingDate>2019-12-
quest_ 09</ScheduledMeterReadingDate>
Out)

<UtilitiesAdvancedMeteringDataSourceTypeCode>0</
UtilitiesAdvancedMeteringDataSourceTypeCode>
<UtiltiesMeasurementTask>
<UtilitiesMeasurementTaskID>000000000000000311<
/UtilitiesMeasurementTaskID>
<UtilitiesObjectIdentificationSystemCodeText>000001
00</UtilitiesObjectIdentificationSystemCodeText>
<UtiltiesDevice>
<UtilitiesDeviceID>2017104811</UtilitiesDeviceID>
<SmartMeter>
<UtilitiesAdvancedMeteringSystemID>ORCA</Utilities
AdvancedMeteringSystemID>
</SmartMeter>
</UtiltiesDevice>
</UtiltiesMeasurementTask>
</MeterReadingDocument>
</SmartMeterMeterReadingDocumentERPCreateRequ
estMessage>
</ns2:SmartMeterMeterReadingDocumentERPBulkCre
ateRequest>
<glob:SmartMeterMeterReadingDocumentERPBulkCreateC
Step 2: The onfirmation>
MDUS <MessageHeader>
ackno <UUID>e94dcfff-d8d6-4bfe-b463-
wledge 324db97456a7</UUID>
s the <ReferenceUUID>48df37a9-2e10-1eda-88ac-
request 75dfc1bdbcef</ReferenceUUID>
and <CreationDateTime>2020-01-
inform 06T15:06:18+08:00</CreationDateTime>
s SAP
for <SenderBusinessSystemID>BS_UIP</SenderBusinessSy
Utilitie stemID>
s of </MessageHeader>
any
excepti
<SmartMeterMeterReadingDocumentERPCreateConfir
ons
mationMessage>
(Smart
Meter <MessageHeader>
MeterR <UUID>cf5cc173-ee3e-44fb-b5e4-
eading d1fe27d54069</UUID>
Docum <ReferenceUUID>48df37a9-2e10-1eda-88ac-
entERP 75dfc1bdbcef</ReferenceUUID>
BulkCr <CreationDateTime>2020-01-
eateCo 06T15:06:18+08:00</CreationDateTime>

nfirmat
ion_In) <SenderBusinessSystemID>BS_UIP</SenderBusinessSy
stemID>
</MessageHeader>
<MeterReadingDocument>
<ID>335</ID>
<Log>
<Item>
<SeverityCode>1</SeverityCode>
<Note>success</Note>
</Item>
</Log>
</SmartMeterMeterReadingDocumentERPCreateConfi
rmationMessage>
<Log>
<Item>
<Note>success</Note>
</Item>
</Log>
</glob:SmartMeterMeterReadingDocumentERPBulkCr
eateConfirmation>
<glob:MeterReadingDocumentERPResultBulkCreateReques
t>
<MessageHeader>
<UUID>a3d6006a-3295-428d-bbe5-
Step 3: The 9fbff4a6bd8c</UUID>
MDUS <ReferenceUUID>48df37a9-2e10-1eda-88ac-
perfor 75dfc1bddcef</ReferenceUUID>
ms the <CreationDateTime>2020-01-
reading 06T15:06:17+08:00</CreationDateTime>
s and <TestDataIndicator/>
sends <ReconciliationIndicator/>
them to
SAP
<SenderBusinessSystemID>BS_UIP</SenderBusinessSy
for
stemID>
Utilitie
s <RecipientBusinessSystemID/>
(Meter </MessageHeader>
Readin
gDocu <MeterReadingDocumentERPResultCreateRequestMes
mentE sage>
RPRes <MessageHeader>
ultBulk <UUID>099e6232-a309-4fc6-8c39-
Create 1e4f823c9c1d</UUID>
Reques <ReferenceUUID>48df37a9-2e10-1eda-88ac-
t_In) 75dfc1bddcef</ReferenceUUID>

06T15:06:17+08:00</CreationDateTime>
<TestDataIndicator/>
<ReconciliationIndicator/>
stemID>
<RecipientBusinessSystemID/>
</MessageHeader>
<ID>335</ID>
<MeterReadingReasonCode>9</MeterReadingReason
Code>
<UtiltiesDevice>
</UtiltiesDevice>
<Result>
<ActualMeterReadingDate>2020-01-
06</ActualMeterReadingDate>
<ActualMeterReadingTime>15:06:19</ActualMeterRea
dingTime>
<MeterReadingTypeCode>01</MeterReadingTypeCo
de>
<MeterReadingResultValue>2556.475</MeterReading
ResultValue>
</Result>
</MeterReadingDocumentERPResultCreateRequestMe
ssage>
</glob:MeterReadingDocumentERPResultBulkCreateR
equest>
Step 4: <ns2:MeterReadingDocumentERPResultBulkCreateConfirm
SAP ation xmlns:ns2="http://sap.com/xi/IS-U/Global2">
for <MessageHeader>
Utilitie <UUID>48df37a9-2e10-1eea-8c8a-

s 613a7b2a8dde</UUID>
confir <ReferenceUUID>48df37a9-2e10-1eda-88ac-
ms that 75dfc1bddcef</ReferenceUUID>
it <CreationDateTime>2020-01-
receive 06T15:06:20Z</CreationDateTime>
d and
upload <SenderBusinessSystemID>BS_S4H_100</SenderBusin
ed the
essSystemID>
reading
</MessageHeader>
s
(Meter
Readin <MeterReadingDocumentERPResultCreateConfirmatio
gDocu nMessage>
mentE <MessageHeader>
RPRes <UUID>48df37a9-2e10-1eea-8c8a-
ultBulk 613a7b2aadde</UUID>
Create <ReferenceUUID>099e6232-a309-4fc6-8c39-
Confir 1e4f823c9c1d</ReferenceUUID>
mation <CreationDateTime>2020-01-
_Out) 06T07:06:20Z</CreationDateTime>
essSystemID>
</MessageHeader>
<ID>335</ID>
<UtiltiesDevice>
<SmartMeter>
</SmartMeter>
</UtiltiesDevice>
<Log>
<BusinessDocumentProcessingResultCode>5</Busine
ssDocumentProcessingResultCode>
<MaximumLogItemSeverityCode>3</MaximumLogIte
mSeverityCode>
<Item>

<TypeID>569(EL)</TypeID>
<Note>Meter reading result for MR document
number 00000000000000000335 uploaded
successfully</Note>
</Item>
</Log>
</MeterReadingDocumentERPResultCreateConfirmati
onMessage>
<Log>
mSeverityCode>
<Item>
<Note>1 of 1 readings uploaded
successfully</Note>
</Item>
</Log>
</ns2:MeterReadingDocumentERPResultBulkCreateCo
nfirmation>
Use Case 3b:

Sending Meter
Reading
Results from
SAP to MDUS
Step 1: <ns2:SmartMeterMeterReadingDocumentERPResultCreate
Device Request xmlns:ns2="http://sap.com/xi/IS-U/Global2">
installa <MessageHeader>
tion <UUID>48df37a9-2e10-1eda-8a8e-
takes 793404677660</UUID>
place, a <CreationDateTime>2019-12-
meter
reading
result
is
entered essSystemID>
in SAP </MessageHeader>
for <MeterReadingDocument>
Utilitie <ID>366</ID>
s and
sent to <MeterReadingReasonCode>12</MeterReadingReaso
MDUS nCode>

(Smart <UtilitiesMeasurementTask>
Meter
MeterR <UtilitiesMeasurementTaskID>000000000000000332<
eading /UtilitiesMeasurementTaskID>
Docum <UtilitiesDevice>
entERP <UtilitiesDeviceID>10000758</UtilitiesDeviceID>
Result <SmartMeter>
Create
Reques
t_Out )
</SmartMeter>
</UtilitiesDevice>
</UtilitiesMeasurementTask>
<Result>
<MeterReadingDate>2019-12-
25</MeterReadingDate>
<MeterReadingTime>23:59:00</MeterReadingTime>
<MeterReadingTypeCode>1</MeterReadingTypeCod
e>
<MeterReadingResultValue>18.0</MeterReadingResul
tValue>
</Result>
</ns2:SmartMeterMeterReadingDocumentERPResultCr
eateRequest>
Step 2: The <glob:SmartMeterMeterReadingDocumentERPResultCreate

MDUS Confirmation>
ackno <MessageHeader>
wledge <UUID>20f9ad7c-6bc6-44a8-828c-
s the c724ab82cd50</UUID>
request <ReferenceUUID>48df37a9-2e10-1eda-8a8e-
and 793404677660</ReferenceUUID>
inform <CreationDateTime>2019-12-
s SAP 27T14:40:36+08:00</CreationDateTime>
for
Utilitie
s of
stemID>
any
</MessageHeader>
excepti
ons <MeterReadingDocument>
(Smart <ID>366</ID>
Meter </MeterReadingDocument>
MeterR <Log>
eading <Item>
Docum <SeverityCode>1</SeverityCode>
entERP <Note>Sync successed!</Note>

Result </Item>
Create </Log>
Confir </glob:SmartMeterMeterReadingDocumentERPResult
mation CreateConfirmation>
_In)
<glob:MeterReadingDocumentERPResultBulkCreateReques
t>
<MessageHeader>
<UUID>a3d6006a-3295-428d-bbe5-
9fbff4a6bd8c</UUID>
<ReferenceUUID>48df37a9-2e10-1eda-88ac-
75dfc1bddcef</ReferenceUUID>
<TestDataIndicator/>
<ReconciliationIndicator/>
Step 3: stemID>
Meter
reading
</MessageHeader>
result
is
change <MeterReadingDocumentERPResultCreateRequestMes
d in sage>
SAP <MessageHeader>
for <UUID>099e6232-a309-4fc6-8c39-
Utilitie 1e4f823c9c1d</UUID>
s, the <ReferenceUUID>48df37a9-2e10-1eda-88ac-
change 75dfc1bddcef</ReferenceUUID>
d meter <CreationDateTime>2020-01-
reading 06T15:06:17+08:00</CreationDateTime>
result <TestDataIndicator/>
is sent <ReconciliationIndicator/>
to
MDUS <SenderBusinessSystemID>BS_UIP</SenderBusinessSy
(chang stemID>
e
request
</MessageHeader>
)
(Smart
Meter <ID>335</ID>
MeterR
eading <MeterReadingReasonCode>9</MeterReadingReason
Docum Code>
entERP <UtiltiesMeasurementTask>
Result
Change <UtilitiesMeasurementTaskID>000000000000000311<
Reques /UtilitiesMeasurementTaskID>
t_Out)

<UtiltiesDevice>
</UtiltiesDevice>
<Result>
dingTime>
de>
ResultValue>
</Result>
</MeterReadingDocumentERPResultCreateRequestMe
ssage>
</glob:MeterReadingDocumentERPResultBulkCreateR
equest>
Step 4: The <ns2:MeterReadingDocumentERPResultBulkCreateConfirm

MDUS ation xmlns:ns2="http://sap.com/xi/IS-U/Global2">
ackno <MessageHeader>
wledge <UUID>48df37a9-2e10-1eea-8c8a-
s the 613a7b2a8dde</UUID>
request <ReferenceUUID>48df37a9-2e10-1eda-88ac-
and 75dfc1bdbcef</ReferenceUUID>
inform <CreationDateTime>2020-01-
s SAP 06T15:06:20Z</CreationDateTime>
for
Utilitie <SenderBusinessSystemID>BS_S4H_100</SenderBusin
s of essSystemID>
any </MessageHeader>
excepti
ons
<MeterReadingDocumentERPResultCreateConfirmatio
(Smart
nMessage>
Meter
MeterR <MessageHeader>
eading <UUID>48df37a9-2e10-1eea-8c8a-
Docum 613a7b2aadde</UUID>
entERP <ReferenceUUID>099e6232-a309-4fc6-8c39-
Result 1e4f823c9c1d</ReferenceUUID>
Change <CreationDateTime>2020-01-
Confir 06T07:06:20Z</CreationDateTime>

mation
_In) <SenderBusinessSystemID>BS_S4H_100</SenderBusin
essSystemID>
</MessageHeader>
<ID>335</ID>
<UtiltiesDevice>
<SmartMeter>
</SmartMeter>
</UtiltiesDevice>
<Log>
mSeverityCode>
<Item>
number 00000000000000000335 uploaded
successfully</Note>
</Item>
</Log>
</MeterReadingDocumentERPResultCreateConfirmati
onMessage>
<Log>
mSeverityCode>
<Item>

<Note>1 of 1 readings uploaded
successfully</Note>
</Item>
</Log>
</ns2:MeterReadingDocumentERPResultBulkCreateCo
nfirmation>
Use Case 4:
Reading One
Customer's
Meter: On
Demand Read
<ns2:SmartMeterMeterReadingDocumentERPCreateReques
t xmlns:ns2="http://sap.com/xi/IS-U/Global2">
<MessageHeader>
<UUID>48df37a9-2e10-1eea-89ac-
739dd03c4aa2</UUID>
Step 1: essSystemID>
SAP </MessageHeader>
for <MeterReadingDocument>
Utilitie <ID>342</ID>
s sends
a <MeterReadingReasonCode>9</MeterReadingReason
request Code>
to <ScheduledMeterReadingDate>2019-12-
MDUS 23</ScheduledMeterReadingDate>
to read
a <UtilitiesAdvancedMeteringDataSourceTypeCode>0</
certain UtilitiesAdvancedMeteringDataSourceTypeCode>
meter <UtiltiesMeasurementTask>
as of a
given
date,
past or
future
(Smart <UtilitiesObjectIdentificationSystemCodeText>000001
Meter 00</UtilitiesObjectIdentificationSystemCodeText>
MeterR <UtiltiesDevice>
eading
Docum <UtilitiesDeviceID>2017104811</UtilitiesDeviceID>
entERP <SmartMeter>
Create
Reques <UtilitiesAdvancedMeteringSystemID>ORCA</Utilities
t_Out) AdvancedMeteringSystemID>

</SmartMeter>
</UtiltiesDevice>
</ns2:SmartMeterMeterReadingDocumentERPCreateR
equest>
Step 2: The
MDUS
ackno
wledge
s the
request
and
inform
s SAP
for
Utilitie <glob:SmartMeterMeterReadingDocumentERPCreateConfir
s of mation>
any <MessageHeader>
excepti <UUID>49e1c9a6-524e-4472-a9a8-
ons c9e1b583b340</UUID>
(such <ReferenceUUID>48df37a9-2e10-1eea-89ac-
as the 739dd03c4aa2</ReferenceUUID>
meter <CreationDateTime>2020-01-
ID 06T08:52:39+08:00</CreationDateTime>
does
not <SenderBusinessSystemID>BS_UIP</SenderBusinessSy
match stemID>
its </MessageHeader>
inform <MeterReadingDocument>
ation)
<ID>342</ID>
(Smart
Meter
<Log>
MeterR
eading <Item>
Docum <SeverityCode>1</SeverityCode>
entERP <Note>success</Note>
Create </Item>
Confir </Log>
mation </glob:SmartMeterMeterReadingDocumentERPCreate
_In) Confirmation>
Step 3: The
MDUS <glob:MeterReadingDocumentERPResultCreateRequest>
perfor <MessageHeader>
ms the <UUID>3354b668-a11d-4399-8880-
reading 6db7c6dac0fe</UUID>
and <ReferenceUUID>48df37a9-2e10-1eea-89ac-
sends it 739dd03c4aa2</ReferenceUUID>
to SAP <CreationDateTime>2020-01-
for 06T08:52:38+08:00</CreationDateTime>

Utilitie <TestDataIndicator/>
s <ReconciliationIndicator/>
(Smart
Meter <SenderBusinessSystemID>BS_UIP</SenderBusinessSy
MeterR stemID>
eading <RecipientBusinessSystemID/>
Docum </MessageHeader>
entERP
Result
<ID>342</ID>
Create
Reques
t_In) <MeterReadingReasonCode>9</MeterReadingReason
Code>
<UtiltiesDevice>
</UtiltiesDevice>
<Result>
dingTime>
de>
ResultValue>
</Result>
</glob:MeterReadingDocumentERPResultCreateReque
st>
<ns2:MeterReadingDocumentERPResultCreateConfirmatio
Step 4:
n xmlns:ns2="http://sap.com/xi/IS-U/Global2">
SAP
for <MessageHeader>
Utilitie <UUID>48df37a9-2e10-1eea-89bf-
s 0ca0eeac3f7b</UUID>
confir <ReferenceUUID>48df37a9-2e10-1eea-89ac-
ms that 739dd03c4aa2</ReferenceUUID>
it <CreationDateTime>2019-01-
receive 06T08:52:38Z</CreationDateTime>

d and
upload <SenderBusinessSystemID>BS_S4H_100</SenderBusin
ed the essSystemID>
reading </MessageHeader>
(Meter <MeterReadingDocument>
Readin <ID>342</ID>
gDocu <UtiltiesMeasurementTask>
mentE
RPRes
<UtilitiesObjectIdentificationSystemCodeText>111</U
ultCrea
tilitiesObjectIdentificationSystemCodeText>
teConfi
rmatio <UtiltiesDevice>
n_Out)
<SmartMeter>
</SmartMeter>
</UtiltiesDevice>
<Log>
mSeverityCode>
<Item>
number 00000000000000000342 uploaded
successfully</Note>
</Item>
</Log>
</ns2:MeterReadingDocumentERPResultCreateConfir
mation>
Use Case 5:
Uploading
Usage Data to
SAP EDM
Pre-
requisit <ns2:UtilitiesTimeSeriesERPMeasurementTaskAssignmentC
e Step hangeRequest xmlns:ns2="http://sap.com/xi/IS-
1: To U/Global2">
be able <MessageHeader>
to <UUID>48df37a9-2e10-1eea-8d83-

upload a4e5b3be13f2</UUID>
profile <CreationDateTime>2020-01-
data 11T02:50:40Z</CreationDateTime>
from
Hexing <SenderBusinessSystemID>BS_S4H_100</SenderBusin
to essSystemID>
SAP, </MessageHeader>
profile
<UtilitiesTimeSeries
data
measurementTaskAssignmentRoleListCompleteTransm
such as
issionIndicator="true">
profile
headers <ID>13</ID>
and
profile <UtilitiesMeasurementRecurrenceCode>15</UtilitiesM
allocati easurementRecurrenceCode>
ons <MeasureUnitCode>KWH</MeasureUnitCode>
must <DecimalValuePrecision>
be
synchr <TotalDigitNumberValue>31</TotalDigitNumberValu
onized e>
betwee </DecimalValuePrecision>
n
system <ItemsRemotelyStoredIndicator>true</ItemsRemotely
s. StoredIndicator>
When <MeasurementTaskAssignmentRole>
there is
<StartDate>2020-01-11</StartDate>
a new
<StartTime>00:00:00</StartTime>
profile
allocat <EndDate>9999-12-31</EndDate>
ed to a <EndTime>23:59:59</EndTime>
register
, SAP <UtilitiesTimeSeriesAssignmentRoleCode>KWH</Utilit
sends iesTimeSeriesAssignmentRoleCode>
the
mappin <UtilitiesMeasurementTaskID>000000000000000351<
g /UtilitiesMeasurementTaskID>
betwee <UtilitiesDeviceSmartMeter>
n
Profile <UtilitiesAdvancedMeteringSystemID>ORCA</Utilities
ID and AdvancedMeteringSystemID>
Measur </UtilitiesDeviceSmartMeter>
ementT </MeasurementTaskAssignmentRole>
ask ID
</UtilitiesTimeSeries>
to
</ns2:UtilitiesTimeSeriesERPMeasurementTaskAssignm
Hexing
entChangeRequest>
.
(Utiliti
esTime
SeriesE
RPMea

sureme
ntTask
Assign
mentC
hangeR
equest_
Out)
<glob:UtilitiesTimeSeriesERPMeasurementTaskAssignment
ChangeConfirmation>
<MessageHeader>
<UUID>f1b64f12-db7b-4fc7-9010-
Pre- be314db42002</UUID>
requisit <ReferenceUUID>48df37a9-2e10-1eea-8d83-
e Step a4e5b3be13f2</ReferenceUUID>
2: AMI <CreationDateTime>2020-01-
system 11T10:50:41+08:00</CreationDateTime>
sends
confir <SenderBusinessSystemID>BS_UIP</SenderBusinessSy
mation stemID>
to SAP </MessageHeader>
(Utiliti <UtilitiesTimeSeries>
esTime
<ID>13</ID>
SeriesE
</UtilitiesTimeSeries>
RPMea
<Log>
sureme
ntTask <Item>
Assign <SeverityCode>1</SeverityCode>
mentC <Note>Sync successed!</Note>
hangeC </Item>
onfirm </Log>
ation_I </glob:UtilitiesTimeSeriesERPMeasurementTaskAssign
n) mentChangeConfirmation>
Pre-
requisit
e Step
3: On
daily
basis,
SAP
will
execute
batch
progra
m to
send
profile
allocati
on
(attribu

te ID)
for
each
device
which
will
trigger
Hexing
send
profile
vaule
to
SAP.
(Utiliti
esTime
SeriesE
RPRep
lication
BulkRe
quest_
Out)
<glob:UtilitiesTimeSeriesERPItemBulkCreateRequest
xmlns:glob='http://sap.com/xi/SAPGlobal20/Global'
Pre- xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'>
requisit <MessageHeader>
e Step <UUID>15847471-217d-4ed4-94b4-727d91a80a75</UUID>
4: In <CreationDateTime>2020-01-
respons 08T14:01:54+08:00</CreationDateTime>
e to <SenderBusinessSystemID>BS_UIP</SenderBusinessSystemID>
Utilitie </MessageHeader>
sTimeS <UtilitiesTimeSeriesERPItemCreateRequestMessage>
eriesE <MessageHeader>
RPRep <UUID>022bffd6-724f-4d67-8913-161b7edd0875</UUID>
lication <CreationDateTime>2020-01-
BulkRe
<SenderBusinessSystemID>BS_UIP</SenderBusinessSystemID>
quest_
</MessageHeader>
Out,
<UtilitiesTimeSeries>
AMI
<ID>12</ID>
system <Item>
sends <Quantity unitCode='KWH'>26</Quantity>
data to <UTCValidityStartDateTime>2020-01-
SAP 03T19:00:00+08:00</UTCValidityStartDateTime>
for <UTCValidityEndDateTime>2020-01-
Utilitie 03T19:15:00+08:00</UTCValidityEndDateTime>
s <ItemStatus>
(Utiliti <UtilitiesTimeSeriesItemTypeCode>0001</UtilitiesTimeSeriesIte
esTime mTypeCode>
SeriesE </ItemStatus>
RPItem </Item>
BulkCr </UtilitiesTimeSeries>
eateRe </UtilitiesTimeSeriesERPItemCreateRequestMessage>

quest_I
</glob:UtilitiesTimeSeriesERPItemBulkCreateRequest>
n)
Use Case 6a:
Remotely
Disconnecting
and
Reconnecting a
Meter
Step 1: The
custom
er does
not pay
his bill
Step 2: The
custom
er's
delinqu
ent
accoun
t
reaches
a
dunnin
g level
that
require
s
discon
nection
of
service
Step 3: A <ns2:SmartMeterUtilitiesConnectionStatusChangeRequestE
call RPCreateRequest xmlns:ns2="http://sap.com/xi/IS-
center U/Global2">
employ <MessageHeader>
ee fills <UUID>48df37a9-2e10-1eea-8ada-
in a 5bff2b470af0</UUID>
discon <CreationDateTime>2019-12-
nection
or
reconn
ection
docum essSystemID>
ent in </MessageHeader>
SAP <UtilitiesConnectionStatusChangeRequest>
for <ID>000000000006</ID>
Utilitie <CategoryCode>1</CategoryCode>
s,
which <UtilitiesServiceDisconnectionReasonCode>03</Utiliti

sends a esServiceDisconnectionReasonCode>
messag <PlannedProcessingDateTime>2019-12-
e to the 30T07:06:17Z</PlannedProcessingDateTime>
MDUS
(Smart <ImmediateStatusChangeIndicator>true</ImmediateS
Meter tatusChangeIndicator>
Utilitie <DeviceConnectionStatus>
sConne
ctionSt
<SmartMeter>
atusCh
angeRe
quest_ <UtilitiesAdvancedMeteringSystemID>ORCA</Utilities
Out) AdvancedMeteringSystemID>
</SmartMeter>
</DeviceConnectionStatus>
</UtilitiesConnectionStatusChangeRequest>
</ns2:SmartMeterUtilitiesConnectionStatusChangeReq
uestERPCreateRequest>
<glob:SmartMeterUtilitiesConnectionStatusChangeRequest
ERPCreateConfirmation>
<MessageHeader>
<ID/>
<UUID>ee5cbf9f-327c-494b-a9ff-
43e25e5c2eb1</UUID>
<ReferenceUUID>48df37a9-2e10-1eea-8ada-
Step 4: The 5bff2b470af0</ReferenceUUID>
MDUS <CreationDateTime>2019-12-
confir 30T15:06:39+08:00</CreationDateTime>
ms that <TestDataIndicator/>
the <ReconciliationIndicator/>
meter
has <SenderBusinessSystemID>BS_S4H_100</SenderBusin
been essSystemID>
discon <RecipientBusinessSystemID/>
nected </MessageHeader>
(or <UtilitiesConnectionStatusChangeRequest>
reconn <ID>000000000006</ID>
ected)
<CategoryCode>1</CategoryCode>
(Smart
<DeviceConnectionStatus>
Meter
Utilitie <ProcessingDateTime>2019-12-
sConne 30T15:06:39+08:00</ProcessingDateTime>
ctionSt
atusCh <UtilitiesDeviceConnectionStatusProcessingResultCod
angeRe e>2</UtilitiesDeviceConnectionStatusProcessingResult
questE Code>
RPCre <UtilitiesDeviceID/>
ateCon </DeviceConnectionStatus>
firmati </UtilitiesConnectionStatusChangeRequest>
on_In) <Log>

<Note>Executed Successfully</Note>
</Log>
</glob:SmartMeterUtilitiesConnectionStatusChangeRe
questERPCreateConfirmation>
Use Case 6b:

Manually
Disconnecting
and
Reconnecting a
Smart Meter
Step 1: The
custom
er does
not pay
their
bill
Step 2: The
custom
er's
delinqu
ent
accoun
t
reaches
a
dunnin
g level
that
require
s the
service
to be
discon
nected
Step 3: A
call
center
employ
ee fills
in a
discon
nection
or
reconn
ection
docum
ent in

SAP
for
Utilitie
s,
creatin
ga
service
order
that is
execute
d by a
service
technic
ian
<ns2:SmartMeterUtilitiesConnectionStatusChangeRequestERPBul
kNotification xmlns:ns2="http://sap.com/xi/IS-U/Global2">
<MessageHeader>
<UUID>48df37a9-2e10-1eea-8cb8-52db824e8002</UUID>
Step 4: The <SenderBusinessSystemID>BS_S4H_100</SenderBusinessSystem

discon ID>
nection </MessageHeader>
/
reconn <SmartMeterUtilitiesConnectionStatusChangeRequestERPNotific
ection ationMessage>
is <MessageHeader>
execute <UUID>48df37a9-2e10-1eea-8cb8-52db824ea002</UUID>
d <CreationDateTime>2020-01-
manual 08T02:57:22Z</CreationDateTime>
ly by
the <SenderBusinessSystemID>BS_S4H_100</SenderBusinessSystem
service ID>
technic </MessageHeader>
ian, the <UtilitiesConnectionStatusChangeRequest>
discon <ID>000000000008</ID>
nection <CategoryCode>1</CategoryCode>
/
<UtilitiesServiceDisconnectionReasonCode>03</UtilitiesServiceD
reconn
isconnectionReasonCode>
ection
<DeviceConnectionStatus>
docum
<ProcessingDateTime>2020-01-
ent is
07T23:00:00Z</ProcessingDateTime>
update <UtilitiesDeviceID>2017104811</UtilitiesDeviceID>
d in the <SmartMeter>
system,
the <UtilitiesAdvancedMeteringSystemID>ORCA</UtilitiesAdvanced
inform MeteringSystemID>
ation is </SmartMeter>
sent to </DeviceConnectionStatus>
MDUS </UtilitiesConnectionStatusChangeRequest>

</SmartMeterUtilitiesConnectionStatusChangeRequestERPNotific
ationMessage>
</ns2:SmartMeterUtilitiesConnectionStatusChangeRequest
ERPBulkNotification>
Use Case 8: Event

Management
<glob:UtilitiesSmartMeterEventERPBulkCreateRequest>
<MessageHeader>
<UUID>5a1b806c-86ea-411f-a4c6-
9aa7452af1fd</UUID>
stemID>
</MessageHeader>
<UtilitiesSmartMeterEventERPCreateRequestMessage>
<MessageHeader>
<UUID>857032d1-98c0-42be-baf7-
3a2934bf354a</UUID>
stemID>
Step 1: </MessageHeader>
Extern <UtilitiesSmartMeterEvent>
al <ID>3N83BiL2qK8jSCaHqyxuec</ID>
system <UtilitiesDeviceID>2017104811</UtilitiesDeviceID>
sends <DateTime>2020-01-
AMI 08T15:36:44+08:00</DateTime>
event <CategoryCode>9002</CategoryCode>
messag <TypeCode>0502</TypeCode>
e to
SAP
</UtilitiesSmartMeterEvent>
for
Utilitie
s </UtilitiesSmartMeterEventERPCreateRequestMessage
(Utiliti >
esSmar
tMeter <UtilitiesSmartMeterEventERPCreateRequestMessage>
EventE <MessageHeader>
RPBul <UUID>7766358f-f520-415a-a4c3-
kCreat b45b0b42d87e</UUID>
eReque <CreationDateTime>2020-01-
st_In) 08T19:26:00+08:00</CreationDateTime>

stemID>
</MessageHeader>
<UtilitiesSmartMeterEvent>
<ID>zcZAlwk0qCcCFxufh9To31</ID>
<DateTime>2020-01-
08T11:12:53+08:00</DateTime>
<TypeCode>0502</TypeCode>
</UtilitiesSmartMeterEventERPCreateRequestMessage
>
<MessageHeader>
<UUID>655214fd-3fc0-4cc6-b651-
46a9ab3e334d</UUID>
stemID>
</MessageHeader>
<ID>U8zX1Pwdqx4xj8sWeqGA86</ID>
<DateTime>2020-01-
08T10:46:50+08:00</DateTime>
>
<MessageHeader>
<UUID>98db09ac-5d7a-42c8-864d-
c9692aa93f9d</UUID>

stemID>
</MessageHeader>
<ID>70ioqg20rNKNHIxeIOzDe6</ID>
<DateTime>2020-01-
08T10:27:25+08:00</DateTime>
>
<MessageHeader>
<UUID>75ab8a70-d5fc-4758-9ace-
636aa13e3b93</UUID>
stemID>
</MessageHeader>
<ID>4Z6OyVhcs1st8HjkUf7r7b</ID>
<DateTime>2020-01-
07T14:18:45+08:00</DateTime>
>
</glob:UtilitiesSmartMeterEventERPBulkCreateRequest
>
<ns2:UtilitiesSmartMeterEventERPBulkCreateConfirmation
Step 2: To
xmlns:ns2="http://sap.com/xi/IS-U/Global2">
send
creatio <MessageHeader>
n <UUID>48df37a9-2e10-1eea-8cc1-
confir 34bff85bc9d3</UUID>
mation <ReferenceUUID>5a1b806c-86ea-411f-a4c6-
of 9aa7452af1fd</ReferenceUUID>
utilities <CreationDateTime>2020-01-
smart 08T11:26:01Z</CreationDateTime>

meter
event <SenderBusinessSystemID>BS_S4H_100</SenderBusin
request essSystemID>
as bulk </MessageHeader>
(Utiliti
esSmar <UtilitiesSmartMeterEventERPCreateConfirmationMess
tMeter age>
EventE
<MessageHeader>
RPBul
<UUID>48df37a9-2e10-1eea-8cc1-
kCreat
34bff85be9d3</UUID>
eConfir
mation <ReferenceUUID>857032d1-98c0-42be-baf7-
_Out) 3a2934bf354a</ReferenceUUID>
essSystemID>
</MessageHeader>
<ID>3N83BiL2qK8jSCaHqyxuec</ID>
<Log>
mSeverityCode>
<Item>
<TypeID>023(EE_AMI_EM)</TypeID>
<Note>Immediate rejection from
customizing parameter</Note>
</Item>
</Log>
</UtilitiesSmartMeterEventERPCreateConfirmationMes
sage>
<UtilitiesSmartMeterEventERPCreateConfirmationMess
age>
<MessageHeader>
34bff85c09d3</UUID>
<ReferenceUUID>7766358f-f520-415a-a4c3-
b45b0b42d87e</ReferenceUUID>

essSystemID>
</MessageHeader>
<ID>zcZAlwk0qCcCFxufh9To31</ID>
<Log>
mSeverityCode>
<Item>
</Item>
</Log>
sage>
age>
<MessageHeader>
34bff85c29d3</UUID>
<ReferenceUUID>655214fd-3fc0-4cc6-b651-
46a9ab3e334d</ReferenceUUID>
essSystemID>
</MessageHeader>
<ID>U8zX1Pwdqx4xj8sWeqGA86</ID>
<Log>

mSeverityCode>
<Item>
</Item>
</Log>
sage>
age>
<MessageHeader>
34bff85c49d3</UUID>
<ReferenceUUID>98db09ac-5d7a-42c8-864d-
c9692aa93f9d</ReferenceUUID>
essSystemID>
</MessageHeader>
<ID>70ioqg20rNKNHIxeIOzDe6</ID>
<Log>
mSeverityCode>
<Item>
</Item>

</Log>
sage>
age>
<MessageHeader>
34bff85c69d3</UUID>
<ReferenceUUID>75ab8a70-d5fc-4758-9ace-
636aa13e3b93</ReferenceUUID>
essSystemID>
</MessageHeader>
<ID>4Z6OyVhcs1st8HjkUf7r7b</ID>
<Log>
mSeverityCode>
<Item>
</Item>
</Log>
sage>
<Log>
mSeverityCode>
<Item>

<Note>All events were received in
error</Note>
</Item>
</Log>
</ns2:UtilitiesSmartMeterEventERPBulkCreateConfirma
tion>
Use Case 9: Text

Messaging to
AMI Device
Step 1:
Compo
se
messag
e in
SAP
for
Utilitie
s
<ns2:UtilitiesDeviceERPSmartMeterTextBulkNotification
xmlns:ns2="http://sap.com/xi/IS-U/Global2">
<MessageHeader>
<UUID>48df37a9-2e10-1eda-8cda-
0b6fd70c2581</UUID>
Step 2: <SenderBusinessSystemID>BS_S4H_100</SenderBusin
SAP essSystemID>
for </MessageHeader>
Utilitie
s sends <UtilitiesDeviceERPSmartMeterTextNotificationMessag
out a e>
text <MessageHeader>
messag
<UUID>48df37a9-2e10-1eda-8cda-
e to an
0b6fd70c4581</UUID>
AMI
device
(Utiliti 09T11:08:25Z</CreationDateTime>
esDevi
ceERP <SenderBusinessSystemID>BS_S4H_100</SenderBusin
Smart essSystemID>
MeterT </MessageHeader>
extBul <UtilitiesDevice>
kNotifi <ID>2017104811</ID>
cation_ <SmartMeter>
Out)

</SmartMeter>
<Text>
<ID>IDytgIuG7jgCsWjlrmm5WG</ID>
<DisplayValidityEndTimePoint>
<DateTime>2020-01-09T15:59:59Z</DateTime>
</DisplayValidityEndTimePoint>
<TextPlainContent>
<Text
languageCode="en">{"Encryption":"0","AuthMode":"G
MAC"}</Text>
</TextPlainContent>
</Text>
</UtilitiesDevice>
</UtilitiesDeviceERPSmartMeterTextNotificationMessa
ge>
</ns2:UtilitiesDeviceERPSmartMeterTextBulkNotificatio
n>
5.2 DESCRIBE PERFORMANCE LOAD TEST STEPS TO BE EXECUTED DURING TEST-

DRIVE
N/A
6. ADDITIONAL SERVICES AND SUPPORT
Does the partner company offer consulting yes

services for this product?
no
Remarks
Does the partner company offer training yes

classes for this product?
no
Remarks

Does the partner company offer general yes

problem support for this product?
no
Remarks
7. PARTNER CONFIRMATION
Partner states that by following the guidelines of the ICC Integration Assessment or ICC Integration
Guide, only the integration technologies listed in this document are used in the described interface
software.
Certification is only valid for the SAP release and partner product release noted in this document;
in the event of SAP or partner release changes SAP offers re-certification of the interface software.

© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
www.sap.com/contactsap
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
information and notices.

Certificacion ORCA PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Certificacion ORCA PDF

Uploaded by

Copyright:

Available Formats

Certificate

SAP INTEGRATION CERTIFICATION

The certification test is documented in report no. 15496 and expires on

SAP Test System: SAP S/4HANA SAP Utility 1809

For Details, see test report

Interface Certification: Test Report

SAP Integration and Certification Center (SAP ICC)

Interface Certification: 15496

based on an ICC Integration Assessment

SAP Solution Version SAP S/4HANA SAP Utility 1809

Hardware used for SAP Test System HPE

Operating System for SAP Test System Linux

Vendor Number 1607242

Vendor Product Name & Release Orca@MDC/MDM/Vending V8.0

Vendor Product Number (SAP internal) 28605

Operating System of Vendor Test System Linux

Language Version Tested English

Certification Date 16.01.2020

Expiration Date 16.01.2023

Person Present - Vendor Peng Shizhou

Use Case 1 Device Initialization Process

For Details, see test report

SAP Integration and Certification Center (SAP ICC)

1. VENDOR COMPANY AND PRODUCT INFORMATION

For which databases is the software available? Mysql&Oracle

On which server platform(s) does the software run? SUSE Linux

Supported Functions and Business Processes – General Description

SAP Integration and Certification Center (SAP ICC)

3.1 PERFORMANCE AND SCALABILITY

3.2 QUALITY ASSURANCE

SAP Integration and Certification Center (SAP ICC)

4. SOFTWARE PRODUCT ASSESSMENT

4.1 CHECK DOCUMENTATION

4.2 INSTALL AND CONFIGURE PRODUCT FOR SAP INTEGRATION

SAP Integration and Certification Center (SAP ICC)

5.1 DESCRIBE TEST STEPS TO BE EXECUTED DURING TEST-DRIVE

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

Step 2: The <glob:UtilitiesDeviceERPSmartMeterRegisterChangeConf

SAP Integration and Certification Center (SAP ICC)

Use Case 3a: SAP

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

Use Case 3b:

SAP Integration and Certification Center (SAP ICC)

Step 2: The <glob:SmartMeterMeterReadingDocumentERPResultCreate

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

Step 4: The <ns2:MeterReadingDocumentERPResultBulkCreateConfirm

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)

SAP Integration and Certification Center (SAP ICC)