In this article, you will learn how to use Spring Boot and HarperDB to create a microservice. Later on, you will also look at how to deploy the complete application on AWS Elastic Beanstalk.

You will be building an Employee Leave Management System. This application will be responsible for tracking the detailed record of employees’ leaves. You will also be implementing the functionality to add, edit, and cancel leaves.

Source de l’article sur DZONE

Article Image

Chatbots Are Here To Stay

Chatbots have been around for a long time and based on the global chatbot market size (and the expected growth), they will stick around for a long time and gain importance. In the past, they’ve rarely met customer expectations or provided much positive experience. However, over the last few years, advances in conversational AI have transformed how they can be used. Since chatbots offer a wide range of applications, in certain cases, they become responsible for collecting and protecting personal information as well. 
Consequently, they are a great attraction for hackers and malicious attacks too. The responsibility of ensuring chatbot security has become more evident after the introduction of GDPR in Europe. As statistics show that this technology will be a determining factor in our lives, security testing must also become part of our daily tasks, so that these chatbots can be used with confidence.

Security Risks, Threats, and Vulnerabilities                 

The words risk, threat, and vulnerability are often confused or used interchangeably when reading about computer security, so let’s first clarify the terminology:

  • Vulnerability refers to a weakness in your software (or hardware, or in your processes, or anything related). In other words, it’s a way hackers could find their way into and exploit your systems.
  • A threat exploits a vulnerability and can cause loss, damage, or destruction of an asset – threats exploit vulnerabilities.                
  • Risk refers to the potential for lost, damaged, or destroyed assets – threats + vulnerability = risk! 
The well-known OWASP Top 10 is a list of top security risks for a web application. Most chatbots out there are available over a public web frontend, and as such, all the OWASP security risks apply to those chatbots as well. Out of these risks, there are two especially important to defend against, as in contrast to the other risks, those two are nearly always a serious threat — XSS (Cross-Site Scripting) and SQL Injection.
In addition, for artificial intelligence-enabled chatbots, there is an increased risk for Denial of Service attacks, due to the higher amount of computing resources involved.

Vulnerability 1: XSS – Cross-Site Scripting

A typical implementation of a chatbot user interface:           


  • There is a chat window with an input box.
  • Everything the user enters in the input box is mirrored in the chat window.
  • Chatbot response is shown in the chat window.

The XSS vulnerability is in the second step — when entering text including malicious Javascript code, the XSS attack is fulfilled when the web browser is running the injected code:


Possible Attack Vector

For exploiting an XSS vulnerability the attacker has to trick the victim to send malicious input text. It can be done through one of the following ways:

It’s that time of year again when we get the Red Hat Summit 2022 call for papers!

This year seemed to be a perfect time to go all in with sessions around our architectures based on a series of talks we’ve designed to showcase the various aspects we cover. Some are vertical aligned and others are just customer domains, but all of them include extensive research into how to implement successful architectures at scale.

Source de l’article sur DZONE

Few things are more important to a web designer or developer’s chances of success than having the proper workflow. The term “workflow” applies to the set of standardized steps you or your company uses to create, test, and deploy designs or products.

Over the years, as development processes have evolved, so too have the workflows experts use to bring their ideas to life. The MVP workflow, or “Minimum Viable Product” strategy, is one of the most popular options in 2022.

Here’s what you need to know about the MVP workflow and how it differs from some of the other standard workflows developers may be used to.

What is the Designer/Developer Workflow?

As mentioned above, the designer/developer workflow is a series of steps used by experts in the web design world to achieve a creative goal. The process includes the steps taken to start a project, evolve it, and finish it. Since software is never developed without tools, the technology you’ll access throughout the development process is also considered in most workflows.

An example of a standard development workflow might look like this:

  • Scaffolding: This is the stage wherein you start your new web project, creating a git repo, downloading libraries, preparing file structures, and completing other tasks to make sure your product is ready to roll out into the world.
  • Develop: This is where you’ll spend most of your time writing code for your application or website. The development process may include various specific tools and support from other staff members.
  • Test: In this stage, you examine the functionality of your code to determine if everything works as it should. If there are errors or issues, you can go back and develop fixes to the potential problems. Your code may go through the development/test process several times before you can move to the next stage.
  • Integrate: This is when you merge the code for your part of the development process with the rest of the team. You can also integrate your code into websites and existing apps at this point. If you’re working solo, you can skip this process.
  • Optimize: You prepare all your assets for use on a production server during the optimization stage. Files are generally optimized to ensure your visitors can view your site easily or access your applications with ease.
  • Deploy: In the deployment stage, developers push code and assets up into the server and allow for changes to be viewed by the public.

