WO2017021186A1 - A computerized database management system - Google Patents

A computerized database management system Download PDF

Info

Publication number
WO2017021186A1
WO2017021186A1 PCT/EP2016/067640 EP2016067640W WO2017021186A1 WO 2017021186 A1 WO2017021186 A1 WO 2017021186A1 EP 2016067640 W EP2016067640 W EP 2016067640W WO 2017021186 A1 WO2017021186 A1 WO 2017021186A1
Authority
WO
WIPO (PCT)
Prior art keywords
management system
database management
data
computerized
format
Prior art date
Application number
PCT/EP2016/067640
Other languages
French (fr)
Inventor
Adri R. VAN GAAL
Richard D. PRICE
Joris VAN HALL
Original Assignee
Philip Morris Products S.A.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Philip Morris Products S.A. filed Critical Philip Morris Products S.A.
Publication of WO2017021186A1 publication Critical patent/WO2017021186A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25Integrating or interfacing systems involving database management systems
    • G06F16/254Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25Integrating or interfacing systems involving database management systems
    • G06F16/258Data format conversion from or to a database
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Definitions

  • the present invention relates to a computerized database management system.
  • Enterprise resource planning (ERP) platforms such as SAP ERP of SAP SE, Weinheim, Barden-Wurttemberg, Germany are well known and extensively used.
  • ERPs are good for transaction data.
  • Transaction data is data describing an event typically with a time dimension and a numerical value that refers to one or more objects (the reference data). Examples of transaction data are invoices or payment information.
  • SAP ERP platform has multiple entry points through which users can enter data into the SAP ERP platform with no defined ownership. Because of this, in SAP ERP platforms, there is no control on the creation or maintenance of master data.
  • Master data is a single source of basic business data or common data about business-critical entities such as products, suppliers and customers. It is important that an organization does not use multiple inconsistent versions of master data in different operating locations as this can lead to problems. For example, an organization with many factories may keep details of the parts stored at each of these factories on an ERP platform. If another factory of the same organization wishes to obtain a particular part, it may not be indicated on the ERP platform that such a part is available from another factory in the same organization or there may be misleading information that the part is available in the organization. This is because the multiple entry point ERP platforms may not be up-to-date or data may be duplicated across ERP platforms. This problem is particularly great in large organizations in particular large multinational enterprises with a requirement for high volumes of specialist spare parts for their organization.
  • these organizations may try to obtain a specialist part from outside their organization which cannot be obtained quickly as they are perhaps made to order when the required part could, in theory, be obtained much more quickly from another factory within the same organization.
  • they may try to obtain the part from another factory within the organization only to find that, in fact, the part is not available and leading to a delay in trying to source the part elsewhere. In conclusion, it is difficult and unreliable to find a relevant part.
  • Master database management systems are known. They are effective at managing master data as they can, for example, remove duplicate files and include rules to remove incorrect data. While master database management systems are good at managing master data, they provide data in a different format to ERPs.
  • a computerized database management system or database management system is a collection of computer programs that enables the storing of information in a database, the modification of information in the database and the extraction of information from the database.
  • the computerized database management system includes a computerized master database management system; a plurality of ERP platforms, such as SAP ERP platforms; and a processing intermediary computer between the master database management system and the plurality of ERP platforms.
  • the computerized master database management system manages master data in a master database in a first format, such as XML.
  • XML is a markup language that defines a set of rules for encoding documents in a format which is both human-readable and machine- readable.
  • the ERP platforms manage data in a second format compatible with the ERP platform.
  • the processing intermediary computer system converts data from the first format to the second format and provides data in the second format from the master database management system to the plurality of enterprise resource planning platforms and converts data from the second format to the first format and provides data in the first format from the enterprise resource planning platforms to the computerized master database management system.
  • data in the database managed by the computerized database management system is up-to-date and reliable. It is quick to update data in the database managed by the computerized database management system. It is quick to access data in the database managed by the computerized database management system. This is because the computerized database management system provides a single entry point for data and it allows for control on the creation and maintenance of master data.
  • a computerized database management system comprising: a computerized master database management system for managing master data in a master database in a first format; a plurality of enterprise resource planning platforms for managing data in a second format; and a processing intermediary computer system between the master database management system and the plurality of enterprise resource planning platforms that converts data from the first format to the second format and provides data in the second format from the master database management system to the plurality of enterprise resource planning platforms and converts data from the second format to the first format and provides data in the first format from the enterprise resource planning platforms to the computerized master database management system.
  • This arrangement provides a technical solution to the technical problem of quickly providing reliable data. This arrangement is computationally efficient.
  • the computerized database management system may be configured such that only new data added to a master database managed by the computerized master database management system is sent to at least one of the plurality of enterprise resource planning platforms via the processing intermediary computer system. As a result, the system has quick response times.
  • a confirmation indication may be sent from the at least one of the plurality of enterprise resource planning platforms to the master database management system via the processing intermediary computer system when and only when the or each of the at least one of the plurality of enterprise resource planning platforms has been updated with new data. As a result, there is an indication that the master database is up-to-date.
  • the first format may comprise XML.
  • the plurality of enterprise resource planning platforms may comprise SAP ERP platforms.
  • the computerized database management system may be configured such that it cannot instruct data on the plurality of enterprise resource planning platforms to be overwritten. As a result, the data is reliable and the system quick.
  • the computerized database management system may comprise indications of relationships between different master data in the master database. ERPs cannot provide for this and it allows data related to equivalent elements (such as spare parts) otherwise identified in different ways to be recognised.
  • the master data may comprise parts data.
  • the computerized database management system characterises master data into libraries each with at least one common characteristic. This allows for quick and reliable searching of the data.
  • Master data in the master database may be configured to be searched by entering terms into the computerized master database management system and wherein data in the master database identified by predetermined terms is prioritised to be found above other data in the master database identified by other terms. This provides a more focussed and therefore reliable search.
  • the plurality of enterprise resource planning platforms may each act as a slave to the computerized master database management system. In this way, there is a single entry point for data, which provides reliable data.
  • the computerized master database management system may be configured to send data to each of the plurality of enterprise resource planning platforms based on pre-defined data sets available to the computerized master database management system. This prevents the duplication of data as the computerized master database management system only sends out data to the enterprise resource planning platforms needed by the enterprise resource planning platforms.
  • a processing intermediary computer of a computerized database management system is configured to: convert data from a first format interpretable by a master database management system to a second format interpretable by a plurality of enterprise resource planning platforms and provide data in the second format from a master database management system to a plurality of enterprise resource planning platforms; and convert data from the second format to the first format and provide data in the first format from the plurality of enterprise resource planning platforms to the computerized master database management system.
  • a computerized database management method comprising: a computerized master database management system managing master data in a master database in a first format; a plurality of enterprise resource planning platforms managing data in a second format; and a processing intermediary computer system between the master database management system and the plurality of enterprise resource planning platforms converting data from the first format to the second format and providing data in the second format from the master database management system to the plurality of enterprise resource planning platforms and converting data from the second format to the first format and providing data in the first format from the enterprise resource planning platforms to the computerized master database management system.
  • a processing intermediary computing method comprising: converting data from a first format interpretable by a master database management system to a second format interpretable by a plurality of enterprise resource planning platforms and providing data in the second format from the master database management system to the plurality of enterprise resource planning platforms; and converting data from the second format to the first format and providing data in the first format from the plurality of enterprise resource planning platforms to the computerized master database management system.
  • a computer program for controlling the methods above may be provided.
  • a computer program product containing a set of instructions that causes a computer device to control the methods above may be provided.
  • the computer program product may be a CD-ROM, DVD- ROM, hard-disk drive or solid-state memory, such as a flash drive or USB memory stick.
  • FIG 1 is a schematic illustration of a computerized master database management system in accordance with an embodiment of the invention.
  • the computerized database management system 10 of Figure 1 includes a plurality of separate computer components. These components are arranged in different layers of the computerized database management system 10 as described below.
  • Each user is provided with different access rights to the computerized database management system defined by their role, such as administrator, co-ordinator, participant or observer.
  • the user computer terminals are in communication connection with computerized master database management system 13 through a user authentication arrangement 14 that includes a Microsoft Windows authentication module 16 at the user-side and another authentication module or authentication layer 18 at the computerized master database management system side.
  • the database management system uses Microsoft Windows as its primary authentication mode and the database management system can only be used by authorized users within an authorized network. Authorization of a particular user is maintained by the computerized master database management system.
  • TMA The computerized master database management system is called a technical material application (TMA) in Figure 1 .
  • TMA is a web-based application that uses the web application platform SharePoint 2010 (SharePoint) that is part of the Microsoft Office server suite of Microsoft Corporation, Redmond, Washington, United States.
  • SharePoint 2010 SharePoint
  • TMA effectively manages master data in a master database 13 in XML format. It is a single entry point for all users of a database to browse and manage master data using SharePoint. All information required by users of the database can be reviewed in a single platform whether compliant with an SAP ERP or not. Users can adapt information according to their requirements.
  • All master data has defined processes with roles and responsibilities embedded in the tool. The tool is simple and easy to use requiring, at most, little training. It allows stock levels, for example of spare parts, in all connected affiliates of a multinational enterprise even when they are on ERP platforms.
  • the TMA includes several layers a user interface (Ul) layer, a data layer, an application layer, and a data access layer.
  • Ul user interface
  • the Ul layer includes a site resources or site collection component 20, a web parts component 22 and a features component (not illustrated in Figure 1 ).
  • the Ul layer provides a Ul to the user computer terminals.
  • the site resources or site collection component 20 contains all pages, styles, scripts, images and configuration XML files to deploy in Microsoft SharePoint target content database with respective lists, libraries and roots.
  • the web parts component 22 creates the Ul components for the user computer terminals using the TMA application. These Ul components work with the application data as well as forming the core navigation system within the application.
  • the features component or feature infrastructure of SharePoint provides a "plug and play" ability to add and remove different functionalities to an existing component of a SharePoint site (the ability to add and remove components without needing user intervention).
  • the data layer of the TMA includes SharePoint lists and libraries component 24, SQL server database component 26 and a SharePoint data store component 27.
  • the SharePoint lists and libraries component contains all configuration data for the TMA application. Master data is characterised into libraries each with at least one common characteristic. The SharePoint lists and libraries component can only be modified and updated by a SharePoint site administrator; other users will have read-only access.
  • the SQL server database uses an SQL server 2008 R2 database instance to store and maintain data. It is maintained outside the SharePoint infrastructure. It is treated as an external database to the TMA application (although effectively part of the TMA application) and a connection is made through business connectivity services (BCS) 28 entities through LINQ DBML (a modelling file for LINQ SQL, which is an XML file that broadly includes a set of information about the tables in a database).
  • the SQL server database component stores master data. In this example, the master data is parts or spare parts data for machines in a factory.
  • the SharePoint data store 27 includes some application related data that is stored in SharePoint data stores using the Sharepoint Lists and Libraries component. It is a metadata database. It does not store large object byte (LOB) data; only configuration data is stored. This metadata includes indications of relationships between different master data in the SQL server database component 26.
  • LOB large object byte
  • the data access layer includes the BCS 28 component.
  • This component allows Sharepoint to connect to external data stores in a secure and controlled environment. For example, such that only new data added to a master database by a user terminal 12 is sent to at least one ERP platform 36 via processing intermediary (PI) computer system 34 and such that data is sent to each of the ERP platforms based on pre-defined data sets provided to the BCS and therefore available to the TMA 13. All access to the SQL server database component 26 and SharePoint data store component 27 is through the data access layer and the BCS component in particular.
  • PI processing intermediary
  • the application layer includes a web services component 30 and a search engine component 32.
  • the web service component of the TMA application is used to receive communication, triggers and requests from the PI applications 34. It is hosted within a SharePoint hosting framework.
  • the search engine component 32 or index/crawler component provides indexer and crawler functionality to crawl an external content source and index keywords. The resulting index can be searched using SharePoint server application program interfaces (APIs) of user terminals 12.
  • the master data in the master database is configured or indexed to be searched by entering terms into the computerized master database management system 10 using a user terminal 12.
  • the search engine component identifies data in the master database by predetermined terms prioritised to be found above other data in the master database identified by other terms.
  • the PI computer system 34 of the computerized database management system is between the TMA 13 and a plurality of ERP platforms 36. It converts data from the XML format of the TMA to the SMDL format of the ERP platforms. It provides data in the SMDL format from the master database management system to the ERP platforms using a web services infrastructure and SQL routine. It converts data from the SMDL format to the XML format. It provides data in the XML format from the ERP platforms to the TMA.
  • the SMDL file type is associated with SQL server of Microsoft Corporation, Redmond, Washington, United States.
  • the SMDL file type is a report model that is a metadata description of a data source and its relationships. Report models provide familiar business names for database fields and tables, logically grouped model items, and predefined relationships between items within the data source.
  • the computerized database management system 10 also includes a plurality of ERP platforms 36 (only one is shown in Figure 1 ) for managing data in SMDL format that is different to the XML format of the TMA.
  • the ERP platforms are SAP ERP platforms.
  • a confirmation indication is sent from an ERP platform to the TMA 13 via the PI computer system 34 when and only when the or each of the ERP platforms has been updated with new data.
  • the computerized database management system 10 cannot instruct data on the ERP platforms 36 to be overwritten.
  • the ERP platforms each act as a slave to the TMA 13.
  • the PI computer system 34 also interfaces with external applications or data suppliers using, in this example, SAP Process Integration (SAP PI) to SAP PI using clients 38 or electronic data exchange (EDI) to other external data suppliers 40 that use EDI.
  • SAP PI SAP Process Integration
  • EDI electronic data exchange
  • EDI is an electronic communication method that provides standards for exchanging data by electronic means.
  • SAP PI is a component of the SAP NetWeaver product group that enables information among a company's internal software and systems and those of external parties. Again, all of the interfacing to external sources and applications is routed through the PI application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

