KR101855251B1 - Client program of erp system - Google Patents

Abstract

A client program of an enterprise resource management system is disclosed. This client program is a client program that interacts with an enterprise resource management system including a database and an ERP operation unit. The client program is a client program that stores a SQL ID, a SQL type, a SQL description, and an SQL content in the form of text for requesting one or more data stored in a database A SQL input module for setting the SQL information to be included, a control attribute including a control ID, a type, a position, a default value, and a text attribute field on the screen in order to set one or more controls for inputting a query condition value for SQL information A text box for inputting a grid model ID and a model name on the screen, a grid group for inputting a grid name, And a radio button for setting the movement attribute of the column, A grid setting module for displaying an attribute input window for setting attributes for each order, type, width, and sort for each model, and one independent setting module corresponding to SQL information, set control and grid setting values And a program registration module for registering the generated setting module as an additional business module in the pre-registered business module, wherein at least one of the grid forms is set as a pop-up form, And registers the setting module as a business module for conducting a business process.

Description

Client program of enterprise resource management system {CLIENT PROGRAM OF ERP SYSTEM}

The present invention relates to an enterprise resource management system, and more particularly, to an enterprise resource management system in which an end user who is not a system developer but has no expert knowledge performs customizing and adding a business process to a business screen provided by a system To a client program of an enterprise resource management system.

In accordance with the rapid development of information technology (IT), it is applied to the overall management of the enterprise to manage the business efficiently, while minimizing the human error by the practitioners, . Among these attempts, a typical information technology solution is an enterprise resource planning (EPR) system.

The above-mentioned ERP system is a solution that enables business-related activities to be combined with information technology in all areas of the company. It is a system that integrates information on all business related to the company's business, It is a system that enables quick decision making. Through this, companies can integrate and manage the whole business of the company such as personnel, sales, purchasing, sales, outsourcing, accounting, logistics and production in real time, so that man and material resources can be managed in optimal condition do.

At present, by introducing an ERP system, companies integrate and integrate key business processes to maximize company-wide efficiency and increase the trust of companies. The introduction of ERP system is usually performed through ERP consulting between ERP consultant and practitioners in each field of the company, and after the introduction, the process of revising and supplementing is continuously carried out to suit the company.

However, the business environment of the modern enterprise is continuously changing, and the business process of the enterprise to adapt to this environmental change is also changing from time to time. Therefore, in order to cope with changes in corporate goals and organizational structure, ERP systems need to be continuously supplemented and reconfigured after introduction.

The supplementing or reconfiguring of the existing ERP system has usually been carried out by the developers belonging to the ERP system builder, but it is difficult to accurately reflect the opinion of each practitioner of the enterprise, that is, the end user.

In order to overcome this limitation, as disclosed in Korean Patent No. 10-1052742 and the like, a solution such as a screen registration wizard is provided so that a user can edit the ERP user screen and the like on his / . However, the conventional methods disclosed in the prior arts merely constitute only a screen by combining modules already built in the ERP system, making it impossible to add new data in accordance with changed business processes. The data must be directly added through the terminal in which the environment is established.

That is, the complement of the existing ERP system is to change only the portion displayed on the screen when the user sets up the user environment and performs the task, and it is possible to process new data that does not exist in the existing system, There is a limitation that it is impossible to perform operations such as modification, modification, and renewal of the part for the user.

FIG. 1 is a diagram schematically illustrating a process of introducing an ERP system in a general enterprise.

Referring to FIG. 1, a company that intends to introduce an ERP system has a process of defining and operating a company's business through a contract with an external professional SI company, , A designing step S11, a building step S12, an implementing step S13, and an introducing step S14.

In the analysis step (S10), the company analyzes and grasps the tasks performed by the current business, and in the design step (S11), the business processes and the program modules that perform the tasks are defined based on the analysis results. In the building step (S12), the actual developers build the database and the ERP system. In the implementation step S13, the ERP system built by the practitioner of the company, that is, the end user, is tested and operated to perform problems such as problem diagnosis, supplementation and improvement. When the test is completed, the actual enterprise applies the ERP system to the business as the introduction step (S14).

