C_S4CPR_2408 Extensibility and Integration

Extensibility and Integration Detailed Explanation

SAP S/4HANA Cloud is designed to provide flexibility and scalability for businesses while maintaining a standard, stable core system. The extensibility and integration options allow businesses to tailor the solution to meet specific needs and connect SAP S/4HANA Cloud with other systems seamlessly.

6.1 Extensibility Options

Extensibility in SAP S/4HANA Cloud refers to the ability to enhance or customize the system to fit specific business requirements. It is categorized into two main types:

1. In-App Extensibility – Customizations made within SAP S/4HANA Cloud using tools that do not require technical coding skills.
2. Side-by-Side Extensibility – Extensions developed outside SAP S/4HANA Cloud on the SAP Business Technology Platform (SAP BTP).

6.1.1 In-App Extensibility

In-app extensibility is designed for key users (business users with administrative permissions) who need to make enhancements directly in SAP S/4HANA Cloud. These enhancements are low-complexity and preserved during quarterly updates.

Key Tools and Features

1. Custom Fields and Logic:

   • What It Is:

     • Add custom fields to existing business objects, such as Purchase Orders, Suppliers, or Invoices.
     • Define custom logic to influence calculations or workflows.

   • How to Use It:

     • Go to the “Custom Fields and Logic” app in SAP Fiori.
     • Select the relevant business object (e.g., Purchase Order).
     • Add the required field (e.g., “Urgency Level” for PRs).
     • Publish the custom field so it appears in relevant Fiori apps, reports, and APIs.

   • Example:

     • A company wants to add a “Delivery Priority” field to purchase orders.
       • Add the custom field in the Custom Fields app.
       • Integrate the field into the “Manage Purchase Orders” app.

2. Custom Business Objects:

   • What It Is:

     • Create entirely new business objects to extend functionality.
     • These objects can be linked to existing processes.

   • How to Use It:

     • Use the “Custom Business Objects” app in SAP Fiori.
     • Define the object structure: add fields, attributes, and relationships.
     • Generate a UI for the new object automatically.

   • Example:

     • A logistics company wants to manage shipping details.
       • Create a custom business object named “Shipping Information.”
       • Add fields like Carrier Name, Tracking ID, and Delivery Status.
       • Integrate it with Purchase Orders for better visibility.

3. UI Adaptation:

   • What It Is:

     • Customize the SAP Fiori user interface (UI) for specific roles.
     • Hide, rearrange, or add new fields to screens.

   • How to Use It:

     • Open any Fiori app and enter Adapt UI mode.
     • Adjust the layout by:
       • Hiding unnecessary fields.
       • Adding custom fields created earlier.
     • Save the changes for specific business roles.

   • Example:

     • For the “Manage Purchase Orders” app, hide fields like “Payment Terms” for junior buyers while showing only critical fields like “Supplier” and “Delivery Date.”

4. Custom CDS Views:

   • What It Is:

     • CDS (Core Data Services) Views allow users to create custom data views for reporting purposes.
     • Extend existing data models by adding new fields or combining multiple objects.

   • How to Use It:

     • Use the “Custom CDS Views” app in SAP Fiori.
     • Select the base CDS view (e.g., Purchase Orders).
     • Add custom fields or join related tables (e.g., Supplier and Purchase Order tables).

   • Example:

     • Create a report combining Purchase Order data and Supplier evaluation scores to analyze procurement performance.

Benefits of In-App Extensibility

1. Low Complexity:

   • Enhancements can be done without coding or advanced technical skills.

2. User-Friendly Tools:

   • Tools like Custom Fields, Custom Business Objects, and Adapt UI are accessible via SAP Fiori apps.

3. Quarterly Updates:

   • Changes are automatically preserved during SAP’s quarterly updates.
   • This ensures that custom enhancements do not disrupt the system.

4. Faster Implementation:

   • Changes can be implemented and tested quickly without lengthy development cycles.

6.1.2 Side-by-Side Extensibility

Side-by-side extensibility is used when advanced customizations or external developments are required. These are built outside SAP S/4HANA Cloud using SAP Business Technology Platform (SAP BTP).

Key Tools and Capabilities

1. SAP Extension Suite:

   • Allows developers to build and deploy new applications and logic outside the core SAP S/4HANA Cloud system.

   Examples:

   • Build custom applications for industry-specific workflows.
   • Develop advanced automation tools that integrate with SAP.

2. SAP Integration Suite:

   • Facilitates integration between SAP S/4HANA Cloud and external systems.
   • Enables real-time data exchange using APIs and pre-built connectors.

   Examples:

   • Integrate with supplier portals for RFQs.
   • Connect with third-party logistics providers to track deliveries.