What is MVP? (Minimum Viable Product)

Now you know what a developer workflow looks like, you can begin to assess the concept of the “MVP” workflow. The term “MVP” stands for Minimum Viable Product.

The idea of “Minimum Viable Product” applies to a range of industries, from education to healthcare and government entities. This term comes from lean start-up practices and focuses heavily on the value of learning and changing during the development process.

When you adapt your workflow to focus on an MVP, you’re essentially adjusting your focus to a point where you can create a stripped-back version of something new – like an app or a website. The MVP is built just with the core features (the minimum), so you can bring the idea to market and test it as quickly as possible.

For instance, if your goal were to create an attractive new website for a client, an MVP would focus on implementing the crucial initial tools, and nothing else. While you may create checkout pages, product pages, and other aspects of the site, you wouldn’t populate it with content or start experimenting with bonus widgets and apps.

So, how does this offer a better alternative to the standard workflow?

Simply put, an MVP workflow is quick, agile, and easy. The idea is you can validate key concepts with speed, fail quickly, and learn just as fast. Rather than having to build an entire app and almost start over from scratch every time you find an error, you can race through the iteration and development process.

MVP workflows are also highly appealing to start-ups and entrepreneurs hoping to validate ideas without a massive amount of upfront investment.

Examples of MVP Workflows

Still confused? The easiest way to understand how an MVP workflow works is to look at an example.

Let’s start with a conceptual example. Say you were building a voice transcription service for businesses. The desired features of this product might include the ability to download transcription, translate them into different languages, and integrate them into AI analytics tools.

However, using the MVP approach, you wouldn’t try to accomplish all of your goals with your software at once. Instead, you’d focus on something simple first – like the ability to download the transcripts. Once you confirm you can do that, you can start a new workflow for the next most important feature for the app.

One excellent example of a company with an MVP approach is Airbnb. The entrepreneurs behind this unicorn company, Joe Gebbia and Brian Chesky, didn’t have a lot of cash to build a business with at first. They had to use their own apartment to validate the idea of creating a website where people could share their available “space” in a home or apartment with the public.

To begin, Airbnb only created a very basic website, published photos of their property, and waited to see the results. After discovering people were genuinely interested in renting another person’s home, the company was able to begin experimenting with new ideas to make a site where people could list their properties for travelers.

The Pros and Cons of an MVP Workflow

There are a lot of benefits to the MVP workflow – particularly when it comes to gaining agility and developing new products quickly. However, there are downsides too.


  • With an MVP approach, you can maximize your learning opportunities and create a more innovative, successful product at speed. You get to test every step of the way.
  • You release iterations or versions of your product quickly, which means you discover problems faster, allowing you to quickly solve these issues.
  • You build on the benefits of customer fans, “evangelists” in the marketplace who are keen to help your product or service grow.
  • An MVP gives you more freedom to try out unique ideas and “risks” you might otherwise avoid with a traditional workflow.
  • Because you’re focusing on creating only the “minimum viable product,” you don’t have to spend a fortune on initially setting up your workflows.


  • Agile work with an MVP flow requires a lot of effort in collecting constant feedback from customers and releasing iterations.
  • You’ll need to dedicate yourself to releasing many small and frequent product releases on a tight schedule.
  • You might have to revise the functionality of your product or app a number of times.

Creating Your MVP Workflow

If you believe an MVP workflow might be effective for you, the first step is defining your “Minimum Viable Product.” The app, website, or product you design needs to align with your team’s strategic goals, so think about what your company is trying to achieve at this moment – before you get started. If you have limited resources, or specific purposes, like improving your reputation as a reliable company, now might not be the right time to develop a new MVP.

Ask what purpose your minimum viable product will serve and what kind of market you’re going to be targeting. You’ll need to know your target customer to help you test the quality and performance of each iteration of your MVP. Once you know what your ideal “product” is, ask yourself what the most important features will be.

