JP2001306898A - System for managing merchandise sales - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a merchandise sales management system for unifying the functions of computer processing systems that selling side companies and purchasing side companies respectively have. SOLUTION: This merchandise sales management system is provided with a database server provided with a merchandise master in which the respective merchandise codes of a plurality of selling side companies for specifying a plurality of respective pieces of merchandise are made to correspond to the merchandise codes of the purchasing side companies and stored, a 1st server for receiving data related to an order including the merchandise code of a purchasing side company about prescribed merchandise from the purchasing side company, and a 2nd server for converting the merchandise code of the purchasing side company into the merchandise code of a selling side company about the prescribed merchandise on the basis of the merchandise master and transmitting the data related to the order as data related to order reception including the merchandise code to the selling side company.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a merchandise sales management system utilizing electronic commerce.

[0002]

2. Description of the Related Art In conventional e-commerce between companies mainly in the retail business, purchase request information, quote information, order information, payment information, etc. are collectively transmitted from a purchasing company to a selling company. On the other hand, a communication mode is adopted in which the delivery schedule information, the delivery information, the billing information, and the like are transmitted from the sales company to the purchase company in a batch. This is called data exchange by the batch transfer method. For example, JCA (Japan Chai
n store Association (chain store unification procedure). With such a communication form, both a purchasing company and a selling company need a computer processing system (a merchandise sales management system) capable of individually generating information necessary for communication and communicating with a specific communication procedure. become.

[0003]

However, some sales companies do not have such a computer processing system. The reason is that, at present, requirements (eg, product code, delivery data or invoice format, etc.) differ for each purchasing company, and the description contents of messages used in e-commerce are also different. This is because the request must be maintained and managed, and the financial and technical capabilities for that are lacking.

[0004] On the other hand, the purchasing company must prepare another transaction system if a specific processing system cannot be introduced even in a part of the sales companies of a plurality of business partners. Management effort and investment are required due to the triplication.

[0005] Under the circumstances described above, as a result, there is a computer processing system having a current (number of purchasing companies) x (number of selling companies) scale. In this situation,
For example, if a certain purchasing company changes the system settings, it is necessary to change the processing system of the selling company that has business with the purchasing company, and the maintenance and management of the system is extremely complicated.

[0006] As a technology capable of reducing the number of (number of purchasing companies) x (number of selling companies) computer processing systems, there is an application providing technology used by an application service provider (ASP). This technology is a technology in which the same business program group (application) is installed on one server, and many companies access using a communication line such as the Internet and jointly use the application (and its functions). is there. However, the ASP is a one-way business program for a sales company or a purchase company, and reduces the number of (number of purchase companies) × (number of sales companies) computer processing systems. Not something.

An object of the present invention is to provide a merchandise sales management system that unifies the functions of a computer processing system possessed by each of a selling company and a purchasing company.

[0008]

The merchandise sales management system according to the present invention includes a merchandise code of each of a plurality of selling companies and a merchandise code of a purchasing company for specifying each of a plurality of merchandise. A database server having a merchandise master stored in association therewith, a first server for receiving order-related data including a merchandise code of the purchasing side for a predetermined product from the purchasing side, Based on the, the product code of the purchasing company is converted to the product code of the selling company for the predetermined product,
A second server for transmitting the order-related data to the selling company as order-related data including the product code, whereby the object is achieved.

The purchasing company has a plurality of stores, and the database server further includes a store master storing a store code for specifying each of the plurality of stores, wherein the order-related data and the order-related data are stored. Data is,
The store code may be included.

[0010] The second server receives an order-related data transmission request including the store code and requesting transmission of the order-related data, and the first server is included in the order-related data transmission request. The shop may be specified based on the shop code, and an order-related data transmission request may be transmitted to the purchasing company requesting transmission of the order-related data.

The database server further includes a queue management master for storing a data type code indicating a type of data to be transmitted or received, wherein the order-related data transmission request includes the data type code, and the data type code is: It may be a code for identifying quote request information, order information, and payment information.

The second server receives an order-related data transmission request including the store code and requesting transmission of the order-related data, and the first server is included in the order-related data transmission request. The purchasing company may be specified based on the store code, and order-related data of the selling company may be transmitted to the purchasing company.

The database server further includes a queue management master for storing a data type code indicating a type of data to be transmitted or received, the order-related data includes the data type code, and the data type code includes quote information. , A code for identifying delivery schedule information, delivery information, and billing information.

[0014] The second server may receive an order-related data transmission request transmitted from the selling company itself.

[0015] The information processing apparatus may further include a timer for transmitting the order-related data transmission request to the second server at a predetermined time.

[0016] The first server may further include a monitoring unit that monitors the queue management master, and transmits the order-related data transmission request or the order-related data based on the monitoring of the monitoring unit.

The database server further includes an account management master in which accounts for specifying the plurality of sales companies are stored, and at least one of the order-related data, the order-related data transmission request, or the order-related data transmission request. One may include the account, and the second server may communicate with the merchant identified by the account.

There may be a plurality of purchasing companies, each of which may have a plurality of stores.

[0019] The product master may include a product code of each of the plurality of selling companies and a product code of the purchasing company with respect to a product not provided with a JAN code.

[0020]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A merchandise sales management system according to an embodiment of the present invention will be described below with reference to the accompanying drawings.

FIG. 1 shows a network configuration 10 including a product sales management system 100. Network configuration 10
, The merchandise sales management system 100 is connected to a plurality of sales companies 120-1,... 120-m that sell merchandise via a network line 110-1,
Further, it is connected to a plurality of purchasing companies 130-1 to 130-n that purchase products via a network line 110-2. The detailed configuration and operation of the product sales management system 100 will be described later. Network line 110
Reference numerals -1 and 110-2 denote communication lines such as the Internet and a local LAN for transmitting information. Each of them may be constituted by a cable, and all or a part thereof may be a wireless line. Although the network lines 110-1 and 110-2 are shown as different lines, they may be substantially the same Internet line or the like.

The selling company 120-k (1 ≦ k ≦ m)
A wholesale company that wholesales products to be handled for each of the plurality of purchasing companies 130-1 to 130-n.
A computer (not shown) connected to a network line 110-1 that can use a browser of Wide Web (WWW) is installed. The computer has a suitable input device such as a keyboard and a mouse, and a printer. Each of the plurality of purchasing companies 130-1 to 130-n is a retail company that wholesales products from a wholesale company.

Next, an outline of processing using the network configuration 10 including such a product sales management system 100 will be described. A plurality of selling companies 120-1,... 120-
m request the merchandise sales management system 100 to perform order-related processing such as quotation of merchandise, notification of delivery schedule, delivery, and issuance of bills to a plurality of purchasing companies 130-1 to 130-n. . A plurality of purchasing companies 130-1 ... 130
Each of -n requests the merchandise sales management system 100 to perform an order-related process such as an estimate request, an order, and a payment for a plurality of sales-side companies 120-1,... 120-m.

The features of the merchandise sales management system 100 will be described in relation to the above processing.
00, the selling company 120-k for the same product
(1 ≦ k ≦ m) and the purchasing company 130-j (1 ≦ j ≦
n) There is provided a product master describing each product code in association with each other. Thus, the selling company 120-k (1 ≦ k
≦ m) and the purchasing company 130-j (1 ≦ j ≦ n)
Even if you use the product code you want to use as it is, the same product is converted to the product code used by the other party and transmitted to the other party, so the conventional transaction format using original product code etc. Can be traded. Therefore, the selling company 120-k (1 ≦ k ≦ m) does not need to provide a separate system for dealing with each of the selling companies 120-k (1 ≦ k ≦ m), and simply manages product sales. By simply providing a terminal that can access the system 100, commodity transactions with the purchasing company 130-j can be performed.
Further, in the product sales management system 100, there is no need to maintain data for each purchasing company. Even if a purchasing company requests a change in the product code of a certain product, it is sufficient to change the product code of the product in the product master, and there is no need to change the data for the partner sales company. . In addition, a plurality of selling companies 120-
When k (1 ≦ k ≦ m) is trading with a common purchasing company 130-j, the store master database relating to the store information of the purchasing company also has a plurality of sales companies 120-k.
(1 ≦ k ≦ m). Therefore, when a plurality of selling companies 120-k (1 ≦ k ≦ m) make a transaction with a common purchasing company 130-j, each of the selling companies 120 stores the store information of the purchasing company 130-j. Need not be held.

Next, the merchandise sales management system 100 as described above will be specifically described with reference to FIG. FIG.
Indicates a group of servers constituting the product sales management system 100. The product sales management system 100 includes a web server 210, a database (DB) server 220,
And a batch transfer communication server 230.

The web server 210 is a server that provides documents, electronic information, etc. on the WWW, and sells the company 120-k (1) via the network line 110-1.
≦ k ≦ m). The web server 210 transmits and receives data to and from the DB server 220 or the batch transfer communication server 230.