In the process of introducing the ERP described above, in most cases, the developers terminate the project after completing the correction of the problems found in the implementation step (S13). In the introduction step (S14), the exceptional fatal error It is a common practice to perform only maintenance work on the product. As a result, in the introduction step (S14), it is difficult to re-execute work such as addition or change of the already defined business process, and a considerable additional cost is incurred when the developer is input again.

Therefore, the conventional ERP system has a disadvantage that it is difficult to actively cope with rapidly changing corporate environment.

The present invention has been devised to overcome the above-mentioned limitations, and it is an object of the present invention to provide an enterprise resource management system and a method of operating the enterprise resource management system that can apply a new business process through an end user terminal The purpose is to do.

It is another object of the present invention to allow a final user to utilize a new screen and desired data using a menu that is simply provided.

Another object of the present invention is to easily create and use a business screen on a user terminal without modifying the source level.

It is another object of the present invention to reduce unnecessary costs in setting a screen in a short period of time in response to a new project construction or an additional screen request of an existing customer.

In order to solve the above-mentioned problems, a client program of an enterprise resource management system according to a preferred embodiment of the present invention is a client program linked to an enterprise resource management system including a database and an ERP operating unit, An SQL input module for setting SQL information including a SQL ID, an SQL type, an SQL description, and SQL content in the form of a text for requesting the SQL query module to set one or more controls for inputting a query condition value for SQL information, A query condition setting module for displaying an attribute input window for setting a control attribute including control ID, type, position, default value, and text attribute field on the screen, a grid setting value for displaying grid form when receiving data To receive the input, enter the grid model ID and model name on the screen. A grid setting module for displaying an attribute input window for setting properties for each order, type, width, and sort by grid model, radio buttons for setting a movement attribute of a text box, a grid group and a column, And a program registration module for creating one independent setting module corresponding to the SQL information, the set control and the grid setting value, and registering the generated setting module in the already registered business module as an additional business module, At least one of which is set in a pop-up form, and the program registration module may be registered as a business module for requesting the ERP operating unit to conduct a business process for the setting module.

In addition, SQL information can be input in text form.

The SQL information may also include SQL identifiers and SQL code.

The control may also include at least one of a combo box, a text box, a pop-up form, a date box, a number box, and a radio button.

The enterprise resource management system according to the embodiment of the present invention has an effect that the end user can directly reflect the changed business process through the user terminal and the screen can be produced according to the needs without coding the source code level.

In addition, the present invention has an effect that a system developer or a user can utilize a new screen and desired data by using a menu that is simply provided.

In addition, according to the present invention, it is possible to modify and reuse SQL (Structured Query Language), a query condition, and an inquiry model defined in each screen, The development time of the screen can be shortened.

In addition, the present invention has the effect of reducing unnecessary costs in developing a screen in a short period of time for a new project construction or an additional screen request of an existing customer.

FIG. 1 is a diagram schematically illustrating a process of introducing an ERP system in a general enterprise.
FIG. 2 is a diagram illustrating an overall structure of an enterprise resource management system according to an embodiment of the present invention.
3 is a diagram illustrating a structure of a client program of an enterprise resource management system according to an embodiment of the present invention and a connection relationship therebetween.
4 is a diagram illustrating a method of operating a client program of an enterprise resource management system according to an embodiment of the present invention.
5A to 5D are views showing an example of a setup screen provided by the client program of the enterprise resource management system according to the embodiment of the present invention.

Prior to the description, when an element is referred to as being "comprising" or "including" an element throughout the specification, it is to be understood that the element may be further comprised of other elements . Also, terms such as " Unit ... ", "Module, " and " Component " refer to units that process at least one function or operation, , A combination of hardware and software.

Furthermore, the term "embodiment" is used herein to mean serving as an example, instance, or illustration, but the subject matter of the invention is not limited by such example. It is also to be understood that the terms "including, "" having, "and other similar terms are used, but that they do not exclude any additional or different components when used in the claims, Quot; is < / RTI > used in a manner similar to the term " Comprising ".

The various techniques described herein may be implemented with hardware or software, or may be implemented with a combination of both, where appropriate. As used herein, terms such as "Unit," "Module," "System," and the like are likewise equally applicable to computer-related entities, It can be handled as equivalent to the software at the time of execution. For example, a program module may be composed of one component or a combination of two or more components. Further, in the present invention, both the application and hardware executed in the server or the terminal can be configured on a module basis, and can be recorded in one physical memory, or distributed among two or more memories and recording media.

