WO2015198362A1

WO2015198362A1 - Coordination server, coordination program, and electronic commerce system

Info

Publication number: WO2015198362A1
Application number: PCT/JP2014/003362
Authority: WO
Inventors: 敏文秋田
Original assignee: 株式会社アイ・ピー・エス
Priority date: 2014-06-23
Filing date: 2014-06-23
Publication date: 2015-12-30
Also published as: US20160253730A1

Abstract

Provided is an electronic commerce system that is easy to build. A coordination server that coordinates an electronic commerce site with a core business system that displays products on the electronic commerce site is provided with a coordination data storage unit for storing coordination data that is configured on the basis of business data transmitted from the core business system, said core business system being provided with a business data storage unit for storing business data that is generated as a result of business. When the business data is updated by the core business system, the coordination server receives business data update content information that indicates business data update content from the core business system, updates the coordination data on the basis of the business data update content information that is received, and, when the coordination data is updated, performs processing for updating product data so as to reflect the business data update content.

Description

Cooperation server, cooperation program, and EC system

The present invention relates to a linked server that links an EC site that sells products on the Internet with reference to a product data storage unit that stores product data, and a core business system that displays products on the EC site, and the linked server The present invention relates to a cooperation program for functioning EC and an EC system.

Conventionally, a system (EC (electronic commerce) system) related to a distribution and wholesale service of IT (Information Technology) related products is known.

For example, information that includes distribution information for IT-related products with clients that support distribution and wholesale operations for distributing IT-related products from manufacturers to users on computers and communication networks, and that are arranged at each distribution stage from users to manufacturers. An EC system that exchanges information in real time via communication means is disclosed (see Patent Document 1).

JP 2001-344323 A

However, in the EC system described in the above-mentioned patent document, there is a problem that a maker that provides services using IT-related products needs to prepare data dedicated to the EC system such as a product database. That is, there is a problem that the design burden when constructing the EC system is large.

An object of the present invention is to solve the above-described problems and provide an EC system that can be easily constructed.

The linkage server of the present invention is a linkage server that links an EC site that sells products on the Internet with reference to a product data storage unit that stores product data and a core business system that sells products on the EC site. A data storage unit for cooperation that stores data for cooperation configured based on the business data transmitted from the core business system including business data storage means for storing business data generated in business; Update content information receiving means for receiving, from the core business system, business data update content information indicating the update content of the business data when the business data is updated by the business system, and the received business data update content information First linkage data updating means for updating the linkage data based on the update data, and the linkage data is updated. Occasionally, to; and a product data updating processing means for executing processing for updating the product data as updated contents of the operational data is reflected.

The above configuration makes it possible to provide an EC system that can be easily constructed.

When a purchase request for a product is received from a user of the EC site, second linkage data update means for updating the linkage data according to the content of the purchase request, and indicating that the purchase request has been accepted It may be configured to include purchase request information transmitting means for transmitting purchase request information to the basic business system.

The core business system includes a business data DB as the business data storage means, and the business data stored in the business data DB is data composed of at least one table, and has a table with the same structure. The process data may be configured to be data in which process data indicating data relating to each business process constituting the process flow is collected in the same entry in the table.

The basic business system includes at least two or more business data DBs, and further includes replica data receiving means for receiving replica data of each of the at least two business data DBs and data obtained by integrating the received replica data. In addition, it may be configured to include first cooperation DB update means for updating the cooperation DB as the cooperation data storage means.

The first cooperation DB update means may be configured to update the cooperation DB so that data obtained by integrating the received plurality of replica data as it is is used as cooperation data.

Second linkage data update means for updating a linkage DB as the linkage data storage means so that data including at least process data corresponding to display items displayed on the EC site is used as linkage data; It may be configured.

The product data update processing unit updates the product data by transmitting the business data update content information to an EC site management server that manages the EC site, and the EC site management server includes the product data storage unit. And EC page generation means for generating EC pages constituting the EC site with reference to the product data storage means.

The server that manages the EC site may be the linkage server, and the server including the product data storage unit may be the linkage server.

In addition, the cooperation program of the present invention links an EC site that sells products on the Internet with reference to product data storage means for storing product data and a core business system that sells products on the EC site. A linkage program for controlling the server,
In the cooperation server provided with the cooperation data storage means for storing the cooperation data configured based on the work data transmitted from the core business system provided with the work data storage means for storing the work data generated in the work, Update content information reception processing for receiving business data update content information indicating the update content of the business data when the business data is updated by the core business system, and the received business data update content information And a process for updating the product data so that the update contents of the business data are reflected when the cooperation data is updated. This is to execute the product data update process for executing

The EC system of the present invention also includes an EC site for selling products on the Internet with reference to product data storage means for storing product data, a core business system for selling products on the EC site, and the EC site. And a linkage server that links the mission-critical business system, the mission-critical system includes business data storage means for storing business data generated in business, and the linkage server includes the business data Coordination data storage means for storing cooperation data configured based on the business data transmitted from the core business system comprising storage means, and the business data when the business data is updated by the core business system Update content information for receiving business data update content information indicating data update content from the core business system Receiving means, first cooperation data updating means for updating the cooperation data based on the received business data update content information, and when the cooperation data is updated, the update content of the business data is And product data update processing means for executing processing for updating the product data so as to be reflected.

According to the present invention, an EC system that can be easily constructed can be provided.

It is a block diagram which shows the structural example of EC system which concerns on 1st Embodiment. It is explanatory drawing which shows the example of the storage state of process flow data. It is a block diagram which shows the structural example of a cooperation server. It is explanatory drawing which shows the example of the storage state of transaction data. It is explanatory drawing which shows the example of the storage state of the data for cooperation. It is explanatory drawing which shows the example of the storage state of goods data. It is a conceptual diagram which shows the concept of EC system. It is a conceptual diagram which shows the concept of EC system. It is a flowchart which shows the example of DB update process for cooperation. It is a flowchart which shows the example of a 1st update process. It is explanatory drawing which shows the example of the storage state of the updated data for cooperation. It is explanatory drawing which shows the example of the storage state of the updated transaction data. It is a flowchart which shows the example of a 2nd update process. It is explanatory drawing which shows the example of the storage state of the updated merchandise data. It is a flowchart which shows the example of a business data update process. It is a flowchart which shows the example of the 2nd update process which concerns on 2nd Embodiment. It is a block diagram which shows the structural example of EC system which concerns on 2nd Embodiment. It is a flowchart which shows the example of the 1st update process which concerns on 2nd Embodiment.