The DB server 220 is a server that stores a plurality of databases, retrieves data from the databases upon receiving predetermined instructions, or stores data in the databases. These data are transmitted and received between the web server 210 and the batch transfer communication server 230. The specific contents, the type of the database, and the contents will be described later with reference to FIGS.

Finally, the batch transfer communication server 230 is a server that transmits and receives data using a batch transfer communication procedure. The batch transfer communication server 230 is, for example, a JCA (Japan Chainstore As
chain store unification procedures and FTP (File Transfer Protocol)
The server transmits and receives data to and from the purchasing company 130-j (1 ≦ j ≦ n) via the network line 110-2 by using, for example, an Internet service (e.g., col.). Bulk transfer communication server 2
30 is a web server 210 and a DB server 22
Data transmission / reception is carried out even with 0.

Hereinafter, the merchandise sales management system 1 will be described in more detail.
00 will be described. Web server 210 is called Ap
functions as an HTTP server such as ache, HTML
And a script description language process of interpreting a script description language such as PHP3 to be executed on the server side and transmitting data to be extracted or data to be stored to the DB server 220. Unit 214, connected to any of these,
And a memory 216 for storing data. Note that the memory 216 here is not only a semiconductor memory such as a dynamic RAM, but also a magnetic recording medium such as a hard disk,
D means a general recording medium such as an optical recording medium. On the other hand, the batch transfer communication server 230
32 and the memory 23 connected to the batch transfer processing unit 232
4 is included. The batch transfer processing unit 232 includes the DB server 2
The contents of the database 20 are monitored, the data is taken out from the database based on the monitoring, the data format of the data is adjusted by a predetermined transmission procedure,
Output to 0-2. Further, the batch transfer processing unit 232 acquires the data stored in the memory 216 of the web server 210 by FTP or the like, arranges the data format, and outputs the data to the network line 110-2. Batch transfer processing unit 23
2 receives data from the purchasing company 130-j (1 ≦ j ≦ n) (FIG. 1), and stores the contents in the DB server 220.
Alternatively, the data is transmitted to the memory 234.

Based on such a configuration, the server unit 2
The operation in the case where 12 receives data from the selling company 120-k (1 ≦ k ≦ m) will be described. First server part 2
12 interprets the content represented by the received data. The received data is, for example, an order-related data transmission request.
The order-related data transmission request is a request for transmitting the order-related data, and the order-related data is quote information, order information, delivery schedule information, delivery information, and billing information. The order-related data includes a data type code indicating the type of the information, so that it can be determined which information the order-related data indicates. As a result of receiving the data, if the data needs to be transmitted to the script description language processing unit 214, the interpreted data is transmitted to the script description language processing unit 214.
Send to The case where data transmission is necessary is a case where it is necessary to refer to a database in the DB server 220 and store data in the database. The reference to the database corresponds to the reference to the database of the delivery data storing the data on the delivered product in the example of the delivery information described above.

The script description language processing unit 214
The contents requested to the server 220 are processed based on a predetermined format, and transmitted to the DB server 220. The DB server 220 searches a database based on the data received from the script description language processing unit 214 or stores the database in the database. The database search result is transmitted to the script description language processing unit 214 and further transmitted to the server unit 212. The server unit 212 provides the selling company 120-k (1 ≦ k ≦ m) (FIG. 1) in a format that can be browsed by the selling company 120-k (1 ≦ k ≦ m) (FIG. 1). . Note that the server unit 212 transmits the interpreted data from the selling company 120-k (1 ≦ k ≦ m) (FIG. 1) when it is data to be transmitted to the batch transfer communication server 230 or temporarily as a temporary file. If the data is to be stored in the memory 216, the data is transmitted to the memory 216.

More specifically, the selling company 12
0-k (1 ≦ k ≦ m) (FIG. 1) is the purchasing company 130-j
When an order-related data transmission request is transmitted by specifying (FIG. 1), the request reaches the DB server 220 via the server unit 212 and the script description language processing unit 214. Then, from the purchasing company 130-j (FIG. 1) to the selling company 1
If data related to ordering to 20-k (1 ≦ k ≦ m) (FIG. 1) exists in the database, the data is read out and sent to the script description language processing unit 214.
In the server unit 212, the selling company 120-k (1 ≦
k ≦ m) (FIG. 1).
If the data does not exist in the database as the order-related data or if the data type code is a code of a different type, an order-related data transmission request to be described later is transmitted to the purchasing company 130-j (FIG. 1). The resulting order-related data is stored in the database.

Here, the selling company 120-k (1 ≦ k ≦
m) (FIG. 1) uses a store code to specify the purchasing company 130-j (FIG. 1). The store code is a code uniquely assigned to each of a plurality of purchasing companies 130-j (1 ≦ j ≦ n) (FIG. 1), and one purchasing company has a plurality of stores. In the case, each of the stores is indicated. FIG. 3 shows a store master 300 including a store code 302. The store master 300 further includes a store name and store-related items (postal code, address, telephone number, etc.) 306 corresponding to the store code 302. The store master 300 has a sales company 120-k (1 ≦ k ≦
m) (FIG. 1). Thus, there is a transaction with a plurality of selling companies 120-k (1 ≦ k ≦ m) (FIG. 1) with a particular purchasing company 130-j (FIG. 1),
The same store code can be used for transmitting the order-related data transmission request. This is in comparison with the case where a plurality of selling companies 120-k (1 ≦ k ≦ m) (FIG. 1) individually provide store codes for their purchasing companies 130-j (FIG. 1). The amount of data to be held as a whole can be significantly reduced. Further, a sales company decides that the delivery of goods to the ordered store A is performed by the store B in accordance with an instruction from the purchase company.
Even if it is changed to, the product sales management system 10
0 can easily determine whether the selling company is appropriate as a business partner based on the changed store code of store B.

Referring again to FIG. 2, batch transfer processing section 23
2 will be described. The batch transfer processing unit 232
The contents of a predetermined database of the B server 220 are monitored, and based on the contents and order, the DB server 220 is monitored.
, And transmits the data to the purchasing company 130-j (1 ≦ j ≦ n) (FIG. 1) based on the batch transfer procedure. The data to be transmitted are, for example, an order-related data and an order-related data transmission request. The order-related data is as described above.

The order-related data transmission request is a request for transmitting order-related data, and is a request corresponding to the order-related data transmission request. That is, the selling company 120-k
The request for receiving the order-related data from (1 ≦ k ≦ m) (FIG. 1) is the purchaser company 130-j (1 ≦ j ≦ n) (FIG. 1).
Is a request for transmission of order-related data. Order related data includes quote request information, order information, and payment information. The order-related data includes a data type code indicating the type of the information, so that it can be determined which information the order-related data indicates. Upon receiving the order-related data from the purchasing company 130-j (1 ≦ j ≦ n) (FIG. 1), the batch transfer processing unit 232 converts the data into D
The data is transmitted to the B server 220, and the DB server 220 stores the order-related data in the database.

The order-related data and the order-related data in the above description include a product code for specifying which product is the data. The product code is a code assigned independently by the purchasing side or the selling side, or commonly assigned in the distribution industry to specify each of a plurality of products. The product code in the order-related data is a product code used by the purchasing company 130-j (1 ≦ j ≦ n) (FIG. 1). On the other hand, the product code of the order-related data is a product code used by the selling company 120-k (1 ≦ k ≦ m) (FIG. 1) of the business partner for the product represented by the product code in the order-related data.

FIG. 4 shows a product master 400 including a product code 402. The merchandise master 400 stores, for each of a plurality of merchandise, a selling company 120-k (1 ≦ k ≦ m).
The product code 402 used by (FIG. 1) and the supplier company 130-j of the trading partner for the product (1 ≦ j ≦ n)
(FIG. 1) is a database defining product codes to be used, and is provided for each selling company 120-k (1 ≦ k ≦ m) (FIG. 1). The product master 400 includes a product code 402 used by the selling company, a product name 404 of the product, and a general JAN code 406 in the distribution industry.
And product code-related information 408-1 to 408-1 for each purchasing company
408-n. The individual product data 408-1 to 408-n for each purchasing company includes a product code used by a store of the purchasing company for the product and a unit delivery price of the product to the company. In addition, this product code related information 4
08-1 to 408-n are purchasing companies 130-j (1 ≦
j ≦ n) (FIG. 1), and may be provided as individual files because the number increases as the number increases. In that case, the file contains the purchasing company 130-j (1 ≦ j ≦
n) A purchasing code (or purchasing company name) for identifying (FIG. 1), a product code, a delivery unit price, and the like are stored.

The JAN code is a combination of the name of a product maker and a product code uniquely set by the maker, and depends on the maker including the selling company 120-k (1 ≦ k ≦ m) (FIG. 1). It is a code that has a large character. Further, some of the current purchasing companies 130-j (1 ≦ j ≦ n) (FIG. 1) may have different JAN codes for the same product or may have the same JAN code. Some products have a JAN code indicating different products. As represented by the JAN code, at present, product codes are not unified among companies. Conventionally, companies that trade with each other specify a product code of each other's business partner and conduct business. Therefore, each company needs to hold product codes of a plurality of business partners. However, according to the product master 400 of the present invention, even if the purchasing company and the selling company use the product code they want to use as they are, they can send the same product to the product code used by the other company. Since it is converted and transmitted, it can be traded in a transaction format using a conventional unique product code or the like. Note that some products have JAN code 406.
Some products are not marked with. In this case as well, a product code uniquely assigned to the product by the purchasing company and the selling company is stored.

Next, the operation of the merchandise sales management system 100 as described above will be described with reference to FIG. However, in the following, a case will be described as an example where the selling company 120-k requests the purchasing company 130-j to receive order information (order data) representing an order for a product. The data flow will be mainly described. However, if it is order-related data, other quotation information, delivery schedule information, delivery information, and billing information can be described by the same data flow. The selling company 120-k has an account, user I
D and the password are used to log in to the merchandise sales management system 100 in advance, and the merchandise sales management system 10
0 specifies that the logged-in company is the sales company 120-k. At the time of login, the entered account, user ID and password are compared with the account, user ID and password registered in the account management master 254 (FIG. 2), and whether or not the login is a login by a valid user Is determined. By using this account, even if there are a plurality of selling companies, each of them can be specified. As described with reference to FIG. 2, since the WWW web server 210 is used to transmit and receive data to and from the selling company 120-k, login is performed using an appropriate web browser. .

In the following, "send" from the selling company 120-k to the merchandise sales management system 100 means that a predetermined item on a screen displayed using a web browser is checked and clicked, or a predetermined item is clicked. This means that data is transmitted to the product sales management system 100 by inputting the data. “Receiving” by the selling company 120-k means that the selling company 120-k receives the data transmitted from the product sales management system 100 and displays the data using a web browser. .

FIG. 5 shows a flow of data between databases related to receiving order data. FIG. 6 is a main flowchart of the processing of the merchandise sales management system 100 related to receiving the order data. In FIG. 5, the product sales management system 100 is divided into a web server 210, a DB server 220, and a batch transfer communication server 230. The database contained in each of these compartments, represented by the "direct access storage" as the basic data symbol, is the web server 2 shown at the top of the compartment.
10, DB server 220, batch transfer communication server 23
0 is a database held in any one of 0. The processing represented by “processing” as a basic processing symbol is processing performed by any of them. The store master and the product master are not shown. Hereinafter, the data and processing flow relating to the reception of the order data will be described with reference to FIG.

First, the selling company 120-k transmits a store code specifying each of the purchasing companies and an order data receiving request to the product sales management system 100 in order to request reception of order data. In this example, the purchasing company 130-j
Is transmitted.

When web server 210 receives the store code and the order data reception request (step 60 in FIG. 6).
2) Instruct the system DB control 250 to transmit the job number. The system DB control 250 holds a job number as a queue number, and upon receiving this instruction, transmits one of the job numbers corresponding to the instruction to the web server 210.

The web server 210 receives the job number from the system DB control 250 and uses it as a queue registration log including the queue number in the user DB log 26.
0 and transmitted to the user DB control 262 (step 604 in FIG. 6). User DB log 260
Stores the queue number.

The user DB log 260 stores the status indicating the status of the request with the queue number in association with the queue number. The “state” is the current state of whether or not there is a response to the request from the purchasing company 130-j. This example shows the current state of whether or not the purchaser company 130-j has transmitted order data in response to an order data reception request. Hereinafter, a description will be given assuming that the order data has not been transmitted yet.

The user DB control 262 receives the queue number, generates and stores an ID and a slip number. The user DB control 262, when receiving a response of order-related data from the purchasing company 130-j to a request with a certain ID, adds the content of the response (for example, quote, order, etc.) to the request. Used to generate the corresponding voucher number. The ID is generated based on the queue number.

Following these processes, the web server 210 further transmits this job number as a queue number to the queue management master database 252 by adding it to the data type code corresponding to the received order data reception request.
The data type code is a code indicating the type of data to be transmitted or received.In addition to the code corresponding to the order data reception request, there are codes corresponding to the estimate request data reception request and the request data reception request, respectively. I do. Simultaneously with this transmission, the web server 210 transmits the account and store code of the selling company 120-k to the queue management master 252. It can be said that these series of data type code, queue number, account and store code are received as queue management data (FIG. 6).
Step 606). As described above, the merchandise sales management system 100 knows the logged-in sales company 120-k and also knows that it is an order data transmission request from the sales company 120-k. Web server 210 reads the account from account management master 254 (FIG. 2) and queue management master 2
52. The account stored in the queue management master 252 may not be an account uniquely assigned in the merchandise sales management system 100, but is determined between a specific purchasing company and the selling company 120-k. May be the code of the selling company 120-k. This is because a plurality of purchasing companies have the same sales company 12
This is because, even when trading with 0-k, each purchasing company may assign a different code to the selling company 120-k. As will be described later, when requesting the transmission of order data, an account is first transmitted, and the purchasing company 130-j approves whether or not the request is from a trading partner. It is useful to use the code of the selling company 120-k viewed from j as an account.

The queue management master 252 receives the data type code, the queue number, the account and the store code, and stores them as queue data together with the date and time. The description using this example is based on one sales company 12.
Although only 0-k is targeted, a plurality of selling companies are actually targeted. Therefore, the queue management master 25
No. 2 also stores queue data for requests from selling companies other than the selling company 120-k. However, even if multiple queue data are registered, depending on the queue number, account, store code, and data type code, You can determine whether you are making the request.

On the other hand, the batch transfer communication server 230 has a monitoring mechanism for constantly monitoring the queue data stored in the queue management master 252 at set intervals (step 608 in FIG. 6). Upon recognizing that queue data exists in the queue management master 252 by monitoring, the batch transfer communication server 230 performs a receiving process according to a batch transfer procedure (step 610 in FIG. 6). However, this is performed based on the queue number, and processing is performed from the queue data with the smaller queue number. This "reception processing by batch transfer procedure" will be described. First, an account, a store code, and a data type code are read from the queue management master 252. Bulk transfer communication server 230
Is the purchasing company 130 specified based on the store code
-J, the order data reception request is transmitted as an order data transmission request together with the account. The transmission may be in the form of a data type code indicating an order data transmission request, or in another form. As a result of transmitting the order data transmission request, data from the purchasing company 130-j is received, and thereafter, predetermined processing is performed according to the content of the data. These processes are reception processes by the batch transfer procedure. This will be described in more detail.

When the batch transfer communication server 230 transmits an order data reception request together with an account as an order data transmission request, the purchasing company 130-j transmits a sales request for transmission based on the account and the order data transmission request. It is confirmed whether the side company 120-k is a legitimate business partner. If it is not a legitimate business partner, it responds with a disapproval stating that it cannot be approved as the sending party of the order data.
If approved as a legitimate trading partner, the purchasing company 13
0-j transmits order data to the selling company 120-k, which is the business partner, to the batch transfer communication server 230.
The order data includes an order number, a store code 302 (FIG. 3) of the supplier company 130-j that is the delivery destination, a product code 402 (FIG. 4), a product name 404 (FIG. 4), and a JAN code 406 (FIG. 4). , Unit price, quantity, etc. are attached. It should be noted that the batch transfer communication server 230 determines which purchasing company 13
Since it knows what kind of request was sent to 0-j, the sales company 120-k for specifying the sales company 120-k to which the order data is directed is specified. Information need not be provided.

The batch transfer communication server 230 receives the order data or the disapproval response transmitted from the purchasing company 130-j. If the data is disapproved data (“No” in step 612 of FIG. 6), the user DB log 260
, A status indicating that the order data could not be received is written to the queue management master 252, and the queue data having the queue number is deleted from the queue management master 252 (step 61 in FIG. 6).
4). When the order data is received (“Yes” in step 612 of FIG. 6), the contents are simply converted into text format and temporarily stored in the batch transfer communication server 230 as text file reception data 256. The text file reception data 256 is generated (step 6 in FIG. 6).
16) When stored, the batch transfer communication server 230 writes a status to the user DB log 260 indicating that reception of order data, which is a processing result, has been completed. Further, the batch transfer communication server 230 deletes the queue data registered with the queue management master 252 and having the queue number from the queue management master 252 (step 618 in FIG. 6). When these processes are completed, the batch transfer communication server 230 sets the text file reception data 2
56 is transferred to the text file reception data 258 of the DB server 220 (step 620 in FIG. 6). At this stage, the order data is stored in the text file reception data 258 of the DB server 220.

Next, a data flow for the sales company 120-k to acquire order data will be described. When the sales company 120-k desires to take in the order data, it transmits an instruction to take in the order data. Upon receiving the instruction (step 622 in FIG. 6), the web server 21
0 confirms the contents of the user DB log 260, and if the status indicates that the order data has been received, fetches the received data from the text file received data 258. As described above, the order data includes the product code (for example, 408-
1), the product name 404 (FIG. 4), and the JAN code 406 (FIG. 4), so that the text file reception data 258 also includes such information. The web server 210, based on the product master 400 (FIG. 4),
The product code 408-1 of the purchasing company is converted into the product code 402 (FIG. 4) of the selling company. Then, the web server 210 transmits the converted text file reception data to the sales company 120-k as order data (step 624 in FIG. 6). The selling company 120-k receives the text file reception data.

Further, web server 210 presents the ID number generated based on the queue number and acquires the slip number from user DB control 262. The merchandise sales management system 100 performs order management, delivery management, and the like using the slip number. Then web server 2
10 generates delivery data, order confirmation data, and order data based on the text file reception data 258.

The delivery data includes the order number indicated in the order data, the store code 302 (FIG. 3), the product code 402 (FIG. 4), and the product name 4 of the supplier company 130-j that is the delivery destination.
04 (FIG. 4), JAN code 406 (FIG. 4), unit price, quantity and the like.
4 is stored. As described later, the contents of the user DB delivery data 264 can be edited by the selling company 120-k, and the edited delivery data becomes final delivery data of the user DB delivery data 264. Generally,
Since the ordered product is delivered according to the order data, the contents of the order data ordered by the purchasing company 130-j and the delivery data are substantially the same with respect to the contents described above. For the same reason, the order confirmation data and the user DB order data 268 also include the order number and the store code 302 of the supplier company 130-j that is the delivery destination.
(FIG. 3), product code 402 (FIG. 4), product name 404
There are data including (FIG. 4), JAN code 406 (FIG. 4), unit price, quantity, and the like. The generated order confirmation data is the user DB order confirmation data 266, and the order data is
The contents are the same as the order data in the text file format received by the selling company 120-k, but need not be in the text format.

Here, in order to match the product ordered by the purchasing company 130-j with the product recognized by the selling company 120-k, the web server 210 transmits the product code and the product name 404 of the ordering data. (FIG. 4), JAN code 40
6 (FIG. 4) and the like with the product master 400 (FIG. 4),
Delivery data is generated while confirming that an incorrect order is not transmitted to the selling company 120-k. This operation is a process of converting the product code of the purchasing company into the product code of the selling company. This is also performed when the user DB order confirmation data 266 and the user DB order data 268 are generated. In this way, the purchasing company 130
-J and the selling company 120-k are both guaranteed to handle the same merchandise, ensuring transactional security.

As described above, the user DB order data 26
By storing the order data in 8, not only the purchase company 130-j described as an example, but also the order data with other purchase companies, the sales company 120-j can be used.
k can be displayed in a list.

When the selling company 120-k transmits an order list reception request to the web server 210 to receive the order list, the web server 210 generates print data based on the user DB order data 268.
The print data 270 is data for displaying a list of order data. At this time, the web server 21
0 further refers to the merchandise master 400 (FIG. 4) and is configured to be in a format designated by the selling company 120-k in advance. As a result, the purchasing company 130-j becomes the selling company 1
Even if an order is not placed in a format required by 20-k, the product sales management system 100 configures the order data in a format designated by the selling company 120-k, so that there is no need to provide a separate processing system. The print data 270 generated in this manner is temporarily stored on the DB server 220 as a temporary file, and then transmitted to the sales company 120-k. The flow of data related to receiving order data has been described above.

Next, a data flow for acquiring the delivery data transmitted from the selling company 120-k to the purchasing company 130-j will be described. However, in the following, a case will be described as an example where the selling company 120-k requests transmission of delivery information (delivery data) representing the delivery details of a product to the purchasing company 130-j. The data flow will be mainly described. However, if it is order-related data, other quotation information, delivery schedule information, and billing information can be described by the same data flow.

FIG. 7 shows a data flow between databases relating to delivery data transmission. FIG. 8 shows a flowchart of the main processing of the product sales management system 100 related to the delivery data transmission. In FIG. 7, as in FIG.
The product sales management system 100 includes a web server 210,
DB server 220 and batch transfer communication server 230
Is divided into The database as a columnar figure included in each of these sections and the processing described in the rectangle are processed by the web server 210, the DB server 220, and the batch transfer communication server 230 shown at the top of the section, respectively. This is a database held in any of them, or a process performed by any of them. Hereinafter, the data and processing flow related to the delivery data transmission will be described with reference to FIG.

First, the selling company 120-k transmits a delivery data transmission request to the web server 210, requesting transmission of delivery data. Along with the delivery data transmission request, a store code 302 (FIG. 3) for specifying the purchasing company 130-j is also transmitted.

The web server 210 receives the store code and the delivery data transmission request (step 8 in FIG. 8).
02), instruct the system DB control 250 to transmit the job number. The system DB control 250 holds a job number as a queue number, and upon receiving this instruction, transmits one of the job numbers corresponding to the instruction to the web server 210.

The web server 210 receives the job number from the system DB control 250 and uses it as a queue registration log including a queue number.
0 and transmitted to the user DB control 262.
The user DB log 260 stores the queue number. The user DB log 260 stores a status indicating the status of the request with the queue number in association with the queue number. The “state” in this example is a state indicating whether or not the delivery data has been transmitted to the purchasing company 130-j based on the delivery data transmission request. The user DB control 262 receives the queue number, generates and stores an ID and a slip number. The ID is generated based on the queue number.

Following these processes, the web server 210 further adds the job number as a queue number to the data type code corresponding to the delivery data transmission request, and transmits the queue number to the queue management master 252. In addition to the code corresponding to the delivery data transmission request, the data type code includes codes corresponding to each of the estimate data transmission request, the scheduled delivery data transmission request, and the billing data transmission request. At the same time as this transmission, the web server 210
Sells the sales company 120-k to the queue management master 252.
Submit your account and store code. As described above, the merchandise sales management system 100 grasps the logged-in sales company 120-k, and
The web server 210 also reads out the account from the account management master 254 (FIG. 2) because it knows that the request is an order data transmission request from 20-k.
It can be sent to the queue management master 252.

The data type code, queue number, account and store code are output as queue management data (step 804 in FIG. 8), and the queue management master 252
Stores this as queue data together with the date, time, and the like. Note that the description using this example is directed to only one selling company 120-k, but is actually a plurality of selling companies. Therefore, the queue management master 252 also stores queue data for requests from sales companies other than the sales company 120-k.
However, even if multiple queue data are registered,
Based on the queue number, the account, the store code, and the data type code, it is possible to determine at which queue the sales company makes a request to the purchase company and what kind of request.

Subsequently, the web server 210 generates data to be transmitted to the purchasing company 130-j. The data to be transmitted includes the delivery data relating to the delivery stored in the user DB delivery data 264 and the product master 400.
(FIG. 4). As a premise, FIG.
It is necessary that the delivery data has already been stored in the user DB delivery data 264 described with reference to FIG. The delivery data is stored in the user DB delivery data 264 when the product has already been ordered through the product sales management system 100 or the sales company 120-k registers the delivery data,
This is done by making corrections. Sales company 120-k
In order to specify the delivery data between the purchasing companies 130-j, first, the user DB delivery data 264 of the selling company 120-k is specified, and further, the user DB delivery data 130-j is identified. You need to identify delivery data for the transaction. The identification is performed as follows. First, the merchandise sales management system 100 logs in the sales company 1
20-k, and also knows that it is an order data transmission request from the selling company 120-k.
-K user DB delivery data 264 can be specified. Since the delivery data is provided with the store code 302 (FIG. 3) as the delivery code, the delivery data for the purchasing company 130-j is specified based on the store code.

When the user DB delivery data 264 is specified, at this stage, the selling company 120-k can transmit a delivery data registration instruction for the delivery data to the web server 210 and an instruction to correct the delivery data. Upon receiving the delivery input instruction, the web server 210 further receives the change content transmitted from the selling company 120-k and stores it in the user DB delivery data 264, or changes the content.

Subsequently, the web server 210 reads the delivery data from the user DB delivery data 264 and prepares for transmission in the form of a text file. At this time, the delivery data is described by the product code 402 of the selling company. The web server 210 stores the product master 400
Based on (FIG. 4), the product code 402 of the selling company is converted to the product code of the purchasing company to generate transmission data (step 806 in FIG. 8). Then web server 2
Reference numeral 10 temporarily stores the delivery data in the text file format in the text file transmission data 274 of the DB server 220 as a temporary file.

On the other hand, as described with reference to FIG. 5, the batch transfer communication server 230 has a monitoring mechanism for constantly monitoring the queue data stored in the queue management master 252 at set intervals (see FIG. 8). Step 81
0). When recognizing that queue data exists in the queue management master 252 by monitoring, the batch transfer communication server 230 performs transmission processing according to a batch transfer procedure (step 812 in FIG. 8). The “transmission processing by the batch transfer procedure” will be described. First, a store code and a data type code are read from the queue management master 252. The collective transfer communication server 230 specifies the purchaser company 130-j as the transmission destination based on the store code, and determines that the transmission content is a delivery data transmission request. Since the delivery data to be transmitted is stored in the text file transmission data 274 of the DB server 220, the batch transfer communication server 230 obtains the delivery data from the text file transmission data 274 and outputs the text file in the batch transfer communication server 230. The transmission data 276 is stored in the transmission data 276, and transmission processing is performed by a batch transfer procedure. As described above, the batch transfer communication server 230 transmits the delivery data to the purchasing company 130-j. After this, batch transfer communication server 2
30 writes the status indicating that the delivery data has been transmitted to the purchasing company 130-j in the user DB log 260, and deletes the queue data of the delivery data transmission request existing in the queue management master 252. (Step 814 in FIG. 8).

As described above, the batch transfer communication server 2
30 performs “transmission processing by batch transfer procedure” and transmits the delivery data to the purchasing company 130-j.

The purchasing company 130-j can request issuance of a delivery slip in which the contents of the delivery data are arranged in a predetermined format. This processing is the same as the procedure of the order list reception request described with reference to FIG. That is, the selling company 120-
When k sends a delivery slip issuance request requesting issuance of a delivery slip addressed to the purchasing company 130-j, the web server 2
10 generates print data 272 representing a delivery slip based on the user DB delivery data 264. At this time, the web server 210 further stores the product master 400
Referring to (FIG. 4), a configuration is adopted in which the purchasing company 130-j has a format designated in advance. Thus, the selling company 12
Since the merchandise sales management system 100 configures the delivery slip in the format specified by the purchasing company 130-j without having to place an order in the format requested by the purchasing company 130-j, There is no need to provide a processing system. The print data 272 generated in this way is temporarily stored on the DB server 220 as a temporary file, and then transmitted to the sales company 120-k. The data flow related to the delivery data transmission has been described above.

