Skip to Content
|

Category Archives: Uncategorized

For 6 weeks I struggled getting BOE 4.2 SP05 installed fresh on a newly created Windows 2016 virtual server. I finally figured out the issue. I thought it might be helpful to relate my experience.

The issue presented itself whenever I would choose my previously prepared 64-bit ODBC datasource (based on SQL Server 2014).

I would get the following error…

“The system cannot verify the database logon information.”

Despite that error the CMS_InfoObjects7 table would get created. If I would immediately hit “Next” again another table would get created, I would get the same error again. I tested my ODBC datasource and it was able to connect successfully.

The mystifying part was I had run this same install on another server (idenitical virtual servers), but against a different database and it worked just fine.

I thought if I could create the tables prior to the install perhaps it would just skip over that portion since the tables were already there. So I scripted out the tables from the other installation that worked and ran it on the SQL Server I with which I was having problems. The install made it past that stage, but finished with errors.

I did open an incident with SAP in working with a support engineer we confirmed the issue was with SQL Server because we were able to get the install to work using SQL Anywhere as the database.

After some time away from the issue due to other tasks I had the virtual server recreated and tried again. I got the same result.

In talking over the situation with our internal DBAs one of them mentioned maybe the database server level trigger in place to track database object changes on the server was interfering with the BusinessObjects install. As it turns out that was enabled on the problematic SQL Server, but not on the SQL Server used for the first installation that worked.

With that database server level trigger disabled I tried the install again. IT WORKED! I then applied 4.2 SP05 Patch 2 and 4.2 SP05 Patch 2 Hotfix 2 successfully. I have a lot of configuration and content migration to do, but at least I have a system that is up and running.

I hope this helps someone down the road.

Noel

Business leaders typically approach digital transformation by focusing on the variety of technologies and solutions available to them, but what truly shapes a company’s competitive advantage is rarely the technology they use. People are what make the difference. These same people use technology in just about every aspect of their lives, leveraging mobile devices, conversational interfaces, and the web to simplify and streamline how they live and communicate in an increasingly digital world. SAP SuccessFactors continues to innovate in creating tools and technology that are truly focused on the needs of your people, enabling them in the workplace the same way technology enables them at home.

 

In the Q3 release we delivered enhancements throughout the mobile platform to enable easier, more seamless connection between people and their careers.

We started by focusing on the Android experience. Android app users have historically had access to all of the robust HCM capabilities enjoyed by iOS users, but the user experience itself was not always intuitive. This quarter we delivered a completely redesigned Android app, created in collaboration with Google developers. We followed Google Material Design Guidelines to create a totally native, consumer-grade Android experience, translating powerful SAP SuccessFactors functionality into familiar Android interactions. The result is an enhanced home page and improved navigation, optimized employee profile with just-in-time actions (shown below), an updated approvals center, modernized Continuous Performance Management, dynamic and engaging learning experiences, simplified time entry, and more, all now available to Android users.

To leverage the redesigned Android app, mobile users should upgrade to the most current release, available through the Google Play store.

 

We also focused on enhancing the web experience. Utilizing the SAP Fiori interface, SAP SuccessFactors is already designed to be intuitive, fast, and easy. But HR leaders continue to invest time and money enabling people on how to use the solution—time they could be spending on more impactful things. In our continued efforts to create a solution that truly needs no enablement, this quarter we delivered an integration with SAP Enable Now that allows customers to embed standard in-app guidance and help throughout the SAP SuccessFactors solution. This content can be accessed seamlessly within the solution, providing context-sensitive, automated support to users struggling to figure out how best to execute actions in the system (e.g., completing a goal plan).

 

 

Finally, this quarter we launched the beta program for our digital assistant functionality, accessible across web, mobile, and third-party channels. Built on SAP’s intelligent bot framework CoPilot, the digital assistant is an intelligent, conversational interface enabling direct interaction with the SAP SuccessFactors solution. Employees and managers can utilize the digital assistant interface to streamline onboarding, simplify time entry, and facilitate continuous dialogue and performance management, creating a workplace technology experience just as engaging and empowering as the one people have at home.

 

