JP2009266243A - Dynamic access of data - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide dynamic access to data stored in a database maintained and managed by a server. <P>SOLUTION: A client sends a request to the server to access the data stored in the database. A first set of data is retrieved from the database and mapped to a second set of data on the basis of a set of mapping rules that is defined by the client. The client then receives the second set of data. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to dynamic access of master data.

  In a hybrid information technology environment, different computer application systems are used within one configuration or across different configurations. For example, one system can be used to manage information about a company's clients, and another system can be used to manage information about products. Each system will have its own user interface, data storage and processing method for processing the data. Each system will be designed to optimize performance to handle a particular task. There will be a correlation between the data maintained by the two systems. For example, some products may be requested by a client and must be modified to meet certain characteristics and need to be delivered to the client's specific address.

  For a system to be able to share data, one system must be introduced as a master data server to maintain a master database that stores all client data in the form of client objects. The system must be implemented as a master data server to maintain a master database that stores all product data in the form of product objects. Each client object has attributes that describe various aspects of the client. Some of the client attributes are partial and some are global. Partial attributes are only stored in their respective databases, but overall attributes are replicated asynchronously to another database periodically or by some factor. Because the overall attributes are duplicated, the system can access client data and product data that require access to each database using a partial application programming interface. Each system maintains its own database, so each system can improve performance or maintain independently.

JP-A-7-65032

  In one aspect, the present invention is widely used in a method for dynamically accessing data. The method includes the steps of a client sending a request to the server to access data stored in a database maintained by the server, reading a first set of data from the database, and a mapping defined by the client. Mapping the first set of data to the second set of data based on the set of rules and receiving the second set of data at the client are included.

  By implementing the present invention, one or more of the following features can be obtained. An object included in the database includes an attribute value of the object. The object contains a product. The object includes a business partner. Mapping the first set of data to the second set of data includes removing attribute data in the first set of data not associated with the client. The set of mapping rules is sometimes changed by clients unrelated to the server.

  In another aspect, the invention is widely used in a method for maintaining data. The method includes receiving at the server an identifier and data associated with the object identified by the identifier and verifying for each client that the identifier and data conform to a set of rules defined by the client. And entering the identifier and data into the database, wherein the server is configured to maintain a database accessible to the client.

  By implementing the present invention, one or more of the following features can be obtained. The database includes attribute values associated with the object. Verifying that the identifier and database conform to a set of rules includes confirming that the data conforms to a client-defined subset of rules associated with the attributes of the object. The rule subset includes rules for defining formats that are within the allowed range of attribute values. Verifying that the identifier and data conform to a set of rules includes confirming that the identifier conforms to a subset of rules defined by the client associated with the object's identification. . The set of rules includes a rule that defines a format that is within the allowable range of identifiers. The method further includes linking data to the identifier. The method further includes sending a request from the client to the server requesting data linked to the identifier, and converting the data in the database linked to the identifier into a client acceptable format. The method further includes sending a request from the server to the second server, identifying which clients can access the database, and the client identified as being able to access the database from the second server. The request is routed, and the request requires identification and data identification. The object includes a product. The object includes a business partner. The server interacts with the client using messages written in an extensible markup language. The method further includes, for each client, sending a request to the client to verify that the identifier and database conform to the set of rules defined by the client, and if a particular client does not respond. Placing the client on an exception list and notifying that the identifier and data could not be verified as complying with a set of rules defined by a particular client. Another attempt to verify that the identifier and data conform to a set of rules defined by a particular client is after a certain length of time, or a particular client tries to access data in the database. It is carried out at the time.

  In another aspect, the invention is widely used in a method for maintaining data. The method includes sending a request from the client to the server to change a set of data associated with an object, and a message that only the client can change the data set because the server has fixed the data set. Each of the other clients, receiving a message that the modified data is stored in the database, sending a modified set of data to the server to store the modified data in the database, In contrast, the process includes determining at the server which other clients can access the modified data and verifying that the modified data conforms to a set of rules defined by the client. The set of data is stored in a database maintained by the server.

  By implementing the present invention, one or more of the following features can be obtained. The data set includes attribute values associated with the object. The set of rules defined by the client includes rules for defining formats that are within the allowable range of attribute values. The server compares the attribute with a checklist issued by the client to determine which other clients can access the changed data, and each checklist indicates an attribute accessible to the client. Objects include products. Objects include business partners. The server interacts with the client using messages with code written in an extensible markup language.

  In another aspect, the present invention broadly switches between a first mode for storing data in a local database and a second mode for storing data in a remote database maintained by a server computer. Providing a client computer with a module that can be configured, and providing an interface for dynamically mapping data stored in a remote database to data having a format defined by the client computer. Used in the method.

  By implementing the present invention, one or more of the following features can be obtained. The method further includes a second module having a module capable of switching between a first mode for storing data in a localized database and a second mode for storing data in a remote database maintained by the server computer. Providing a client computer, wherein the interface also dynamically maps data stored in the remote database to data having a second format defined by the second client computer, the second format comprising: The second client changes regardless of the first client.

  In another aspect, the present invention broadly relates to a data server that maintains a database that stores data associated with an object identified by an identifier, a client that accesses data stored in the database, a client and a data server, An integration server that communicates, the object has attributes that describe aspects of the object, the data includes attribute values associated with the attributes, each client defines a set of rules for identifiers and attributes, and the integration The server is used in a system characterized by mapping data in the data server to data having a format that conforms to the rules defined by the client in response to a request from the client for the data.

