WO2018097407A1 - Method and system for sharing user-defined erp functions - Google Patents

Abstract

Disclosed are a method and a system for enabling a user, such as a company, using enterprise resource planning (ERP) software to easily share with others user-defined ERP functions adequate for a work process of the user that the user has personally developed. According to one aspect of the present invention, provided is a method for sharing user-defined ERP functions, the method comprising the steps in which: a user-defined ERP function sharing system receives, from a plurality of sharing-party terminals, source packages including at least one structured query language (SQL) file and a design file, and corresponding to predetermined user-defined ERP functions, wherein the SQL file is a file for storing SQL queries for operating a database, and the design file is a file for storing information on the properties of at least one control constituting a screen for user-defined ERP functions, wherein at least some of the controls constituting the screen for user-defined ERP functions are controls that are mapped to specific queries included in the at least one SQL file; the user-defined ERP function sharing system stores, in a predetermined repository, the source packages received from the plurality of sharing-party terminals; the user-defined ERP function sharing system provides, to a user terminal, a list of the source packages stored in the repository; and, as a response to a download request from the user terminal, a source package, among the source packages stored in the repository, that is selected by the user terminal is transmitted to the user terminal.

Description

Custom ERP function sharing method and system

The present invention relates to a user-defined ERP function sharing method and system. More specifically, the present invention relates to a method and a system that enables a user, such as an enterprise, to easily share a custom ERP function suitable for his or her own business process with others.

Enterprise Resource Planning is a computer system for enterprise management and management or packaged software installed in such systems. Representative companies dealing with ERP are SAP, Oracle, etc. Can be mentioned. Meanwhile, in order for an enterprise to be provided with an ERP service, not only ERP software should be installed in a user terminal in the enterprise, but also a database for storing various information of the corresponding enterprise must be established.

The ERP system enables companies to efficiently manage accounting, personnel, payroll, sales, trade, purchasing, materials, production, outsourcing, services, and management information. In addition, companies can maximize productivity by introducing ERP system and reducing inefficiency caused by different information systems between management departments. In addition, ERP can provide the advantage of systematically identifying and managing a variety of corporate information.

Each company has its own business processes and different corporate management strategies, so the ERP software needs to be customized to suit the characteristics, business processes, and workflows of the enterprise, unlike typical packaged software. In the past, in order to build a customized ERP system for several companies, each company had to analyze the requirements and business processes of each company and develop customized ERP software to be applied to the company. It took a lot of time and money to build an ERP system. In addition, due to the high cost, it is very difficult for a small company to adopt an ERP system.

The technical problem to be solved by the present invention is to provide an integrated development environment that enables the integrated development of database modeling, SQL query and UI for manipulating the database, through which ERP individual functions can be easily customized for the enterprise It is intended to provide a method and system that allows users to easily create and share their own ERP functions with others.

According to an aspect of the present invention, a user-defined enterprise resource planning (ERP) function (method) sharing method, the user-defined ERP function sharing system, including at least one SQL file and a design file from a plurality of sharer terminal, Receiving a source package corresponding to an ERP user-defined function-The SQL file is a file that stores a structured query language (SQL) query for manipulating a database, the design file constitutes the screen of the user-defined ERP function A file storing information on at least one property of at least one control, wherein at least some of the controls constituting the screen of the user-defined ERP function are controls mapped to a specific query included in the at least one SQL file; A source EW function received by the user-defined ERP function sharing system from the plurality of sharer terminals. Storing the information in a predetermined storage; providing, by the user-defined ERP function sharing system, a list of source packages stored in the storage to a user terminal; and in response to a download request of the user terminal, source packages stored in the storage. The user-defined ERP function sharing method comprising the step of transmitting the target source package selected by the user terminal to the user terminal is provided.

In an embodiment, the storing of the source packages received from the plurality of sharer terminals in a predetermined storage by the user defined ERP function sharing system may include a plurality of predefined user defined ERP functions corresponding to the source package. The method may include determining which of the categories belong to the category, and classifying the source package into a category to which the user-defined ERP function belongs, and storing the source package in the storage.

In an embodiment, the determining of a user-defined ERP function corresponding to the source package belongs to one of a plurality of predefined categories may include at least one SQL file included in the source package or a design included in the source package. The method may include analyzing a file and determining which of the plurality of categories a user-defined ERP function corresponding to the source package belongs to based on the analysis result.

In an embodiment, the user terminal performs a source package upload method and a source package download method, wherein the source package upload method includes selecting at least some items from a list of at least one source package stored in the user terminal. Providing a source package upload UI for providing and transmitting a source package corresponding to the selected item through the source package upload UI to the user-defined ERP function sharing system, The source package download method, the Receiving a list of source packages stored in the repository from a user-defined ERP function sharing system, providing a source package download UI providing a function of selecting at least some items from the received source package list, and the source package download UI Through It may include receiving a source package corresponding to the selected item from the user-defined function shared ERP system.

In one embodiment, the user terminal, after receiving the target source package from the user-defined ERP function sharing system, performs a user-defined ERP function generation method corresponding to the target source package, and corresponds to the target source package The user-defined ERP function generation method may include a UI object corresponding to an ERD file, a UI object corresponding to each of at least one SQL file included in the target source package, and a UI object corresponding to a design file included in the target source package. Providing a container UI comprising a; wherein the ERD file is a file for storing information modeling the attributes of the table and the relationship between each table stored in a database, the UI object corresponding to the ERD file is selected In this case, an ERD file editing function for editing the ERD file is provided. If a UI object corresponding to any one of the at least one SQL file is selected, providing a SQL file editing function for editing the SQL file corresponding to the selected UI object, UI object corresponding to the design file Is selected, providing a design file editing function for editing the design file and providing the user-defined ERP function based on the at least one SQL file and the design file. Can share method.

According to another aspect of the present invention, there is provided a computer program installed in a data processing apparatus and stored in a recording medium for performing the above-described method.

According to another aspect of the present invention, a user-defined ERP function sharing system comprising at least one processor, a memory for storing a computer program executed by the processor, wherein the computer program, when executed by the processor A user-defined ERP function sharing system is provided which allows a user-defined ERP function sharing system to perform the above-described user-defined ERP function sharing method.

According to an embodiment of the present invention, an integrated development environment for integrating database modeling, SQL query and UI for manipulating the database can be provided, and through this, an ERP individual function customized for an enterprise can be created. A method and system can be provided.

In addition, it can provide a method and system that allows users to easily share their own ERP functions with others.

BRIEF DESCRIPTION OF THE DRAWINGS In order to better understand the drawings cited in the detailed description of the invention, a brief description of each drawing is provided.