A strategy focused solely on technology is an incomplete way of looking at digital transformation. True digital transformation is not about taking advantage of the newest, hottest tools on the market, but rather about your people—how technology can be applied toward enabling them to do their best work. SAP SuccessFactors continues to innovate in developing tools that connect your people to their careers, to HR, and to one another, delivering consumer-grade experiences that help them get the job done.

 

Check out other new features across our HCM suite

Learn about other new features and enhancements across the full SAP SuccessFactors HCM Suite by reading our Q3 2018 Release Highlights document and Q3 release highlights blog.

Did you know SAP SuccessFactors has been named a Leader in the 2018 IDC MarketScape Assessments for Integrated Talent Management, Performance, Learning and Compensation? To access the reports, click here. And to learn more about the exciting innovations coming to the SAP SuccessFactors HCM Suite, join us at SuccessConnect in Las Vegas taking place September 11-13 at the ARIA Resort & Casino.

 

Code optimization is something all of us programmers learn before we even get past our first year in any programming course of study. It’s the meat of the matter, the bones of the animal, the long and short of our lives as code-monkeys. However, among the first things we learn in those courses is that there is no one way to do something. There’s always more than one way to skin a cat. Despite this, optimized code is a very elusive target and as much as you could optimize code to a certain point, there’s no way you could make it completely perfect. Here are a few ways you can try to make your ABAP code more responsive and cut down on the amount of stress you cause to your clients’ devices and their connected databases.

Get Rid of your Unused Code Snippets

Just like anything that’s fluid, if too much gunk starts gathering in a particular area, it’s going to clog up the pipes. The same can be said for custom ABAP code that just isn’t used. Instead of just leaving that code to get into trouble or to cause you undue trouble, you should consider getting rid of it. I know us programmers sometimes see code as something we made and have an irrational attachment to certain snippets. But trust me on this, getting rid of that useless code can enable your system to be far more efficient.

Database Calls should be Precise

Everyone who works in ABAP has done “SELECT *” calls as part of their custom code. It’s one of the most-used bits of code for coders like us, and it’s something all of us tend to have in common. We love how efficient it is at querying the database for information. But is it really that efficient? “SELECT *” tends to be shorter to write, but looking at what’s going on under the hood, maybe it might be more efficient from a data perspective to manually select individual columns containing the data we want? Not only is it inefficient data handling to just broadly select columns, but as data is expanded and we get new columns tacked on to the end of the database you start drawing even more unnecessary information out of the database, bogging it down with your numerous “SELECT *” calls and making your resulting code unreadable. Before you write that “SELECT *” snippet, please, think of the future of your code and the poor guys who have to be working on it when you’re not around.

Include Code Inspection into your Governance Models

Inefficient code doesn’t affect the daily running of a system all that much. Because of this obvious flaw, we tend to let inefficient code slide past because it’s not really harming anyone, right? Wrong. Code inefficiency adds up over time and this leads to a slower execution and overly long processing times for clients. Incorporating regular code checks to remove inefficient snippets will do a lot over the long term, even though chances are you won’t appreciate it unless you left that inefficient code in there and have to wonder later down the line why your code’s taking such a long time to execute. Don’t let past you lead to suffering for future you. Inspect your code for efficiency when you can.

Don’t be Afraid of Code Rewrites for Non-Critical Helpers

The thing with ABAP coding is that what might seem like a great workaround or patch today will have someone coming in later down the line five or even just two years later looking at that code and saying, “You know, we could have done this a lot better by using new tools…” Rewriting non-critical code sections in order to take advantage of new technology and development in the ABAP language makes for a good paradigm to keep code efficient. Upgrades to the language can be used to make workarounds more efficient. What would have needed twenty lines of code a few years ago might only need a couple lines today, utilizing new methods. The long-term benefits of this sort of optimization is something you can definitely feel.