By implementing the present invention, one or more of the following features can be obtained. The integration server interacts with the client and data server using messages containing code written in an extensible markup language.

  In another aspect, the invention broadly relates to data stored explicitly in a machine readable medium for dynamic access of master data and stored in a database maintained by a server for a programmable processor. Receiving a request from the client to access and reading the first set of data from the data, and based on a set of mapping rules defined by the client, the first set of data is Used in a computer program product that includes instructions operable to map to a data set and cause a second data set to be sent to a client.

  By implementing the present invention, one or more of the following features can be obtained. The data stored in the database includes object attribute values. Objects include products. Objects include business partners. The instructions are operable to cause the programmable processor to remove attribute data in the first set of data not relevant to the client. The set of mapping rules is sometimes changed by the client regardless of the server.

  In another aspect, the present invention broadly relates to the dynamic access of master data stored in a database accessible to a client and is clearly stored on a machine-readable medium and an identifier for a programmable processor. And receive data associated with the object identified by the identifier, and allow each client to verify that the identifier and data conform to a set of rules defined by the client, and store the identifier and data in the database. Used in a computer program product that includes instructions operable to cause

  By implementing the present invention, one or more of the following features can be obtained. The data includes attribute values associated with the object. The instructions are operable to cause a programmable processor to verify that the data conforms to a subset of rules defined by the client in relation to the attributes of the object. The rule subset includes rules for defining formats that are within the allowed range of attribute values. The instructions are operable to cause a programmable processor to verify that the identifier conforms to a subset of rules defined by the client in connection with object identification. The set of rules includes rules for defining formats that are within the allowable range of identifiers. The instructions are operable to link data to an identifier for a programmable processor. The instructions are operable to cause the programmable processor to send a request for data linked to the identifier from the client to the server and to convert the data in the database linked to the identifier to a format acceptable to the client. It is. Objects include products. Objects include business partners. The server interacts with the client using messages written in an extensible markup language. The instruction causes the programmable processor to send each client a request to verify that the identifier and data conform to the client-defined set of rules, and if a particular client does not respond The client can be placed on the disclaimer summary table and operate to signal that the identifier and data could not be verified as conforming to a set of rules defined by a particular client. The instruction may cause the programmable processor to make another attempt to verify that the identifier and data conform to a set of rules defined by a particular client, after a predetermined length of time, or when a particular client It is possible to operate to start when trying to access the data within.

  In another aspect, the present invention broadly provides a set of objects associated with a computer system having a client and a server that are explicitly stored on a machine-readable medium for dynamic access of master data. Send a request from the first client to the server for the data change, receive a message that only the client can change the data set because the server has fixed the data set, and store the data in the database For use in a computer program product comprising instructions operable to cause a modified set of data to be sent to a server and to receive a message that the modified data set has been stored in a database. Access the modified data set for each of the clients Possible other clients will determine which, and the modified data set is to ensure their suitability for the set of rules that the client defined.

  By implementing the present invention, one or more of the following features can be obtained. The data set includes attribute values associated with the object. The set of rules defined by the client includes rules for defining formats that are within the allowed range of attribute values. The instructions are operable to cause the computer system to compare the attribute value with a checklist issued by the client, each checklist indicating an attribute accessible to the client. Objects include products. Objects include business partners. The instructions are operable to cause the server to interact with the client using a message comprising code written in an extensible markup language.

  The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.

1 is a diagram of a hybrid system. It is a detailed view of a client and a server. It is a figure which shows the process for confirming the consistency of master data. It is a figure which shows the process for confirming the consistency of master data. It is a figure which shows the process for confirming the consistency of master data. It is a figure which shows the entry of data. It is a figure which shows the architecture with respect to composite type | mold software. FIG. 2 is a diagram illustrating a composite architecture. It is a figure which shows the application which accesses master data using a proxy. It is a figure which shows a computer system.

  Referring to FIG. 1, the hybrid system 100 includes a master data server (MDS) 110, an integration server 109, and client systems 102-106. The master data server 110 maintains one master database 112, and the client systems 102 to 106 dynamically access the master database 112 synchronously through the integration server 109 and the master data server 110. The client systems 102-106 match the data stored in the database 112 by a consistency check process when the data is first stored in the master data 112. When data is updated by the master data server 110 or the client systems 102-106, the changes are visible to all of the client systems 102-106. The advantage of using a single master database 112 is that management overhead is reduced and the problem of synchronization of different databases is eliminated.

  The terms “synchronize” and “dynamic” mean that when processing performed on the client system requires information, the information can be accessed from the master database 112 at any time without storing data locally on the client side. Means. The process may be a batch process executed in the background, or may be a process adapted to allow a user to access, browse and maintain master data. Different processes require different data formats, and data transferred between the client system and the master data server is dynamically mapped from one format to another depending on the configuration of the system. Each client system can be configured independently of the other systems, and each system can view and process data in the master database 112 separately. The integration server 109 dynamically maps data so as to conform to the data format defined by each client system and the master data server.

  Referring to FIG. 2, client 114 is used to represent any of client systems 102-106. For example, different application programs such as a sales application 116 and a product application 118 that accesses data related to the product are executed on the client 114. Application programs 116 and 118 access functions provided by the product service layer 124. Product user interface 120 interacts with product service layer 124 to provide an image representation of user data. The product service layer 124 is specific to the client 114 and provides the ability to process product data according to the product model associated with the client 114. For example, client 114 may have an application that is used to manage client relationships. These applications require data related to the product that is transferred to and from the client. The product data used by the application executed on the client 114 includes sales data, but does not include financial data. Client 114 does not store any data related to the product. Instead, all requests to access such data are routed to the master data server 110 through the exchange interface 126 in the integration server 109.

  The main function of the master data server 110 is to maintain and manage master data stored in the master database 112. Different application programs, such as applications 128 and 130 that access the master data, can be executed on the master data server 110. Applications 128 and 130 access functions provided by the product service layer 134. The product user interface 132 interacts with the product server layer 134 to provide an image representation of user data. The product service layer 134 is unique to the master data server 110 and provides a function of processing product data according to a product model associated with the master data server 110. The product service layer 134 accesses the master database 112. When an application running on the client 114 needs to access master data stored in the master database 112, the request is routed through the exchange interface 126 to the product service layer 134. The exchange interface 126 can connect to the product service layers 124 and 134 using a peer-to-peer connection.

  The product model associated with client 114 will be different from the product model associated with master data server 110. Thus, when the product service layer 124 accesses the master database 112 through the product service 134, semantic mapping is required.

  Product service layer 124 provides a consistent application programming interface that can be used by applications of client 114. This makes it easier to maintain and update the sales application 116 and product application 118. Since the product service layer is unique to the client, different clients will have different product service layers. Each product service layer of a client system and its associated application can be changed or updated independently of the product service layers of other client systems.

