JP2010079699A - Network system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow a user to sequentially acquire sales information in a versatile format in a network system provided with ECR (Electronic Cash Resister). <P>SOLUTION: In the network system 1 including a plurality of ECRs 20A and 20B and a center server 10 which are mutually connected through a communication network N, each of the ECRs 20A and 20B includes an input part 22 which receives input of operation log data on commodity sales; and a communication part 26 which transmits the operation log data, when it is operation log data to be transmitted to the center server 10, to the center server 10 for every transaction of commodity. The center server 10 includes a communication part 16 which receives operation log data transmitted from the ECRs 20A and 20B; a CPU 11 which converts the operation log data to an output file 91 according to a record output specification 71; and a CPU 11 which causes a storage part 15 to store the converted output file 91. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

The present invention relates to a network system.

  2. Description of the Related Art Conventionally, a plurality of POS (Point Of Sales) terminals that are installed in a store that sells products and process sold product data (product name, price, etc.) and a store computer that manages the plurality of POS terminals are provided. A POS system is known (see, for example, Patent Document 1).

There is also known a POS system in which a plurality of ECRs (Electronic Cash Registers) for processing product data are connected by a LAN (Local Area Network) (see, for example, Patent Document 2).
JP 2003-44939 A JP-A-5-325032

  However, when a network system including an ECR is configured as a data processing device, information at the time of sale of the product (for example, information related to product transactions such as product name and price, information related to ECR operator attendance, etc .: Is called “sales information”) in a format that can be used effectively by the user (a format in which the sales information is classified by a predetermined item: hereinafter, a format that can be used effectively by the user is called a general-purpose format). Could not get.

For example, in a POS system equipped with a POS terminal, data input by an operator of the POS terminal at the time of product sales (data including sales information input at the time of sales: data input at the time of sales below). Operation log data) is converted into a general-purpose format. When the merchandise is sold and the merchandise transaction ends, a general-purpose format is transmitted from the POS terminal to the store computer for each transaction. However, in the case of a network system equipped with an ECR, the ECR is configured with hardware resources that are more limited than those of the POS terminal. For this reason, unlike the POS terminal, the ECR does not have a function of converting operation log data input by an ECR operator into a general-purpose format. Therefore, in the case of a system equipped with ECR, operation log data is transmitted from the ECR to the center apparatus.
At this time, the ECR temporarily stores the operation log data in the storage device inside the ECR, instead of transmitting the operation log data to the center device for each transaction of goods. Then, when the daily sales are closed, the operation log data for one day stored in the storage unit is transmitted to the center device. Then, in the center device, the operation log data is converted into a general-purpose format, and the converted general-purpose format is stored in the center server. Then, polling of the general-purpose format stored in the center device is performed from the user terminal (host device of a company that manages a store that sells products), and the user terminal receives the general-purpose format. Thereby, the company (user) that manages the store that sells the product acquires the sales information in the general-purpose format.
For this reason, when a network system including an ECR is configured, the user can acquire sales information in a general-purpose format only when closing sales for one day.

  An object of the present invention is to enable a user to sequentially obtain sales information in a general-purpose format in a network system provided with ECR.

The network system of the invention according to claim 1 is:
In a network system in which a plurality of data processing devices and a server device are connected via a network,
The data processing device includes:
Input means for accepting operation log data input when selling products;
When the operation log data accepted by the input means is operation log data to be transmitted to the server device, the operation log data includes transmission means for transmitting the operation log data to the server device for each product transaction,
The server device
Storage means for storing information;
Receiving means for receiving operation log data transmitted from the data processing device;
First conversion means for converting the operation log data received by the receiving means into a general-purpose format that can be used effectively by a user according to a predetermined data conversion specification;
Control means for storing the general-purpose format converted by the first conversion means in the storage means.

The invention according to claim 2 is the network system according to claim 1,
The storage means
Storing a destination folder path indicating a folder destination and identification information for identifying the data processing device in association with each other;
The operation log data is
Including the identification information;
The control means includes
The storage unit is searched for identification information that matches the identification information included in the operation log data, and the general-purpose format is stored in a folder indicating a destination folder path associated with the searched identification information.

The invention according to claim 3 is the network system according to claim 1 or 2,
A second conversion means for converting the general-purpose format stored in the storage means into a user-desired format according to a user-desired conversion specification;
The control means includes
The user-desired format converted by the second conversion means is stored in the storage means.

The invention according to claim 4 is the network system according to claim 3,
The storage means
Storing the conversion timing for converting the general-purpose format into a format desired by the user;
The control means includes
According to the conversion timing stored in the storage means, the general-purpose format is converted into a format desired by the user.

  According to the present invention, in a network system equipped with ECR, a user can sequentially acquire sales information in a general-purpose format.

  Hereinafter, an example of an embodiment according to the present invention will be described in detail with reference to the accompanying drawings. However, the scope of the invention is not limited to the illustrated examples.

An embodiment according to the present invention will be described with reference to FIGS. First, with reference to FIG. 1, the structure of the network system 1 of this Embodiment is shown.
As shown in FIG. 1, the network system 1 includes a center server 10 as a server device, ECRs (Electronic Cash Registers) 20A and 20B as data processing devices, and user backbone systems 30A and 30B. The

The center server 10 is communicatively connected to the ECRs 20A and 20B via a communication network N such as the Internet. The ECRs 20A and 20B are installed in each store that sells products, and process data (operation log data) input by the operator who operates the ECRs 20A and 20B when the products are sold. The number of ECRs is not limited to the example of FIG.

  The user backbone systems 30A and 30B are communicatively connected to the center server 10 via a communication network N such as the Internet. The user backbone systems 30A and 30B are server devices installed in a user (a company that manages a store that sells products). The user backbone systems 30 </ b> A and 30 </ b> B poll the output file 91 or the user specification file 103 described later, and receive the output file 91 or the user specification file 103 from the center server 10.

  Next, the internal configuration of the center server 10 will be described with reference to FIG. As shown in FIG. 2, the center server 10 includes a first conversion unit, a second conversion unit, a CPU (Central Processing Unit) 11 as a control unit, an input unit 12, a RAM 13 (Random Access Memory), A display unit 14, a storage unit 15 as a storage unit, a communication unit 16 as a reception unit, and a timer unit 17 are provided, and each unit is connected via a bus 18.

  The CPU 11 centrally controls each unit of the center server 10. The CPU 11 expands a program designated from the system program and various application programs stored in the storage unit 15 in the RAM 13 and executes various processes in cooperation with the program expanded in the RAM 13.

The CPU 11 is a general-purpose that allows the user to effectively use the operation log data 51 received via the communication unit 16 according to a predetermined data conversion specification (record output specification 71) in cooperation with the conversion 1 program described later. The data is converted into a format (output file 91), and the converted general-purpose format is stored in the storage unit 15.
Further, the CPU 11 cooperates with the conversion 2 program described later to convert the general-purpose format stored in the storage unit 15 into a user-desired format (user specification file 103) according to the user-specified conversion specification (conversion specification file 101). The converted format desired by the user is stored in the storage unit 15.

  The input unit 12 includes a keyboard having cursor keys, characters, numeric input keys, various function keys, and the like, and outputs an operation signal indicating that each key is pressed by the operator to the CPU 11. The input unit 12 may include a pointing device such as a mouse, and may receive a position input signal and transmit it to the CPU 11.

  The RAM 13 is a volatile memory that temporarily stores information, and has a plurality of work areas that store various programs to be executed and data related to these various programs.

  The display unit 14 is configured by an LCD (Liquid Crystal Display), an ELD (Electro Luminescent Display), or the like, and performs various displays according to a display signal from the CPU 11.