1A is a diagram illustrating an operating environment of a method for generating a user-defined ERP function according to an embodiment of the present invention.

1B is a block diagram schematically illustrating a configuration of a user terminal according to an embodiment of the present invention.

2 is a diagram briefly illustrating a process of generating a user-defined ERP function by the user terminal according to an embodiment of the present invention.

3 is a diagram illustrating an example of a UI of an integrated development environment provided by a user terminal according to an embodiment of the present invention.

4 is a diagram illustrating an example of a project window.

5 is a diagram illustrating an example of a database search window.

6 is a flowchart schematically illustrating a process of performing an ERD file editing function by a generation system according to an embodiment of the present invention.

7 is a diagram illustrating an example of an ERD file editing UI.

8 is a flowchart schematically illustrating a process of performing an SQL file editing function by a user terminal according to an embodiment of the present invention.

9 is a diagram illustrating an example of an SQL file editing UI.

10 is a flowchart schematically illustrating a process of performing a design file editing function by a user terminal according to an exemplary embodiment of the present invention.

11 is a diagram illustrating an example of a design file editing UI.

12 is a diagram illustrating an example of a toolbox window.

13 is a diagram illustrating an example of an attribute window.

14 is a diagram illustrating an example of a script window.

15A to 15E illustrate an example of the SQL mapping UI.

16 is a flowchart schematically illustrating a mapping process between SQL and a control.

17 is a diagram illustrating an example of a process in which a user-defined ERP function is shared by a user-defined ERP function sharing system and a user terminal according to an embodiment of the present invention.

18 is a diagram illustrating an example of a source package upload UI.

19 is a diagram illustrating an example of a source package download UI.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all transformations, equivalents, and substitutes included in the spirit and scope of the present invention. In the following description of the present invention, if it is determined that the detailed description of the related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted.

Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise.

In this specification, terms such as "comprise" or "have" are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described in the specification, one or more other It is to be understood that the present invention does not exclude the possibility of the presence or the addition of features, numbers, steps, operations, components, parts, or a combination thereof.

In addition, in the present specification, when one component 'transmits' data to another component, the component may directly transmit the data to the other component, or through at least one other component. Means that the data may be transmitted to the other component. On the contrary, when one component 'directly transmits' data to another component, it means that the data is transmitted from the component to the other component without passing through the other component.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. Like reference numerals in the drawings denote like elements.

1A is a diagram illustrating an operating environment of a method for generating a user-defined ERP function according to an embodiment of the present invention. Referring to FIG. 1A, a plurality of user terminals 100-1 to 100 -N and a user-defined ERP function sharing system 200 (hereinafter, referred to as a 'sharing system') are connected through a wired / wireless network to thereby provide an embodiment of the invention. A method of generating a user-defined ERP function according to an embodiment may be performed. The plurality of user terminals 100-1 to 100 -N may share a source package corresponding to an ERP user-defined function through the sharing system 200.

For example, each user terminal 100-1 to 100 -N may generate a source package corresponding to a user-defined ERP function, and upload it to the sharing system 200 to share it with others. Hereinafter, a user terminal uploading a source package will be referred to as a sharer terminal.

The uploaded source package may be stored in a given repository 210. The storage 210 may be a device for storing a source package uploaded to the sharing system 200. The storage 210 may be a database or a memory device. The storage 210 may be an element included in the sharing system 200, but is not limited thereto. As illustrated in FIG. 1A, the storage 210 may be a physical device separate from the sharing system 200.

Meanwhile, each of the user terminals 100-1 to 100 -N may download some of a plurality of source packages stored in the storage 210 of the sharing system 200.

The user terminal 100 may be a handheld device such as a mobile phone, a satellite phone, a wireless phone, a Session Initiation Protocol (SIP), a Wireless Local Loop (WLL) station, a smartphone, a tablet PC, a personal digital assistant (PDA), or a desk. It can include a tower or laptop.

The sharing system 200 may include hardware resources and / or software necessary to implement the technical idea of the present invention, and does not necessarily mean one physical component or one device. . That is, the sharing system 200 may mean a logical combination of hardware and / or software provided to implement the technical idea of the present invention. If necessary, the sharing system 200 may be installed in devices spaced apart from each other to perform respective functions. As a result, it may be implemented as a set of logical configurations for implementing the technical idea of the present invention. In addition, the sharing system 200 may refer to a set of components separately implemented for each function or role for implementing the technical idea of the present invention.

The sharing system 200 may be implemented in the form of a plurality of modules. For example, the sharing system 200 performs at least one communication module capable of communicating with various user terminals 100-1 through 100 -N or a main function of the sharing system 200 through a network, and It may include a control module capable of controlling and functioning the functions and / or resources of other components included in the sharing system 200, a storage module for storing various information, an input / output module for interfacing with a user, and the like. Various modules included in the sharing system 200 may be located in different physical devices or may be located in the same physical device.

In the present specification, the module may mean a functional and structural combination of hardware for performing the technical idea of the present invention and software for driving the hardware. For example, the module may mean a logical unit of a predetermined code and a hardware resource for performing the predetermined code, and means a physically connected code or does not necessarily mean one kind of hardware. It can be easily inferred by the average expert in the art.

1B is a block diagram schematically illustrating a configuration of a user terminal 100 according to an exemplary embodiment of the present invention. Referring to FIG. 1B, the user terminal 100 may include a user-defined ERP function generation module 110. A 'generation module'), the user-defined ERP function driving module 120 (hereinafter referred to as a 'drive module'), and a user-defined ERP function sharing module 140 (hereinafter referred to as a 'shared module'). have.

In some cases, the user terminal 100 may further include a DB 130 for storing various data necessary for implementing the technical idea of the present invention and various information of the company.

FIG. 1B illustrates an example in which the DB 130 is included in the user terminal 100, but in another embodiment, the DB 130 is physically separated from the user terminal 100. It may be implemented in the form of a system. In this case, the user terminal 100 and the DB 130 may be connected through a network to transmit and receive various data or information. In addition, according to an implementation example, the user terminal 100 may operate in conjunction with a plurality of DBs included in the user terminal 100 or connected through a network.

In the present specification, DB (DataBase) may be implemented as at least one table, and used as a meaning including a separate DBMS (Database Management System) for searching, storing, and managing information stored in the DB. It may be. In addition, it may be implemented in various ways such as a linked-list, a tree, a relational DB, and includes all data storage media and data structures capable of storing information to be stored in the DB 130. It can be used to mean.

The generation module 110 may perform a function of generating a user-defined ERP function or editing a previously generated user-defined ERP function. The driving module 120 may drive the user-defined ERP function generated by the generation module 110 to provide the user-defined ERP function. The sharing module 140 may upload the user-defined ERP function generated by the generation module 110 to the sharing system 200 and share it to others, and share the user-defined ERP function shared by others. Download from system 200.