[Maintenance of master data]
When master data is created or changed, the data should be consistent with the business processes running on the client. In order to process correctly, the process needs to depend on the integrity of the data it uses. It is known which clients use the data when the master data is created or updated. Thus, all clients involved in the data check the integrity of the data before using the data.

  Because the user maintains (eg, adds, changes, deletes) the master data, the user wants to make sure that the changes are consistent with the processing performed on the client. The user needs a quick response that informs them that they are consistent and helps the data to be consistent.

  Consistency rules by clients are contradictory to each other. If there is a conflict, there is no choice of data that will satisfy all clients, so the master data object cannot be maintained. Therefore, the client must be harmonized by the user maintaining the data before the master data object may be created.

  Consistency can be checked either when writing or reading data. The advantage of checking consistency when reading data is that each client checks the consistency of the data used in its processing when reading the data. The disadvantage is that reading is performed more frequently than writing, so checking consistency when reading data is less efficient than writing data. Another drawback is that the inconsistency cannot be resolved when an inconsistency is discovered during the read operation. It is necessary to stop the process accessing the inconsistent data, find out who invaded the data, and determine whether the correction is possible and which data is correct. In comparison, the advantage of checking consistency when writing data is that it allows the user to modify the database before the data is actually stored and written to the master database.

  Referring to FIG. 3, when new data enters the master database 112, the user performs a data input process 142 through the master data server 110. In this example, master data maintenance management is executed by the master data server 110. Clients A 114 and B 114 are connected to the integrated server 109. The user selects a user interface (eg, screen) to create and fix a new input for the new product <146>. As an example, the user selects the number “4711” to identify a new product. Before the new entry is saved in the master database 112, the identifier “4711” is “fixed” so that other users cannot use it to identify other products. Due to the immobilization procedure, only one person can create master data related to the identifier “4711”.

  In order to ensure that all applications can access the data entered into the master database 112 by identifier, the identifier (ie, the number “4711”) matches against a scheme that defines a format that is within the allowable range of identifiers. <148>. Each of the master data server 110, the client A 114, and the client B 114 can have its own system different from other systems. For example, the master data server 110 may use a scheme that requires an identifier of less than 10 digits. Once the identifier is confirmed to match the scheme required by the master data server 110, a request is sent from the master data server 110 to the integration server 109 to examine the identifier against the scheme generated by various clients.

  The integration server 109 has information where clients can access new data. For example, both client A 114 and client B 114 access data related to “product”. The integration server 109 sends a request for checking the identifier to the system to the client concerned, in this case, client A 114 and client B 114 <150>. When client A 114 receives a request to verify the identifier, client A 114 checks the identifier against its system <152>. If the identifier does not match the scheme, an error message is sent to the master data server 110 to indicate that the user must choose another identifier. Similarly, client B 114 checks the identifier for its scheme <154> and if the identifier does not match the scheme, it sends an error message to master data server 110. By examining at 148, 152, 154, the master data server 110, client A 114, and client B 113 can all access new data using the correct identifier for each of the server 110, client A 114, and client B 114. It is certain that it can be done.

  If the identifier format is confirmed, the user continues to maintain general attributes for the product 4711. For example, an attribute can be a short description of a product, a basic unit of measurement, a sales unit of measurement, a price of a product, a quantity of a product, a planning parameter for a product, or a seller of a product. It may be. General attributes are those associated with more than one client.

  The user enters an attribute value for each attribute and checks whether the attribute value satisfies a collection of consistency records for those attributes <158>. For example, consistency rules require that if a new unit of measurement is added, it requires a conversion factor for the existing unit of measurement. As another example, consistency rules must be specified in the same way if money is used to represent the price of a product.

  The master data server 110 sends a request to the integration server 109 to request confirmation of the attribute value. Integration server 109 routes the request to the associated client <160>. Upon receipt of the request, client A 114 checks the attribute value against the consistency record defined by client A 114 <162> and sends a message to master data server 110 if a rule violation occurs. For example, client A 114 may define a consistency rule that requires a basic unit of measurement with a sales unit of measurement (eg, if a sales person sells a product in a box, the sales person ) And additional information on how many products are in one box). Other consistency rules may require that prices be specified in euros.

  Upon receiving the request for attribute confirmation, the client B 144 checks the attribute value against the rule defined by the client 144 <164>. For example, the consistency rule requires that only the production time can be changed if there is no pending plan execution (because, for example, the planned execution is determined by a certain production time).

  After Client A 114 and Client B 114 confirm that the attributes conform to the rules defined by these clients, the user selects an interface (eg, a screen) to maintain, for example, data related to sales <166. >. The attributes related to sales are related only to client A 114 and not related to client B 114. The integration server 109 keeps track of which types of attributes are associated with which clients. After the user adds or changes data related to sales, the master data server 110 sends a request to the integration server 109 to confirm that the data meets the client's integrity rules. The integration server 109 routes the request to the associated client, which in this example is client A 114 <168>. Upon receipt of the request, client A 114 checks the sales related data with the consistency rules associated with the sales data defined by client A 114. If the data is consistent with the consistency rules, the master data server 110 stores the new data in the master database 112 <172>.

  Master data can also be maintained by the user of the client using an interface that executes the maintenance dialog. The interface can be designed so that only data relevant to the client is displayed and maintained.

  Referring to FIG. 4, the data maintenance management process 174 is executed when the client updates data in the master database 112. In this example, the client A 114 desires to update data related to the product 4711. Client A 114 "opens" product 4711 <176>, which shows a graphical user interface that allows the user to enter the identifier "product 4711" to identify what data needs to be updated Let's mean.

  Client A 114 sends a request to integration server 109, which requests data from master data server 110 <178>. Upon receipt of the request, the master data server 110 reads and fixes data associated with the product 4711 <180>. Fixing is performed by the master data server 110 regardless of which client has changed the database. The master data server 110 needs to know which client has locked the database so that this information can communicate with other clients that are trying to access the data. This data is sent to the integration server 109, and the data is mapped to data having the format of the client A 114. As an example, the client A 114 maintains and manages data related to sales. The client 114 uses a graphical user interface to display a screen showing only data related to sales. The user at client A 114 proceeds with maintenance (eg, correction or deletion) of data related to sales <182>. The updated data is checked for consistency with rules defined by other clients and the master data server 110.

  The client A 114 sends a request to the server 109 and starts the confirmation process. The integration server 109 routes this request to the associated client. In this example, the integration server 109 does not send the request to the client B 144 because it is not related to the sales data client B 144. The integration server 109 sends the request to the master data server 110, which responds to the request by matching the attributes against the consistency rules that the master data server 110 has defined for consistency <188>. The master data server 110 and other clients send a message indicating that the updated data is consistent with the integrity rules, and request that the master data server store the updated data in the master database 112. To the master data server 110.

  The master data server 110 maintains and manages data required for processing executed on many applications or different clients. Clients that maintain data related to objects (or users who use clients) are not entitled or authorized to change all data, only data related to their processing (eg sales) Can be maintained. The integration server 109 is configured such that the user can only access a screen having data related to his process, and therefore can only handle consistency requests for this screen. Data that has been maintained (and the objects associated with the data) can be used for this screen (eg, can be used for processing related to this screen). The data cannot be used on screens that have not yet been created (eg, future plans).

  The clients that need to be checked for consistency are determined by the integration server 109. The integration server 109 routes the verification request to the client at runtime and returns the result of each client, either an “acknowledgement message” or a collection of messages describing the consistency error. Errors are displayed so that the user can change the data to ensure consistency.

  During the consistency verification process, if the client does not respond, the client is placed on the disclaimer summary table and the verification process continues for the remaining clients. This ensures that master data maintenance is not hampered by some mistakes of the client.

  Referring to FIG. 5, the data maintenance process 194 occurs when the client does not respond. The master data server 110 maintains data related to the product 4711 <196> and sends a request to the integration server 109 to confirm consistency. Integration server 109 routes the request to the associated client <198>. Upon receipt of this request, client A 114 checks the attributes <200>. When client B 144 receives this request, it is considered that the client B 144 also checks the attribute <202>. However, for several reasons (eg, shutdown), client B 144 may not respond <204>. The integration server 109 collects all responses from the client <206> and finds that no response has been received from the client B 144. The integration server 109 sends the responses collected from the clients to the master data server 110.

  Master data server 110 adds client B 144 to the disclaimer summary table <208>, indicating that client B 144 has not been verified that the updated data is consistent with the consistency rules requested by client B 144. . The master data server 110 stores the updated data in the master database 112 <208> and begins the workflow of examining client B 144 <212>. This work flow is an opportunity to inform client B 144 that it is possible to check client B 144 manually or automatically after a certain period of time, or to communicate with the client, such as when client B 144 sends a read request. When there is an event, the client B 144 is checked. If the integration server 109 is able to successfully communicate with the client B 144, the client B 144 checks the attribute for checking consistency <214>. Upon receiving confirmation from client B 144 that there is no mismatch, master data server 110 removes client B 144 from the exemption summary table.

  Using the above method, the master data maintenance process is not installed when the client is not available in the network. Inconsistent data is not passed to the client. The disclaimer summary table is used to determine which clients should be temporarily prohibited from accessing the object until the integrity check is complete.

