SAP S4HANA on AWS Reviews

I have used the solution for the IT systems of a German client and for our data center. I also build sandbox servers, and then I build SAP S4HANA. So, now I am working on a POC environment, which is a PCC that is SPS 7 with HANA 2.0 SPS 05. I'm doing this tech upgrade which is a requirement of critical use for SAP S4HANA, and then multiple systems with the current patch. I'll start with SAP S4HANA installation into the POC environment and will do this backup with Commvault. Then, I will start with the database for the HANA readiness check. And I will resize my hardware with analytics browser support, and I will do this readiness check with the functionality and run the report. So I will keep a check on if the objects come, and I have to be forwarded with this functionality, how they can soon, you know, do online check, and they will do the modifications.

The documentation part on SAP S4HANA includes the technical guidance and sites where they have been given a map of transit gateway and API gateway, and you see environments over there, and if you have to check about EC2 instance sites where they have given the prerequisites before moving to AWS. So, we have to check SAP notes first before moving to SAP S4HANA. For instance, if I want to move SAP S4HANA 2022, and I want to find the conversion from EHP 7, but then I have to check for EC2, along with figuring out which is the supported environment over there for analytics, SAP S4HANA, because they have given a set of prerequisites before moving to EC2. Then we have to stick to IPs, and we have to design the solutions, and with the system going into a POC environment, with Overlay IP and configure for the SSR application part. According to that note, we have to plan for this, whether SAP is for the HANA system or if we should go with Fiori embedded solutions. Designing should be not only for SAP ECC, but you have to be thorough with the GRC component and BW of SAP since, for SAP S4HANA, we need to do a readiness check. So we have to simultaneously do two reports in one POC system. And for DRC, we have to download some add-ons, and we also have to do some maintenance, optimize the stack files, and we have to do some uploads as a standard practice. I can say that we have to check the release node first, which is the OSB part. So, SAP HANA 2.0 SPS 05 with the latest patch we can do, and it is supported on SAP HANA 8.6 and 8.7, whereas SUSE Linux Enterprise Server for SAP Applications 15 SP3 supports SAP HANA. So it depends on how we can go fast with the readiness checks, and we can deploy this solution. You have to do modifications to your POC environment first and into this, and then, again, we have to run some prerequisites check nodes related to FI, and fewer issues should come from the frontend team, and the backend will look after SAP S4HANA. So that could be with the functionality, we have to provide MM and SD to those who can do the online custom code analysis for PPE and vendor masters, and so it could be a collaboration team with a functional team that we have to be data support, then you have to fix it here. Within a week, the POC will be from my side, and it should be from the business activity, which is potentially completed within a week. All the activities from the basic side, I can complete within a week. I have done migrations that are successfully running. With the internet supply, I have it for systems like POC and marketing. But I don't have any issue until you know the way any systems will require, whether it may be Azure or maybe AWS. But I can speak for AWS because, security-wise, it's a very good feature. When it's in Azure, we have to be aware that Red Hat support is not good. So we have to go with either Windows. People might be aware of ransomware taking to Windows servers. So I will not go with that solution, but I will go with this S4HANA on Red Hat and SUSE Linux. So, the solution could be very good over there, and we can deploy it into HANA, and I know that form part is very well that we have to do some AMI integrations for that, and we can build the servers within a day. POC from my side based on my activities can be done in seven to eight days because we have to check with our transit gateway, IP, and network integration.

We can run once the POC is done since, after that, we can run the parallel without development, quality, and production. So, if our production is on the HA part, we can take downtime for that. But before that, we have to do a parallel QA because it's very easy to move it via some transportation on the sandbox. We could move it later on to development and quality and then later on to the POC, when the live production will start, after which SAP will let us do more. It all depends on which solution we are going for, and it may be public or private editions of SAP S4HANA. With the public edition, we talk to SAP's third by itself. The private edition is chosen by companies with AWS. So if we go with the SAP on BTP public cloud, it may fall under the delay side, but with AWS, it will be fine.

One of my use cases is pretty simple. This is an ERP solution, and the whole idea is to streamline my sales and distribution systems, materials management, procurement, warehousing, and production, in case I am a production company that can work on the production part. Then I have quality management, human capital management, and sales and distribution. There are many use cases specifically for this particular ERP. It's an ERP solution. To put it in one line, it is like having a solution integrated across different lines of business within my company.

Specifically, in terms of manufacturing, SAP S/4HANA is a very good solution. I have top-line solutions across different verticals. Especially for manufacturing, it offers great integration with my costing. I can know exactly how the costing works and identify any gaps in the costing area. The costing and personnel planning integration are among the strongest areas of this solution.

