| Status | |
|---|---|
| Owner | YILMAZTURK-ext, Gokhan |
| Stakeholders | LEIGHTON-ext, Dean |
| Jira Request ID | |
| Jira Development ID |
| Implementing System | SAP S/4HANA, SAP APM |
|---|---|
| Invoked by/Invokes | Link to any Integration Process spec which is related to this System Interface, e.g. because it is invoking this interface, or because this interface is sending data to it. |
| Business Process Reference | 7.03.02 - Monitor Asset Performance |
The purpose of this document is to define the functional and configuration requirements to integrate SAP S/4HANA Private Cloud Edition (2025) with SAP Asset Performance Management (APM) on SAP BTP for SyWay Project.
SAP APM provides advanced reliability engineering tools (RCM, FMEA, Maintenance Strategy Optimization). For these tools to function, a seamless synchronization of Master Data (Technical Objects) and Transactional Data (Maintenance Orders/Notifications) is required between the S/4HANA core and the APM cloud tenants.
The scope includes the end-to-end connectivity and data synchronization framework:
Insert the flowchart and fill in the steps
Step | Description | Comment |
|---|---|---|
1 | Data Extraction | The S/4HANA system identifies relevant technical objects based on "Scope Filters" defined in the configuration. |
2 | Synchronization | Data is pushed/pulled via OData services through the SAP Cloud Connector to the APM Tenant on BTP |
3 | Feedback Loop | Maintenance recommendations generated in APM are sent back to S/4HANA to create or update Maintenance Plans/Orders |
Maintenance Work Integration
To enable the value help for selecting alerts and notifications in the Condition tab of the Manage Rules app, another destination for rules needs to be configured in the tenant.
You have:
Created the service instances and service keys for SAP Asset Performance Management. For more information, refer to Create Service Instances.
Generated the service instance. For more information, refer to Creating Service Instances in Cloud Foundry.
Generated the service keys. For more information, refer to Creating Service Keys in Cloud Foundry.
You create a destination named RULES_EIOT_DESIGNTIME in the subscribing subaccount by providing the connection details to SAP Asset Performance Management Rules Service.
This template section may be used to specify the custom API design. The requirement can be for an API provider which means the API will be designed in the system or can be for an API consumer which means that an API will be consumed in the system.
Following key components must be activated for the integration;
Component | Requirement |
OData v2 Services |
|
OData v4 Service Groups |
|
Configure Enterprise Event Enablement framework | SAP Event Mesh is a fully managed cloud service enabling real-time and asynchronous communication between applications through events. Follow the sequence below to set up the Enterprise Event Enablement:
|
OAuth 2.0 | Setup in S/4HANA (Transaction OA2C_CONFIG) using the Client ID and Secret from the BTP Service Key. |
This interface can be monitored from SAP APM using the app "Integration Monitor", for checking both Master Data & Configuration Data Synchronizations.
Please describe delivery requirements driven by message sequencing, i.e. specific order, impact of disruption of sequence, are duplicates allowed, etc.
Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)
Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures
Please provide some guidance and/or test data to help the developer unit test the interface. Please include both positive and negative testing (to validate error situations handling)
The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again, or explain how to create new input data to the test. In particular, the developer will need logons for test users representing the various roles within the approval process.
| ID | Condition | Expected Results |
|---|---|---|
List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.
| Package Name | Parent Package |
|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.
