• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
5DT
 

5DT

on

  • 561 views

 

Statistics

Views

Total Views
561
Views on SlideShare
561
Embed Views
0

Actions

Likes
0
Downloads
6
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • EP 2.0 has a comprehensive, integrated e-Business infrastructure that can be deployed globally using different languages and character sets. It can help you streamline global IT operations because you don’t have to buy a different platform for each country. This infrastructure offers the robust functionality required by large enterprises. It is scalable for hundreds of thousands of users, and available on a 24/7 basis. It is built on a J2EE-compliant application server. It offers LDAP directory support. It has a built-in, integrated security framework that enables role-based single sign-on. It has a context-based search mechanism to narrow searches effectively. It supports Data Server to store and synchronize data. It’s a comprehensive infrastructure that is extensible. You can build new applications on it, and you can deploy applications company-wide to streamline your operations.
  • With Enterprise Portal 2.0 we have expanded capabilities of every level to create a foundation for e-Business. EP 2.0 provides an extended e-Business platform and enterprise portal. It has greater enterprise integration capability. Its B2B extensions provide for automated B2B collaboration and marketplace integration. Its mobile/wireless extensions integrates mobile and wireless devices into the enterprise.
  • Note: this is an optional slide that shows how e-Biz Integrator works This diagram represents a typical network of applications. The top row are applications which produce data, and the bottom row applications which receive data. Here’s how e-Biz Integrator works (click the mouse). The policy processing system produces a policy. This is a source of data sending a message to MQSeries Integrator. Next, based on the message content (click the mouse), a rule is triggered, which generates two different messages (click the mouse), to two different systems, in the appropriate formats. Let’s see what happens when you add another application to the network. (click the mouse) The compliance system only wants data from certain policy events. To handle this requirement all you need do is add another rule (click the mouse). The original message triggers this rule, which generates another message in the format, required by the new application. (Note that with a data mapping product, Compliance would get ALL messages, regardless of content, or you would need to program the selection logic in the Policy System, which is invasive.)
  • Once logged on to the SAP system, the left window pane shows the integration technologies that are available for SAP. In this case the administrator can choose between Intermediate Documents (IDOCs) Data Migration Interface (DMI) BAPIs Remote Function Calls (RFCs) In this example the user would click on Intermediate Document IDOC. In the editor window the user can leave the fields blank in which case when the check mark is clicked all IDOCs will be presented as shown in the next slide. The user can also enter wild card criteria in the Name field to find a specific set of IDOCs or just one IDOC to work with.
  • This screen shows a list of all IDOCs in the SAP system. The user can then click on the specific IDOC format that they want to have copied from the SAP system to the MQSI Formatter. The user also has the option of copying the input form of the IDOC or the output form of the IDOC or both. There is also a validate button on the screen. This little button is extremely powerful and will save the user an incredible amount of time. In large SAP environments there are hundreds if not thousands of people involved in the installation. In this large effort there are people changing IDOCs on the SAP side with out necessarily communicating the changes to every person involved with the integration efforts. If the IDOC in SAP changes and the IDOC format in MQSI is not changed in a similar manner, MQSI will be outputting incorrect records to SAP which will not be accepted by the ALE subsystem. The user can push this ‘validate’ button at anytime, and the system will check the IDOC definition in the SAP system against the format loaded in MQSI. If there is a difference the user will be notified of the discrepancy.

