SAP Connector

As a popular, packaged ERP for enterprises today, SAP has no equal. It is also a fact that effective business decision-making requires a holistic view of enterprise information. Strategic business decisions require timely intelligence from various sources and there is a clear need for historical and operational data to be invoked from disparate (SAP and non-SAP) environments.

As middleware components, SAP connectors can provide quick and simple integration between SAP modules and external business processes without having to write any custom code or modify existing SAP landscape.

Skelta BPM.NET SAP Connector

To connect business insights with business process, Skelta's BPM.NET incorporates a customer centric approach in the form of a proprietary SAP connector that integrates external applications with SAP modules especially when presenting a BizTalk server solution to customers. Skelta's SAP Connector makes provision for data access in and out of SAP without the need to write code or create a host footprint.

Skelta’s proprietary SAP Connector and advanced workflow platform scales SAP’s limited approval and escalation processes by spanning across legacy systems and handling escalation scenarios via SAP.

• Requires no code integration with SAP for business processes
• Integrates transactional and analytical data with any module of SAP using RFCs
• Built on top of Microsoft LOB Adapter

• Eliminates IT dependencies by removing the need for writing code
• Ensures scalability for even complex approval processes
• Information flow is bi-directional – can be retrieved from as well as submitted to SAP
• Focus to configuration instead of developing custom applications for seamless data flow.

Business Scenario

Company 'X' is using SAP HR system for leave management, wherein the leave details are stored in SAP for accounting purposes. The SAP HR system has limited capability in terms of advanced approval and escalation processes. The organization does not want to develop the process using Netweaver platform as it is an expensive option and requires a lot of time and effort. The need is felt for an advanced human workflow, which can span across legacy systems and handle complex approval and escalation scenarios via SAP.

The gap can be bridged with Skelta’s proprietary SAP Connector and advanced human workflow features.

Now, before the leave is posted in SAP, Skelta’s BPM.NET platform is called to have a proper approval process in place.

An employee enters the leave details by making use of Skelta’s form. Once the employee submits the leave request, it triggers the workflow for approval in Skelta through SAP Connector. The Skelta Workflow then forwards it to the relevant managers for approval. The Skelta workflow can also be configured for escalation if the approval does not happen within a specified time period. For example, if the manager does not respond within a certain within a certain timeframe (say 3 days), the request is escalated to the next higher level - to the next manager in the hierarchy. There will be some cases in which the leave request may require approval from a group of people. In that case, the Skelta workflow can be configured to get the approval from the group (which can be set at minimum number of approvals or approval by all). Skelta's advanced workflow engine acts on the approval process, and the workflow will send the approved leave to the leave management system, via SAP, at the same time updating the leave status in SAP. Following this, the employee is intimated of the status.