Reusable Code doesn’t mean Cloning

Calling methods and libraries allows us to access functions that have been designed with the intention of being “plug-and-play”. We call them, pass them parameters and we get results. However, when we copy code from somewhere else as opposed to calling it, we introduce cloned statements. These can lead to slowdowns over time, especially if there are code snippets that are copies of copies lying around on the system after the involvement of a business plan writer. Best practice would indicate that we should find and terminate these snippets anywhere we can to ensure that our processing power isn’t being abused.

Keep Efficiency in Mind While Coding

There’s no way to code something perfectly from the first pass. There are always changes to be done to code, bugs to be worked out and sometimes your code just doesn’t work the way you want it to. That’s fine, it’s all part of being a programmer. However, when you’re doing that debugging or inspecting an old code snippet for an idea of how it works, you should keep in mind how these small changes can affect your system’s overall performance. Sometimes, all it needs is a little cleaning for your code to stop working like a jalopy and start working like a finely-tuned race car.

In the usual developmental cycle, companies usually have their programmers work on web apps before moving onto a mobile-based platform. It’s a lot simpler to debug a web application than it is to debug a mobile application partially because of the difficulty in debugging tools available to the developer. Luckily, Apple has managed to make life easy for us devs by allowing us to do debugging on iOS devices from a Safari browser and it’s this method of debugging that we will look at today. Fiori Client apps are how we develop Fiori apps for mobile but the Fiori Client architecture is unique in how it runs. The Fiori Client is a Cordova-based hybrid app, which means that it’s built partially off of Cordova, which allows for the adaption of code to multiple platforms. Generating a *.IPA file (or an equivalent *.apk file for Android platforms) is a simple process. Browser-based testing for the purpose of ensuring the app is working on a connected physical device can allow for a lot more insight than a mobile can offer a developer in and of itself, short of including debug code that needs to be cleaned up after debugging has completed. Let’s see how we can use a browser to debug a Fiori Client app on iOS, through the Safari browser.

STEP 1 – Launching the Application

Tap the correct application icon and load it up. Login to the system with the correct username and password in order to connect the app to the Fiori system.

STEP 2 – Connect the iPhone to a desktop or laptop running the Safari browser.

We can check the connected devices on Safari by using the Develop menu. The device should be visible in the main menu selections there labeled with the device’s name. If the device isn’t showing up, then we may have to enable developer mode on the device itself. This is a straightforward operation on iOS 10. We’ve already connected our device previously to our laptop or desktop, so all we need to do is open the iPhone settings application on the mobile device itself. There should be an option labeled Developer that you can activate to allow the mobile device to enter developer mode. If we can’t find the Develop menu option on our Safari install, we may need to activate that as well. This option can be found under the Advanced tab in the Safari settings. there should be a checkbox labeled “Show Develop menu in menu bar“. Once we’ve gotten all those kinks worked out, we’re ready to forge forward.

STEP 3 – Opening the Web Inspector Tools

Under the Develop menu, if we move to the mobile device name, we have the option to open the Web Inspector to get a feel for the connected device’s running apps. That’s exactly what we want to use to get a true approximation for what’s going on under the hood for our app. Once we select the app in question, the Web Inspector will populate fields showing the device’s name, application’s name and the URL that is undergoing inspection. We will refresh the app and that should allow Web Inspector to make note of all the calls being made by that particular app.

STEP 4 – Loading the App under Normal Circumstances

In order to see what could possible go wrong, we’ll have to simulate the app’s behavior under normal circumstances. For this, we simply load the app again. Web inspector allows us to view the existing custom JavaScript files that exist in the resources tab along the top of the window. We can further filter these files to narrow down the ones to the names of the files we’re interested in. We can attach a custom break point to our file then hit the reload button to reload the app and take note of how the app behaves.