A computerized database management system (10) comprising a computerized master database management system (13) for managing master data in a master database in a first format; a plurality of enterprise resource planning platforms (36) for managing data in a second format; and a processing intermediary computer system (34) between the master database management system (13) and the plurality of enterprise resource planning platforms (36). The processing intermediary computer system (34) converts data from the first format to the second format and provides data in the second format from the master database management system (13) to the plurality of enterprise resource planning platforms (36) and converts data from the second format to the first format and provides data in the first format from the enterprise resource planning platforms (36) to the computerized master database management system (13).

Description

A COMPUTERIZED DATABASE MANAGEMENT SYSTEM
The present invention relates to a computerized database management system. Enterprise resource planning (ERP) platforms such as SAP ERP of SAP SE, Weinheim, Barden-Wurttemberg, Germany are well known and extensively used. Broadly, an ERP is a suite of integrated applications to store business data. ERPs are good for transaction data. Transaction data is data describing an event typically with a time dimension and a numerical value that refers to one or more objects (the reference data). Examples of transaction data are invoices or payment information. Typically, a SAP ERP platform has multiple entry points through which users can enter data into the SAP ERP platform with no defined ownership. Because of this, in SAP ERP platforms, there is no control on the creation or maintenance of master data. Master data is a single source of basic business data or common data about business-critical entities such as products, suppliers and customers. It is important that an organization does not use multiple inconsistent versions of master data in different operating locations as this can lead to problems. For example, an organization with many factories may keep details of the parts stored at each of these factories on an ERP platform. If another factory of the same organization wishes to obtain a particular part, it may not be indicated on the ERP platform that such a part is available from another factory in the same organization or there may be misleading information that the part is available in the organization. This is because the multiple entry point ERP platforms may not be up-to-date or data may be duplicated across ERP platforms. This problem is particularly great in large organizations in particular large multinational enterprises with a requirement for high volumes of specialist spare parts for their organization. As a result, these organizations, in particular, may try to obtain a specialist part from outside their organization which cannot be obtained quickly as they are perhaps made to order when the required part could, in theory, be obtained much more quickly from another factory within the same organization. On the other hand, they may try to obtain the part from another factory within the organization only to find that, in fact, the part is not available and leading to a delay in trying to source the part elsewhere. In conclusion, it is difficult and unreliable to find a relevant part.
Master database management systems are known. They are effective at managing master data as they can, for example, remove duplicate files and include rules to remove incorrect data. While master database management systems are good at managing master data, they provide data in a different format to ERPs.
It would be desirable to provide a computerized database management system that can reliably create and maintain master data based on data stored in a plurality of ERP platforms. In this way, users, particularly of large multinational enterprises with huge volumes of data, can have clear and correct knowledge of data, such as related to parts. The inventors of the present patent application have appreciated that an intermediate layer can be provided to convert data between ERPs and a master database management system.
Broadly, embodiments of the present invention take the form of a computerized database management system. A computerized database management system or database management system (DBMS) is a collection of computer programs that enables the storing of information in a database, the modification of information in the database and the extraction of information from the database. The computerized database management system includes a computerized master database management system; a plurality of ERP platforms, such as SAP ERP platforms; and a processing intermediary computer between the master database management system and the plurality of ERP platforms. The computerized master database management system manages master data in a master database in a first format, such as XML. XML is a markup language that defines a set of rules for encoding documents in a format which is both human-readable and machine- readable. The ERP platforms manage data in a second format compatible with the ERP platform. The processing intermediary computer system converts data from the first format to the second format and provides data in the second format from the master database management system to the plurality of enterprise resource planning platforms and converts data from the second format to the first format and provides data in the first format from the enterprise resource planning platforms to the computerized master database management system.
In embodiments of the present invention, data in the database managed by the computerized database management system is up-to-date and reliable. It is quick to update data in the database managed by the computerized database management system. It is quick to access data in the database managed by the computerized database management system. This is because the computerized database management system provides a single entry point for data and it allows for control on the creation and maintenance of master data.
In one aspect there is provided a computerized database management system comprising: a computerized master database management system for managing master data in a master database in a first format; a plurality of enterprise resource planning platforms for managing data in a second format; and a processing intermediary computer system between the master database management system and the plurality of enterprise resource planning platforms that converts data from the first format to the second format and provides data in the second format from the master database management system to the plurality of enterprise resource planning platforms and converts data from the second format to the first format and provides data in the first format from the enterprise resource planning platforms to the computerized master database management system. This arrangement provides a technical solution to the technical problem of quickly providing reliable data. This arrangement is computationally efficient.
The computerized database management system may be configured such that only new data added to a master database managed by the computerized master database management system is sent to at least one of the plurality of enterprise resource planning platforms via the processing intermediary computer system. As a result, the system has quick response times.
A confirmation indication may be sent from the at least one of the plurality of enterprise resource planning platforms to the master database management system via the processing intermediary computer system when and only when the or each of the at least one of the plurality of enterprise resource planning platforms has been updated with new data. As a result, there is an indication that the master database is up-to-date.
The first format may comprise XML. The plurality of enterprise resource planning platforms may comprise SAP ERP platforms.
The computerized database management system may be configured such that it cannot instruct data on the plurality of enterprise resource planning platforms to be overwritten. As a result, the data is reliable and the system quick.
The computerized database management system may comprise indications of relationships between different master data in the master database. ERPs cannot provide for this and it allows data related to equivalent elements (such as spare parts) otherwise identified in different ways to be recognised.
The master data may comprise parts data.
The computerized database management system characterises master data into libraries each with at least one common characteristic. This allows for quick and reliable searching of the data.
Master data in the master database may be configured to be searched by entering terms into the computerized master database management system and wherein data in the master database identified by predetermined terms is prioritised to be found above other data in the master database identified by other terms. This provides a more focussed and therefore reliable search.
The plurality of enterprise resource planning platforms may each act as a slave to the computerized master database management system. In this way, there is a single entry point for data, which provides reliable data.
The computerized master database management system may be configured to send data to each of the plurality of enterprise resource planning platforms based on pre-defined data sets available to the computerized master database management system. This prevents the duplication of data as the computerized master database management system only sends out data to the enterprise resource planning platforms needed by the enterprise resource planning platforms.
In one aspect there is provided a processing intermediary computer of a computerized database management system, the processing intermediary computer is configured to: convert data from a first format interpretable by a master database management system to a second format interpretable by a plurality of enterprise resource planning platforms and provide data in the second format from a master database management system to a plurality of enterprise resource planning platforms; and convert data from the second format to the first format and provide data in the first format from the plurality of enterprise resource planning platforms to the computerized master database management system.
In one aspect there is provided a computerized database management method comprising: a computerized master database management system managing master data in a master database in a first format; a plurality of enterprise resource planning platforms managing data in a second format; and a processing intermediary computer system between the master database management system and the plurality of enterprise resource planning platforms converting data from the first format to the second format and providing data in the second format from the master database management system to the plurality of enterprise resource planning platforms and converting data from the second format to the first format and providing data in the first format from the enterprise resource planning platforms to the computerized master database management system.
In one aspect there is provided a processing intermediary computing method comprising: converting data from a first format interpretable by a master database management system to a second format interpretable by a plurality of enterprise resource planning platforms and providing data in the second format from the master database management system to the plurality of enterprise resource planning platforms; and converting data from the second format to the first format and providing data in the first format from the plurality of enterprise resource planning platforms to the computerized master database management system.
A computer program for controlling the methods above may be provided. A computer program product containing a set of instructions that causes a computer device to control the methods above may be provided. The computer program product may be a CD-ROM, DVD- ROM, hard-disk drive or solid-state memory, such as a flash drive or USB memory stick.
Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawing, in which:
Figure 1 is a schematic illustration of a computerized master database management system in accordance with an embodiment of the invention. The computerized database management system 10 of Figure 1 includes a plurality of separate computer components. These components are arranged in different layers of the computerized database management system 10 as described below.
A plurality of user terminals 12, such as desktop or laptop computers, provide access to the computerized database management system 10. Each user is provided with different access rights to the computerized database management system defined by their role, such as administrator, co-ordinator, participant or observer. The user computer terminals are in communication connection with computerized master database management system 13 through a user authentication arrangement 14 that includes a Microsoft Windows authentication module 16 at the user-side and another authentication module or authentication layer 18 at the computerized master database management system side. In this way, the database management system uses Microsoft Windows as its primary authentication mode and the database management system can only be used by authorized users within an authorized network. Authorization of a particular user is maintained by the computerized master database management system.
The computerized master database management system is called a technical material application (TMA) in Figure 1 . TMA is a web-based application that uses the web application platform SharePoint 2010 (SharePoint) that is part of the Microsoft Office server suite of Microsoft Corporation, Redmond, Washington, United States. Broadly, TMA effectively manages master data in a master database 13 in XML format. It is a single entry point for all users of a database to browse and manage master data using SharePoint. All information required by users of the database can be reviewed in a single platform whether compliant with an SAP ERP or not. Users can adapt information according to their requirements. All master data has defined processes with roles and responsibilities embedded in the tool. The tool is simple and easy to use requiring, at most, little training. It allows stock levels, for example of spare parts, in all connected affiliates of a multinational enterprise even when they are on ERP platforms.
In addition to the authentication module 18, the TMA includes several layers a user interface (Ul) layer, a data layer, an application layer, and a data access layer.
The Ul layer includes a site resources or site collection component 20, a web parts component 22 and a features component (not illustrated in Figure 1 ). The Ul layer provides a Ul to the user computer terminals. The site resources or site collection component 20 contains all pages, styles, scripts, images and configuration XML files to deploy in Microsoft SharePoint target content database with respective lists, libraries and roots. The web parts component 22 creates the Ul components for the user computer terminals using the TMA application. These Ul components work with the application data as well as forming the core navigation system within the application. The features component or feature infrastructure of SharePoint provides a "plug and play" ability to add and remove different functionalities to an existing component of a SharePoint site (the ability to add and remove components without needing user intervention).
The data layer of the TMA includes SharePoint lists and libraries component 24, SQL server database component 26 and a SharePoint data store component 27. The SharePoint lists and libraries component contains all configuration data for the TMA application. Master data is characterised into libraries each with at least one common characteristic. The SharePoint lists and libraries component can only be modified and updated by a SharePoint site administrator; other users will have read-only access. The SQL server database uses an SQL server 2008 R2 database instance to store and maintain data. It is maintained outside the SharePoint infrastructure. It is treated as an external database to the TMA application (although effectively part of the TMA application) and a connection is made through business connectivity services (BCS) 28 entities through LINQ DBML (a modelling file for LINQ SQL, which is an XML file that broadly includes a set of information about the tables in a database). The SQL server database component stores master data. In this example, the master data is parts or spare parts data for machines in a factory.
The SharePoint data store 27 includes some application related data that is stored in SharePoint data stores using the Sharepoint Lists and Libraries component. It is a metadata database. It does not store large object byte (LOB) data; only configuration data is stored. This metadata includes indications of relationships between different master data in the SQL server database component 26.
The data access layer includes the BCS 28 component. This component allows Sharepoint to connect to external data stores in a secure and controlled environment. For example, such that only new data added to a master database by a user terminal 12 is sent to at least one ERP platform 36 via processing intermediary (PI) computer system 34 and such that data is sent to each of the ERP platforms based on pre-defined data sets provided to the BCS and therefore available to the TMA 13. All access to the SQL server database component 26 and SharePoint data store component 27 is through the data access layer and the BCS component in particular.
The application layer includes a web services component 30 and a search engine component 32. The web service component of the TMA application is used to receive communication, triggers and requests from the PI applications 34. It is hosted within a SharePoint hosting framework. The search engine component 32 or index/crawler component provides indexer and crawler functionality to crawl an external content source and index keywords. The resulting index can be searched using SharePoint server application program interfaces (APIs) of user terminals 12. The master data in the master database is configured or indexed to be searched by entering terms into the computerized master database management system 10 using a user terminal 12. The search engine component identifies data in the master database by predetermined terms prioritised to be found above other data in the master database identified by other terms.
The PI computer system 34 of the computerized database management system is between the TMA 13 and a plurality of ERP platforms 36. It converts data from the XML format of the TMA to the SMDL format of the ERP platforms. It provides data in the SMDL format from the master database management system to the ERP platforms using a web services infrastructure and SQL routine. It converts data from the SMDL format to the XML format. It provides data in the XML format from the ERP platforms to the TMA. The SMDL file type is associated with SQL server of Microsoft Corporation, Redmond, Washington, United States. The SMDL file type is a report model that is a metadata description of a data source and its relationships. Report models provide familiar business names for database fields and tables, logically grouped model items, and predefined relationships between items within the data source.
The computerized database management system 10 also includes a plurality of ERP platforms 36 (only one is shown in Figure 1 ) for managing data in SMDL format that is different to the XML format of the TMA. In this example, the ERP platforms are SAP ERP platforms. A confirmation indication is sent from an ERP platform to the TMA 13 via the PI computer system 34 when and only when the or each of the ERP platforms has been updated with new data. Significantly, the computerized database management system 10 cannot instruct data on the ERP platforms 36 to be overwritten. The ERP platforms each act as a slave to the TMA 13.
The PI computer system 34 also interfaces with external applications or data suppliers using, in this example, SAP Process Integration (SAP PI) to SAP PI using clients 38 or electronic data exchange (EDI) to other external data suppliers 40 that use EDI. EDI is an electronic communication method that provides standards for exchanging data by electronic means. SAP PI is a component of the SAP NetWeaver product group that enables information among a company's internal software and systems and those of external parties. Again, all of the interfacing to external sources and applications is routed through the PI application.
The exemplary embodiments described above illustrate but are not limiting. In view of the above discussed exemplary embodiments, other embodiments consistent with the above exemplary embodiments will now be apparent to one of ordinary skill in the art.