[First Embodiment]
An example of the first embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a configuration example of an EC system 500 according to the first embodiment of the present invention. As shown in FIG. 1, the EC system 500 includes a linkage server 10, user terminals 41 to 4N (N is an arbitrary positive integer), a basic business system (system integrated basic business system 100, and integrated basic business system 200). And an integrated core business system 300).

The linkage server 10 includes an integrated backbone business system 100, an integrated backbone business system 200, an integrated backbone business system 300, user terminals 41 to 4N, and

communication networks

51 and 52 such as a LAN (Local Area Network) and a dedicated communication line, respectively. , 53, 54. The linkage server 10 of this example refers to a merchandise data storage unit that stores merchandise data, and links an EC site that sells merchandise on the Internet and a core business system that sells merchandise on the EC site. It is a server. A detailed description of the cooperation server will be given later.

The integrated core business system 100 includes a core business server 110, a data warehouse server (DWH server) 120, a cooperation program DB 130, and a process flow DB 101. The integrated core business system 200 includes a DWH server 220, a cooperation program DB 230, and a process flow DB 201. The integrated core business system 300 includes a core business server 310, a cooperation program 330, and a process flow DB 301.

A plurality of integrated

core business systems

100, 200, and 300 having different configurations communicate with a predetermined server on which an ERP operates as necessary (that is, according to the functions of each), thereby forming an integrated core business system. Demonstrate the function. That is, in the EC system 500, even if the system 200 does not have a mission-critical server or the system 300 does not have a DWH server, the integrated mission-critical business can be performed by communicating with a predetermined server on which ERP operates. Can function as a system. The EC system may be configured such that a predetermined server on which the ERP operates is provided in each of the integrated

core business systems

200 and 300. In each core business system (for example, the integrated

core business system

100, 200, 300), components having the same name have the same configuration, and therefore, all the systems in the integrated

core business system

100, 200, 300 are included. An explanation will be given taking the integrated core business system 100 including the common components as an example.

It is assumed that the core business server 110 and the DWH server 120 are connected by a dedicated communication line.

The core business server 110 is a server managed by, for example, an administrator of the integrated core business system 100, and has various functions for managing form information related to various business (for example, creation, update, storage, etc. of information). Have. The core business server 110 is configured by a general information processing apparatus including an OS (Operating System) and a relational DB.

Here, the form is data generated in business and is a general term for books and slips. In addition, a book is a field in which items relating to cash and goods are entered, and a slip is data that is the basis for creating a book and is evidence of business transactions. In this example, the case where the core business server 110 handles process data indicating only slip data as form data will be described as an example.

The core business server 110 executes various processes according to the business application program. Examples of application programs include a sales business management program, a sales business management program, a production management program, a financial accounting management program, and a management accounting management program.

The DWH server 120 is a server managed by an administrator of the system, for example, and has various functions for realizing a data warehouse. Here, the data warehouse refers to a system that analyzes the relationship between items from business data such as form data accumulated in time series. Also, the DWH server 120 has a function of registering various data in a predetermined storage area (a business related data DB 101b described later) by converting a CSV file transferred from the core business server 110 into a predetermined data format. Have Note that the DWH server 120 may be configured to extract data corresponding to each storage area from a CSV (CommaparSeparatedsValues) format state without converting the data format.

The cooperation program DB 130 is a DB in which a cooperation program for executing processing for reflecting update information on the entire EC system in real time is stored. Here, as processing executed according to the cooperation program, for example, processing for receiving data transmitted from the EC system cooperation server 10, input to a WEB page of an EC site (not shown) that does not belong to the EC system 500 Processing to receive the received data, processing to update the process flow data stored in the process flow DB 101 based on the received data, processing to notify the EC system cooperation server 10 that the process flow data has been updated, and delivery There are a process for sending a shipping instruction to a terminal (not shown) managed by a merchant, a process for receiving a shipping record from a terminal managed by a delivery company, and the like.

Although not shown in particular, the integrated core business system 100 of this example includes an inventory information storage unit that stores inventory information calculated based on information relating to loading and unloading in the process flow data. The inventory information of this example includes an item ID that can uniquely identify an item, an actual stock quantity, and an order-receiving quantity. Here, “actual stock quantity” is information indicating actual stock. Further, “quantity during order reception” is information indicating the quantity before delivery out of the number of orders received.

The process flow DB 101 includes various process data (or form data) collected and organized by various information processing using various programs stored in an application program DB (not shown) of the core business server 110. A storage medium for storing business data. In this example, the case where process flow data is handled as business data will be described as an example. Therefore, hereinafter, business data may be referred to as process flow data.

FIG. 2 is an explanatory diagram illustrating an example of a storage state of process flow data in the process flow DB 101. As shown in FIG. 2, the process flow data in this example is composed of at least one table, and includes a main key part, a reference key part, a type part, a status part, a common data part, and process specific data. Part. Each item corresponding to each part of the process flow data (that is, each column item in the process flow table) indicates the type of process data constituting the process flow data. That is, data (process data) related to each business process constituting the process flow is allocated and stored in each part (each item) constituting the process flow data.

Note that in the system 500 of this example, the process flow data is composed of at least one table, is composed of tables having the same structure, and data in which data relating to one process flow is collected in the same entry in the table. The case of using as will be described as an example.

In this example, data stored as process flow data is the basis of data related to products or services that are subject to electronic commerce. That is, in this example, the process flow data stored in the process flow DB 101 is used as the basis of product data in the EC system 500.

Process data relating to one process flow (for example, a series of process flows from order receipt to delivery from a certain company) is stored in the same entry (that is, the same row in the process table PT) in the process flow table. That is, the process flow data has a structure in which data related to one process flow is collected in the same entry in the process flow table. According to such a configuration, it is possible to define the correspondence between the process data.

Here, the “primary key part” is a part in which primary key data, which is data for uniquely identifying the process flow data, is stored in the process flow data. In this example, the main key part is composed of a process flow number and a process flow detail number. That is, in this example, a combination of a process flow number and a process flow detail number becomes an identifier (ID) of each process flow data. The main key part is updated when the process flow data is registered for the first time. Here, “when process flow data is registered for the first time” means, for example, when process data belonging to a certain process flow and corresponding other process data is not registered is registered. Shall. The “update” here includes addition of data.

