1 / 204

FMS XML Class

May 18-19, 2002. FMS XML Class. Nauman Malik DFAS/XML Global. Outline. Business impetus Collaboration between DFAS and FMS Semantic alignment between Federal stakeholders w/ Treasury as data steward (Project 1) Reporting + Collaborative Components (Project 2) MAF XBRL

naava
Download Presentation

FMS XML Class

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. May 18-19, 2002 FMS XML Class Nauman Malik DFAS/XML Global

  2. Outline • Business impetus • Collaboration between DFAS and FMS • Semantic alignment between Federal stakeholders w/ Treasury as data steward • (Project 1) Reporting + Collaborative Components • (Project 2) MAF • XBRL • Technology vehicles (XML & Related Technologies) • Approach (Validation via registry, MAF transformation) • Tools (XML Spy, XSL Tester, Transform, Registry) • XML, XML Schema, XSLT • Conclusion • FMS should now have the understanding of the technology involved to begin semantic alignment (w/ DFAS & other partners)

  3. Business impetus (Audience: Business and Technical)

  4. Joint Treasury & DFAS Collaborative XML Strategy:Standards-based Data Interchange Among US Government Entities Test Project : Trial Balance Reports

  5. Purpose: To start the process for defining a sound financial data management strategy for the federal government.

  6. Example of Business Artifact / Collaborative Component United States Standard General Ledger Chart of Accounts - XML Schema <?xml version="1.0" encoding="UTF-8"?> <!-- Created by Nauman Malik, DFAS --> <xs:schema targetNamespace="http://www.fms.treas.gov/namespaces/SGLaccount" xmlns:sglac="http://www.fms.treas.gov/namespaces/SGLaccount" xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.2"> <xs:complexType name="SGLaccountType"> <xs:annotation> <xs:documentation>The datatypes for a general ledger account. Device that sums financial business events. This will provide the linkage to the accounting descriptions of various reporting entities. </xs:documentation> </xs:annotation> <xs:all> <xs:element name="BalanceCode" type="sglac:BalanceCodeType"/> <xs:element name="BalanceIndicatorCode" type="sglac:BalanceIndicatorCodeType"/> <xs:element name="BeginningCalendarDate" type="sglac:BeginningCalendarDateType"/> <xs:element name="Code" type="sglac:CodeType"/> <xs:element name="EndingCalendarDate" type="sglac:EndingCalendarDateType"/> <xs:element name="ID" type="sglac:IDtype"/> <xs:element name="JournalVoucherIndicatorCode" type="sglac:JournalVoucherIndicatorCodeType"/> <xs:element name="Name" type="sglac:NameType"/> <xs:element name="PostedIndicatorCode" type="sglac:PostedIndicatorCodeType"/> <xs:element name="Text" type="sglac:TextType"/> <xs:element name="FederalNonfederalCode" type="sglac:FederalNonfederalCodeType"/> <xs:element name="BudgetSubfunctionCode" type="sglac:BudgetSubfunctionCodeType"/> <xs:element name="CustodialNoncustodialCode" type="sglac:CustodialNoncustodialCodeType"/> <xs:element name="CapitalizedAcquisitionsCode" type="sglac:CapitalizedAcquisitionsCodeType"/> <xs:element name="TradingPartnerCode" type="sglac:TradingPartnerCodeType"/> <xs:element name="ExchangeNonexchangeCode" type="sglac:ExchangeNonexchangeCodeType"/> <xs:element name="Amount" type="sglac:AmountType"/> </xs:all> <xs:attribute name="uid" type="xs:string"/> </xs:complexType>

  7. Demonstrate Proof of Principle Demonstrate Capability for Deployment Build Core/ Reusable Components Phase 1 Phase 2 Phase 3 Test Project Trial Balance Reports

  8. Phase II : Implementation • Create XML-based instance documents (for example, balance sheets) by extracting data from an RDBMS and DDRS application. Phase III : Collaboration • Building & using Federal Government Financial Community’s collaborative business artifacts.

  9. FACTS I Reporting Environment (w/ collaborative components ) Components & schema Repository legend Notes Fund Group SGL Other CC’s XML Schema document inherits from XML instance document inherits from Non-XML data generator/ data store Reporting System/ DB FACTS I Report-Specific XML Schema XSLT Stylesheet Created, maintained, and provided by Treasury Final Output Extraction and conversion to XML Web Server validates reside on Stylesheet 1 Web Browser (HTML) Stylesheet 2 Acrobat Reader (PDF) FACTS I Report Stylesheet 3 PDA/Cellphone (WML) transformed by resides on Stylesheet 4 Excel Spreadsheet Web Server/ Registry reside on

  10. Treasury HTML Treasury PDF Treasury WAP/PDA ... Treasury XML-based reporting: DOD to Treasury DOD DDRS XML Schema Transform/ validate DFAS ACT Parser Treasury DB Valid Transform Reject / Return Invalid

  11. XML-based reporting: Treasury & its Trading Partners Integration Environment Treasury Department Repository / web server Schemas / components have access to Reporting Departments Transformations Display XML FACTS Report Data DoD Reporting System Optional validation before submission Validate and transform for DB storage Library of Congress Reporting System XML FACTS Report Extract from DB Transform Engine DB Transform Engine Dept of Agriculture Reporting System XML FACTS Report Transform to XML . . . XML FACTS Report intelligent querying Reject if non-conformant device of choice 13

  12. Trans-mission Upgrade (optional) Preferred Transfor-mation End- to-End Notes Registry & Out-briefing Phase 3.1 Phase 3.2 Phase 3.3 Phase 4 Phase 5

  13. DFAS Distributed to all reporting organizations MAF Template XSL MAF Filter XSL Edit XSL Template for appropriate DepartmentID values Treasury XSLT Process MAF XML MAF DFAS XML zipped Transform 2 Oracle SDK 1 MAF Buffer Application MAF Flow GET GET GET

  14. XBRL Specification V.2 Courtesy: David vun Kannon, KPMG LLP Specification Group Co-Chair

  15. Fundamental Goals of XBRL Transfer syntax for Financial Information Throughout the value chain Internal systems to Management Company to Regulator Company to Investor Company to Capital Market Archival representation of financial facts and concepts

  16. Technical Approach of XBRL XBRL is an XML language XBRL builds on other XML specifications XML Schema XML Namespaces XML Linking XBRL can be processed by standard XML tools DOM API XSLT

  17. Fundamental Design of XBRL Financial information is worthless without proper context. What is the meaning of “7”? The most important piece of context – What concept are we measuring. What does “operating income” mean? Whose definition of that concept? AICPA, IASB, SEC? Company specific?

  18. Fundamental Design of XBRL A bag of financial facts Financial facts are independent of each other. This is the XBRL “instance document”. A bag of financial concepts The set of definitions used by the facts. Concepts are interrelated in many ways. This is the XBRL “taxonomy document” One instance document usually uses several taxonomy documents.

  19. XML & Related Technologies (Audience: Technical and Business-Technical)

  20. Course Overview • XML • Information Modeling • XML Schema • XSLT

  21. XML • Introduction to XML • Applications of XML • XML & Related Technologies • XML Syntax

  22. Introduction to XML What is XML? What were the goals of its design?

  23. Summary Slide • What is XML? • XML - Labeling Data • XML - Organizing Data • Design Goals for XML

  24. What is XML? • eXtensible Markup Language • Formatted DATA - label and organize • Not a programming language

  25. Applications can't use unlabeled data efficiently: Applications CAN use LABELED data efficiently XML - Labeling Data car Camry Camry 4Runner suv 4Runner Corolla car Corolla

  26. XML - Organizing Data • Data is organized in a hierarchical tree

  27. Design Goals for XML • XML documents should be human-legible and reasonably clear. • XML documents shall be easy to create. • The design of XML shall be formal and concise. • Terseness in XML markup is of minimal importance

  28. Design Goals of XML con't • XML shall be compatible with SGML. • The number of optional features in XML is to be kept to the absolute minimum, ideally zero. • The XML design should be prepared quickly.

  29. Design Goals of XML con't • XML shall be straightforwardly usable over the Internet. • XML shall support a wide variety of applications • It shall be easy to write programs which process XML documents.

  30. Applications of XML What are some uses of XML? Business Case Scenarios

  31. Summary Slide • Data Mining • Content Reusability • Transformations • Application Integration • B2B • Value Proposition • Business Case Scenarios

  32. Data Mining • Querying for specific information • Extracting data according to the tag name (label) <car>Camry</car> car Camry

  33. Content Reusability Flat File (EDI) XML File … … DTM*002*20000928! PO1*AAA849*100! QTY*28*.500! AMT*FL*50.00*D! … … … … <Date>20000928</Date> <PO>100</PO> <Quantity>.500</Quantity> <Amount>50.00</Amount> … …

  34. Transformations • Filtered views (via searches) • File representations of data (ie PDF) • Browser viewable versions (multiple)

  35. Application Integration • Easy to learn / maintain • Human readable • Defined structure and hierarchy • Useful tools for building infrastructure and translating into proprietary systems • Open standard

  36. B2B • Custom Markup Languages can be created to address specific exchange needs • Conformance to the standard ensures interoperablility of data • Provides a common standard for integration into backend systems

  37. Value Proposition • Increased speed to market • Lower information exchange barrier • Fluid information exchange among trading partners • Streamlined business processes

  38. Business Case Scenarios Scenario 1: Business Partnerships

  39. Business Partnerships (before) Converters SAP Oracle Loan Processing Company People Soft Car Dealership SAP Banks

  40. Business Partnerships (leveraging XML) Interpreters SAP Oracle XML Loan Processing Company XML People Soft Car Dealership SAP Banks

  41. Business Partnerships (XML enhancing EDI) EDI S Region SAP Major Grocery Chain Headquarters N Region EDI 879 Fax Independent Outlet Major Distributor Email Independent Outlet Outlets Converters

  42. Business Partnerships (XML enhancing EDI) Interpreters S Region EDI N Region SAP Major Grocery Chain Headquarters EDI 879 XML Independent Outlet Browser Version Major Distributor Independent Outlet Browser Version Outlets

  43. Business Case Scenarios Scenario 2: Government Agency

  44. Content ReusabilityData Longevity Information Repository Inner Departmental Agency Government Agency Person with Query

  45. XML & Related Technologies What are the technologies surrounding XML?

  46. Summary Slide • Definition of Documentsand Structure • Processing and Transformation • Rendering XML • Linking and Querying XML

  47. Definition of Documentsand Structure XML Namespaces

  48. Definition of Documentsand Structure DTD XMLSchema

  49. Processing and Transformation SAX DOM

  50. Processing and Transformation XSLT

More Related