3. APIs and Events:

   • SAP provides a comprehensive set of standard APIs to enable secure, real-time communication between systems.
   • Event-driven integrations allow SAP S/4HANA Cloud to trigger external actions when certain events occur.

   Examples of APIs and Events:

   • API for Purchase Orders → Retrieve PO details for supplier collaboration.
   • Event: New Purchase Order Created → Trigger a notification to the supplier’s portal.

Common Use Cases for Side-by-Side Extensibility

1. Build New Applications:

   • Develop industry-specific apps, such as a custom supplier portal or a tool to manage procurement bids.

2. Integrate with External Systems:

   • Connect SAP S/4HANA Cloud with:
     • Logistics Partners: To track shipments.
     • Tax Engines: For real-time tax calculation.

3. Develop Custom Analytics Dashboards:

   • Use SAP BTP tools to build advanced reporting dashboards that combine data from SAP S/4HANA Cloud and other systems.

Benefits of Side-by-Side Extensibility

1. Scalability:

   • Custom solutions can scale independently of the core system.

2. Separation from Core:

   • Changes are developed outside SAP S/4HANA Cloud, ensuring the core remains stable.

3. Advanced Customization:

   • Supports complex use cases that cannot be achieved with in-app tools.

4. Integration Flexibility:

   • Easily integrate with SAP and non-SAP systems.

6.2 Integration Capabilities

Integration is a key feature of SAP S/4HANA Cloud that enables seamless communication and data exchange between SAP systems, external systems, and third-party applications. SAP provides a robust framework for integrations using tools like the SAP Integration Suite, standard APIs, and event-driven architecture.

6.2.1 SAP Integration Suite

The SAP Integration Suite is a cloud-based integration platform, part of the SAP Business Technology Platform (BTP). It provides pre-built tools, connectors, and content to integrate SAP S/4HANA Cloud with other systems.

Key Features of SAP Integration Suite

1. Pre-Built Connectors:

   • SAP offers ready-made connectors for integrating with SAP systems and non-SAP systems.
   • Example systems include:
     • SAP Ariba for procurement.
     • Third-party logistics providers for shipment tracking.

2. Message-Based and File-Based Integration:

   • Message-Based Integration: Real-time communication between systems using messages (e.g., sending purchase orders to a supplier portal).
   • File-Based Integration: Batch uploads or file transfers (e.g., transferring a list of suppliers from a legacy system to SAP S/4HANA Cloud).

3. Cloud-to-On-Premise and Cloud-to-Cloud Integration:

   • Enables integration between:
     • Cloud-to-Cloud: Two cloud-based systems (e.g., SAP S/4HANA Cloud and SAP Ariba).
     • Cloud-to-On-Premise: SAP S/4HANA Cloud with on-premise ERP systems or databases.

4. Monitoring and Security:

   • Track integration processes with dashboards and error logs.
   • Ensures secure data transfer with encryption and authentication protocols.

How SAP Integration Suite Works

1. Design Integration Flows:

   • Use pre-built integration flows or design custom flows using the Integration Suite Designer.

2. Configure Connections:

   • Set up connections between SAP S/4HANA Cloud and the target system.
   • Example: Connect SAP S/4HANA Cloud to a supplier portal for automated PO transmission.

3. Deploy and Monitor:

   • Deploy the integration flows and monitor data exchange using integration logs.

Example Use Case:

• Scenario: Integrating SAP S/4HANA Cloud with a third-party logistics provider.
  • Step 1: Use a pre-built connector to link the logistics partner’s system to SAP S/4HANA Cloud.
  • Step 2: When a purchase order (PO) is created in SAP S/4HANA Cloud, the PO details are sent automatically to the logistics provider.
  • Step 3: The provider sends back shipment updates, which are updated in SAP S/4HANA Cloud.

6.2.2 APIs and SAP API Business Hub

APIs (Application Programming Interfaces) are key to enabling real-time integration and communication between systems. SAP provides a wide range of pre-configured APIs in the SAP API Business Hub.

What is the SAP API Business Hub?

The SAP API Business Hub is a central repository where SAP provides standard APIs for:

• Business objects (e.g., Purchase Orders, Supplier Master Data).
• Real-time and batch integrations.
• System-to-system communication.

Types of APIs

1. OData APIs (RESTful):

   • Designed for real-time integration.
   • Lightweight and suitable for cloud-to-cloud communication.
   • Example: Fetching live purchase order details from SAP S/4HANA Cloud.

2. SOAP APIs:

   • More complex and secure APIs for batch processes or on-premise integrations.
   • Example: Uploading large supplier master data files.

3. Event APIs:

   • Used for event-driven integration (e.g., triggering workflows when a business object is created or changed).

How to Use APIs for Integration

1. Discover APIs:

   • Go to the SAP API Business Hub and search for APIs related to your business needs.

2. Access APIs:

   • Download the API documentation to understand the fields and integration process.

