Month: May 2021

MDG for Customers – All that you need to know

Posted on by stridely

The Master Data Governance (MDG-C) of SAP allows users to crosscheck master data of customers on a leading hub system and to imitate that data to a wide array of diverse client systems.

These superior features and upholding features such as the colossal data load are primarily given to the “Master Data Governance for customer” business function. Another premium feature for redistribution of the customer’s master data ruling is the MDG-C on the clients’ business function.

Also Read: SAP MDG Implementation – Stridely sets another milestone with record time delivery

Therefore, it allows you to contrast and search understandable data on that hub system before changing or building customer master data on ERP. Furthermore, this MDG-C is beneficial to regulate the governance of customer master data on a hub.

So, during this process, some alteration requests are utilized to modulate the creation, and such information is securely preserved in the staging area temporarily. This article will showcase everything you must know about MDG-C. Let’s get started!

How to utilize MDG-C?

Follow the steps below to use MDG-C in an appropriate way:

The major prerequisites

In the data personalization activity of activating business functions, you need to activate the below-mentioned business functions:

  • MDG-C on a Hub system

➔ Generic Functions 2, Master Data Governance (MDG_FOUNDATION_2)

➔ Business Foundation: Business Partner Services (CA_BP_SOA)

➔ Generic Functions, Master Data Governance (MDG_FOUNDATION)

➔ FND_SOA_REUSE_1

  • MDG-C on a Client system

➔ FND_SOA_REUSE_1

➔ Master Data Governance for Customer on Client (ERP) (MDG_CUST_ERPCLIENT_1)

➔ Business Foundation: Services for Business Partner (CA_BP_SOA)

Also Read: Ensure data integrity and consistency across the business infrastructure with SAP MDG

How can customization be done?

All the MDG oriented customizing data can be accessed via utilizing the transaction MDGIMG. You need to coordinate the settings in the below-mentioned customizing undertakings for the business partner:

➢ Identify and clearly define BP roles

➢ Sustain industry work ethics and systems

➢ Chosen BP roles can be repeatedly utilized while setting the BP role category for directing BP to consumers

➢ A premium activation switch for function

What can you do with an ERP client system?

You should know that customer data could also be managed on that ERP client system. Here you can:

  • Change or create customers on its client system
  • Changes will be saved on the client tables to continue business with this data
  • The customer data is imitated to the governance process and central hub
  • Once approved, the customer is copied to all the pertinent client systems

What can you do with a central hub system?

Here you can:

  • Control customer data and imitate it to MDG-C to distinct client systems, for example, CRM, ERP, and non-SAP systems
  • Utilization of colossal data to draw out data from the client system
  • Upload those data into the master data portal
  • This system upholds the uprooting business partner and customer data from both the ERP and CRM systems across various releases
  • Utilizing SOA services for the recent release
  • In the case of previous releases, it uses iDocs, one of its existing functions

Leading features of MDG 7.0 the application

The Master Data Governance for the customer provides the following top-notch features:

➢ Improved CRM integration

The top-notch CRM integration allows users to disseminate a broader range of data into various CRM client systems. The master data controlling for customer 7.0 can be evenly distributed to the ERP customer-oriented traits, such as partner functions and sales. However, this data is incorporated into the fathomable data structure given by the CRM.

➢ IBAN without BIC

MDG-C satisfies the legitimate need of the SEPA to sustain the IBAN for such countries diligently. The generation and maintenance of bank details such as business identifiers code are not at all needed again.

➢ Listed features

It provides numerous enhancements for the services, for example, searching, creating, and changing customer data.

➢ Template for disseminating workflow

The business function allows a brand new workflow template that adjusts to the general organizational establishment to generate customer master data. So, once the request is submitted, an approver will crosscheck the central data.

➢ The connection between ERP vendor and ERP customer

The standard data of an ERP customer consists of a link to a similar ERP vendor. The premium business function helps create a vital link between the master data model.

➢ One-step creation of powerful relationships

