Side-by-Side Extension of SAP Asset Performance Management: Overview
In this blog series, we shall explore various approaches to extend the SAP Asset Performance Management (hereinafter referred to as “APM“ for brevity), to meet the specific business requirements of the customers. We shall focus on custom / third-party applications, which are developed and operated either in external platforms or in SAP Business Technology Platform (hereinafter referred to as “BTP“ for brevity).
APM presents its features to end users as applications through standard SAP Fiori launchpad (hereinafter referred to as “standard launchpad” for brevity). The applications are organized into groups and catalogs in the standard launchpad. Visibility and access to these applications is managed using standard roles, which are assigned to end users through creation of role collections, as described in help page Creating and Assigning Role Collections | SAP Help Portal.
During implementation phase or over the operational lifetime of any standardized software, customers often want to extend the solution by adding custom and/or third-party applications that differentiates their business model and practices from rest of the industry. APM supports these scenarios through side-by-side extension techniques.
Below diagram depicts the typical solution landscape for side-by-side extension of APM with custom and third-party applications.
In the following series of blog posts, we shall explore the steps to create new custom applications and integrate existing custom / third-party applications into a custom launchpad, along with standard applications. We shall start with a bare bones consumer sub-account with active APM subscription and incrementally add solution components and connections to that sub-account, in each of the blog posts, to eventually arrive at the depicted solution landscape.
- Build Custom Launchpad ➤ Using SAP Build Work Zone, standard edition service build a custom launchpad and add APM standard applications to it, by organizing the content using Groups, Catalogs and Business Roles.
- Integrate Custom / Third-Party Applications into Launchpad ➤ Integrate external (non-BTP) web based custom or third-party application into the custom launchpad, alongside the standard applications.
- Build Custom Application with SAP Business Application Studio ➤ Create a custom application that consumes an OData API from SAP S/4HANA system connected to APM, using the SAP Business Application Studio and integrate it into custom launchpad.
Stay tuned for further blog posts in the series. Share your feedback or thoughts in the comment section of this blog post.
Furthermore, explore our SAP Asset Performance Management Topic Page and follow the tag SAP Asset Performance Management to not miss out on more content to come! Don’t forget to submit or vote for the improvement you would like to see in Customer Influence!