The generation module 110, the driving module 120, and the sharing module 140 may be implemented in the form of independent physical devices. Alternatively, the modules 110, 120, and 140 may be implemented as one physical device. In the latter case, the three modules 110, 120, and 140 may each be configured as separate software that is logically divided, or may be implemented in the form of one integrated software.

Hereinafter, for the convenience of understanding, a function of generating a user-defined ERP function according to the spirit of the present invention is performed by the generation module 110, and the function of driving the generated user-defined ERP function is the driving module 110. Although it is described that the user-defined ERP function sharing function is performed by the sharing module 140, according to the implementation example, unlike in Figure 1b, the user terminal 100 is in accordance with the spirit of the present invention. The user-defined ERP function generation function, the generated user-defined ERP function driving function, and the user-defined ERP function may be implemented as one system that performs a combination of the user-defined ERP function sharing function.

User-defined ERP functions can be integrated into an ERP system and can be unit functions with their own meaning. The user-defined ERP function may perform a function of managing, manipulating, using, and analyzing enterprise information stored in the DB 130. A customized user interface (UI) can be provided for the user to perform these functions. That is, the user may manage, manipulate, use, and analyze enterprise information stored in the DB 130 through a UI provided by a user-defined ERP function.

Examples of user-defined ERP functions include document entry, book management, account increase management, bond age analysis / management, settlement of accounts, financial statements, fund / budget management, budget / use analysis, fixed asset management, tax return management, financial account management, etc. , Personnel management, attendance management, payroll management, social insurance management, year-end settlement management, retirement settlement management, tax return management, income-specific slip processing, daily work management, domestic sales plan establishment / management, quotation / order processing, request / inspection management , Issue / return processing, sales contribution analysis, delivery / delivery management, temporary issue / consignment management, sales settlement, electronic tax invoice processing, collection / debt management, bond age analysis, export plan establishment / management, order management, issue processing, Sales Settlement, Shipment Management, Goods / Order Processing, Shipment / Receipt Management, Import Cost Processing, Non-Settlement Processing, Import Cost Allocation, MPS, Required Materials Calculation, Invoice / Order, Goods Receipt / Inspection, Temporary Goods Receipt Management, Purchase Settlement / Accounting, Payment / Debt Management, Inventory Management (LOT) , Production plan establishment / management, in-house production management, mixed process management, by-product / dismantle management, forestry production management, input order management, outsourcing production management, service reception / processing, service bond management, financial / profit analysis, profit / loss analysis , Major Fund Analysis, Logistics / Fish Summary Analysis, Sales Analysis by Characteristics, Seasonal / Quarterly Production Performance Analysis, T & A Analysis by Characteristics, Salary / Bonus Simulation, Contract Management, Field Management, Contract / Ready Management, Work Daily, Concession / Non-payment management, labor equipment management, deadline settlement management, labor report management, external periodicity management, cost income management, etc., but there are various functions as well.

As shown in FIG. 1B, the user terminal 100 may be connected to the sharing system 200 through a network to transmit and receive various information, data, signals, and / or messages necessary to implement the technical idea of the present invention. have.

The user terminal 100 may transmit a result generated through a user-defined ERP function generation function to the sharing system 200, and the sharing system 200 may provide (transmit) it if desired by other users. . That is, the sharing system 200 may play a role of allowing each user to share a user-defined uploaded ERP function with other users.

The result generated by the ERP function generation function may include an ERP file, at least one SQL file, and a design file. In some embodiments, the result file may further include a report file.

The ERD file may be a file that stores information modeling the attributes of the tables stored in the DB 130 and the relationships between the tables.

An entity relationship diagram (ERD) is the most data-modeling technique that uses simple shapes (squares, ellipses, diamonds, etc.) to describe the structure and relationships of data, and to form relationships and properties between data entities. Most commonly used as a tool. Users can visually understand this easily by using ERD to graphically represent the relationship of the database. Components of an ERD include an entity, a relationship, and an attribute. An entity represents an object that is separated into the subject or object of information to be stored in the database. In database modeling, one table stored in the database may be an object. A relationship represents how two or more entities are related to each other. Attributes are data items that describe the characteristics of an entity or relationship. Attributes that uniquely identify each entity are called key attributes.

The SQL file may be a file that stores a structured query language (SQL) query for manipulating the DB 130. Each SQL file can store one or more SQL queries.

SQL is a special-purpose programming language designed to manage data in a database management system (DBMS). It is used to write queries to retrieve and manage data stored in a database, create and modify database schemas, and manage database object access coordination. Can be used. SQL commands can be classified into three categories: data manipulation (DML), data definition (DDL), and data control (DCL). Data manipulation (DML) is a command used to modify or retrieve data in a database, such as INSERT (add data), UPDATE (update data), DELETE (delete data), and SELECT (data search). Data definition (DDL) is a command used to modify the structure of a table or the like that contains data, such as CREATE (create a table, etc.), DROP (remove a table, etc.), ALTER (change a table, etc.). Data control (DCL) is a command that grants or revokes access to the database. It includes GRANT and REVOKE.

The design file may be a file that stores information about attributes of at least one control constituting the screen of the user-defined ERP function. Here, the control may be a UI object that can perform interaction with the user such as displaying information or receiving information from the user.

Meanwhile, at least some of the controls constituting the screen of the user-defined ERP function may be controls mapped to a specific query included in the at least one SQL file, which will be referred to as a grid control hereinafter.

The report file may include information about properties of a plurality of controls constituting a report electronic document and information about data bound to each control.

2 is a diagram briefly illustrating a process of generating a user-defined ERP function by the generation module 110 according to an embodiment of the present invention.

Referring to FIG. 2, the generation module 110 may provide a container UI including a UI object corresponding to an ERD file, a UI object corresponding to each of at least one SQL file, and a UI object corresponding to a design file. In operation S110, the user may select any one of the UI objects included in the container UI in operation S120.

When a UI object corresponding to the ERD file is selected, the generation module 110 may provide an ERD file editing function for editing the ERD file (S130).

When a UI object corresponding to the SQL file is selected, the generation module 110 may provide an SQL file editing function for editing the SQL file (S140).

When a UI object corresponding to the design file is selected, the generation module 110 may provide an ERD file editing function for editing the design file (S150).

On the other hand, the generation module 110 may provide an integrated development environment for the user to create and customize a user-defined ERP function. Using the provided integrated development environment, users can create or edit ERD files, SQL files, design files, and report files required to run custom ERP functions.