This allows you to enter relationship-driven data referring to the business partner, which is not recorded in the system. Hence, it means you can efficiently edit a customer’s relationships to a significant business partner, which you build in a collateral way.

Also Read: SAP Master Data Governance – Streamlining Business Processes

Leading features of MDG 8.0 the application

The features of MDG 8.0 are shown below:

➢ Imitate customer data

Such an incredible feature enables you to imitate company code and sales area information within a customer. So, the mentioned data restrains you from choosing a copy, and it will copy the entire data reutilizing a predefined option of the saved data. However, this feature has been incorporated into MDG 7.0 SPO3.

➢ Address screening: Business partner

Such an incredible address screening feature is based on the association of SAP Fraud Management. So, it allows authorized consumers in change request processing in central governance, SAP MDG, in order to execute the screening of an individual and an organization by SAP Fraud Management.

In order to utilize the SPO7 address scanning feature, it needs to be installed first and must be enabled too! If you want a detailed guide on how to upgrade and install SAP Fraud Management, you will have to visit the SAP portal.

You may also take assistance of SAP experts at Stridely for this, or any SAP MDG for Customers issue.

➢ Build up business partner with reference

Such an extraordinary MDG 8.0 feature enables you to build up a customer with reference to any existing data. Within the application list, you may opt for any record and select a preferable copy. So, it will help you create a top-notch record reutilizing a predefined alternative to the existing data.

Leading features of MDG 9.0 the application

  • Texts for your ERP customers

You can efficiently type explanatory texts for your leading ERP customers on common ground, such as organizational sales and code area levels.

  • Data imitation

For all the necessary fields, value mapping configuration is available on all terms. All the significant value mapping fields are given to a personalizable value table.

  • Long tax numbers and IDs

Anyone can now type tax numbers with a maximum length of 60 characters. Its features have nowadays been made accessible to SAP Masters Data Governance 7.0 and higher versions.

  • Organizational addresses of International address versions of the Contact person

You may type countless versions of an organization address of a contact person in distinct character sets; let’s consider Cyrillic or Chinese sets. This unrivaled function has been pretty accessible to workplaces and their employees. Moreover, it is also available for organizational addresses. Extra necessary fields are open on the Fiori App request MDG-C.

  • Countless record processing

This function allows you to edit a customer data number record. Therefore, such data processing provides a hassle-free and seamless procedure. With the help of a UI, you can efficiently create change requests with optimum effectiveness for numerous records. However, multiple-record processing provides the below-mentioned benefits:

➔ Multiple records could be directly upgraded from the search function

➔ Find and replace features allow to emulate data to chosen rows and to display rows with analogous values

➔ Direct omission of specific individual options and values to eliminate changes

➔ Highlight alterations feature offers color coding for a fathomable identification of values and fields altered in the recent change request

  • Highlight deletions

As the fleet advancement of the highlight changes feature, the “highlight deletion” features is accessible and allows the customer to highlight omitted values, such as eliminated rows.

So, in order to recuperate the advanced version of the omitted data, it showcases the pertinent rows and those values as strikethrough. Therefore, it supports you in rapidly ascertaining items for elimination while going through the change requests.

That’s how a customer can get an easy and new way to recoup data with the availability of SAP Master Data Governance 8.0 SP02.

The major constraints

  • To disseminate customer data and business partner data from an ERP system finally into a crucial CRM client system as of CRM 7.01 and more than 7.01 services are needed.
  • Master data Governance for customers (MDG-C) neither uphold time validity for bank information and addresses nor time dependency for address usage and central data.
  • MDG-C can’t operate on customers utilizing the SAP business customer and partner with time validity and dependency for other objectives.
  • MDG-C only upholds the reutilization of some of the opted field modification criteria. Moreover, it is not at all doable to subdue fields or change fields to demonstrate only the MDG-C user interface.

Concluding words

In a nutshell, the SAP MDG-C application manages and integrates master data throughout any workplace. Being the SAP’s seamless Business Technology program and the master data management layer, it offers trustworthy and consolidated master data via countless domains.

 

 

 