You can base these decisions on things like:

  • User research
  • Competitive analysis
  • Feedback from your audience

For example, if you’re producing an AI chatbot that helps companies to sort through customer inquiries, the most important “initial feature” may be the ability to integrate that bot into existing websites and apps owned by the company.

MVP Approach Guidelines

Once you have your hierarchy of most valuable features for your minimum viable product, you can translate this into an action plan for development. Remember, although you’re focusing on the “minimum” in development, your product still needs to be “viable.” In other words, it still needs to allow your customer to achieve a specific goal.

  • Review your features: Reviewing your prioritized product requirements and the minimum level of functionality you can deliver with each of these “features.” You need to ensure you’re still providing value to your customer with anything you produce.
  • Build your solution: Build your minimum set of features for the product or service. Remember to build only what is required. You can use methodologies like the agile or waterfall method to help guide your team during this process.
  • Validate your solution: Release your offering into the market, and ensure you have tools in place to gather feedback from early adopters. Use beta programs, focus groups, and market interviews to understand how your solution works for your customers and where you can improve on your current offer.
  • Release new iterations: Based on what you learn from your target audience, release improvements to your product quickly. Use your validation strategies to collect information from your audience with each release.
  • Review again: Go back to your product requirements and desired features and start the process over again, this time focusing on the next most valuable functionality. Over time, the value of your minimum viable product will increase.

Using the MVP Workflow Approach

While the MVP workflow approach might not be the right solution for every development or design team, it can work very effectively in the right circumstances. The MVP approach doesn’t minimize the importance of understanding market problems and delivering value. Instead, the focus is on delivering quick value that gradually increases and evolves over time.

As many developers and designers know, the most useful form of product validation in most cases is real-world validation. When your customers have had an opportunity to use a product on a day-to-day basis, they can provide much more effective feedback.

Just keep in mind that committing to the MVP approach also means changing your workflow and committing to iterations – otherwise, other features may never be completed. You’ll need to be willing to work quickly and in small bursts without getting too heavily caught up in one feature or functionality.


Featured image via Pexels.


The post How to Get Started with the MVP Workflow first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

This is the first piece in a series on developing XR applications and experiences using Oracle.  Specifically, I will show applications running with the following:

  • Oracle database and cloud technologies
  • Hololens 2 (Microsoft Mixed Reality Headset)
  • MRTK (Mixed Reality Toolkit) APIs (v2.7.2)
  • Unity (v2021.1.20f) platform (leading software for creating and operating interactive, real-time 3D content)

Throughout the blog, I will reference a corresponding workshop video found at

Source de l’article sur DZONE

If you’re looking for a WordPress theme for your 2022 projects, it never hurts to see what the experts consider to be the best of the bunch. That’s not to say that experts don’t have their favorites. They often do, and we are no different.

We’ve tried, successfully, we believe, to avoid any biases we may have in compiling what we believe to be the 10 top WordPress themes going into 2022.

Working with a WordPress theme has the advantage of giving you a great starting point. It makes it much easier to create an attractive website that will charm any visitors who stop by and convince them to linger awhile.

Another advantage of using a theme can be its cost-effectiveness. Most of the popular WordPress themes are reasonably priced, they save you time, and they can save you money as well.

The main problem you’re apt to encounter is finding the right one since many of them are out there. You could spend hours and hours making comparisons among a host of candidates that appear to be reliable and easily customizable. Or you could select from among the following 10 top WordPress themes, all of which are guaranteed to give you your money’s worth and more. 

1. BeTheme – The Biggest Multipurpose WordPress Theme with 650+ Pre-Built Websites

BeTheme justifiably lays claim to being the biggest WordPress and WooCommerce theme of all for several reasons.

  • BeTheme’s 40+ core features give its users a complete tool kit to work with that includes 650+ pre-built websites and tons of design elements, aids, and options.
  • A 240,000+ customer base also contributes to making this the biggest WordPress theme of them all.

It’s not just about size, of course. Performance is all-important, and BeTheme has it in spades thanks to:

  • The Muffin Live Builder lets users edit live content visually and create, save, and restore design elements, blocks, and sections.
  • The WooCommerce Builder helps users design engaging shop and single product layouts and is packed with customer-centric features and options.
  • Full Elementor compatibility, with 30+ unique design elements and 120+ dedicated pre-built websites.
  • Assurance that every website is 100% responsive.
  • The Muffin Builder: this old standby is more intuitive than any other page builder on the market.
  • Regular Updates, plus BeTheme purchasers also receive free lifetime updates.