A user may generate a plurality of user-specified ERP functions through the generation module 110, in which case the plurality of user-specified ERP functions may be managed as a single project corresponding thereto. Each project can be a package or container that contains at least one SQL file and a design file.

Even if multiple projects exist, there may be one ERD file. In this case, a plurality of user-specified ERP functions generated by the plurality of projects may use one common ERD file.

Hereinafter, a method of creating / editing a custom ERP function through the integrated development environment will be described in detail.

3 is a diagram illustrating an example of a UI of an integrated development environment provided by the generation module 110.

Referring to FIG. 3, the integrated development environment UI 1000 includes a menu 1100, a project window 1200, a database search window 1300, an editor window 1400, a toolbox window 1500, and a property window 1600. ), May include a script window 1700.

The menu 1100 may include a plurality of icons, and each icon may be a UI object for executing a function frequently used by a user, including creating a new project, opening a file, saving a file, copying, and pasting.

The project window 1200 may be a container UI including a UI object (eg, an icon) corresponding to an ERD file, a UI object corresponding to each of at least one SQL file, and a UI object corresponding to a design file.

4 is a diagram illustrating an example of the project window 1200.

As shown in FIG. 4, in the project window 1200, a UI object 1211 corresponding to an ERD file may be displayed, and when a UI object 1211 corresponding to the ERD file is selected by a user ( For example, when a corresponding UI object is clicked, double-clicked, or touched), the generation module 110 may provide an ERD file editing function for editing the ERD file. The generation module 110 may display a UI for editing an ERD file in the editor window 1400 to provide an ERD file editing function, and the user may edit the ERD file on the UI displayed in the editor window 1400. Can be.

The UI object 1211 corresponding to the ERD file may be displayed at a lower level of the ERD container UI object 1210. The user may interact with the ERD container UI object 1210 in a predetermined manner to generate a new ERD file, and the UI object corresponding to the newly created ERD file may be added as a lower level of the ERD container UI object 1210. Can be. In this case, the newly generated ERD file may be a blank file including no information.

In the project window 1200, UI objects 1201, 1202, and 1203 corresponding to each of at least one project may be displayed, and each project may correspond to a different user-defined ERP function.

As described above, each project may be a container including at least one SQL file, a design file, and at least one report file, and the project window 1200 may include at least one belonging to each project (eg, 1202). UI objects 1221 and 1222 corresponding to each of the SQL files of the UI object, UI objects 1231 corresponding to each of the at least one report file, and the UI objects 1241 corresponding to the design file may be displayed.

The UI objects 1221 and 1222 corresponding to each of the at least one SQL file may be displayed at a lower level of the SQL container UI object 1220. The user can interact with the SQL container UI object 1220 in some way to generate a new SQL file, and the UI object corresponding to the newly created SQL file is added to the lower level of the SQL container UI object 1220. Can be. In this case, the newly created SQL file may be an empty file including no information.

The UI object 1231 corresponding to each of the at least one report file may be displayed at a lower level of the report container UI object 1230. The user may interact with the report container UI object 1230 in a predetermined manner to generate a new report file, and the UI object corresponding to the newly generated report file may be added as a lower level of the report container UI object 1230. Can be. In this case, the newly generated report file may be an empty file including no information.

Meanwhile, when a UI object (eg, 1221) corresponding to any one of the at least one SQL file is selected by the user, the generation module 110 may generate an SQL file corresponding to the selected UI object 1221. SQL file editing function can be provided for editing. The generation module 110 may display a UI for editing an SQL file in the editor window 1400 to provide an SQL file editing function, and the user may edit the SQL file on the UI displayed in the editor window 1400. Can be.

In addition, when a UI object corresponding to any one of the at least one report file (for example, 1231) is selected by the user, the generation module 110 may provide a report editing UI for editing a report electronic document. have. The generation module 110 may display a UI for editing a report file in the editor window 1400 to provide a report file editing function, and the user may edit a report file on the UI displayed in the editor window 1400. Can be.

Also, when a UI object 1241 corresponding to a design file is selected by a user, the generation module 110 may provide a design file editing function for editing the design file. The generation module 110 may display a UI for editing the design file in the editor window 1400 to provide a design file editing function, and the user may edit the design file on the UI displayed in the editor window 1400. Can be.

Meanwhile, a user may generate a new design file by interacting with a UI object (eg, 1202) corresponding to a specific project in a predetermined manner, and the UI object corresponding to the newly created design file corresponds to the project. It can be added as a lower level of the UI object 1202. In this case, the newly created design file may be an empty file including no information.

In the above, an example in which the generation module 110 provides each file editing function on the editor window 1400 included in the integrated development environment UI 1000 has been described, but according to an embodiment, the generation module 110 May execute a separate application corresponding to each file editing function, in which case the user may edit each file on the executed application.

5 is a diagram illustrating an example of a database search window 1300.

As shown in FIG. 5, the database search window 1300 may include UI objects 1310 and 1320 corresponding to the DB 130 connected to the user terminal 100 or the generation module 110.

The UI object (eg, 1310) may have UI objects 1311 to 1313 representing at least one schema at a lower level. A schema is a structure that defines the structure of data in a database, how data is represented, and the relationship between data in a formal language, or as a namespace, and may mean a container including objects such as a table and a stored procedure. Therefore, a lower level of the UI object representing a specific schema may have UI objects corresponding to each object such as a table or a stored procedure included in the schema.

A table refers to a collection of data composed of fields, which are items for storing respective data, and one database may be composed of several tables. A stored procedure or stored procedure is a set of queries for executing a series of queries as a function. A stored procedure is a stored procedure in the database management system that organizes a series of operations on a database. Also called a Persistent Storage Module.

The editor window 1400 may display an editing UI corresponding to the file selected by the user.

6 is a flowchart schematically illustrating a process of the generation module 110 performing an ERD file editing function.

Referring to FIG. 6, when a user selects an object corresponding to an ERD file, the generation module 110 may provide an ERD file editing UI (S131). In an embodiment, the generation module 110 may display an ERD file editing UI in the editor window 1400. In this case, the ERD file editing UI may include a table structure UI object representing a structure of a database table and a relationship UI object representing a relationship between a table.

Thereafter, the generation module 110 may change a relationship between a table schema and a table schema according to a user input on the ERD file editing UI (S132). When the change is completed, the changed table structure and the relationship between the tables may be reflected in the ERD file (S133).

Hereinafter, the process of FIG. 6 will be described in more detail with reference to FIG. 7.

The generation module 110 may provide an ERD file editing UI 2000 through the editor window 1400 based on the contents of an ERD file corresponding to an ERD file object selected by a user.

7 is a diagram illustrating an example of an ERD file editing UI 2000.