Advanced Analysis and Debugging Tools

Safari offers a unique insight to app developers allowing them to take a look at how their code interacts with the internet through the Web Inspector. This can aid us in figuring out exactly where our custom JavaScript code may be misbehaving and allow us to debug without including massive amounts of extraneous code under the hood. This, in turn, allows programmers to make code more efficient and less heavily typed. The result is faster development and prototyping and a much easier method of dealing with possible app-breaking scenarios quickly and efficiently.

I’m pretty sure every longtime Internet surfer has had a craving, at least once, to find out who the author of a particular website is. A likely motivation is to expose someone who ripped off a “friend of yours” online or track down a black PR crew that’s slandering a company – in fact, there can be lots of different scenarios.

The desire to find those people and perhaps hand them over to law enforcement is perfectly understandable, but there is one nontrivial snag – how do you actually hunt down the villains? The “Contact us” page on most of scam sites usually provides nothing but fake details.

Of course, this objective is a piece of cake for certain authorities that have unrestricted access to special forensic resources, but unlike you, they won’t bother doing it to help a “friend of yours” sort out their problem. This is both your weakness and your power at the same time. With a strong desire and plenty of time on your hands, you may be able to do a lot of interesting things and get some impressive results.

I will make hardly any references to specific services in this article. They are easy to find if you know what to look for, and they can turn out to be more effective than you could ever imagine.

  1. Human error can leave some breadcrumbs behind

This one boils down to a simple speculation: the shenanigans were done by a person or a group of culprits, and people make mistakes. Well, there are high-profile cybercriminals out there, but this isn’t always the case. A “friend of yours” may have been targeted by professionals, meaning that those people have a background of doing similar things for a reward. If you are persistent and meticulous enough and if you get a little bit lucky, you’ll find the traces of their past activities along with new mistakes they made.

  1. Obvious things are sometimes not as obvious and important and small details

First of all, you need to scrutinize the contents of the website. Have a look at what they write, who they write about, whom they endorse and whom they criticize, who they make references to or advertise, and whether there is any private information. All the different how’s, where’s, and why’s, along with the language and vocabulary used, will give you some important clues regarding the authors’ skills, motives, and customers who pay them for what they do.

If you are a linguist – good for you. If you aren’t, it’s no big deal. A bit of ordinary logic and attention to detail can suffice for effective de-anonymization. The author’s style, punctuation, narration, text structure, and favorite words can speak volumes about them. Additionally, if you manage to spot some unique patterns and look them up in search engines, you can obtain way more data.

Keep in mind that penmanship isn’t reflected in text only – it can also be discerned in “technical” elements of the website, including the footers and specific hyperlinks.

It can be extremely effective to analyze source code fragments. Unfortunately, major services like Google don’t allow for source code based search. However, there are alternative search engines, but they are gradually fading away and don’t feature nearly as complete indexing as regular search providers. By the way, be sure to run a Google search for “site:domain name”.

  1. The universal truths

Even elementary school students know what an IP address, domain name and the “whois” service are, therefore identifying website authors should be a more creative process than that.

Yet, given a domain name, you have to check the following:

  • IP address of the site
  • Domains registered with this IP address
  • Registrant details (first and last name, company name, email, phone number)
  • Other websites with the same registrant data
  • Other resources used by the DNS servers
  • Mail exchange (MX) details. Furthermore, not everyone uses VPN services. Some people may forget to enable VPN and give away their actual IP address when responding to emails
  • Verify the information via search engines and social networks

When analyzing the list of websites using the same IP/DNS, look for similar ones by name, niche, theme, and design. Admins often use the same hosting service for different websites – perhaps out of laziness or in pursuit of saving money – thus making it easier for you to find other resources made by the same webmaster. If the creators realize the risk, though, then your odds are pretty scarce.

Speaking of IP obfuscation through anti-DDoS services and identity concealment via “Private Person” attribute, that’s actually a problem. You may still be able to get around it using Google and the Codeby service.