The “process flow number” is an identifier for specifying one process flow data (that is, one column in the process flow table shown in FIG. 2). The process flow number is assigned to each process data having the same predetermined item. In this example, the same number is assigned to the process flow number of the process flow number that has the same type and the order-receiving party in the process flow data.

Further, the “process flow detail number” is an identifier for identifying specific process flow data from among the process flow data assigned with the same process flow number. For example, the process flow table shown in FIG. 2 indicates that the business process “order” in the process flow type “inventory sales” indicates that the business of the amounts “1200” and “2600” has been received from the order recipient “T001”. The process flow data including the data can be uniquely specified by a combination of the process flow number “000001” and the process flow detail number “0010” or “0020”, respectively.

Next, the “reference key part” is data for specifying other process flow data (or other process data) related to the process flow, such as the original transaction for sales returns, among the process flow data. This is the part where key data is stored. In this example, the reference key part is composed of a reference number and a reference specification number. The reference key part is updated when the process flow data is registered for the first time.

It should be noted that the process number and process flow detail number of other process flows related to the process flow are stored in the reference number and the reference detail number, respectively. However, when there is no other process flow related to the process flow, such as in the case of a new transaction, the reference key portion contains data indicating the same value as the primary key portion of the same entry (that is, the reference number is a process) A flow number is stored, and a process flow item number is stored in the reference item number. Further, when the reference key part indicates other process data related to the process flow, the reference key part is further provided with data for specifying the type of the process data.

In addition, the “type part” is a part in which type data that is a type of process flow, such as inventory sales and sample shipment, is stored in the process flow data. The type part is updated when the process flow data is registered for the first time. Note that the type of process flow is not limited to inventory sales or sample shipment. Also, it is assumed that which process is required for each type of process flow is determined in advance (that is, the type and number of business processes included in each type of process flow are different). A plurality of other types of process flows will be presented later.

In addition, the “status part” stores status data that is data indicating the progress of the process flow (that is, data indicating the progress of each of a plurality of business processes included in the process flow) among the process flow data. Part. In this example, the status data indicates the progress of each business process by setting “0” for the unfinished business process and “1” for the completed business process for the business process required by the process flow. Show. For example, as shown in FIG. 2, the process flow of “inventory sales”, and the business processes included in the process flow are “order receipt”, “shipment”, “issue”, “exception inspection”, and “sales”. In some cases, it is assumed that process-specific data (for example, order date) relating to the business process “order received” is registered. In this case, in the status data, the portion corresponding to “sales” is “1”, and the other portions remain in the initial state (ie, the state in which “0” is set).

That is, the status part in this example is updated for each business process. In other words, the status part is updated when process-specific data to be described later is input, specifically, when it is determined that each business process is completed because a predetermined status change condition is satisfied. Although the status change condition is not particularly limited, in this example, “all process specific data corresponding to one business process is input” is stored in a predetermined storage area of the integrated core business system 100 as the status change condition. It shall be remembered.

In this example, since different types of process flows are stored in the same table, a part of the items (column items) constituting the table stores unnecessary process data in a specific process flow. In some cases. In this case, in the process flow table, a part for storing unnecessary process data is empty data, and “0” is stored in status data corresponding to the empty data.

In addition, the “common data part” is data that does not depend on the business process such as the order receiving party and the shipping destination among the process flow data (that is, common data between business processes included in the same process flow). This is the part where data is stored. The common data part is updated when the process flow data is registered for the first time. The “common data portion” in this example includes an image indicating an item ID, a quantity, and an item for uniquely identifying the item.

In addition, the “process specific data part” is a text that indicates precautions such as the order date and data registered in each business process in the process flow data (for example, “delivery deadline” and “breaker”) Data), etc., is a part in which process-specific data that is data unique to each business process included in the same process flow is stored. The process specific data part is updated for each business process. Therefore, in this example, it can be said that the process flow data based on the business process is “process-specific data” and the data not based on the business process is “common data”.

The above is the description of the process flow data in this example. Here, the definitions of various terms shown in FIG. 2 will be briefly described.

First, “order received” means a state in which an order is received from a customer and a contract with the customer is concluded. That is, in this example, “order received” means a state including not only a case where an order is received from a normal customer but also a case where an order is received from a user of an EC site.

Also, the “shipment instruction” means a state in which an instruction to ship a product is given to a warehouse company or a logistics person. That is, in this example, it means a state in which a user who has purchased a product at the EC site has been instructed to ship the product.

Also, “shipping” means a state in which the goods are shipped from the warehouse and the movement is started. In other words, in this example, it means that a product purchased by a user of the EC site is shipped from the warehouse.

Also, “acceptance” means a state in which the acceptance of the customer is completed and the ownership of the product is transferred to the customer.

Also, “sales” means a state in which the customer's acceptance has been confirmed and the amount of receivables from the customer has been finalized (= accounting for receivables).

In addition, the term “acceptance” means “business to inspect whether the delivered product or service has the specifications as ordered (= quantity, color, shape, quality as ordered)” or “ It is also used to mean “ownership is transferred”. Note that, in financial accounting (or institutional accounting) and the ERP system, in order to clarify the timing of asset ownership transfer, an event “acceptance” is defined separately from shipping.

In this example, the process flow data includes generally used slip data (for example, for the slip data corresponding to the order slip, the order slip header information, the order slip detail information, the delivery date schedule, etc. Is stored in a structure that can be searched based on the key such as the slip number, etc. Note that the slip number includes the order number, order number, shipping number, entry / exit number, invoice inquiry, billing number, Account number etc. are included)).

