CN114969255B - ERP document searching method and system - Google Patents
ERP document searching method and system Download PDFInfo
- Publication number
- CN114969255B CN114969255B CN202210579236.XA CN202210579236A CN114969255B CN 114969255 B CN114969255 B CN 114969255B CN 202210579236 A CN202210579236 A CN 202210579236A CN 114969255 B CN114969255 B CN 114969255B
- Authority
- CN
- China
- Prior art keywords
- odoo
- search
- query
- data
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 61
- 230000006870 function Effects 0.000 claims abstract description 12
- 230000001360 synchronised effect Effects 0.000 claims description 30
- 229920001971 elastomer Polymers 0.000 claims description 11
- 239000000806 elastomer Substances 0.000 claims description 11
- 230000011218 segmentation Effects 0.000 claims description 11
- 238000004806 packaging method and process Methods 0.000 claims description 10
- 238000004220 aggregation Methods 0.000 claims description 5
- 230000002776 aggregation Effects 0.000 claims description 5
- 238000012163 sequencing technique Methods 0.000 claims description 4
- 238000005538 encapsulation Methods 0.000 claims description 3
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 238000012559 user support system Methods 0.000 claims description 3
- 230000004931 aggregating effect Effects 0.000 claims description 2
- 230000008571 general function Effects 0.000 claims 1
- 230000000694 effects Effects 0.000 abstract description 3
- 238000003860 storage Methods 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 5
- 230000018109 developmental process Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 230000033772 system development Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/3331—Query processing
- G06F16/334—Query execution
- G06F16/3344—Query execution using natural language analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
- G06F40/279—Recognition of textual entities
- G06F40/289—Phrasal analysis, e.g. finite state techniques or chunking
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Artificial Intelligence (AREA)
- Computational Linguistics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Health & Medical Sciences (AREA)
- Audiology, Speech & Language Pathology (AREA)
- General Health & Medical Sciences (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and a system for searching ERP documents, which belong to the technical field of ERP document inquiry, the method analyzes and packages the inquiry of Odoo frame ORM, packages the common functions of Odoo inquiry conditions based on a full-text search engine elastic search, and provides service for exposing a Restful API; and calling the packaged API by using Odoo ORM framework query language to obtain a corresponding query result, and realizing the joint query of the Odoo framework on the bill header data and the detail data. The invention can achieve the effect of opening the box for use without Odoo developer knowing the relevant knowledge of the elastic search, and can solve the problems of the scene of the combined query of the Odoo complex list and the scene of the complex query under a large data volume.
Description
Technical Field
The invention relates to the technical field of ERP document inquiry, in particular to a method and a system for searching ERP documents.
Background
In ERP system development and application, odoo frames provide an efficient ERP system development means, and by using the ORM frames of Odoo, developers can be enabled to achieve the purpose of rapid development without being concerned about underlying data models and implementations. However, the Odoo framework also has certain drawbacks, such as not very good support for complex joint query, and can only query by means of returning the results of the superior query to the next result of the list again, which is almost impossible for Odoo if the list view presentation of the multi-list Cartesian product mode is required to be realized. For ERP systems, almost all documents are in a "header + body" structure, so that Odoo can only support list presentation to the header in the list view of the document. If the form details of the list documents need to be displayed, the user needs to drill down to the document detail page to view, and if the user needs to view a plurality of form detail lines at a time, the native Odoo cannot do so.
Disclosure of Invention
The technical task of the invention is to provide the ERP document searching method and the ERP document searching system aiming at the defects, so that the problems of the scene of the Odoo complex list combined query and the scene of the complex query under a large data volume can be solved.
The technical scheme adopted for solving the technical problems is as follows:
An ERP document searching method analyzes and encapsulates the query of Odoo frame ORM, encapsulates the common functions of Odoo query conditions based on an elastic search of a full-text search engine, and provides services for exposing a Restful API;
and calling the packaged API by using Odoo ORM framework query language to obtain a corresponding query result, and realizing the joint query of the Odoo framework on the bill header data and the detail data.
The full-text search engine is used as a full-text search solution which is most popular in internet application, can support TB-level document retrieval, an ES bottom layer uses a word segmentation algorithm to build an inverted index for documents needing to be indexed in a database, can quickly inquire about documents related to terms, and uses TF/IDF algorithm scores to evaluate document relevance.
The method is based on the combination of a full-text search engine and an ERP framework Odoo, introduces an elastomer search, synchronizes data in a PostgreSQL database to the elastomer search database, and provides support for the joint search of the table head and table body in Odoo and the search requirement under a large data volume by using the technical scheme of elastomer search parent-child documents. The client can call the packaged API by using Odoo ORM framework query language under the condition without any elastic search basis, so as to obtain a corresponding query result.
Preferably, the conventional functions based on the full text search engine elastic search encapsulate Odoo query conditions, and further include middleware dis and Rabbitmq,
When the synchronous data quantity exceeds the threshold set by the user, the asynchronous MQ is used for data synchronization, otherwise, when the data quantity is smaller, the synchronous http interface is called for data synchronization, and the ES server uses an immediate refreshing strategy to write the data into the disk, so that the real-time property of the data is ensured.
The data in the PostgreSQL database is synchronized to the elastomer search database in a synchronous + asynchronous manner.
Preferably, the common functions of Odoo query terms include parsing, querying, aggregating, paging, and sorting.
Preferably, the specific packaging content comprises:
odoo a synchronous consumer and synchronous Restful interface of database source data;
the Odoo search _read interface rewrites the call API, passing Odoo query parameters including domain, sort, limit, model; calling the packaged elastic search service, analyzing domain as ELASTICSEARCH DSL by a server, searching for inquiry and returning a result;
The Odoo search _count interface rewrites and calls the API, transmits Odoo to inquire domain, inquires the number of documents meeting the domain condition in the elastomer search and returns;
the Odoo read _group interface rewrites and calls the API, and queries the transferred aggregation field according to Odoo;
And rewriting Odoo cr, wherein when cr triggers submission, a data synchronization producer is automatically triggered, and synchronous call of Restful interface synchronous data or message queue synchronous data can be selected according to user demand configuration. In the scene that the real-time performance is not too high, the asynchronous and synchronous data of the message queue is recommended to be used, and the performance and the user experience are improved.
According to the method, through the methods of reconstructing Odoo bottom layer search_read, search_count, read_group and the like, combined inquiry of Odoo frames to bill header data and detail data is solved by combining with elastic search, and pain points of ERP system users under Odoo frames in a multi-table joint inquiry scene, a large data amount inquiry speed and the like are solved.
Preferably, the elastic search is selected from elastic search 7.8.1;
the word segmentation device selects the word segmentation mode with the finest granularity of the ik_max_word under the ik word segmentation device, when the user inquires that the domain contains ilike and like operators, TF/IDF scores are used as sequencing basis, and when the user inquires that the domain contains only strong conditions, odoo is used for designating sort.
Preferably, the specific implementation process of the method comprises the following steps:
1) Preparing a service environment;
2) Installing a middleware;
3) Modifying a dock-compose yml file, and configuring an ES host, a port number, an MQ host and a port number of an elastic search encapsulation service;
4) Synchronizing data from Odoo clients to a search system service;
5) Index establishment process: if the user supports the user-defined data structure, the method supports the user to maintain the index by himself; odoo when the user defines the data structure by himself, the user can call the service interface of the search system at the same time to establish the index;
6) The query process: initiating a query request from a Odoo client, when the front end calls a search_read method in Odoo, calling a search system service interface by the Odoo client to search and query, and calling the interface to analyze parameters transmitted from the Odoo front end by the search system service;
7) And (3) a grouping process: the front end of Odoo calls read_group to trigger and call a search system service interface, grouping is realized by packaging Aggrouping in an elastic search, and the search system service realizes grouping inquiry by recursively assembling Odoo front end parameter group;
8) And (3) counting: and enabling Odoo front ends to call search_count to trigger and call a search system service interface, and realizing element counting meeting the conditions by packaging a count method in an elastic search.
Preferably, the parameters entered by the Odoo front end include domain, sort, fields, model,
And Odoo, domain is a Polish expression with a specific element of element ancestor, and when the search system service analyzes the domain expression, the Polish expression is converted into an inverse Polish expression, and the domain of Odoo is converted into DSL of an elastic search by means of being put into a stack.
The invention also claims an ERP document searching system, which analyzes and encapsulates the query of Odoo frame ORM, and provides service for the analysis of Odoo and the query call of elastic search in the form of Restful interface;
The system realizes the ERP document searching method, and by using the system, a Odoo developer does not need to know the related knowledge of the elastic search, so that the effect of being used after unpacking can be achieved.
The invention also claims an ERP document searching device, which comprises: at least one memory and at least one processor;
The at least one memory for storing a machine readable program;
The at least one processor is configured to invoke the machine-readable program to execute the ERP document searching method described above.
The present invention also claims a computer readable medium having stored thereon computer instructions that, when executed by a processor, cause the processor to perform the ERP document searching method described above.
Compared with the prior art, the ERP document searching method and system have the following beneficial effects:
Aiming at the problem that in the prior art, for an ERP system, almost all documents are in a structure of 'header + body', list view Odoo of the documents can only support list display of the header, if the body details of the list documents need to be displayed, the list detail page needs to be checked down, if a user needs to check a plurality of body detail lines at a time, the original Odoo is an unrealizable problem, a full-text search engine is introduced, data in a PostgreSQL database is synchronized to the elastic search database, the technical scheme of the elastic search parent-child documents is used for providing support for search requirements of header body joint check and a large data volume in Odoo, and through testing, global search efficiency under a certain data volume is improved by more than 50% compared with Odoo ORM query efficiency, and a linkage check service scene which cannot be supported by the original ORM can be realized.
Drawings
FIG. 1 is a diagram of an implementation architecture of an ERP document searching method provided by an embodiment of the present invention;
FIG. 2 is a process diagram of a search system service parsing Odoo domain expression provided by an embodiment of the present invention.
Detailed Description
The invention will be further illustrated with reference to specific examples.
The embodiment of the invention provides an ERP document searching method, which uses Java as a development language and Springboot.5.1 as a development framework, analyzes and packages the query of an ORM of a Odoo framework, packages the common functions of analysis, query, aggregation, paging, sequencing and the like of Odoo query conditions based on an elastic search of a full-text search engine, and provides service for exposing a Restful API;
The client can call the packaged API by using Odoo ORM frame query language under the condition without any elastic search basis to obtain a corresponding query result, so that the combined query of Odoo frames on bill header data and detail data is realized.
The package content comprises:
odoo a synchronous consumer and synchronous Restful interface of database source data;
the Odoo search _read interface rewrites the call API, passes Odoo query domain, sort, limit, model and other parameters; calling the packaged elastic search service, analyzing domain as ELASTICSEARCH DSL by a server, searching for inquiry and returning a result;
The Odoo search _count interface rewrites and calls the API, transmits Odoo to inquire domain, inquires the number of documents meeting the domain condition in the elastomer search and returns;
The Odoo read _group interface rewrites and calls the API, and queries the transferred aggregation field according to Odoo; the method can support the grouping aggregation query of at most 5 levels, and takes the fact that the ES grouping query performance is not very good, makes 5-level limitation, and can basically meet the requirements of users;
And rewriting Odoo cr, wherein when cr triggers submission, a data synchronization producer is automatically triggered, and synchronous call of Restful interface synchronous data or message queue synchronous data can be selected according to user demand configuration. In the scene that the real-time performance is not too high, the asynchronous and synchronous data of the message queue is recommended to be used, and the performance and the user experience are improved.
According to the method, through the methods of reconstructing Odoo bottom layer search_read, search_count, read_group and the like, combined inquiry of Odoo frames to bill header data and detail data is solved by combining with elastic search, and pain points of ERP system users under Odoo frames in a multi-table joint inquiry scene, a large data amount inquiry speed and the like are solved.
The full text search engine based elastic search encapsulates the usual functions of Odoo query terms, further includes middleware dis and Rabbitmq,
When the synchronous data quantity exceeds the threshold set by the user, the asynchronous MQ is used for data synchronization, otherwise, when the data quantity is smaller, the synchronous http interface is called for data synchronization, and the ES server uses an immediate refreshing strategy to write the data into the disk, so that the real-time property of the data is ensured.
The method synchronizes the data in the PostgreSQL database to the elastomer search database in a synchronous and asynchronous mode.
The elastiscearch is selected from elastiscearch 7.8.1;
the word segmentation device selects the word segmentation mode with the finest granularity of the ik_max_word under the ik word segmentation device, when the user inquires that the domain contains ilike and like operators, TF/IDF scores are used as sequencing basis, and when the user inquires that the domain contains only strong conditions, odoo is used for designating sort.
The method comprises the following specific implementation processes:
1) Service environment: preparing java operation environment and selecting JDK1.8;
2) And (3) middleware: mounting RabbitMQ, redis 6.0.0 above version, elastic search 7.8.1;
3) Modifying a dock-compose yml file, and configuring an ES host, a port number, an MQ host and a port number of an elastic search encapsulation service;
4) There are a number of support ways to synchronize data from Odoo clients to search system services:
LogStash configure source data to synchronize with target data;
The data synchronization Restful interface provided by the method is used for synchronizing data;
The data synchronous message body agreed by the method uses middleware Rabbitmq to asynchronously synchronize data;
When using a data synchronization scheme other than LogStash, it is suggested to make interface calls or message transmissions by modifying Cr; when Cr triggers the commit behavior, the changed data is transferred to the search system service through a synchronous interface or an asynchronous message.
5) Index establishment process: if the user supports the user-defined data structure, the method supports the user to maintain the index by himself; odoo when the user defines the data structure by himself, the user can call the service interface of the search system at the same time to establish the index;
6) The query process: initiating a query request from a Odoo client, when the front end calls a search_read method in Odoo, the Odoo client calls a search system service interface to search for, and parameters transmitted from the Odoo front end are called through the interface: domain, sort, fields, model and other conditions are submitted to the search system service for analysis;
And Odoo, domain is a Polish expression with a specific element of element ancestor, when the search system service analyzes the domain expression, the Polish expression is firstly converted into an inverse Polish expression, and the domain of Odoo is converted into DSL of an elastic search by way of being put into a stack, and the analysis process is shown in figure 2.
7) And (3) a grouping process: the front end of Odoo calls read_group to trigger and call a search system service interface, grouping is realized by packaging Aggrouping in an elastic search, and the search system service realizes grouping inquiry by recursively assembling Odoo front end parameter group;
8) And (3) counting: and enabling Odoo front ends to call search_count to trigger and call a search system service interface, and realizing element counting meeting the conditions by packaging a count method in an elastic search.
The full-text search engine is used as a full-text search solution which is most popular in internet application, can support TB-level document retrieval, an ES bottom layer uses a word segmentation algorithm to build an inverted index for documents needing to be indexed in a database, can quickly inquire about documents related to terms, and uses TF/IDF algorithm scores to evaluate document relevance.
The method is based on the combination of a full-text search engine and an ERP framework Odoo, introduces an elastomer search, synchronizes data in a PostgreSQL database to the elastomer search database in a synchronous and asynchronous mode, and provides support for the joint search of the header and the table in Odoo and the search requirement under a large data volume by using the technical scheme of an elastomer search parent-child document. The client can call the packaged API by using Odoo ORM framework query language under the condition without any elastic search basis, so as to obtain a corresponding query result.
The method most directly solves the joint query of Odoo frames on bill header data and detail data, and effectively verifies in a production environment, supports the search adaptation of more than 100 application bills of modules such as Langchao inSuite2.0 product finance, supply chain and the like, and obtains good feedback. The invention requires that ERP developers use development technology as Odoo framework, the bottom layer provides service by using a Restful interface, odoo developers do not need to know how an elastic search server performs treatment, do not need to have the relevant knowledge of the elastic search, realize complete transparency of a search system to Odoo developers, and can use the search system packaged by the invention as long as Odoo developers have Odoo relevant technical skills.
The embodiment of the invention also provides an ERP document searching system, which analyzes and encapsulates the query of Odoo frame ORM, and provides service for the analysis of Odoo and the query call of elastic search in the form of a Restful interface;
The system realizes the ERP document searching method in the embodiment, and by using the system, the effect of being used after unpacking can be achieved without Odoo developers knowing the related knowledge of the elastic search.
The embodiment of the invention also provides an ERP document searching device, which comprises: at least one memory and at least one processor;
The at least one memory for storing a machine readable program;
The at least one processor is configured to invoke the machine-readable program to perform the ERP document searching method described in the above embodiment.
The embodiment of the invention also provides a computer readable medium, wherein the computer readable medium stores computer instructions, and the computer instructions, when executed by a processor, cause the processor to execute the ERP document searching method in the embodiment. Specifically, a system or apparatus provided with a storage medium on which a software program code realizing the functions of any of the above embodiments is stored, and a computer (or CPU or MPU) of the system or apparatus may be caused to read out and execute the program code stored in the storage medium.
In this case, the program code itself read from the storage medium may realize the functions of any of the above-described embodiments, and thus the program code and the storage medium storing the program code form part of the present invention.
Examples of storage media for providing program code include floppy disks, hard disks, magneto-optical disks, optical disks (e.g., CD-ROMs, CD-R, CD-RWs, DVD-ROMs, DVD-RAMs, DVD-RWs, DVD+RWs), magnetic tapes, nonvolatile memory cards, and ROMs. Alternatively, the program code may be downloaded from a server computer by a communication network.
Further, it should be apparent that the functions of any of the above-described embodiments may be implemented not only by executing the program code read out by the computer, but also by causing an operating system or the like operating on the computer to perform part or all of the actual operations based on the instructions of the program code.
Further, it is understood that the program code read out by the storage medium is written into a memory provided in an expansion board inserted into a computer or into a memory provided in an expansion unit connected to the computer, and then a CPU or the like mounted on the expansion board or the expansion unit is caused to perform part and all of actual operations based on instructions of the program code, thereby realizing the functions of any of the above embodiments.
While the invention has been illustrated and described in detail in the drawings and in the preferred embodiments, the invention is not limited to the disclosed embodiments, and it will be appreciated by those skilled in the art that the code audits of the various embodiments described above may be combined to produce further embodiments of the invention, which are also within the scope of the invention.
Claims (8)
1. The ERP document searching method is characterized by comprising the steps of analyzing and packaging the query of Odoo frame ORM, packaging the common functions of Odoo query conditions based on an elastic search of a full-text search engine, and providing services for externally exposing a Restful API;
Calling the packaged API by using Odoo ORM frame query language to obtain a corresponding query result, and realizing the joint query of the Odoo frame on the bill header data and the detail data;
the specific packaging content comprises the following steps:
odoo a synchronous consumer and synchronous Restful interface of database source data;
the Odoo search _read interface rewrites the call API, passing Odoo query parameters including domain, sort, limit, model; calling the packaged elastic search service, analyzing domain as ELASTICSEARCH DSL by a server, searching for inquiry and returning a result;
The Odoo search _count interface rewrites and calls the API, transmits Odoo to inquire domain, inquires the number of documents meeting the domain condition in the elastomer search and returns;
the Odoo read _group interface rewrites and calls the API, and queries the transferred aggregation field according to Odoo;
Overwriting Odoo cr, when cr triggers submission, automatically triggering a data synchronization producer, and selecting synchronous call Restful interface synchronous data or using message queue synchronous data according to user demand configuration;
The specific implementation process of the method comprises the following steps:
1) Preparing a service environment;
2) Installing a middleware;
3) Modifying a dock-compose yml file, and configuring an ES host, a port number, an MQ host and a port number of an elastic search encapsulation service;
4) Synchronizing data from Odoo clients to a search system service;
5) Index establishment process: if the user supports the user-defined data structure, the method supports the user to maintain the index by himself; odoo when the user defines the data structure by himself, the user can call the service interface of the search system at the same time to establish the index;
6) The query process: initiating a query request from a Odoo client, when the front end calls a search_read method in Odoo, calling a search system service interface by the Odoo client to search and query, and calling the interface to analyze parameters transmitted from the Odoo front end by the search system service;
7) And (3) a grouping process: the front end of Odoo calls read_group to trigger and call a search system service interface, grouping is realized by packaging Aggrouping in an elastic search, and the search system service realizes grouping inquiry by recursively assembling Odoo front end parameter group;
8) And (3) counting: and enabling Odoo front ends to call search_count to trigger and call a search system service interface, and realizing element counting meeting the conditions by packaging a count method in an elastic search.
2. The ERP document searching method according to claim 1, wherein the general functions based on the full text search engine elastic search encapsulate Odoo query conditions, further comprising middleware Redis and Rabbitmq,
When the synchronous data quantity exceeds the threshold set by the user, the asynchronous MQ is used for data synchronization, otherwise, when the data quantity is smaller, the synchronous http interface is called for data synchronization, and the ES server uses an immediate refreshing strategy to write the data into the disk, so that the real-time property of the data is ensured.
3. The method for searching for ERP documents according to claim 1 or 2, wherein the common functions of Odoo query terms include parsing, querying, aggregating, paging and sorting.
4. The ERP document searching method of claim 3, wherein,
The word segmentation device selects the word segmentation mode with the finest granularity of the ik_max_word under the ik word segmentation device, when the user inquires that the domain contains ilike and like operators, TF/IDF scores are used as sequencing basis, and when the user inquires that the domain contains only strong conditions, odoo is used for designating sort.
5. The ERP document searching method according to claim 1, wherein the parameters input from the front end of Odoo include domain, sort, fields, model,
And Odoo, domain is a Polish expression with a specific element of element ancestor, and when the search system service analyzes the domain expression, the Polish expression is converted into an inverse Polish expression, and the domain of Odoo is converted into DSL of an elastic search by means of being put into a stack.
6. An ERP document searching system is characterized in that the query of Odoo frame ORM is parsed and packaged, the parsing of Odoo and the query call of elastic search are provided with services in the form of a Restful interface,
The system implements the ERP document searching method of any one of claims 1 to 5.
7. An ERP document searching apparatus, comprising: at least one memory and at least one processor;
The at least one memory for storing a machine readable program;
the at least one processor being configured to invoke the machine readable program to perform the method of any of claims 1 to 5.
8. A computer readable medium having stored thereon computer instructions which, when executed by a processor, cause the processor to perform the method of any of claims 1 to 5.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210579236.XA CN114969255B (en) | 2022-05-26 | 2022-05-26 | ERP document searching method and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202210579236.XA CN114969255B (en) | 2022-05-26 | 2022-05-26 | ERP document searching method and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN114969255A CN114969255A (en) | 2022-08-30 |
CN114969255B true CN114969255B (en) | 2024-05-14 |
Family
ID=82955558
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202210579236.XA Active CN114969255B (en) | 2022-05-26 | 2022-05-26 | ERP document searching method and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114969255B (en) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101576923A (en) * | 2009-06-25 | 2009-11-11 | 用友软件股份有限公司 | ERP receipts searching method and ERP receipts searching system |
CN106503274A (en) * | 2016-12-22 | 2017-03-15 | 北京览群智数据科技有限责任公司 | A kind of Data Integration and searching method and server |
CN112988863A (en) * | 2021-02-09 | 2021-06-18 | 苏州中科蓝迪软件技术有限公司 | Elasticissearch-based efficient search engine method for heterogeneous multiple data sources |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11064073B2 (en) * | 2019-12-05 | 2021-07-13 | UiPath, Inc. | Unified support framework for a contact center |
-
2022
- 2022-05-26 CN CN202210579236.XA patent/CN114969255B/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101576923A (en) * | 2009-06-25 | 2009-11-11 | 用友软件股份有限公司 | ERP receipts searching method and ERP receipts searching system |
CN106503274A (en) * | 2016-12-22 | 2017-03-15 | 北京览群智数据科技有限责任公司 | A kind of Data Integration and searching method and server |
CN112988863A (en) * | 2021-02-09 | 2021-06-18 | 苏州中科蓝迪软件技术有限公司 | Elasticissearch-based efficient search engine method for heterogeneous multiple data sources |
Also Published As
Publication number | Publication date |
---|---|
CN114969255A (en) | 2022-08-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2616965B1 (en) | Support for a parameterized query/view in complex event processing | |
US11537606B2 (en) | Solution for implementing computing service based on structured query language statement | |
US9420034B2 (en) | Providing services to multiple tenants of an application | |
US20110231784A1 (en) | System and method for desktop application migration | |
US10216846B2 (en) | Combinatorial business intelligence | |
WO2007047900A2 (en) | System and method for displaying data on a thin client | |
CN107766532A (en) | A kind of front end Node.js automates positive static method | |
CN109145051A (en) | The data summarization method and device and electronic equipment of distributed data base | |
US8108768B2 (en) | Improving efficiency of content rule checking in a content management system | |
CN108984155A (en) | Flow chart of data processing setting method and device | |
KR20060045965A (en) | Integrating best practices into database design | |
CN110427188A (en) | It is single to survey configuration method, device, equipment and the storage medium for asserting program | |
TW201409273A (en) | Method and Apparatus of Responding to Webpage Access Request | |
CN111597238A (en) | Method and device for dynamically displaying table data based on database | |
US20050066273A1 (en) | Document creation using a template | |
CN107391528B (en) | Front-end component dependent information searching method and equipment | |
CN109491802A (en) | A kind of method and adapter of the RESTFul network request based on Unity | |
CN114969255B (en) | ERP document searching method and system | |
US20040064804A1 (en) | Generation of partitioned enterprise application using a high-level specification | |
CN109947736A (en) | The method and system calculated in real time | |
US20080244382A1 (en) | Autonomic generation of document structure in a content management system | |
CN112597036B (en) | Universal baffle plate testing method and device | |
CN114281494A (en) | Data full life cycle management method, system, terminal device and storage medium | |
CN113064914A (en) | Data extraction method and device | |
Norrie et al. | Empowering Databases for Context-Dependent Information Delivery. |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |