JP2011060057A - Information processing apparatus, control method thereof, program, and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technology of changing display items for each user when different users refer to the same data in a web-EDI system. <P>SOLUTION: An information processing apparatus includes: a layout setting means for setting a screen layout to be referred to according to the kind of a user; a user information registration means for registering information for identifying users and a plurality of pieces of user information; a receiving means for receiving a log-in request from a client terminal; a user specification means for specifying the kind of a user from the user information registered in the user information registration means by using information for identifying the user included in a log-in request received by the receiving means; a generation means for generating screen data to be displayed on a client terminal by using the screen layout registered in the layout registration means, according to the kind of the user and order receiving/placing data in accordance with the kind of the user specified by the specification means; and a transmission means for transmitting the screen data generated by the generation means. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  This is a technique related to a display method in Web-EDI.

  2. Description of the Related Art Recently, an EDI (Electronic Data Interchange) system that performs electronic commerce has been introduced in enterprises and the like in order to improve operational efficiency in ordering operations.

  Normally, a system used in a company is constructed in a format decided by the company, but the EDI system converts it into a standard format in order to try electronic commerce with other companies. In addition, it communicates with the other company using a standard protocol.

  Currently, among EDI systems, there is Web-EDI that realizes EDI on the Internet. Web-EDI has an advantage that the line cost can be reduced compared to the conventional EDI using a line such as a dedicated line or a VAN (value added communication network).

  As one form of using Web-EDI, in order for a company to receive and place orders for products with a supplier company, a site that can use Web-EDI is disclosed to the supplier company, and the supplier In a company, there is a form in which product ordering work is performed through a Web browser. There is also a form in which there is a re-supplier company that the supplier company further purchases.

  In a transaction form in which a re-supplier company appears, it is necessary to refer to the same data in the supplier company and the re-supplier company. For example, each needs to refer to order data from an ordering company.

  Currently, data for each user can be handled by menus, business screens, forms, and file transmission / reception (upload / download), but the same data cannot be referenced by supplier companies and re-supplier companies. Even if the same data can be referred to, when the supplier company and the re-supplier company refer to it, the re-supplier company cannot make the items that should be kept private.

Patent Document 1 includes World.
With regard to WEB-EDI that is constructed using EDI using Wide Web technology, a technology that creates an EDI message by formatting each client based on a format definition file eliminates the need for conversion work at the time of download. It is disclosed.

JP 2004-287972 A

  However, the technique described in Patent Document 1 has conventionally required the work of creating a new CSV file by converting it into a format suitable for its own system in order to import the downloaded CSV file into various systems. Is a technique that does not solve the problem when different users refer to the same data.

  An object of the present invention is to provide a technique capable of changing display items for each user when different users refer to the same data in a Web-EDI system. To do.

  The present invention is an information processing apparatus that receives and orders merchandise via a network, and includes a layout setting unit that sets a screen layout that can be referred to according to the type of the user, and a plurality of user information together with information for identifying the user Registered by the user information registration unit using information identifying a user included in the login request received by the receiving unit, a receiving unit receiving a login request from the client terminal, User specifying means for specifying the type of the user from the user information, and a screen layout registered by the layout registration means corresponding to the type of the user according to the type of user specified by the specifying means, The screen data that can be displayed on the client terminal is generated using the ordering data. With a generation unit, and transmission means for transmitting the screen data generated by the generation unit.

  According to the present invention, in a Web-EDI system, when different users refer to the same data, display items can be changed for each user.

