Commercial transaction business system, commercial transaction business method, and commercial transaction business program

Abstract

To synchronize data mutually between a front-side database and a backyard-side database, thereby regulating the data to be referred by the front side.SOLUTION: In a commercial transaction business system, a front-side system includes: a front database for storing first transaction data; and first processing means which inputs the first transaction data to be stored in the front database or outputs the first transaction data stored in the front database, in accordance with a request from a client via a web site, and a backyard-side system includes: a backyard database for storing second transaction data; second processing means which inputs the second transaction data to be stored in the backyard database; and integration processing means which synchronizes data mutually between the front database and the backyard database for integration.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present invention relates to a commercial transaction system, a commercial transaction method, and a commercial transaction program. [Background technology]

[0002] Recently, systems that use WebEDI (Electronic Data Interchange) systems to exchange electronic data with business partners have become popular. Due to the characteristics of WebEDI, business partners can register and access data in a database managed by the company, which carries the risk of accessing data that should not be made public. For example, Patent Document 1 describes a system that uses a WebEDI system to conduct electronic commerce with business partners. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-234220 Summary of the Invention [Problem to be solved by the invention]

[0004] However, Patent Document 1 does not state anything about restricting the data that can be accessed on the front side by distinguishing between the database on the front side (also called the "front yard") and the database on the back side in a WebEDI (Electronic Data Interchange) system and synchronizing the data with each other.

[0005] The present invention has been made in consideration of the above, and aims to provide a business transaction system, a business transaction method, and a business transaction program that can limit the data that can be accessed on the front side by distinguishing between a front-end database and a back-end database and synchronizing the data with each other. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a commerce business system for conducting electronic commerce with a trading partner for a predetermined transaction, comprising a front-side system and a back-end system, wherein the front-side system includes a front database for storing first transaction data, and a first processing means for inputting the first transaction data and storing it in the front database or outputting the first transaction data stored in the front database in response to a request from the trading partner via a website, and the back-end system includes a back-end database for storing second transaction data, a second processing means for inputting the second transaction data and storing it in the back-end database, and a linking processing means for bidirectionally synchronizing and linking the data in the front database and the back-end database.

[0007] According to another aspect of the present invention, the predetermined transaction is a transaction related to an order or receipt, In the front-side system, the front database includes a front data table for storing order data including an order number, a customer, a product, an update time, a linked flag specifying whether or not linked with order data, the linking time, and the order number, and a front history table for storing order history data including an order number, a history category specifying new, updated, or deleted, a customer, a product, an update time, a linked flag specifying whether or not linked with order history data, the linking time, and the order number, and the first processing means inputs new order data in accordance with an input operation by a business partner on an order input screen of a website provided, registers the new order data in the front data table, and registers order history data corresponding to the new order data in the front history table, and in the back-yard side system, the back-yard database includes: The system may include a backyard data table for storing order data including the order number, customer, product, a linkage number which is the order number of the linked order data, and an update time, and a backyard history table for storing order history data including the order number, a history category specifying new, updated, or deleted, the customer, product, a linkage number which is the order number of the linked order data, and an update time, wherein the second processing means inputs order data and registers it in the backyard data table, and registers order history data corresponding to the order data in the backyard history table, and the linkage processing means bidirectionally synchronizes and links the order data in the front data table / order history data in the front history table with the order data in the backyard data table / order history data in the backyard history table.

[0008] According to another aspect of the present invention, the second processing means may modify the received order data and the order history data when there is a modification to the order data.

[0009] Furthermore, according to one aspect of the present invention, the linking processing means may acquire order data with a linked flag = unlinked from the front data table as the link target, and add the acquired order data to the order data in the backyard data table / order history data in the backyard history table, at which time a new order number may be assigned, the linking number may be set to the "order number," and the update time may be set to the "time the linking process was executed," and after the linking, the linked flag for the order data to be linked in the front data table may be updated to "linked," and the linking time may be updated to the "time the linking process was executed."

[0010] According to one aspect of the present invention, the back-end system may further include a linked customer management master that registers customers who are permitted to enter orders, and a linked execution data table for storing linked execution data including the execution time of the linked processing.

[0011] According to another aspect of the present invention, the collaboration processing means acquires the update time of the collaboration execution data in the collaboration execution data table, acquires from the backyard history table, as the collaboration target, order history data that matches the customer registered in the collaboration business partner management master and has an update time after the acquired update time, updates the order data in the front data table / the order history data in the front history table with the acquired order history data, and if the collaboration number in the acquired order history data matches the order number in the order data or the order number matches the order number in the order data, updates the order number in the order data to the order number of the matching order data, and updates any corrections to the order history data, Order history data corresponding to the update of the order data is added to the front history table with a history category of "update", and if the linkage number of the acquired order history data does not match the order number of the order data and the order number does not match the order number of the order data, new order data is created and order history data corresponding to the newly created order data is added to the front history table with a history category of "new", and in the order history data, data with a history category of "delete" is deleted from the order history data with the matching order number, and order history data corresponding to the deleted order data is added to the front history table with a history category of "delete", and after linkage, the update time of the linkage execution data is updated to the execution time of the linkage process.

[0012] Furthermore, according to one aspect of the present invention, the first transaction means may be configured to output the order results and / or history by referring to the order data in the front data table and / or the order history data in the front history table in response to the customer's operation on the order history inquiry screen of the website provided.

[0013] According to another aspect of the present invention, the predetermined transaction may include a transaction for providing goods or services or a transaction for procuring goods or services.

[0014] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a commercial transaction method executed by a commercial transaction system having a front-side system and a back-end system for conducting electronic commercial transactions with trading partners regarding specified transactions, characterized in that the method includes a first processing step in which the front-end system inputs first transaction data and stores it in a front database or outputs the first transaction data stored in the front database in response to a request from the trading partner via a website, a second processing step in which the back-end system inputs second transaction data and stores it in the back-end database, and an integration processing step in which the back-end system bidirectionally synchronizes and integrates the data in the front database and the back-end database.

