Source: http://www.google.com/patents/US20010042092?ie=ISO-8859-1&dq=6,263,507
Timestamp: 2014-10-02 00:21:51
Document Index: 462451045

Matched Legal Cases: ['art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 40', 'art 70', 'art 70', 'art 70', 'art 70', 'art 70', 'art 70', 'art 70', 'art 70', 'art 70', 'art 70']

Patent US20010042092 - Collaboration apparatus between information processing systems, integrated ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign in<nobr>Advanced Patent Search</nobr>PatentsThe present invention relates to a collaboration apparatus between information processing systems for allowing a plurality of information processing systems to collaborate with each other without awareness of the difference in architecture, and an integrated information processing system in which a plurality...http://www.google.com/patents/US20010042092?utm_source=gb-gplus-sharePatent US20010042092 - Collaboration apparatus between information processing systems, integrated information processing system, and recording medium storing a collaboration program between information processing systemsAdvanced Patent SearchPublication numberUS20010042092 A1Publication typeApplicationApplication numberUS 09/874,283Publication dateNov 15, 2001Filing dateJun 6, 2001Priority dateDec 7, 1998Also published asUS7571443, US20070088783, WO2000034868A1Publication number09874283, 874283, US 2001/0042092 A1, US 2001/042092 A1, US 20010042092 A1, US 20010042092A1, US 2001042092 A1, US 2001042092A1, US-A1-20010042092, US-A1-2001042092, US2001/0042092A1, US2001/042092A1, US20010042092 A1, US20010042092A1, US2001042092 A1, US2001042092A1InventorsAkira Kudo, Haruko SotaOriginal AssigneeFujitsu LimitedExport CitationBiBTeX, EndNote, RefManReferenced by (5), Classifications (8), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetCollaboration apparatus between information processing systems, integrated information processing system, and recording medium storing a collaboration program between information processing systemsUS 20010042092 A1Abstract The present invention relates to a collaboration apparatus between information processing systems for allowing a plurality of information processing systems to collaborate with each other without awareness of the difference in architecture, and an integrated information processing system in which a plurality of information processing systems are combined by using such a collaboration apparatus between information processing systems. In the case of allowing an SFA system (30) to collaborate with an EPR system (10) in the integrated information processing system including a plurality of information systems, an intersystem collaboration object (40) of the collaboration apparatus between information processing systems generates an active role (51) corresponding to a system of a collaboration origin and a passive role (52) corresponding to a system of a collaboration target, generates a relating object (53) between these roles in accordance with collaboration information defining a communication method between information systems, and transmits a transaction between the active role (51) and the passive role (52). Images(19) Claims(10)
BRIEF DESCRIPTION OF DRAWINGS [0029]FIG. 1 is a block diagram showing a schematic configuration of an integrated information processing system of Embodiment 1 according to the present invention. [0030]FIG. 2 is a block diagram showing a schematic configuration of a collaboration apparatus between information processing systems provided in the integrated information processing system. [0031]FIG. 3 is a diagram illustrating exemplary information stored in a collaboration information storage table of the collaboration apparatus between information processing systems. [0032]FIG. 4 is a schematic diagram showing a state of intersystem collaboration processing in the integrated information processing system. [0033]FIG. 5 is a flow chart showing a procedure of the intersystem collaboration processing. [0034]FIG. 6 is a diagram illustrating an exemplary format of data passed among respective systems in the integrated information processing system. [0035]FIG. 7 is a diagram illustrating exemplary information stored in a collaboration information storage table of a collaboration apparatus between information processing systems in an integrated information processing system of Embodiment 2 according to the present invention. [0036]FIG. 8 is a schematic diagram showing a state of intersystem collaboration processing in the integrated information processing system of Embodiment 2. [0037]FIG. 9 is a flow chart showing a partial procedure of the intersystem collaboration processing in the integrated information processing system of Embodiment 2. [0038]FIG. 10 is a flow chart showing a continuation of the processing procedure shown in the flow chart in FIG. 9. [0039]FIG. 11 is a block diagram showing an exemplary program as a collaboration information processing procedure in the integrated information processing system of Embodiment 3 according to the present invention. [0040]FIG. 12 is a diagram illustrating exemplary information stored in a collaboration information storage table of a collaboration apparatus between information processing systems in the integrated information processing system of Embodiment 3. [0041]FIG. 13 is a schematic diagram showing a state of intersystem collaboration processing in the integrated information processing system of Embodiment 3. [0042]FIG. 14 is a flow chart showing a procedure of intersystem collaboration processing in the integrated information processing system of Embodiment 3. [0043]FIG. 15 is a block diagram showing a schematic configuration of an integrated information processing system of Embodiment 4 according to the present invention. [0044]FIG. 16 is a diagram illustrating exemplary information stored in a collaboration information storage table of a collaboration apparatus between information processing systems in the integrated information processing system of Embodiment 4. [0045]FIG. 17 is a block diagram showing a schematic configuration of a collaboration apparatus between information processing systems provided in the integrated information processing system of Embodiment 4. [0046]FIG. 18 is a schematic diagram showing a state of intersystem collaboration processing in the integrated information processing system of Embodiment 4. [0047]FIG. 19 is a flow chart showing a procedure of intersystem collaboration processing in the integrated information processing system of Embodiment 4.
BEST MODE FOR CARRYING OUT THE INVENTION Embodiment 1 [0048] Hereinafter, the present invention will be described by way of an embodiment with reference to the drawings. [0049]FIG. 1 is a diagram illustrating a configuration of an integrated information processing system in which a plurality of systems (information processing means) are integrated by a collaboration apparatus between information processing systems of the present invention. [0050] As shown in FIG. 1, the integrated information processing system has a configuration in which three information processing systems, each being operated independently: an integrated transaction package (hereinafter, referred to as an �ERP�) system 10, a supply chain management (hereinafter, referred to as an �SCM�) system 20, and a sales force automation (hereinafter, referred to as an �SFA�) system 30 are combined through an intersystem collaboration object 40. [0051] The integrated information processing system further includes a collaboration information storage table 41 storing collaboration information among the ERP system 10, the SCM system 20, and the SFA system 30. The intersystem collaboration object 40 allows the systems to collaborate with each other by referring to the collaboration information in the collaboration information storage table 41. More specifically, in the present embodiment, the intersystem collaboration object 40 and the collaboration information storage table 41 constitute the collaboration apparatus between information processing systems. [0052] The ERP system 10 is composed of a plurality of subsystems such as a sales subsystem 10 a, an accounting subsystem 10 b, a stock management subsystem 10 c, and a production collaboration subsystem 10 d. More specifically, upon receiving an order for goods, the sales subsystem 10 a conducts processing of issuing an order intake slip, and the accounting subsystem 10 b issues a debit note. Furthermore, the stock management subsystem 10 c confirms the presence/absence of the stock of ordered goods. In the case where the stock of the goods has run out, the production collaboration subsystem 10 d creates data for requesting the production of the goods to request collaboration with the SCM system 20. [0053] The SCM system 20 globally manages things and information throughout the entire distribution process including the acquirement of raw materials, production, and delivery to customers, so as to optimize the entire process. The SCM system 20 may also be composed of a plurality of subsystems in the same way as in the ERP system 10. [0054] The SFA system 30 supports a person in charge of business, and has functions of a help desk, sales prediction, contact management, and the like. The SCM system 20 may also be composed of a plurality of subsystems in the same way as in the ERP system 10. [0055] As shown in FIG. 2, the intersystem collaboration object 40 includes a table access part 40 a for accessing the collaboration information storage table 41 to obtain collaboration information therefrom, a role object generating part 40 b (role object generating means) for generating a role object described later, and a relating object generating part 40 c (relating object generating means) for generating a relating object for collaboration between role objects. [0056] Herein, the collaboration information referred to by the intersystem collaboration object 40 in the integrated information processing system will be described. As shown in FIG. 3, the collaboration information storage table 41 of the present embodiment stores, as collaboration information, paths for transactions transmitted among the ERP system 10, the SCM system 20, and the SFA system 30, and a communication method thereof. [0057] In an example shown in FIG. 3, the communication method of a transaction from the SFA system 30 to the ERP system 10 is a real method in which communication is conducted immediately. The communication method of a transaction from the ERP system 10 to the SCM system 20 is a delayed batch method in which a transmission origin accumulates data without depending upon the state of a transmission target, and the transmission target conducts processing asynchronously to the transmission origin, if required. [0058] The example in FIG. 3 is shown merely for illustrative purpose. The communication method of a transaction from the SFA system 30 to the SCM system 20, and the communication method of a transaction from the ERP system 10 to the SFA system 30, and the like are not defined. However, collaboration between these systems should be defined, if required. The communication method also includes a batch method in which a unified amount of data is communicated at predetermined time, in addition to the above-mentioned real method and delayed batch method. [0059] The above-mentioned transaction is a generic name for data transmitted among systems, which is a concept containing arbitrary data such as a character string and a file. [0060] Hereinafter, intersystem collaboration processing in the integrated information processing system will be described with reference to FIGS. 4 and 5. [0061] First, when a person in charge of business receives an order for goods from a customer in the SFA system 30, the SFA system 30 requests the intersystem collaboration object 40 to generate a role object for collaboration with the ERP system 10 (Step S1). [0062] In the intersystem collaboration object 40 receiving the abovementioned request, the role object generating part 40 b generates an active role 51 as an object corresponding to the SFA system 30, and generates a passive role 52 as an object corresponding to the ERP system 10 that is a collaboration target (Step S2). The active role 51 thus generated is an object to be a transmission origin of the transaction, and the passive role 52 is an object to be a transmission target of the transaction. [0063] Furthermore, the relating object generating part 40 c of the intersystem collaboration object 40 generates a relating object 53 between the active role 51 and the passive role 52 generated at Step S2 (Step S3). The relating object 53 thus generated conducts collaboration of �transmitting a transaction from the active role 51 to the passive role 52� between the active role 51 and the passive role 52. [0064] Furthermore, the relating object 53 thus generated has a communication method of a transaction as an attribute. For example, in the case of the above-mentioned active role 51 and passive role 52, the active role 51 corresponds to the SFA system 30, and the passive role 52 corresponds to the ERP system 10. Therefore, the relating object generating part 40 c allows the table access part 40 a to refer to the collaboration information storage table 41, thereby obtaining a �real method� as an attribute of the relating object 53 (Step S3). [0065] Next, the SFA system 30 specifies data which the SFA system 30 desires to transmit as a transaction, with respect to the intersystem collaboration object 40 (Step S4). Herein, data representing the contents of the order received from the customer in the SFA system 30 is specified. [0066] The intersystem collaboration object 40 allows a transaction to be communicated between the active role 51 and the passive role 52 in accordance with the attribute of the relating object 53 (Step S5). Because of this, the data representing the contents of the order received from the customer is transmitted from the active role 51 (SFA system 30) to the passive role 52 (ERP system 10) as a transaction by the real method. [0067] Next, in the ERP system 10 receiving this data, the sales subsystem 10 a conducts processing of issuing an order intake slip (Step S6). Furthermore, the accounting subsystem 10 b issues a debit note (Step S7). Then, the stock management subsystem 10 c confirms the presence/absence of stock of the ordered goods (Step S8). [0068] If there is some stock of the ordered goods (the result of Step S8 is YES), another processing of, for example, issuing a delivery slip and an invoice is conducted. On the other hand, if the stock of the ordered goods has run out (the result of Step S8 is NO), the production collaboration subsystem 10 d creates data for requesting the production of the goods, and requests the intersystem collaboration object 40 to generate a role object for collaboration with the SCM system 20 (Step S9). [0069] In the intersystem collaboration object 40 receiving the abovementioned request, the role object generating part 40 b generates an active role 54 as an object corresponding to the ERP system 10, and generates a passive role 55 as an object corresponding to the SCM system 20 that is a collaboration target (Step S10). The active role 54 thus generated is an object to be a transmission origin of a transaction, and the passive role 55 is an object to be a transmission target of the transaction. [0070] Furthermore, the relating object generating part 40 c of the intersystem collaboration object 40 generates a relating object 56 between the active role 54 and the passive role 55 generated at Step S10 (Step S11). The relating object 56 thus generated conducts collaboration of �transmitting a transaction from the active role 54 to the passive role 55� between the active role 54 and the passive role 55. [0071] Furthermore, the relating object 56 thus generated has a communication method of a transaction as an attribute. For example, in the case of the active role 54 and the passive role 55, the active role 54 corresponds to the ERP system 10, and the passive role 55 corresponds to the SCM system 20. Therefore, the relating object generating part 40 c allows the table access part 40 a to refer to the collaboration information storage table 41, thereby obtaining a �delayed batch method� as an attribute of the relating object 56 (Step S11). [0072] Next, the ERP system 10 specifies data which the ERP system 10 desires to transmit as a transaction, with respect to the intersystem collaboration object 40 (Step S12). Herein, the data created at Step S9 for requesting the production of out-of-stock goods is specified. [0073] The intersystem collaboration object 40 allows a transaction to be communicated between the active role 54 and the passive role 55 in accordance with the attribute of the relating object 56 (Step S13). Because of this, data for requesting the production of out-of-stock goods is transmitted from the active role 54 to the passive role 55. Regarding this data transmission, the attribute of the relating object 56 is a delayed batch method; therefore, the ERP system 10 accumulates data for requesting the production of out-of-stock goods without depending upon the state of the SCM system 20. [0074] Furthermore, the SCM system 20 receiving data from the ERP system 10 conducts required processing such as acquirement of raw materials for producing the goods asynchronously to the ERP system 10 (Step S14). [0075] Because of the above-mentioned procedure, the integrated information processing system of the present embodiment realizes collaboration between the respective systems. [0076] Herein, FIG. 6 shows an exemplary format of data passed among the systems as a transaction in the integrated information processing system. [0077] As shown in FIG. 6, the data passed as a transaction consists of an attribute tag Tn an update flag Fn, and a data part Dn (n is a natural number). [0078] A number representing an attribute of the data part Dn is placed in the attribute tag Tn. This number is common in the integrated information processing system and defined as follows: for example, in the case where the attribute of data of the data part Dn is a user ID, �1� is placed in the attribute tag Tn; in the case where the attribute of data of the data part Dn is a user name, �2� is placed in the attribute tag Tn. [0079] Furthermore, a number representing the acceptance/rejection of an update of the contents of the data part Dn in the system of a transmission target of the transaction is placed in the update flag Fn. This number is also common in the integrated information processing system and defined as follows: for example, in the case where an update of the data part Dn is required in the system of the transmission target, �1� is placed in the update flag Fn; in the case where the data part Dn may be updated if required, �2� is placed in the update flag Fn; in the case where an update of the data part Dn is prohibited, �3� is placed in the update flag Fn. [0080] As described above, in the integrated information processing system of the present embodiment, the SFA system 10, the SCM system 20, or the like which attempts to transmit data for collaboration with another system makes a request of the intersystem collaboration object 40 for collaboration with another system, instead of directly transmitting data to a system of a collaboration target by using file transfer as in the prior art. At this time, the intersystem collaboration object 40 generates role objects respectively corresponding to a system of a transmission origin and a system of a transmission target, and generates a relating object representing the relationship between the role objects, thereby realizing collaboration between two systems. [0081] Because of this, each system in the integrated information processing system can transmit data without awareness of the architecture of a system of a collaboration target. Furthermore, the processing of generation of an object for conducting collaboration between systems is centralized at the intersystem collaboration object 40. Therefore, in the case where collaboration between systems is changed, or a new system is added, the intersystem collaboration object 40 may merely be corrected. As a result, a plurality of information processing systems can be combined without awareness of the difference in architecture among these information processing systems, and a burden for integrating systems and configuring an intercompany collaboration system can be reduced. [0082] In the above-mentioned description, the case has been described in which, when each system requires collaboration with another system, each system autonomously requests the intersystem collaboration object 40 to generate a role object. However, the present invention is not limited thereto. It may also be possible that intersystem collaboration information is previously registered in the collaboration information storage table 41 in the order of transmission of transactions, and the intersystem collaboration object 40 refers to the collaboration information to successively transmit transactions. Embodiment 2 [0083] Hereinafter, the present invention will be described by way of another embodiment with reference to the drawings. [0084] In the integrated information processing system of the present embodiment, the processing of the intersystem collaboration object 40 described in Embodiment 1 is also applied to the collaboration between subsystems in the ERP system 10. More specifically, in the present embodiment, information processing means collaborate with each other on a subsystem basis. [0085] More specifically, the collaboration information storage table 41 referred to by the intersystem collaboration object 40 in Embodiment 2 stores collaboration information among subsystems of the ERP system 10, in addition to the collaboration information among the ERP system 10, the SCM system 20, and the SFA system 30, as exemplified in FIG. 7. [0086] In the example shown in FIG. 7, a �real method� is defined as an attribute of a relating object for collaboration from the sales subsystem 10 a to the accounting subsystem 10 b, a �real method� is defined as an attribute of a relating object for collaboration from the accounting subsystem 10 b to the stock management subsystem 10 c, and a �batch method� is defined as an attribute of a relating object for collaboration from the stock management subsystem 10 c to the production collaboration subsystem 10 d. In the same way as in FIG. 3, the example in FIG. 7 is merely shown for illustrative purpose. Collaboration between any subsystems can be defined, if required. [0087] Herein, a processing procedure for collaboration between subsystems of the ERP system 10 through the intersystem collaboration object 40 will be described with reference to FIGS. 8 to 10. This processing corresponds to the internal processings at Steps S6 to S9 in the flow chart of FIG. 5 described in Embodiment 1. [0088] In the ERP system 10, upon receiving data representing the contents of an order from a customer from the SFA system 30, the sales subsystem 10 a creates an order intake slip based on this data, and requests the intersystem collaboration object 40 to generate a role object for collaboration with the accounting subsystem 10 b (Step S21). [0089] In the intersystem collaboration object 40 receiving the abovementioned request, the role object generating part 40 b generates an active role 57 as an object corresponding to the sales subsystem 10 a, and generates a passive role 58 as an object corresponding to the accounting subsystem 10 b that is a collaboration target (Step S22). The active role 57 thus generated is an object to be a transmission origin of a transaction, and the passive role 58 is an object to be a transmission target of the transaction. [0090] Furthermore, the relating object generating part 40 c of the intersystem collaboration object 40 generates a relating object 59 between the active role 57 and the passive role 58 generated at Step S22 (Step S23). The relating object 59 thus generated conducts collaboration of �transmitting a transaction from the active role 57 to the passive role 58� between the active role 57 and the passive role 58. [0091] Furthermore, the relating object 59 thus generated has a communication method of a transaction as an attribute. For example, in the case of the above-mentioned active role 57 and passive role 58, the active role 57 corresponds to the sales subsystem 10 a, and the passive role 58 corresponds to the accounting subsystem 10 b. Therefore, the relating object generating part 40 c instructs the table access part 40 a to refer to the collaboration information storage table 41 shown in FIG. 7, thereby obtaining a �real method� as an attribute of the relating object 59 (Step S23). [0092] Next, the sales subsystem 10 a specifies data which the sales subsystem 10 a desires to transmit as a transaction, with respect to the intersystem collaboration object 40 (Step S24). Herein, the contents of the above-mentioned order intake slip is specified. At this time, the sales subsystem 10 a issues an order intake slip. This processing corresponds to Step S6 in FIG. 5. [0093] The intersystem collaboration object 40 allows a transaction to be communicated between the active role 57 and the passive role 58 in accordance with the attribute of the relating object 59 (Step S25). Because of this, the data representing the contents of the order intake slip is transmitted from the active role 57 to the passive role 58 as a transaction by the real method. [0094] Next, the accounting subsystem 10 b receiving the transaction issues a debit note based on the order intake slip transmitted from the sales subsystem 10 a by the transaction (Step S26). Step S26 corresponds to Step S7 in FIG. 5. [0095] Furthermore, in order to confirm the presence/absence of stock of the ordered goods, the accounting subsystem 10 b requests the intersystem collaboration object 40 to generate a role object for collaboration with the stock management subsystem 10 c (Step S27). [0096] In the intersystem collaboration object 40 receiving the abovementioned request, the role object generating part 40 b generates an active role 60 as an object corresponding to the accounting subsystem 10 b, and generates a passive role 61 as an object corresponding to the stock management subsystem 10 c that is a collaboration target (Step S28). The active role 60 thus generated is an object to be a transmission origin of a transaction, and the passive role 61 is an object to be a transmission target of a transaction. [0097] Furthermore, the relating object generating part 40 c of the intersystem collaboration object 40 generates a relating object 62 between the active role 60 and the passive role 61 generated at Step S28 (Step S29). The relating object 62 thus generated conducts collaboration of �transmitting a transaction from the active role 60 to the passive role 61� between the active role 60 and the passive role 61. [0098] Furthermore, the relating object 62 thus generated has a communication method of a transaction as an attribute. For example, in the case of the above-mentioned active role 60 and passive role 61, the active role 60 corresponds to the accounting subsystem 10 b, and the passive role 61 corresponds to the stock management subsystem 10 c. Therefore, the relating object generating part 40 c instructs the table access part 40 a to refer to the collaboration information storage table 41, thereby obtaining a �real method� as an attribute of the relating object 62 (Step S29). [0099] Next, the accounting subsystem 10 b specifies data which the accounting subsystem 10 b desires to transmit as a transaction, with respect to the intersystem collaboration object 40 (Step S30). Herein, the contents of the debit note created at Step S26 is specified. [0100] The intersystem collaboration object 40 allows a transaction to be communicated between the active role 60 and the passive role 61 in accordance with the attribute of the relating object 62 (Step S31). Because of this, the contents of the debit note is transmitted from the active role 60 to the passive role 61. This data transmission is conducted immediately since the attribute of the relating object 62 is a real method. [0101] Upon receiving the transaction from the accounting subsystem 10 b, the stock management subsystem 10 c checks the stock of the goods based on the contents of the debit note transmitted as the transaction (Step S32). Step S32 corresponds to Step S8 in FIG. 5. [0102] In the case where the stock of the ordered goods has run out, the stock management subsystem 10 c requests the intersystem collaboration object 40 to generate a role object for collaboration with the production collaboration subsystem 10 d (Step S33). [0103] In the intersystem collaboration object 40 receiving the abovementioned request, the role object generating part 40 b generates an active role 63 as an object corresponding to the stock management subsystem 10 c, and generates a passive role 64 as an object corresponding to the production collaboration subsystem 10 d that is a collaboration target (Step S34). The active role 63 thus generated is an object to be a transmission origin of a transaction, and the passive role 64 is an object to be a transmission target of a transaction. [0104] Furthermore, the relating object generating part 40 c of the intersystem collaboration object 40 generates a relating object 65 between the active role 63 and the passive role 64 generated at Step S34 (Step S35). The relating object 65 thus generated conducts collaboration of �transmitting a transaction from the active role 63 to the passive role 64� between the active role 63 and the passive role 64. [0105] Furthermore, the relating object 65 thus generated has a communication method of a transaction as an attribute. For example, in the case of the above-mentioned active role 63 and passive role 64, the active role 63 corresponds to the stock management subsystem 10 c, and the passive role 64 corresponds to the production collaboration subsystem 10 d. Therefore, the relating object generating part 40 c instructs the table access part 40 a to refer to the collaboration information storage table 41 shown in FIG. 7, thereby obtaining a �batch method� as an attribute of the relating object 65 (Step S35). [0106] Next, the stock management subsystem 10 c specifies data which the stock management subsystem 10 c desires to transmit as a transaction, with respect to the intersystem collaboration object 40 (Step S36). Herein, data on the goods whose stock is found to have run out during checking of stock at Step S32 is specified. [0107] The intersystem collaboration object 40 allows a transaction to be communicated between the active role 63 and the passive role 64 in accordance with the attribute of the relating object 65 (Step S37). Because of this, the data on goods whose stock is found to have run out is transmitted from the active role 63 to the passive role 64. This data transmission is conducted at predetermined time since the attribute of the relating object 65 is a batch method. [0108] After the data transmission is conducted, the production collaboration subsystem 10 d corresponding to the passive role 64 starts required processing such as preparation for production, based on the data, transmitted as a transaction, on goods whose stock is found to have run out. [0109] As described above, in the integrated information processing system of the present embodiment, each subsystem makes a request of the intersystem collaboration object 40 for collaboration with another subsystem, instead of directly transmitting data to a subsystem of a collaboration target. At this time, the intersystem collaboration object 40 generates role objects respectively corresponding to a subsystem of a transmission origin and a subsystem of a transmission target, and generates a relating object representing the relationship between the role objects, thereby realizing collaboration between two subsystems. [0110] Because of this, each subsystem in the integrated information processing system can transmit data without awareness of the architecture of a subsystem of a collaboration target. Furthermore, the processing of generation of an object for conducting collaboration between subsystems is centralized at the intersystem collaboration object 40. Therefore, in the case where collaboration between subsystems is changed, or a new subsystem is added, the intersystem collaboration object 40 may merely be corrected. As a result, a plurality of subsystems can be combined without awareness of the difference in architecture among these subsystems. [0111] In the above-mentioned description, the case has been described in which the collaboration information storage table 41 of the present embodiment stores collaboration information among systems such as the ERP system 10 and collaboration information among subsystems in parallel. However, it may also be possible to provide another collaboration information storage table in accordance with the granularity of systems. [0112] Furthermore, in the above-mentioned description, the case has been described in which, when each subsystem requires collaboration with another subsystem, each subsystem autonomously requests the intersystem collaboration object 40 to generate a role object. However, the present invention is not limited thereto. It may also be possible that collaboration information between subsystems is previously registered in the collaboration information storage table 41 in the order of transmission of transactions, and the intersystem collaboration object 40 refers to the collaboration information to successively transmit transactions. [0113] Furthermore, in the above-mentioned description, the case has been described in which the subsystems in the identical system (ERP system 10) collaborate with each other. However, it may also be possible that subsystems in different systems collaborate with each other. Embodiment 3 [0114] Hereinafter, the present invention will be described by way of still another embodiment with reference to the drawings. [0115] In the integrated information processing system of the present embodiment, the processing of the intersystem collaboration object 40 described in Embodiments 1 and 2 is also applied to the collaboration between programs. More specifically, in the present embodiment, the information processing means collaborate with each other on a program basis. [0116] Herein, as an example, as shown in FIG. 11, only the collaboration between an order receiving processing program 10 a 1 and an order placement processing program 10 a 2 operated on the sales subsystem 10 a of the ERP system 10 will be described. [0117] The collaboration information storage table 41 referred to by the intersystem collaboration object 40 in Embodiment 3 contains collaboration information defining the collaboration between the order receiving processing program 10 a 1 and the order placement processing program 10 a 2 as shown in FIG. 12. [0118] In the example shown in FIG. 12, a �real method� is defined as an attribute of a relating object for collaboration from the order receiving program 10 a 1 to the order placement processing program 10 a 2. [0119] Herein, a processing procedure for collaboration between programs through the intersystem collaboration object 40 will be described with reference to FIGS. 13 and 14. [0120] In the sales subsystem 10 a of the ERP system 10, upon receiving data representing the contents of an order from a customer from the SFA system 30, the order receiving processing program 10 a 1 creates an order intake slip based on this data, and requests the intersystem collaboration object 40 to generate a role object for collaboration with the order placement processing program 10 a 2 (Step S41). [0121] In the intersystem collaboration object 40 receiving the abovementioned request, the role object generating part 40 b generates an active role 66 as an object corresponding to the order receiving processing program 10 a 1, and generates a passive role 67 as an object corresponding to the order placement processing program 10 a 2 that is a collaboration target (Step S42). The active role 66 thus generated is an object to be a transmission origin of a transaction, and the passive role 67 is an object to be a transmission target of the transaction. [0122] Furthermore, the relating object generating part 40 c of the intersystem collaboration object 40 generates a relating object 68 between the active role 66 and the passive role 67 generated at Step S42 (Step S43). The relating object 68 thus generated conducts collaboration of �transmitting a transaction from the active role 66 to the passive role 67� between the active role 66 and the passive role 67. [0123] Furthermore, the relating object 68 thus generated has a communication method of a transaction as an attribute. For example, in the case of the above-mentioned active role 66 and passive role 67, the relating object generating part 40 c instructs the table access part 40 a to refer to the collaboration information storage table 41 shown in FIG. 12, thereby obtaining a �real method� as an attribute of the relating object 68 (Step S43). [0124] Next, the order receiving processing program 10 a 1 specifies data which the order receiving processing program 10 a 1 desires to transmit as a transaction, with respect to the intersystem collaboration object 40 (Step S44). Herein, the contents of the above-mentioned order receiving slip created at Step S41 is specified. [0125] The intersystem collaboration object 40 allows a transaction to be communicated between the active role 66 and the passive role 67 in accordance with the attribute of the relating object 68 (Step S45). Herein, as described above, since the attribute of the relating object 68 is a real method, the data representing the contents of the order intake slip is immediately transmitted from the active role 66 to the passive role 67. [0126] As described above, in the present embodiment, the collaboration between programs is also conducted through the intersystem collaboration object 40, instead of being conducted directly therebetween. Because of this, the collaboration between programs can be easily realized without awareness of the difference in interface between programs. [0127] In the above-mentioned description, the case has been described in which the programs in the identical subsystem collaborate with each other. However, it may also be possible that programs collaborate with each other between different subsystems or between different systems. Furthermore, FIG. 12 illustrates only the collaboration information between programs. However, this collaboration information may be stored in the collaboration information storage table 41, in parallel with the intersystem collaboration information shown in FIG. 3 and the collaboration information among subsystems shown in FIG. 7, or may be stored in a separate table. [0128] Furthermore, in the above-mentioned description, the case has been described in which, when each program requires collaboration with another program, each program autonomously requests the intersystem collaboration object 40 to generate a role object. However, the present invention is not limited thereto. It may also be possible that collaboration information between programs is previously registered in the collaboration information storage table 41 in the order of transmission of transactions, and the intersystem collaboration object 40 refers to the collaboration information to successively transmit transactions. Embodiment 4 [0129] Hereinafter, the present invention will be described by way of still another embodiment with reference to the drawings. [0130] As shown in FIG. 15, an integrated information processing system of the present embodiment has a configuration in which the ERP system 10, the SCM system 20, and the SFA system 30 are combined through a data perpetuation object 70. The ERP system 10 includes an ODB (object database) 11 as a storage apparatus. The SCM system 20 includes an RDB (relational database) 21. The SFA system 30 includes an SAM (sequential access method file) 31. The storage apparatus of each system is not limited to the above. [0131] The ODB 11, the RDB 21, and the SAM 31 hold duplicate data. In the case where duplicate data is updated in either of the systems, in order to maintain the consistency of the data, it is required to update the data in another system. [0132] In the integrated information processing system of the present embodiment, the data perpetuation object 70 conducts unified management of data that is managed by each system in duplicate. Hereinafter, the procedure thereof will be described. [0133] As shown in FIG. 15, in the integrated information processing system, the data perpetuation object 70 has a master maintenance table 71 (collaboration information storage means) for reference during unified management of data. [0134] As shown in FIG. 16, the master maintenance table 71 stores data defining a path for transmitting data to be updated from a system to another system and a communication method of the data transmission. In the example shown in FIG. 16, it is defined that updated data is transmitted from the ERP system 10 to the SCM system 20 by a real method, and updated data is transmitted from the SCM system 20 to the SFA system 30 by a delayed batch method. The path and the communication method shown herein are examples. Any communication method may be defined for a path between any systems, depending upon the relationship between the systems. [0135] Referring to FIG. 17, the data perpetuation object 70 includes a table access part 70 a for accessing the master maintenance table 71 to obtain collaboration information therefrom, a role object generating part 70 b (role object generating means) for generating a role object, a relating object generating part 70 c (relating object generating means) for generating a relating object for collaboration between role objects, and a permanent data identification object generating part 70 d (information identification object generating means) for generating a permanent data identification object (information identification object) described later. [0136] Herein, a procedure of unified management of data perpetuation in the integrated information processing system will be described with reference to FIGS. 18 and 19. Herein, the data perpetuation refers to processing of storing data in a non-volatile magnetic disk apparatus or the like. [0137] First, in the case where it is required to update data in the ODB 11 in the middle of or at the end of processing, the ERP system 10 requests the data perpetuation object 70 to generate a permanent data identification object, using information on a data storage target as arguments (Step S51). In this case, as the information on a data storage target, the information that a storage target is the ODB 11, the attribute of the ODB 11, and the like are given as arguments. [0138] In the data perpetuation object 70 receiving the above-mentioned request, the permanent data identification object generating part 70 d generates a permanent data identification object 81, using the information on a data storage target given as arguments (Step S52). [0139] The data perpetuation object 70 sets data to be updated with respect to the generated permanent data identification object 81, in accordance with the information on a data storage target (Step S53). Herein, it can be determined whether or not data is required to be updated, based on an update flag Fn contained in the data, for example, as described in Embodiment 1 with reference to FIG. 6. [0140] Next, the data perpetuation object 70 updates the ODB 11 in accordance with the contents set in the permanent data identification object 81 (Step S54). [0141] Then, the table access part 70 a of the data perpetuation object 70 refers to the master maintenance table 71, and obtains the name of a system that needs to collaborate, i.e., the name of a system to which the updated data should be transmitted (Step S55). [0142] Next, the role object generating part 70 b of the data perpetuation object 70 generates an active role 82 as an object corresponding to the ERP system 10, and generates a passive role 83 as an object corresponding to the SCM system 20 that is a collaboration target (Step S56). [0143] Furthermore, the relating object generating part 70 c of the data perpetuation object 70 generates a relating object 84 between the active role 82 and the passive role 83 generated at Step S56 (Step S57). The relating object 84 thus generated conducts collaboration of �transmitting updated data from the active role 82 to the passive role 83� between the active role 82 and the passive role 83. [0144] Furthermore, the relating object 84 thus generated has a communication method of updated data as an attribute. For example, in the case of the above-mentioned active role 82 and passive role 83, the active role 82 corresponds to the ERP system 10, and the passive role 83 corresponds to the SCM system 20. Therefore, the relating object generating part 70 c allows the table access part 70 a to refer to the master maintenance table 71, thereby obtaining a �real method� as an attribute of the relating object 84 (Step S57). [0145] The data perpetuation object 70 allows updated data to be communicated between the active role 82 and the passive role 83 in accordance with the attribute of the relating object 84 (Step S59). In this case, the attribute of the relating object 84 is a �real method� as described above, so that the updated data is immediately transmitted from the active role 82 (ERP system 10) to the passive role 83 (SCM system 20). [0146] When the updated data is transmitted from the ERP system 10, the SCM system 20 requests the data perpetuation object 70 to generate a permanent data identification object as arguments of information on a data storage target (Step S60). In this case, as the information on a data storage target, the information that a storage target is the RDB 21, the attribute of the RDB 21, and the like are given. [0147] Subsequently, although not shown in FIGS. 18 or 19, the processings similar to those at Steps S52 to S58 are conducted, whereby data is updated in the RDB 21 of the SCM system 20, the updated data is further transmitted from the SCM system 20 to the SFA system 30, and data is similarly updated in the SFA system 30. [0148] As described above, in the present embodiment, in the case where a plurality of systems hold the identical data in each storage apparatus in duplicate, data to be updated in each storage apparatus is determined by the permanent data identification object, and the updated data is transmitted between the role objects generated based on the collaboration information of the master maintenance table 71, in accordance with the relating object also generated based on the collaboration information of the master maintenance table 71. [0149] More specifically, in the above-mentioned configuration, unlike the prior art, the consistency of information among a plurality of systems is not maintained by directly transmitting information required to be updated to another system through file transfer or the like, but information held in a plurality of systems in duplicate can be managed in a unified manner by defining the collaboration between systems in the master maintenance table 71. [0150] Because of this, each system can maintain the consistency of information among a plurality of systems without awareness of the difference in architecture between systems holding the identical information. Furthermore, the processing of generating an object for conducting collaboration between systems is centralized at the data perpetuation object 70. Therefore, in the case where the collaboration between systems is changed, or a new system is added, the master maintenance table 71 may merely be corrected. As a result, a plurality of systems can be combined without awareness of the difference in architecture among them, and an integrated information processing system that is easily configured can be provided. [0151] Each processing at Steps S55 to S58 in the data perpetuation object can also be conducted similarly by requesting the intersystem collaboration object 40 to do it. [0152] The intersystem collaboration object 40 described in Embodiments 1 to 3 and the data perpetuation object 70 described in Embodiment 4 can be realized respectively as programs, and distributed to the market by being stored in a computer-readable recording medium such as a floppy disk and a CD-ROM. INDUSTRIAL APPLICABILITY [0153] As described above, in a collaboration apparatus between information processing systems, a plurality of information processing means can be combined without awareness of the difference in architecture among them, and a burden for integrating systems and configuring an intercompany collaboration system can be reduced. Furthermore, an integrated information processing system that is easily configured can be provided by using the collaboration apparatus between information processing systems. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7107186Oct 31, 2003Sep 12, 2006Abb Research Ltd.Transformer testingUS7376664Oct 31, 2003May 20, 2008Abb Research Ltd.Method for evaluating a transformer designUS7908611Mar 17, 2006Mar 15, 2011Microsoft CorporationUnmanaged programming language interoperability with managed internet protocol contextUS7921432Mar 17, 2006Apr 5, 2011Microsoft CorporationManaged application execution application programming interface and schemaWO2003010700A2 *Jul 19, 2002Feb 6, 2003Electronic Data Syst CorpMethod and tool for achieving data consistency in an enterprise resource planning system* Cited by examinerClassifications U.S. Classification709/200International ClassificationG06F15/177, G06F12/00, G06F17/30, G06F9/46, B65G61/00Cooperative ClassificationG06F9/54European ClassificationG06F9/54Legal EventsDateCodeEventDescriptionJan 9, 2013FPAYFee paymentYear of fee payment: 4Sep 5, 2001ASAssignmentOwner name: FUJITSU LIMITED, JAPANFree format text: CORRECTIVE ASSIGNMENT TO CORRECT REEL/FRAME 0118;ASSIGNORS:KUDO, AKIRA;SOTA, HARUKO;REEL/FRAME:012135/0625Effective date: 20010531Jun 6, 2001ASAssignmentOwner name: FUJITSU LIMITED, STATELESSFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KUDO, AKIRA;SOTA, HARUKO;REEL/FRAME:011889/0362Effective date: 20010531RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google