Note that the EC system 500 of this example is configured such that process flow data is managed by one process flow table as described above. However, the basic business system (for example, the integrated core business system 100) is not limited to such a configuration, and the process flow data is, for example, for each type described later or a part of the content of common data described later (for example, A configuration may be adopted in which, for each item with the same order recipient, etc., management is performed using a plurality of tables.

The cooperation server 10 is a server for linking an EC site managed by itself with a core business system (integrated

core business system

100, 200, 300). The cooperation server 10 is configured by an information processing apparatus such as a WWW server, for example, and is managed by an administrator of the EC system 500 or the like.

FIG. 3 is a block diagram illustrating a configuration example of the cooperation server 10. As shown in FIG. 3, the linkage server 10 includes a control unit 11 that performs various controls, a transaction data DB 14, a linkage DB 15, a product data DB 16, a business application program DB 17, a process flow DB 18, a DWHDB 19, And a DB 10X for storing various data (for example, data used by various programs stored in the business application program DB 17) necessary for realizing a function as a general core business server.

The control unit 11 includes a communication processing unit 11a, a data update processing unit 11b, a coordination DB update processing unit 11c, and an EC site management processing unit 11d. Each processing unit included in the control unit 11 executes each process based on a program stored in the business application DB 17.

The communication processing unit 11a has a function of executing processing for transmitting data used in the EC system 500 to other terminals, processing for receiving from other terminals, and the like.

The data update processing unit 11b has a function of executing processing for updating data used in the EC system 500. Specifically, the data update processing unit 11b executes processing for adding / deleting data, processing for writing data in a predetermined writing area, and the like.

The EC site management processing unit 11c executes processing for causing the cooperation server to function as an EC site management server for managing the EC site. Specifically, the EC site management processing unit 11d confirms that a process for receiving a purchase request for a product from a user on the EC site, a process for updating linkage data according to the content of the purchase request, and a purchase request are received. A function of executing processing for transmitting the purchase request information shown to the core business system.

The transaction data DB 14 is a storage medium that stores transaction data including purchase request information transmitted from the user terminals 41 to 4N. Transaction data is data constituting an EC site.

FIG. 4 is an explanatory diagram showing an example of a storage state of transaction data stored in the transaction data DB 14. As shown in FIG. 4, the transaction data is information stored when purchase request information is received from the user terminals 41 to 4N, and includes a user ID, a process flow number, a core business system ID, an item ID, and the like. , Quantity and status information. Note that the status information becomes “in order” when data is added (that is, when a purchase request is accepted), and then updated appropriately according to the progress of the process (for example, “shipped”, etc.) To be updated).

Here, the core business system ID is ID information for specifying the core business system as the exhibitor. For example, an identifier “K0001” is stored in the product exhibited by the integrated core business system 100.

The cooperation DB 15 is a storage medium for storing cooperation data for linking the EC site and the core business system (integrated

core business system

100, 200, 300).

Here, the cooperation data is process flow data transmitted from a core business system (for example, the integrated core business systems 100 and 200). In this example, the linkage server 10 is configured to include one linkage DB 16, but may be configured to include a plurality of DBs in which each replica data is stored.

FIG. 5 is an explanatory diagram showing an example of the storage state of the cooperation data stored in the cooperation DB 15. In this example, since the process flow data is integrated as it is without changing the configuration of the process flow data, the link data has the same configuration as the process flow data stored in the process flow DB 101 described above. .

The product data DB 16 is a storage medium that stores product data for configuring an EC site.

FIG. 6 is an explanatory diagram showing an example of the storage state of the product data stored in the product data DB. As shown in FIG. 6, the product data is data constituting an EC site, and includes a core business system ID, an item ID, an image, and an inventory quantity.

Here, the stock quantity is information indicating the stock quantity of the product. The inventory quantity managed here is updated by the EC site management processing unit 11d when the cooperation server 10 receives an order from the user terminal. Specifically, it is rewritten to a value obtained by subtracting the order quantity from the current inventory quantity.

The business application program DB 17 is a storage medium that stores programs used for various businesses. The business application program DB 17 stores various programs such as a sales business management program, a sales business management program, a production management program, a financial accounting management program, a management accounting management program, a data update processing program, and a data transmission / reception processing program.

The process flow DB 18 is a storage medium that stores process flow data including various process data (or form data) collected and organized by various information processing using various programs stored in the business application program DB 17. is there. The process flow data stored in the process flow DB 18 is generated based on information (for example, process flow data) transmitted from each core business system.

In this example, the cooperation server 10 provides various data stored in the process flow DB 18 and other DB 10X in response to a request from a predetermined external device (for example, the integrated

core business system

100, 200, 300). It has composition which has. Therefore, the cooperation server 10 has a function as a core business server. In other words, the cooperation server 10 includes an ERP engine.

Although not shown, in this example, the cooperation server 10 can have a function as a DWH server having various functions for realizing a data warehouse. When the cooperation server 10 includes an ERP engine and a configuration for functioning as a DWH server, the integrated core business system 100 having different configurations (for example, the integrated core business system 100 having both the core business server and the DWH server). And the integrated mission-critical business system 200 having only the DWH server and the integrated mission-critical business system 300 having only the DWH server). .

Each of the user terminals 41 to 4N is an information processing apparatus such as a portable terminal or a PC including a CPU (Central Processing Unit), a ROM, a RAM, and a display unit. Here, the business partners assumed as users include not only final consumers but also companies and public institutions.

Each user terminal 41 to 4N communicates with the cooperation server 10 via the relay device 20 and the communication network 54. Each of the user terminals 41 to 4N includes a storage medium that stores various applications such as a Web browser that can browse EC pages. Each of the user terminals 41 to 4N has a function of acquiring product data from the cooperation server 10 in accordance with, for example, an operation input by the user, and displaying the acquired product data.

Next, the concept of the EC system 500 of this example (hereinafter sometimes referred to as the system 500) will be described with reference to the drawings.

FIG. 7 is a conceptual diagram showing the concept of the EC system of this example. More specifically, FIG. 7 is a conceptual diagram showing a flow of building a basic configuration. As shown in FIG. 7, the EC system can be roughly divided into three sections. Specifically, the EC system includes an online shop section that sells products and services, a plurality of core business system sections (main business systems A, B, and C) that manage data generated in business, an online shop section, It consists of a data management section for linking that links with the core business system section. Here, the online shop section and the linkage data management section are configured by one server.

In the EC system of this example, each core business system first generates a replica of its own DB and transmits the generated replica to the cooperation server. The linkage server manages a plurality of received DBs of each basic business system as one DB (see “DB integration processing” in FIG. 7). And a cooperation server manages several DB as 1 DB. Further, the cooperation server generates site management data for managing the EC site based on the integrated DB and stores it in the DB. This site management data becomes the product master. In this way, a basic configuration of an EC system is constructed that directly uses each DB managed by a plurality of basic business systems.

FIG. 8 is a conceptual diagram showing the concept of the EC system of this example. More specifically, FIG. 8 is a conceptual diagram showing a flow of processing for handling real-time information at the EC site. In the EC system having the basic configuration shown in FIG. 7, when the information is updated in the core business system section, the updated content is transmitted to the cooperation server. The cooperation server updates the site management DB based on the transmitted information (see “first update process” in FIG. 8). For example, in the core business system, when product inventory data fluctuates due to the occurrence of a shipping process, the fact is notified to the cooperation server and the site management server, and information relating to the change is reflected in real time.