[0015] In addition, in order to solve the above-mentioned problems and achieve the object, the present invention provides a commercial transaction business program to be executed by a commercial transaction business system having a front-side system and a back-end system for conducting electronic commercial transactions with trading partners regarding specified transactions, the commercial transaction business program causing a computer to execute the following steps: a first processing step in which the front-end system inputs first transaction data and stores it in a front database or outputs the first transaction data stored in the front database in response to a request from the trading partner via a website; a second processing step in which the back-end system inputs second transaction data and stores it in a back-end database; and an integration processing step in which the back-end system bidirectionally synchronizes and integrates the data in the front database and the back-end database. [Effects of the Invention]

[0016] According to the present invention, by distinguishing between the front-end database and the back-end database and synchronizing the data with each other, it is possible to restrict the data that can be referenced on the front-end. [Brief explanation of the drawings]

[0017] [Figure 1] FIG. 1 is a diagram illustrating an example of a sales business system. [Figure 2] FIG. 2 is a diagram showing an image of a commercial transaction system according to the present invention in which the front environment and the backyard environment are separated. [Figure 3] FIG. 3 is a diagram showing an example of a business flow according to the present invention. [Figure 4] FIG. 4 is a block diagram showing an example of the configuration of a commercial transaction system according to this embodiment. [Figure 5] FIG. 5 is a diagram showing an example of a flow for explaining an outline of the overall processing of the commercial transaction system according to this embodiment. [Figure 6] FIG. 6 is a diagram showing sample data for explaining a specific example of processing in the commercial transaction system according to this embodiment. [Figure 7] FIG. 7 is a diagram showing sample data for explaining a specific example of processing in the commercial transaction system according to this embodiment. [Figure 8] FIG. 8 is a diagram showing sample data for explaining a specific example of processing in the commercial transaction system according to this embodiment. [Figure 9] FIG. 9 is a diagram showing sample data for explaining a specific example of processing in the commercial transaction system according to this embodiment. [Figure 10] FIG. 10 is a diagram showing sample data for explaining a specific example of processing in the commercial transaction system according to this embodiment. [Figure 11] FIG. 11 is a diagram showing sample data for explaining a specific example of processing in the commercial transaction system according to this embodiment. [Figure 12] FIG. 12 is a diagram for explaining an application example of the commercial transaction system of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0018] Hereinafter, embodiments of a commercial transaction system, a commercial transaction method, and a commercial transaction program according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to these embodiments.

[0019] [1. Overview] In this invention, in an electronic commerce system, a mechanism is constructed to distinguish between a front-end database and a back-end database, synchronize the data with each other, and data update information is properly managed, thereby minimizing the data that can be referenced on the front-end.

[0020] (1. WebEDI) There is a growing need to computerize business-to-business transactions, and the need for WebEDI is increasing. WebEDI is a method for realizing electronic commerce between businesses, and is a mechanism for conducting business transactions over the Internet by introducing a web system.

[0021] 1 is a diagram showing an example of a sales business system. The operating company is a company that operates the WebEDI system, introduces the commercial transaction business system, and is the company that is responsible for managing the commercial transaction business data.

[0022] A business partner (e.g., a customer or supplier) is a company that is a "recipient of goods and services" or a "source of goods and services" from the perspective of the operating company, and is not a company that introduces a business transaction system. A business partner enters into a contract with the operating company to transact using WebEDI, and logs into the system using a user account issued by the operating company.

[0023] (2. Overview of the Commercial Transaction System of the Present Invention) In this invention, the commercial transaction business system that operates the WebEDI system is composed of a front environment and a back-end environment. The front environment is an environment used by trading partner users and operating company users who log in, and is assumed to be open to the Internet and accessible to a large number of users who have trading relationships with the operating company. It is possible to access the primary storage database for transactions that occur between the operating company and "recipients of goods, services, etc." and "suppliers of goods, services, etc." If the number of trading partners is small, it can be made public with higher security by restricting the sources of connection.

[0024] The backyard environment is an environment that only users of the operating company can log in to and use. It is assumed that connections from external companies such as business partners are not permitted and that only the operating company can connect. It is possible to access the commercial transaction data management database, which is the core system of the operating company.

[0025] The reason for separating the front environment and the backyard environment in this invention is that the advantages gained from separating the environments outweigh the disadvantages that arise, so in principle the environments are separated in WebEDI.

[0026] The disadvantage is that the databases storing the transaction data of the two environments are separated, so data cannot be synchronized in real time. Therefore, it is necessary to implement data synchronization processing.

[0027] The advantage is that even if one environment goes down, business can continue by keeping the other environment running. Environments with specifications that match the expected number of users of each environment can be built, and resources can be optimized. For example, the front environment, which has a large number of users, can be built on high-spec machines, while the back-end environment can be built on low-spec machines.

[0028] In addition, operations can be tailored to the nature of the data stored in each database. For example, the front-end database may contain personal information of business partners, so it is encrypted using a special method.

[0029] In addition, security can be strengthened by setting up infrastructure boundaries on servers / networks to separate them and allowing only specific communications.

[0030] Figure 2 is a diagram showing an image of the commercial transaction business system of the present invention, which separates the front environment and the backyard environment. The front environment provides a website that can be accessed by business partner users (users of Company A, Company B, and Company C) and operating company users, and stores user data and business data (for primary storage). The user data may include personal information of business partner users (names, email addresses, etc.). It is not linked to the backyard environment.

[0031] Business data (primary storage data) is transaction data that occurs between the operating company and "recipients of goods and services, etc." and "sources of goods and services, etc."