3. Connect Systems:

   • Use APIs to connect external systems to SAP S/4HANA Cloud.

4. Test and Monitor:

   • Test the APIs in the API Hub Sandbox to ensure they work correctly.

Example Use Case: Master Data Synchronization

• Scenario: Synchronize supplier master data between SAP S/4HANA Cloud and a legacy procurement system.
  • Step 1: Use the Supplier Master API to fetch supplier details from SAP S/4HANA Cloud.
  • Step 2: The API sends this data to the legacy system.
  • Step 3: Changes made in the legacy system (e.g., updated address) are synchronized back into SAP S/4HANA Cloud via the same API.

6.2.3 Event-Driven Architecture

An event-driven architecture enables systems to trigger actions in response to events. Instead of continuously checking for updates, the system notifies other systems when specific events occur.

How Event-Driven Integration Works

1. Trigger Events:

   • Events occur when a business process or object changes.
   • Example Events:
     • A Purchase Order (PO) is created.
     • A Supplier Invoice is approved.

2. Event Notifications:

   • The system publishes an event notification.
   • Example: “New PO Created.”

3. External System Actions:

   • External systems receive the notification and act on it.
   • Example: A supplier portal receives the PO details and sends an acknowledgment.

Example Use Case: PO Creation Triggering Supplier Notification

• Scenario: Notify suppliers when a new Purchase Order (PO) is created.
  • Step 1: A PO is created in SAP S/4HANA Cloud.
  • Step 2: The system triggers an event called “New PO Created.”
  • Step 3: The event sends details to the supplier’s system using an API.
  • Step 4: The supplier’s system processes the PO and sends an order confirmation back to SAP S/4HANA Cloud.

6.2.4 Common Integration Scenarios

Here are some typical real-world integration scenarios for SAP S/4HANA Cloud:

1. Integrating SAP S/4HANA Cloud with SAP Ariba (Procurement):

   • Automates supplier collaboration for purchase requisitions, orders, and invoices.
   • SAP Integration Suite connects the two systems seamlessly.

2. Connecting External Supplier Portals:

   • Supplier systems receive RFQs (Request for Quotations) and Purchase Orders via APIs.
   • Real-time updates are exchanged between the supplier portal and SAP S/4HANA Cloud.

3. Real-Time Integration with Financial Systems:

   • Integrate with external accounting software to post financial transactions.
   • Example: Posting approved supplier invoices automatically into the finance system.

4. Logistics and Shipment Tracking:

   • Connect SAP S/4HANA Cloud with third-party logistics providers to:
     • Send shipping requests.
     • Receive real-time delivery updates.

Extensibility and Integration (Additional Content)

This section provides additional insights into SAP Extensibility, SAP Business Technology Platform (BTP), SAP Fiori App Extensibility, SAP Integration Suite, and real-world integration scenarios. These additions will help you understand how to extend and integrate SAP S/4HANA Cloud effectively.

1. SAP Extensibility – When to Use In-App vs. Side-by-Side Extensibility

SAP S/4HANA Cloud offers two extensibility options: In-App Extensibility and Side-by-Side Extensibility. Choosing the right approach is critical for ensuring scalability, maintainability, and system upgrade compatibility.

1.1 When to Use In-App Extensibility?

Best for lightweight customizations and UI changes
Requires no coding and can be done by key users
Changes stay within SAP S/4HANA Cloud core but do not modify standard business logic

Feature	Description	Example Use Case
Custom Fields & Logic	Add new fields to business objects	Adding a "Priority" field to Purchase Orders
UI Adaptation	Modify SAP Fiori screens without coding	Hiding non-relevant fields in Manage Purchase Orders
Business Rules	Configure decision logic to influence processes	Auto-approve PRs below $5,000
CDS Views for Reporting	Create custom reports by combining existing tables	Generating a custom supplier performance report

Limitations of In-App Extensibility:

• Cannot modify SAP standard business logic
• Cannot create new applications
• Limited integration capabilities

1.2 When to Use Side-by-Side Extensibility?

Best for advanced customizations, integrations, and new applications
Uses SAP BTP to build and deploy apps outside SAP S/4HANA Cloud core
Allows custom workflows, APIs, and third-party integrations

Feature	Description	Example Use Case
Custom Applications	Develop new applications independent of S/4HANA core	Supplier Portal to allow vendors to view POs
Workflow Extensions	Automate complex approvals or processes	AI-based purchase requisition approval workflow
Integration with External Systems	Use SAP Integration Suite for external API connections	Connect SAP S/4HANA Cloud with a third-party logistics system
SAP AI & Analytics	Leverage AI/ML models for predictive analytics	AI-based forecasting for demand planning

Advantage of Side-by-Side Extensibility:

• Keeps S/4HANA core clean and upgrade-safe
• Highly scalable and flexible for advanced use cases
• Supports modern cloud-native development (SAP BTP)