The storage unit 15 includes an HDD (Hard Disk Drive) having a magnetic recording medium,
Various programs and various data are stored so as to be readable and writable from a recording medium.
The storage unit 15 stores a conversion 1 program, a conversion 2 program, a destination master 61, a cash register authentication master 62, a record output specification 71, an output file 91, a conversion specification file 101, a conversion master 102, and a user specification file 103, which will be described later.

  The communication unit 16 includes a modem, a TA (Terminal Adapter), a router, a network card, and the like. The communication unit 16 transmits and receives information to and from the ECRs 20A and 20B on the connected communication network N. The communication unit 16 transmits and receives information to and from the user backbone systems 30A and 30B. The timer unit 17 has a built-in timing circuit, and measures and outputs the current time and the current date.

  Next, the configuration of the ECRs 20A and 20B will be described. FIG. 3 shows the internal configuration of the ECR 20A. Here, the ECR 20A is described as a representative, but the same applies to the ECR 20B.

  As shown in FIG. 3, the ECR 20A includes a CPU 21, an input unit 22 as an input unit, a RAM 23, a display unit 24, a storage unit 25, a communication unit 26 as a transmission unit, a drawer 27, and a print unit. 28 and a time measuring unit 29, each of which is connected via a bus 29a.

  The CPU 21, the RAM 23, the communication unit 26, and the time measuring unit 29 are the same as the configurations of the CPU 11, the RAM 13, the communication unit 16, and the time measuring unit 17 of the center server 10, respectively, and different parts will be mainly described.

  The CPU 21 receives input of operation log data via the input unit 22 at the time of sale of a product in cooperation with a transmission program described later, and the received operation log data is operation log data to be transmitted to the center server 10. In some cases, the operation log data is transmitted to the center server 10 via the communication unit 26.

  The input unit 22 includes a cash register keyboard including cursor keys, characters, numeric input keys, various function keys, and the like, and outputs an operation signal indicating that each key is pressed by the operator to the CPU 21. The display unit 24 includes an LCD, an ELD, and the like, and performs screen display according to a display control signal from the CPU 21. The input unit 22 may be configured as a touch panel integrally with the display unit 24. Further, the input unit 22 may include a barcode reader, a barcode scanner, or the like that reads a barcode provided on the product.

  The storage unit 25 is configured by a ROM (Read Only Memory) or the like. The storage unit 25 stores various programs and various data so that they can be read from the ROM. The storage unit 25 may be configured with an HDD or the like. The storage unit 25 stores a transmission program and operation log data 51 described later. The communication unit 26 transmits / receives information to / from the center server 10 on the communication network N.

  The drawer 27 is a drawer that stores cash such as coins and banknotes. The drawer 28 opens the drawer, for example, according to an instruction from the CPU 21.

  The printing unit 28 is, for example, a thermal printer, and has receipt and journal roll papers, and prints out data such as the amount of money on each roll paper in accordance with an instruction input from the CPU 21.

  Next, an outline of the conversion 1 process executed by the center server 10 will be described with reference to FIG. In the following description, it is assumed that the operation log data 51 is transmitted from the ECR 20A. The change 1 process is a general-purpose format (output file 91: total file, sales details file) that allows the user to use the operation log data 51 effectively based on the record output specification 71 and the destination master 61 stored in advance in the storage unit 15. , Accounting details file, opening / closing file). Specifically, in the conversion 1 process, the destination folder path of the folder (A company folder, B company folder, C company folder) in which the output file 91 is stored is acquired from the destination master 61, and the acquired destination folder path is set to the acquired destination folder path. This is a process of outputting the operation log data 51 to the output file 91 that exists and is specified by the record output specification 71.

  Here, an example of the configuration of the operation log data 51 is shown with reference to FIG. The operation log data 51 is an example of data to be registered in the center server 10 (data to be transmitted to the center server 10) among the operation log data input by the operator of the ECR 20A at the time of selling the product. The operation log data 51 includes, for example, a first record, a TYPE1 record, a TYPE2 record, a TYPE3 record, a TYPE9 record, and an END record.

  The first record and the END code are records that are always included in the operation log data 51. The first record is a record that stores information for identifying the operation log data 51. The END record is a record added to the end of the operation log data 51. The TYPE1 record, the TYPE2 record, the TYPE7 record, and the TYPE9 record are prepared in a format corresponding to the content of information input by the operator of the ECR 20A.

  Next, the configuration of the destination master 61 will be described with reference to FIG. The destination master 61 includes a registration code as an identification number indicating a code number for identifying an ECR, a company code for identifying a company, a company name of a user, and a destination folder indicating a destination of a folder in which the output file 91 is stored. Pass.

  Next, the configuration of the cash register authentication master 62 will be described with reference to FIG. The cash register authentication master 62 is a master file having information for the center server 10 to authenticate cash registers (ECR). The cash register authentication master 62 is generated / updated in the center server 10 at the time of registration of an owner who manages a store having an ECR. The cash register authentication master 62 includes a cash register number (a cash register code), a group code for classifying the type of company of the store where the ECR is installed, a company code for identifying the company, and a store where the ECR is installed. A store code for identification.

  In the conversion 1 process, a registration code that matches the registration code included in the first record of the operation log data 51 is retrieved from the destination master 61. Then, the destination folder path corresponding to (associated with) the searched registration code is referred to, and the operation log data 51 is output to the output file 91 existing in the folder indicating the referenced destination folder path.

  Next, the configuration of the record output specification 71 will be described with reference to FIGS. The record output specification 71 is a list that defines the output file 91 that outputs the operation log data 51. As shown in FIGS. 7 and 8, the record output specification 71 has an operation log data part 72 and an output file part 73. The operation log data part 72 has a record type, a function code, and a key name. The output file unit 73 includes total data indicating the total file, accounting details indicating the accounting details file, business details indicating the business details file, opening / closing stores indicating the opening / closing store files, and general purposes indicating the general-purpose file, And a record output exception that defines exceptions when the operation log data 51 is output to the output file 91.

  For example, in ECR 20A, it is assumed that there is a transaction in which “100 yen product A” and “190 yen product B” are settled with “290 yen cash”. In this case, (1) “first record”, (2) “TYPE1 record product A 100 yen (function code = 0063)”, (3) “TYPE1 record product B 190 yen (function code = 0063)”, (4 ) Operation log data is transmitted from the ECR 20A to the center server 10 in the order of “TYPE1 record cash 290 yen (function code = 00001)” and (5) “END record”. Then, the record output specification 71 is referred to in the center server 10, and (2) “TYPE1 record product A 100 yen (function code = 0063)” and (3) “TYPE1 record product B 190 yen (function code = 0063)”. (4) “TYPE1 record cash 290 yen (function code = 00001)” is output to the accounting details file, and (5) “END record” is output to the total data file.

  Next, an example of the structure of the output file 91 is shown with reference to FIG. 9 and FIG. The output file 91 includes a total file, a business details file, a transaction details file, and a store / exit file. The total file is a file that stores data relating to the total amount of goods. The business detail file is a file for storing data relating to sales merchandise. The accounting detail file is a file for storing data related to accounting for products. The store / exit file is a file that stores data related to the ECR operator's attendance / exit. The output file 91 shown in FIGS. 9 and 10 shows a record in which information for one transaction (information such as product name and amount) is stored.

  Next, an operation in which the operation log data 51 is transmitted from the ECR 20A to the center server 10 and the conversion 1 process is performed by the center server 10 will be described with reference to FIGS. First, the transmission process executed by the CPU 21 of the ECR 20A will be described with reference to FIG. The transmission process is a process of transmitting the operation log data 51 from the ECR 20A to the center server 10 via the communication unit 16.

  For example, when a product is sold, the transmission program read from the storage unit 25 and appropriately expanded in the RAM 23 and the CPU 21 is triggered by the input of an execution instruction of the transmission process via the input unit 22 by the operator of the ECR 20A. The transmission process is executed in cooperation with.

  First, a registration operation input of operation log data 51 (for example, data such as “100 yen” and “milk”) is received from an operator of the ECR 20A via the input unit 22 (step S11). And it is discriminate | determined whether the operation log data 51 is object registration data (step S12). Here, in the storage unit 25 of the ECR 20A, information (flag) indicating whether or not the operation log data 51 is target registration data (data to be transmitted to the center server 10) and operation log data are associated with each other. Masters are stored in advance. For example, when data of “100 yen” and “milk” is accepted in step S11, a flag associated with “100 yen” and “milk” is referred to. Then, if the reference flag is set to be the target registration data (for example, when the flag is “1”), the data of “100 yen” and “milk” are the target registration data. Determined.

  If it is determined in step S12 that the data is not target registration data (step S12; NO), the transmission process is terminated. When it is determined that it is target registration data (step S12; YES), the operation log data 51 is stored (added) in the storage unit 25 (step S13). Here, for example, when the operation log data is not transmitted to the center server 10 in the previous transaction, the operation log data for the previous transaction is still stored in the storage unit 25. In this case, operation log data for the current transaction is appended to the operation log data for the previous transaction.

  After the execution of step S13, when the product is sold and the transaction of the product is completed, it is determined whether or not the transaction is completed based on whether or not an input of a settlement button indicating that the transaction of the product is completed is received ( Step S14). When it is determined that the transaction has not ended (step S14; NO), the process proceeds to step S11. When it is determined that the transaction is over (step S14; YES), all the operation log data 51 stored in the storage unit 25 is transmitted to the center server 10 via the communication unit 26 (step S15). For example, when the operation log data for the previous transaction is stored in the storage unit 25, the operation log data 51 for the previous transaction is also transmitted to the center server 10 together with the log data for the current transaction.

  After execution of step S15, it is determined whether or not the operation log data 51 has been successfully transmitted (step S16). For example, the determination of this step is performed based on whether or not a message indicating that transmission of the operation log data 51 has failed has been received, or whether or not a response has been received from the center server 10 within a predetermined time. . If it is determined in step S15 that the transmission has not been successful (step S16; NO), the transmission process is terminated. In step S15, when it is determined that the transmission is successful (step S16; YES), the operation log data 51 stored in the storage unit 25 is cleared (memory is cleared) (step S17). After execution of step S17, the transmission process is terminated.