[0032] The backyard environment provides an environment that can only be accessed by the operating company's users (for example, an environment accessible via a website, local program, remote connection, etc.), is equipped with collaboration tools, and stores business data (for data management). The collaboration tools periodically synchronize business data between the front and backyard environments. Communication between environments other than that of the collaboration tools is restricted.

[0033] Due to the characteristics of WebEDI, business partners can register and access data in a company's managed database, which poses the risk of accessing data that should not be made public. Therefore, the commercial transaction business system of this invention takes security measures by separating the front-end database from the back-end database and minimizing the data that can be accessed on the front-end.

[0034] In addition, the front-end only allows registration, and information on modified data must be updated on the back-end. Therefore, it is essential to synchronize the data in the front-end database with the data in the back-end database.

[0035] In addition, since linking all data takes time, by storing the time of linking in a separate table, it is possible to link only the data that has been updated since the last link the next time. Here, we will explain an example of an order on the front side (an order received on the back side).

[0036] Order data registered by business partners is treated as the company's order data and updated across databases. In addition, order data registered by the company is treated as the business partner's order data and updated across databases, allowing the business partner to check the data online.

[0037] (3. Main components of the commercial transaction system of the present invention) The commercial transaction system of the present invention comprises a front-side system and a back-end system, and conducts electronic commercial transactions with trading partners for predetermined transactions. The front-side system comprises a front database for storing first transaction data, and a first processing means for inputting the first transaction data and storing it in the front database or outputting the first transaction data stored in the front database in response to a request from the trading partner via a website. The back-end system comprises a back-end database for storing second transaction data, a second processing means for inputting the second transaction data and storing it in the back-end database, and a linking processing means for bidirectionally synchronizing and linking the data in the front database and the back-end database.

[0038] The specified transactions include transactions for the provision of various goods and services or transactions for the procurement of goods and services. In the following explanation, an example of an order / receive transaction will be described as an example, but the present invention is not limited to this and can also be applied to transactions for the provision of other goods and services or transactions for the procurement of goods and services. For example, the present invention can be applied to the entire retail industry, such as steel, manufacturing, food, and distribution retail, and can also be applied to the service industry in general by including transactions such as work requests to outsourced parties.

[0039] (4. An example of the business flow of the present invention) 3 is a diagram showing an example of a business flow of the present invention. In the following embodiment, an example of ordering in a front environment / receiving an order in a backyard environment will be described.

[0040] In Figure 3, the front environment (1) accepts orders from business partners via a website and stores the order data in a front database. The order data in the front database is linked to the order data in the back-end database, and (2) the front database is linked to the back-end database, and (3) the back-end database is linked to the front database.

[0041] On the other hand, in the back-end environment, (4) orders from business partners are received and the order data is stored in the back-end database. The order data in the back-end database is linked to the order data in the front-end database, and (5) the back-end database is linked to the front-end database.

[0042] In the front environment, (6) customers can inquire about order data in the front database (for example, inquire about the list of order history) via the website.

[0043] (5. Functional Overview of the Commercial Transaction System of the Present Invention) Next, a functional overview of the commercial transaction system of the present invention will be described.

[0044] 1. Prepare a linked flag to link the order data on the front end. Specifically, it is as follows: (1) The linking process (front side → backyard side) only allows new input on the front side, and it is assumed that linking is always required. (2) When the order data is registered, the linked flag is registered as unlinked. (3) When acquiring data to be linked, only data with a linked flag set to "unlinked" will be linked. (4) When the linking process (front side → backyard side) is performed, the linking completion flag is updated to linking completion. (5) Data linked from the back-end side is updated as linked (so that it will not be included in the next link).

[0045] 2. Prepare the linkage execution data to link the order data on the back-end side. Specifically, it is as follows. (1) Because input and history data management that does not use the linkage process (backyard side → front side) is also performed in the backyard, linkage execution data is prepared separately and the tables to be linked are identified by data classification. By implementing such a mechanism, it becomes possible to flexibly respond to an expansion of the business scope on the front side without changing the structure of the backyard system. (2) Collaboration is performed on data that has been updated since the update time stored in the collaboration execution data. (3) Updated data is obtained from historical data.

[0046] [2. Configuration] The configuration of the commercial transaction system 1 according to this embodiment will be described with reference to Fig. 4. Fig. 4 is a block diagram showing an example of the configuration of the commercial transaction system 1 according to this embodiment.

[0047] The commercial transaction system 1 is a system that uses, for example, WebEDI to conduct predetermined commercial transactions with business partners, and is composed of a front-side system 100 and a back-of-house system 200 that are configured to be able to communicate data with each other. The "front-side system 100" is a system that applies the WebEDI system, and may be simply referred to as the "front side." The "back-of-house system 200" is a business system that employees use to conduct their work, and may be simply referred to as the "back-of-house."

[0048] The front-side system 100 and the back-yard-side system 200 are commercially available desktop personal computers, workstations, or the like.

[0049] 4, the front-side system 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the front-side system 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0050] The communication interface unit 104 has a function (network interface function) of communicatively connecting the front-side system 100 to a network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. Here, the network 300 has a function of communicatively connecting the front-side system 100 to other devices such as customer terminals 310, etc., and is, for example, the Internet. The customer terminal 310 is, for example, a customer's terminal. The front-side system 100 and the customer terminal 310 are communicatively connected via the network (Internet) 300.

[0051] The communication interface unit 104 also has a function (communication interface function) for directly communicating data with other devices, and is connected to the backyard-side system 200 so as to be able to communicate with it.

[0052] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. Note that, hereinafter, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112. Furthermore, an operation performed by a user on the screen (GUI, etc.) of the output device (monitor) 114 using the input device 112 may be simply referred to as a "user operation."

[0053] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0054] The storage unit 106 includes a front data table 106a, a front history table 106b, and the like.

[0055] The front data table 106a is a table for storing order data. The order data may include an order number, a customer, a product, an update time, a linked flag indicating whether or not the order data is linked, the linked time, and an order number.