As shown in FIG. 7, the ERD file editing UI 2000 may include a toolbar UI 2100 including a button for creating a new table, a button for creating a new relationship, and a button for reflecting changes to the DB 130. Can be. In addition, the ERD file editing UI 2000 may include a table structure UI object (eg, 2210, 2220, 2230) representing a structure of a database table, and a relationship UI object (eg, 2310, 2320) representing a relationship between a table. It may include.

Each column information included in the table may be displayed on the table structure UI objects 2210, 2220, and 2230.

The relationship UI objects 2310 and 2320 may be in the form of lines connecting two table structure UI objects 2100 and 2110. The relationship UI object may be expressed in different forms (for example, solid line or dotted line) depending on whether the relationship between two tables is an identification relationship or a non-identification relationship.

The generation module 110 may change a relationship between a table structure and a table structure according to a user input on the ERD file editing UI.

The user may create a new table UI object on the ERD file editing UI 2000.

The user may create a UI object corresponding to a table previously created in the DB 130. To this end, a user may input a command such as selecting a UI object corresponding to a specific table displayed in the above-described database search window 1300 or dragging and dropping onto the ERD file editing UI 2000. In response, the generation module 110 may generate a new table UI object corresponding to the table in the ERD file editing UI 2000. Alternatively, the user may select a new table generation UI provided by the ERD file editing UI 2000 to generate a UI object corresponding to the new table.

On the other hand, the user deletes the table UI object existing on the ERD file editing UI 2000 or changes the structure of the table through the corresponding table UI object (for example, add / delete / change column or change attribute of the table). You may.

In addition, the user may create a new relationship UI object indicating a relationship between table UI objects existing on the ERD file editing UI 2000. For example, the user selects a button for creating a new relationship provided by the ERD file editing UI 2000 and then selects two tables to form a relationship to generate a new relationship UI object representing a relationship between the two selected tables. Can be.

Meanwhile, the user may delete the relationship UI object existing on the ERD file editing UI 2000 or change the relationship information through the relationship UI object.

On the other hand, after the database modeling is changed through the above process, for example, when the user presses a predetermined storage button, the generation module 110 may reflect the relationship between the changed table schema and the table schema in the ERD file.

In addition, the generation module 110 may change the table structure of the DB 130, add a new table, or delete an existing table by reflecting the relationship between the changed table schema and the table schema DB 130.

8 is a flowchart schematically illustrating a process of the generation module 110 performing a SQL file editing function.

Referring to FIG. 8, when the user selects an object corresponding to an SQL file, the generation module 110 may provide an SQL editing UI (S141). In an embodiment, the generation module 110 may display an SQL editing UI in the editor window 1400.

Thereafter, the generation module 110 may change the SQL query according to a user input on the SQL editing UI (S142). When the change is completed, the changed query may be reflected in the SQL file (S143).

Hereinafter, the process of FIG. 8 will be described in more detail with reference to FIG. 9.

When the user selects an object corresponding to the SQL file, the SQL file editing UI 3000 may be displayed in the editor window 1400. That is, the generation module 110 may provide the SQL file editing UI 3000 displaying the contents of the SQL file corresponding to the SQL file object selected by the user through the editor window 1400.

9 is a diagram illustrating an example of the SQL file editing UI 3000.

As shown in FIG. 9, the SQL file editing UI 3000 includes a UI for selecting a DB to be connected, a button for performing a connection with the DB, a button for releasing the connection, and whether the created query is Insert or Update. It may include a toolbar UI 3100 including a UI for selecting.

In addition, the SQL file editing UI 3000 may include an editing UI 3200 for creating a query, and a user may create or edit an SQL query on the editing UI 3200. The user can include parameter variable names when creating queries. For example, the parameter variable name may be in the form of '@variable name'. The parameter variable name can be used to associate a query with a control on the function screen editing UI described below. To this end, at least some of the controls included in the design file may be mapped to the parameter variable names. Meanwhile, when the SQL query is executed later, data input to the control mapped to the parameter variable name may be input to the SQL query. More precisely, data input to a control mapped to the parameter variable name may be allocated to the parameter variable name of the SQL query.

The toolbar UI 3200 may include a button for executing a created query, and the SQL file editing UI 3000 may include a result display UI 3300 on which an execution result is displayed. On the result display UI 3300, the structure of the table and the data inquired by the query may be displayed.

On the other hand, if the SQL query is changed through the above process, for example, when the user presses a predetermined save button, the generation module 110 may reflect the changed SQL query to the SQL file.

10 is a flowchart schematically illustrating a process in which the generation module 110 performs a design file editing function.

Referring to FIG. 10, when a user selects an object corresponding to a design file, the generation module 110 may provide a function screen editing UI (S151). In an embodiment, the generation module 110 may display a function editing UI in the editor window 1400.

Thereafter, the generation module 110 may change the control constituting the screen of the user-defined ERP function and the property of each control according to a user input on the function screen editing UI (S152).

Thereafter, the generation module 110 may reflect, in the design file, the control file constituting the changed screen of the user-defined ERP function, the properties of each changed control, and mapping information between the changed control and the query (S153).

Hereinafter, the process of FIG. 10 will be described in more detail with reference to FIGS. 11 to 14.

When the user selects an object corresponding to the design file, the design file editing UI may be displayed in the editor window 1400. That is, the generation module 110 may provide a design file editing UI through the editor window 1400 based on a design file corresponding to a design file object selected by the user.

11 is a diagram illustrating an example of a design file editing UI 4000.

The design file editing UI 4000 may display various controls (for example, 4010 to 4040) previously defined in the design file.

The user can delete the control displayed in the design file editing UI 4000, change the layout, or modify the external elements such as the size.

The user may also add new controls to the design file editing UI 4000. To this end, the generation module 110 may provide a toolbox window 1500 for selecting various controls. 12 is a diagram illustrating an example of a toolbox window 1500.

As shown in FIG. 12, the toolbox window 1500 may include various types of controls, and the user may select a desired control or drag and drop it to the design file editing UI 4000 to drop the control into the design file editing UI. It can be placed at (4000).

Meanwhile, various controls may be classified into specific categories in the toolbox window 1500 according to a predetermined classification criterion. For example, as shown in FIG. 2F, a common control 1510 commonly used in a GUI, a business control 1520 specially used in the ERP field, a data control 1530, and a layout of a screen are configured. The layout control 1550, a popup control 1570, etc., serving as a container may be classified.

In particular, a control belonging to the data control category 1530 (hereinafter, referred to as a “data control”) may perform a function of displaying data retrieved by an SQL query. Data controls can include a Flex Grid that displays in the form of a data table queried by an SQL query, a Pivot Grid that displays in a PivotTable format, and a Chart Grid that displays in the form of a chart. have. In addition, there may be various types of data controls. An example of a flex grid is the data control 4040 of FIG. 11.