Next, the flow of the conversion 1 process executed by the CPU 11 of the center server 10 will be described in detail with reference to FIG.
It is assumed that the destination master 61 and the record output specification 71 are stored in the storage unit 15 of the center server 10 in advance.

  For example, with the operation log data 51 received via the communication unit 16 as a trigger, the conversion 1 process is executed by the operation of the conversion 1 program read from the storage unit 15 and appropriately expanded in the RAM 13 and the CPU 11. Is done.

  First, it is determined whether or not the OS is terminated based on whether or not an OS (Operating System) termination operation input is received from the operator of the center server 10 via the input unit 12 (step S21). If it is determined that the OS has ended (step S21; YES), the transmission process ends. If it is determined that the OS has not ended (step S21; NO), one record of the operation log data 51 is received from the ECR 20A via the communication unit 16 (step S22).

  After execution of step S22, the record type of the received operation log data 51 is referred to, and it is determined whether or not the operation log data 51 is the first record (step S23). When it is determined that the record is not the first record (step S23; NO), the process proceeds to step S21. If it is determined that the record is the first record (step S23; YES), the registration code (registration number) included in the first record is checked (step S24). Then, based on whether or not the registration code included in the first record matches the registration number (registration code) of the registration authentication master 62, it is determined whether or not the registration number is OK (step S25). When it is determined that the registration number is not OK (step S25; NO), authentication error information is transmitted to the ECR 20A via the communication unit 16 (step S26). And after execution of step S26, it transfers to step S21.

  If it is determined in step S25 that the registration number is OK (step S25; YES), the destination master 61 is searched using the registration code as a key, and the destination folder path is obtained (step S27). Specifically, a registration code that matches the registration code included in the first record of the operation log data 51 is searched from the destination master 61, and the destination folder path (for example, the A company folder associated with the searched registration code). Folder path) is obtained.

  After execution of step S27, the work file temporarily generated to output (read) the record is cleared (step S28). Then, one record of operation log data 51 is received from the ECR 20A via the communication unit 16 (step S29).

  After execution of step S29, the record type of the operation log data 51 received in step S29 is referred to, and it is determined whether or not the record type of the operation log data 51 is TYPE1-9 records (step S30). If it is determined that the record is a TYPE 1-9 record (step S30; YES), the record is output to the work file (step S31). After execution of step S31, the process proceeds to step S29.

  If it is determined in step S30 that the record is not TYPE 1-9 (step S30; NO), it is determined whether the record is an END record (step S32). If it is determined that the record is not an END record (step S32; NO), the process proceeds to step S29. If it is determined that the record is an END record (step S32; YES), the END record is output to the work file (step S33). After execution of step S33, a record output process for outputting the record output to the work file to the output file 91 is executed (step S34). After execution of step S34, the process proceeds to step S21.

  Next, the record output process executed in step S34 of the conversion 1 process shown in FIG. 12 will be described with reference to FIG. First, one record of the work file is read (step S41). Then, based on whether or not the record output to the work file is an END record, it is determined whether or not the record is over (step S42). If it is determined that the record is over (step S42; YES), the record output process is terminated, and the process proceeds to step S21 of the conversion 1 process.

  If it is determined in step S42 that the record is not the end (step S42; NO), the record type of the record output to the work file is referred to, and whether or not the record output to the work file is a TYPE1 record. It is determined (step S43). If it is determined that the record is a TYPE1 record (step S43; YES), a TYPE1 record process is executed (step S44). After execution of step S44, the process proceeds to step S41.

  If it is determined in step S43 that the record is not a TYPE1 record (step S43; NO), the record type of the record output to the work file is referred to, and it is determined whether the record output to the work file is a TYPE2 record. (Step S45). If it is determined that the record is a TYPE2 record (step S45; YES), a TYPE2 record process is executed (step S46). After execution of step S46, the process proceeds to step S41.

  If it is determined in step S45 that the record is not a TYPE2 record (step S45; NO), the record type of the record output to the work file is referred to, and it is determined whether or not the record output to the work file is a TYPE7 record. (Step S45). If it is determined that the record is a TYPE7 record (step S47; YES), a TYPE7 record process is executed (step S48). After execution of step S48, the process proceeds to step S41.

  If it is determined in step S47 that the record is not a TYPE7 record (step S47; NO), the record type of the record output to the work file is referred to, and it is determined whether the record output to the work file is a TYPE9 record. (Step S49). If it is determined that the record is a TYPE 9 record (step S49; YES), a TYPE 9 record process is executed (step S50). After execution of step S50, the process proceeds to step S41.

  If it is determined in step S49 that the record is not a TYPE 9 record (step S49; NO), the record type of the record output to the work file is referred to, and it is determined whether or not the record output to the work file is an END record. (Step S51). If it is determined that the record is an END record (step S51; YES), an END record process is executed (step S52). After execution of step S52, the process proceeds to step S41.

  Next, the TYPE1 record process executed in step S44 of the record output process shown in FIG. 13 will be described with reference to FIG. First, the function code included in the TYPE1 record is referred to, and it is determined whether or not the function code is 00001 to 00002 (step S61). When it is determined that the function code is not 00001 to 00002 (step S61; NO), it is determined whether or not the function code is 000051 to 0603 (step S62). When it is determined that the function code is not “00051” to “00063” (step S62; NO), the TYPE1 record process is terminated, and the process proceeds to step S41 of the record output process.

  If it is determined in step S62 that the function code = 00051-00063 (step S62; YES), the function code of the next record output to the work file is referred to and whether the function code of the next record is 0034 or not. A determination is made (step S63). Here, in the record output specification 71 shown in FIG. 7 and FIG. 8, the “record output exception” of the function code = 0051, 0063 of the TYPE1 record is “not output when the next record is 0034 (immediate correction)”. Is set. Therefore, when the function code of the next record is 0034 (immediate correction), no processing is executed.

  If it is determined in step S63 that the function code of the next record is 0034 (step S63; YES), no process is executed, the TYPE1 record process is terminated, and the process proceeds to step S41 of the record output process. .

  If it is determined in step S63 that the function code of the next record is not “0034” (step S63; NO), a record is added to the business statement file existing in the destination folder path (step S64). Here, in the record output specification 71 shown in FIGS. 7 and 8, it is set that the data of TYPE1 with function code = 0051, 0063 is output to the business statement file. Therefore, the record is added to the business statement file existing in the destination folder path (existing in the folder indicating the destination folder path).

  If it is determined in step S61 that the function code is 00001 to 00002 (step S61; YES), the function code of the next record output to the work file is referred to and whether or not the function code of the next record is 0034 is determined. It is determined (step S65). Here, in the record output specification 71 shown in FIG. 7 and FIG. 8, the “record output exception” of the function code = 0001 to 0021 of the TYPE 1 record is “not output when the next record is 0034 (immediate correction)”. Is set. Therefore, when the function code of the next record is 0034 (immediate correction), no processing is executed.

  If it is determined in step S65 that the function code of the next record is 0034 (step S65; YES), no process is executed, the TYPE1 record process is terminated, and the process proceeds to step S41 of the record output process. . If it is determined in step S65 that the function code of the next record is not “0034” (step S65; NO), the record is added to the accounting statement file existing in the destination folder path (step S66). Here, in the record output specification 71 shown in FIGS. 7 and 8, it is set that the data of TYPE1 with function codes = 0001 to 0021 is output to the accounting statement file. Therefore, a record is added to the accounting statement file existing in the destination folder path (existing in the folder indicating the destination folder path). After execution of step S66, the TYPE1 record process is terminated, and the process proceeds to step S41 of the record output process.

  Next, the TYPE2 record process executed in step S46 of the record output process shown in FIG. 13 will be described with reference to FIG. First, the function code included in the TYPE2 record is referred to, and it is determined whether or not function code = 1001 (step S71). If it is determined that the function code is not 1001 (step S71; NO), the TYPE2 record process is terminated.

  If it is determined in step S71 that the function code is 1001 (step S71; YES), the function code of the next record output to the work file is referred to, and it is determined whether or not the function code of the next record is 0034. (Step S72). Here, in the record output specification 71 shown in FIG. 7 and FIG. 8, “Record output exception” of function code = 1001 of TYPE2 record is set to “not output when the next record is 0034 (immediate correction)” Has been. Therefore, when the function code of the next record is 0034 (immediate correction), no processing is executed.

  If it is determined in step S72 that the function code of the next record is 0034 (step S72; YES), no process is executed, the TYPE2 record process is terminated, and the process proceeds to step S41 of the record output process. . If it is determined in step S72 that the function code of the next record is not “0034” (step S72; NO), a record is added to the business statement file existing in the destination folder path (step S73). Here, in the record output specification 71 shown in FIG. 7 and FIG. 8, it is set that the data of TYPE2 with function code = 1001 is output to the business statement file. Therefore, the record is added to the business statement file existing in the destination folder path (existing in the folder indicating the destination folder path). After execution of step S73, the TYPE2 record process is terminated, and the process proceeds to step S41 of the record output process.

  Next, the TYPE7 record process executed in step S48 of the record output process shown in FIG. 13 will be described with reference to FIG. First, the function code included in the TYPE7 record is referred to, and it is determined whether or not the function code = 0108 (step S81). If it is determined that the function code is not 0108 (step S81; NO), the TYPE7 record process is terminated.

  If it is determined in step S81 that the function code = 0108 (step S81; YES), a record is added to the store / exit file existing in the destination folder path (step S82). Here, in the record output specification 71 shown in FIGS. 7 and 8, it is set that the data of TYPE 7 with the function code = 0108 is output to the store / exit file. Therefore, the record is added to the store / leave file existing in the destination folder path (existing in the folder indicating the destination folder path). After execution of step S82, the TYPE7 record process is terminated, and the process proceeds to step S41 of the record output process.

  Next, with reference to FIG. 17, the TYPE9 record process executed in step S50 of the record output process shown in FIG. 13 will be described. First, the function code included in the TYPE 9 record is referred to, and it is determined whether or not the function code = 0023,0027-0030 (step S91). If it is determined that the function code is not 0023, 0027 to 0030 (step S91; NO), the TYPE 9 record process is terminated.

  If it is determined in step S91 that the function code is 0023, 0027 to 0030 (step S91; YES), the function code of the next record output to the work file is referred to, and whether the function code of the next record is 0034 or not. Is determined (step S92). Here, in the record output specification 71 shown in FIG. 7 and FIG. 8, the “record output exception” of the function code of the TYPE 9 record = 0023, 0027 to 0030 is “not output when the next record is 0034 (immediate correction)”. "Is set. Therefore, when the function code of the next record is 0034 (immediate correction), no processing is executed.

  If it is determined in step S92 that the function code of the next record is 0034 (step S92; YES), no process is executed, the TYPE9 record process is terminated, and the process proceeds to step S41 of the record output process. . If it is determined in step S92 that the function code of the next record is not 0034 (step S92; NO), a record is added to the business statement file existing in the destination folder path (step S93). Here, in the record output specification 71 shown in FIGS. 7 and 8, it is set that the data of TYPE 9 with the function code = 0023, 0027 to 0030 is output to the business statement file. Therefore, the record is added to the business statement file existing in the destination folder path (existing in the folder indicating the destination folder path). After execution of step S93, the TYPE9 record process is terminated, and the process proceeds to step S41 of the record output process.

  Next, the END record process executed in step S52 of the record output process shown in FIG. 13 will be described with reference to FIG. First, the function code included in the END record is referred to, and it is determined whether or not the function code = 0023,0027 to 0030 (step S101). If it is determined that the function code is not 0023, 0027 to 0030 (step S101; NO), the END record process is terminated.

  If it is determined in step S101 that the function code = 0023,0027-0030 (step S101; YES), the function code of the previous record output to the work file is referred to, and the function code of the previous record = 0108. It is determined whether or not (step S102). Here, in the record output specification 71 shown in FIG. 7 and FIG. 8, the “record output exception” of the END record function code = 0023,0027 to 0030 is “however, if the previous record is an END record of a store opening / closing. "Do not output" is set. Therefore, when the function code of the previous record is 0108 (exit / leave), no processing is executed.

  If it is determined in step S102 that the function code of the previous record is 0108 (step S102; YES), no process is executed, the END record process is terminated, and the process proceeds to step S41 of the record output process. . If it is determined that the function code of the previous record is not 0108 (step S102; NO), a record is added to the total file existing in the destination folder path (step S103). Here, in the record output specification 71 shown in FIGS. 7 and 8, it is set that the data of the END record having the function code = 0023, 0027 to 0030 is output to the total file. Therefore, a record is added to the total file existing in the destination folder path (existing in the folder indicating the destination folder path). After execution of step S103, the END record process is terminated, and the process proceeds to step S41 of the record output process.

  Next, an overview of the conversion 2 process executed by the CPU 11 of the center server 10 will be described with reference to FIG. The conversion 2 process refers to the conversion specification file 101 and the conversion master 102, and converts the output file 91 (total file, business details file, accounting details file, store opening and closing file) converted by the conversion 1 processing into the conversion specification file of each company. Is converted into a dedicated format (user specification file 103: user specification total file, user specification sales details file, user specification accounting details file, user specification exit / exit file). Specifically, in the conversion 2 process, the output file 91 existing in the folder indicating the input folder path registered in the conversion master 102 is converted into the user specification file 103 by the filter (data conversion program), and the converted user specification is converted. This is a process for outputting the file 103 to a folder having an output folder path registered in the conversion master 102 (Company A distribution folder, Company B distribution folder, Company C distribution folder). Here, the conversion by the filter is performed based on the contents defined in the conversion specification file. Further, the conversion by the filter is performed according to the conversion timing (execution time) registered in the conversion master 102.

