1 / 62

XML and XBRL-compliant SAP R/3 Systems

XML and XBRL-compliant SAP R/3 Systems. Paul Sheldon Foote California State University, Fullerton SAP Congress, February 2001. Paul Sheldon Foote Department of Accounting California State University, Fullerton PO Box 6848 Fullerton, CA 92834-6848 (714) 278-2682 pfoote@fullerton.edu

vinaya
Download Presentation

XML and XBRL-compliant SAP R/3 Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. XML and XBRL-compliant SAP R/3 Systems Paul Sheldon Foote California State University, Fullerton SAP Congress, February 2001

  2. Paul Sheldon Foote Department of Accounting California State University, Fullerton PO Box 6848 Fullerton, CA 92834-6848 (714) 278-2682 pfoote@fullerton.edu http://business.fullerton.edu/pfoote http://business.fullerton.edu/sap Paul Sheldon Foote

  3. Focus • Identify how SAP and third party vendors are implementing XML and XBRL-compliant systems • Suggest research opportunities Paul Sheldon Foote

  4. XML Paul Sheldon Foote

  5. XML • Extensible Markup Language • In 1999, SAP added XML as a format for data interchange across its SAP Business Framework • XML, a meta language, provides developers with a standard way to describe data containers, enabling exchanges with non-SAP applications Paul Sheldon Foote

  6. XML 2 • Eliminates the need for custom translation code • Capable of accessing SAP’s Business APIs (BAPIs) • SAP will enable all of its major interfaces with XML • SAP Business-to-Business Procurement: example of product using XML Paul Sheldon Foote

  7. XML 3 • SAP’s goal is to make all IDOCS available in XML format • With IDOCS in XML format, it will be easier to integrate SAP R/3 with legacy and with non-SAP systems Paul Sheldon Foote

  8. SAP’s XML SEC filing www.secinfo.com -<filer>-<company-data><conformed-name>SAP AKTIENGESELLSCHAFT SYSTEMS APPLICATIONS PRODUCTS IN DATA</conformed-name><cik>0001000184</cik><assigned-sic>7372</assigned-sic><irs-number>000000000</irs-number><state-of-incorporation>I8</state-of-incorporation><fiscal-year-end>1231</fiscal-year-end> Paul Sheldon Foote

  9. IBM’s Visual Age for Java • SAP has agreed to use IBM’s Visual Age for Java development tool for implementing business-to-business data interchange • This will provide JavaBean interfaces into SAP’s BAPIs • Server-side Java and XML integration for SAP R/3 systems Paul Sheldon Foote

  10. IBM’s Visual Age for Java 2 • With SAP’s BAPIs available through IBM Component Broker middleware, many tool vendors will be able to connect to SAP R/3 systems via open rather than proprietary systems Paul Sheldon Foote

  11. XBRL Paul Sheldon Foote

  12. XBRL • Extensible Business Reporting Language • Custom markup language based upon XML • Being added to accounting and financial reporting software Paul Sheldon Foote

  13. XBRL 2 • XBRL-compliant software automatically and transparently translates numbers and words for viewing of segments in Web browsers, spreadsheets, and in other application software Paul Sheldon Foote

  14. XBRL 3 • Faster distribution of financial information • Eliminate rewrites of financial reports • Faster and better Internet searches • Find desired XBRL-tagged data, not thousands of useless “hits” • Drill down • Minimize reentering data Paul Sheldon Foote

  15. XBRL Components • XBRL taxonomy • Database tables and maps • Customized XBRL tags • XBRL instance documents Paul Sheldon Foote

  16. XBRL Security • Security features are not built into XBRL Paul Sheldon Foote

  17. XBRL Steering Committee • Not-for-profit corporation started by the American Institute of Certified Public Accountants (AICPA) • SAP is a member • XBRL specifications • http://www.xbrl.org Paul Sheldon Foote

  18. XBRL Taxonomy Viewer • XBRL Taxonomy Builder • XBRL Instance Validator • XBRL Instance Creator • XBRL Extractor • XBRL DOM • A DLL Paul Sheldon Foote

  19. XBRL Lists and Enumeration Services • Training • XBRL Taxonomy Creation • XBRL Financial Statement Creation • XBRL Style Sheet Creation • Financial Information Conversion and Financial Reporting Paul Sheldon Foote

  20. http://xbrlsolutions.com • Web site includes additional documentation authored by Charles Hoffman Paul Sheldon Foote

  21. SAP's Internal Solutions Paul Sheldon Foote

  22. SAP R/3 Before the Internet • Within a single firm, SAP R/3 ended the problem of “islands of information.” Paul Sheldon Foote

  23. SAP Business Framework • SAP supports XML as a data format for data interchange across the entire SAP Business Framework • Support of XML enables SAP R/3 to use the Internet to pass messages to receiving applications having no prior knowledge of the data formats contained in the messages Paul Sheldon Foote

  24. SAP’s Business APIs (BAPIs) • XML enables access to SAP’s Business APIs (BAPIs) without custom translation code Paul Sheldon Foote

  25. SAP's External Solutions Paul Sheldon Foote

  26. SAP Business-to-Business Procurement • Web-based “requisition-order-payment” solution • Use as part of R/3 or as a stand-alone component interfacing to R/3 or to legacy systems • Little or no training to use Web front end • Real-time supplier integration Paul Sheldon Foote

  27. SAP OLAP Consolidation • SAP has no current plans to build XBRL functionality into applications • Instead, all XBRL-tagged data will be collected in SAP’s Business Information Warehouse (BW) for use by applications • XBRL support will be in SAP’s OLAP Consolidation Tool (ConsTool), a tool built into SAP-BW Paul Sheldon Foote

  28. SAP’s XBRL Templates(a future possibility?) • Reporting • Financial Consolidation • Modeling • Simulation • Planning • Budgeting Paul Sheldon Foote

  29. Third Party Solutions Paul Sheldon Foote

  30. Java and XML-Based wireless applications for SAP R/3 • EPIConnect: Warehouse Edition • Developed using Epic Data’s eXpresso development environment (XML and Java technologies) • Operating system independence for servers and mobile devices Paul Sheldon Foote

  31. Development for all major server operating systems, including: Windows, Unix, Linux • Development for all major mobile device operating systems, including: DOS, Windows CE, Palm Paul Sheldon Foote

  32. Automatic data collection (ADC) solutions for SAP R/3 customer installations • EPIConnect controls the flow of material from the receiving dock to the shipping bay • Workers with no SAP R/3 training can enter data into SAP R/3 Paul Sheldon Foote

  33. Intermec Technologies Corporation • RF Hand Held Data Collection Computer used by Epic Data • Weighs under 1 pound • European and Asian character sets available Paul Sheldon Foote

  34. Intermec Technologies Corporation 2 • Send and receive real time data with 2.4 GHz radio • Develop applications with Microsoft C/C++ Paul Sheldon Foote

  35. Intermec Technologies Corporation 3 • Configurations • Terminal emulation • Client/server • Web-enabled for integration into HTML applications Paul Sheldon Foote

  36. Intermec Technologies Corporation 4 • Data collection applications • Time & Attendance • Shipping/Receiving • Picking and Pricing Paul Sheldon Foote

  37. SAP R/3 Cases Paul Sheldon Foote

  38. “We want to put ERP into every facet of our business from development through manufacturing to the maintenance, repair, and overhaul market.” --Mike Paul, Pratt &Whitney ERP director Paul Sheldon Foote

  39. SAP host computer in Connecticut • Epic Data’s ADC server in Singapore • Intermec hand held • Data travels 14,000 miles each way in less than 2 seconds Paul Sheldon Foote

  40. Aircraft engines worth more than $5 million can be assembled from more than 2,000 unique part numbers in 8 days, instead of 6 weeks • Single instance of SAP R/3 Paul Sheldon Foote

  41. All worldwide data now resides in one location • Over 20 – 30 years for each engine have: • How part manufactured • Tests performed • Quality issues Paul Sheldon Foote

  42. Manufacturer of high-quality plumbing fixtures • Fine furniture • Cabinetry and tile • Small engines and generators Paul Sheldon Foote

  43. SAP R/3 • Epic Data for automated data collection for SAP R/3 • Intermec Antares hand-held terminals Paul Sheldon Foote

  44. At month-end processing, pull data from SAP via Epic Data system to work offline with Intermec terminals while SAP R/3 is unavailable • Can continue to pack and close shipments Paul Sheldon Foote

  45. Research Opportunities Paul Sheldon Foote

  46. Continuous Auditing • Real-time processing of transactions • Real-time auditing Paul Sheldon Foote

  47. Continuous Auditing 2 • Reduce time for existing audits? • Increase audits in same amount of time? • Reduce insurance costs for liabilities of CPA firms? • Less overtime to meet reporting deadlines? Paul Sheldon Foote

  48. Value Added Services • Direct communication to stakeholders • Shareholders • Analysts • Investors • Employees • General information on Web sites • Regulatory reporting (SEC) • Tax reporting (IRS) Paul Sheldon Foote

  49. mySAP.com Internet-Business Framework • Open Internet standards (such as XML and HTTP) combined with SAP R/3’s scalable, high-performance architecture • SAP’s WebFlow technology for business communities is based upon XML-enabled Business Objects • Information exchange between companies via XML messages Paul Sheldon Foote

  50. mySAP.com Marketplace • Instead of using independent buying and selling systems, companies may purchase or use mySAP.com Marketplace • An example of a live marketplace using mySAP.com Marketplace is http://www.neoforma.com Paul Sheldon Foote

More Related