Meanwhile, when the user selects (eg, clicks) a control disposed in the design file editing UI 4000 in a predetermined manner, the property value of the selected control may be displayed in the property window 1600, and the user may view the property window. You can change the property value of the control shown in (1600). 13 is a diagram illustrating an example of a property window 1600.

In addition, when the user selects (eg, double-clicks) a control disposed in the design file editing UI 4000 in a predetermined manner, the script window 1700 has a method indicating an action to be performed when a specific event occurs. The script can be displayed and the user can create / edit the method script shown in the script window 1700. 14 is a diagram illustrating an example of a script window 1700.

As shown in FIG. 14, the script window 1700 includes a UI 1710 for selecting any one of the controls disposed in the design file editing UI 4000, and a UI 1720 for selecting an event that may occur in the control. It may include a UI 1730 for writing a method script to be executed when the selected event occurs in the selected control.

Meanwhile, when the control constituting the screen of the user-defined ERP function, the properties of each control, and / or the method script are changed through the above process, for example, when the user presses a predetermined save button, the generation module 110 ) Can be reflected in the design file.

Meanwhile, the generation module 110 may perform a mapping process so that the content displayed on the screen of the user-defined ERP function is associated with the SQL query. That is, the generation module 110 may include a SQL mapping UI for mapping at least a portion (for example, 4040) of the data controls displayed in the design file editing UI 4000 to a specific query included in the at least one SQL file. The at least one control may be mapped to a specific query included in the at least one SQL file according to a user input on the SQL mapping UI. 15A to 15E illustrate an example of the SQL mapping UI.

15A is a diagram illustrating a current SQL mapping state. The SQL mapping UI 5000 illustrated in FIG. 15A may include a UI 5010 that displays a list of queries defined in at least one SQL file corresponding to a user-defined ERP function. In the example of FIG. 15A, a query named SQL may be mapped to a given data control. The user can map parameters and input controls (controls that can receive data from the user) described in the SQL query through the SQL mapping UI (5000), and map the SQL query and the data control to display the results of the query. can do. In addition, you can set up a separate query to be executed when the user changes the value displayed in the data control or adds / deletes a column, which will be described in detail below.

In the case of selecting the 'query setting' 5020 of the SQL query in FIG. 15A, the UI 5100 as shown in FIG. 15B may be displayed. On the UI 5100 as shown in FIG. 15B, a user may map each parameter variable name included in an SQL statement and a specific control (eg, 4010 and / or 4030) included in the design file editing UI 4000. have. The control mapped to the parameter variable name may be a control (input control) that performs a function of receiving data from a user. As shown in FIG. 15B, the UI 5100 may include a list 5110 listing each parameter variable name included in an SQL statement. The UI 5100 may include a UI for selecting a control to be mapped to each parameter variable name. For example, 5101 to 5103).

In the example of FIG. 15B, @multiModule is mapped with bpComboBox1 4010, and @keyword is mapped with textBoxExt1 4030. As described above, when the parameter variable name in the SQL query and the specific control included in the design file editing UI 4000 are mapped, the data input to the control mapped to the parameter variable name is executed when the pepper SQL query is executed. It can be entered into the SQL query.

When selecting 'control setting' 5030 in FIG. 15A, the UI 5200 as shown in FIG. 15C may be displayed. The UI 5200 may include a UI 5210 for selecting a data control displayed on the design file editing UI 4000. This allows the user to select a data control (e.g. 4040) to be mapped with the SQL query.

In addition, the UI 5200 may be used to perform customization such as selecting columns to be used / outputted from the columns included in the DB table to be queried through SQL query, adjusting the display order, or setting the display format of each field. ) May be further included.

When selecting the binding setting 5040 in FIG. 15A, the UI 5300 may be displayed as illustrated in FIG. 15D. On the UI 5300 as illustrated in FIG. 15D, a user may map a specific control included in the design file editing UI 4000 and a column included in a DB table to be queried through an SQL query.

In the case of selecting the 'save setting' 5050 in FIG. 15A, the UI 5400 shown in FIG. 15E may be displayed. The UI 5400 as shown in FIG. 15E includes a UI 5410 for selecting an SQL query for inserting a record inserted through the data control into a database, and a UI 5520 for selecting a query for updating changed data on the data control. ), A UI 5430 for selecting a query for deleting a record.

16 is a flowchart schematically illustrating the above-described mapping process.

In one embodiment, the generation module 110 may display each SQL query included in the at least one SQL file (S210).

When the user selects one of the displayed SQL queries, the selected SQL query may be analyzed to obtain a parameter variable name included in the SQL query (S220), and the obtained parameter variable name may be displayed.

Then, according to a user input, the generation module 110 may map each parameter variable name displayed with a control (for example, 4010 or 4030) displayed on the design file editing UI 4000 (S240).

In addition, the generation module 110 may map the SQL query selected by the user's input with any one data control (for example, 4040) displayed on the design file editing UI 4000 (S240 and S250).

Referring back to FIG. 1B, the driving module 120 may drive the user-defined ERP function generated by the generation module 110 to provide the user-defined ERP function.

As described above, the generation module 110 may generate at least one SQL file and a design file corresponding to the user-defined ERP function, and the driving module 120 may interpret the information and drive the user-defined ERP function. have. The driving module 120 may be a kind of engine that receives a kind of metadata or a script and performs an operation corresponding thereto.

For example, the driving module 120 may configure a screen of a user-defined ERP function by using information about various controls included in the design file, and display it. In addition, when the user inputs a specific command or data to the control, the driving module 120 may perform a method, a script, or a built-in function corresponding thereto. In addition, the driving module 120 may execute an SQL query mapped to the data control and reflect the execution result to the data control or the DB 130. In addition, the driving module 120 may perform various instructions to enable the user-defined ERP function to operate correctly.

The sharing module 140 may perform a user-defined ERP sharing function to be described below.

FIG. 17 is a diagram illustrating an example of a process in which a user-defined ERP function is shared by the user terminal 100 and the sharing system 200. 17 illustrates an example in which one user-defined ERP function is shared between two terminals for convenience of description, but a plurality of user-defined ERP functions may be shared among a plurality of terminals.

Referring to FIG. 17, a process of sharing a user-defined ERP function between two terminals 100-1 and 100-2 may be largely divided into a source package upload process (S310 ˜ S340) and a source package download process (S350 ˜ S370). have.