SAP Hybris Upgradation to 2005 – Why and How to do it?

Posted on by stridely

SAP Hybris commerce has been getting upgraded to keep itself up for the ongoing competition in the field. The changes that are considered include tackling the defects of the platform, updates on the security, enhancements, and modifications to its architecture.

The existing integration is now powered by the enhanced data model of SAP Commerce Cloud 2005, and it’s the very right time for an upgrade.

Also Read: FedEx Integration in SAP Hybris eCommerce – Everything you need to know about it.

Benefits of the Upgrade

Here are few major benefits of the upgrade of SAP Hybris to 2005:

  • The upgrade allows an organization to streamline the complete ecosystem.
  • Gathering information, examining them, and ensuring whether or not they are required for the current set, this ensures that the system runs smoothly and the way it should benefit the enterprise in the best possible manner.
  • It allows refreshing all the applications and enhances the performance of the system.
  • It also strengthens your enterprise’s security. As the patches do not last more than two years, the system runs smoothly without any interruption in the technical support.

Step-by-Step Procedure: SAP Hybris Upgradation to 2005

Upgrading SAP commerce includes the following steps. These steps are common for near to almost all releases. Let’s have a quick glance.

  • Download, unzip and build the new distribution.
  • Pass the custom code to the newer version of SAP Commerce and make the changes that are required to ensure compatibility
  • Copy the configuration files and make change wherever necessary
  • Migrate data and media files.

Note: Compatibility can be a major issue if you are carrying over the custom code, so pay attention to the additional information section of the upgrade guide for each module you include in the upgraded system.

Here is the detailed procedure for the same:

Step 1: Close the SAP Commerce Instance

The first step should be shutting down the instance of SAP Commerce that you want to upgrade.

Caution: It is advised to take back up of everything that will be touched in this upgrade. So, keep a copy of the entire SAP Commerce while retaining its directory structure and components, e.g. platform, configuration files and extensions. To optimize the size of your archive, you can run ant clean.

Step 2: Determining the location for 2005 Platform Deployment

  1. Replace Platform and SAP Commerce alongside the extensions (in $ {HYBRIS_BIN_DIR})
  2. Download the SAP Commerce ZIP file and Extract everything to a new folder, just where you want to install the 2005 system.
  3. If required, update the customized extensions to accommodate changes to the third-party libraries or deprecated functions.

Step 3: Migrating System Configuration

Move to the old system configuration and do the following:

  1. Run ant clean on the new system. This will create the config folder in the new instance of SAP Commerce. If asked to choose a configuration template, choose the production configuration template.
  2. From your old location copy local. properties and local extensions.xml configuration files to the new config folder (<${HYBRIS_CONFIG_DIR})>
  3. You might have a few third-party DB drivers, e.g. MySQL or Oracle, look for them in your ${HYBRIS_BIN_DIR}/platform/lib/dbdriver folder.
  4. If found, make a copy of these drivers to your new platform in a folder placed at the same path.
  5. In case you need to, editing can be done in the localextesios.xml file to add more extensions found in the new release. Also, optionally, adjust the local properties file to include any new or changed properties.
  6. We recommended changing the database connection and let it locate to the point that contains the new copy of your database, In this way, the old database will be preserved and will be available back in case of migration errors.
  7. Install a License if necessary. You can find more information regarding the license here.

Step 4: Migrating File Data

A platform stores data in the binary form that needs to be migrated before starting the system with the new upgrade.

Those media data files are stored in ${HYBRIS_DATA_DIR}/media

Step 5: Migrate your media data

  1. Create a backup of the media files for future safety.
  2. Copy the files in the same directory in the new SAP Commerce location
  3. For the systems with embedded HSQLDB, database is located at <HYBRIS_DATA_DIR>/hsqldb. You may again create the same path and copy-paste that folder there.