[Consistency and organizational units]
The attribute of the data object will be “organizational unit”. Data created for an organizational unit will only be relevant to certain clients. For example, when planning data for the first manufacturing plant is created, that data is only needed by the application that performs the planning for the first manufacturing plant (eg, senior planner and optimizer applications) It will be independent of the planning application that implements the plan for the manufacturing plant.

  The integration server 109 passes the data only to clients to which the data is related. The consistency check is performed by those clients. If the message processed by the integration server 109 contains references to two organizations, the message can be split into two small messages, each of which is used to perform a consistency check. Will be done. This method can also be used to route data to different clients depending on attributes other than organizational units.

  Sometimes the data is not rotated accurately. Therefore, the client is designed to react to irrelevant data in a manner that does not disrupt the normal operation of the client. For example, if the planning application for the second manufacturing plant receives data for the first manufacturing plant, the planning application needs to ignore this data before returning an error to the integrity verification process.

[Add client]
When a new client with a new consistency request is added to the hybrid system 100, a client consistency check is performed on all master data before the new client can access the data.

  The new client is registered with the integration server 109 and issues a matching interface that indicates which attributes to match. The new client is placed in the disclaimer summary table for all data so that the new client is not accessed until the integrity check is complete. A workflow similar to workflow 212 (FIG. 6) is initiated to perform a consistency check against the new client.