First, the source package upload process will be described. First, the sharer terminal 100-1 who wants to share a user-defined ERP function with others may provide a source package upload UI (S310). The source package upload UI may provide a function for the user to select a user-defined ERP function to be transmitted to the sharing system 200. The sharer terminal 100-1 may store a project corresponding to a plurality of user-defined ERP functions, and a user may select a project among them, through the source package upload UI.

Some or all of the projects stored in the sharer terminal 100-1 may be generated in advance through the above-described user-defined ERP generation process. Alternatively, some or all of the projects stored in the sharer terminal 100-1 may be downloaded to the sharer terminal 100-1 through a source package download function to be described later.

The source package may correspond to a predetermined user defined ERP function, and may include at least one SQL file and a design file corresponding to the user defined ERP function. According to an embodiment, the source package may further include an ERD file.

In addition, the source package may further include additional information about a corresponding user-defined ERP function. The additional information may include any information related to the user-defined ERP function, and may be, for example, the name, description, creator, sharer and / or screenshot, category information, etc. of the user-defined ERP function.

18 is a diagram illustrating an example of a source package upload UI 6000.

The source package upload UI 6000 may include a list 6100 of projects of the user-defined ERP function stored in the sharer terminal 100-1. Each list contains a UI object (e.g. 6010) for selecting whether to upload or not, a UI object (e.g. 6020) for displaying the name of the project (or a name of a user-defined ERP function), and detailed description information. A UI object (eg, 6030), a UI object (eg, 6040) for selecting whether to publish, a UI object (eg, 6050) for designating a screenshot, and the like. In addition, the source package upload UI may further include a UI object for inputting / specifying various additional information included in the source package.

As shown in FIG. 18, the user may select some of the seven projects (Project1 and Project2 in the example of FIG. 18). After selecting a project to be shared, the user may select a button 6200 for performing upload to instruct the sharer terminal 100-1 to perform upload.

Referring back to FIG. 17, the sharer terminal 100-1 may generate a source package corresponding to a user-defined ERP function selected by a user (S320), and transmit the same to the sharing system 200 (S330). .

Then, the sharing system 200 may store the received source package in the predetermined storage 210 (S340).

Meanwhile, according to an embodiment, the sharing system 200 may classify and store the received source package according to a predetermined criterion. To this end, the sharing system 200 may determine where a user-defined ERP function corresponding to the source package is frequently belonged among a plurality of predefined categories, and the source package includes a user-defined ERP function. It may be classified into categories and stored in the storage 210. The plurality of predefined categories may include categories that are widely used in the ERP field. For example, categories can include accounting, human resources, sales, purchasing / materials, outsourcing, trade, services, construction, production, standards, costs, consolidated accounting, and so on.

The category to which the user-defined ERP function belongs may be specified by the sharer.

Alternatively, the category to which the user-defined ERP function belongs may be determined by the sharing system 200. The sharing system 200 may analyze at least one SQL file included in the source package or a design file included in the source package in order to determine which category the user-defined ERP function belongs to. Based on the determination, the user-defined ERP function corresponding to the source package belongs to one of the plurality of categories. For example, the sharing system 200 analyzes the name or other information of the database described in the query statement of the SQL file included in the source package, the name or other information of the table or field, and / or the name or other information of the parameter. can do. Alternatively, the sharing system 200 may analyze various types of information (for example, names or properties of controls) described in the design file included in the source package.