Step 6: Start the Platform Build Once

  1. Navigate to the <HYBRIS_BIN_DIR>/platform directory.
  2. Run sentantenv.bat on Windows or ../setantenx.sh on Linux.
  3. Execute ant all.
  4. Wait for the build to finish. It may take some time.

Step 7: Upgrading the Database

To be able to use the existing database, you need to make some changes to adjust it to the new system installed. Two ways of executing this upgrade are as follows:

  1. Online using Administration Console of SAP
  2. Using the Command Line

Step 8: Adjust your existing database for the new system.

Upgrade using the Administration Console can be handled in the following manner:

  1. Navigate to $ {HYBRIS_BIN_DIR}/platform directory
  2. To start your system, execute hybrisserver.bat on Windows. For a Linux system, run hybrisserver.sh from your current directory.
  3. Quick open SAP Commerce Console, http://localhost:9001/platform/update
  4. Select Update Running System and confirm by clicking the update button.

Step 9: Upgrade from the command line

To upgrade from the command line:

  1. Go to <HYBRIS_BIN_DIR/platform> directory
  2. Run ant updatesystem

Also Read: Dynatrace for SAP Hybris – The Arrival of the Commerce Cloud Monitoring Age

The Final Word

SAP Hybris upgrades are important for the smooth functioning of the system but at times get complex too. The entire upgrade should be taken as teamwork where all the enterprise teams can work together to make this happen appropriately. It is, indeed, a realization of the foundation of each enterprise where new futures are implemented.

Also, a very important thing that needs to be kept in mind during the upgrade is to ensure minimal moving parts. It would lead to a successful upgrade in a short period.  This fact plays a vital role in the major upgrades.

Make sure to upgrade your SAP Hybris Commerce regularly. When a gap of time gets in between the two upgrades, it becomes difficult to manage things and makes it much more complex. An interval of 12-18 months is considered an ideal period for the gap between the two upgrades. Follow all the above-mentioned steps and suggestions and make sure the upgrade takes place well in time and efficiently.

To take expert help in SAP Hybris Upgradation to 2005, contact Stridely. This way, you can save your time and efforts while having the surety of successful upgrade.

 

 

Enabling SSO between Your On-Premise and Cloud Application – Should you do it, and how to do it?

Posted on by stridely

SSO refers to a Single Sign-On portal for the users, enabling them to use one as their user credentials to access all their apps on the web in the cloud and behind the firewall. This has proved to be a blessing for the users that saves time and ensures various other benefits. The companies have now got something that provides multiple benefits to them with a single login.

Here is a brief discussion about how these two systems work and what is the need of each one of them in an organization:

  1. Cloud SSO: It does not support access to the applications that are popular on-premises applications. Such applications include PeopleSoft, e-business suite. It also lacks the support for the patterns which are integrated like Gerber’s, Header based authentication and IWA
  2. On-premise SSO: These lack the key carriers required to support the applications on the cloud, including popular apps like Office 365, Salesforce, and AWS. It also lacks the new age features of security, which are needed in the public networks, like password less access to the network and the Ability to endure easy scaling of cloud traffic support.

Benefits of enabling SSO between on-premise and cloud application

Here are some of the benefits of enabling SSO between on premise and cloud application:

  • Increased productivity: With the features like passwords refers, provisioning projects, manual de-provisioning and shadow IT policing, and it helps the company to increase its productivity to a great extent.
  • Reduced costs: The major factor influencing a business is its finances. If they are taken care of properly, half of the battle is won. The automated processes, deployment of integrated applications and much more enable the company to eliminate identity infrastructure costs. This reduction in the costs helps it in infinite other ways.
  • Strong security: Security is a major problem of concern for an organisation. By executing the identity policy across its users, clouds, and devices, it helps make sure that instances like data breach and losing data do not occur at all.
  • Growth: Things that relate to the growth of an enterprise are not limited to a certain area. With the new king of SO between on promise and cold application, users get an opportunity to start instantly with the required apps, along with aligning with the identity policy completely.
  • Increased Finances: With the implementation of these techniques, the companies tend to witness a great increase in the overall finances.