Claims

Claims
A computerized database management system comprising:
a computerized master database management system for managing master data in a master database in a first format;
a plurality of enterprise resource planning platforms for managing data in a second format; and
a processing intermediary computer system between the master database management system and the plurality of enterprise resource planning platforms that converts data from the first format to the second format and provides data in the second format from the master database management system to the plurality of enterprise resource planning platforms and converts data from the second format to the first format and provides data in the first format from the enterprise resource planning platforms to the computerized master database management system;
wherein the computerized database management system comprises indications of relationships between different master data in the master database.
A computerized database management system according to claim 1 , wherein the computerized database management system is configured such that only new data added to a master database managed by the computerized master database management system is sent to at least one of the plurality of enterprise resource planning platforms via the processing intermediary computer system.
A computerized database management system according to claim 1 or claim 2, wherein a confirmation indication is sent from the at least one of the plurality of enterprise resource planning platforms to the master database management system via the processing intermediary computer system when and only when the or each of the at least one of the plurality of enterprise resource planning platforms has been updated with new data.
A computerized database management system according to any preceding claim, wherein the first format comprises XML.
A computerized database management system according to any preceding claim, wherein the plurality of enterprise resource planning platforms comprise SAP ERP platforms.
A computerized database management system arrangement according to any preceding claim, wherein the computerized database management system cannot instruct data on the plurality of enterprise resource planning platforms to be overwritten. A computerized database management system according to any preceding claim, wherein the master data comprises parts data.
8. A computerized database management system according to any preceding claim, wherein the computerized database management system characterises master data into libraries each with at least one common characteristic.
9. A computerized database management system according to any preceding claim, wherein master data in the master database is configured to be searched by entering terms into the computerized master database management system and wherein data in the master database identified by predetermined terms is prioritised to be found above other data in the master database identified by other terms.
10. A computerized database management system according to any preceding claim, wherein the plurality of enterprise resource planning platforms each act as a slave to the computerized master database management system.
1 1 . A computerized database management system according to any preceding claim, wherein the plurality of enterprise resource planning platforms each act as a slave to the computerized master database management system.
12. A computerized database management system according to any preceding claim, wherein the computerized master database management system is configured to send data to each of the plurality of enterprise resource planning platforms based on predefined data sets available to the computerized master database management system.
13. A processing intermediary computer of a computerized database management system, the processing intermediary computer being configured to:
convert data from a first format interpretable by a master database management system comprising indications of relationships between different master data in a master database to a second format interpretable by a plurality of enterprise resource planning platforms and provide data in the second format from a master database management system to a plurality of enterprise resource planning platforms; and
convert data from the second format to the first format and provide data in the first format from the plurality of enterprise resource planning platforms to the computerized master database management system.
14. A computerized database management method comprising:
a computerized master database management system managing master data in a master database in a first format;
a plurality of enterprise resource planning platforms managing data in a second format; and
a processing intermediary computer system between the master database management system and the plurality of enterprise resource planning platforms converting data from the first format to the second format and providing data in the second format from the master database management system to the plurality of enterprise resource planning platforms and converting data from the second format to the first format and providing data in the first format from the enterprise resource planning platforms to the computerized master database management system;
wherein the computerized database management system comprises indications of relationships between different master data in the master database.
PCT/EP2016/067640 2015-08-03 2016-07-25 A computerized database management system WO2017021186A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP15179540 2015-08-03
EP15179540.8 2015-08-03