Hereinafter, an enterprise resource management system and a method of driving the same according to a preferred embodiment of the present invention will be described with reference to the drawings.

FIG. 2 is a diagram illustrating an overall structure of an enterprise resource management system according to an embodiment of the present invention.

Referring to FIG. 2, the enterprise resource planning (ERP) system of the present invention includes a client program 110 for changing a work screen according to a user's intention and generating a user-defined module for a new business process, An ERP operation unit 210 for performing a business process of an enterprise in response to a request of the user terminal 100 and an ERP 210 including a database 220 for storing various data required when a business process is performed, And a server 200.

In detail, the user terminal 100 is a computing device in which a normal OS (Operating System) is allocated to the employees of the company, that is, the end users are assigned to the ERP server 200 through the information communication network. And inquires the data to proceed with the business process.

Particularly, in the embodiment of the present invention, the user terminal 100 is installed in the client program 110 interlocked with the ERP server 200, and not only performs data transmission / reception with the ERP server 200, And can set and register a new business process necessary for the business process.

Specifically, the client program 110 directly sets a SQL (Structured Query Language) for requesting stored data for a database, and selects an input value using a GUI such as a combo box, a text box, and a radio box And the like. The user can select one or more of the items provided by the modules and set a data inquiry method according to his / her task. The client program 110 automatically generates a screen related to the inquiry method set, And requests additional registration to the business process defined in the ERP operation unit 210.

The ERP server 200 performs a business process for a task requested from each user terminal 100 through an information communication network and provides the result to the user terminal 100. The ERP server 200 may be divided into an ERP operating unit 210 configured to include a plurality of business modules according to functions thereof and a database 220 configured to store task related data in a database , And may further include functions of a separate web server and application server (not shown) according to the designer's intention.

The ERP server 200 includes a high-performance microprocessor and a large-capacity physical storage space so as to process various work requests in real time without delay in cooperation with the client programs 110 installed in a plurality of user terminals 100 desirable.

In particular, the above-described ERP operating unit 210 may be configured with a plurality of modules for processing a process according to the enterprise service. As an example, the ERP operating unit 210 may include an accounting module, a logistics module, a personnel module, a purchase module, an order processing module, and a production module. The accounting module handles the process of accounting related to the money, such as revenue and expenses that occur within the enterprise. The logistics module handles logistics related business processes such as goods receipt, goods issue, transportation, and inventory warehouse management. The HR module maintains a database of productivity and skills related to HR, such as attendance, salary and bonuses, recruitment, training related training, assessment and career planning. The purchasing module handles the processes required in planning the material requirements that are directly required for product production. The order processing module processes a series of processes such as ordering by the customer, purchase decision and dispatch. The production module processes the business processes such as material requirements planning, production site, outsourcing management, product management, LOT management and on-site control.

In addition, the ERP server 200 may include a program application module 215 that reflects a setting module created by the user terminal 100 as a program as a program to the modules, The new module is reflected in the module related to the new module.

According to the above-described configuration, in the enterprise resource management system according to the present invention, the end user can easily supplement the currently implemented ERP system and add a new business process without having expertise related to programming like a system developer. The detailed configuration of the client program 110 will be described later.

Therefore, the enterprise resource management system including the client program 110 of the present invention can be implemented not only in the system building step (S13 in FIG. 1) but also in the end users And it is possible to add work processes required for changes in the business environment directly by practitioners.

Hereinafter, a structure of a client program installed in a user terminal in an enterprise resource management system according to an embodiment of the present invention will be described with reference to the drawings.

3 is a diagram illustrating a structure of a client program of an enterprise resource management system according to an embodiment of the present invention and a connection relationship therebetween.

3, the client program 110 of the enterprise resource management system of the present invention is a client program linked with an ERP system including a database 220 and an ERP operating unit 210, A SQL input module 111 for receiving SQL information including an instruction for requesting one or more data, a query condition setting module 112 for setting one or more control attributes for inputting a query condition value for SQL information, A grid setting module 113 for receiving a grid setting value for displaying the grid setting data on the screen when receiving data, and an independent setting module corresponding to the SQL setting, control, and grid setting values, And a program registration module (114) for registering the setting module in the ERP operating unit.