Required roles and services

To configure and ensure that the web applications are activated in the cloud, here are a few roles of an administrator:

  1. Security administrator
  2. Identity domain administrator
  3. Application administrator

Accessing the applications and various kinds of services may need users to keep a regular check on multiple URLs, passwords, and usernames. When the cloud provides SSO capability across on-premises and cloud applications, it is highly convenient for users to access the applications and maintain high-end security.

As it is difficult to migrate the applications on-premises, identity management becomes even more challenging. One has to add software as a service that is also referred to as SaaS. There are various ways that the cloud provides to integrate and take advantage of SSO.

With the help of a single sign-in, it is easily controllable to manage who can have access to SSO, and the users can, after that, enjoy one-click access to all these apps. While it also connects most securely through trusted relationships, this trust is formed when the application is added from the SSO console-After that, configuring it with appropriate metadata is the most desired input.

After installing the application successfully, one can manage the users who have to access the applications. No users are assigned by default; they have to be added manually, ensuring efficient use. Here are the following applications supported by AWS SSO:

  • Cloud applications
  • AWS SSO integrated applications
  • Custom security assertion markup language.

The system also allows the employees to grant access to the management console for a single account.

The required balance for the system

As SSO enables the user to access many apps simultaneously with just one credential and a single click, it tends to raise the impact of the user’s credential being compromised.

MFA is a method of controlling the access where the user is given the access only when he successfully presents separate pieces of evidence, typically any two: possession, inference or knowledge. The most common type of MFA used is two-factor authentication, also called 2FA.

Here is an example to understand things more clearly:

Most of us are aware of two-step verification which includes a password and then setting up an OTP as a sector factor. Other factors involved are OTP, phone call or SMS. As it involves 2 factors in the authentication, it is called 2FA.

The changing trends

After knowing about the details of the system, here are two major things or the trends that have changed:

  • Cloud Solutions support almost all the on-premises applications
  • SSO on-premises solutions are getting more deprecated.

The change in this two-key trend has brought about a revolution in the way the system works.

Organisation uses several other variations in the cases where the user is not personally known to the company. A very good example of this is the way credit card companies work. They tend to take out information from their credit files and present these as questions to them. They tend to move further with the course of action only when they can answer all the questions.

Conclusion

It is a really good idea to use SSO for on-premises and the cloud. As these are used, various solutions are answered very easily and abruptly.

While SSO can be used for servers, custom apps and on-premises apps, it is indeed a recommended measure to ensure improvement in not just the user experience but improved standards for administrators too. It enables the organisation to strengthen its security, reduce costs and avoid any kind of deprecated solutions.

Not sure if you could handle it in-house?

You may ask experts to help you in this process, or any other kind of ERP implementation support if needed.

 

 

App Modernization for Enterprises – The Transition from Legacy Systems

Posted on by stridely

Wine gets better with time or age, not applications or software. We can’t emphasize much on the need of owing updated, latest, and feature–rich application to thrive. In the ever-changing world, it is not easy to prevail in all the hurdles with a system that is a decade old.

Can you imagine make through the current remote or work-from-home situation with an IT infrastructure that still runs on Windows 5? It is out of the question. This is where app modernization comes for help.

What it is, how it happens, and why one should give their curial legacy systems require a much-needed makeover are some of the questions that we will try to answer in this post.

Are Legacy Systems Enough To Pull You Through?

The legacy system often referred to as tools & technologies that are based on outdated technologies yet are crucial for conducting day-to-day tasks, are both a boon and bane.

While their existence is needed for seamless processing, their outworn modus operandi can make you lag or linger in today’s competitive world.

The perfect example of facing hassles because a business/enterprise didn’t gave-up its love for the legacy system just happened recently. On Tax Day 201, the Internal Revenue Service wasn’t able to process all the electronic-filed tax returns because their existing IT systems were outdated and crashed in the blink of an eye.

Also Read: Transform your enterprise outlook with Data Modernization