There is a fairly broad choice of applicable resources. These include official free services and search engines, open-source data integration tools, and paid services that cost a pretty penny to use.

  1. History, sir, will tell lies, as usual

If you are dealing with an old resource, a “whois” history lookup can help you a lot. At the dawn of the World Wide Web, as we know it, would-be criminals used to register domains with their real identity information. Therefore, some services – paid ones or not – will output the owner’s entire background, including their actual mobile numbers and email addresses.

However, keep in mind that the site might have been sold, handed over, or re-registered. If so, you may chase down the wrong guy. In other words, once you obtain the person’s details, be sure to double-check whether they could have possibly caused trouble to a “friend of yours”.

One of the latest trends gaining momentum in the western world is the new data protection regulation known as GDPR. It tangles information retrieval about an individual significantly.

Of course, you shouldn’t underestimate website history when performing your reconnaissance. Archives and cached versions of the site might work wonders.

  1. The only thing people need from each other is confirmation of love rather than love itself

Let’s suppose you have found some other suspicious site, but how can you verify that it was made by the author you’re looking for?

Coining numerous absolutely different websites is what only well-paid paranoids do. Therefore, it won’t hurt to check the original and every supposedly related site for the CMS, plugins, modules, fonts, themes, design styles, and pictures used. This isn’t the ultimate source of information, but the totality of matches should help you gauge the credibility of your hypothesis.

  1. Poverty is not a vice

It isn’t indeed, but when combined with stupidity and greed, it becomes a major cause for screw-ups. For instance, some people don’t bother purchasing a new SSL certificate for their website. In that case, a few mouse clicks in the browser will reveal a bevy of interesting facts.

  1. To understand recursion, you must first understand recursion

Let’s say you have spotted sites that really resemble each other by a number of properties. Now, scrutinize their contents and go back to tip 1 – keep on looking for mistakes and giveaways. At the end of the day, you will collect a data set that will allow you to de-anonymize the scoundrels. That’s a whole different story, though.

Finally, don’t forget that the offenders are likely to have done the same misdemeanor to someone else before. Chances are that a predecessor of a “friend of yours” has already unearthed their identities, punished them and posted the results online. In this scenario, all you need to do is find that readily available data.

Olá pessoal,

Nossas equipes de desenvolvimento, suporte e produto perceberam que há execuções de pagamentos de empregados por meio do princípio de caixa. Se sua empresa se enquadra neste cenário, não perca: desenvolvemos as funcionalidades que permitem o uso do princípio de caixa para cálculos retroativos nos eventos S-1200 Remuneração de trabalhador vinculado ao Regime Geral de Previd. Social e S-1210 Pagamentos de rendimentos do trabalho.

Destacamos que, segundo a legislação brasileira, o princípio de origem deve ser usado para o cálculo de FGTS e INSS, e o princípio de caixa deve ser usado só para o cálculo do IRRF. Além disso, a legislação indica que todos os pagamentos realizados fora da competência estão sujeitos a penalidades; portanto, o princípio de origem deve ser usado. Tendo isso em mente, recomendamos muita atenção na decisão de usar o princípio de caixa para todas as contribuições de sua empresa!

Se quiser ler mais detalhes das funcionalidades, acesse as SAP Notes 2673685 e 2678217.

Gostou desse post? Dê um Like e compartilhe o conteúdo com seus colegas.

Fique à vontade para deixar um feedback, comentário ou pergunta no espaço abaixo. E não esqueça de seguir a tag HCM Payroll Brazil na SAP Community para ficar ligado nas últimas notícias sobre o eSocial.

Um abraço,

Alice

—-

Hi everyone,

Our development, support, and product teams have realized that there are employee payments calculated via the inflow principle. If this is the scenario on your company, check this out: we have developed a functionality that allows you to use the inflow principle for retroactive accounting in events S-1200 Employee remuneration from Social Security General Regime and S-1210 Labor income payments.