[0056] The front desk history table 106b is a table for storing order history data. The order history data may include an order number, a history category (new, updated, deleted), a customer, a product, an update time, a linked flag indicating whether or not linked with the order history data, a linked time, and an order number.

[0057] The control unit 102 is a CPU or the like that performs overall control of the front-end system 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing operations based on these stored programs.

[0058] The control unit 102 conceptually includes a first processing unit 102a.

[0059] The first processing unit 102a functions as a WebEDI provider, and for example, inputs new order data in response to input operations on the order input screen of the provided website from the trading partner terminal 310, and registers the data in the front data table 106a. The first processing unit 102a also registers order history data corresponding to the order data in the front history table 106b. Passwords that allow access to the provided website are issued to customers (trading partners) registered in the linked trading partner management master 206c, and trading partner terminals 310 enter the password when accessing the website.

[0060] In addition, the first processing unit 102a displays and outputs the order results or history by referring to the order data in the front data table 106a or the front history table 106b in response to operations on the customer terminal 310 on the order history inquiry screen of the provided website.

[0061] 4, the backyard-side system 200 includes a control unit 202, a communication interface unit 204, a storage unit 206, and an input / output interface unit 208. The units included in the backyard-side system 200 are connected to each other so as to be able to communicate with each other via any communication path.

[0062] The communication interface unit 204 has a function (network interface function) of communicatively connecting the backyard-side system 200 to the network 400 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. Here, the network 400 has a function of communicatively connecting the backyard-side system 200 to other devices such as employee terminals 410, etc., for example, an in-house LAN. The employee terminals 410, etc. are, for example, employee terminals. The backyard-side system 200 and the employee terminals 410 are communicatively connected via the network (in-house LAN (Local Area Network)) 400. In this way, the devices that can be connected to the backyard-side system 200 are limited.

[0063] The communication interface unit 204 has a function of directly communicating data with other devices (communication interface function), and is connected to the front-end system 100 so as to be able to communicate with it.

[0064] An input device 212 and an output device 214 are connected to the input / output interface unit 208. The output device 214 may be a monitor (including a home television), a speaker, or a printer. The input device 212 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. Note that, hereinafter, the output device 214 may be referred to as the monitor 214, and the input device 212 may be referred to as the keyboard 212 or the mouse 212. Furthermore, an operation performed by a user on the screen (GUI, etc.) of the output device (monitor) 214 using the input device 212 may be simply referred to as a "user operation."

[0065] The storage unit 206 stores various databases, tables, files, etc. The storage unit 206 stores computer programs that work in conjunction with an operating system (OS) to issue commands to a central processing unit (CPU) to perform various processes. The storage unit 106 can be, for example, a memory device such as a random access memory (RAM) or a read-only memory (ROM), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0066] The storage unit 206 includes a backyard data table 206a, a backyard history table 206b, a partner management master table 206c, and a partner execution data table 206d.

[0067] The backyard data table 206a is a table for storing order data. The order data may include an order number, a customer, a product, a link number which is the order number of linked order data, and an update time.

[0068] The backyard history table 206b is a table for storing order history data. The order history data may include the order number, history category (new, updated, deleted), customer, product, link number which is the order number of linked order data, and update time.

[0069] The linked business partner management master 206c registers the customers who are permitted to use WebEDI. A password for using WebEDI is issued to these customers, and the customers enter the password when accessing the front side (WebEDI).

[0070] The collaboration execution data table 206d is a table for storing collaboration execution data, which may include data classification and update time.

[0071] The control unit 202 is a CPU or the like that performs overall control of the backyard system 200. The control unit 202 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processes based on these stored programs.

[0072] The control unit 202 conceptually includes a second processing unit 202a and a cooperative processing unit 202b.

[0073] The second processing unit 202a inputs order data and registers it in the backyard data table 206a in response to, for example, an operation on the employee terminal 410. The second processing unit 202a also registers order history data corresponding to the order data in the backyard history table 206b.

[0074] For example, if there is a need to correct the order data, the second processing unit 202a corrects the order data and the order history data in response to an operation on the employee terminal 410, for example.

[0075] The linking processor 202b bidirectionally synchronizes and links the order data in the front data table 106a / order history data in the front history table 106b with the order data in the backyard data table 206a / order history data in the backyard history table 206b.

[0076] The linking processing unit 202b executes linking processing from the front side to the backyard side, and first obtains order data with a linked flag = unlinked from the front data table 106a as the link target, and adds the obtained order data to the order data in the backyard data table 206a / order history data in the backyard history table 206b, at which time a new order number is assigned, the link number is set to the "order number", and the update time is set to the "time the linking processing was executed", and after the linking, the linking flag for the order data to be linked in the front data table 106a may be updated to "linked" and the linking time to the "time the linking processing was executed".

[0077] The collaboration processing unit 202b executes collaboration processing from the backyard side to the front side, first acquiring the update time of the collaboration execution data in the collaboration execution data table 206d, acquiring from the backyard history table 206b the order history data that matches the customer registered in the collaboration business partner management master 206c and has an update time after the acquired update time as the collaboration target, and updating the order data in the front data table 106a / the order history data in the front history table 106b with the acquired order history data, and at that time, if the collaboration number of the acquired order history data matches the order number of the order data or the order number matches the order number of the order data, updating the order number of the order data to the order number of the matching order data, and If there is, it is updated, and the order history data corresponding to the update of the order data is added to the front history table 106b with a history category of "update." If the linkage number of the acquired order history data does not match the order number of the order data and the order number does not match the order number of the order data, new order data is created, and the order history data corresponding to the newly created order data is added to the front history table 106b with a history category of "new." In the order history data, data with a history category of "delete" is deleted from the order data with the matching order number, and the order history data corresponding to the deleted order data is added to the front history table 106b with a history category of "delete." After linkage, the update time of the linkage execution data is updated to the execution time of the linkage process.