5DT 5DT Presentation Transcript

  • ERP Integration Rob Smith Pre-Sales Manager New Era of Networks North Europe [email_address]
  • ERP Integration - Agenda Open Business Interchange
    • Why Integrate?
    • What Integration Architecture?
    • What can Sybase Offer?
    • SAP Example
  • But, Firstly...
    • Who am I?
    • Who are You?
  • ERP Integration - Agenda Open Business Interchange
    • Why Integrate?
    • What Integration Architecture?
    • What can Sybase Offer?
    • SAP Example
  • Problems Without Integration... Open Business Interchange
    • Duplicate data entry
    • Multiple user interfaces
    • Out-of-step data
    • Data errors
    • Inability to obtain complete information
    • Inefficient operation
  • ...Problems Without Integration Open Business Interchange
    • Poor customer service
    • Long cycle times
    • High costs
    • Inadequate operational support
    • Poorly informed management decisions
  • Couldn’t We Just Re-write? Open Business Interchange
    • Large investment in existing software
    • Business depends on it
    • Lack of knowledge and skills
    • Long timescale
    • High cost
    • High risk
  • Business Integration Drivers Corporate acquisitions Your Suppliers Your Company Your customers Globalization e-Business Cost and cycle time Competition & Consumer power 2. Mergers & acquisitions 1. Packaged application integration (ERP) 4. Supply Chain 5. Straight-through Processing 6. Web Integration 3. Customer relationship management
  • Enterprise Portal EP 2.0: e-Business Infrastructure
    • Comprehensive, integrated e-Business infrastructure for streamlined global IT operations
    • Scalable and available for 24x7 operations
    • J2EE Application Server
    • LDAP Directory Support
    • Integrated Security
    • Concept based Search
    • Data Server
    Enterprise Integration B2B Extensions Develop and Deploy Faster Mobile & Wireless Extensions Portal Services
  • Sybase EP 2.0 Foundation for e-Business e-Business Infrastructure Documents ERP/ CRM Database Mainframe Custom Feeds Net Markets Web Users Mobile/Wireless Users Business Systems www Enterprise Integration Enterprise Portal 2.0 Trading Partners Portal Services Mobile/Wireless Extensions B2B Extensions
  • ERP Integration - Agenda Open Business Interchange
    • Why Integrate?
    • What Integration Architecture?
    • What can Sybase Offer?
    • SAP Example
  • Point to Point Integration 56 Interfaces SAP Legacy Mfg. Human Resources General Ledger Customer Relations Logistics Web Application Supply Chain
  • Critical Integration Issue How can users substantially reduce the effort required to integrate the next built or bought application? ERP Deployment Level of Effort Integrating 2/3 Configuring 1/3
  • Point to Point Integration 56 Interfaces SAP Legacy Mfg. Human Resources General Ledger Customer Relations Logistics Web Application Supply Chain
  • Point to Point Integration ….
    • complex core integration design
    • high impact of changes to business practices
    • high impact of additions to the business
    • high cost of design, development and testing skills
    Hub and Spoke Integration Architecture Minimises these Problems
  • Integrating systems with an Integration Broker 16 Interfaces Integration Broker SAP Legacy Mfg. Human Resources General Ledger Customer Relations Logistics Web Application Supply Chain
  • Integration Broker Advantages
    • higher speed to market of new products and services
    • extended life of existing systems
    • unrestricted use of new ‘best of breed’ by businesses
    • administrative efficiency
  • The Need for Adapters
    • Link applications to the integration architecture
    • Import application formats to the broker
    • Put application data onto queues
    • Get application data from queues
    Logistics Integration Broker SAP Legacy Mfg. Human Resources General Ledger Customer Relations Web Application Supply Chain
  • Essential Integration Capabilities Move Route Transform Enrich Bridge Application Application Application Application Application Application Application Application P R O C E S S A U T O M A T I O N
  • ERP Integration - Agenda Open Business Interchange
    • Why Integrate?
    • What Integration Architecture?
    • What can Sybase Offer?
    • SAP Example
  • Sybase Brokers and Supporting Products Total Solutions Products Integration Brokers Powering the new economy Support & Enhance Integration Broker Delivery e-Biz Integrator - Designer - Rules - Formatter e-Biz 2000 - MS environment Enterprise Portal Adapters Monitoring Security Validation Repair Conversion Tools Plug-in Libraries Services Training Support P R O C E S S A U T O M A T I O N
  • Integration Designer
  • e- Biz Integrator Processing In the appropriate formats e-Biz Integrator Rule Rule Update target systems Produces a policy In the right format Add a new rule! Add a new application Claims Policy Processing Payroll/ Personnel Investments G/L Asset Management Customer Management Regulatory Reporting EDI Compliance
  • Process Server Business Process Automation BroadVision Commerce One EDI XML Application Server Map Process Flow Within and Between Enterprises Manage Runtime Execution of the Process Monitor Business Process Effectiveness Modify and Update the Process e-Biz Integrator Adapter Adapter Adapter Adapter Process Server Enterprise Portal Customers Suppliers Partners
  • Our Adapters….. Business Packages: Enterprise Adapters: B2B Standards: Protocols: Other: Adapter Adapter Adapter Adapter Adapter Terminal Adapters:
    • COBOL
    • Database
    • Flat Files
    • 3270/5250
    • VT220
    • 26 others
    • user defined
    • LU6.2
    • TCP/IP
    • FTP
    • EDIFACT
    • XML
    • S.W.I.F.T.
    • FIX
    • HL/7
    • COM
    • CORBA
    • Java
    • e-ADK
    • e-Mail
    NEON Integration Broker
  • Sybase - The Total Integration Platform Logistics Distributors Partners Suppliers Exchanges FIREWALL Enterprise Portal FIREWALL Process Server Business Process Accelerators Integration Brokers Adapters Enterprise Portal Back Office SAP Oracle PeopleSoft JDE Seibel Legacy Supply Chain i2 Manugistics Oracle SAP FIREWALL Open Business Interchange Wired Wireless Collaboration Self Service Sybase Interwoven Vignette IBM BEA
  • Open Business Interchange Services
    • Self Service
      • Configure
      • Monitor
      • Maintain
    • Format Transformation
      • NEON Formatter
      • NEON e-Biz2000
    • Message and mapping repository
      • xCBL, cXML, RosettaNet, OAG, ebXML
      • EDI, FIX, SWIFT etc….
      • Custom
    EAI F I R E W A L L Open Biz C1 Ariba Oracle Partners Others.
    • Send your format, protocol, and security and Open Biz will deliver to your partner or exchange in their format, protocol, and security
  • Open Business Interchange Services
    • Protocols
      • SMTP/ POP3
      • FTP
      • HTTP/HTTPS
      • MQSeries/MSMQ
      • NEONEmq
      • SOAP
      • EDI VAN
      • XPC
      • BizTalk
      • WAP/WML
      • Our intent is to support all protocols
    SQL Internet WWW BIZ CONFIG HTTP FTP HTTP POP3 OTI SMTP FTP OTI … Queue Farm/Backbone Back-end Processors/Mappers/Services Routing & Service Rules Engines Response Agents Resources Agents HTTPS EB2K XML
  • ERP Integration - Agenda Open Business Interchange
    • Why Integrate?
    • What Integration Architecture?
    • What can Sybase Offer?
    • SAP Example
  • Integrating SAP with... Business Packages: Enterprise Adapters: B2B Standards: Protocols: Other: Adapter Adapter Adapter Adapter Adapter Terminal Adapters:
    • COBOL
    • Database
    • Flat Files
    • 3270/5250
    • VT220
    • 26 others
    • user defined
    • LU6.2
    • TCP/IP
    • FTP
    • EDIFACT
    • XML
    • S.W.I.F.T.
    • FIX
    • HL/7
    • COM
    • CORBA
    • Java
    • e-ADK
    • e-Mail
    NEON Integration Broker
  • SAP R/3 Structural Basics
    • ABAP/4
      • Specific object oriented programming language, dynamically developed: (Advanced Business Application Programming)
    • Business Object
      • The SAP business objects held in the Business Object Repository (BOR) describe complete business entities that encapsulate their data and processes
    • BAPIs - Business APIs
      • Methods by which processing applications (external or internal) can access Business Objects
  • SAP R/3 Structural Basics
    • Function Modules
      • Subroutines written in ABAP that process data inside R/3. Developed in the Function Builder, they are managed in a central function library, and can therefore be called from any ABAP program
    • Remote Function Calls (RFCs)
      • Provide the transactional integrity
      • The access through the application server controls the correct data synchronization  database integrity
      • Calls are executed in the right order and within the same program context
  • BAPIs and Remote Function Calls
    • BAPIs are defined in the Business Object Repository (BOR) as methods of SAP business object types or SAP interface types and are implemented as function modules
      • You can call the BAPI in the BOR using object-oriented method calls
      • You can make RFC calls to the function module on which the BAPI is based
    Active X C++ Class Lib Java Class Lib RFC
  • Application Link Enabling (ALE)
    • ALE (Application Link and Enabling) is SAP’s technology to support business processes across a distributed yet integrated environment
    • The IDoc is a SAP standard container/template
      • Used to exchange data between any two processes that understand the syntax and semantics, and between a SAP system and an external application
    • IDocs are used in SAP R/3 both by EDI and ALE
    • SAP provides standard tools for IDoc creation or enhancement to support custom interfaces
  • IDoc Screen
  • SAP R/3 External Interfaces -
    • GUI-based
      • May be volatile from one release to another; high maintenance may be required
    • BAPI-RFC
      • Safe and sure; one may call the method (BAPI) or the function (RFC) with the same consistent results
    • IDoc
      • EDI and ALE both use this vehicle. Very stable
    • Batch Input
      • Still has to obey formal SAP requirements. Very good for massive asynchronous data uploads
  • Integration Hot Points
    • Support of multiple API’s
    • Matching SAP’s metadata definitions for message brokerage
    • Future maintenance requirements (upward and downward release stability/compatibility)
  • Sybase Adapter for SAP R/3
    • Works with the Integration Brokers
    • Its components provide tools and functions that
      • Extract SAP R/3 metadata into NEONFormatter
      • Mitigate the asynchronous nature of MQSeries with the synchronous nature of IDocs/BAPIs/RFCs
      • Put the control of data transformation, enrichment, validation, mapping and routing in the hands of the end-user
    • Supports all the main dialog processes
      • ALE/IDocs, BAPI/RFC, DMI/Batch, ABAP Direct
  • Sybase Adapter for SAP R/3 : Architecture Sybase Integration Broker SAP IDoc BAPI RFC ABAP DMI Adapter ALE RFC Batch in Input file Adapter Manager SAP Meta data Formatter Meta-data Other Systems
  • Adapter Manager IDOC Management
  • Adapter Manager IDOC Management
  • Sybase Adapter for R/3 Summary
    • All major SAP interfaces are supported
    • SAP Certifications verifies the functionality
    • The user interface makes the integration task easy
    • No need for point to point legacy integration coding
    • Adapter Manager is a single point of control
    • Supports all SAP R/3 environments 3.1 and greater
  • Sybase - The Total Integration Platform Logistics Distributors Partners Suppliers Exchanges FIREWALL Enterprise Portal FIREWALL Process Server Business Process Accelerators Integration Brokers Adapters Enterprise Portal Back Office SAP Oracle PeopleSoft JDE Seibel Legacy Supply Chain i2 Manugistics Oracle SAP FIREWALL Open Business Interchange Wired Wireless Collaboration Self Service Sybase Interwoven Vignette IBM BEA
  • ERP Integration Questions? Rob Smith Pre-Sales Manager New Era of Networks North Europe [email_address]