[search]
When the client searches for master data, the request is routed to the master data server 110. Initially, the master data server 110 returns a table of search results with a few important fields (eg, short descriptions) to the client. If the client needs more information on all or some of the search results, the client uses the read process (described below) to access more information. The application programming interface (API) of the master data server 110 used for the search is designed to present a number of possibilities covering the search choices required by the client.

  When a client requests to read data in the master database 112, the request is routed to the master data server 110. For example, there are two types of read processing. One type of read-out process is a request for object identification information, called "get identification result", which is an object identifier and some descriptive parameters (for example, a short sentence for a product or a name for a business partner). return it. Another type of read process is a request for detailed information about an object, called “get details”, which returns all information related to the object.

  Each client will have its own definition of the attributes of the object, and the client will consider a portion of the object in the “get details” read process. Those attributes would be a subset of all attributes known within the master data server 110. It is possible that the master data server 110 has another, more general data model, and therefore the client API needs to be mapped to the master data server API. This mapping is performed in the application integration layer.

[Delete]
Deletion of data in the master database 112 can be executed in two stages. Initially, each client is asked if there is a reference to the object. If there is no reference, read processing that attempts to read data associated with the object from the client will not be accepted thereafter, and the object will not be returned in any search results. Second, the object is stored in the master database 112 and deleted from it. The second stage is performed when all clients have stated that there are no references to the object. While other clients can still access and use the object, it is possible to “delete” the object with respect to one client (the second step was skipped).

  Many processes allow navigation from a processing transaction to the master data associated with that transaction. For example, when a sales order for a product is created, the user looks at the product identifier and the product description. If the user wants to know more details, he can navigate to the interface showing the master data about the product to see other attributes.

  There are two cases when the client connection is loose, as in the example shown in FIG. If the client has its own master data user interface, that master data user interface should be used to display the product's master data. If the client does not have its own user interface, the master data server 110 user interface is used.

[Communication between applications]
FIG. 6 shows the interrelationship between the application and master data such as product master data. The user creates an order 220 for the product using the user interface 218. A user uses a search application to find a product with various attributes (eg, permanent key, description, product type). After the user enters data into the input screen, the search application checks to see if the product exists. The search application calls a product API 222 that accesses the product master database 112. If the search application finds a product, a short description of that product appears on the user interface. After the user has entered the order data, the user saves the data. When the order data is saved, a link (or reference) to the master data for the product is created. In some cases, product attributes are updated as needed.

[Communications between software layers]
FIG. 7 illustrates communication between the client system 224 and the software layer of the master data server 110. The client system 224 includes a user interface 226, a business server layer 228, a persistence service layer 230, and a master database 232. Similarly, the master data server 110 includes a user interface 234, a business service layer 236, a continuation service layer 238, and a database 240. The client system 224 and the master data server 110 have a hierarchical software architecture. Each layer has access to the functions of the layers immediately below each system. When the client system 224 needs to access data in the database 240 of the master data server 110, the business service layer 228 of the client 224 communicates with the business service layer 238 of the master data server 110 to access the master data. To do.

  Only the master data server 110 accesses the master data in the master database 240. In one mode of operation, the client system 224 does not maintain master data and uses its own continuation service 230 for only client-specific processing data. For example, by using a portal, user interfaces 226 and 234 can be integrated and a user can link or navigate from user interface 226 to user interface 234.

  The user interface 226 and business service layer 228 of the client system 224 can access the business service layer 236 of the master data server 110 directly, for example through an exchange interface or web service.

  The continuation service layer 230 of the client system 224 can delegate the continuation of master data using the business service layer 236 of the master data server 110.

  A user of the client system 224 may decide to access the master database 240 from the business service layer 228 (through link 242), or the continuation service layer 230 (through link 244), depending on architectural requirements. The advantage of connecting from the continuation service layer 230 is that the number of services in the continuation service layer 230 is typically less than the number of services in the business service layer 228. As a result, the client system 224 is adapted with little effort to gain access to the master database 240. Another advantage of connecting from the continuation service layer 230 is that by accessing the master data server 110 from the continuation service layer 230, the business service layer 228 is configured independently regardless of where the data is stored. It is a point that can be. This makes it easier to implement the hybrid architecture shown in FIG.

[Hybrid data storage on the client side]
In one embodiment of a hybrid information technology system, how a client accesses master data depends on how the client is configured. If the client is a single system, the master data is stored directly in the client's database. If the client runs in a distributed environment with a master data server, the master data continuity of the master data server is used.

  From the point of view of the software being developed, it is advantageous to implement only one software “instance” of the master data, which is used in different systems—ie distributed environments as well as in integrated deployment scenarios. be able to. This reduces development and maintenance costs and allows customers to provide a single piece of software.

  “Hybrid software” for accessing master data can be developed using the architecture shown in FIG. The continuation server layer 230 is designed to allow access to either the local database 232 or the remote master database 240 through the business service layer 236 of the master data server 110. This makes it possible to determine whether the data is maintained locally or remotely in customizing the software on the client side.