1.3 Comparison: In-App vs. Side-by-Side Extensibility

Comparison	In-App Extensibility	Side-by-Side Extensibility
Modification Scope	UI changes, field additions	New applications, external system integration
Customization Level	Limited to SAP pre-built capabilities	Fully customizable using SAP BTP
Impact on Upgrades	Upgrade-safe	Upgrade-safe (separate from S/4HANA core)
Use Case Examples	Add custom fields, minor UI changes	Build AI-powered supplier portal, custom workflow approvals

Exam Tip: Expect questions that ask when to use In-App vs. Side-by-Side Extensibility. Be prepared to recognize real-world scenarios where each applies.

2. SAP Business Technology Platform (BTP) – The Foundation for Side-by-Side Extensibility

SAP BTP provides the technical foundation for Side-by-Side Extensibility by offering tools for application development, integration, and AI capabilities.

2.1 Key Components of SAP BTP

Component	Purpose	Example
SAP Extension Suite	Develop custom applications outside S/4HANA Cloud	Build a Supplier Portal with real-time data access
SAP Integration Suite	Enable seamless system-to-system connectivity	Connect SAP S/4HANA Cloud with a third-party logistics system
SAP AI & Analytics	Apply machine learning and predictive analytics	Predict supplier lead times based on historical data

2.2 SAP BTP and SAP S/4HANA Cloud – How They Work Together

• SAP BTP applications run separately from S/4HANA Cloud, ensuring that SAP upgrades do not impact custom apps.
• SAP BTP supports multi-cloud deployments on AWS, Azure, and Google Cloud.
• Real-world use case: AI-driven contract analytics app that analyzes purchase order patterns and supplier performance.

Exam Tip: Be familiar with SAP BTP capabilities and how it enables Side-by-Side Extensibility.

3. SAP Fiori App Extensibility

SAP Fiori apps can be extended using three primary methods:

Methods to Extend SAP Fiori Apps

Extensibility Method	Purpose	Example Use Case
UI Adaptation	Modify the UI without coding	Rearranging fields in "Manage Purchase Orders"
Fiori Elements Extension	Extend existing SAP templates	Adding a supplier rating field in a purchase order app
SAP UI5 Custom Development	Build new SAP Fiori apps from scratch	Creating a vendor portal for supplier onboarding

Exam Tip: Be ready to identify which method is best for extending a Fiori app.

4. SAP Integration Suite – Connecting SAP S/4HANA Cloud with External Systems

SAP Integration Suite provides pre-built connectors, APIs, and workflow automation for seamless integration.

4.1 Key Features of SAP Integration Suite

Feature	Description	Example
Integration Flow Designer	Drag-and-drop interface to design integration flows	Connecting SAP S/4HANA Cloud with a third-party tax engine
Pre-Built APIs	Ready-to-use SAP S/4HANA Cloud APIs available in SAP API Business Hub	Real-time synchronization of supplier invoices
Security & Authentication	OAuth, SAML, and API Key authentication	Secure API access for external finance systems

4.2 API Communication in SAP S/4HANA Cloud

API Type	Purpose	Example Use Case
OData API	Real-time read/write operations	Fetching open purchase orders
SOAP API	Batch processing for large transactions	Uploading supplier master data
REST API	Lightweight data exchange	Sending invoice approvals to an external finance system

Exam Tip: Expect questions about OData vs. SOAP APIs and how they connect SAP with third-party applications.

5. Real-World SAP S/4HANA Cloud Integration Scenarios

SAP S/4HANA Cloud is commonly integrated with external systems for procurement, finance, and logistics.

5.1 Procurement Integration

Scenario	Integration Example
SAP S/4HANA Cloud ↔ SAP Ariba	Automate purchase requisitions and supplier contracts
SAP S/4HANA Cloud ↔ Supplier Portal	Allow vendors to view and accept purchase orders

5.2 Finance Integration

Scenario	Integration Example
SAP S/4HANA Cloud ↔ External Tax System	Automate tax calculations in supplier invoices
SAP S/4HANA Cloud ↔ Banking System	Automate payment processing and bank reconciliations

5.3 Logistics Integration

Scenario	Integration Example
SAP S/4HANA Cloud ↔ Third-Party Logistics (DHL, FedEx)	Track real-time shipments and delivery status

Exam Tip: Be prepared for scenario-based questions on how SAP S/4HANA Cloud integrates with external procurement, finance, and logistics systems.

Conclusion

This supplementary knowledge enhances SAP Extensibility and Integration understanding by covering: When to use In-App vs. Side-by-Side Extensibility
SAP BTP and how it powers SAP S/4HANA Cloud extensions
How to extend SAP Fiori Apps
SAP Integration Suite and real-world SAP integration scenarios