System Configuration Hardware configuration diagram Pre-setting flowchart Example showing registered user information Screen example for screen editing Example of edit screen Example of edit screen Example of edit screen Example of edit screen Example of edit screen Example of edit screen Example of edit screen Example of edit screen Flow chart showing the flow of processing in Web-EDI Flow chart showing the flow of processing in Web-EDI Login screen example Registration table example Registration table example Example of menu screen Example of menu screen Example of search screen Example of search results Example of search results An example of a PDF file Example of menu screen Example of search screen Example of search results Example of search results An example of a PDF file

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram illustrating a configuration of a Web-EDI system (information processing system) according to an embodiment of this invention.

  The Web-EDI server 101 (information processing apparatus) and the client terminal 102 exchange EDI data, which is electronic information related to commercial transactions, via the network 103.

  The configuration of various terminals connected to the network in FIG. 1 is an example, and it goes without saying that there are various configuration examples depending on the application and purpose.

  The Web-EDI server 101 has an EDI communication function and exchanges data with the client terminal 102.

  In addition, since the connection destination is mostly not a single company but a plurality of companies, the Web-EDI terminal 101 exchanges EDI data with a plurality of client terminals 102.

  Next, the hardware configuration of the EDI terminal 101 in FIG. 1 will be described with reference to FIG. Since the hardware configuration of the EDI server 102 is the same, the description thereof is omitted.

  FIG. 2 is a diagram illustrating a hardware configuration of the EDI terminal 101.

  The CPU 201 comprehensively controls each device and controller connected to the system bus 204.

  Further, the ROM 202 or the external memory 211 is necessary to realize a BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as an OS), which is a control program of the CPU 201, or a function executed by each server or each PC. Various programs to be described later are stored.

  The RAM 203 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program necessary for execution of processing into the RAM 203 and executing the program.

  An input controller (input C) 205 controls input from a pointing device such as a keyboard 209 or a mouse (not shown).

  A video controller (VC) 206 controls display on a display device such as a CRT display (CRT) 210. The display device may be a liquid crystal display as well as a CRT. These are used by the administrator as needed. The present invention is not directly related.

  The memory controller (MC) 207 is connected via an adapter to a hard disk (HD), FD or PCMCIA card slot for storing boot programs, browser software, various applications, font data, user files, editing files, various data, etc. The access to the external memory 211 such as the CF memory to be controlled is controlled.

  A communication I / F controller (communication I / FC) 208 is connected to and communicates with an external device via a network, and executes communication control processing in the network. For example, Internet communication using TCP / IP is possible.

  Note that the CPU 201 enables display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example. In addition, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the CRT 210.

  A program 212 for realizing the present invention is recorded in the external memory 211 and is executed by the CPU 201 by being loaded into the RAM 203 as necessary. Furthermore, the definition file 213 and various information tables 214 used by the program 212 according to the present invention are stored in the external memory 211, and detailed description thereof will be described later.

  FIG. 3 is a flowchart showing a pre-registration process in the Web-EDI server.

  First, the administrator of the Web-EDI server needs to perform user registration for using this system.

  In step 301, the Web-EDI server sets company information / department information. Thereby, user registration is completed. Specifically, the administrator operates the registration screen to register various input information.

  FIG. 4 shows an example of a table for managing user information after registration.

  In the group 401, a group to which the user belongs is registered. In the company code 402, a code for identifying a supplier company (a supplier company) that uses this system is input. In the company name 403, a supplier name corresponding to the company code is registered. In the department code 404, a department code for further distinguishing users in the business partner company is registered. In the department name 405, the department name is registered. In the present embodiment, the supplier company code and company name of the supplier company are registered. For example, when the company that manages the Web-EDI server is company A and the company A's customer company is company B (also referred to as a supplier company or a contractor company), the company B further deals with the transaction. When there is a company C (also referred to as a re-purchasing company or a subcontracting company), a department code and department name for identifying the company C are registered. In the present embodiment, it is assumed that the name of the shipping location of the company (also referred to as a shipping place; the same applies hereinafter) is input as the department name, not the company name. Note that 404 and 405 are blank in the record of company B itself. In the user ID 406, a user ID in the system is registered. In the login name 407, a login name in the system is registered. Note that passwords are managed separately.

  In step 302, the Web-EDI server sets various menu screens. Thereby, registration of the menu screen operated by each user is completed. Specifically, the menu screen is registered using information input by the administrator operating the registration screen.

  The procedure for registering the menu screen will be described with reference to FIGS.

  FIG. 5 is an example of a screen displayed on the administrator terminal when menu screen editing is performed.

  In the screen name 501, the edited screen name is registered.

  Here, the registration procedure of order form printing (supplier) 502 and order form printing (shipping place) 503 relating to the present embodiment will be described. The registration procedure starts when the add 504 button is pressed.

  A registration example of order form printing (supplier) 502 will be described with reference to FIGS. 6 to 9, and a registration example of order form printing (shipping place) 503 will be described with reference to FIGS.

  FIG. 6 is an example of a screen for editing the details of the menu screen.

  Various settings related to the menu screen are input via the screen. By setting “for each company” in all data 601, data for all suppliers is extracted for each supplier. In addition, by checking the search, header, and details with the internal_warehouse code 602, the “internal_warehouse code” can be used in the search, list, and detail screens.

  FIG. 7 is an example of a screen for setting a search key.

  Settings relating to the search key are input via the screen. The internal_warehouse code 701 is set to use “internal_warehouse code” as a combo box on the search screen.

  FIG. 8 is an example of a screen for editing the layout (list) of the menu screen.

  Settings relating to the screen layout (list) are input via the screen. In 801, a setting for displaying the shipping location as a heading on the list screen is made. In addition, according to 802, a setting for replacing the shipping location name based on “internal_vendor code” and “internal_warehouse code” on the list screen, and “internal_warehouse code” not being displayed are the shipping location name Settings are made for use during replacement. Thereby, an item (heading) that can be referred to is set.

  FIG. 9 is a screen example for editing the layout (details) of the menu screen.

  Settings relating to the layout (details) are input via the screen. In 901, a setting is made to display the shipping location as a heading in the header portion of the detailed screen. From 902, the setting to display the replacement location name based on “Internal_Vendor Code” and “Internal_Warehouse Code” in the header part of the detail screen, and the hidden “Internal_Warehouse Code” Settings for use in name substitution and flight type name substitution are made. From 903, the purchase price and the order amount are set as headings in the detail part of the detail screen. In step 904, a setting for displaying “purchase price” in the detail part of the detailed screen and a setting for displaying the result of “number of orders” × “purchase price” are made as the order amount of the calculation output. In step 905, the sum of the sum (calculation result) “order amount” of the detailed records is displayed in the footer portion (total field) of the detail screen.

  FIG. 10 is a screen example for editing the details of the menu screen.

  Various settings related to the menu screen are input via the screen. Note that by setting “for each company” in all data 1001, data of all suppliers is extracted for each supplier. In 1002, data is extracted with the department code (warehouse code) whose “internal_warehouse code” belongs to the login user and the above conditions. Further, by checking the item with the internal_warehouse code 1002, the “internal_warehouse code” can be used on the detailed screen.

  FIG. 11 is an example of a screen for setting a search key. FIG. 12 is an example of a screen for editing the layout (list) of the menu screen. FIG. 13 is a screen example for editing the layout (details) of the menu screen. In the purchase order printing (shipping place) 503, unlike the order form printing (supplier) 502, the setting for displaying the shipping place, the purchase price, and the order amount on the list / detail screen is not performed.

  The procedure for registering the menu screen has been described above.

  This completes the preliminary preparation.

  Next, an operation flow of a business partner that actually uses the Web-EDI system will be described.

  FIG. 14 is a flowchart showing the flow of processing in the Web-EDI server in this embodiment.

  An operator of a supplier company (a supplier company and a re-supplier company) accesses the Web-EDI system via the Web browser of the client terminal. Then, the user name and password are input from the login screen shown in FIG. 16, and login processing is performed on the Web-EDI server.

  In step 1401, the Web-EDI server performs authentication using the input user name and password. Then, the company information / department information of the user is specified from the user name. Various tables are registered in the Web-EDI server, and examples of the various tables are shown in FIGS. Each table is related to each table as a relational database. This table includes ordering data.

  In step 1402, the Web-EDI server transmits screen information for displaying the top menu shown in FIG. 19 in the Web browser of the client terminal.