In the description with reference to FIGS. 5 and 6, it is assumed that the selling company 120-k transmits the order data reception request and the delivery data transmission request to the web server 210. However, in the industrial world, reception of order data and transmission of delivery data are performed at regular intervals. Therefore, a timer is provided outside or inside the web server 210, and a setting is made so that an order data reception request or a delivery data transmission request is transmitted to the web server 210 at a certain date and time. At this time, as described above, the order data reception request and the delivery data transmission request need to be transmitted together with the store code specifying the business partner.
If the store code and the date and time at which -k sends the request are set in advance in the merchandise sales management system 100, the sales company 120-k itself will need to send the request each time. Thus, the burden on the selling company 120-k can be greatly reduced.

[0072]

According to the present invention, for each of a plurality of products, a product master that defines a product code used by a selling company and a product code used by a purchasing company of a trading partner for the product is provided. Provided. According to the product master, even if each of the purchasing company and the selling company uses the desired product code as it is, the same product is converted to the product code used by that partner and transmitted to the other party. Therefore, it is possible to trade in a transaction format using a conventional unique product code or the like.

According to the present invention, the store master database of the purchasing company is also shared. When a plurality of selling companies deal with a common purchasing company, each of the selling companies does not need to maintain the store information of the purchasing company, so the burden on system construction and maintenance is greatly reduced. Is done.

Further, even if the configuration of the system and the contents of the database are changed, each of the purchasing company and the selling company does not need to maintain the database. If the corresponding product master or store master is changed, the contents are changed. Is reflected in all transactions. Therefore, each of the purchasing company and the selling company does not need to perform many tests and operation checks.

Further, since information such as a format decided between a specific purchasing company and a selling company can be used as individual information, the input / output format conforming to the requirements of the supplier's purchasing company as before can be used. Maintain transactions with purchasing companies.

[Brief description of the drawings]

FIG. 1 shows a network configuration including a product sales management system.

FIG. 2 shows a group of servers constituting the product sales management system.

FIG. 3 shows a store master including a store code.

FIG. 4 shows a product master including a product code.

FIG. 5 shows a flow of data related to receiving order data.

FIG. 6 shows a flowchart of main processing of the merchandise sales management system 100 related to receiving order data.

FIG. 7 shows a flow of data related to delivery data transmission.

FIG. 8 shows a flowchart of main processing of the product sales management system 100 related to delivery data transmission.

[Explanation of symbols]

 100 Merchandise sales management system 210 Web server 212 Server section 214 Script description language processing section 216 Memory 220 DB server 230 Batch transfer communication server 232 Batch transfer processing section 234 Memory

Claims (12)

[Claims] 1. A database server having a product master for storing each product code of each of a plurality of sales companies and the product code of a purchase company in association with each other for specifying each of the plurality of products. A first server that receives order-related data including a product code of the purchasing company for a predetermined product from the purchasing company; and a product code of the purchasing company based on the product master. A second server that converts the predetermined product into a product code of the sales company and transmits the order-related data to the sales company as order-related data including the product code. system. 2. The purchasing company has a plurality of stores, and the database server further includes a store master storing a store code for specifying each of the plurality of stores, wherein the order-related data and the The merchandise sales management system according to claim 1, wherein the order-related data includes the store code. 3. The second server receives an order-related data transmission request including the store code and requesting transmission of the order-related data, wherein the first server responds to the order-related data transmission request. Identifying the store based on the included store code,
3. The merchandise sales management system according to claim 2, wherein an order-related data transmission request for requesting the purchase-side company to transmit the order-related data is transmitted. 4. The database server further comprises a queue management master storing a data type code representing a type of data to be transmitted or received, wherein the order-related data transmission request includes the data type code, The merchandise sales management system according to claim 3, wherein is a code for identifying quote request information, order information, and payment information. 5. The second server receives an order-related data transmission request including the shop code and requesting transmission of the order-related data, wherein the first server responds to the order-related data transmission request. The merchandise sales management system according to claim 2, wherein the purchasing company is specified based on the included store code, and order-related data of the selling company is transmitted to the purchasing company. 6. The database server further includes a queue management master storing a data type code indicating a type of data to be transmitted or received, the order-related data includes the data type code, and the data type code is 6. A code for identifying quote information, delivery schedule information, delivery information and billing information.
Product sales management system described in. 7. The merchandise sales management system according to claim 3, wherein the second server receives an order-related data transmission request transmitted from the selling company itself. 8. The merchandise sales management system according to claim 3, further comprising a timer for transmitting the order-related data transmission request to the second server at a predetermined time. 9. The first server further includes a monitoring unit that monitors the queue management master, and transmits the order-related data transmission request or order-related data based on the monitoring of the monitoring unit. The merchandise sales management system according to 4 or 6. 10. The database server further includes an account management master in which accounts specifying the plurality of sales-side companies are stored, and the database server receives the order-related data, the order-related data transmission request, or the order-related data transmission request. The merchandise sales management system according to any one of claims 3 to 9, wherein at least one includes the account, and the second server communicates with the selling company specified by the account. 11. The merchandise sales management system according to claim 2, wherein a plurality of said purchasing companies exist, each of which has a plurality of stores. 12. The merchandise master includes a merchandise code of each of the plurality of selling-side companies and a merchandise code of the purchasing-side company for products to which a JAN code is not attached. The merchandise sales management system according to any of the above.