[0078] [3. Specific examples of processing] A specific example of the processing of the commercial transaction system 1 in this embodiment will be described with reference to Figures 4 to 11. Figures 5 to 11 are diagrams for explaining a specific example of the processing of the commercial transaction system 1 in this embodiment.

[0079] (Overall processing) 5 is a diagram showing an example of a flow for explaining an outline of the overall processing of the commercial transaction system 1 in this embodiment. In the diagram, the timing of order registration on the front side and order reception registration on the back side is one example, and the timing is not limited to this flow timing, and may be performed at other times.

[0080] In Figure 5, an order is registered on the front side, and an order is registered on the back side (step S1). Specifically, on the front side, the first processing unit 102a inputs new order data in response to input operations on the customer terminal 310 on the order input screen of the provided website, and registers the data in the front data table 106a. The first processing unit 102a also registers order history data corresponding to the order data in the front history table 106b. At this stage, no linking process has been performed, so the linking flags for the order data and order history data are set to "unlinked", the linking time is "-", and the order number is "-".

[0081] On the backyard side, the second processing unit 202a inputs order data in response to, for example, the operation of the employee terminal 410, and registers the data in the backyard data table 206a. The second processing unit 202a also registers order history data corresponding to the order data in the backyard history table 206b. At this stage, no linking process has been performed, so the linking number for the order data and order history data is set to "-".

[0082] Order registration is possible only for customers registered in the linked business partner management master 206c. Order registration is possible not only for customers registered in the linked business partner management master 206c, but also for customers who are not registered.

[0083] Hereinafter, the process of linking the order data in the front data table 106a / the order history data in the front history table 106b with the order data in the backyard data table 206a / the order history data in the backyard history table 206b will be referred to as the "linking process (front side → backyard side)". Also, the process of linking the order data in the backyard data table 206a / the order history data in the backyard history table 206b with the order data in the front data table 106a / the order history data in the front history table 106b will be referred to as the "linking process (backyard side → front side)".

[0084] On the backyard side, a linking process (front side → backyard side) is carried out (step S2).

[0085] The collaboration processing unit 202b first acquires the execution time of the collaboration process. The collaboration processing unit 202b acquires order data with a collaboration completion flag = unlinked from the front data table 106a as the collaboration target, and adds the acquired order data to the order data in the backyard data table 206a / order history data in the backyard history table 206b, assigning a new order number, setting the collaboration number to "order number," and setting the update time to "execution time of the acquired collaboration process." After the collaboration, the collaboration completion flag for the order data to be linked in the front data table 106a is updated to "linked," and the collaboration time to "execution time of the acquired collaboration process."

[0086] On the backyard side, a linking process (backyard side → front side) is carried out (step S3).

[0087] The collaboration processor 202b acquires the update time of the collaboration execution data in the collaboration execution data table 206d, where the data category is "order received." The collaboration processor 202b acquires, as the collaboration target, order history data from the backyard history table 206b that matches the customer registered in the collaborative business partner management master 206c and that has an update time after the acquired update time.

[0088] The order data in the front data table 106a / order history data in the front history table 106b are updated with the acquired order history data. In this case, if the link number in the acquired order history data matches the order number in the order data, or if the order number matches the order number in the order data, the order number is updated to the matched order data, and the history category of the order history data is updated to "updated."

[0089] On the other hand, if the link number of the acquired order history data does not match the order number in the order data and the order number does not match the order number in the order data, new order data is created and the history category of the order history data is set to "New." In the order history data, data with a history category of "Delete" that matches the order number is deleted, and the history category of the order history data is set to "Delete."

[0090] The integration time of the data that was added or updated in the order data / order history data is updated as the "integration process execution time." After integration, the update time of the integration execution data is updated as the "integration process execution time."

[0091] The order registration (modification, etc.) is performed on the backyard side (step S4). Since only new registrations are allowed on the front side (WebEDI), modifications such as additions, changes, and deletions are performed on the backyard side. The second processing unit 202a modifies the order data in the backyard data table 206a. The second processing unit 202a also updates the order history data in response to the modification of the order data.

[0092] The backyard side performs a linking process (backyard side → front side) (step S5). The data updated after the update time of the collaboration execution data is the target of collaboration, and collaboration processing (backyard side → front side) is performed on the backyard side. The collaboration processing (backyard side → front side) is performed in the same way as in step S3.

[0093] The front-end checks the order data (step S6). It is possible to check both the order data performance and history. For example, the first processing unit 102a outputs the order performance or history by referring to the order data in the front-end data table 106a or the front-end history table 106b in response to an operation of the customer terminal 310 on the order history list screen of the provided website.

[0094] (3-2. Sample data) 6 to 11 are diagrams showing sample data for explaining a specific example of the processing of the commercial transaction system 1 according to this embodiment. A specific example of the processing of FIG. 5 will be explained with reference to FIGS. 6 to 11.

[0095] (S1. Order data is registered at the front desk, and order data is registered at the back desk) A specific example of the processing in step S1 will be described with reference to Figure 6. On the front side, for example, in response to an input operation on the order input screen of the trading partner terminal 310, order data of order numbers (D001, D002, D003) is registered in the front data table 106a. The linkage flag for the order data is set to "unlinked." In addition, order history data for the order data is registered in the front history table 106b.

[0096] 6(A) is a diagram showing an example of an order entry screen. The order entry screen has fields for entering the order date and product.

[0097] FIG. 6(B) shows an example of order data. The order data may include an order number, customer, product, update time, linked flag, linked time, and order number. In the example shown in the figure, the first line registers the order number "D001," the customer "T001," the product "ShohinA," the update time "2022 / 3 / 2 10:00," and the linked flag "unlinked." The second line registers the order number "D002," the customer "T001," the product "ShohinB," the update time "2022 / 3 / 2 10:05," and the linked flag "unlinked." The third line registers the order number "D003," the customer "T002," the product "ShohinC," the update time "2022 / 3 / 2 10:10," and the linked flag "unlinked."