In step 1403, the Web-EDI server determines whether the “work menu display” button 1901 or the “up / down menu” button 1901 has been selected. If the “work menu display” button 1901 is selected, the process proceeds to step 1404, and if the “up / down menu” button 1901 is selected, the process proceeds to step 1406.

  In step 1404, the Web-EDI server transmits screen information for displaying the business menu screen in the Web browser of the client terminal. Specifically, screen data for displaying necessary button items is generated according to the group management number in the business management information table. Note that the screen data to be generated differs depending on the type of login user. FIG. 20 shows an example of a screen when the logged-in user is a supplier company, and FIG. 25 shows an example of a screen when the login user is a supplier company. There is a “print invoice” button in FIG. 20, but not in FIG. This is a necessary item for the supplier company, but is an unnecessary item for the re-supplier company, and is created separately when the business menu is designed.

  In step 1405, the Web-EDI server performs screen transition and form output processing according to the definition. Here, a case will be described as an example where the “print order form” button, which is commonly present on the business menu screen, is pressed. Details of this processing will be described with reference to FIG.

  In step 1501, the Web-EDI server determines whether the login user is a supplier company. If YES, the process proceeds to step 1502, and if NO, the process proceeds to step 1505.

  In step 1502, the Web-EDI server generates and transmits a screen for displaying the supplier search screen in the Web browser of the client terminal. FIG. 21 shows an example of a search screen. Here, a case where “warehouse 31” is searched in the shipping location 2101 will be described. After the search condition is input by the user, the Web-EDI server acquires a data record based on the input search condition and supplier code (company code). In the case of a supplier company, “shipment location” is set to be displayed as the heading of the list screen, so that the shipping location can be searched.

  In step 1503, the Web-EDI server generates and transmits a screen for displaying a supplier screen on the Web browser of the client terminal. FIG. 22 shows an example of a list screen. Since the search is performed in “warehouse 31”, “warehouse 31” is displayed in the shipping location 2201 as a search result. In the case of a supplier company, it is displayed because “shipment location” is set as a heading on the list screen.

  When the detail button 2202 is pressed, the Web-EDI server generates and transmits a screen for displaying a supplier screen on the Web browser of the client terminal. FIG. 23 shows an example of a detail screen. “Warehouse 31” is displayed in the shipping location 2301. In addition, a purchase price / order amount is displayed in 2302. This is because, in the case of a supplier company, the “purchase price” and “order amount” are displayed on the detail screen.

  In step 1504, the Web-EDI server generates a PDF file and transmits it to the client terminal. Specifically, a PDF file is generated by pressing a “print order form” button 2303. FIG. 24 shows an example of a PDF file. The numerical value 2302 and other values are used, and “unit price”, “amount”, and “shipping cost” are input to 2401 and 2402.

  The case of a supplier company has been described above.

  Next, a case where it is not a supplier company will be described. In this embodiment, it becomes a re-purchasing company. Note that the processing in the Web-EDI server in steps 1505 to 1507 is the same, and the description thereof is omitted. The difference is that the settings of the display screen are different, and the items that can be selected and the headings that are displayed are different.

  For example, FIG. 26 shows an example of a search screen, but “shipment location” cannot be selected here. This is because when there are a plurality of re-supplier companies, one re-supplier company cannot search for another re-supplier company. “Shipment location” is an item that should be displayed only to the supplier company, and thus the item is excluded.

  Therefore, the “shipping location” is not displayed on the screens shown in FIGS. Also, the purchase price and the order amount are not displayed because they are not required to be displayed. Accordingly, the generated PDF files 2901 and 2902 are blank.

  This is the end of the description of FIG.