I have used SAP S4HANA on AWS. SAP S4HANA can be used on many hosting services, such as IBM RISE and Microsft Azure. When you're using someone else's hardware and being a tenant in it. Then those are some of the main players out there. You're going to become a business partner with who's hosting the software. You're a business partner with SAP, you've chosen to use SAP or whatever the ERP software is. Then it just comes down to, who you want to host your data on their servers. 

When the PO is issued, the cost center budget is reduced immediately to highlight the fact that the PO has been issued and liability has been incurred. The vendor received a PO electronically to fill and the liability is set up in the vendor. Encumbrance in the cost center reduces the available budget for that cost center and GL account expense for the amount of the issued PO. All of this happens in real-time with ACDOCA universal table in S/4 Hana where all data is stored in real-time on Hana DB.

AWS if hosting, would be hosting and running the server but the functionality is in the way S/4 HANA stores data in columns, now using multicore processing. It uses the ACDOCA universal table. In the past, several tables had to be reconciled to get to actual GL balances and the data itself may have been updated in DB at various intervals, five minutes, ten minutes, one hour, or overnight, but with HANA it happens immediately in real-time.

With S/4 HANA you can see a PO and that the vendor has a PO. When the AP vendor shows liability in GL, the cost center is reflecting this liability and the profit is updated. Once the Goods Receipt and invoice are received, the PO is closed and line items are cleared. Now the cost center shows the actual expense in the cost center and GL along with Profit Center. The BS AP vendor shows zero balance, the liability credit has been reversed by cash payments during disbursements and cash in bank is reduced on the balance sheet.

The HANA DB product is running both OLTP and OLAP data in one single HANA database which in the past was in two separate databases, and actually a third report too. This speeds up the process, keeps data reporting more current and reduces the amount of server space for your data. This leads to lowering the IT cost of ownership, increasing the speed of data reporting, and reflection of transactions in GL and P&L. Data is reported in Fiori tiles or apps on your device.

You can see AP balances, open POs, cost center actual expenses versus budget versus committed expenses from outstanding POs, and the Profit Center versus budget. You can see up-to-date AP vendor balances and all of the data in real-time. No reconciliation is needed to get to true data with ACDOCA universal table. In the past, prior to S/4, the FAGAFLXA table had mostly GL data in it but reconciliation had to take place with Asset Accounting, Material Ledger and Profitability Accounting in order for Cost Centers, Profit Areas and GL to get to correct balances.

Now all balances can be found in a single source of truth, the ACDOCA table, with no need for reconciling. All transactions are real-time and are available instantly, with no batch running or delayed updates. Users and stakeholders can see real-time results of key indicators on their PC or devices via Fiori reporting apps.

I am using modules like finance and sourcing for procurement with SAP S4HANA on AWS.

The reporting capability is good, providing very in-depth information. It manages complexity in various industries such as banking, manufacturing, and trading. The configurations are quite comprehensive, and the product can handle many complex scenarios.

The most valuable feature of SAP S/4HANA on AWS for our large company is the robust database management capabilities offered by AWS. With extensive data and a sizable client base, this ensures seamless operations, responsiveness, and overall reliability, addressing our enterprise-scale needs effectively.

I would like scalability to be improved in the future for faster performance.

SAP S4HANA is popular for managing operations related to workforce planning and product reporting. We also have a lot of Fiori apps that make the process easier for business users. Additionally, it's well integrated with inventory management, including stock values and material movement. It's been helpful.

Before we implemented SAP S4HANA, we had a lot of issues with inventory reconciliation and reporting errors. However, with SAP S4HANA, the process has become much faster and more efficient. For example, reading the bill of materials and component details has become much quicker due to the underlying CDFX data. We still face challenges with material locks that occur during inventory confirmations and movement.

After the implementation of ETP for S4HANA on the customer site, the customer may need support. We need to change some reports, do some enhancements to the workflow, and fix issues. Support environment, you know, technical support. I am the head of technical support and understanding and responsible for the growth of S4HANA. I also look after the tool's integration.

The most valuable feature of the solution is that it is one of the most professional and integrated software ever. The tool covers many modules, like production, planning, management, and finance. It is a very scalable tool that can be beneficial for any company.

We use this product to run our business on the cloud. Specifically, we are using the SAP product called S4HANA. We are in the cable industry, so our entire business runs on S4HANA using the APM modules, along with finances.

Firstly, it's very flexible and has interfaces that are interconnected with all the departments and modules, such as sales and distribution, warehouse management, finance, etc. It's an enterprise solution that eliminates the need to work separately for each module or department. Secondly, it promotes a paperless environment when you work with the Fiori app and workbook. You don't need a person physically moving around with papers. And thirdly, there is seamless integration between all the departments, making tasks like customer payments follow-up and vendor print follow-up much easier and less troublesome for the business. The internal integration within departments and integration with third parties is simplified in the system.