On the other hand, when a product (or service) purchase request is accepted in the online shop section, the purchase request content is transmitted to the linkage server. The cooperation server updates the DB based on the transmitted information (see “second update process” in FIG. 8). Then, the cooperation server transmits the updated content to the core business system side. At this time, the DB is updated based on the purchase request contents in the core business system section, and the update result is notified to the cooperation server. Upon receiving the update notification, the cooperation server updates the site management DB based on the content of the update notification.

As described above, the EC system can easily manage data managed by a plurality of mission-critical systems as one DB. Furthermore, the data managed by the core business system, a part of the data managed by the linkage server, and the data used at the EC site are synchronized almost in real time. In this way, the EC system can realize electronic commerce with a simple configuration, and the electronic commerce site can reflect the update information in the system in the entire EC system in real time. Will be able to provide.

Next, the operation of the system 500 of this example will be described with reference to the drawings. Note that the contents of operations and processes not particularly related to the present invention may be omitted.

First, the cooperation DB update processing executed by the cooperation server 10 in the system 500 of this example will be described.

FIG. 9 is a flowchart showing an example of the coordination DB update process executed by the collaboration server 10 in the system 500 of this example. Here, a case will be described as an example where there are a plurality of core business systems (for example, a company or a predetermined group within a company) included in the EC system 500. Further, a case where data transmitted from a plurality of mission-critical systems is integrated as one data will be described as an example.

In the cooperation DB update process, first, the cooperation server 10 receives DB replica data from each of the core business systems (integrated

core business systems

100, 200, 300) included in the EC system (step S101). In this example, three DBs are received. Specifically, the cooperation server 10 receives the replica data of the process flow DB 101 from the integrated core business system 100. Further, the cooperation server 10 receives the replica data of the process flow DB 201 from the integrated core business system 200. Further, the cooperation server 10 receives the replica data of the process flow DB 301 from the integrated core business system 300. Note that the data received in step S101 includes a mission-critical system ID for uniquely identifying the mission-critical business system that is the transmission source.

The system 500 of this example is configured to transmit DB replica data stored in the mission-critical business system 100. However, the data necessary for the mission-critical business system 100 to configure an EC site is extracted. And may be configured to transmit.

When a DB replica is received from each core business system, the cooperation server 10 integrates each received replica data into one data, and updates the cooperation DB based on the integrated data (step S102). As described above, in this example, the process flow data stored in each of the received three DBs is data composed of at least one table, data composed of tables having the same structure, and 1 This is data in which data relating to the process flow is collected in the same entry in the table. Therefore, the cooperation server 10 can generate the data for cooperation by integrating the replica data of the DBs as they are. According to such a configuration, since the number of tables included in the process flow data can be minimized, it is possible to reduce the capacity of data necessary for constructing the EC site. . When an EC system that handles a plurality of process flow data stored in the core business system as in this example is constructed, the EC system can be constructed with a simple configuration.

In this example, the cooperation server 10 generates one cooperation DB 15 by receiving a replica of the DB managed by each basic business system from each of a plurality of basic business systems included in the EC system. It is configured. However, the system 500 of this example is not limited to such a configuration. For example, the cooperation server 10 may be configured to generate one cooperation DB from a plurality of DBs by receiving replica data of each of a plurality of process flow DBs included in one core business system. Furthermore, the cooperation server 10 may be configured to generate one cooperation DB by receiving replica data of one process flow DB included in one core business system.

Also, when building the cooperation DB, based on the received process flow data, data related to the display item displayed on the EC site is extracted from the data related to the process flow. It is also possible to construct a linkage DB having a structure that is grouped in the same entry. Specifically, the cooperation server 10 includes a storage unit including data indicating display items displayed on the EC site, and displays the data displayed on the EC site among the data relating to the process flow with reference to the data. What is necessary is just to be comprised so that the data regarding the item corresponding to an item may be extracted.

When the cooperation DB is updated by integrating the data as 1 data, the cooperation server 10 updates the product data DB based on the cooperation data (step S103). That is, the product data for configuring the EC site is generated based on the cooperation data. Specifically, data corresponding to predetermined items (for example, item ID, basic business system ID, inventory quantity, status) in the cooperation data is extracted, and each extracted item is stored in the product data DB.

When the product data DB is updated, the linkage server 10 ends the linkage DB update process.

Next, an example of the first update process executed by the cooperation server 10 in the system 500 of this example will be described. In the first update process, a process of reflecting the update contents of the process flow data on the EC site is executed.

FIG. 10 is a flowchart showing an example of the first update process executed by the cooperation server 10 in the system 500 of this example. In the first update process, various data are transmitted from each core business system. However, in the first update process described below, data is transmitted from the integrated core business system 100, and the transaction data shown in FIG. The case where the data for cooperation shown and the product data shown in FIG. 6 are updated will be described as an example. In this example, it is assumed that the process loops while the cooperation server 10 is operating.

In the first update process, first, the cooperation server 10 receives business data update information (process flow data update information) indicating that the integrated core business system 100 has updated the process flow DB 101 from the integrated core business system 100 (steps). S201). The business data update information includes the added table and a core business system ID indicating the integrated core business system 100 of the transmission source. Here, the business data update including the core business system ID of “K00001”, the process flow data whose “shipping” is “1”, “item ID” is “S00001”, and “order received” is “T001” Information will be described as an example.

When the business data update information is received, the cooperation server 10 updates the cooperation DB 15 based on the received business data update information (step S202). Specifically, a new table as data received in step S201 is added to the bottom of the cooperation data shown in FIG. That is, the cooperation data shown in FIG. 5 is updated to the cooperation data shown in FIG.

When the cooperation DB 15 is updated, the cooperation server 10 updates the DB according to the update content (step S203). That is, referring to the status part in the updated linkage data, it is determined which information (DB) is to be changed, and the product data DB is updated according to the determination. As shown in FIG. 11, in this example, since the status of the added table is “issue”, “T001” is identified with reference to “order received” in the added table, and the status is changed to issue. Transaction data is identified. Then, as shown in FIG. 12, the status of the identified location is changed from “pending order” to “shipped”. That is, the transaction data shown in FIG. 4 is updated to the transaction data shown in FIG.

When the DB is updated, the cooperation server 10 proceeds to step S201 and waits until business data update information is received.