The SQL input module 111 receives a query command for requesting one or more business-related data stored in the database from a user in the course of a predetermined business process. Since the normal DBMS performs input and output of data through SQL according to a specific grammar, the SQL input module 111 provides a registration setting screen to provide SQL ID, SQL type, SQL description, and SQL The contents are input in text form and SQL information is generated. It is desirable for the end user to take advantage of the initial values of the pre-written SQL. SQL statements can be used to create tables and add fields.

The inquiry condition setting module 112 sets the control for receiving the inquiry condition value for requesting the actual data by substituting into the SQL information. Here, the query condition value is a value such as an input parameter for the SQL information, and the user terminal needs one or more control to input the query condition value. Accordingly, the query condition setting module 112 sets an attribute defining a position, a width, and an input type on a screen of a control for querying a query condition value at the time of data inquiry, and when the query is initially called, And so on.

 That is, the inquiry condition setting module 112 sets the design of the input part of the inquiry condition value in the inquiry screen provided to the user terminal. For this, the inquiry condition setting module 112 may include a combo box, a pop-up form, a date box, a number box, a check box (not shown), a text box Check button) and a radio button (Radio button).

The grid setting module 113 plays a role of receiving a record and a field attribute of a model in which the inquired data is to be displayed on the screen, that is, a grid (Grid). Each data retrieved in the ERP system is generally displayed in a grid form, and the grid configuration module 113 receives a grid configuration value for setting the display mode of data in the data retrieval screen. As an example, the input set value maps the fields of the records of the SELECT clause of the SQL statement included in the SQL information and reflects the attributes of each field. The GUI provided by the grid setting module 113 includes a text box, a numeric box, a date box, and a check box.

In particular, in the inquiry result screen, the grid is divided into a plurality of groups so that each grid can be divided into two window forms on one screen, and some of them are not included in one window form but in a separate pop-up form . ≪ / RTI > The user can set these attributes through the grid setting module 113. [ Here, the window form in the inquiry result screen displayed on the user terminal may be configured in XML format.

The program registration module 114 creates one independent configuration module corresponding to the SQL information, the inquiry condition value, and the grid setting value input through the above-described modules and registers it in the ERP operation unit 210 . The program registration module 215 of the ERP operation unit 210 requests registration of the received setting module to the task processing module 211 and is used to process a business process like a predetermined task module. Since the registered configuration module includes SQL information, the registered configuration module can access the database 220 in the same manner as other business modules at the time of execution, and can receive the same authority as other business modules.

Accordingly, the user can perform a task in a work environment set by the user by calling a setting module created at the time of task execution, and can add a new work process in association with the task processing modules previously defined in the ERP server .

Hereinafter, a method of operating a client program of an enterprise resource management system according to an embodiment of the present invention will be described with reference to the drawings.

FIG. 4 is a diagram illustrating a method of operating a client program of an enterprise resource management system according to an embodiment of the present invention. FIGS. 5A to 5D are diagrams illustrating a configuration of a client program of an enterprise resource management system according to an exemplary embodiment of the present invention. And Fig.

4, when an end user belonging to an enterprise drives a client program through his / her user terminal and executes a task addition function, The client program displays a registration setting screen for editing on the screen of the user terminal (S100).

4 and 5A, the SQL registration module provides the registration setting screen 300 to receive SQL information from the user (S110). At this time, the previously created SQL example can be displayed in the text box on the registration setting screen 300, and the user can set the SQL information in a form of modifying the corresponding SQL.

As shown in FIG. 5A, the registration setting screen 300 for registering SQL information includes UI boxes 310 to 340 for receiving SQL ID, SQL type, SQL description, and SQL contents. In the SQL ID input box 310, an identifier for distinguishing a plurality of SQLs registered by the user can be input in a text form, and the SQL type box 320 can select and set a predefined SQL type in a list box form have. In addition, the SQL description box 330 may describe a description of SQL that the user wants to register.

In the SQL content box 340, the basic SQL syntax is described in a text form in the text box. The user can modify the basic SQL syntax and add a function of generating a table necessary for business or retrieving data have.

When the input of the SQL information is completed, as shown in FIGS. 4 and 5B, the query condition module displays a plurality of GUI controls on the registration setting screen and registers one or more controls for receiving a query condition value from the user ( S120).

The registration setting screen 400 related to the registration of the control of the inquiry condition value may include a text box 410 for receiving a model ID and a model name and includes an attribute input window 420 for setting attributes of one or more controls can do. The fields of the control property input window 420 include a control ID, a type, a location property, a default property, a text property, and the like. In the data inquiry screen, do.

4 and 5C, the grid setting module switches to a screen for receiving a grid setting value for displaying the inquired data. At this time, the user can set a plurality of grids or set them to be displayed in a pop-up form on the inquiry result screen (S130).

In the grid setting step S130, the registration setting screen 500 includes a text box 510 for receiving a grid model ID and a model name, a radio button 520 for setting a movement attribute of a group and a column ). In addition, it may include an attribute input window 530 that can set attributes for each order, type, width, alignment, and the like, by the grid model ID. The user can customize the screen environment by changing the field value of the attribute input window 530 and the grid is displayed in one or more forms in the query result screen.