Publications (1)

Publication Number Publication Date
WO2017021186A1 true WO2017021186A1 (en) 2017-02-09

Family

ID=53794074

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2016/067640 WO2017021186A1 (en) 2015-08-03 2016-07-25 A computerized database management system

Country Status (1)

Country Link
WO (1) WO2017021186A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110955715A (en) * 2019-12-03 2020-04-03 望海康信(北京)科技股份公司 ERP system, data conversion method and device of target platform and electronic equipment
CN111611230A (en) * 2020-06-30 2020-09-01 望海康信(北京)科技股份公司 Method and device for establishing main data system, computer equipment and storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110071979A1 (en) * 2009-09-22 2011-03-24 Oracle International Corporation Data Governance Manager for Master Data Management Hubs
US20110282969A1 (en) * 2010-05-13 2011-11-17 SEAL Innotech Method and system for exchanging information between back-end and front-end systems

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110071979A1 (en) * 2009-09-22 2011-03-24 Oracle International Corporation Data Governance Manager for Master Data Management Hubs
US20110282969A1 (en) * 2010-05-13 2011-11-17 SEAL Innotech Method and system for exchanging information between back-end and front-end systems

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
GREGOR HOHPE: "Hub and Spoke [or] Zen and the Art of Message Broker Maintenance - Enterprise Integration Patterns", 12 November 2003 (2003-11-12), XP055241474, Retrieved from the Internet <URL:http://www.enterpriseintegrationpatterns.com/ramblings/03_hubandspoke.html> [retrieved on 20160114] *
LINTHICUM D S: "Enterprise Application Integration", ENTERPRISE APPLICATION INTEGRATION, XX, XX, 1 March 2000 (2000-03-01), pages 291 - 317, XP002322125 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110955715A (en) * 2019-12-03 2020-04-03 望海康信(北京)科技股份公司 ERP system, data conversion method and device of target platform and electronic equipment
CN110955715B (en) * 2019-12-03 2023-04-28 望海康信(北京)科技股份公司 Data conversion method and device for ERP system and target platform and electronic device
CN111611230A (en) * 2020-06-30 2020-09-01 望海康信(北京)科技股份公司 Method and device for establishing main data system, computer equipment and storage medium