[0098] 6(C) shows an example of order history data. The order history data may include the order number, history category (new, updated, deleted), customer, product, update time, linked flag, linked time, and order number. In the example shown in the same figure, the first line registers the order number "D001", history category "New", customer "T001", product "ShouhinA", update time "2022 / 3 / 2 10:00", and linked flag "Not linked". The second line registers the order number "D002", history category "New", customer "T001", product "ShouhinB", update time "2022 / 3 / 2 10:05", and linked flag "Not linked". The third line registers the order number "D003", history category "New", customer "T002", product "ShouhinC", update time "2022 / 3 / 2 10:10", and linked flag "Not linked".

[0099] For example, the backyard side receives urgent orders from business partners "T001" and "T002" registered in the linked business partner management master 206c, and registers the order data for order numbers "J001" and "J002" in the backyard data table 206a by directly entering the order data on the backyard side, not via WebEDI. The backyard side also receives an order from customer "T003" who is not registered in the linked business partner management master 206c, and registers the order data for order number "J003" in the backyard data table 206a by entering the order data on the backyard side. The order history data for the order data is also registered in the backyard history table 206b.

[0100] Figure 6(E) shows an example of data in the linked business partner management master 206c. The linked business partner management master 206c stores the customers who use WebEDI. In the example shown in the figure, customers "T001" and "T002" are registered.

[0101] Figure 6(D) shows an example of collaboration execution data. Collaboration execution data may include a data category and an update time. In the example shown in the figure, the first line has the data category "Order" and the update time "2022 / 3 / 2 10:01", and the second line has the data category "Order" and the update time "2022 / 3 / 2 10:00".

[0102] FIG. 6(F) shows an example of order data. The order data may include the order number, customer, product, link number, and update time. In the example shown in the figure, the first line registers the order number "J001," the customer "T001," the product "ShohinA," and the update time "2022 / 3 / 2 10:00." The second line registers the order number "J002," the customer "T002," the product "ShohinA," and the update time "2022 / 3 / 2 10:05." The third line registers the order number "J003," the customer "T003," the product "ShohinA," and the update time "2022 / 3 / 2 10:10."

[0103] FIG. 6(G) shows an example of order history data. The order history data may include the order number, history category, customer, product, link number, and update time. In the example shown in the figure, the first line registers the order number "J001," history category "new," customer "T001," product "ShohinA," and update time "2022 / 3 / 2 10:00." The second line registers the order number "J002," history category "new," customer "T001," product "ShohinA," and update time "2022 / 3 / 2 10:05." The third line registers the order number "J003," history category "new," customer "T003," product "ShohinA," and update time "2022 / 3 / 2 10:10."

[0104] (S2: Linkage processing is performed on the backyard side (front side → backyard side)) A specific example of the processing in step S2 will be described with reference to Figure 7. The data D001, D002, and D003 of the order data registered in step S1, whose linked flag = unlinked, are the data to be linked. After linking, the linked flags that are "unlinked" are updated to "linked." A specific processing flow is described below.

[0105] (1) When executing the linking process (front side → backyard side), the execution time of the linking process is obtained. In this example, the execution time of the linking process is set to "2022 / 3 / 2 10:30."

[0106] (2) Obtain the data whose order data linkage flag = unlinked. In this case, the target data for linkage processing are order numbers "D001," "D002," and "D003."

[0107] (3) The target data obtained in (2) is added to the order data / order history data (rows marked with circles in Figures 7(E) and 7(F)). Here, the order data for order numbers "D001", "D002", and "D003" are added to rows 4 to 6, as shown in Figures 7(E) and 7(F), along with order numbers "J004", "J005", and "J006", history category "New", link numbers "D001", "D002", and "D003", and update time "2022 / 3 / 2 10:30".

[0108] (4) The linked flag of the target data of the order data acquired in (2) is updated to "Linked," and the linked time is updated to the execution time acquired in (1). In this case, as shown in Figure 7(A), the linked flag of the data of order numbers "D001," "D002," and "D003" is updated to "Linked," and the linked time is updated to "2022 / 3 / 2 10:30."

[0109] (S3: Linkage processing is performed on the backyard side (backyard side → front side)) A specific example of the processing in step S3 will be described with reference to FIG. 8. Here, the update is performed to update the order number stored in the back-office. Of the order history data, the data to be linked is customer data registered in the linked business partner management master 206c and data that has been updated after the update time of the linkage execution data. After the linkage processing is executed, the update time of the linkage execution data is updated to the time the linkage processing was executed. A specific processing flow is described below (the same procedure is also used in step S5).

[0110] (1) When executing the linkage process (backyard → front), the update time of the linkage execution data whose data category is "Order received" is obtained. In this case, the update time "2022 / 3 / 2 10:01" is obtained, as shown in Figure 8(C).

[0111] (2) From the order history data, obtain data that matches a customer existing in the linked business partner management master 206c and has an update time that is later than the update time obtained in (1). Here, in Figure 8(F), the order numbers corresponding to the update times "2022 / 3 / 2 10:05" and "10:30" of the order history data for customers "T001" and "T002" ≥ the update time "2022 / 3 / 2 10:01" in (1) are "J002," "J004," "J005," and "J006." Note that order number "J001" is not eligible for collaboration because it is before the update time of the collaboration execution data. Furthermore, order number "J003" is not eligible for collaboration because it is a customer that does not exist in the linked business partner management master 206c.

[0112] (3) When executing the linkage process (backyard side → front side), the execution time of the linkage process is obtained. In this example, the execution time is set to "2022 / 3 / 2 11:00."