Further, the registration setting screen 500 may further include a setting window 540 for changing the color of each row of data and the display order of the fields in the inquiry result screen.

4 and 5D, the program registration module collects the SQL information, the inquiry condition, and the grid setting value input by each setting module on the registration setting screen to generate a setting module for the user, and the ERP The server is requested to register (S140).

5D shows an example of the registration setting screen 600 provided by the program registration module in the program registration step of the setting module. The user sets the setting through the type of setting module, the menu attribute, and the popup selection box 610 In particular, the registration setting screen 600 includes a type of grid displayed on the inquiry result screen at the time of execution of the setting module, a menu ID, a control for inputting a query condition, a corresponding SQL ID, And a setting window 620 for setting properties of the master model, the master-detail model, the size and the sorting method for the Detail model, and the like.

In addition, the registration setting screen 600 may further include a user-defined number format window 630 for setting the number of digits for the numbers displayed upon data inquiry.

Accordingly, the user can set a proper working environment for his / her work with respect to the inquiry and result screen through the setting window provided by the client program, and can add a new business process as the program is modularized and registered in the EPR system.

While a great many are described in the foregoing description, it should be construed as an example of preferred embodiments rather than limiting the scope of the invention. Accordingly, the invention is not to be determined by the embodiments described, but should be determined by equivalents to the claims and the appended claims.

110: client program 110: SQL registration module
112: Condition setting module 113: Grid setting module
114: Program setting module 210: ERP operating section
211: business processing module 215: program registration module
220: Database

Claims (4)

A client program interworking with an enterprise resource management system including a database and an ERP operation unit,
On computer
An SQL input module for setting SQL information including a SQL ID, an SQL type, an SQL description, and SQL content, which is a text form for requesting one or more data stored in the database;
An attribute input window for setting a control attribute including a control ID, a type, a position, a default value, and a text attribute field on the screen is displayed to set one or more controls for inputting a query condition value for the SQL information A query condition setting module;
A radio button for setting a grid model ID and a text box for inputting a model name, a grid group, and a movement attribute of a column on the screen to receive a grid setting value for displaying the grid form when the data is received, A grid setting module for displaying an attribute input window for setting attributes for each order, type, width, and sort of the grid models; And
And a program registration module for creating one independent configuration module corresponding to the SQL information, a set control and a grid setting value, and registering the generated configuration module in an already registered business module as an additional business module,
The grid foams may be,
At least one of which is set in a pop-up form,
Wherein the program registration module comprises:
Wherein the setting module is registered as a business module for requesting the ERP operating unit to proceed with the business process of the setting module. The method according to claim 1,
The SQL information includes:
Wherein the client program is input in a text format. 4. The method according to any one of claims 1 and 2,
The SQL information includes:
A computer-readable recording medium recording a client program of an enterprise resource management system including an SQL identifier and an SQL code. The method according to claim 1,
The above-
Wherein the client program includes at least one of a combo box, a text box, a pop-up form, a date box, a number box, and a radio button.

Images