The previous blog of this series – Implementing Services in ABAP (Part 8) – showed you how the previously modeled & defined service interface can be implemented using ABAP technology. This blog highlights the concept of custom enterprise services (ES) provisioned by SAP Custom Development. Custom ES bridge the gap between the standard enterprise service and customer specific requirements of enterprise service. With this blog we try to highlight the unique value proposition of and key differentiator for custom ES.
Custom ES cover the following use cases to fulfill unique customer requirements:
- No enterprise service exists for a standard business process: Custom ES act as Gap Fillers.
- Custom has older system and no upgrade is planned: Downport standard ES to create a new custom ES in older system.
- Customers already existing functionalities have to be encapsulated: Create a new customer specific custom ES.
- Bundling information of different business objects in one enterprise service: Transformed custom enterprise service.
- Call single custom enterprise service to get the details of multiple entities of a business object instead of calling standard enterprise service multiple times: Mass (Bulk) enabled custom enterprise service.
Hence when neither extension (new versions of standard ES by SAP) nor enhancement (as per Enhancement Concept) fulfills customer specific requirements the need for creation of custom ES arise.
Custom ES: Methodology & Governance
In terms of Methodology and Governance custom ES offer the following unique advantages:
- Custom ES follow SAP standard methodology, governance & implementation guidelines for service provisioning.
- Custom ES follow the well defined SAP internal governance process for service provisioning at SAP. Hence Custom ES utilize the same (already tried and tested) infrastructure which is used for governing standard ES.
- Custom Development is the central entity in SAP’s (internal) SOA ecosystem for custom service provisioning. Hence we can leverage the contacts with the standard development governance teams to harmonize custom enterprise services across SAP Business Suite.
Custom ES: Shipment and Delivery
From a provisioning perspective custom ES involves two parts: Service content (ESR content which is the service definition consisting of harmonized service signature) and service implementation (backend implementation of the service in ABAP/Java). Custom Development offers agility in custom ES delivery by offering delivery of individual part as per customer requirement:
- Service content only delivery: Customer intends to have SAP PIC approved custom enterprise service content within his own ESR.
- Custom ES implementation only delivery: Customer does not have ESR but has custom ES implementation requirement.
- Both service content and service implementation delivery
8D Composite Case Study
Last but not the least we have a case study for you highlighting the custom ES service provisioning aspects for 8D Composite application.
Custom Development v/s PdES
Upto this point you might have wondered how custom development custom ES and the previously mentioned Partner delivered enterprise services fit together?
In both the approach the services are built according to SAP’s modeling and definition guidelines, whereas SAP Custom Development takes an SAP internal approach for building the services and the PdES takes an external partner driven development approach. SAP Custom Development follows the SAP internal governance process and quality gates (Lean process as compared to standard is adopted).
Summary & Further References
To sum up the end-to-end perspective (inception to delivery) on provisioning a custom ES can be depicted via the following diagram:
Customers can get custom enterprise services individually based on their requirements in a very simple way.
In case you are interested learning more about custom ES then visit PdES: SAP Custom Enterprise Services page to discover custom ES by SAP Custom Development and know more details regarding them.
In the following the links to all other blogs from the PdES Architecture Series:
1. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Introduction (Part 1) – Screencam
2. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Outlining the ‘way to deliver’ services (Part 2)
3. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Modeling Services (Part 3) – Screencam
4. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services- Defining services (Part 4) – Screencam
5. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Leveraging a wizard to automate Service Creation (Part 5) – Screencam + Wizard
6. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing Services in Java (Part 6) – Screencam
7. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing Services in .NET (Part 7 – provided by Nakisa) – Screencam
8. SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing services in ABAP (Part 8) – Screencam
9. SAP Co-Innovation Lab Architecture Series: Custom Development delivered Custom Enterprise Services (Part 9) – Screencam (This Blog)
10. The specified item was not found. – Certification