[0113] (4) Update the order data / order history data on the front side (lines marked with circles in Figures 8(A) and 8(B)). At that time, if the link number of the data acquired in (2) matches the order number in the order data, or if the order number matches the order number in the order data, update it to the order number of the matching order data. Also, update the history category of the order history data to "updated."

[0114] If the linkage number of the data obtained in (2) does not match the order number in the order data and the order number does not match the order number in the order data, new order data will be created. The history category of the order history data will be set to "New". In the order history data, data with a history category of "Delete" will be deleted if the order number matches. The history category of the order history data will be set to "Delete".

[0115] As shown in Figure 8(C), the link time of the data for which the order data / order history data was added or updated is updated with the execution time obtained in (3) (link time: 2022 / 3 / 2 11:00).

[0116] For the order number "J002" and the link number "-", as shown in Figures 8(A) and (B), there is no data for the target order number and link number that matches the order number and order number in the order data, so new order data is created and the history category of the order history data is set to "New".

[0117] For order number "J004", linkage number "D001", order number "J005", linkage number "D002", order number "J006", and linkage number "D003", as shown in Figures 8(A) and (B), data exists where the target order number and linkage number match the order number and order number in the order data, so the order data is updated. Also, the history category of the order history data is set to "update".

[0118] (S4. Order registration (correction) in the backyard) A specific example of step S4 will be explained with reference to Figure 9. Only new registrations are accepted via WebEDI. Therefore, corrections are made on the back-office side. The back-office side is notified that an error occurred during registration on the front-office side, and the data is corrected on the back-office side.

[0119] For example, a new order for product "ShohinD" is received from customer "T001," so it is registered using back-office order entry. Also, product "ShohinA" for order number "D002" is changed to "ShohinE" using back-office order entry. Order number "D003" is deleted using back-office order entry because customer T002 has requested that the order be canceled. The specific processing flow is described below.

[0120] (1) New order data for order number "J007" is registered at "2022 / 3 / 2 11:05." Specifically, as shown in Figure 9 (E) and (F), a new order request for "ShouhinD" has been received from customer "T001," so this is registered using the order entry function in the back office.

[0121] (2) At 11:10 on March 2, 2022, the product with order number "J005" is corrected and updated. Specifically, as shown in Figure 9 (E) and (F), the product with link number "D002" is changed from "ShouhinA" to "ShouhinE" in the order entry on the back-end side.

[0122] (3) At 11:15 on March 2, 2022, the order number "J006" is deleted. Specifically, as shown in Figure 9 (E) and (F), the link number "D003" is deleted by the order entry on the back-end side because the customer "T002" requested to cancel the order.

[0123] (S5: Implementing linkage processing on the backyard side (backyard side → front side)) A specific example of the processing in step S5 will be described with reference to Fig. 10. Data updated after the update time of the collaboration execution data is set as the collaboration target. A specific processing flow is described below (the same processing as in S3 is performed).

[0124] (1) When executing the linkage process (back-office side → front-office side), the update time of the linkage execution data whose data category is "Order" is obtained. In this example, the update time "2022 / 3 / 2 11:00" is obtained.

[0125] (2) From the order history data, obtain data that matches the customers existing in the linked business partner management master 206c and has an update time after the update time obtained in (1). As shown in Figure 10(F), for the target customers "T001" and "T002", the order history data update times "2022 / 3 / 2 11:05", "11:10", and "11:15" are ≧ (1), and the data that corresponds to the update time "2022 / 3 / 2 11:00" are the order numbers "J007", "J005", and "J006".

[0126] (3) When executing the linking process (backyard side → front side), the execution time of the linking process is obtained. In this example, it is set to "2022 / 3 / 2 11:30."

[0127] (4) Update the order data / order history data on the front side (lines marked with circles in Figure 10(A) and (B)). At that time, if the link number of the order history data acquired in (2) matches the order number of the order data, or if the order number matches the order number of the order data, update the order number of the matching order data and set the history category of the order history data to "update."

[0128] If the link number of the order history data obtained in (2) does not match the order number of the order data and the order number does not match the order number of the order data, new order data is created and the history category of the order history data is set to "New."

[0129] In the order history data on the back-end side, if the history category is "delete," the order data with the matching order number is deleted, and the history category of the order history data is set to "delete."

[0130] The linkage time of the data for which order data / order history data was added or updated is updated with the execution time of the linkage process obtained in (3) (linkage time "2022 / 3 / 2 11:30").

[0131] For the order number "J007" and linkage number "-", there is no data for the target order number and linkage number that matches the order number and order number in the order data, so new order data is created as shown in the fifth line of Figure 10(A), and the history category of the order history data is set to "New" as shown in the eighth line of Figure 10(B).

[0132] For order number "J005" and linkage number "D002," data exists in which the target order number and linkage number match the order number and order number in the order data, so the order data is updated as shown in the second line of Figure 10(A), and the history category of the order history data is set to "updated" as shown in the ninth line of Figure 10(B).

[0133] For order number "J006" and history category "Delete", since the history category is "Delete", the order data whose target order number matches the order number in the order data is deleted as shown in the third line of Figure 10(A), and the history category of the order history data is set to "Delete" as shown in the tenth line of Figure 10(B).

[0134] (S6: Check order data at the front desk) A specific example of the processing in step S6 will be described with reference to Figure 11. It is possible to check both the actual results and history of order data. On the front side, in response to the operation of the trading partner terminal 310 on the order history list inquiry screen of the provided website, the order data in the front data table 106a or the front history table 106b is referenced and the actual results or history of the order is output.

[0135] FIG. 11(A) is a diagram showing an example of the display of an order history list inquiry screen (in the (actual) mode). FIG. 11(B) is a diagram showing an example of order data. FIG. 11(C) is a diagram showing an example of the display of an order history list inquiry screen (in the (history) mode). FIG. 11(D) is a diagram showing an example of order history data.

