Gimmal Blog

Read the latest thought leadership and industry news from the experts at Gimmal!

All Posts

Can SharePoint and SAP Work Hand-in-Hand?

The below blog post comes from a white paper produced by ASUG and Gimmal: Cruising Along the Information Highway: Understanding your SAP EIM Environment. It discusses the results of a recent survey of the ASUG community surrounding information management best practice awareness.

The data is crystal clear: Almost everyone uses SharePoint. The near-optimal penetration of Microsoft Office 365 as a productivity suite means SharePoint is often the first line of defense when it comes to storing and retrieving documents. Those engaging in EIM would be foolish to ignore its role among most companies, especially those who run SAP technology. Any software solution provider with EIM support products would be wise to integrate well with SharePoint. After all, it’s much easier to leverage and optimize an already-existing product than to try and replace it with a new one, right?

Don't just use SharePoint: Use SharePoint Right

While SharePoint is a popular product that has evolved and expanded to accommodate as many business needs as possible, it can introduce major difficulties with properly storing and retrieving documents, especially within large companies with significant volumes of information. How should you handle this? In short, you can leverage EIM software integrations that can connect with SharePoint but automate certain steps to make document retrieval and management simpler. These solutions are designed to streamline SharePoint for those who use it as the default information discovery platform. They make things easy to find and act on. For example, by integrating SharePoint and SAP at the content level, the data level, and the workflow level, your organization can use SharePoint as an SAP HTTP Content Server, providing the simplest and widest access to unstructured content while retaining its association with SAP business processes.

Certain processes can also reduce human error if automated. For example, if two employees are working on the same document, being able to automate the retrieval and execution (e.g., only one employee working within a document at a time) will help eliminate possible issues with duplication. This means that your company’s people can collaborate (not duplicate) and work on the same document-centric processes without having to worry about platform constraints.

There are many benefits to running an EIM extension that complements SharePoint. Of the 94 percent of ASUG members who use SharePoint currently, however, only 36 percent employ a second EIM solution to optimize their processes. This may be due to lack of awareness rather than a conscious business decision.

ASUG Figure 3

To learn more about how SAP and SharePoint can work together to improve your organization's information flow, watch our September 5th webinar with ASUG: Building a Better Information Engine.

Building a Better Information Engine: Register now!

Related Posts

3 Tips to Ensure KORA Compliance

There has been a spotlight on the Kansas Open Records Act (KORA) in the media lately, largely due to recent violations. Under KORA, any individual can request public records from government bodies. If all requested records are not provided within in a specific timeframe, these organizations are subject to significant repercussions. This is merely one example of a ‘sunshine law’. The purpose of sunshine laws is to provide transparency into government agencies by giving the public access to local government proceedings.

Creating a Retention Schedule that Works

Creating a usable, automated, and simple file plan is an important part of ensuring records are managed in a consistent manner and that you are protected from legal risks, such as failure to disclose information during a discovery proceeding or the unauthorized leakage of information. The first step in the process is creating a retention schedule, which outlines how long records are kept in accordance with the organization’s obligations and the law.

How to Manage Your Sprawling Content

Sprawling content, the spread of content across multiple repositories, has been a thorn in the side of records managers since the dawn of document management. Consolidation of repositories, which began in the early 2000s, at first looked to be the solution. However, it ended up highlighting the problems of content sprawl due to the high costs of consolidation as well as need for records managers to manage multiple file plans. Federated records management offers a solution to these problems but doesn’t offer the same locked-down approach with regards to regulation that consolidation can. Consolidation of repositories and federated records management both have pros and cons and, depending on your organization’s content management processes and repositories, one can be more beneficial than the other in the long term.