Click on the banner. There’s much, much more to see.

2. Total WordPress Theme

Total is aptly named because of the tools it gives its users; tools that include a premium page builder, demo and template libraries, an assortment of design and layout options, and cool navigation features.

  • The premium page builder is an extended version of the popular WPBakery frontend drag and drop page builder. Slider Revolution, another premium design aide, also comes with the package.
  • Design options include more than 500 live customizer options and 100+ customizable builder blocks, page builder block animation capabilities, custom backgrounds, and custom title backgrounds.
  • Layout options range from boxed and full-width and dynamic layouts to page and post designs and one-page site layouts.
  • Header styles, local scroll menus, and mobile menu styles contribute to website navigation capabilities.

Total is easy to set up and work with, plus it is 100% responsive. Click on the banner to find out more.

3. WoodMart

WoodMart is a premium WordPress theme that has been designed from the ground up to enable its users to create superlative WooCommerce online stores. WoodMart doesn’t require the use of multiple plugins as the most important tools, and features users simply must have come right out of the box.

They include:

  • For starters, a supply of 70+ demo layouts, 370 premade sections, plus an extensive template library for Elementor and WP Bakery.
  • A powerful Theme Settings Panel with a graphics interface to make changes quickly and easily.
  • AJAX techniques that guarantee the super-fast loading that is so important with multi-product pages and galleries.

WoodMart-built websites are search engine friendly, multilanguage ready, 100% responsive, and RTL and retina ready, and GDPR compliant.

Click on the banner to see what your WooCommerce store could look like.

4. TheGem – Creative Multi-Purpose & WooCommerce WordPress Theme

TheGem is the best-selling theme on ThemeForest, which isn’t surprising since its multiplicity of features has led to it being called the Swiss Army Knife of WordPress themes.

Key features include –

  • 400+ beautiful websites and templates for any purpose or niche.
  • TheGem Blocks with its 300+ pre-designed section templates to speed up your workflow – a genuine game-changer.
  • Elementor and WPBakery page builders.
  • An outstanding collection of WooCommerce templates for any shop type.

5. Uncode – Creative & WooCommerce WordPress Theme 

Uncode is a pixel-perfect theme packed with dozens of advanced and unique features designed to produce a pixel-perfect website.

These features include:

  • An enhanced Page Builder with a juiced-up Frontend editor
  • A WooCommerce Custom Builder
  • A wireframes plugin for importing 550+ professionally designed section templates

Uncode has sold more than 85,000 copies to date. It is the ideal WordPress theme for building an impressive blog, portfolio, eCommerce, and magazine sites.

6. Rey Theme for WooCommerce

eCommerce is said to rest on four pillars – filtering, search, navigation, and presentation. This WooCommerce-oriented WordPress theme fully addresses each one. Rey lets you experience design, innovation, and performance in ways you could only dream of before.


  • The powerful and popular Elementor page builder with built-in features supplemented with Rey’s extra spices.
  • Ajax navigation, including infinite loading.

Rey is multilanguage-ready, obviously responsive, SEO friendly, developer-friendly, and performance-oriented.

7. Avada Theme

One easy way to know you’ve picked the right theme is to select Avada, the #1 best-selling theme of all time, a popular theme that is loved by 450,000+ happy users.

  • Avada’s Fusion Theme Options, Fusion Page Options, and Fusion Builder will give you more than enough flexibility, while its 40+ free eye-candy demos provide the inspiration.
  • Avada also gives you easy access to some of the most popular premium plugins.

And that’s just the beginning.

8. Impeka – Creative Multipurpose WordPress Theme

This simply impeccable WordPress theme is filled with potential for the advanced user and, at the same time, easy for a beginner to use. Using Impeka simply involves:

  • Selecting Elementor, Gutenberg, or an enhanced WPBakery as your page builder.
  • Using WooCommerce to build your online shop.
  • Sifting through a multitude of features that include the Mega Menu and Footer and Popup builders.

Your website will be super-attractive, lightning-fast, fully responsive, and SEO perfected.

