Skip to Content

How To Adopt A Hybrid Cloud Scenario With SAP ECC System and SAP Cloud Platform

In accounting departments around the world, there exists a demand for faster deployment of updates and upgrades. SAP taps into this demand by the creation of their Hybrid Cloud systems which allow for apps to be developed and deployed quickly. Because of the nature of accounting, a small change could potentially affect a wide range of results and with this understanding, accountants have traditionally been wary about fiddling around with their systems, or even allowing others to do so. As such, the update window for an accounting system is usually small, which brings us back to SAP’s Hybrid Cloud solutions. The solution we’re about to describe is useful in a number of different scenarios, but it only provides Accounts Receivable processing and is unsuited to companies that need to use Contract Accounting for their ledgers. That said, we can start exploring the steps in developing for the hybrid cloud.

STEP 1 – Preparation for Installation

The first thing we’re going to need to do is set up a secure connection that bridges the SAP ECC environment with the SAP Cloud Platform. For each SAP ECC we intend to connect to the system, we’re going to have to use the Add Resources function located under the Limiting the Accessible Resources for RFC header. We’re going to use EBPP_BD as the name of the function and select Prefix to define the naming policy. The next step is to locate the SAP notes that refer to your particular SAP install that deal with the creation of Data Dictionaries and fix minor issues with products. There should be four of these notes, but since they vary by version type, including the numbers here would be of no benefit. To end this section, we’re going to create a technical user (with requisite username and password) in order to develop a link to the ECC system. The built-in role SAP_FI_FSCM_CUSTOMER_PAYMENT should already exist in our system after the latest update, and can be used as a template to adapt the system to our needs.

STEP 2 – Customizing the Back End

There are a handful of options that can be added in order to increase the functionality of the system overall. These include:

  • Partial payment setup: This offers clients the option to pay bills in parts, and splits the bill into a paid portion and non-paid portion which can then be referenced as an outstanding balance.
  • Payment method customization: Automatic systems and direct debit payments can be supported with the proper setup. Additionally, early payment can add an automatic discount to payments made before the due date.
  • The ‘Send to AR Clerk’ option: The system offers information to directly liaise with the AR clerk dealing with the processing of the payments in the event of difficulties or questions.
  • Payment advice instructions: There should already exist a generic client 000 than can be used as a template for customizing the payment advice information. The payment type 09 should exist on the ECC system prior to doing this.
  • Downloading bills: The customer payment app allows for the display of both billing documentation as well as FI-AR invoices which can be saved and viewed at the client’s leisure.

STEP 3 – User Creation Specifics and Setting up the Cloud Platform

We first need to configure the SAP system. In Step 1 we set up the technical user SAP_FI_FSCM_CUSTOMER_PAYMENT and we’re going to use this to wire up the app to our SAP system. In-app configuration is available through the provided Configure Customer Payments app in SAP Fiori. Checking the administrator guide can help to guide what setting you should be adjusting to better adapt your payment model to the app processing particulars.

STEP 4 – Customer Data Records

While SAP uses the company code and customer number to determine the details of a particular customer, that type of referencing is archaic and tedious from an accounting perspective. As a result, the app uses email addresses in order to reference customers of an online adult toy store like Beyourlover masturbator cup, as well as a useful link to send updates to said clients. The first and last names of AP clerks that are likely to be dealing with files along with their contact information should also be updated and kept current, as they form part of the system.

STEP 5 – Managing Users and Accessibility

The users have been separated into an administrator user group and an end-user group, with each group having access to the system based on their needs. The Administrator Guide covers how to set these groups up in more detail. Following this, we will develop a trust mapping between the SAP S/4HANA Cloud Platform and the Cloud Identity Service to tie email addresses, as well as first and last names to user information. We will then generate a CSV file to incorporate web users into our SAP ECC customers, using their email addresses to link them to their user accounts within SAP.

STEP 6 – Testing the System

Using a set of reliable test data, we can run the system through its paces to ensure that all connections are working properly and we can access the data we need to through our app. The data set need not be hundreds of user accounts – for the purposes of testing we only need a few client accounts to verify the processing of data works properly. If an error arises, we may need to revisit one of the previously mentioned steps to correct it.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.