[Master data mapping]
Master data is exchanged between the client system and the master data server using messages. The integration server is responsible for message routing and mapping. The integration server has information about the client and can select the appropriate one for message mapping and data types and interfaces.

  The advantage of using an integrated server is that no code needs to be added on the client system or the master data server. Mapping rules are maintained and stored on the integrated server. In one example, the mapping rules are developed by a person developing a client application.

[Access master data from clients]
Referring to FIG. 9, the master data server 114 includes a product data module 288 that manages product data. Product data module 288 includes user interface component 282, application programming interface component 284, and master database 286. The client application 250 accesses the product data module 288 by calling the master data broker 284, which performs cache functions and authorization checks, and stores locally stored data. To access (if the client is configured as a single system) or to access remotely stored data (if the client is configured to interact with the master data server). When the client 110 interacts with the master data server, some data may also be stored in a cache locally (eg, in the memory of the client 110).

  Master data broker 252 includes product server component 290, exchange interface proxy 292 and localized master database 296. Product server component 290 provides an application programming interface that application 250 can call. If client 110 is a single system, product server component 290 can access data stored in localized master database 296 through path 298. If the client 110 is configured to interact with the master data server 114, the product service component 290 can communicate with the exchange interface proxy 292 through the path 300. The exchange interface proxy 292 communicates with the application programming interface 284 of the master data server 114 through the exchange interface 126 of the integration server 109. Application programming interface 284 is used to access master data stored in master database 286. Whether the client 110 is configured as a single system or as part of a network system that interacts with the master data server 114, the master data can be either the local master database 290 or the master database 286. Are maintained in one database.

[Links between data objects]
Master data objects and processing objects can be associated with certain semantics. The execution is performed by a pattern such as the relationship of the time-dependent attribute n: m of, for example, general customer relationship management interlinkage.

  Master data is stored on the master data server 110. The determination of whether the link between master data objects should be stored on the master data server 110 depends on the usage of the link in the connected client. If link semantics are required for many systems, the link must be stored on the master data server 110.

  In general, the master data server 110 does not know (or does not store) processing data. Accordingly, the client 114 is responsible for maintaining a link from the process data to the referenced master data.

  Sometimes it will be necessary to maintain a link to the processing data on the master data server 110. It is common to implement such a link on the master data server 100.

Data caching
Master data read access occurs more frequently than other processes of master data and is often part of an application where speed is important. By caching the data on the client side, the read access operation can be performed at a higher speed.

  Different methods can be used to perform caching on the client. Which method is better depends on the architecture of the master data. One way is to cache the data in the integration server. In one method, the integration server can cache responses to message read operations. If the same message is sent again, the response can be sent from the cache. Alternatively, caching can be performed at the message level. Messages are cached by the master data application. In yet another method, the object model is cached. Often, client master data transactions have a cache mechanism. This cache can also be used when communicating with the master data server.

  In order to get proper caching results, the cached content needs to be split between client sessions. Typically this is accomplished by continuing the cache on the database. Using a new standard technique for partitioned objects, the cache in memory can also be partitioned to improve performance.

  If a continuous cache is used, the client will record the last access time so that old entries are removed from the cache.

  Cached data needs to be invalidated when the data is no longer useful. Since master data rarely changes, a better way is to use an explicit invalidation method rather than periodic invalidation. When the master data changes, this information is communicated to all clients and everyone can invalidate their cache. The client can also re-read all invalidated data at a convenient time, such as at night. Caching can be offered on the server side. Performance will improve as a result of caching divided between sessions.

[Check permissions]
The user plays an important role in checking authority. The user is entitled to request an object or object type. One way is to have all users on the master data server from all clients. User rights can be granted on the master data server as usual. This method tends to increase system management. Another way is to have all authorization checks on the client and the master data server to return all requested data. While this method is simpler from a user management perspective, it makes it more difficult to implement a consistent authority concept.

  The master data server uses a two-level authority architecture. In the first stage, the master data server assigns authority to the client system. In the second stage, the client system further assigns a level of authority to the client user or the processing being executed on the client. For example, a sales client system can have the authority to read general data and sales data, as well as the authority to change sales data. Other client systems can have the authority to read general data and sales data without having the authority to change the sales data. A particular user of a sales client system may be authorized to read general data and sales data for a specific product. A user on a client cannot have a higher authority level than the client has to access master data.

  The method described above is used when data is accessed through a client. When a user navigates directly to the master data server, it is necessary to log on as a user on the master data server. The user is granted a certain level of authority based on the user's current status.

[Results of master data management]
The following describes some results of using a master data server to store data.

  The master data server is designed to meet the demands of many clients. The master data software is flexibly designed to allow storage of attributes that are not known prior to configuration at the client site. The same method can be used for all master data using the Easy Extension Workbench provided by SAP.

  A framework for checking consistency is provided so that the client can check the consistency of the data.

  The software is written in a mixed manner so that the storage of master data can be performed locally or remotely depending on the connection of the system.

