CN112883243A - Data query method and device, electronic equipment and storage medium - Google Patents
Data query method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112883243A CN112883243A CN202110101995.0A CN202110101995A CN112883243A CN 112883243 A CN112883243 A CN 112883243A CN 202110101995 A CN202110101995 A CN 202110101995A CN 112883243 A CN112883243 A CN 112883243A
- Authority
- CN
- China
- Prior art keywords
- monitoring
- query
- code
- data
- database
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000012544 monitoring process Methods 0.000 claims abstract description 242
- 230000008520 organization Effects 0.000 claims description 78
- 238000011144 upstream manufacturing Methods 0.000 claims description 72
- 238000004590 computer program Methods 0.000 claims description 7
- 238000012545 processing Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 6
- 238000007726 management method Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000004146 energy storage Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
Images
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/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Economics (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Finance (AREA)
- Human Resources & Organizations (AREA)
- Accounting & Taxation (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Computational Linguistics (AREA)
- Entrepreneurship & Innovation (AREA)
- General Engineering & Computer Science (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a data query method, a data query device, electronic equipment and a storage medium, and belongs to the field of computers. The data query method comprises the following steps: receiving an inquiry request about a warehousing operation condition input by a user on a display interface, wherein the inquiry request comprises a monitoring dimension and a monitoring inquiry condition, and the monitoring dimension is one of comprehensive monitoring, non-shipping and daily broadcasting displayed in the display interface; and determining and displaying the warehouse configuration operation data which corresponds to the monitoring dimension and accords with the monitoring query condition from a database. Because the comprehensive monitoring, the non-shipping and the daily broadcasting in the monitoring dimension are all positioned on the same interface, the interface does not need to be replaced when the warehouse configuration operation data with different dimensions are inquired, the operation flow of a user is reduced, the time of the user is saved, and the user experience is improved.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a data query method, apparatus, electronic device, and storage medium.
Background
With the rapid development of the internet and logistics industry in the modern society, people put forward higher and higher requirements on the warehousing industry. The customer of storage industry not only needs the storage to provide storage service, still hopes storehouse energy storage to carry out the control statistics to the operation data of self, makes things convenient for self to inquire to acquire the operation condition of self. In the prior art, when warehouse configuration operation data of different monitoring dimensions are inquired, operation needs to be carried out among different interfaces, and the operation process is excessively complicated.
Disclosure of Invention
The application provides a data query method, a data query device, electronic equipment and a storage medium, and aims to solve the problem that in the prior art, when querying warehouse configuration operation data with different monitoring dimensions, the operation process is too complicated.
In a first aspect, an embodiment of the present application provides a data query method, including: receiving an inquiry request about a warehousing operation condition input by a user on a display interface, wherein the inquiry request comprises a monitoring dimension and a monitoring inquiry condition, and the monitoring dimension is one of comprehensive monitoring, non-shipping and daily broadcasting displayed in the display interface; and determining and displaying the warehouse configuration operation data which corresponds to the monitoring dimension and accords with the monitoring query condition from a database.
In the embodiment of the application, by receiving an inquiry request about the warehouse configuration operation condition input by a user on a display interface, warehouse configuration operation data which corresponds to the monitoring dimension in the inquiry request and meets the monitoring inquiry condition in the inquiry request is determined and displayed from a database. Because the comprehensive monitoring, the non-shipping and the daily broadcasting in the monitoring dimension are all positioned on the same interface, the interface does not need to be replaced when the warehouse configuration operation data with different dimensions are inquired, the operation flow of a user is reduced, the time of the user is saved, and the user experience is improved.
With reference to the technical solution provided by the first aspect, in some possible implementation manners, the monitoring dimension is a comprehensive monitoring, the monitoring query condition includes a date and a customer code, and the warehouse configuration operation data that corresponds to the monitoring dimension and meets the monitoring query condition is determined from a database, including: and determining comprehensive monitoring data with the same date and customer codes as those in the query conditions from the database, wherein the comprehensive monitoring data comprises order completion conditions and order completion condition ranks of all warehouses of the customers corresponding to the customer codes.
In the embodiment of the application, when the monitoring dimension is comprehensive monitoring, comprehensive monitoring data with the same date and customer codes as those in the query condition can be determined from the database through the date and customer codes. The comprehensive monitoring data comprises the order completion conditions and the order completion condition ranking of all the warehouses of the client corresponding to the client codes, so that the client can master the operation condition of the subordinate warehouse within the date by adjusting the date in the monitoring query condition, and accurate operation condition data can be provided for the client.
With reference to the technical solution provided by the first aspect, in some possible implementation manners, the monitoring query condition further includes an upstream organization code, and the determining, from the database, the comprehensive monitoring data whose date and customer code are the same as the date and customer code in the query condition includes: and determining the comprehensive monitoring data with the same date and upstream organization code as the date and the upstream organization code to which the client code belongs in the query condition from the database.
In the embodiment of the application, by monitoring the upstream organization code and the date in the query condition, the comprehensive monitoring data with the date and the upstream organization code identical to the date and the upstream organization code to which the client code belongs in the query condition can be determined from the database, so that order completion conditions and order completion condition ranks of all warehouses owned by the clients of the plurality of client codes under the upstream organization code can be checked at the same time, the comprehensive monitoring data corresponding to each client code does not need to be queried independently, and the client time is saved.
With reference to the technical solution provided by the first aspect, in some possible implementation manners, the monitoring dimension is not shipped, the monitoring query condition includes a customer code, and the warehouse configuration operation data that corresponds to the monitoring dimension and meets the monitoring query condition is determined from a database, including: and determining non-shipment monitoring data which has the same customer code as the customer code in the query condition and is not shipped before the query time point from the database, wherein the non-shipment monitoring data comprises all non-shipped order conditions of the customer corresponding to the customer code before the query time point.
In the embodiment of the application, when the monitoring dimension is undelivered, undelivered monitoring data which is undelivered before the query time point and has the same customer code as the customer code in the query condition can be determined from the database through the customer code. Because the undelivered monitoring data comprises all the undelivered order conditions of the client corresponding to the client code before the query time point, the client can quickly master all the undelivered order conditions of the client, and the convenience is enhanced.
With reference to the technical solution provided by the first aspect, in some possible implementation manners, the monitoring query condition further includes an upstream organization code, and determining, from the database, non-shipment monitoring data that is the same as the client code in the query condition and is not shipped before the query time point, where the non-shipment monitoring data includes: and determining non-shipment monitoring data which is the same as the upstream organization code to which the client code belongs in the query condition and is not shipped before the query time point from the database.
In the embodiment of the application, by monitoring the upstream organization code in the query condition, the un-shipped monitoring data with the upstream organization code being the same as the upstream organization code to which the client code in the query condition belongs can be determined from the database, so that all un-shipped order conditions of the clients of the plurality of client codes under the upstream organization code before the query time point can be queried simultaneously, the comprehensive monitoring data corresponding to each client code does not need to be queried independently, and the client time is saved.
With reference to the technical solution provided by the first aspect, in some possible implementation manners, the monitoring dimension is daily broadcast, the query condition includes a date and a customer code, and the warehouse configuration operation data that corresponds to the monitoring dimension and meets the monitoring query condition is determined from a database, including: and determining daily broadcast monitoring data with the same date and customer codes as those in the query conditions from the database, wherein the daily broadcast monitoring data comprise the order states of the customers within the date.
In the embodiment of the application, when the monitoring dimension is daily broadcast, the daily broadcast monitoring data with the date and the client code identical to the date and the client code in the query condition can be determined from the database through the date and the client code. And the daily broadcast monitoring data is included in the date, the order state of the client is convenient for the user to master the self condition in real time, and the user experience is improved.
With reference to the technical solution provided by the first aspect, in some possible implementation manners, the monitoring query condition further includes an upstream organization code, and the broadcasting-on-day monitoring data whose date and customer code are the same as the date and customer code in the query condition is determined from the database includes: and determining the daily broadcast monitoring data with the same date and upstream organization code as the date and the upstream organization code to which the client code belongs in the query condition from the database.
In the embodiment of the application, by monitoring the upstream organization code and the date in the query condition, the date and the date of the upstream organization code, which are the same as the date in the query condition and the upstream organization code to which the client code belongs, can be determined from the database to broadcast the monitoring data, so that the order states of all warehouses owned by the clients of the client codes under the upstream organization code in the date can be queried simultaneously, the comprehensive monitoring data corresponding to each client code does not need to be queried independently, and the client time is saved.
With reference to the technical solution provided by the first aspect, in some possible implementation manners, an organization management label is further displayed on the display interface, and the method further includes: responding to the operation of clicking the organization management tag by a user, and displaying a corresponding window page, wherein the window page comprises whether a quality report is combined with an option box, a customer code and an upstream organization code; responding to the operation of a user on whether the quality report is combined with the option box, combining the warehouse matching operation data corresponding to the client codes with the same upstream organization codes when the user selects to combine the quality report, and storing the combined warehouse matching operation data in the database; and when the user selects not to combine the quality report, counting the warehouse matching operation data with the same client code, and storing the acquired warehouse matching operation data in the database.
In the embodiment of the application, when a user selects to merge quality reports in a quality report merging option frame in a window page, the system merges warehouse matching operation data corresponding to client codes with the same upstream organization codes, stores the merged warehouse matching operation data in the database, counts the warehouse matching operation data with the same client codes when the user selects not to merge quality reports in a quality report merging option frame in a viewing window, and stores the obtained warehouse matching operation data in the database. The client can select whether quality report merging is needed or not according to the self requirement, more choices are provided for the client, the user experience is improved, and the application range of the scheme is enlarged.
In a second aspect, an embodiment of the present application provides an information query apparatus, including a receiving module and a query module, where the receiving module is configured to receive a query request about a warehouse configuration operation condition, which is input by a user on a display interface, where the query request includes a monitoring dimension and a monitoring query condition, and the monitoring dimension is one of comprehensive monitoring, non-shipping, and daily broadcast displayed in the display interface; and the query module is used for determining and displaying the warehouse configuration operation data which corresponds to the monitoring dimensionality and accords with the monitoring query condition from a database.
In a third aspect, an embodiment of the present application provides an electronic device, including: a memory and a processor, the memory and the processor connected; the memory is used for storing programs; the processor is configured to invoke a program stored in the memory to perform the method according to the embodiment of the first aspect and/or any possible implementation manner in combination with the embodiment of the first aspect.
In a fourth aspect, embodiments of the present application provide a storage medium, on which a computer program is stored, where the computer program, when executed by a computer, performs a method as described in the embodiments of the first aspect and/or any possible implementation manner in combination with the embodiments of the first aspect.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic flowchart of an information query method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a display interface according to an embodiment of the present disclosure;
FIG. 3 is a schematic view of a viewing window shown in an embodiment of the present application;
FIG. 4 is a diagram illustrating a report configuration window according to an embodiment of the present application;
fig. 5 is a schematic view of a display interface for comprehensive monitoring in monitoring dimension according to an embodiment of the present application;
FIG. 6 is a schematic diagram of a display interface with undelivered monitoring dimensions according to an embodiment of the present application;
fig. 7 is a schematic view of a display interface for daily reporting of monitoring dimensions according to an embodiment of the present application;
fig. 8 is a block diagram illustrating a structure of an information query apparatus according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solution of the present application will be clearly and completely described below with reference to the accompanying drawings.
Referring to fig. 1, fig. 1 is a data query method according to an embodiment of the present application, and the steps included in the data query method will be described with reference to fig. 1.
Step S100: receiving a query request about the warehousing operation condition input by a user on a display interface, wherein the query request comprises a monitoring dimension and a monitoring query condition.
Receiving an inquiry request about the warehouse distribution operation condition input by a user on a display interface, wherein the inquiry request comprises a monitoring dimension and a monitoring inquiry condition, the monitoring dimension is one of comprehensive monitoring, non-shipping and daily broadcasting displayed in the display interface, namely the comprehensive monitoring, the non-shipping and the daily broadcasting are displayed in the same display interface, and the monitoring inquiry condition is not completely the same according to different monitoring dimensions.
In an embodiment, as shown in fig. 2, one embodiment of the display interface may be selected from comprehensive monitoring, non-shipping, and daily broadcast according to a requirement in the monitoring dimension option box, and after the monitoring dimension is selected, the monitoring query condition may be input in the monitoring query condition input box located at the same horizontal position as the monitoring dimension option box. Because the comprehensive monitoring, the non-shipping and the daily broadcasting in the monitoring dimension are all positioned on the same interface, the interface does not need to be replaced when the warehouse configuration operation data with different dimensions are inquired, the operation flow of a user is reduced, the time of the user is saved, and the user experience is improved. The example is provided only as one embodiment of the present application and should not be construed as limiting the present application.
Before step S100, a client that needs to be monitored is also configured, and data of three dimensions of comprehensive monitoring, non-delivery and daily broadcast of the client that needs to be monitored is stored in a database and is directly called when querying.
Optionally, before receiving a query request about the warehousing operation condition input by a user on the display interface, the corresponding window page is displayed by clicking an organization management tag of the display interface, where the window page includes whether the quality report is merged with the option box, the customer code, and the upstream organization code. When a user selects to merge quality reports in the option boxes for merging quality reports in the viewing window, the system merges the warehouse matching operation data corresponding to the client codes with the same upstream organization codes, and stores the merged warehouse matching operation data in the database, and when the user selects not to merge quality reports in the option boxes for merging quality reports in the viewing window, the system counts the warehouse matching operation data with the same client codes and stores the obtained warehouse matching operation data in the database.
In one embodiment, the window interface is as shown in fig. 3, the user clicks on organization management of the display interface, the window interface as shown in fig. 3 is displayed, the user can modify the upstream organization code of the client code according to the "upstream organization system code" in the window interface, whether to merge the data of the client with the same upstream organization code is determined by "whether to merge quality reports", if the user selects "yes", the data of the client with the same upstream organization code is merged, and if the user selects "no", the data of the client with the same upstream organization code is not merged. The example is provided only as one embodiment of the present application and should not be construed as limiting the present application.
Optionally, because the requirements of the customers are not completely the same, the customer codes can be configured individually according to the requirements of the customers, wherein the warehouses under the customer codes can be removed, for example, when the user does not examine the data of the generation operation warehouse, the corresponding warehouses can be removed; the user can select the type of the monitored order, for example, when the user only needs to monitor the B2B (Business-to-Business) delivery order, the B2B delivery order can be monitored; the user may select the carrier to monitor, for example, when the user may only monitor carrier a. In one embodiment, a report configuration window configured individually according to a client code according to a client's requirement is shown in fig. 4, and a user may click a report configuration button on a display interface to obtain the report configuration window shown in fig. 4, then click a new button, input a client name in a client name input box, input a configuration type in a configuration name input box, input a configuration code in a configuration code input box, and input a configuration warehouse name in a configuration type input box, thereby completing configuration. The example is provided only as one embodiment of the present application and should not be construed as limiting the present application.
Step S200: and determining and displaying the warehouse configuration operation data which corresponds to the monitoring dimension and accords with the monitoring query condition from the database.
And determining the warehouse configuration operation data which corresponds to the monitoring dimension and accords with the monitoring query condition from the database, and displaying the warehouse configuration operation data. Because the monitoring query conditions of different monitoring dimensions are not completely the same, the finally obtained warehouse configuration operation data are also different.
In one embodiment, when the monitoring dimension is the integrated monitoring, the monitoring query condition includes a date and a customer code, and the warehouse configuration operation data corresponding to the monitoring dimension and conforming to the monitoring query condition is determined from the database, including: and determining comprehensive monitoring data with the same date and the same client code as those in the query condition from the database, wherein the comprehensive monitoring data comprises order completion conditions and order completion condition ranks of all warehouses of the client corresponding to the client code.
In one embodiment, the date in the monitoring query condition may be a date including a year and a month, and the comprehensive monitoring data obtained based on the date encodes the order completion and the order completion ranking of all warehouses corresponding to the month represented by the date of the customer for the customer. Wherein, when the inquiry time is within the month included in the date, the integrated monitoring data from the first day of the month to the inquiry time is obtained. For example, when the date of the query condition is 2020-12, the aggregate monitoring data obtained based on that date encodes the order completion and order completion ranking for the customer for all of the warehouses of the customer in 12 months of 2020. Wherein, when the query time is 2020-12-15, the obtained comprehensive monitoring data is all the data from 2020-12-01 to 2020-12-15.
Optionally, the date in the monitoring query condition may also be a time period including a start date and an end date, and the comprehensive monitoring data obtained based on the date encodes the order completion and the order completion ranking of all warehouses corresponding to the customer between the start date and the end date for the customer. For example, the start date is 2020-12-03 and the end date is 2020-12-25, the obtained comprehensive monitoring data is all the data from 2020-12-03 to 2020-12-25. The start date and the end date can be any dates, but the start date is required to be before the end date so as to obtain the comprehensive monitoring data corresponding to the dates.
In one implementation mode, after a customer code is input, the system obtains the customer code, obtains a customer name corresponding to the customer code from a database, and displays the customer name in a customer code input box, so that the situation that the comprehensive monitoring data of other customers is obtained due to errors generated when the customer code is input is avoided. Optionally, after the customer code is input, the customer code may be displayed in the customer code, or the customer code and the customer name corresponding to the customer code may be displayed at the same time.
In one embodiment, when the monitoring dimension is integrated monitoring, the monitoring query further includes an upstream organization code, and the integrated monitoring data having the same date and customer code as the date and customer code in the query is determined from the database, including: and determining the date and the upstream organization code from the database, and the integrated monitoring data of the date and the upstream organization code to which the client code belongs in the query condition. For example, customer a has customer code a, and customer a has 5 warehouses a1, a2, A3, a4, a5, wherein customer code a1 is a1 and upstream organization code a; the client code of A2 is a, and the upstream organization code is a; the client code of A3 is a2, the upstream organization code is a; the client code of A4 is a3, the upstream organization code is a; the client code of A5 is a, and the upstream organization code is a; then the consolidated monitoring data includes data for a1, a2, A3, a4, a5 when the upstream organization in the monitoring query is encoded as a. When the client code in the monitoring query condition is a, the integrated monitoring data includes data of A2 and A5. The example is provided only as one embodiment of the present application and should not be construed as limiting the present application.
In one embodiment, the upstream organization code may be an option box, and after the user selects the upstream organization code, after the customer code input by the customer code input box, the operation monitoring data corresponding to the upstream organization code to which the customer code belongs is determined from the database and displayed. Alternatively, a separate input box is provided for upstream tissue encoding.
In one embodiment, a display interface with integrated monitoring and control dimensions is shown in fig. 5, in which an "upstream organization code" checkbox, a date input box, a customer code input box, a "reset" button, and a "query" button are disposed in the horizontal direction of a monitoring and control dimension selection box. And after the monitoring dimension selects the comprehensive monitoring, respectively inputting a date and a customer code in a date input box and a customer code input box, and displaying a customer name corresponding to the input customer code after the system identifies the customer code. The comprehensive monitoring data comprises the name of the warehouse of the client, the area of each warehouse, the daily peak value of each hundred square meters area, the ranking of each warehouse, the total number of orders, cancel orders, valid orders, order changes and the like. The example is provided only as one embodiment of the present application and should not be construed as limiting the present application.
When the monitoring dimension is not shipped, the monitoring query condition comprises a client code, the warehouse configuration operation data which corresponds to the monitoring dimension and accords with the monitoring query condition is determined from the database, and the method comprises the following steps: and determining non-delivery monitoring data before the query time point, wherein the customer code is the same as the customer code in the query condition, and the non-delivery monitoring data comprises all non-delivery order conditions of the customer corresponding to the customer code before the query time point.
In one embodiment, when the user queries the non-shipment monitoring data, the time does not need to be input by the user, and the system defaults to query the data of all non-shipment orders at the current time point, or in another embodiment, when the monitoring dimension is non-shipment, the monitoring query condition further includes time, and when the user queries the non-shipment monitoring data based on the time and the client code, the conditions of all non-shipment orders before the time are obtained. When the accuracy is "day", the user needs to input time information including year, month and day, and the unserviceable monitoring data inquired based on the time is data of all unserviceable orders at the end of the day of the input time. For example, when the input time is 2020-12-05, i.e. 12/5/2020, the non-shipment monitoring data is queried as the data of all non-shipment orders at the end of 2020-12-05, where the end may be the time of next work or 23 hours, 59 minutes and 59 seconds of the day. Similarly, the case of the accuracy "time", "minute" and "second" is similar to the above accuracy "day", and is not described herein again.
In one embodiment, when the monitoring dimension is not shipped, the monitoring query further includes an upstream organization code, and the un-shipped monitoring data before the query time point, in which the client code is the same as the client code in the query, is determined from the database, including: and determining the un-shipped monitoring data of which the upstream organization code is the same as the upstream organization code to which the client code in the query condition belongs from the database. The implementation manner of the upstream organization code is consistent with that of the monitoring dimension when the monitoring dimension is comprehensive monitoring, and details are not repeated here.
In one embodiment, the display interface with the monitoring dimension of non-shipment is shown in fig. 6, and an "upstream organization code" checkbox, a date input box, a customer code input box, a "reset" button, and a "query" button are arranged in the horizontal direction of the monitoring dimension selection box. And when the monitoring dimension is not shipped, respectively inputting a date and a customer code in a date input box and a customer code input box, and displaying a customer name corresponding to the input customer code after the system identifies the customer code. Wherein the non-shipment monitoring data includes the name of the customer's warehouse, and the total number of orders per warehouse, order changed, picked, transport non-loaded, warehouse non-operational orders, warehouse transport non-operational orders. The example is provided only as one embodiment of the present application and should not be construed as limiting the present application.
When the monitoring dimension is daily broadcast, the query condition comprises date and customer code, the warehouse configuration operation data which corresponds to the monitoring dimension and accords with the monitoring query condition is determined from the database, and the method comprises the following steps: and determining daily broadcast monitoring data with the date and the client code identical to the date and the client code in the query condition from a database, wherein the daily broadcast monitoring data comprise the order state of the client in the date. The date in the monitoring query condition is the date including year, month and day, the user needs to input the time information including year, month and day, and the state of all orders of the client is reported at the end of the day when the date queried based on the time is the input time. For example, when the input time is 2020-12-05, that is, when 2020 is given 12/5/2020, the inquired daily broadcast monitoring data is the status of all orders at the end of 2020-12-05, where the end may be the next shift time or 23 hours, 59 minutes and 59 seconds of the day. When inquiring the broadcasting data of the day, the state of all orders of the corresponding clients of the client code from the beginning of the day to the inquiring time point is obtained, wherein the beginning can be the working hour of the day or 00 minutes and 00 seconds when the day is 00.
In one embodiment, when the monitoring dimension is daily broadcast, the monitoring query condition further includes an upstream organization code, and daily broadcast monitoring data whose date and client code are the same as the date and client code in the query condition is determined from the database, including: and determining the daily broadcast monitoring data with the date and the upstream organization code identical to the date and the upstream organization code to which the client code belongs in the query condition from the database. The implementation manner of the upstream organization code is consistent with that of the monitoring dimension when the monitoring dimension is comprehensive monitoring, and details are not repeated here.
In one embodiment, a display interface for daily broadcast of the monitoring dimension is shown in fig. 7, and an "upstream organization code" checkbox, a date input box, a customer code input box, a "reset" button, and a "query" button are arranged in the horizontal direction of the monitoring dimension selection box. And after the monitoring dimension selects daily broadcasting, respectively inputting a date and a customer code in a date input box and a customer code input box, and displaying a customer name corresponding to the input customer code after the system identifies the customer code. The daily broadcast monitoring data comprises the name of the warehouse of the client, and the total number of orders, cancel orders, valid orders, change orders, sent orders and picked orders of each warehouse. The example is provided only as one embodiment of the present application and should not be construed as limiting the present application.
Referring to fig. 8, fig. 8 is a diagram illustrating an information query apparatus 100 according to an embodiment of the present disclosure, which includes a receiving module 110 and a query module 120.
A receiving module 110, configured to receive an inquiry request about a warehouse configuration operation condition, input by a user on a display interface, where the inquiry request includes a monitoring dimension and a monitoring inquiry condition, and the monitoring dimension is one of comprehensive monitoring, non-shipping, and daily broadcast displayed in the display interface;
and the query module 120 is configured to determine, from a database, the warehouse configuration operation data that corresponds to the monitoring dimension and meets the monitoring query condition, and display the warehouse configuration operation data.
The query module 120 is further configured to determine, when the monitoring dimension is the comprehensive monitoring, comprehensive monitoring data with a date and a client code that are the same as the date and the client code in the query condition from the database, where the comprehensive monitoring data includes order completion conditions and order completion condition ranks of all warehouses of the client corresponding to the client code.
The query module 120 is further configured to determine, when the monitoring dimension is integrated monitoring, integrated monitoring data with the same date and upstream organization code as the date in the query condition and the upstream organization code to which the client code belongs from the database.
The query module 120 is further configured to determine, when the monitoring dimension is not shipped, non-shipped monitoring data that is not shipped before the query time point and has a customer code that is the same as the customer code in the query condition from the database, where the non-shipped monitoring data includes all non-shipped order conditions of the customer corresponding to the customer code before the query time point.
The query module 120 is further configured to determine, when the monitoring dimension is not shipped, non-shipped monitoring data that is not shipped before the query time point and has an upstream organization code that is the same as the upstream organization code to which the client code in the query condition belongs from the database.
The query module 120 is further configured to determine, when the monitoring dimension is daily broadcast, daily broadcast monitoring data with a date and a client code that are the same as the date and the client code in the query condition from the database, where the daily broadcast monitoring data includes an order state of the client within the date.
The query module 120 is further configured to determine, when the monitoring dimension is daily broadcast, daily broadcast monitoring data whose date and upstream organization code are the same as the date in the query condition and the upstream organization code to which the client code belongs from the database.
The receiving module 110 is further configured to respond to an operation of clicking the organization management tag by a user, and display a corresponding window page, where the window page includes whether the quality report merges an option box, a customer code, and an upstream organization code; responding to the operation of a user on whether the quality report is combined with the option box, combining the warehouse matching operation data corresponding to the client codes with the same upstream organization codes when the user selects to combine the quality report, and storing the combined warehouse matching operation data in the database; and when the user selects not to combine the quality report, counting the warehouse matching operation data with the same client code, and storing the acquired warehouse matching operation data in the database.
The information query apparatus 100 according to the embodiment of the present application has the same implementation principle and technical effect as those of the foregoing method embodiments, and for brevity, reference may be made to the corresponding contents in the foregoing method embodiments for the parts that are not mentioned in the apparatus embodiments.
Please refer to fig. 9, which is an electronic device 200 according to an embodiment of the present disclosure. The electronic device 200 includes: a transceiver 210, a memory 220, a communication bus 230, and a processor 240.
The elements of the transceiver 210, the memory 220, and the processor 240 are electrically connected to each other directly or indirectly to achieve data transmission or interaction. For example, the components may be electrically coupled to each other via one or more communication buses 230 or signal lines. The transceiver 210 is used for transceiving data. The memory 220 is used for storing a computer program, such as the software functional module shown in fig. 8, i.e., the information inquiry apparatus 100. The information query apparatus 100 includes at least one software function module, which may be stored in the memory 220 in the form of software or firmware (firmware) or solidified in an Operating System (OS) of the electronic device 200. The processor 240 is configured to execute an executable module stored in the memory 220, such as a software functional module or a computer program included in the information query apparatus 100. For example, receiving an inquiry request about a warehousing operation condition input by a user on a display interface, wherein the inquiry request comprises a monitoring dimension and a monitoring inquiry condition, and the monitoring dimension is one of comprehensive monitoring, non-shipping and daily broadcasting displayed in the display interface; and determining and displaying the warehouse configuration operation data which corresponds to the monitoring dimension and accords with the monitoring query condition from a database.
The Memory 220 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like.
The processor 240 may be an integrated circuit chip having signal processing capabilities. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor 240 may be any conventional processor or the like.
The electronic device 200 includes, but is not limited to, a personal computer, a server, and the like.
The present embodiment also provides a non-volatile computer-readable storage medium (hereinafter, referred to as a storage medium), where the storage medium stores a computer program, and the computer program is executed by the electronic device 200 as described above to perform the data query method described above.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (11)
1. A method for querying data, comprising:
receiving an inquiry request about a warehousing operation condition input by a user on a display interface, wherein the inquiry request comprises a monitoring dimension and a monitoring inquiry condition, and the monitoring dimension is one of comprehensive monitoring, non-shipping and daily broadcasting displayed in the display interface;
and determining and displaying the warehouse configuration operation data which corresponds to the monitoring dimension and accords with the monitoring query condition from a database.
2. The data query method of claim 1, wherein the monitoring dimension is a comprehensive monitoring, the monitoring query condition includes a date and a customer code, and the warehousing operation data corresponding to the monitoring dimension and conforming to the monitoring query condition is determined from a database, and includes:
and determining comprehensive monitoring data with the same date and customer codes as those in the query conditions from the database, wherein the comprehensive monitoring data comprises order completion conditions and order completion condition ranks of all warehouses of the customers corresponding to the customer codes.
3. The data query method of claim 2, wherein said monitoring query further comprises an upstream organization code, and determining from said database integrated monitoring data having a date and customer code identical to said date and said customer code in said query comprises:
and determining the comprehensive monitoring data with the same date and upstream organization code as the date and the upstream organization code to which the client code belongs in the query condition from the database.
4. The data query method of claim 1, wherein the monitoring dimension is not shipped, the monitoring query condition includes a customer code, and the step of determining the warehouse operation data corresponding to the monitoring dimension and conforming to the monitoring query condition from a database includes:
and determining non-shipment monitoring data which has the same customer code as the customer code in the query condition and is not shipped before the query time point from the database, wherein the non-shipment monitoring data comprises all non-shipped order conditions of the customer corresponding to the customer code before the query time point.
5. The method of claim 4, wherein the monitoring query further comprises an upstream organization code, and the non-shipment monitoring data that is determined from the database and has a customer code that is the same as the customer code in the query and has not been shipped before the query time point comprises:
and determining non-shipment monitoring data which is the same as the upstream organization code to which the client code belongs in the query condition and is not shipped before the query time point from the database.
6. The data query method according to claim 1, wherein the monitoring dimension is daily broadcast, the query condition includes a date and a customer code, and the warehouse configuration operation data corresponding to the monitoring dimension and conforming to the monitoring query condition is determined from a database, and includes:
and determining daily broadcast monitoring data with the same date and customer codes as those in the query conditions from the database, wherein the daily broadcast monitoring data comprise the order states of the customers within the date.
7. The data query method of claim 6, wherein the monitoring query further comprises an upstream organization code, and determining from the database that the date and customer code are the same as the date and customer code in the query comprises:
and determining the daily broadcast monitoring data with the same date and upstream organization code as the date and the upstream organization code to which the client code belongs in the query condition from the database.
8. The data query method of claim 1, wherein an organization management label is further displayed on the display interface, and the method further comprises:
responding to the operation of clicking the organization management tag by a user, and displaying a corresponding window page, wherein the window page comprises whether a quality report is combined with an option box, a customer code and an upstream organization code;
responding to the operation of a user on whether the quality report is combined with the option box, combining the warehouse matching operation data corresponding to the client codes with the same upstream organization codes when the user selects to combine the quality report, and storing the combined warehouse matching operation data in the database;
and when the user selects not to combine the quality report, counting the warehouse matching operation data with the same client code, and storing the acquired warehouse matching operation data in the database.
9. An information inquiry apparatus, comprising:
the system comprises a receiving module, a processing module and a display module, wherein the receiving module is used for receiving an inquiry request about the warehouse allocation operation condition input on a display interface by a user, the inquiry request comprises a monitoring dimension and a monitoring inquiry condition, and the monitoring dimension is one of comprehensive monitoring, non-shipping and daily broadcasting displayed in the display interface;
and the query module is used for determining and displaying the warehouse configuration operation data which corresponds to the monitoring dimensionality and accords with the monitoring query condition from a database.
10. An electronic device, comprising: a memory and a processor, the memory and the processor connected;
the memory is used for storing programs;
the processor to invoke a program stored in the memory to perform the method of any of claims 1-8.
11. A storage medium having stored thereon a computer program which, when executed by a computer, performs the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110101995.0A CN112883243A (en) | 2021-01-25 | 2021-01-25 | Data query method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110101995.0A CN112883243A (en) | 2021-01-25 | 2021-01-25 | Data query method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112883243A true CN112883243A (en) | 2021-06-01 |
Family
ID=76051876
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110101995.0A Pending CN112883243A (en) | 2021-01-25 | 2021-01-25 | Data query method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112883243A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090177988A1 (en) * | 2008-01-08 | 2009-07-09 | International Business Machines Corporation | Generating data queries using a graphical selection tree |
| CN101599087A (en) * | 2009-07-02 | 2009-12-09 | 金蝶软件（中国）有限公司 | Data enquire method and device |
| US20180032574A1 (en) * | 2016-07-31 | 2018-02-01 | Appdynamics Llc | Dynamic Streaming of Results of Multi-Leveled Queries |
| CN108959291A (en) * | 2017-05-19 | 2018-12-07 | 腾讯科技（深圳）有限公司 | Querying method and relevant apparatus |
| CN109359123A (en) * | 2018-08-24 | 2019-02-19 | 周宁 | A kind of inquiry of operation data and analysis system and method |
| CN110489632A (en) * | 2019-07-23 | 2019-11-22 | 平安科技（深圳）有限公司 | Related information querying method and device |
| CN112181993A (en) * | 2020-10-27 | 2021-01-05 | 广州市网星信息技术有限公司 | Service data query method, device, server and storage medium |
-
2021
- 2021-01-25 CN CN202110101995.0A patent/CN112883243A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090177988A1 (en) * | 2008-01-08 | 2009-07-09 | International Business Machines Corporation | Generating data queries using a graphical selection tree |
| CN101599087A (en) * | 2009-07-02 | 2009-12-09 | 金蝶软件（中国）有限公司 | Data enquire method and device |
| US20180032574A1 (en) * | 2016-07-31 | 2018-02-01 | Appdynamics Llc | Dynamic Streaming of Results of Multi-Leveled Queries |
| CN108959291A (en) * | 2017-05-19 | 2018-12-07 | 腾讯科技（深圳）有限公司 | Querying method and relevant apparatus |
| CN109359123A (en) * | 2018-08-24 | 2019-02-19 | 周宁 | A kind of inquiry of operation data and analysis system and method |
| CN110489632A (en) * | 2019-07-23 | 2019-11-22 | 平安科技（深圳）有限公司 | Related information querying method and device |
| CN112181993A (en) * | 2020-10-27 | 2021-01-05 | 广州市网星信息技术有限公司 | Service data query method, device, server and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 张晶: "基于RFID的货物跟踪信息系统分析与设计", 中国优秀硕士学位论文全文数据库信息科技辑, pages 41 - 58 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6530518B1 (en) | Method, system and storage medium for viewing product delivery information | |
| US8290833B2 (en) | Multi-stage supply chain management system with dynamic order placement | |
| US7218980B1 (en) | Prediction based optimization of a semiconductor supply chain using an adaptive real time work-in-progress tracking system | |
| US7188075B1 (en) | Extended product configuration techniques | |
| CN117807065A (en) | Method, computing system and computer readable medium for determining data quality rules | |
| US10642812B1 (en) | Database system, computing device and method for message construction, processing and storage dependent upon satisfaction of predefined requirements | |
| CN104636933A (en) | Method and device for positioning oversell reasons of e-commerce website | |
| CN110796413A (en) | Cargo distribution method and device, storage medium and electronic equipment | |
| KR102523860B1 (en) | Method for providing customized smart order service of food material required to order through forecasting consumption | |
| CN112364004B (en) | Data warehouse-based policy data processing method, device and storage medium | |
| KR20190073039A (en) | Shopping mall integrated management method and system | |
| US20210241357A1 (en) | Customizable and extensible managed integration platform | |
| US20050071207A1 (en) | Visibility and synchronization in a multi tier supply chain model | |
| US20230025466A1 (en) | System and method for optimizing transmission of requests for updated content from external data sources | |
| CN112883243A (en) | Data query method and device, electronic equipment and storage medium | |
| CN109377391B (en) | Information tracking method, storage medium and server | |
| US20140089146A1 (en) | System, method and apparatus for managing pharmacy inventories | |
| CN110659859A (en) | E-commerce order inventory ERP management method and system | |
| KR20200094991A (en) | System for trading commodity in shopping mall and control method thereof | |
| CN113706254A (en) | Online material management method, device and equipment based on bill and storage medium | |
| CN113191853A (en) | Networked multi-terminal interactive price searching and quotation processing method and system | |
| WO2021024205A1 (en) | Method and system of optimizing stock availability and sales opportunity | |
| US7877311B1 (en) | System and method for analyzing transactions at an electronic exchange | |
| WO2001099003A1 (en) | System and method for sourcing, purchasing and analysis across multiple commercial marketplace | |
| KR101450273B1 (en) | Selling statistics system and method for operating thereof |
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 |