1 / 48

Business Documents – Concepts and Techniques

Business Documents – Concepts and Techniques. Ulrike Greiner, SAP. Course Structure. Introduction Business Document Standards Business Document Modelling Business Document Mapping. Introduction. Definition.

tybalt
Download Presentation

Business Documents – Concepts and Techniques

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. Business Documents – Concepts and Techniques Ulrike Greiner, SAP

  2. Course Structure • Introduction • Business Document Standards • Business Document Modelling • Business Document Mapping

  3. Introduction

  4. Definition • A business document is a set of information components that are interchanged as part of a business activity (Definition from ebXML). • Possible components are: • Information (data) • Meaning of that information (meta-data) • Presentation information (layout) • Links to other information components

  5. Information Contained v2 • Information in business documents can be of different types: • Structured: • e.g. XML documents or databases • Unstructured: • e.g. text files, Word documents, Emails, most Web pages • Semi-structured: • Web pages with known fields of content (annotations) Structured information: Unstructured information: <xml>…</xml>

  6. RETAILER SUPPLIER MANUFACTURER Business Example Business documents represent the information exchanged in cross-organisational business processes. Order Request for Quotation Quotation Order Conf. Request for Quotation Quotation Goal of this course: Show methods for efficient and easy management of business documents exchanged in a cross-organisational business process Order Conf. Order

  7. Questions

  8. Course Navigation Recommended next section: • Business Document Standards You can also continue with: • Business Document Modeling • Business Document Mapping

  9. Business Document Standards

  10. Classification Categories • Collaboration Agreement: • agree on a document standard and how to implement it • Collaboration: • exchange information and data between organisations, specified e.g. in protocols, or cross-organisational business processes • Business Process / Service Definition: • define organisation-internal business processes and business services • Information Definition: • define business documents and data models • Infrastructure Services: • specify infrastructure necessary to model and exchange business documents

  11. Classification of Standards Collaboration Agreement ebXML CPPA Impl. Guide Variant Problem Collaboration RosettaNet PIPs STEP EDI STAR OAGI WS-CDL Business Process / Service Def. ebXML BPSS WS-BPEL XPDL Information Def. RosettaNet Data Dictionary standard product attributes ebXML CCTS EDI STAR OAGI UML UBL Infrastructure Services W3C transport protocols (HTTP, SOAP, etc.) WSDL Discovery IEEE FIPA OGSA OGSI

  12. Selected Standards • Detailed description and analysis of the following standards: • ebXML CCTS • RosettaNet data dictionary and schemas • STEP • OAGI • DFDL Collaboration Agreement ebXML CPPA Impl. Guide Variant Problem Collaboration RosettaNet PIPs STEP EDI STAR OAGI WS-CDL Business Process / Service Def. ebXML BPSS WS-BPEL XPDL Information Def. RosettaNet Data Dictionary standard product attributes ebXML CCTS STAR OAGI EDI UML UBL Infrastructure Services W3C transport protocols (HTTP, SOAP, etc.) WSDL Discovery IEEE FIPA OGSA OGSI

  13. General information: Core Components Technical Specification (CCTS) / Part 8 of the ebXML Framework Defined and maintained by United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT) CCTS is fixed; extensions and modifications are performed by UN/CEFACT ebXML CCTS can be used in all industries CCTS does not provide implementation guidelines Repository: CCTS describes a repository structure that should be used to store CCTS-based business documents No information about repository interfaces is provided ebXML CCTS (1) Collaboration Agreement ebXML CPPA Impl. Guide Variant Problem Collaboration RosettaNet PIPs STEP EDI STAR OAGI WS-CDL Business Process / Service Def. ebXML BPSS WS-BPEL XPDL Information Def. RosettaNet Data Dictionary standard product attributes STAR OAGI ebXML CCTS EDI UML UBL Infrastructure Services W3C transport protocols (HTTP, SOAP, etc.) WSDL Discovery IEEE FIPA OGSA OGSI

  14. Business document modeling: Component-oriented approach to model business documents on the business level (i.e. business experts are involved in modelling) including different variants of one document No transformation to more technical representations is specified Business documents can be used for company-internal and –external communications Specifications are done in a semantically standardized syntax-neutral way Normative rules in CCTS allow for checking correctness of business documents Transformations / Mapping: CCTS defines a vocabulary for common concepts that are used in different business documents No specification provided for mapping CCTS-based documents to other formats ebXML CCTS (2) Collaboration Agreement ebXML CPPA Impl. Guide Variant Problem Collaboration RosettaNet PIPs STEP EDI STAR OAGI WS-CDL Business Process / Service Def. ebXML BPSS WS-BPEL XPDL Information Def. RosettaNet Data Dictionary standard product attributes STAR OAGI ebXML CCTS EDI UML UBL Infrastructure Services W3C transport protocols (HTTP, SOAP, etc.) WSDL Discovery IEEE FIPA OGSA OGSI

  15. General information: RosettaNet Business Dictionary (RNBD), RosettaNet Technical Dictionary (RNTD), RosettaNet Implementation Framework (RNIF) Mainly developed by industrial member organizations of RosettaNet Definitions follow the RosettaNet Standards Methodology (RSM) Initially targeted at high-tech industry, extended to other industries Provides excel-based tools to support implementation projects Repository: No specifications for a repository are provided RosettaNet (1) Collaboration Agreement ebXML CPPA Impl. Guide Variant Problem Collaboration RosettaNet PIPs STEP EDI STAR OAGI WS-CDL Business Process / Service Def. ebXML BPSS WS-BPEL XPDL Information Def. RosettaNet Data Dictionary standard product attributes ebXML CCTS STAR OAGI EDI UML UBL Infrastructure Services W3C transport protocols (HTTP, SOAP, etc.) WSDL Discovery IEEE FIPA OGSA OGSI

  16. Business document modeling: Component-oriented XML specifications for business documents on technical and execution level are provided Business documents can be used for company-external information exchange Variants of a document are supported through implementation guides describing which elements are generic and can be specialized to meet the specific needs of trading partners Software programs to test the validity of RosettaNet business documents Transformations / Mapping: RosettaNet provides dictionaries for both business terms and technical term that can be used to create documents. No specifications provided for mapping RosettaNet documents to other formats RosettaNet (2) Collaboration Agreement ebXML CPPA Impl. Guide Variant Problem Collaboration RosettaNet PIPs STEP EDI STAR OAGI WS-CDL Business Process / Service Def. ebXML BPSS WS-BPEL XPDL Information Def. RosettaNet Data Dictionary standard product attributes ebXML CCTS STAR OAGI EDI UML UBL Infrastructure Services W3C transport protocols (HTTP, SOAP, etc.) WSDL Discovery IEEE FIPA OGSA OGSI

  17. General information: Standard for the Exchange of Product Model Data Defined by TC184/SC4 at ISO STEP is fixed, extensions and modifications are performed by TC184/SC4 STEP is used in manufacturing industry Provides implementation guidelines for business documents Repository: ISO 13584 specifies a repository structure, the Parts Library Structure Also specifies how documents should be stored and retrieved STEP (1) Collaboration Agreement ebXML CPPA Impl. Guide Variant Problem Collaboration RosettaNet PIPs STEP EDI STAR OAGI WS-CDL Business Process / Service Def. ebXML BPSS WS-BPEL XPDL Information Def. RosettaNet Data Dictionary standard product attributes ebXML CCTS STAR OAGI EDI UML UBL Infrastructure Services W3C transport protocols (HTTP, SOAP, etc.) WSDL Discovery IEEE FIPA OGSA OGSI

  18. Business document modeling: Component-oriented approach to specify technical level business documents for internal as well as external communication Business documents are specified in EXPRESS Variants of documents can be specified using specialization and generalization of entities EXPRESS to XML transformations are described to generate execution level document representations Validation process for STEP implementations supported by conformance testing methodology and framework Transformations / Mapping: STEP defines a vocabulary / data dictionary for common concepts No specifications provided for mapping STEP documents to other formats STEP (2) Collaboration Agreement ebXML CPPA Impl. Guide Variant Problem Collaboration RosettaNet PIPs STEP EDI STAR OAGI WS-CDL Business Process / Service Def. ebXML BPSS WS-BPEL XPDL Information Def. RosettaNet Data Dictionary standard product attributes ebXML CCTS STAR OAGI EDI UML UBL Infrastructure Services W3C transport protocols (HTTP, SOAP, etc.) WSDL Discovery IEEE FIPA OGSA OGSI

  19. General information: OAGIS = OAG Integration Standard Defined by OAGi = Open Applications Group, inc. plus, AIAG (Automotive Industry Action Group), AAIA (Automotive Aftermarket Industry Association ) Standard is defined in ISO 10303 documents and can be extended or modified following a dedicated procedure Standard is open for all industries OAGi provides implementation guidelines and support services Repository: OAGi does not describe a repository structure Business documents are usually stored on standard but structured file systems OAGI (1) Collaboration Agreement ebXML CPPA Impl. Guide Variant Problem Collaboration RosettaNet PIPs STEP EDI STAR OAGI WS-CDL Business Process / Service Def. ebXML BPSS WS-BPEL XPDL Information Def. RosettaNet Data Dictionary standard product attributes ebXML CCTS STAR EDI OAGI UML UBL Infrastructure Services W3C transport protocols (HTTP, SOAP, etc.) WSDL Discovery IEEE FIPA OGSA OGSI

  20. Business document modeling: Component-oriented specification of company-internal and –external business documents on technical and execution level Business documents are specified using XML, XSD No explicit support for handling variants of documents XML schemas available to check correctness of business documents Transformations / Mapping: No specifications provided for mapping OAG business documents to other formats OAGI (2) Collaboration Agreement ebXML CPPA Impl. Guide Variant Problem Collaboration RosettaNet PIPs STEP EDI STAR OAGI WS-CDL Business Process / Service Def. ebXML BPSS WS-BPEL XPDL Information Def. RosettaNet Data Dictionary standard product attributes ebXML CCTS STAR EDI OAGI UML UBL Infrastructure Services W3C transport protocols (HTTP, SOAP, etc.) WSDL Discovery IEEE FIPA OGSA OGSI

  21. Format Description for Non-XML data Need for a mechanism bringing the benefits of formal schema definition to legacy or other non-XML formats. Description, rather than prescription, of formats, to allow use with existing technology alongside definition of new Uses in integration of new and legacy systems, creation of high performance formats, and mapping and transformation tooling. Standard for use in implementing mapping tools DFDL – Data Format Description Language Something fulfilling this role already exists in many proprietary systems (e.g. Websphere Message Broker, Microsoft Biztalk) Common way of describing physical format desirable for interoperability DFDL Working Group within Open Grid Forum developing specification First revision to be available in near future DFDL (1) – Why and Who

  22. Schema based approach XML schema used to describe logical data format Annotations contain physical format information e.g. <xs:sequence dfdl:separator=","> <xs:element name="y" type="double" dfdl:initiator="baseQ" dfdl:tagSeparator="=" /> Use of XML Schema gives several benefits Existing body of tooling Can apply prior knowledge Useful document model and implementation libraries Implementation and status Provided properties should support description of a wide variety of formats Support for fixed length formats, binary and text encodings, field delimeters Support for ‘variables‘ e.g. field specifying length of another Parsers and Serializers can make use of physical annotations to read and write data in the described format Prototype making use of the current version of specification available (within Virtual XML Framework from IBM) DFDL (2) – What and How

  23. Questions

  24. Course Navigation Recommended next section: • Business Document Modeling You can also continue with: • Business Document Mapping

  25. Business Document Modelling

  26. Modeling Requirements • Requirements for modeling of business document: • Re-use of model types that are modeled once and can then be used in different document models • Model representation targeted at business experts • Semi-automatic transformation to technical specification • Support for handling variants of business documents: • Share most of their data fields • Differ in a limited number of data fields that depend on the context in which the document is used • Example: a purchase order that differs slightly if used in different European countries

  27. Modeling Approach • Based on Core Components Technical Specification (CCTS) • Component-based thus supporting re-use • Graphical representation to support business experts • Export functionality to create e.g. XML representations • Provides the concept of a business context: • Defines a specific context in which a document is used • Can be assigned to mark a particular variant of a business document

  28. Types of Models • Primitive Type Model • Context Category Model • Code List Model • Core Component Type Model • Core Component Model • Business Context Model • Data Type Model • Business Information Entity Model

  29. Relationships between Models Business Information Entity Model Data Type Model Business Context Model Core Component Model Core Component Type Model Code List Model Context Category Model Primitive Type Model

  30. Primitive Type Model • Models all primitive types • Examples: string, integer, URL • Represented by nodes • Primitive type nodes can be connected by edges: • Means that primitive type x can be substituted by primitive type x • e.g. a URL can be substituted by a string Primitive type integer: Primitive types string and URL:

  31. Core Component Type Model • Specifies the data fields of business documents • Groups multiple data fields each represented by a primitive type • exactly 1 content component: primary data field with the actual value • 1 to n supplementary components: describe the value • Examples: Price, Text Core Component Type Price:

  32. Core Component Model Association Core Component • Represents a template of a business document: • contains all possible data fields • Examples: order, quotation • Aggregate Core Component (ACC) aggregates core components • Association Core Components (ASCC) connects two ACCs • Basic Core Component (BCC) connects ACC with CCT • Property Terms specify the child CC Aggregate Core Component Core Component Type Basic Core Component

  33. Data Type Model • Represent data fields of a business document • similar to CCTs but more restrictive • Is based on a CCT or on a primitive type model • Specifies a Data Type Restriction (DTR) for each content and supplementary component of a CCT • limits the possible values • Several Data Types can be based on the same CCT Data Type A7_Number (based on CCT Number):

  34. Context Category Model • Classify the business circumstances, which define a business context • Examples: industry, geopolitical • Represented by nodes • Edges define a hierarchy of categories Context Category Geopolitical with two sub-categories:

  35. Code List Model Code list authority ISO and four code lists defined by ISO: • Provide values for business contexts • Restrict the values of data types • Example: country code • Represented by nodes • Code values of a code list are specified textually as an attribute value • Code list authority: organization that wants to define code lists (e.g. ISO)

  36. Business Context Model • Describes the business circumstances in which a variant of a business document is used • Specified by an enumeration of context values • Context values are code values of a code list • All necessary code lists are put into a business context node • All required code values are selected • Examples: geopolitical region Business context CountryContext: Selected value from code list:

  37. Business Information Entity Model • Represents a concrete business document used in a cross-organizational business process • Is a variant of a Core Component • Is created in three steps: • Assign a business context • Select the required data field from the data fields of the core component • Add a qualifier • Examples: quotation

  38. Questions

  39. Course Navigation Recommended next section: • Business Document Mapping You can also continue with: • Business Document Standards

  40. Mapping Business Documents

  41. Requester 1 Service Doc 2 Service Doc 1 . . . Requester n MAP Server Mapping Requirement • Requirement for document mapping • Business processes and services are developed by different groups and use different interfaces. • Standards (ebXML, RosettaNet, etc,) are too complicated for applications to implement • Document mapping bridges between requester‘s service definition and provider‘s service definition.

  42. Automatic matching Map Generator Source Schema Target Schema save conforms to Maps conforms to Transformation generator generate Runtime Transformation Source Target XQuery, XSLT, Java, proprietary Mapping Architecture (1) • A mapping generator • An optional automatic map generator • A transformation generator • A runtime that executes the transformation

  43. Mapping Architecture (2) • A mapping generator • Is usually a graphical component that is used to define the relationship between the source and target schema. • An optional automatic map generator • Automatically populates mapping generator based on computed similarities between source and target • A transformation generator • Generates the runtime instantiation of the map in the target mapping language. For example XSLT, XQuery, Java, SQL • A runtime that executes the transformation against business documents.

  44. Automatic Map Generator • Automatically discovers mappings between elements and attributes in the source and target schema using • Examples of source and target documents (Instance level matching) • Names and structure defined in the schema only(schema level matching) Source Target DeliveryAddress CustomerAdress AddrLine1 AddrLine1 City City State State

  45. Schema Level Matching • Schema level matching can use a number of matching algorithms or combination of algorithms • Lexical matcher looks for schema elements with equal or similar names • A thesaurus matcher makes use of an external non-domain specific thesaurus to find common synonyms and hyponyms • A type matcher makes uses of the simple and complex types of the elements • A structure matcher looks for similar structures and sub-structures within the source and target • An ontology matcher makes use of an external ontology which provides a domain specific vocabulary

  46. Source Schema Target Schema PartNumber subClassOf EAN 8 EANCode type type subClassOf EAN 13 UPC Example See ontology on next foil Thesaurus matching Ontology matching Lexical matching

  47. Due Date PartNumber subClassOf EquivalentClass type EAN 8 EANCode Delivery Date type subClassOf EAN 13 UPC NumberOfItems EquivalentClass Quantity Ontology

  48. Questions

More Related