Next, an example of the second update process executed by the cooperation server 10 in the system 500 of this example will be described. FIG. 13 is a flowchart illustrating an example of the second update process 2 executed by the cooperation server 10 in the system 500 of the present example. In the second update process, a purchase request for a product is transmitted from the user terminals 41 to 4N. In the second update process described below, an example in which a purchase request for a product is transmitted from the user terminal 41 will be described. To do. Further, in this example, a case where a purchase request for a product is transmitted will be described as an example. However, a configuration may be used in which a browsing request such as information regarding the shipment status of a product is transmitted. In this example, it is assumed that the process loops while the cooperation server 10 is operating.

In the second update process, first, the cooperation server 10 receives a purchase request from the user terminal 41 (step S301).

When the purchase request information is received, the linkage server 10 stores the purchase request information in the transaction data DB 14 and updates the linkage DB 15 (step S302). Specifically, a new table to which a process flow detail number is assigned based on the process flow number in the purchase request information is added, and other information included in the purchase request information such as the core business system ID is added to the new table. Stored in

When the cooperation DB 15 is updated, the cooperation server 10 updates the product data DB 16 (step S303). Specifically, product data to be updated is specified based on the core business system ID and the item ID. Specifically, in the product data, the same data as the core business system ID and item ID indicated by the purchase request information is specified, and the stock quantity of the specified data is subtracted by the purchase quantity. For example, in the case where the product data shown in FIG. 6 is stored, the purchase request information with “usage business system ID” “00001”, “item ID” “S00001”, and “purchase quantity” “3”. When received, “stock information” is updated from “25” to “22” as in the product data shown in FIG.

When the product data DB 16 is updated, the linkage server 10 identifies the core business system corresponding to the purchase request information (step S304). That is, the core business system that is the merchandise exhibitor is specified. The corresponding core business system refers to the core business system that has transmitted the replica data corresponding to the information transmitted from the user terminal to the cooperation server 10 in step S101 described above.

When the core business system corresponding to the purchase request is identified, the cooperation server 10 transmits purchase request information to the identified core business system (step S305). In the system 500 of this example, the purchase request information is transmitted to the integrated core business system 100. However, the table added in step S302 may be transmitted.

When the purchase request information is transmitted, the cooperation server 10 proceeds to step S301 and waits until the purchase request information is received.

Next, an example of business data update processing executed by the core business system (integrated

core business system

100, 200, 300) in the system 500 of this example will be described. In the business data update processing of this example, the case where the integrated core business system 100 executes processing in the core business system will be described as an example.

FIG. 15 is a flowchart showing an example of business data update processing executed by the integrated core business system 100 in the system 500 of this example. The business data update process of this example is executed by the cooperation program included in the cooperation program DB 130. Further, in the business data update process, a process of transmitting predetermined data to a terminal managed by the cooperation server 10 or a delivery company or the like is executed with the reception of information that requires process flow data being received as a trigger. In this example, it is assumed that the process loops while the core business system 100 is operating.

In the business data update process, first, the integrated core business system 100 receives information that requires the process flow DB 101 to be updated (step S401). The data received here is, for example, purchase request information indicating that there is a purchase request for a product transmitted from the cooperation server 10, or a new process flow input by direct input by the administrator of the integrated core business system 100 Data (that is, one column in the process flow table shown in FIG. 2), process flow data related to shipment results transmitted from a terminal managed by the delivery company, and the like.

When the information requiring the update of the process flow DB 101 is received, the integrated core business system 100 updates the process flow DB 101 based on the input data (step S402). Specifically, a new table to which a process flow detail number is assigned based on the process flow number in the purchase request information is added, and other information included in the purchase request information such as the core business system ID is added to the new table. Stored in

When the process flow DB 101 is updated, the integrated core business system 100 determines whether or not the process flow DB 101 has been updated based on the receipt of the purchase request information (step S403).

When it is determined that the process flow DB 101 has been updated based on the receipt of the purchase request information (Y in step S403), the integrated core business system 100 requires other processing for the data received in step S401. It is determined whether or not the information is to be processed (step S405).

On the other hand, when it is determined that the update of the process flow DB 101 is not based on the purchase request information (N in step S403), the integrated core business system 100 displays information indicating that the process flow DB 101 has been updated. It transmits to the cooperation server 10 (step S404). That is, the integrated core business system 100 transmits the business data update information to the cooperation server 10.

When the process flow data update information is transmitted to the linkage server 10, the integrated core business system 100 determines whether the data received in step S401 is information that requires other processing (step S405).

When it is determined that the data received in step S401 is information that requires other processing (Y in step S405), the integrated core business system 100 executes processing according to the contents of the data (step S405). S406). When the processing according to the content of the data is executed, the integrated core business system 100 returns to step S401 and waits until data requiring update of the process flow DB is input.

Here, the “information that requires other processing” is, for example, information that requires a shipping instruction to a delivery company, information that indicates that a predetermined product has been issued, and the like. For example, if information that requires a shipping instruction for the delivery company is received in step S401, the integrated core business system 100 transmits the shipping instruction to a terminal managed by the delivery company that is the shipping source. Execute. For example, when data indicating that a predetermined product has been issued is received in step S401, the integrated core business system 100 updates the inventory quantity in the inventory information by subtracting the number of goods issued.

Here, the “process in the case where information indicating that a predetermined product has been delivered has been received in step S401” executed as other processing will be described in detail. In the processing, the core business system 100 specifies “item ID” and “quantity” with reference to the “common data portion”. Thereafter, the core business system 100 identifies inventory information corresponding to the item ID identified with reference to the inventory information storage unit. Then, the core business system 100 updates the “quantity” specified above by subtracting it from the “real inventory quantity” and “quantity on order” stored in the inventory information. In this way, the process in the case where information indicating that the predetermined product has been issued is received in step S401 is executed.

On the other hand, when it is determined that the data input in step S401 is data that does not require other processing (N in step S405), the integrated core business system 100 returns to step S401, and the process flow DB Wait until data that needs to be updated is entered.