Next, when the source package download process is described, when the user terminal 100-2 accesses the sharing system 200 or requests a list in order to download various user-defined ERP functions shared by others, the sharing system ( 200 may transmit a list of source packages stored in the storage 210 to the user terminal 100-2 (S350).

Then, the user terminal 200 may provide a source package download UI (S360). The source package download UI may display a list of received source packages and may provide a function of selecting at least some items from the received source package list.

19 is a diagram illustrating an example of a source package download UI 7000. Referring to FIG. 19, the source package download UI 7000 may include a list UI 7100 displaying a list of source packages received from the sharing system 200. Each item of the list UI 7100 may include information such as a name of a source package, a name of a corresponding user-defined ERP function, a representative icon, a registration date, and the like. In addition, the source package download UI 7000 may further include a detailed information display UI 7200 for displaying detailed information of the source package selected by the user. The detailed information display UI 7200 is a name of the application (for example, the driving module 120 described above) to which the user-defined ERP function corresponding to the corresponding source package is applied, the registrant, the name of the source package, and the corresponding user definition. It may include a name and a detailed description of the ERP function. The detailed information display UI 7200 may also display a screen shot 7210 of a user-defined ERP function. The screenshot may be an image designated by the sharer who shared the source package.

Alternatively, the screen shot 7210 may be an image generated by the sharing system 200. For example, the sharing system 200 may perform the functions of the driving module 200 described above, and execute a user-defined ERP function using a SQL file and a design file included in a source package, and then take a screenshot. You can take a picture.

The source package download UI 7000 may further include a category UI 7300 displaying a list of categories to which the user-defined ERP function may belong. When the user selects one of the categories included in the category UI 7300, the list UI 7100 may display only a list of source packages corresponding to the user-defined ERP function belonging to the selected category.

The source package download UI 7000 may further include an upload button 7400. When the upload button 7400 is selected, the user terminal 100-2 provides the source package upload UI 6000 described above. The user terminal 100-2 may share the user-specified ERP function with others.

In addition, the source package download UI may further include a button UI 7410 for requesting the download of the source package selected by the user. When the user selects the button UI 7410, the user terminal 100-2 may request a download of a source package from the sharing system 200.

Referring back to FIG. 17, in response to a download request of the user terminal 100-2, the sharing system 200 selects a target source package selected by the user terminal from among source packages stored in the storage 210. It may transmit to the terminal 100-2 (S370).

In some implementations, the user-defined ERP function sharing system may include at least one processor and a memory storing a program executed by the processor. The processor may include a single core CPU or a multi core CPU. The memory may include fast random access memory and may include nonvolatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other nonvolatile solid state memory devices. Access to memory by the processor and other components may be controlled by the memory controller. Here, when the program is executed by a processor, the user-defined ERP function sharing system according to the present embodiment may allow the user-defined ERP function sharing method to be performed.

Meanwhile, the method for generating a user-defined ERP function according to an embodiment of the present invention may be implemented in a computer-readable program command form and stored in a computer-readable recording medium. The computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored.

The program instructions recorded on the recording medium may be those specially designed and constructed for the present invention, or may be known and available to those skilled in the software art.

Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, floppy disks, and the like. Included are hardware devices specifically configured to store and execute the same magneto-optical media and program instructions such as ROM, RAM, flash memory, and the like. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

Examples of program instructions include not only machine code generated by a compiler, but also devices that process information electronically using an interpreter, for example, high-level language code that can be executed by a computer.

The hardware device described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

The foregoing description of the present invention is intended for illustration, and it will be understood by those skilled in the art that the present invention may be easily modified in other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are exemplary in all respects and not restrictive. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined form.

The scope of the present invention is shown by the following claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included in the scope of the present invention. .

The present invention can be used in a user-defined ERP function sharing method and system.

Claims (11)

1. A custom enterprise resource planning (ERP) function sharing method.

   Receiving, by the user-defined ERP function sharing system, a source package including at least one SQL file and design file from a plurality of sharer terminals and corresponding to a predetermined ERP user-defined function, wherein the SQL file is for operating a database. A file that stores a structured query language (SQL) query, wherein the design file is a file that stores information about attributes of at least one control constituting the screen of the user defined ERP function, and displays the screen of the user defined ERP function. At least some of the constituting controls are controls mapped to specific queries included in the at least one SQL file;

   Storing, by the user-defined ERP function sharing system, source packages received from the plurality of sharer terminals in a predetermined storage;

   Providing, by the user-defined ERP function sharing system, a list of source packages stored in the repository to a user terminal; And

   In response to a download request of the user terminal, transmitting the target source package selected by the user terminal among the source packages stored in the storage to the user terminal.
2. The method of claim 1,

   The user-defined ERP function sharing system, storing the source package received from the plurality of sharer terminals in a predetermined storage,

   Determining where a user-defined ERP function corresponding to the source package belongs among a plurality of predefined categories; And

   And classifying the source package into a category to which the corresponding custom ERP function belongs and storing the source package in the repository.
3. The method of claim 2,

   Determining where the user-defined ERP function corresponding to the source package belongs to a plurality of predefined categories,

   Analyzing at least one SQL file included in the source package or a design file included in the source package; And

   And determining which of the plurality of categories a user-defined ERP function corresponding to the source package belongs to based on the analysis result.
4. The method of claim 1,

   The user terminal performs a source package upload method and a source package download method,

   The source package upload method,

   Providing a source package upload UI providing a function of selecting at least some items from a list of at least one source package stored in the user terminal; And

   Transmitting a source package corresponding to the selected item through the source package upload UI to the user-defined ERP function sharing system;

   The source package download method,

   Receiving a list of source packages stored in the repository from the user defined ERP function sharing system;

   Providing a source package download UI providing a function of selecting at least some items of the received source package list; And

   Receiving a source package corresponding to the item selected through the source package download UI from the user-defined ERP function sharing system.
5. The method of claim 1,

   The user terminal receives the target source package from the user defined ERP function sharing system, and then performs a method for generating a user defined ERP function corresponding to the target source package,

   Method for generating a user-defined ERP function corresponding to the target source package,

   Providing a container UI including a UI object corresponding to an ERD file, a UI object corresponding to each of at least one SQL file included in the target source package, and a UI object corresponding to a design file included in the target source package. Wherein the ERD file is a file for storing information modeling attributes of tables stored in a database and relationships between the tables;

   If an UI object corresponding to the ERD file is selected, providing an ERD file editing function for editing the ERD file;

   When a UI object corresponding to any one of the at least one SQL file is selected, providing an SQL file editing function for editing an SQL file corresponding to the selected UI object;

   If a UI object corresponding to the design file is selected, providing a design file editing function for editing the design file; And

   Providing the user-defined ERP function based on the at least one SQL file and the design file.
6. A computer program installed in a data processing apparatus and stored in a recording medium for carrying out the method according to any one of claims 1 to 5.
7. At least one processor;

   A user defined ERP function sharing system comprising a memory for storing a computer program executed by the processor,

   The computer program causes the user-defined ERP function sharing system to execute a user-defined ERP function sharing method when executed by the processor,

   The user-defined ERP function sharing method,

   Receiving, by the user-defined ERP function sharing system, a source package including at least one SQL file and a design file from a plurality of sharer terminals and corresponding to a predetermined ERP user-defined function, wherein the SQL file operates a database. A file for storing a SQL query, wherein the design file is a file for storing information on the properties of at least one control constituting the screen of the user-defined ERP function, Among the controls constituting the screen of the user-defined ERP function At least some of the controls are mapped to particular queries included in the at least one SQL file;

   Storing, by the user-defined ERP function sharing system, source packages received from the plurality of sharer terminals in a predetermined storage;

   Providing, by the user-defined ERP function sharing system, a list of source packages stored in the repository to a user terminal; And

   And in response to a download request of the user terminal, transmitting the target source package selected by the user terminal among the source packages stored in the storage to the user terminal.
8. The method of claim 7, wherein

   The user-defined ERP function sharing system, storing the source package received from the plurality of sharer terminals in a predetermined storage,

   Determining where a user-defined ERP function corresponding to the source package belongs among a plurality of predefined categories; And

   And classifying the source package into a category to which a corresponding custom ERP function belongs and storing the source package in the repository.
9. The method of claim 8,

   Determining where the user-defined ERP function corresponding to the source package belongs to a plurality of predefined categories,

   Analyzing at least one SQL file included in the source package or a design file included in the source package; And

   And determining which of the plurality of categories a user-defined ERP function corresponding to the source package belongs to based on the analysis result.
10. The method of claim 7, wherein

    The user terminal performs a source package upload method and a source package download method,

    The source package upload method,

    Providing a source package upload UI providing a function of selecting at least some items from a list of at least one source package stored in the user terminal; And

    Transmitting a source package corresponding to the selected item through the source package upload UI to the user-defined ERP function sharing system;

    The source package download method,

    Receiving a list of source packages stored in the repository from the user defined ERP function sharing system;

    Providing a source package download UI providing a function of selecting at least some items of the received source package list; And

    Receiving a source package corresponding to the item selected through the source package download UI from the user-defined ERP function sharing system.
11. The method of claim 7, wherein

    The user terminal receives the target source package from the user defined ERP function sharing system, and then performs a method for generating a user defined ERP function corresponding to the target source package,

    Method for generating a user-defined ERP function corresponding to the target source package,

    Providing a container UI including a UI object corresponding to an ERD file, a UI object corresponding to each of at least one SQL file included in the target source package, and a UI object corresponding to a design file included in the target source package. Wherein the ERD file is a file for storing information modeling attributes of tables stored in a database and relationships between the tables;

    If an UI object corresponding to the ERD file is selected, providing an ERD file editing function for editing the ERD file;

    When a UI object corresponding to any one of the at least one SQL file is selected, providing an SQL file editing function for editing an SQL file corresponding to the selected UI object;

    If a UI object corresponding to the design file is selected, providing a design file editing function for editing the design file; And

    Providing the user-defined ERP function based on the at least one SQL file and the design file.

Images