SAPLiNg

1
SAPLiNg

• Harness the power of Lotus and SAP coming
  together

Yatin Dhareshwar - Solution ArchitectCactus
Computers Pvt. Ltd.
2
Agenda

• Overview
• Why Integrate Customers tell us why
• The Possibilities
• Skepticism
• The Technology
• Case Study
• The Big Picture
• QA

3
Overview

• Leverage individual strengths
• SAP Powerful and complex business application
  that manages an organizations high volume
  business service processing
• Lotus Robust platform for managing unstructured
  content, workflows and messaging

4
Overview
5
Why Integrate?

• Applications need access to multiple data
  sources, other than ERP
• SAP has limited support for Approval systems
• Applications require workflow and other
  functionality across organization remote/mobile
  access
• Savings on Nos. of SAP licences
• Easier tools for custom development and lower COO
• Reduce load on ERP production servers
• Friendlier UI, implementations and training
• Not about just SAP and Lotus thanks to LEI

6
The Possibilities

• ERP Managed Processes
• Manufacturing Processes, subcontracts, shipments
• Sales Order Management, Billings
• HR Data Management
• Payroll/Accounting

• Domino Managed Processes
• Inventory levels management, approvals, vendor
  self-service status verification, production
  reporting
• Workflow managed approvals, customer
  self-service, order placement
• Employee self-service applications
• Appraisal Systems

7
The Possibilities

• Lotus as front-end for SAP
• Disburse SAP information to a much wider audience
• Powerful Office Automation / BPM applications
• Logical progression towards consolidation and
  aggregation of business assets and applications
  The Corporate Portal

8
Lotus as front-end

• Capture data using web-based or PDA based
  front-ends developed using Domino
• Sales team use Domino based SFA with PDA
  interface. Sales information channeled to SAP
• Web-based front-end, extended to the internet
  allows vendors to register online.

9
Disburse SAP information

• Use SAP data in other systems such as Project
  Management
• Use SAP BW to consolidate information from
  different sources
• For distribution of generated reports, these are
  transferred into Domino database and then
  distributed
• Use Domino replication to create offline SAP
  servers

10
Office Automation/BPM

• Office Automation Approval based workflows can
  be handled by Lotus
• Purchase Requisition
• Purchase Order
• Vendor Master (and many other masters)

11
Skepticism

• But SAP can do everything !!
• Wont we create two parallel systems ??
• Lotus is for messaging, isnt it?
• Wont this mean more resources to manage data
  between two systems?
• The Domino guys cant spell SAP and the SAP team
  couldnt care about Domino
• Its not SAP v/s Domino, its SAP and Domino
  together

12
The Technology

• Lotus Connector for SAP R/3 as integration layer
• Plug-in for SAP Connectivity using DECS, LEI
• LCLSX for SAP for customized programming
  interfaces
• MTA for mail routing
• Access to SAP BW
• DECS realtime data transfer between Domino and
  SAP
• LEI transfer huge amounts of data
• Direct Transfer Agent
• Replication
• Archive
• Agent

13
Case Study

• ISPAT

14
Process Block Diagram
15
System Users

• Requisitioners Group of users who prepare PRs
  for their departments
• Department Managers First level approvers
• Head of Departments Second level approvers
• Divisional Heads Third level approvers
• Directors Fourth level approvers
• Account Users Users from accounts group who
  verify account codes in a given PR Item
• Auditors Users interested in viewing Approval
  History for any PR.
• System Administrator Special user who can manage
  the system

16
Functional Requirements

• Requisitioners release PR Item from SAP for
  approval using the Lotus Notes application.
• Whenever PR Item is released, appropriate
  notifications are sent.
• Requisitioners, Approvers, Account Users see PR
  Items that are pending approval or clearances.
• Account Users should be sent reminders if they
  have not verified account code till such time
  that all approvals have been obtained for the PR
  Item.
• Auditors view Approval History of all
  approved/rejected PR Items.
• Requisitioners and Approvers see list of Approved
  and Rejected PR Items for their Department or
  Division

17
Functional Requirements

• Once a PR Item is approved or rejected, its
  corresponding entry in SAP is automatically
  updated.
• Upon approval appropriate notifications should be
  sent to the next approver for the PR Item.
• Upon rejection appropriate notifications should
  be sent to the all previous approvers and the
  requisitioner for the PR Item.
• Capture reasons for approval and rejection System
  can be accessed only by authorized users.
• System should be available for use from Notes
  Client as well as web browser.

18
The Big Picture
19
QA