9. Litho – Multipurpose Elementor WordPress Theme

This popular multipurpose WordPress theme is built with Elementor, the world’s #1-page builder.

  • Litho can be used to build websites of any type and for any business niche.
  • It is excellent for building portfolio, blog, and eCommerce websites.
  • There are 37+ home pages, 200+ creative elements, and 300+ templates to get you started and assist you along the way.

Litho-built websites are fast loading and deliver healthy SEO results.

10. XStore – Best Premium WordPress WooCommerce Theme for eCommerce

You can start with one of XStore’s more than 110 amazing pre-built shops, or start from scratch and let Elementor or WPBakery and more than 550 pre-built blocks help you along the way, together with:

  • $559 worth of premium plugins.
  • A Live Ajax theme option.
  • A header builder and a single product page builder.
  • A built-in WooCommerce email builder.

You can get this complete and highly customizable WooCommerce theme for an amazing $39.

One of the benefits of using WordPress is the number of great WordPress themes you can work with. Whatever your niche, your target audience, or your skill level may be, there’s a premium WordPress theme out there that looks and feels as though it was made, especially with you in mind.

If you’re planning to create a fresh and beautiful website for 2022, or you want to completely rebuild an existing one, or simply make some design changes, this roundup of the most popular and the best WordPress themes in the market is meant for you. And we really mean it!


This is a sponsored post.


The post 10 Top WordPress Themes for 2022 first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

This article describes the steps to create a new KeyStore with a new self-signed SSL certificate and a new CN (Common Name) in WSO2 API-M 3.2.0 and how it can be used to invoke APIs’ in WSO2 from a remote host. By default, WSO2 API-M has a KeyStore named wso2carbon.jks which contains a self-signed certificate. However, the default certificate has Common Name (CN) as localhost and this certificate can be used to invoke the APIs from the same server where WSO2 API-M is hosted. This article is useful when the client/end-user wants to invoke APIs exposed via WSO2 gateway that is hosted on a remote server and using an SSL certificate.


1.  Open a command prompt and go to <API-M_HOME>/repository/resources/security/. Then, create the new KeyStore that includes the private key by executing the following command. We will provide the hostname/domain name where WSO2 API-M is hosted as the CN value while creating this new KeyStore. For example, in this case, it is

Source de l’article sur DZONE

Picture a dark office, blinds drawn. Picture a UX designer smoking a cigar. See the light filtered through the smoke whipped to fog by a spinning ceiling fan. Watch as the UX designer sits at a desk and considers the website.

The UX designer has devised a series of tests to determine if a green button is better than a red button. One of them involves tipping a tortoise onto its back. He looks the website over carefully and says, “Describe in single words, only the good things that come to mind about your mother.”

The website pauses, sweating under pressure, then replies, “Let me tell you about my mother…”

BLAM! The website pulls the trigger of an unseen gun, and the UX designer collapses, leaving the project to be rebuilt from scratch in Material by Harrison Ford, with overuse of Post-its delegated to Edward James Olmos.

Who Does UX Testing Actually Serve?

In the past’s bleak dystopian future (1982’s Blade Runner was set in 2019) no one benefitted from asking the wrong questions. And little has changed.

Designing any test to verify UX is fraught with as many complications as administering the test. Questions are skewed by bias, conscious or otherwise, and competing agendas. Even with something as apparently simple as a split test, the potential for distortion is immense.

When planned by a designer, a UX test offers little benefit to a client; the benefit is to the designer, who can then say their ideas are validated (or not).

Imagine hiring a developer to code a website, only to discover that the developer didn’t know CSS and expected to be paid to learn it before completing the work. You would hire someone else because that developer isn’t qualified.

From a client’s perspective, a UX designer should know, through experience, whether a green button is better than a red button. Designing an elaborate test to split-test the button color serves little purpose other than indemnifying the designer against mistakes.

The ROI of UX Testing

It’s widely accepted that there is substantial ROI (Return On Investment) from UX testing. We’ve all heard apocryphal stories about sites that split-tested their checkout and improved retention by 5%.

I’m going to go out on a limb and say that without user testing, that site could have improved its checkout retention by 4.9% simply by hiring a competent, experienced designer. But what about the remaining 0.1%? Well, for most sites, 0.1% represents very little profit. And the cost of recovering it via testing far exceeds the benefits.