If a high-end body like IRS can’t prevent an IT downfall, what can we expect from a small or budding business? They can lose their grounds because of using legacy systems.

Let’s show you a big picture of issues that can face due to legacy apps:

  • Legacy apps are not properly guarded. Even if you try to safeguard them, you will taste failure as their year-old configuration doesn’t support the advanced security configuration. And we all know what could happen to data or other crucial details, saved on an unprotected system.
  • Most of the legacy system refuses customization and integration. Hence, you will experience literally zero flexibility.
  • It is imperative to invest a huge chunk of money in the support and maintenance of the legacy system. All thanks go to their complex nature. You will be shocked to know that the US Federal government wasted 80% of the total IT budget on Operations and Maintenance in 2019. A huge a portion of that 80% was consumed by aging legacy systems.
  • Legacy systems score very less when user experience gets counted. Their proprietary languages and technologies render a shoddy experience to the end-user. The direct impact of this is on the team’s productivity and efficiency.

We think all the above points are adequate to let you realize that what hidden damage that your decade-long legacy system is doing to your organization.

App Modernization – A Viable Solution 

While it this clear those old-fashioned technologies are no less than an open pit of hurdles, enterprises are trying hard to spot a way out from this situation. App modernization is the ray of hope in this situation.

It refers to the process of giving a touch of modernism to the existing legacy system by updating its infrastructure, features, and internal architecture.

Some of the most ideal legacy systems for app modernization are monolithic and on-premises applications.

Below mentioned are some of the reasons explaining that app modernization paves the path for beneficial transformation:

  • App modernization keeps an enterprise-ready to face the world and remain relevant. Capabilities like recording and conferencing, which were absent earlier, can be acquired easily.
  • As app modernization allows an organization to add/implement security features in the legacy systems, there would be enhanced and leveraged data security.
  • With app modernization, enhances business agility is a sure thing It will become easier to add existing features and changes as per the changing business needs. This has a direct impact on the efficiency of the businesses.

Now, that it is clear the transformation of legacy systems lies in the heart of app modernization, it’s time to know about some of the best legacy system modernization strategies.

Strategy 1 – Architecture-Driven Modernization (ADM) 

This is a coordinated strategy involving understanding and advancing the existing software assets. The best advantage of this strategy that it adheres to a design-based perspective towards legacy system modernization. With the help of this strategy, aging software will become more agile.

Strategy 2 – SABA

SABA is an upper-level app modernization framework used mainly for planning organizational issues that might arise during the evolution and migration of legacy systems. This strategy is famed for tackling multiple issues while offering a means of finding out the future implications of software choices.

Strategy 3 – Reverse Engineering Model

In the strategy, old-fashioned legacy applications are migrated to the new and updated ecosystem slowly and gradually. Legacy data migration is the last step in this strategy. For accessing legacy data in a new environment, the Reverse Gateway process is used. This is the best pick for the transition of hefty and price projects.

Strategy 4 – Visaggio’s Value-based Decision Model (VDM)

If technical and economic aspects of app modernization are taken into account, this is one of the viable software renewal processes that any enterprise can adopt. This is bought into the picture when enterprises feel that their legacy systems are reaping reduced economic returns and quality than the expectations.

Strategy 5 – WMU 

WMU stands for Warrants, Maintenance, and Upgrade. This is a customer-centric legacy system transformation process in which maintenance strategies are chosen as per the customers’ satisfaction and need. Because of this reason only, it often becomes too hectic. One has to gather and analyze a whole bunch of information. But, it is quite impactful.

The Bottom Line 

Regardless of the shape and size of your business, you must give your legacy systems a quick and much-needed update. This single step will help me become more time-relevant, productive, and competitive. So, if you haven’t thought about it, it’s time. There are many kinds of processes and strategies available for app modernization. Chose as you please.

While you’re thinking of app modernization, always hand over this job in the hands of experts only. Stridely Solutions has the best team to make this happen. You may contact us immediately.