Next, in Step 1406, the Web-EDI server transmits screen information for displaying the up / down menu screen in the Web browser of the client terminal. Specifically, the necessary button items are displayed in accordance with the group management number of the up / down screen table. In step 1407, when the CSV download is selected, the Web-EDI server displays the generated CSV file on the client terminal. Forward to.

  As described above, according to the present invention, in the Web-EDI system, when different users refer to the same data, it is possible to change display items for each user.

  It should be noted that the configuration and contents of the various data described above are not limited to this, and it goes without saying that the various data and configurations are configured according to the application and purpose.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

101 Web-EDI server 102 Client terminal 103 Network

Claims (5)

An information processing apparatus for ordering products via a network,
Layout setting means for setting a screen layout that can be referred to according to the type of user;
User information registration means for registering a plurality of user information together with information for identifying a user;
Accepting means for accepting a login request from a client terminal;
User identifying means for identifying the type of the user from user information registered by the user information registering means, using information for identifying a user included in the login request received by the accepting means;
A screen that can be displayed on the client terminal using the screen layout registered by the layout registration unit corresponding to the type of the user and the ordering data according to the type of user specified by the specifying unit Generating means for generating data;
An information processing apparatus comprising: a transmission unit that transmits the screen data generated by the generation unit.   The information processing apparatus according to claim 1, wherein items that can be referred to in the screen layout differ depending on a type of user. A control method in an information processing apparatus for ordering goods via a network,
A layout setting step for setting a screen layout that can be referred to according to the type of user;
A user information registration step of registering a plurality of user information together with information for identifying a user;
An accepting step for accepting a login request from a client terminal;
A user specifying step for specifying the type of the user from the user information registered by the user information registration step using information for identifying the user included in the login request received by the receiving step;
A screen that can be displayed on the client terminal by using the screen layout registered by the layout registration step corresponding to the type of the user and the ordering data according to the type of user specified by the specifying step A generation step for generating data;
And a transmitting step of transmitting the screen data generated by the generating step. A program that can be executed in an information processing apparatus that orders and orders goods via a network,
Layout setting means for setting a screen layout that can be referred to according to the type of user,
User information registration means for registering a plurality of user information together with information for identifying a user;
Accepting means for accepting login requests from client terminals,
User identifying means for identifying the type of the user from the user information registered by the user information registering means, using information for identifying the user included in the login request accepted by the accepting means;
A screen that can be displayed on the client terminal using the screen layout registered by the layout registration unit corresponding to the type of the user and the ordering data according to the type of user specified by the specifying unit Generating means for generating data,
A program comprising: causing the information processing apparatus to function as a transmission unit that transmits screen data generated by the generation unit.   The recording medium which recorded the program of Claim 4 so that computer reading was possible.

Images