[principle]
Table 1 shows an example of principles for supporting dynamic access to a central master data server.

  There are several dangers in realizing a system in which master data is stored centrally in a master database maintained by the master data server. The integration server and master data server must have high usability (absolute security). If the master data server is not available, processing based on the master data can no longer be performed. To mitigate the damage caused by the failure of the master data server, a local caching mechanism is put on the client. Processing stops due to an error in the master data. Therefore, the mapping of master data must never be wrong. All objects must be mapped correctly and all necessary attributes must be mapped correctly. Transaction consistency between systems is difficult to achieve. Data should be modeled so that it does not require delegation of two phases. Application customization at the client must be harmonized. Master data models and implementations need to provide the flexibility to extend master data in such a way that every client can be given special attributes.

  The processing for dynamic access to the master data can be realized by digital electronic circuits, computer hardware, firmware, software, or a combination thereof. The device for dynamic access to the master data is realized in a computer program product that is clearly embodied in an information means, for example in a machine-readable storage device or in a propagation signal running on a programmable processor. can do. Method steps for dynamic access to master data may be performed by a programmable processor executing a program of instructions that perform the functions of the present invention by operating on input data and generating output. it can. Processing of dynamic access to master data advantageously includes at least one programmable processor coupled to receive data and instructions therefrom and to send data and instructions thereto, a data storage system, It can be executed in one or more computer programs that are executable on a programmable system including at least one input device and at least one output device. A computer program is a set of instructions that can be used directly or indirectly in a computer to perform an action or derive a result. Computer programs can be written in any form of programming language, including compiled and interpreted languages, and computer programs can be arranged in any form, including And other units suitable for use as stand-alone programs or as modules, parts or subroutines, or within a computer environment.

  Suitable processors for execution of a program of instructions include, by way of example, a general purpose or special purpose microprocessor, a single processor or one of a number of processors of any type of computer. In general, one processor receives instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data. Generally, a computer also includes or is operably coupled to communicate with one or more mass storage devices for storing data files, including an internal hard disk or A magnetic disk such as a movable disk, a magneto-optical disk, and an optical disk are included. Clearly suitable storage devices for embodying computer program instructions and data include all forms of non-volatile memory, including, for example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices. And a magnetic disk such as an internal hard disk and a movable disk, a magneto-optical disk, a CD-ROM, and a DVD-ROM disk. The processor and memory can be supplemented by, or incorporated in, an ASIC (Application Specific Integrated Circuit).

  An example of such a computer is shown in FIG. 10, where a block of a processing system 256 suitable for implementing processing for dynamic access of master data is shown. The system 256 includes a processor 258, a random access memory (RAM) 260, a program memory 262 (eg, a writable read-only memory (ROM) such as a flash ROM), a hard drive controller 264, a video A controller 266 and an input / output (I / O) controller 268 coupled to a processor (CPU) bus 270 are included. The system 256 can be programmed in advance in, for example, a ROM, or by loading a program from another data source (eg, from a floppy disk (registered trademark), a CD-ROM, or another computer). (Also pre-programmed).

  The hard drive controller 264 is coupled to a hard disk 272 suitable for storing executable computer programs, including programs for executing master data software. Video controller 266 is coupled to a display device 274 for displaying a graphical user interface. I / O controller 268 is coupled to I / O interface 278 using I / O bus 276. The I / O interface 278 receives and sends data in analog or digital form over communication links such as serial links, local area networks, wireless links and parallel links.

  Also coupled to the I / O bus 276 is a keyboard 280. Alternatively, separate connections (separate buses) can be used for the I / O interface 278 and the keyboard 280. Processing of dynamic access of master data includes back-end components such as data servers, or includes middleware components such as application servers or interface servers, or has a graphical user interface, Internet browser, or a combination thereof It can be implemented in a computer system that includes front-end components such as a client computer. The components of the system can be connected in any form or medium of digital data communication such as a communication network. Examples of communication networks include, for example, a local area network (“LAN”), a wide area network (“WAN”), and the Internet.

  The computer system includes a client and a server. A client and server are generally remote from each other and typically interact through a network as previously described. The relationship between the client and the server is generated based on computer programs that are executed on each computer and have a client-server relationship with each other.

  The present invention has been described with respect to particular embodiments. Other embodiments are within the scope of the appended claims. For example, the steps of the present invention can be performed in a different order and still achieve the desired results.

  A number of embodiments of the invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. For example, the integration server 109 and the master data server 110 may be physically in the same computer. The present invention can be applied to all kinds of data shared between two computers, and is not limited to “master data”. The data may be general data or application data. Accordingly, other embodiments are within the scope of the appended claims.

DESCRIPTION OF SYMBOLS 100 ... Hybrid system 102-106 ... Client system 109 ... Integrated server 110 ... Master data server 112 ... Master database 114 ... Client 116 ... Sales application 118 ... Manufacturing application 120 ... Product user interface 124 ... Product service layer 126 ... Exchange interface 128 ... Application A
130: Application B
132 ... Product user interface 134 ... Product service layer

Claims (41)

