DataXstream ALE and IDOC Leveraging

  • View
    7

  • Download
    5

Embed Size (px)

DESCRIPTION

sap le

Text of DataXstream ALE and IDOC Leveraging

  • Successfully Leverage ALE and IDocs for New Application Integration

    Thomas Nittmann, Timothy YatesDataxstream, LLC

  • 2What Well Cover

    z Understanding the SAP product offeringz Following the evolution of SAP integration technologyz Examining ALE/IDOC interfacing technologyz Reviewing SAP product integration scenarios z Using ALE/IDocs

    X Application of technologyX Cool tools

    z Applying ALE/IDOCS with R/3 and mySAP z 7 key points to take homez Questions and answers

  • 3Understanding SAP Product Offering R/3

    z SAP R/3: enterprise resource planningX Provides a traditional set of ERP transactional applicationsX Applications include finance, controlling, materials management, etcX OLTP (On line transactional processing) systems

    } Supports a business day-to-day activities} High update rate} Simple queries} Typically measured in GB

  • 4Understanding SAP Product Offering mySAP

    z Re-branding of SAP into a provider of e-business solutions and services.X Collaboration, integration and empowermentX OLAP (on-line analytical processing) systems

    } Analyzes operational data} Low update rate} Complex queries} Usually measured in GB or TB} A strategic business decision (high rewards, but difficult to implement)

  • 5Understanding SAP Product Offering- R/3 and mySAP

  • 6What Well Cover

    z Understanding the SAP Product Offeringz Following the Evolution of SAP Integration

    Technologyz Examining ALE/IDOC Interfacing Technologyz Reviewing SAP Product Integration Scenarios z Using ALE/IDOCs

    z Application of Technologyz Cool Tools

    z Applying ALE/IDOCS with R/3 and mySAP z 7 Key Points to Take Homez Questions and Answers

  • 7Following The Evolution of SAP Integration Technology

    1992

    1993

    1994

    1995

    1996

    1997

    1998

    1999

    2000

    2001

    2002

  • 8What Well Cover

    z Understanding the SAP Product Offeringz Following the Evolution of SAP Integration

    Technologyz Examining ALE/IDOC Interfacing Technologyz Reviewing SAP Product Integration Scenarios z Using ALE/IDOCs

    z Application of Technologyz Cool Tools

    z Applying ALE/IDOCS with R/3 and mySAP z 7 Key Points to Take Homez Questions and Answers

  • 9Examining ALE/IDOC Interfacing Technology

    z Files, IDocsz ALE, tRFCz BAPIsz Plugins, qRFC

  • 10

    ALE/IDOC Interfacing Technology - File / IDOC

    Key Features:z EDI technology originally

    based on file transfer.z IDocs can be written to files

    and transferred via standard file transfer protocols (FTP, HTTP, etc) for processing on other systems.

    z Requires some form of job scheduling to implement.

    z File interface provides minimal performance overhead when transferring large volumes of data

    Common Issues:z Most issues with file

    interfaces are related to file permissions, file ownership and character conversions moving between platforms.

  • 11

    ALE/IDOC Interfacing Technology ALE

    Key Features: z Asynchronous communication

    between system via IDocs.z Message types (Business

    Function), IDocs (Data Container)z Leverages a transactional RFC

    (tRFC) to guarantee message delivery between systems.

    z Requires some form of job scheduling: processes controlled via background jobs.

    z Content based modeling tools, data transformations and change tracking.

    Common Issues:z Added Overhead of tRFC and

    Data Format (1000 Byte Data Records)

    z Most issues with ALE interfaces are application\configuration related or with RFC user ID permissions.

  • 12

    ALE/IDOC Interfacing Technology tRFC

    (1) Send (3) Inbound_IDOC_Asynchronous (4.X)Inbound_IDOC_Process (3.X)

  • 13

    ALE/IDOC Interfacing Technology BAPIs

    Key Features:z Leverages BOR (Business

    Object Repository) - methodsz Can be used for synchronous

    or asynchronous data transferz Most BAPIs are direct input

    methods (i.e. should be faster). Be sure to test!

    z Open to non-SAP systemsz Uses content-based data

    models, transformations and supports a number of change tracking options

    Common Issuesz Similar issues to ALE, field

    conversion routines (screen fields versus table fields)

    z Note: In 4.X MOST BAPIS require the commit work to be executed by the calling program.

    GOTCHA!

  • 14

    ALE Interfacing Technology Plugins

    Key Features:z Standard interfaces for tightly

    coupling SAP R/3 and mySAP products

    z Leverages a variety of ALE technologies such as change pointers and tRFC buffers

    z Incorporates the use of new BAPIs and BTEs

    z Supports content-based routing via Variant configuration during model generation (APO CIF Interface)

    z Uses qRFCs to control dependencies of data object and ensure FIFO processing

    Common Issues:z Performance issues with BTEs

  • 15

    What Well Cover

    z Understanding the SAP Product Offeringz Following the Evolution of SAP Integration

    Technologyz Examining ALE/IDOC Interfacing Technologyz Reviewing SAP Product Integration Scenarios z Using ALE/IDOCsz Application of Technologyz Cool Tools

    z Applying ALE/IDOCS with R/3 and mySAP z 7 Key Points to Take Homez Questions and Answers

  • 16

    Reviewing SAP Product Integration Scenarios

    z R/3 to R/3z R/3 to APOz R/3 to BWz mySAP to mySAPz R/3 to Non-SAP Systems

    X ALE/BAPI/IDocs

  • 17

    Reviewing SAP Integration Scenarios R/3 to R/3

    z Master Dataz Transactional Data

    X Central HRX Central FIX Distributed LogisticsX Many more SAP-provided scenarios

    z Newer ScenariosX Project Systems WBS ElementsX Bank Distribution (BAPI)

    GOTCHA!Transactional scenarios often require enhancements and/or modifications, e.g. reconciliation process

  • 18

    Reviewing SAP Integration Scenarios R/3 to APO

    z Near Real Time Data Transfer Possible

    z Data transfer primarily based on plug-ins, qRFC based

    Quota ArrangementsQuota Arrangements

    No EquivalentTransportation Lanes

    Various objectsPlantsVendor MastersPlants set up as distribution centers

    Customer Masters

    Location MastersPlant LocationsSupplier LocationsDistribution Center LocationsCustomer Locations

    Production VersionsPPM

    Work CenterResource Master

    Material MasterProduct Master

    R/3APO

  • 19

    Reviewing SAP Integration Scenarios R/3 to BW

    z Data Warehouse Technology z Original version of BW used IDocsz Current data transfer based on plug-Ins (extractors) z IDoc data transfer is obsolete and replaced by

    X PSA: Persistent Staging AreaX ODS: Operational Data Store

  • 20

    Reviewing SAP Integration Scenarios between mySAP Components

    z Data transfer between mySAP components, e.g.X CRM needs ATP check from APOX APO and BW heavily integrated

    } Data Marts} InfoCubes} Livecache

    z Most data transfer between mySAP components is based on plug-ins

    z SAP moving towards XML format for future integration

    z ALE/IDoc technology used in places where appropriate, i.e. data may be structured in IDoc format and posted via ALE function module but IDoc is never created

  • 21

    What Well Cover

    z Understanding the SAP Product Offeringz Following the Evolution of SAP Integration

    Technologyz Examining ALE/IDOC Interfacing Technologyz Reviewing SAP Product Integration Scenariosz Using ALE/IDOCs

    X Application of TechnologyX Cool Tools

    z Applying ALE/IDOCS with R/3 and mySAP z 7 Key Points to Take Homez Questions and Answers

  • 22

    Using ALE/IDOCs Application of Technology

    z Master Data Reference Serverz Refreshing test and development with ALE z EAI integration using ALE

    X Best-of-breed architectureX Hub-and-spoke architecture

    z General ALE (tips and tricks)

  • 23

    Master Data Reference Server (Concept)

    z Using SAP R/3 as a single point for storage and maintenance of master data, common code and configuration for enterprise.

    Building Block

  • 24

    Master Data Reference Server (Concept)

    z Examples of Master Data elements include:X Chart of Accounts (GLMAST), X Cost Centers (COSMAS)X Material Master (MATMAS)X Vendor Master (CREMAS)X Search for more messages w/ transaction BALM and WE81

    z Examples of common code customer reports, system maintenance jobs, custom interfaces, etc.

    z Examples of common configuration company codes, sales areas, customer and vendor groups, material types, etc.

    z Can be implemented in conjunction with other SAP functionality, or independently.

  • 25

    Master Data Reference Servers (Example)

  • 26

    Master Data Reference Servers (Features)

    z Distribution of data is controlled by customer distribution model. Modeling allows for content-based routing rules and filtering.

    z Routing and filtering can also be achieved by using characteristic and classification system.

    z Changes are tracked via change pointers and data can be transformed using conversion rules.

    z SAP master data is structured in normalized maintenance views based on organizational structure. Therefore, it allows for centralization of certain master data elements and distributed maintenance of other data elements.

  • 27

    Master Data Reference Servers (Benefits)

    z Creates a central repository for all master data within an organization.

    z Reduces master data maintenance and conversion activities by eliminating redundant maintenance activities.

    z Reduces confusion and mistakes when working across inter-organization boundaries and with