Skip to Content
Technical Articles
Author's profile photo PVSB Prasad K

Vehicle-as-a-Service(V-a-a-S) –Driving Digital Transformation with SAP

The electric car is a symbol of our progress towards a more sustainable and efficient future.” – Elon Musk

We have illustrated One Office Theme-Front Office to Back Office using SAP Build App(SAP BTP),Subscription Life Cycle Mgt(Subscription Billing),Billing(S/4HANA Cloud) and SAP Service Cloud for Tickets.

In the bustling city of Tomorrowville, a visionary startup called “DriveEase” redefined transportation by offering “Vehicle as a Service” (VaaS). No more car ownership hassles. Through an intuitive app, users access an array of vehicles: electric cars, sleek hybrids, or even electric bikes. DriveEase prioritizes sustainability, reducing emissions and traffic congestion, while providing seamless mobility. As word spread, the city’s streets transformed, and traditional car ownership declined. DriveEase became an inspiring example of innovation, demonstrating that a shared, eco-friendly, and convenient approach to transportation could lead to a brighter, greener future.

Key Capabilities

  • Easily integrate with SAP Subscription Billing (runs on SAP BTP)
  • Easily integrate with SAP S/4 HANA Cloud for Contract Accounting and Invoicing
  • Easily integrate with S4 via SAP Build Apps

Prerequisites:

  • SAP BTP (SAP Build Apps )
  •  SAP Subscription Billing
  •  SAP Service Cloud
  •  S/4HANA Cloud for Billing
  •  SAP Service Cloud

Architecture:

Step by Step Process:

Step 1: Using build Apps, create as many pages as you need for your scenario.

Step 2: Show casing few pages for you refence.

  • Create launch page.

  • Showing casing list of all EV cars

  • Subscription page

Step 3: Generate the necessary pages for the story.

Step 4:Story flow

  • Account Verification: In landing page -> Select Subscription button -> followed by list of EV vehicles -> followed by mobile verification

  • Subscription Creation: select the relevant fields and click on Subscribe -> it will create Subscription document in backend.

The information mentioned above is updated to the subscription billing document.

  • Pay As You Use: is a payment model in cloud computing those charges based on resource usage.

The information mentioned above is updated to the subscription billing document.

 

  • Renewal:  the car for an extended period, for example more than a month, your electric vehicle battery will be fine to leave unplugged.

The information mentioned above is updated to the subscription billing document.

  • Cancel: the car for an extended period will be cancelled.

The information mentioned above is updated to the subscription billing document.

  • Customer Support: Customer support is the team of people who provide help when customers have trouble with a company’s products or services.it will create ticket in c4c ticket

The information mentioned above is updated to the subscription billing document.

 

Conclusion : We have illustrated One Office Theme-Front Office to Back Office using SAP Build App(SAP BTP).

Assigned Tags

      2 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Fidan Abbasova
      Fidan Abbasova

      Hi Prasad,

      Very interesting and informative solution build up proposal!

      Great work, keep it up!

      Interesting to see new ideas and initiatives like this.

       

      Couple of questions:

      • How do you think to manage invoicing per customer? Will customer verification (with customer data) be replicated in SAP Cloud for Billing or Contract Accounting in this case?
      • Interesting to know your ideas for Revenue Recognition. What will be the high level architecture on recognizing the revenue?
      • Resource Usage (charging stations, for instance) - do you plan to receive the usage data from charging stations separately and how to do you plan to do verification/reconciliation of usage data?

      Thanks.

      BR

      Fidan.

      Author's profile photo PVSB Prasad K
      PVSB Prasad K
      Blog Post Author

      HI Fabin,

      • How do you think to manage invoicing per customer? Will customer verification (with customer data) be replicated in SAP Cloud for Billing or Contract Accounting in this case?

      Yes, the customer data will be replicated back. The source of customer bill would be from Subscription Billing in the frontend system. Yes, when bills would be due for billing or status is closed then it will get transfer to S/4HANA Cloud for convergent invoicing. This will also be reflected back in Subscription Billing.

       

      • Interesting to know your ideas for Revenue Recognition. What will be the high level architecture on recognizing the revenue?

      The RR would be standard as we have in S/4HANA Cloud or OP.

      • Resource Usage (charging stations, for instance) - do you plan to receive the usage data from charging stations separately and how to do you plan to do verification/reconciliation of usage data.

      The usage data will be replicated from Charging Station for particular SB document. The customer will be appraise the usage made as well. We can have reconciliation in SB as will track usage posted again individual SB document.

      Regards,

      Prasad