In the method of maintaining data,
Receiving an identifier and data associated with the object identified by the identifier;
For each client, the server verifies that the identifier and data conform to the set of rules defined by the client;
The server entering the identifier and data into the database, wherein the server is configured to maintain a database accessible to the client.   The method of claim 1, wherein the data comprises attribute values associated with an object.   Claiming that the identifier and database conform to the set of rules comprises the server confirming that the data conforms to a client-defined subset of rules associated with the attributes of the object. Item 3. The method according to Item 2.   The method of claim 3, wherein the subset of rules comprises a rule for defining a format that is within an acceptable range of attribute values.   Verifying that the identifier and data conform to the set of rules includes the server confirming that the identifier conforms to a client-defined subset of rules associated with identifying the object. The method of claim 1 wherein:   6. The method of claim 5, wherein the set of rules comprises rules defining a format that is within an acceptable range of identifiers.   The method of claim 1, further comprising the step of the server linking data to the identifier. In addition, the client sends a request to the server requesting data linked to the identifier;
8. The method of claim 7, comprising the step of the server converting data in the database linked to the identifier into a client acceptable format. The server sends a request to the second server;
The second server determines which clients can access the database;
The second server further comprises the step of routing the request to a client identified as being able to access the database, the request requesting identification of the identifier and data. Method.   The method of claim 1, wherein the object is a product.   The method of claim 1, wherein the object is a business partner.   The method of claim 1, wherein the server interacts with the client using messages written in an extensible markup language. In addition, for each client,
Sending a request to the client to verify that the identifier and database meet the set of rules defined by the client;
If a particular client does not respond, the server places the client on the disclaimer table and informs that its identifier and data could not be verified as conforming to the set of rules defined by the particular client The method of claim 1, comprising:   Other attempts to ensure that identifiers and data conform to a set of rules defined by a particular client are after a certain length of time or when a particular client attempts to access data in the database 14. The method of claim 13, wherein the method is sometimes performed. In a method for maintaining data,
The client sends a request to the server for a set of data related to an object;
The client receives a message that only the client can modify the data set because the server has fixed the data set,
Sending the modified set of data to the server to store the modified data in the database;
The client receives a message that the modified data has been saved to the database,
For each of the other clients, the server determines which other clients can access the modified data;
A server confirming that the modified data conforms to a set of rules defined by the client, and wherein the set of data is stored in a database maintained by the server.   The method of claim 15, wherein the set of data comprises attribute values associated with an object.   The method of claim 16, wherein the set of rules defined by the client comprises rules for defining a format that is within an acceptable range of attribute values.   The server compares the attributes with the checklist issued by the client to determine which other clients can access the modified data, and each checklist indicates which attributes are accessible to the client The method according to claim 16.   The method of claim 15, wherein the object is a product.   The method of claim 15, wherein the object is a business partner.   The method of claim 15, wherein the server interacts with the client using a message comprising code written in an extensible markup language. In a machine readable medium storing a computer program for dynamic access of master data stored in a database accessible to a client,
For programmable processors,
Causing the server to receive data associated with the identifier and the object identified by the identifier;
For each client, let the server check that the identifier and data conform to the set of rules defined by the client,
A machine-readable medium storing a computer program comprising instructions operable to cause a server to enter an identifier and data into a database.   The machine-readable medium storing a computer program according to claim 22, wherein the data includes an attribute value related to the object.   The instructions are operable to cause a programmable processor to cause a server to verify that data conforms to a subset of rules defined by the client in relation to object attributes. A machine-readable medium storing the computer program according to Item 23.   25. A machine-readable medium storing a computer program according to claim 24, wherein the rule subset includes a rule for defining a format within an allowable range of attribute values.   The instructions are operable to cause a programmable processor to cause a server to confirm that the identifier conforms to a subset of rules defined by the client in connection with object identification. A machine-readable medium storing the computer program according to claim 22.   27. A machine-readable medium storing a computer program according to claim 26, wherein the set of rules includes a rule for defining a format within an allowable range of identifiers.   23. A machine-readable medium storing a computer program as recited in claim 22, wherein the instructions are operable to cause a program-controllable processor to cause a server to link data to an identifier.   The instructions cause the programmable processor to cause the client to send a request for data linked to the identifier to the server, which causes the data in the database linked to the identifier to be in a format acceptable to the client. 29. A machine-readable medium having stored thereon a computer program according to claim 28, wherein the computer-readable medium is operable to convert the computer program.   23. A machine-readable medium storing a computer program according to claim 22, wherein the object is a product.   23. A machine-readable medium storing a computer program according to claim 22, wherein the object is a business partner.   The machine-readable medium storing a computer program according to claim 22, wherein the server communicates with the client using a message written in an extensible markup language. The instructions are for program-controllable processors:
Have the server send each client a request to verify that the identifier and data conform to the set of rules defined by the client, and if a particular client does not respond, list that client 23. The computer program product of claim 22, wherein the computer program is operable to inform that the identifier and data have not been confirmed to conform to a set of rules defined by a particular client. A machine-readable medium on which is stored.   The instructions may cause the programmable processor to make another attempt to verify that the identifier and data conform to a set of rules defined by a particular client, after a predetermined amount of time, or for a particular client. 34. A machine-readable medium having stored thereon a computer program as recited in claim 33, wherein the computer program is operable to cause a server to initiate when attempting to access data in a database. In a machine readable medium storing a computer program for dynamic access of master data,
For a computer system with a client and server,
Have the first client send a request to the server for changes to the set of data associated with the object,
Let the server receive a message that only the client can change the data set because the server has fixed the data set,
Have the first client send a modified set of data to the server to save the data in the database,
With instructions operable to cause the first client to receive a message that the modified set of data has been stored in the database;
The server determines for each of the other clients which other clients can access the modified set of data and that the modified set of data conforms to the set of rules defined by the client. A machine-readable medium storing a computer program characterized by being confirmed.   36. A machine-readable medium storing a computer program as recited in claim 35, wherein the set of data includes attribute values associated with an object.   37. A machine-readable medium storing a computer program according to claim 36, wherein the set of rules defined by the client includes rules for defining a format within an allowable range of attribute values.   The instructions are operable to cause a computer system to cause a server to compare an attribute value with a checklist issued by a client, each checklist indicating an attribute accessible to the client. A machine-readable medium storing the computer program according to Item 36.   36. A machine-readable medium storing a computer program according to claim 35, wherein the object is a product.   36. A machine-readable medium storing a computer program according to claim 35, wherein the object is a business partner.   36. A machine storing a computer program according to claim 35, wherein the instructions are operable to cause the server to interact with the client using a message comprising code written in an extensible markup language. A readable medium.

Images