As described above, in the first embodiment described above, an EC site that sells products on the Internet with reference to a product data storage unit (product data DB 16) that stores product data, and the EC site. The linkage server that links the core business system that sells products to the system is transmitted from the core business system (integrated core business system 100) that includes the business data storage unit (process flow DB 101) that stores business data generated in business. Business data update content that includes a data storage unit for collaboration (cooperation DB 15) that stores data for collaboration configured based on business data, and indicates business data update content when business data is updated by the core business system Receive information from the core business system, and link data based on the received business data update content information New, when updating linking data, configured to perform a processing for updating the product data as updated contents of the business data is reflected. According to such a configuration, an EC system that can be easily constructed can be provided by using data managed by the core business system. In addition, since the update information on the core business system side can be reflected in the entire EC system in real time, the user browsing the EC site can browse the information with high accuracy. In addition, when information is updated on the core business system side, no special operation is required to change the information displayed on the EC site, so it is built based on information managed by the core business system. In the EC system, the burden on the manager of the core business system side can be reduced.

In the first embodiment described above, when the cooperation server receives a purchase request for a product from a user of the EC site, the cooperation server updates the data for cooperation according to the content of the purchase request, and issues a purchase request. Purchase request information indicating acceptance is transmitted to the core business system. According to such a configuration, since update information generated at the EC site can be reflected in the entire EC system in real time, a user browsing the EC site can browse information with high accuracy.

In the first embodiment described above, the basic business system includes a business data DB (process flow DB 101). The business data (process flow data) stored in the business data DB is data composed of at least one table and is composed of tables having the same structure, and each business constituting the process flow. Process data indicating process data is configured to be data that is collected in the same entry in the table. According to such a configuration, the number of tables included in the business data can be minimized, so that it is possible to reduce the capacity of data necessary for constructing the EC site.

Further, as mentioned in the first embodiment, the basic business system includes at least two business data DBs, and further receives replica data of each of at least two business data DBs. And the cooperation DB as the cooperation data storage means is updated based on the data obtained by integrating the received replica data. According to such a configuration, even when there are a plurality of DBs that store business data, the number of programs used for data management is reduced by managing a plurality of business data as data combined into one. It becomes. Therefore, the required data capacity can be reduced, and even when an EC system including different core business systems is constructed, it can be flexibly handled.

In the first embodiment described above, the cooperation server is configured to update the cooperation DB so that data obtained by integrating the received plurality of replica data as it is is used as the cooperation data. According to such a configuration, when an EC system is constructed by handling a plurality of business data stored in the core business system, the EC system can be constructed with a simple configuration.

Further, as mentioned in the first embodiment described above, the linkage DB is set so that the linkage server uses, as linkage data, data including at least process data corresponding to display items displayed on the EC site. It may be configured to update. According to such a configuration, since data constituting the table can be reduced, the capacity of data necessary for constructing an EC site can be reduced while system construction is easy. It becomes like this.

As mentioned in the first embodiment, the basic business system in the system includes an item ID that uniquely identifies a product, a basic business system ID that uniquely identifies its core business system, and an inventory. An inventory information storage unit that stores inventory information including the quantity and the number of orders may be provided, and the inventory information may be updated when information indicating that the shipment has been received is received as business data update information. Specifically, the core business system determines whether the information that needs to be updated in the process flow data received in step S401 in the business data update process described above is information indicating that a product has been issued, It may be configured to update the stock quantity in the stock information when it is determined that the information indicates that it has been delivered. According to such a configuration, since temporary inventory information indicating temporary inventory information at the time of receiving an order and actual inventory information indicating actual inventory information can be managed separately, accurate information can be obtained. It becomes possible to handle.

Although not particularly mentioned in the first embodiment described above, the cooperation server 10 receives actual stock information from the core business system at a predetermined timing, and is included in the received actual stock information and product data. It may be configured to determine whether or not the numerical value matches the provisional inventory information, and to transmit an alert to the core business system when it is determined that the numerical value does not match. Note that the core business system to which the alert is transmitted displays the content of the alert on the display device that the alert is transmitted to. According to such a configuration, it is possible to notify in advance of troubles based on inconsistencies in inventory, and it is possible to take measures for obtaining accurate information on the notified main business system side.

The EC system according to the first embodiment has been described above. Next, an EC system according to the second embodiment will be described.

[Second Embodiment]
In the EC system 500 in the first embodiment, the linkage server 10 is configured to have a function as a server for managing an EC site. In the EC system 600 according to the second embodiment, a server different from the cooperation server 10 is configured to manage the EC site. Specifically, the EC site management server 30 is configured to function as a server that manages the EC site. In addition, below, when it has the structure similar to the description performed with the system 500 which concerns on 1st Embodiment mentioned above, the detailed description is abbreviate | omitted by performing description by the same code | symbol.

FIG. 16 is a block diagram showing a configuration example of an EC system 600 according to the second embodiment of the present invention. As shown in FIG. 16, the EC system 600 includes a linkage server 610, an EC site management server 30, a relay device 20, user terminals 41 to 4N (N is an arbitrary positive integer), and an integrated core business system 100. And an integrated core business system 200 and an integrated core business system 300.

The EC site management server 30 is a server that provides various data via the communication network 56 in response to requests from the user terminals 41 to 4N used by the user. The EC site management server 30 is configured by an information processing apparatus such as a WWW server, for example, and is managed by an administrator of the EC site.

As shown in FIG. 16, the EC site management server 30 includes a control unit 31 that performs various controls, a product data DB 32, a transaction data DB 33, and a DB that stores a control program for configuring an EC site. That is, the EC site management server 30 according to the second embodiment includes a configuration corresponding to the product DB 16 and the EC site management processing unit 11d included in the cooperation server 10 according to the first embodiment.

The control unit 31 provided in the EC site management server 30 executes various processes for managing the EC site. In particular, among the various types of processing that the cooperation server 10 executes in its own server in the first embodiment, processing for receiving requests from the user terminals 41 to 4N and various types of data (for example, EC pages and products) Data), processing for updating various data (for example, product data), processing for transmitting to the user terminals 41 to 4N, and transmitting various data (various information) to the cooperation server 10. Processing such as processing is executed.

The product data DB 32 is a storage medium that stores product data for configuring an EC site. Here, the product data includes at least information related to inventory. Although not particularly illustrated, in this example, the product data includes an item ID, a core business system ID, an inventory quantity, and a status. Further, the product data according to the second embodiment is generated by the EC site management server 30 based on the cooperation data transmitted from the cooperation server 610.

The transaction data DB 33 is a storage medium that stores transaction data constituting the EC site.

Next, an example of EC site update processing executed by the cooperation server 610 in the system 600 of this example will be described.