Next, filter processing specifications will be described with reference to FIG. The filter converts the output file 91 into the user specification file 103 according to the definition contents of the conversion specification file 101 (input file definition, output file definition, record conversion definition), and outputs the converted user specification file 103 to the distribution folder. It is a printer type file conversion program software. The filter command format is represented by "filter -s spec file name -i input file name -o output file name".
For example, in the input file definition, the first field of the record of the input file is defined. In the output file definition, the first field of the record of the output file 91 is defined. Further, the record conversion definition defines that the data of the first field of the record of the input file is substituted for the first field of the output file 91.

  The specification file name shown in FIG. 21 is defined as the specification file name in the filter command format. For example, “xxxxxxxx_total data.spc” is defined (set) in the specification file name. Here, xxxxxxxx = company code. In the input file name, the name of the output file 91 is defined. The name of the user specification file 103 is defined as the output file name.

  Next, the configuration of the conversion master 102 will be described with reference to FIG. The conversion master 102 includes a company code, an input folder path indicating the folder path of the folder in which the output file 91 exists, an output folder path indicating the folder path of the folder outputting the user specification file 103, and a conversion process (conversion described later). The processing executed in step S118 or S122 of the two processes) at time intervals or at a specified time, the execution time indicating the execution time of the conversion process, and the conversion process And a previous execution date and time indicating the date and time of execution.

  Specifically, when the execution category = “1”, the execution interval is specified in units of 4 digits. When the execution classification = “2”, the execution time is specified by a 4-digit time (hhmm; h is hours, m is minutes). When the execution category = “1”, the execution interval is set in minutes at the execution time. For example, when the execution interval is 5 minutes, “0005” is set as the execution interval. Further, when the execution category = “2”, the designated time is set as the execution time. For example, when the designated time is AM 3:00, “0300” is set as the execution interval.

  As the previous execution date and time, the date and time (yyyymmddhhmmss; y is the year, m is the month, d is the day, h is the hour, m is the minute, and s is the second) when the conversion process was previously executed.

  Next, an example of the user specification file 103 converted by the conversion 2 process will be described with reference to FIG. As shown in FIG. 23, the user specification file 103 is expressed in an output format defined in the conversion specifications of each user company.

  Next, the flow of the conversion 2 process executed by the CPU 11 of the center server 10 will be described in detail with reference to FIGS.

  It is assumed that the filter in which the conversion specification file 101 is defined and the conversion master 102 are stored in the storage unit 15 in advance.

  For example, when the operator of the center server 10 inputs an execution instruction for conversion 2 processing via the input unit 12, the conversion 2 program read from the storage unit 15 and appropriately expanded in the RAM 13 and the CPU 11 are triggered. The conversion 2 process is executed in cooperation with the above.

  First, it is determined whether or not the OS has ended (step S111). If it is determined that the OS has ended (step S111; NO), the conversion 2 process ends. When it is determined that the OS has not ended (step S111; YES), one conversion master 102 is read (step S112). Specifically, the contents set in the conversion master 102 are read one by one from the top.

  After execution of step S112, it is determined whether or not the conversion master 102 is over (step S113). Specifically, for example, when there are data for 10 companies in the conversion master 102, the determination of this step is performed based on whether or not all the data for 10 companies have been read. If it is determined that it is not the end (step S113; NO), the conversion master 102 is positioned at the head (step S114). For example, if the execution time of the conversion process is designated in units of “5 minutes” as the execution time of the conversion master 102, the content set in the conversion master 102 every 5 minutes is positioned at the beginning of the reading position, Read out. After execution of step S114, the process proceeds to step S111.

  If it is determined in step S113 that the process is over (step S113; YES), the execution section of the conversion master 102 is referred to and it is determined whether or not execution section = 1 (step S115). If it is determined that the execution category = 1 (step S115; YES), it is determined whether (system date-previous execution date)> (system date + execution time) (step S116). Here, the system date and time indicates the current time “yyymmddhhmms” (y is the year, m is the month, d is the day, h is the hour, m is the minute, and s is the second) timed by the time measuring unit 17. The previous execution date and time indicates the date and time when the conversion process described later was executed last time. The system date indicates the time “yyymmdd” up to the day of the current time. The execution time indicates the execution time of the conversion master 102. For example, when the current time is 13:00 on September 16, 2008, the previous execution date is 12:53:00 on September 16, 2008, and the execution time (execution interval) is 5 minutes The system date and time “2008091610000” —the previous execution date and time “200809916125300”> the system date and time “20080916” + the execution time “000500” (that is, “20080916000700”> “20080916 + 000500”, and step S116 becomes YES.

  In step S116, when it is determined that (system date-previous execution date)> (system date + execution time) is not satisfied (step S116; NO), the process proceeds to step S111. In step S116, if it is determined that (system date-previous execution date)> (system date + execution time) (step S116; YES), the conversion master 102 is updated with the system date / time set to the previous execution date / time. (Step 117). After execution of step S117, conversion processing is executed (step S118). After execution of step S118, the process proceeds to step S111.

  If it is determined in step S115 that the execution category is not 1 (step S115; NO), it is determined whether or not the execution category is 2 (step S119). When it is determined that the execution category is not 2 (step S119; NO), the process proceeds to step S111. If it is determined that the execution classification = 2 (step S119; YES), it is determined whether (system date> system date + execution time) and (system date ≠ first six execution dates). (Step S120). For example, the current time is 13:00 on September 16, 2008, the execution time is 12:55:00 on September 16, 2008, and the previous execution date is September 15, 2008. In this case, the system date and time “2008091610000”> the system date and time “20080916” + the execution time “125500” and the system date and time “20080916” ≠ the first six digits “20080915” of the previous execution date and time, step S120;

  If it is determined in step S120 that (system date> system date + execution time) and (system date ≠ first six digits of previous execution date) are not satisfied (step S120; NO), the process proceeds to step S111. If it is determined in step S120 that (system date> system date + execution time) and (system date ≠ first 6 digits of previous execution date) (step S120; YES), the system date and time is set to the previous execution date and time. The change master is updated (step S121). After execution of step S121, conversion processing is executed (step S122). After execution of step S122, the process proceeds to step S111.

  Next, the details of the conversion process executed in step S118 or step S122 of the conversion 2 process shown in FIGS. 24 and 25 will be described with reference to FIG.

  First, the company code_total data is set to the spec file name of the filter command format (company code_total data → set to the spec file name). Also, the file name of the total file existing in the folder indicating the input folder path registered in the conversion master 102 is set to the input file name of the filter command format (the total file of the input folder path → set to the input file name) ). Also, the file name of the user specification total file to be output to the folder (distribution folder) indicating the output folder path registered in the conversion master 102 is set to the output file name of the filter command format (total file of the output folder path) → Set to output file name) (step S131). Then, the file conversion program software “filter” is executed (step S132). When “filter” is executed, the total file is converted into a user specification total file, and the converted user specification total file is output to the distribution folder. Then, the total file (total file of the input folder path) existing in the folder indicating the input folder path is deleted (step S133).

  After the execution of step S133, the company code_accounting statement data is set to the spec file name in the filter command format (company code_company statement data → set to the spec file name). In addition, the file name of the accounting detail file existing in the folder indicating the input folder path registered in the conversion master 102 is set to the input file name in the command format of filter (the accounting statement file of the input folder path → the input file name) Set). In addition, the file name of the user specification accounting statement file to be output to the folder (distribution folder) indicating the output folder path registered in the conversion master 102 is set to the output file name of the filter command format (accounting of the output folder path). Detail file → set to output file name) (step S134). Then, the file conversion program software “filter” is executed (step S135). When “filter” is executed, the accounting statement file is converted into a user specification accounting statement file, and the converted user specification accounting statement file is output to the distribution folder. Then, the accounting details file (the accounting details file of the input folder path) existing in the folder indicating the input folder path is deleted (step S136).

  After the execution of step S136, the company code_business statement data is set to the filter format spec file name (company code_business statement data → spec file name). Further, the file name of the business statement file existing in the folder indicating the input folder path registered in the conversion master 102 is set to the input file name in the command format of filter (the business statement file of the input folder path → the input file name) Set). In addition, the file name of the user-specific business statement file to be output to the folder (distribution folder) indicating the output folder path registered in the conversion master 102 is set to the output file name of the filter command format (the business of the output folder path) Detail file → set to output file name) (step S137). Then, the file conversion program software “filter” is executed (step S138). When “filter” is executed, the business specification file is converted into a user specification business specification file, and the converted user specification business specification file is output to the distribution folder. Then, the business detail file (business detail file of the input folder path) that existed in the folder indicating the input folder path is deleted (step S139).

  After execution of step S139, the company code_exit / exit data is set in the filter command format spec file name (company code_exit / exit data → set spec file name). Further, the file name of the store / exit file existing in the folder indicating the input folder path registered in the conversion master 102 is set to the input file name of the filter command format (the store / exit file of the input folder path → input Set to file name). Also, the file name of the user-specified exit / exit file to be output to the folder (distribution folder) indicating the output folder path registered in the conversion master 102 is set to the output file name of the filter command format (the output folder path Store / leave file → set to output file name) (step S140). Then, the file conversion program software “filter” is executed (step S141). When “filter” is executed, the store / exit store file is converted into a user-specific store / exit file, and the converted user-specific store / exit file is output to the distribution folder. Then, the store / exit file (the store / exit file of the input folder path) existing in the folder indicating the input folder path is deleted (step S142). After the execution of step S142, the conversion process is terminated, and the process proceeds to step S111 of the conversion 2 process.

  As described above, according to the present embodiment, the center server 10 receives operation log data from the ECR 20A for each product transaction via the communication unit 16, and stores the received operation log data in the output file 91 according to the record output specification 71. The converted output file 91 is stored in the storage unit 15. For this reason, the user polls and acquires the output file 91 stored in the storage unit 15, so that in the network system 1 equipped with ECR, the sales information (information related to product transactions such as product name and price, ECR The information regarding the operator's attendance / exit etc.) can be obtained sequentially with the output file 91 in a format that can be used effectively by the user.

  In addition, the registration code that matches the registration code included in the operation log data is searched from the storage unit 15 and the output file 91 is stored in the folder indicating the destination folder path associated with the searched registration code. The output file 91 can be stored in an appropriate storage area (folder).

  Further, the output file 91 is converted into the user specification file 103, and the converted user specification file 103 is stored in the storage unit 15. For this reason, the user polls and acquires the user specification file 103 stored in the storage unit 15, so that in the network system 1 having ECR, the sales information (information relating to product transactions such as product name and price, ECR Can be sequentially acquired in the user specification file 103 in a format desired by the user.

  Further, since the output file 91 is converted into the user specification file 103 according to the conversion timing (execution time), the output file 91 can be converted into the user specification file 103 at an appropriate timing.

  Since the center server 10 authenticates the ECR 20A, the network system 1 can be realized by using the Internet for the communication network N. Therefore, the network system 1 can be realized using a general-purpose communication network without using a dedicated communication network.

  Further, it is needless to say that the detailed configuration and detailed operation of each component of the network system 1 in the above embodiment can be appropriately changed without departing from the gist of the present invention.

It is a block diagram which shows the structure of the network system of embodiment which concerns on this invention. It is a block diagram which shows the internal structure of a center server. It is a block diagram which shows the internal structure of ECR. It is a figure which shows the outline | summary of the conversion 1 process. It is a figure which shows operation log data. (A) is a figure which shows a destination master. (B) is a figure which shows an authentication master. It is a figure which shows a record output specification. It is a figure which shows a record output specification. It is a figure which shows an output file. It is a figure which shows an output file. It is a flowchart which shows a transmission process. It is a flowchart which shows the conversion 1 process. It is a flowchart which shows a record output process. It is a flowchart which shows a TYPE1 record process. It is a flowchart which shows a TYPE2 record process. It is a flowchart which shows a TYPE7 record process. It is a flowchart which shows a TYPE9 record process. It is a flowchart which shows an END record process. It is a figure which shows the outline | summary of the conversion 2 process. It is a figure explaining the processing specification of filter. It is the figure which showed the definition content of the specification file name. It is a figure which shows a conversion master. It is a figure which shows a user specification file. It is a flowchart which shows the conversion 2 process. It is a flowchart which shows the conversion 2 process. It is a flowchart which shows a conversion process.

Explanation of symbols

1 Network System 10 Center Server 11, 21 CPU
12, 22 Input unit 13, 23 RAM
14, 24 Display unit 15, 25 Storage unit 16, 26 Communication unit 17, 29 Timekeeping unit 18, 29a Bus 27 Drawer 28 Print unit 20A, 20B ECR
30A, 30B User backbone system N Communication network

Claims (4)

In a network system in which a plurality of data processing devices and a server device are connected via a network,
The data processing device includes:
Input means for accepting operation log data input when selling products;
When the operation log data accepted by the input means is operation log data to be transmitted to the server device, the operation log data includes transmission means for transmitting the operation log data to the server device for each product transaction,
The server device
Storage means for storing information;
Receiving means for receiving operation log data transmitted from the data processing device;
First conversion means for converting the operation log data received by the receiving means into a general-purpose format that can be used effectively by a user according to a predetermined data conversion specification;
Control means for storing the general-purpose format converted by the first conversion means in the storage means;
A network system comprising: The storage means
Storing a destination folder path indicating a folder destination and identification information for identifying the data processing device in association with each other;
The operation log data is
Including the identification information;
The control means includes
The identification format matching the identification information included in the operation log data is searched from the storage unit, and the general-purpose format is stored in a folder indicating a destination folder path associated with the searched identification information. The network system described. A second conversion means for converting the general-purpose format stored in the storage means into a user-desired format according to a user-desired conversion specification;
The control means includes
3. The network system according to claim 1, wherein the format desired by the user converted by the second conversion unit is stored in the storage unit. The storage means
Storing the conversion timing for converting the general-purpose format into a format desired by the user;
The control means includes
4. The network system according to claim 3, wherein the general-purpose format is converted into a user-desired format according to the conversion timing stored in the storage means.

Images