Similar Documents

Publication Publication Date Title
US7941398B2 (en) Autopropagation of business intelligence metadata
EP2199904B1 (en) Flexible multi-tenant support of metadata extensions
CN105144080B (en) System for metadata management
US20170316183A1 (en) Clinical data management system
US9053117B2 (en) Storing application data with a unique ID
US9508048B2 (en) System and method for integrated real time reporting and analytics across networked applications
US11783254B2 (en) Method and system for implementing an adaptive data governance system
US20070203952A1 (en) Configuration management database state model
US20110295791A1 (en) System and method for specifying metadata extension input for extending data warehouse
US20110276603A1 (en) Dependency graphs for multiple domains
US8108373B2 (en) Selecting an author of missing content in a content management system
US20140006342A1 (en) Systems for the integrated design, operation and modification of databases and associated web applications
US20150081744A1 (en) Metadata model repository
Quinton et al. Evolution in dynamic software product lines: challenges and perspectives
US20030131018A1 (en) Common business data management
CN101046822B (en) Centralized management of data nodes
US8429447B2 (en) System and method for providing indexing with high availability in a network based suite of services
Kumar et al. Modern Big Data processing with Hadoop: Expert techniques for architecting end-to-end Big Data solutions to get valuable insights
US20050131825A1 (en) Distributed knowledge management system
WO2017021186A1 (en) A computerized database management system
TW200419388A (en) System and method for automatically comparing and recoding difference between bills of material (BOM)
US20080086385A1 (en) Data processing system using independent and dependent assets
Volarevic et al. A philosophy of the electronic document management
US11113664B2 (en) Data provisioning system and method
US20120166405A1 (en) Changeability And Transport Release Check Framework

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16745093

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16745093

Country of ref document: EP

Kind code of ref document: A1