When a company the size of Amazon, Netflix, Spotify, or Google split tests a website, it can afford to allocate $25k for user testing because it stands to gain 0.1%, and that represents far more than $25k. To meet the same 0.1% improvement, a small business has to design and run the same tests, incurring the same costs. But in the case of a small business, $25k could eat up all of its profits.

UX testing almost always works. But it is only profitable at scale.

If a good UI designer with a grounding in UX can improve checkout retention by 4.9%, tripling the project budget for just 0.1% more is a tough sell. Bluntly, that $25k is better spent on advertising.

What UX Designers Can Learn From Psychiatry

We all have the tendency to think we’re unique. It’s a survival trait attributed to our prehistoric brain. That belief in uniqueness is particularly strong in highly competitive people. We all think our site, our side-project, our approach are original. And we’re all wrong.

When a psychiatrist sits down with a patient, they have two immediate goals: categorize that patient into an established diagnosis, and assess the severity of the condition. It may be that the patient is depressed or anxious or even suffering from a potentially more debilitating condition like schizophrenia. What the psychiatrist is not trying to do, is define a new illness.

Occasionally — perhaps once per decade — a genuinely unusual patient will present themselves, and a new form of illness is considered. New treatments are found and tested. These treatments are rarely developed on behalf of individual patients; doctors work with grants from governments, medical schools, or the pharmaceutical industry and publish their results.

The vast majority of websites face similar problems. They deal with similar demographics, work within a similar culture, and deal with similar technology. As such, they can be categorized in the same manner a psychiatrist categorizes patients.

The key to delivering successful UX solutions is not UX testing in individual cases, but rather UX research, examining similar projects, and cribbing their solutions. If you categorize a project accurately, you’ll find a solution readily available.

Replacing User Testing With UX Best Practices

Your client doesn’t need to pay for UX testing to benefit from it. Enterprise sites, government sites, and even personal projects will test UX patterns. Sites like Shopify or Stripe will user-test their checkout processes at scale and enable companies to benefit from the results by adopting their platforms.

If you’re currently testing designs for small business, one of two things is true: either you’re wasting your client’s money investigating a problem someone else has already solved, or you’re designing something so original that it has no precedent (and you probably shouldn’t be).

Designers should be opinionated. Designers should know UX best practices and how they apply to a range of scenarios. Designers should be capable of making an educated guess. Designers should be self-validating.

Once or twice in your career, you may find a legitimate need to test something. However, the vast majority of the time, the correct answer is to tip the tortoise back onto its feet and choose whichever color button has the higher contrast.


Featured image: Still of Brion James in Blade Runner. Copyright Warner Bros. Entertainment


The post The Case Against UX Testing first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

Steady growth in the FinTech industry has taken place in the past decade. It is revising the lines in financial services. 2021 has witnessed significant innovation like never before. FinTech companies made a 96% increase in global funding and are turning out to be the « Decacorns. » The rise of FinTech as a Service (FaaS) platforms fueled the expansion of digital banks and the rapid adoption of biometric technology in onboarding. Further paradigms, such as embedded finance and autonomous finance, are emerging components of the sector, and 2022 is expected to see significant maturity.

The question that often turns up is: « What is the future of FinTech in 2022? » The prime predictions will be detailed in the sections below. 

Source de l’article sur DZONE

Après avoir adopté l’ERP SAP S/4HANA, METEX NØØVISTAGO a souhaité améliorer son processus d’élaboration budgétaire. Une tâche confiée à SAP Analytics Cloud Planning, déployé par le Groupe KPC.

METEX NØØVISTAGO est un acteur industriel à la pointe de la bio-industrie.L’entreprise produit des ingrédients fonctionnels (principalement des acides aminées à ce jour) par fermentation pour le marché de la nutrition animale et bientôt de la cosmétique : 1 usine, 100KT d’acide aminées par an, 200M€ de CA annuel, et 350 salariés.

En juin 2020, METEX NØØVISTAGO a déployé un nouveau système d’information en mode greenfield, comprenant l’ERP intelligent SAP S/4HANA, un data warehouse SAP BW/4HANA et l’outil d’analyse de données SAP Analytics Cloud. « Un changement de taille pour METEX NØØVISTAGO,qui avait travaillé pendant 35 ans sur IBM AS/400 », explique Paul Stoffaes, DSI de l’entreprise.