We highlight that, according to Brazilian law the principle of origin should be used for the calculation of FGTS and INSS, and the inflow principle should be used for IRRF calculation only. In addition, the law indicates that all payments made outside the competence are subject to penalties; therefore, the principle of origin must be used. Having this in mind, we recommend that you make a careful decision on whether or not to use the inflow principle for all your company’s contribution!

If you want to read more information about the functionality, access SAP Notes 2673685 and 2678217.

Did you enjoy this post? Choose “Like” and share the content with your colleagues.

Feel free to leave your feedback, comment or question in the space provided below. And don’t forget to follow the tag HCM Payroll Brazil in SAP Community to stay tuned on eSocial latest news.

All the best,

Alice

SAP always has plenty of cool technology to show — and even unveil — at the SAP TechEd conferences. SAP also packs each event’s agenda with sessions and networking opportunities, so attendees can gain knowledge and make connections. And this year, we (meaning the Developer & Community Relations Team) may have a surprise or two lined up during the conferences.

Those things alone might be tempting enough reasons to go to an SAP TechEd event at the location nearest you, but all of the temptation in the world really doesn’t matter if you can’t get a ticket.

Assuming you want a ticket so you can go, that is.

Oh, you do want to go? Well, we want you to go too. We want to meet as many people as possible at these events — and we want community members to gain the benefits of SAP TechEd.

That’s why we’re planning to award prizes that can bring more people to SAP TechEd.

Let me tell you — literally — what we’re doing and why we’re doing it.

If you didn’t watch that, then you missed me announcing that we’re holding a contest to give away hundreds of show-floor passes. Specifically, the contest will grant passes to 221 individual winners, who can choose which of the three SAP TechEd events they want to attend (subject to availability).

We have 74 passes for SAP TechEd 2018 Las Vegas, 74 for SAP TechEd 2018 Barcelona, and 73 for SAP TechEd 2018 Bangalore.

Sound good? Maybe too good?

I know what you’re thinking: What’s the catch? As you might expect, there are official rules with the typical legal language, but the gist is this: To be eligible for one of the passes, you must complete a mission.

Don’t worry…it’s hardly impossible.

The mission consists of a series of tutorials covering topics such as Fiori, SAP Cloud Platform, and SAPUI5. Do the tutorials, complete the mission, and you’ll have the option of entering the official SAP TechEd 2018 lottery (one entry per person).

That’s all there is to it.

The contest ends on September 10, and anyone who completed the mission (and chose to participate in the contest) will enter a lottery. A week or so later, winners will be chosen at random, then contacted.

Winners will still need to cover travel, lodging, etc., but a show-floor pass is worth approximately $1,500. Not bad for taking tutorials that teach valuable information anyway. In fact, even if you opt not to enter the contest, I highly recommend that you take advantage of the free education from the tutorials. Win or lose, you can still get yourself a nice prize of sorts — with the information and entertainment that the tutorials provide.

So what are you waiting for? Start on those tutorials now. And who know…maybe I’ll get a chance to congratulate you in person at an SAP TechEd event!

 

It is only another 2 weeks till SAP Inside Track is back in Berlin. After last years great turnout (event pictures, recap) we are really looking forward to welcome you at the SAP DATA SPACE on September 1st.

Agenda

Doors will open at 9am for checkin, breakfast and a short welcome notice. Sessions will start at 10am with plenty of time in between for networking breaks and lunch. We plan to end the official part of sitBER at 5pm to still have some time for barbecue and drinks afterwards. Participation if free, but because SAP Inside Track is a full day event, please plan accordingly.