[0136] The order history list inquiry screen has a button for selecting a mode (actual or history), an extraction condition specification area for specifying extraction conditions (order number, product), and an extraction result display area for displaying extracted order data or order history data. When the "actual" mode is selected, order data that matches the extraction conditions is extracted and displayed in the extraction result display area. On the other hand, when the "history" mode is selected, order history data that matches the extraction conditions is extracted and displayed in the extraction result display area. If no extraction conditions are specified, all data is displayed.

[0137] As described above, the commercial transaction business system 1 of this embodiment comprises a front-side system 100 and a back-end system 200. The front-end system 100 includes a front database for storing first transaction data, and a first processing unit 102a that inputs the first transaction data and stores it in the front database or outputs the first transaction data stored in the front database in response to a request from a trading partner via a website. The back-end system 200 includes a back-end database for storing second transaction data, a second processing unit 202a that inputs the second transaction data and stores it in the back-end database, and an integration processing unit 102b that synchronizes and links the data in the front database and the back-end database in both directions. Therefore, by distinguishing between the front-end database and the back-end database and synchronizing the data with each other, it is possible to limit the data that can be referenced on the front side.

[0138] [4. Application Examples of the Commercial Transaction Business System of the Present Invention] Fig. 12 is a diagram for explaining an application example of the commercial transaction system of the present invention, showing the correspondence between the main items of the commercial transaction system of the present invention and applicable systems (A) to (E).

[0139] System (A) shows an example of a system where orders are entered at the front desk and orders are entered at the back desk (explained in Figures 4 to 11). System (B) shows an example of a system where purchase history is checked at the front desk and sales are entered at the back desk. System (C) shows an example of a system where orders are checked at the front desk and orders are entered at the back desk. System (D) shows an example of a system where delivery date responses are entered at the front desk and order delivery date responses are entered at the back desk. System (E) shows an example of a system where receipt queries are made at the front desk and purchase orders are entered at the back desk.

[0140] Systems (A) and (B) are systems for providing goods and services. Systems (C) to (E) are systems for procuring goods and services. For example, system (A) described in Figures 4 to 11 shows the correspondence between key items required for bidirectional synchronization between the front-end database and the back-end database when the key item "transaction relationship" is "provision of goods and services," the key item "business content (front-end)" is "EDI order," and the key item "business content (back-end)" is "order." The key items are also superordinate concepts of each content in system (A). Similarly, systems (B) to (E) show correspondences that allow bidirectional or unidirectional synchronization using the same synchronization method. The mechanism of the present application allows flexible adaptation and expansion to a wide range of electronic commerce formats by applying the control of key items used in system (A) to the corresponding parts of each system in the same way.

[0141] [5. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0142] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0143] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0144] 6. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0145] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0146] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0147] Furthermore, with regard to the commercial transaction system 1, the components shown in the figure are functional concepts, and do not necessarily have to be physically configured as shown in the figure.

[0148] For example, all or any part of the processing functions of the commercial transaction system 1, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the commercial transaction system 1 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in the storage unit 106, such as a ROM or HDD (Hard Disk Drive). The computer program is executed by being loaded into RAM, and cooperates with the CPU to constitute the control unit 102.

[0149] This computer program may also be stored in an application program server connected to the commercial transaction system 1 via any network, and all or part of it may be downloaded as needed.

[0150] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0151] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0152] The various databases stored in the memory unit 106 are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0153] The commercial transaction system 1 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The commercial transaction system 1 may also be realized by installing software (including programs, data, etc.) that causes the information processing device to perform the processing described in this embodiment.

[0154] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or function additions. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0155] 1. Commercial transaction system 100 Front System 102 Control section 102a First processing unit 104 Communication interface unit 106 Storage section 106a Front Data Table 106b Front History Table 108 Input / Output Interface Section 112 Input Device 114 Output Device 300 Network 310 Customer terminal 200 Backyard system 202 Control section 202a Second processing unit 202b Collaboration processing unit 204 Communication Interface Unit 206 Memory section 206a Backyard Data Table 206b Backyard History Table 206c Collaborative business partner management master 206d Collaboration execution data table 208 Input / Output Interface Section 212 Input Device 214 Output Device 400 Network 410 Employee terminals

Claims

[Claim 1] A commercial transaction system for conducting electronic commerce with a trading partner for a predetermined transaction, the system comprising a front-end system and a back-end system, The front side system includes: a front database for storing first transaction data; a first processing means for inputting first transaction data and storing the first transaction data in the front database or outputting the first transaction data stored in the front database in response to a request from a trading partner via a website; Including, The backyard side system includes: a backyard database for storing second transaction data; second processing means for inputting second transaction data and storing it in the backyard database; a linking processing means for linking the data in the front database and the backyard database by synchronizing them in both directions; Including, The predetermined transaction is a transaction related to an order / received order, In the front-side system, The front database includes: a front data table for storing order data including an order number, a customer, a product, an update time, a linked flag specifying whether or not linked with order data, a linked time, and an order number; a front history table for storing order history data including an order number, a history category specifying new, updated, or deleted, a customer, a product, an update time, a linked flag specifying whether or not linked with order history data, a link time, and an order number; Including, The first processing means inputs new order data in response to an input operation by a business partner on an order input screen of the provided website, registers the new order data in the front data table, and registers order history data corresponding to the new order data in the front history table; In the backyard side system, The backyard database includes: A backyard data table for storing order data including an order number, a customer, a product, a link number which is the order number of linked order data, and an update time; a back-office history table for storing order history data including an order number, a history category specifying new, updated, or deleted, a customer, a product, a link number which is the order number of linked order data, and an update time; Including, the second processing means inputs order data, registers the order data in the backyard data table, and registers order history data corresponding to the order data in the backyard history table; A commercial transaction system characterized in that the linking processing means links the order data in the front data table / order history data in the front history table with the order data in the backyard data table / order history data in the backyard history table.

Images