FIG. 17 is a flowchart showing an example of the first update process executed by the cooperation server 610 in the system 600 of this example. In the first update process, various data are transmitted from each core business system. In the first update process described below, a case where data is transmitted from the integrated core business system 100 will be described as an example. In this example, it is assumed that the process loops while the cooperation server 610 is operating.

In the first update process, first, the cooperation server 610 receives business data update information indicating that the integrated core business system 100 has updated the process flow DB 101 from the integrated core business system 100 (step S501).

When the business data update information is received, the cooperation server 610 updates the cooperation DB 15 based on the received business data update information (step S502).

When the cooperation DB 15 is updated, the cooperation server 610 updates the EC site with information for updating a DB (for example, a product data DB or a transaction data DB) managed by the EC site management server 30 in accordance with the update content. It transmits to the management server 30 (step S503). Here, “information for updating the DB managed by the EC site management server 30” is information for determining which DB is to be changed and how. Specifically, the instruction information indicates an update location based on information (for example, information such as “status” and “order received”) stored in a table added to the cooperation data.

When the information for updating the DB is transmitted to the EC site management server 30, the cooperation server 610 proceeds to step S501 and waits until business data update information is received. The EC site management server 30 executes an update process for the product data DB 32 based on information for updating the DB.

Next, an example of the second update process executed by the cooperation server 610 in the system 600 of this example will be described. FIG. 18 is a flowchart illustrating an example of the second update process executed by the cooperation server 610 in the system 600 of this example. In the second update process, a case where a purchase request for a product is transmitted from the EC site management server 30 will be described as an example.

In the second update process, first, the cooperation server 610 receives purchase request information from the EC site management server 30 (step S601). In this example, when receiving a purchase request for a product from the user terminal 41, the EC site management server 30 updates the product data DB 32 based on the purchase request information and transmits the purchase request information to the cooperation server 610. To do.

When the purchase request information is received, the linkage server 610 stores the purchase request information in the transaction data DB 33 and updates the linkage DB according to the content of the purchase request information (step S602).

When the cooperation DB is updated, the cooperation server 610 identifies the core business system corresponding to the purchase request information (step S603).

When the core business system corresponding to the purchase request is identified, the cooperation server 610 transmits purchase request information to the identified core business system (step S604).

When the purchase request information is transmitted, the linkage server 610 moves to step S601 and waits until the purchase request information is received.

As described above, the EC system of this example includes an EC site management server that manages an EC site that sells products on the Internet with reference to a product data storage unit (product data DB 32) that stores product data. The system can be a system composed of a core business system for listing products on the EC site, and a linkage server that links the EC site management server and the core business system.

Note that the

cooperation servers

10 and 610 execute the above-described processes according to the processing program stored in the storage times included in the

cooperation server

10 or 610.

In addition, the transaction data stored in the transaction data DB (14, 33) described above may be configured integrally with the product data stored in the product data DB (15, 32), respectively.

According to the present invention, it is useful for constructing an EC system using a core business system.

10,610 Cooperation server 20 Relay machine 30 EC site management server 41-4N User terminal 51-56

Communication network

100, 200, 300 Integrated mission-critical system 110 Mission-critical server 120 DWH server 500, 600 EC system

Claims

A linkage server that links an EC site that sells products on the Internet with reference to product data storage means for storing product data and a core business system that sells products on the EC site,
Coordination data storage means for storing cooperation data configured based on the business data transmitted from the core business system including business data storage means for storing business data generated in business,
Update content information receiving means for receiving, from the core business system, business data update content information indicating the update content of the business data when the business data is updated by the core business system;
First linkage data updating means for updating the linkage data based on the received business data update content information;
Product data update processing means for executing processing for updating the product data so that the update contents of the business data are reflected when the data for cooperation is updated. .
Second cooperation data update means for updating the cooperation data according to the content of the purchase request when a purchase request for the product is received from a user of the EC site;
The cooperation server according to claim 1, further comprising purchase request information transmitting means for transmitting purchase request information indicating that the purchase request has been received to the core business system.
The core business system includes a business data DB as the business data storage means,
The business data stored in the business data DB is:
Data composed of at least one table,
Data composed of tables of the same structure,
The linkage server according to claim 1 or 2, wherein process data indicating data related to each business process constituting the process flow is data collected in the same entry in the table.
The core business system includes at least two business data DBs,
further,
Replica data receiving means for receiving replica data of each of at least two business data DBs;
The linkage server according to claim 3, further comprising first linkage DB update means for updating the linkage DB as the linkage data storage means based on data obtained by integrating the received replica data.
The linkage server according to claim 4, wherein the first linkage DB update unit updates the linkage DB so that data obtained by integrating the plurality of received replica data as is is used as linkage data.
Second linkage data update means for updating a linkage DB as the linkage data storage means so that data including at least process data corresponding to display items displayed on the EC site is used as linkage data; The cooperation server according to claim 3.
The product data update processing means updates the product data by transmitting the business data update content information to an EC site management server that manages the EC site,
The EC site management server
The product data storage means;
The linkage server according to any one of claims 1 to 6, further comprising an EC page generation unit that references the product data storage unit and generates an EC page constituting the EC site.
The server that manages the EC site is the linkage server,
The server provided with the said merchandise data storage means is the said cooperation server. The cooperation server in any one of Claims 1-6.
A linked program for controlling a linked server that links an EC site that sells products on the Internet with reference to product data storage means for storing product data and a core business system that sells products on the EC site. There,
In the cooperation server provided with the cooperation data storage means for storing the cooperation data configured based on the work data transmitted from the core business system provided with the work data storage means for storing the work data generated in the work,
Update content information reception processing for receiving business data update content information indicating the update content of the business data when the business data is updated by the core business system;
A first linkage DB update process for updating the linkage data based on the received business data update content information;
A linkage program for executing a product data update process for executing a process for updating the product data so that the update contents of the business data are reflected when the linkage data is updated.
An EC site for selling products on the Internet with reference to product data storage means for storing product data, a core business system for selling products on the EC site, and the EC site and the core business system are linked An EC system including a linkage server,
The core business system is:
Business data storage means for storing business data generated in business,
The linkage server
Cooperation data storage means for storing cooperation data configured based on the business data transmitted from the core business system including the business data storage means;
Update content information receiving means for receiving, from the core business system, business data update content information indicating the update content of the business data when the business data is updated by the core business system;
First linkage data updating means for updating the linkage data based on the received business data update content information;
EC data system comprising: merchandise data update processing means for executing processing for updating the merchandise data so that the update contents of the business data are reflected when the linkage data is updated .