Reste un processus qui n’avait pas été refondu : la planification budgétaire. « Le processus de forecast était réalisé sur Excel, ce qui était long, laborieux et source de nombreuses erreurs. Le contrôle de gestion passait plus de temps à consolider les données qu’à les analyser. Quant au processus d’élaboration budgétaire, il était encore plus fastidieux ».

METEX NØØVISTAGO a donc décidé de mettre en place une solution capable de livrer des prévisions au mois, à l’année et sur plusieurs années, avec une agilité permettant l’intégration aisée de nouveaux produits ou de nouveaux processus. L’objectif est de libérer du temps au contrôle de gestion, afin qu’il puisse se focaliser sur son cœur de métier, l’analyse et le pilotage.

SAP Analytics Cloud Planning déployé sur l’élaboration budgétaire

La société a confié la modélisation de son processus à l’un des modules de SAP Analytics Cloud, le module de Planning. « L’utilisation de SAP Analytics Cloud Planning permet de faciliter l’intégration avec l’ERP SAP S/4HANA, constate Paul Stoffaes. Il y a également une certaine logique à l’utiliser, car nos collaborateurs connaissent déjà SAP Analytics Cloud dans le cadre de la Business Intelligence. »

Le déploiement de la brique Planning de SAP Analytics Cloud a été confié à KPC : « Ils ont bien compris nos enjeux et ont su proposer un déroulé de projet et une méthodologie adaptés, ainsi qu’un chiffrage lisible. Leur capacité à s’engager au forfait sur un planning serré a également été une des raisons du choix de KPC. » METEX NØØVISTAGO avait en effet fixé comme contrainte une réalisation du projet dans un délai restreint de 5 mois.

Le cœur fonctionnel de la solution mise en place est un P&L présenté par produit, accompagné de plusieurs modèles de simulation. Chaque équipe dispose de son propre accès à la solution, afin d’y faire remonter ses données et prévisions : commerciaux, production, achats, logistique… Les informations sont synchronisées chaque jour – dans les deux sens – entre les référentiels SAP S/4HANA, SAP BW/4HANA et SAP Analytics Cloud, au travers de SAP Data Hub.

Voici le détail du processus mis en place :

  • L’équipe de vente fait remonter ses informations : volumes, prix, commissions…
  • L’équipe en charge des achats définit les prix moyens pondérés.
  • L’équipe de production travaille en parallèle sur la définition des nomenclatures.
  • Le contrôle de gestion pilote l’ensemble du processus, en intervenant lorsque nécessaire.

Un projet réussi, qui renforce l’adoption de SAP Analytics Cloud

« De notre point de vue, le projet est une réussite, résume Paul Stoffaes. Il a été mené à bien dans les délais, avec un budget maîtrisé. KPC a su faire preuve d’une solide expertise fonctionnelle et technique. Nous avions séparé le projet sous forme de lots, permettant de dispatcher les livrables tout au long du développement, ce qui s’est avéré très confortable. »

Quels bénéfices a identifié METEX NØØVISTAGO?

  • Des gains de productivité, avec une réduction de la durée du processus et une plus grande autonomie des parties prenantes.
  • Des gains en fiabilité, les données étant extraites puis remontées directement depuis et vers l’ERP SAP S/4HANA.
  • Des gains de flexibilité : « Auparavant, évaluer chacune des hypothèses pouvait tourner rapidement au cauchemar. Aujourd’hui, nous sommes beaucoup plus sereins. »

Le tout avec comme résultat global une amélioration des prévisions. Mais aussi un bénéfice inattendu : un intérêt renouvelé des collaborateurs pour SAP Analytics Cloud. « L’utilisation de SAP Analytics Cloud Planning a poussé certains utilisateurs à se pencher sur SAP Analytics Cloud BI », confirme Paul Stoffaes. La DSI s’attendait à une adoption rapide de SAP Analytics Cloud Planning par les utilisateurs de SAP Analytics Cloud BI. La fertilisation a finalement aussi été constatée dans l’autre sens !

The post L’industriel METEX NØØVISTAGO s’appuie sur SAP Analytics Cloud Planning pour son élaboration budgétaire appeared first on SAP France News.

Source de l’article sur