Here is an overview of what topics we will cover:

  • “DevOps in SAP ABAP Landscapes” – Sascha Junkert will present the latest efforts of bringing Continuous Integration concepts into on premise ABAP development practices.
  • “Tuning ABAP with Hardware mechanics” – Dmitrii Pescov will show you how hardware mechanics influence ABAP performance and how to use them to your advantage
  • Handling security bugs with responsible disclosure and bug bounty programs – Tim Philipp Schäfers & Sebastian Neef will give an insight into the research work of their project “Internetwache.org”
  • Ledgers – how do you even…? – Ricardo J. Méndez will share his opinion about useful applications of Blockchain and where it should be avoided
  • Design Thinking, leadership and creative problem solving – Anne Johnson will present applicable tools and practices that you can bring back and try out back home
  • Writing an SAP PRESS book – Morten Wittrock will share his experience of writing a technical book for SAP PRESS
  • Kubernetes and Gardener – Andrew Karpow & Dirk Marwinski will give you on overview why Kubernetes is the latest hype and how SAP’s Gardener project is contributing to managing Kubernetes clusters.

Participant Registration

Participant registration is still open but seating is restricted at the SAP DATA SPACE. Therefore we have limited the total number of registrations to 70. On the upside, breakfast, lunch, barbecue & beverages are included, and the event is free for all participants 🙂 You can find additional information on the sitBER wiki page.

Please sign up to the second installation of SAP Inside Track Berlin, and join us on September 1st.

SAP S/4HANA Cloud for Sourcing & Procurement is one of the front runners in terms of innovation. Striving for an intelligent, fully automated no-touch world, we delivered many innovations that leverage Machine Learning and Predictive Analytics.

In this blog, you can find the latest collection of innovations for SAP S/4HANA Cloud for Sourcing & Procurement. To familiarize with the latest releases, check the blogs linked below.

1805 Update

1802 Update

1711 Update

1708 Update

1705 Update

 

For more information on SAP S/4HANA Cloud, check out the following links:

Follow us via @SAP and #S4HANA, or myself via @KathHellmich and LinkedIn

 

Achieve Benefits of SaaS and Create Unique Business Value

Part 3 of a 6-part Series

The benefits of Software as a Service (SaaS) are well-known.

From the customer point of view, there are no up-front costs. Customers pay for what they need, for as long as they need it. Their financial risk is greatly minimized. With SaaS, customers can access software from every device with an Internet connection at any time. This increases mobility and independence. Software updates are automated and deployed by the SaaS provider. Customers don’t need to download and install any application patches. SaaS applications are generally compatible across multiple devices. And applications delivered in the SaaS model can be adjusted to a customer’s needs through the availability of APIs that enable integration with existing systems.

From the vendor point of view, it is much easier to predict revenues basing on regular subscription fees. SaaS vendors do not sell a software license – they simply deliver use of the software to customers on a pay-for-use basis. In SaaS model, the cloud becomes a platform for data that is accessible only to paying customers, so it reduces the risk of software pirating. In the SaaS business model, expansion to new markets is easier, and doesn’t require the use of resellers or other distribution channels. The SaaS business model works 24/7, so vendors can gain new clients at every moment of the day. And there is a marketing network affect from customers and influencers alike.

There are many ready adopters of off-the-shelf SaaS applications. But these solutions are generally plain vanilla, so a gap remains between ‘SaaS-simple’ and ‘on premise-customized’. Rapid application development can bridge that gap by offering a controllable, model-driven platform for rapidly extending SaaS applications with little coding.

SAP Market Influencer Tamara McCleary recently sat down with Mark Rogers, from SAP partner and RAD market leader Mendix, to discuss how new SaaS solutions are changing the business market for IT solutions.

To see the third of their 6-part discussion, and to learn why Mark believes, “By looking at low code application development, you have a way of filling a gap – quickly extending and modifying, but doing it in a model-driven approach – without a big pile of legacy code. And you can have very specific customized experiences for employees, customers, partners that add unique value to the business, without losing the benefits of the core SaaS system”, just click here.

Did you miss Part 1 of the Series?

Did you miss Part 2 of the Series?

Learn more about rapid application development.