CN111177302A - Business document processing method and device, computer equipment and storage medium - Google Patents
Business document processing method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111177302A CN111177302A CN201911300217.3A CN201911300217A CN111177302A CN 111177302 A CN111177302 A CN 111177302A CN 201911300217 A CN201911300217 A CN 201911300217A CN 111177302 A CN111177302 A CN 111177302A
- Authority
- CN
- China
- Prior art keywords
- version
- target
- fields
- service data
- type
- 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.)
- Granted
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 15
- 238000000034 method Methods 0.000 claims abstract description 30
- 238000012508 change request Methods 0.000 claims abstract description 18
- 238000012545 processing Methods 0.000 claims abstract description 17
- 230000008859 change Effects 0.000 claims description 37
- 238000004590 computer program Methods 0.000 claims description 14
- 238000012217 deletion Methods 0.000 claims description 6
- 230000037430 deletion Effects 0.000 claims description 6
- 238000003780 insertion Methods 0.000 claims description 4
- 230000037431 insertion Effects 0.000 claims description 4
- 239000000463 material Substances 0.000 description 12
- 238000012384 transportation and delivery Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 11
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000000547 structure data Methods 0.000 description 5
- 238000006243 chemical reaction Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 3
- 230000008520 organization Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000002716 delivery method Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000012550 audit Methods 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000012795 verification Methods 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/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/31—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
- G06F16/24573—Query processing with adaptation to user needs using data annotations, e.g. user-defined metadata
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/288—Entity relationship models
-
- 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/31—Indexing; Data structures therefor; Storage structures
- G06F16/316—Indexing structures
- G06F16/322—Trees
-
- 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)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Library & Information Science (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a business document processing method, a business document processing device, computer equipment and a storage medium. The method comprises the following steps: receiving a data format change request of initial service data, wherein the initial service data is data corresponding to a target service receipt, and the initial service data comprises a plurality of fields and field values corresponding to the fields; forming a text object by each field and the corresponding field value; acquiring the hierarchical relationship among the fields in the target business document, and combining the text objects according to the hierarchical relationship among the fields to obtain combined text objects; and obtaining target service data corresponding to the initial service data according to the combined text object. By adopting the method, the data redundancy can be reduced.
Description
Technical Field
The present application relates to the field of data processing, and in particular, to a method and an apparatus for processing a business document, a computer device, and a storage medium.
Background
As computer technology has developed, various types of databases have been developed, such as relational databases and non-relational databases. More and more enterprises employ databases to store business documents, for example, ERP (enterprise resource Planning) systems employ physical tables and field columns of the databases to store ERP business documents, wherein the business documents may be sales orders, purchase orders and the like.
However, the data is stored by using the physical tables and the field columns of the database, so that the data is stored more dispersedly and tediously, and the data redundancy is high.
Disclosure of Invention
In view of the above, it is necessary to provide a business document processing method, an apparatus, a computer device, and a storage medium capable of reducing data redundancy in order to solve the above technical problem of high data redundancy.
A method for processing business documents, the method comprising: receiving a data format change request of initial service data, wherein the initial service data is data corresponding to a target service receipt, and the initial service data comprises a plurality of fields and field values corresponding to the fields; forming a text object by each field and the corresponding field value; acquiring the hierarchical relationship among the fields in the target business document, and combining the text objects according to the hierarchical relationship among the fields to obtain combined text objects; and obtaining target service data corresponding to the initial service data according to the combined text object.
In some embodiments, the text object is a key-value pair, and the combining each of the fields and the corresponding field value into a text object includes: respectively taking each field as a key, and taking the corresponding field value as a value to obtain a key value pair corresponding to each field; the acquiring the hierarchical relationship between the fields in the target business document, and combining the text objects according to the hierarchical relationship between the fields to obtain a combined text object includes: and acquiring the hierarchical relationship among the fields in the target business document, and combining the key value pairs by the hierarchical relationship among the fields to obtain a combined text object.
In some embodiments, the method further comprises: acquiring a preset field; taking the target service data as a field value corresponding to the preset field to establish a corresponding relation between the preset field and the target service data; and storing the target service data in the preset field.
In some embodiments, the target business data is a first version business data corresponding to the target business document, and the method further includes: receiving a version comparison request corresponding to the target business document, wherein the version comparison request carries a first version identifier and a second version identifier; responding to the version comparison request, extracting the combined text object from the target service data to be used as first version service data corresponding to the first version identification; splitting the combined text object into a plurality of objects according to the hierarchical relationship among the objects in the combined text object to obtain a first object tree; acquiring a second object tree corresponding to the second version identification; and comparing the difference between the first object tree and the second object tree to obtain a version comparison result of the target business receipt.
In some embodiments, the version comparison request further carries a version type corresponding to a version identifier, and the comparing the difference between the first object tree and the second object tree to obtain the version comparison result of the target business document includes: acquiring an object with difference in the first object tree and the second object tree as a target object; acquiring a first version type corresponding to the first version identification and a second version type corresponding to the second version identification; determining a change operation type corresponding to the target object according to the first version type and the second version type; and taking the target object and the version change operation type as version comparison results.
In some embodiments, the obtaining the object having the difference in the first object tree and the second object tree as the target object includes: acquiring an object only existing in the first object tree or the second object tree as a target object; the determining the change operation type corresponding to the target object according to the first version type and the second version type includes: when the first version type is a reference version type and the second version type is a comparison version type, determining that the change operation type corresponding to the target object only existing in the first object tree is a deletion operation type; and when the first version type is a reference version type and the second version type is a comparison version type, determining that the change operation type corresponding to the target object only existing in the second object tree is an insertion operation type.
In some embodiments, the obtaining a first version type corresponding to the first version identifier and a second version type corresponding to the second version identifier includes: receiving a reference version selection operation and a comparison version selection operation through a version change comparison interface; and taking the candidate version identification selected by the reference version selection operation as a first version identification, taking the first version type corresponding to the first version identification as a reference version type, taking the candidate version identification selected by the comparison version selection operation as a second version identification, and taking the second version type corresponding to the second version identification as a comparison version type.
A business document processing apparatus, the apparatus comprising: the data format change request receiving module is used for receiving a data format change request of initial service data, wherein the initial service data is data corresponding to a target service receipt, and the initial service data comprises a plurality of fields and field values corresponding to the fields; the text object composition module is used for composing each field and the corresponding field value into a text object; the combined text object obtaining module is used for obtaining the hierarchical relationship among the fields in the target business document and combining the text objects according to the hierarchical relationship among the fields to obtain a combined text object; and the target service data obtaining module is used for obtaining target service data corresponding to the initial service data according to the combined text object.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the business document processing method when executing the computer program.
A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the above-mentioned business document processing method.
The business receipt processing method, the device, the computer equipment and the storage medium receive a data format change request of initial business data, the initial business data is data corresponding to a target business receipt, the initial business data comprises a plurality of fields and field values corresponding to the fields, each field and the corresponding field values form a text object, the hierarchical relationship among the fields in the target business receipt is obtained, each text object is combined according to the hierarchical relationship among the fields to obtain a combined text object, and the target business data corresponding to the initial business data is obtained according to the combined text object.
Drawings
FIG. 1 is a diagram of an application scenario of a business document processing method in some embodiments;
FIG. 2A is a schematic flow chart diagram of a method for processing a business document in some embodiments;
FIG. 2B is a schematic illustration of a business document in some embodiments;
FIG. 2C is a schematic diagram of a business document processing method in some embodiments;
FIG. 2D is a diagram illustrating the resulting data packet in some embodiments;
FIG. 3 is a flow diagram of a method for processing a business document in some embodiments;
FIG. 4 is a flow diagram of a method for processing a business document in some embodiments;
FIG. 5A is a flowchart illustrating the step of obtaining version comparison results in some embodiments;
FIG. 5B is a diagram of a version change comparison interface in accordance with certain embodiments;
FIG. 5C is a diagram of a packet structure in some embodiments;
FIG. 6 is a flowchart illustrating the step of obtaining version comparison results in some embodiments;
FIG. 7 is a flowchart illustrating the step of obtaining version comparison results in some embodiments;
FIG. 8 is a flowchart illustrating the step of obtaining version comparison results in some embodiments;
FIG. 9 is a block diagram of a business document processing apparatus in some embodiments;
FIG. 10 is a diagram of the internal structure of a computer device in some embodiments.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The business document processing method provided by the application can be applied to the application environment shown in figure 1. The application environment includes a terminal 102 and a server 104. Wherein the terminal 102 communicates with the server 104 via a network. The server 104 is configured to manage a business document, and may be a server corresponding to a business document management system, where the business document management system may be an ERP system, and the business document may be a sales order, a purchase order, or the like. The server 104 may provide a web page or a client for accessing the server 104, and a service person of the service document management system may access the web page or the client corresponding to the server 104 through the terminal 102 and may operate on the web page or the client.
Specifically, the service person may access a web page or a client corresponding to the server 104 through the terminal 102, create a service document, modify the service document, and the like. The same business document may include multiple versions of the change. Generally, a business document often needs to be changed in the execution process, and each changed version needs to be stored in a file, and the changed document which passes the verification each time is a changed version. Generally, the changed versions are stored without modification and can be used for archiving, historical querying, and version comparison. The server 104 may perform format conversion on the initial service data corresponding to the changed version to obtain service data after format conversion, and store the service data after format conversion. The initial service data may include a plurality of fields and field values corresponding to the respective fields.
When a business person performs an operation of changing a version and storing a target business document on a webpage or a client corresponding to the server 104, the business person may trigger sending a data format change request to the server 104, where the data format change request may carry data corresponding to the target business document, that is, initial business data. The server 104 may receive the data format change request, and according to the data format change request, combine each field of the initial service data and the corresponding field value into a text object, may obtain a hierarchical relationship between fields in the service document, combine each text object according to the hierarchical relationship between fields to obtain a combined text object, and may obtain the service data after format conversion according to the combined text object. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In some embodiments, as shown in fig. 2A, a method for processing a business document is provided, which is described by taking the method as an example applied to the server 104 in fig. 1, and includes the following steps:
s202, receiving a data format change request of initial service data, wherein the initial service data is data corresponding to a target service receipt, and the initial service data comprises a plurality of fields and field values corresponding to the fields.
Specifically, the document refers to a carrier for carrying business data of an enterprise in an enterprise ERP system. For example, sales orders and purchase orders, etc. The target business document is the business document needing data format change. The business document may include a number of fields, such as document type, document number, business type, document status, and delivery method.
In some embodiments, a sheet may include a sheet head, a sheet body, and a sub-sheet body. The number of the document heads can be one or more, as shown in fig. 2B, showing the sales order, wherein there are 2 document heads, which are the basic information and the financial information respectively. The document header may correspond to a plurality of fields, for example, the basic information in fig. 2B may include fields of document type, document number, date, service type, sales organization, and delivery method. The document body may include a plurality of fields, for example, the document body in fig. 2B may include fields such as a serial number, a material code, and a material name, and the document body may further include a plurality of entries, as shown in fig. 2B, 3 entries are shown in total, which are an entry corresponding to a serial number 1, an entry corresponding to a serial number 2, and an entry corresponding to a serial number 3, respectively. The sub-bill bodies can be bill bodies corresponding to the entries. As shown in fig. 2B, the sub-sheet body corresponds to the entry with serial number 2. One entry may correspond to a plurality of sub-document bodies.
In some embodiments, the initial service data may be a service data packet corresponding to the target service document, and the service data packet may be, for example, a dynamic object and metadata structure data packet. Wherein, the dynamic object represents a dynamic object data packet, wherein, the object refers to a business document and includes related data of the business document, such as fields and field values in the business document. Since the structure, the number of fields, and the field attributes of different business documents may be different, the data packet storing the business document is called a dynamic object data packet. The business data packet can be bound with the control of the bill interface, so that the bill interface can display the data in the business data packet on the control corresponding to the interface. When a document is updated in a document interface, for example, operations such as modification, saving, submission, and auditing, the service data packet corresponding to the document is updated in the same way. The data package includes a data structure hierarchy relationship and a key-value pair data set. The metadata structure refers to physical structure information of all fields in the business document, and comprises the relationship and the hierarchical structure between the fields, such as the hierarchical relationship of a document head, a document body, a sub-document body and the like.
In some embodiments, when a service person accesses a page corresponding to the server through the terminal, modifies the service document, and clicks a version change generation button on the page, a data format change request may be triggered.
S204, the text objects are formed by the fields and the corresponding field values.
In particular, a text object may include one field and one field value. For example, if the initial service data includes a field a and a field B, where the field value corresponding to the field a is a, and the field value corresponding to the field B is B, the field a and the field value a may be combined to obtain a text object, which may be expressed as { a: a }. The field B and the field value B may be combined to obtain a text object, which may be represented as { B: b }.
S206, acquiring the hierarchical relationship among the fields in the target business document, and combining the text objects according to the hierarchical relationship among the fields to obtain a combined text object.
Specifically, the combined text object is a combination of a plurality of text objects. The hierarchical relationship between fields refers to the membership between fields. For example, for the basic information in fig. 2B, the fields subordinate to the basic information include the fields of document type, document number, and sales organization. The relationship between the fields may be described in terms of parent-child relationships, e.g., the base information may be parent information, and the document type, document number, and sales organization are child information of the base information, respectively.
In some embodiments, the hierarchical relationship between fields defines for each field an identification of the corresponding superior field. Taking fig. 2B as an example, if the identifier of the basic information is key1, the identifier of the upper-level field corresponding to the document type may be defined as key 1.
In some embodiments, an identifier of an entry corresponding to a previous level may also be defined for the sub-document body in the hierarchical relationship between the fields, and the entry may refer to a row of records in the table. Taking fig. 2B as an example, if the identifier corresponding to the entry with the sequence number of 2 is key2, the identifier of the upper-level field corresponding to the sub-bill body may be defined as key 2.
In some embodiments, text objects corresponding to fields belonging to a hierarchy may be combined to obtain a combined text object. Taking the record with sequence number 1 in fig. 2B as an example, the available text objects include { sequence number: 1}, { material code: XXX-001-000}, { Material name: pencil }, { specification type: a }, { sales number: 12} and { pricing unit: meta, since the 6 text objects belong to the same hierarchy, i.e. all belong to records with sequence number 1, the 6 text objects can be combined together to form a combined text object, which can be expressed, for example, as { sequence number: 1, material coding: XXX-001-000, Material name: the pencil, specification model: a, sales number: 12, pricing unit: element }.
In some embodiments, two different combined text objects may be combined to obtain a new combined text object. Taking the sub-document body in fig. 2B as an example, the text object corresponding to the entry with the sequence number 1 is { sequence number: 1, delivery quantity: 4, a sales factory: f1, delivery person: zhang three, the text object corresponding to entry with sequence number 2 is { sequence number: 2, delivery quantity: 4, a sales factory: f2, delivery person: li IV, the text object corresponding to the entry with sequence number 3 is { sequence number: 3, delivery quantity: 5, a sales factory: f3, delivery person: king five, the combined text object corresponding to the sub-document body can be expressed as { { serial number: 1, delivery quantity: 4, a sales factory: f1, delivery person: zhang three }, { sequence number: 2, delivery quantity: 4, a sales factory: f2, delivery person: lie four }, { sequence number: 3, delivery quantity: 5, a sales factory: f3, delivery person: five of king } }.
And S208, obtaining target service data corresponding to the initial service data according to the combined text object.
Specifically, the combined text object may be combined to obtain a new combined text object, and when the obtained combined text object includes all fields corresponding to the initial service data, the combined text object may be used as the target service data. The target service data can be stored locally or in other database servers.
In some embodiments, the combined text object may be used as the target service data corresponding to the initial service data. For example, the text objects corresponding to all the fields may be combined according to the hierarchical relationship between the fields to obtain a combined text object, and at this time, the combined text object may be used as the target service data corresponding to the initial service data.
In some embodiments, the combined text object may be Json text. The Json text is composed of key-value pairs with hierarchical relationships. For example, Json text { a: { b: { c:1} } }, wherein, if the key-value pair { c:1} is taken as the third layer, the key-value pair { b: { c:1} } is taken as the second layer, and the key-value pair { a: { b: { c:1} } } is taken as the first layer. As shown in fig. 2C, the modified version original data packet, the dynamic object, the service data packet, and the metadata structure data packet in the drawing refer to the same data packet, that is, refer to data packets corresponding to the target service document, that is, the initial service data. In fig. 2C, the initial traffic data is serialized into a Json text. The document interface displays corresponding background data as a metadata structure data packet, when the metadata structure data packet passes the audit, the metadata structure data packet can be serialized into a Json text for storage, the serialized Json text can be stored in one physical field, and complicated fields do not need to be stored separately one by one, so that the storage efficiency is improved, and the data redundancy is reduced. In addition, as shown in fig. 2C, when data of a certain version is displayed, the Json text can be deserialized into a data packet, and the data packet can be displayed by being bound as background data of a front-end interface, which is convenient and fast.
In the method for processing the service receipt, a data format change request of initial service data is received, the initial service data is data corresponding to a target service receipt, the initial service data comprises a plurality of fields and field values corresponding to the fields, each field and the corresponding field value form a text object, a hierarchical relationship among the fields in the target service receipt is obtained, the text objects are combined according to the hierarchical relationship among the fields to obtain a combined text object, and the target service data corresponding to the initial service data is obtained according to the combined text object.
Generally, an ERP business document has many fields (for example, hundreds of fields) as physical carriers for carrying business data information storage, and when the business document is stored, a physical table is generally required to be established in a database to store the business document. The physical table comprises a plurality of fields, and one field is used as a column of the physical table and is used for storing a field value corresponding to the field. However, the documents storing business by using physical tables and fields of the database are large, scattered and tedious, and each field is isolated, so that the structure and the relationship between the documents cannot be clearly reflected. When business documents stored in a database need to be acquired, for example, historical business documents or business documents of different versions are queried for comparison, as shown in fig. 2D, a database query script needs to be used to query and summarize data of all physical columns, however, the database query script usually involves many fields, resulting in a long script, and thus the query efficiency is low, resulting in poor performance. Therefore, it is inefficient to use physical tables to store and retrieve data related to business documents. By adopting the scheme of the embodiment of the application, the business document is stored without a huge physical table in a database, the data redundancy can be reduced, and the storage and acquisition efficiency of the business document can be improved.
In some embodiments, as shown in fig. 3, the text object is a key-value pair, and the step S204 is to combine each field and the corresponding field value into a text object, including:
s302, each field is used as a key, the corresponding field value is used as a value, and the key value pair corresponding to each field is obtained.
Specifically, a key-value pair includes a key (key) and a value (value), where the key serves as an index to the value. The key-value pair may take { key: value }. As shown in fig. 2B, for a field document number and a corresponding field value XXX001, a key value pair { document number: XXX001 }.
Step S306, acquiring the hierarchical relationship among the fields in the target business document, and combining the text objects according to the hierarchical relationship among the fields to obtain a combined text object, wherein the step S comprises the following steps:
s304, obtaining the hierarchical relation among the fields in the target business document, and combining the key value pairs through the hierarchical relation among the fields to obtain a combined text object.
Specifically, the key value pairs may be combined according to the hierarchical relationship between the keys in the key value pairs. For example, for a key-value pair { document type: standard sales order }, { document number: XXX001, since the previous level of the document type and the document number is the basic information, that is, the document type and the document number are fields of the same level, the document type: standard sales order }, { document number: XXX001} are combined.
According to the embodiment of the application, the fields and the corresponding field values are combined in a key value pair mode, the combination mode is simple, and the efficiency is high.
In some embodiments, as shown in fig. 4, the method further comprises:
s402, acquiring a preset field.
S404, the target service data is used as a field value corresponding to the preset field so as to establish a corresponding relation between the preset field and the target service data.
S406, storing the target service data in a preset field.
Specifically, the preset field may be preset according to a specific service scenario. The preset field can be used as a field of the target service data in the database, and the target service data is inserted into the database, so that the target service data is stored in one physical field, namely the initial service data is stored in one physical field.
According to the embodiment of the application, the corresponding relation between the preset field and the target business data is established, so that the preset field can be used as the field of the target business data in the database, and the target business data is inserted into the database, so that the data corresponding to the target business document is stored as a whole, the storage efficiency is improved, and the data redundancy is reduced.
In some embodiments, the target business data is a first version of business data corresponding to the target business document, as shown in fig. 5A, the method further includes:
s502, receiving a version comparison request corresponding to the target business document, wherein the version comparison request carries a first version identification and a second version identification.
Specifically, the target business document may correspond to multiple versions. And the version comparison request is used for requesting comparison of data of different versions of the target business document. The version identification is used for uniquely identifying the target business document of a specific version. The version identification may include a version number and a document encoding. The bill codes of different versions of the target business bill are the same, and the version numbers are different. As shown in the document version area in fig. 5B, 3 versions corresponding to a document whose document code is XXX-001 are shown, with version numbers 000, 001, and 003, respectively. The version designations are "000 and XXX-001", "001 and XXX-001", and "002 and XXX-001", respectively. And the bill codes of the target business bills corresponding to different business bills are different. For example, the document code for the sales order may be represented as XXX-002, the document code for the purchase order may be represented as XXX-012, and the document codes for the sales order and the purchase order may not be the same.
In some embodiments, the server may correspond to a version change comparison interface, and a service person may select any version on the version change comparison interface corresponding to the target service document to perform comparison, and trigger sending of a version comparison request corresponding to the target service document to the server. As shown in fig. 5B, a version change comparison interface corresponding to a document with document code XXX-001 is shown, a reference version may be selected in a document version area on the version change comparison interface, and then a view button corresponding to a non-reference version is clicked, for example, a document with version number 000 is selected as the reference version, and a view button corresponding to a document with version number 001 is clicked, so that the first version identifier may be "000 and XXX-001", and the second version identifier may be "001 and XXX-001", which means that a document with document code XXX-001 and version number 000 is compared with a document with document code XXX-001 and version number 001.
S504, responding to the version comparison request, extracting the combined text object from the target service data to be used as the first version service data corresponding to the first version identification.
Specifically, the server may obtain the version identifier in the version comparison request, find the corresponding target service data according to the version identifier, and obtain the combined object corresponding to the target service data as the version service data corresponding to the version identifier.
S506, splitting the combined text object into a plurality of objects according to the hierarchical relation among the objects in the combined text object to obtain a first object tree.
In particular, a tree is a data structure, and an object tree refers to a structure between objects that presents a tree structure. A combined text object may be split into multiple objects. For example, for a combined text object { sequence number: 1, material coding: XXX-001-000, Material name: pencil, including 3 fields and corresponding field values, since the hierarchy of 3 fields, i.e. sequence number, material code and material name, is the same, the hierarchy of 3 corresponding objects is also the same, so that the combined text object can be split into 3 objects, which are respectively a { sequence number: 1}, { material code: XXX-001-000} and { Material name: pencil }.
In some embodiments, the combined text object is a Json text, and the Json text may be split into a plurality of key-value pairs according to a hierarchical relationship between the key-value pairs in the Json text, where a key-value pair may be an object. As shown in fig. 2C, the Json text may be deserialized to obtain a service data packet with an object tree structure.
S508, a second object tree corresponding to the second version identification is obtained.
In some embodiments, the object tree structure is a structure of a service data packet corresponding to a service document, and as shown in fig. 5C, the structure of two different versions of service data packets is shown, where Head represents a document header, SubHead represents a sub-document header, Row1 represents an entry, and SubRow1 represents a sub-entry or sub-document body to which entry Row1 belongs. Row2 denotes another entry. Head may be represented as the root of the object tree, SubHead, Row1, and Row2 as the next level objects of the root, SubRow1 as the next level objects of Row 1.
And S510, comparing the difference between the first object tree and the second object tree to obtain a version comparison result of the target business document.
Specifically, the objects at the corresponding positions of the first object tree and the second object tree may be compared to obtain the difference between the first object tree and the second object tree, which is used as the version comparison result of the target business document.
In some embodiments, the objects in the object tree are key-value pairs, and the keys and values of the key-value pairs at the same position may be compared to determine the difference between the first object tree and the second object tree. For example, if the key-value pairs at the same position of the first object tree and the second object tree are { sales number, 20} and { sales number, 24} respectively, the values of the two key-value pairs are different.
In the embodiment of the application, when different versions of the target business document need to be compared, the corresponding object tree can be directly obtained according to the target business data for comparison, and the object tree does not need to be obtained according to a large number of isolated fields, so that the comparison efficiency of the business document data of different versions is improved. In addition, the business data packets are sequenced into a json form, so that the structural integrity and consistency of the historical version data are guaranteed, and the historical versions can be conveniently, quickly and efficiently stored, displayed and compared.
In some embodiments, the version comparison request further carries a version type corresponding to the version identifier, as shown in fig. 6, step S510 is to compare the difference between the first object tree and the second object tree, and obtaining the version comparison result of the target business document includes:
s602, acquiring the object with difference in the first object tree and the second object tree as the target object.
Specifically, the object having a difference may be an object existing in the first object tree and not existing in the second object tree, an object existing in the second object tree and not existing in the first object tree, or an object existing in the first object tree and the second object tree and having a different corresponding field or field value.
S604, a first version type corresponding to the first version identification and a second version type corresponding to the second version identification are obtained.
S606, determining the change operation type corresponding to the target object according to the first version type and the second version type.
In particular, the version type may include a reference version type and a comparison version type. The change operation type may include new, delete, and modify, etc. When the first version type is a reference version type and the second version type is a comparison version type, if the target object is an object existing in the first object tree and an object not existing in the second object tree, the change type corresponding to the target object is determined to be a deletion operation, if the target object is an object existing in the second object tree and an object not existing in the first object tree, the change type corresponding to the target object is determined to be an addition operation, and if the target object is an object existing in the first object tree and the second object tree and corresponding fields or field values are different, the change operation type corresponding to the target object may be a modification operation, for example, a field is modified or a field value is modified.
S608, the target object and the version change operation type are used as version comparison results.
Specifically, the version comparison result may be the addition of a target object, the deletion of a target object, or the modification of the content of a target object.
In the embodiment of the application, the version comparison result of the target business document is obtained by comparing the objects at the same position in different object trees, and the comparison mode is simple and the efficiency is high.
In some embodiments, as shown in fig. 7, the step S602 of acquiring the objects with differences in the first object tree and the second object tree as the target objects includes:
s702, acquiring the object only existing in the first object tree or the second object tree as the target object.
Step S606, determining the change operation type corresponding to the target object according to the first version type and the second version type includes:
s704, when the first version type is a reference version type and the second version type is a comparison version type, determining that the change operation type corresponding to the target object only existing in the first object tree is a deletion operation type.
S706, when the first version type is a reference version type and the second version type is a comparison version type, determining that the change operation type corresponding to the target object only existing in the second object tree is an insertion operation type.
In some embodiments, as shown in fig. 8, the step S604 of obtaining the first version type corresponding to the first version identifier and the second version type corresponding to the second version identifier includes:
s802, a reference version selection operation and a comparison version selection operation are received through a version change comparison interface.
Specifically, the reference version selection operation is used to select the reference version, and the comparison version selection operation is used to select the comparison version. When the reference version and the comparison version are selected, a difference in the comparison version with respect to the reference version is indicated.
And S804, taking the candidate version identification selected by the reference version selection operation as a first version identification, taking the first version type corresponding to the first version identification as a reference version type, taking the candidate version identification selected by the comparison version selection operation as a second version identification, and taking the second version type corresponding to the second version identification as a comparison version type.
Specifically, the candidate version identifier refers to an identifier corresponding to target service data of each different version corresponding to the target service document, and the server may use the candidate version identifier selected by the reference version selection operation as the first version identifier and use the candidate version identifier selected by the comparison version selection operation as the second version identifier. The version types may include a reference version type and a comparison version type, where the version type corresponding to the reference version identifier is the reference version type, and the version type corresponding to the comparison version identifier is the comparison version type.
It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, the steps are not necessarily executed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts of the above embodiments may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or the stages is not necessarily sequential, but may be performed alternately or alternatingly with other steps or at least a part of the sub-steps or the stages of other steps.
In some embodiments, as shown in fig. 9, there is provided a business document processing apparatus comprising: a data format change request receiving module 902, a text object composing module 904, a combined text object obtaining module 906, and a target service data obtaining module 908, wherein:
a data format change request receiving module 902, configured to receive a data format change request of initial service data, where the initial service data is data corresponding to a target service document, and the initial service data includes multiple fields and field values corresponding to the fields.
A text object composing module 904, configured to compose each field and the corresponding field value into a text object.
And the combined text object obtaining module 906 is configured to obtain a hierarchical relationship between fields in the target service document, and combine the text objects according to the hierarchical relationship between the fields to obtain a combined text object.
And a target service data obtaining module 908, configured to obtain target service data corresponding to the initial service data according to the combined text object.
In some embodiments, the text object is a key-value pair, and the text object composing module 904 is further configured to take each field as a key and take the corresponding field value as a value, so as to obtain the key-value pair corresponding to each field; the combined text object obtaining module 906 is further configured to obtain a hierarchical relationship between fields in the target business document, where the hierarchical relationship between the fields combines the key values to obtain a combined text object.
In some embodiments, the apparatus further comprises:
and the preset field acquisition module is used for acquiring the preset field.
And the corresponding relation establishing module is used for taking the target service data as a field value corresponding to the preset field so as to establish the corresponding relation between the preset field and the target service data.
And the storage module is used for storing the target service data in a preset field.
In some embodiments, the target business data is a first version of business data corresponding to the target business document, and the apparatus further includes:
and the version comparison request receiving module is used for receiving a version comparison request corresponding to the target business document, and the version comparison request carries the first version identification and the second version identification.
And the first version service data obtaining module is used for responding to the version comparison request, and extracting the combined text object from the target service data to be used as the first version service data corresponding to the first version identification.
And the first object tree obtaining module is used for splitting the combined text object into a plurality of objects according to the hierarchical relationship among the objects in the combined text object to obtain a first object tree.
The second object tree obtaining module is used for obtaining a second object tree corresponding to the second version identification;
and the version comparison result obtaining module is used for comparing the difference between the first object tree and the second object tree to obtain the version comparison result of the target business document.
In some embodiments, the version comparison request further carries a version type corresponding to the version identifier, and the version comparison result obtaining module includes:
and a target object acquisition unit for acquiring an object having a difference in the first object tree and the second object tree as a target object.
And the version type acquisition unit is used for acquiring a first version type corresponding to the first version identification and a second version type corresponding to the second version identification.
And the change operation type determining unit is used for determining the change operation type corresponding to the target object according to the first version type and the second version type.
And the version comparison result obtaining unit is used for taking the target object and the version change operation type as the version comparison result.
In some embodiments, the target object obtaining unit is further configured to obtain, as the target object, an object existing only in the first object tree or the second object tree;
the change operation type determining unit is further used for determining the change operation type corresponding to the target object only existing in the first object tree as the deletion operation type when the first version type is the reference version type and the second version type is the comparison version type; and when the first version type is a reference version type and the second version type is a comparison version type, determining that the change operation type corresponding to the target object only existing in the second object tree is an insertion operation type.
In some embodiments, the version type obtaining unit is further configured to receive a reference version selection operation and a comparison version selection operation through the version change comparison interface; and taking the candidate version identification selected by the reference version selection operation as a first version identification, taking the first version type corresponding to the first version identification as a reference version type, taking the candidate version identification selected by the comparison version selection operation as a second version identification, and taking the second version type corresponding to the second version identification as a comparison version type.
For specific limitations of the business document processing apparatus, reference may be made to the above limitations of the business document processing method, which are not described herein again. All or part of the modules in the business document processing device can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In some embodiments, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 10. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a business document processing method.
Those skilled in the art will appreciate that the architecture shown in fig. 10 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In some embodiments, a computer device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the above-mentioned business document processing method when executing the computer program.
In some embodiments, a computer-readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, realizes the steps of the above-mentioned business document processing method.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for processing business documents, the method comprising:
receiving a data format change request of initial service data, wherein the initial service data is data corresponding to a target service receipt, and the initial service data comprises a plurality of fields and field values corresponding to the fields;
forming a text object by each field and the corresponding field value;
acquiring the hierarchical relationship among the fields in the target business document, and combining the text objects according to the hierarchical relationship among the fields to obtain combined text objects;
and obtaining target service data corresponding to the initial service data according to the combined text object.
2. The method of claim 1, wherein the text object is a key-value pair, and wherein the step of composing each of the fields and the corresponding field value into a text object comprises:
respectively taking each field as a key, and taking the corresponding field value as a value to obtain a key value pair corresponding to each field;
the acquiring the hierarchical relationship between the fields in the target business document, and combining the text objects according to the hierarchical relationship between the fields to obtain a combined text object includes:
and acquiring the hierarchical relationship among the fields in the target business document, and combining the key value pairs by the hierarchical relationship among the fields to obtain a combined text object.
3. The method of claim 1, further comprising:
acquiring a preset field;
taking the target service data as a field value corresponding to the preset field to establish a corresponding relation between the preset field and the target service data;
and storing the target service data in the preset field.
4. The method of claim 1, wherein the target business data is a first version of business data corresponding to the target business document, and the method further comprises:
receiving a version comparison request corresponding to the target business document, wherein the version comparison request carries a first version identifier and a second version identifier;
responding to the version comparison request, extracting the combined text object from the target service data to be used as first version service data corresponding to the first version identification;
splitting the combined text object into a plurality of objects according to the hierarchical relationship among the objects in the combined text object to obtain a first object tree;
acquiring a second object tree corresponding to the second version identification;
and comparing the difference between the first object tree and the second object tree to obtain a version comparison result of the target business receipt.
5. The method of claim 4, wherein the version comparison request further carries a version type corresponding to a version identifier, and the comparing the difference between the first object tree and the second object tree to obtain the version comparison result of the target business document comprises:
acquiring an object with difference in the first object tree and the second object tree as a target object;
acquiring a first version type corresponding to the first version identification and a second version type corresponding to the second version identification;
determining a change operation type corresponding to the target object according to the first version type and the second version type;
and taking the target object and the version change operation type as version comparison results.
6. The method of claim 5, wherein obtaining the object with the difference between the first object tree and the second object tree as the target object comprises:
acquiring an object only existing in the first object tree or the second object tree as a target object;
the determining the change operation type corresponding to the target object according to the first version type and the second version type includes:
when the first version type is a reference version type and the second version type is a comparison version type, determining that the change operation type corresponding to the target object only existing in the first object tree is a deletion operation type;
and when the first version type is a reference version type and the second version type is a comparison version type, determining that the change operation type corresponding to the target object only existing in the second object tree is an insertion operation type.
7. The method of claim 5, wherein the obtaining a first version type corresponding to the first version identifier and a second version type corresponding to the second version identifier comprises:
receiving a reference version selection operation and a comparison version selection operation through a version change comparison interface;
and taking the candidate version identification selected by the reference version selection operation as a first version identification, taking the first version type corresponding to the first version identification as a reference version type, taking the candidate version identification selected by the comparison version selection operation as a second version identification, and taking the second version type corresponding to the second version identification as a comparison version type.
8. A business document processing apparatus, the apparatus comprising:
the data format change request receiving module is used for receiving a data format change request of initial service data, wherein the initial service data is data corresponding to a target service receipt, and the initial service data comprises a plurality of fields and field values corresponding to the fields;
the text object composition module is used for composing each field and the corresponding field value into a text object;
the combined text object obtaining module is used for obtaining the hierarchical relationship among the fields in the target business document and combining the text objects according to the hierarchical relationship among the fields to obtain a combined text object;
and the target service data obtaining module is used for obtaining target service data corresponding to the initial service data according to the combined text object.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the business document processing method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method for processing a business document according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911300217.3A CN111177302B (en) | 2019-12-16 | 2019-12-16 | Service bill processing method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911300217.3A CN111177302B (en) | 2019-12-16 | 2019-12-16 | Service bill processing method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111177302A true CN111177302A (en) | 2020-05-19 |
| CN111177302B CN111177302B (en) | 2024-02-13 |
Family
ID=70624186
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911300217.3A Active CN111177302B (en) | 2019-12-16 | 2019-12-16 | Service bill processing method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111177302B (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112434555A (en) * | 2020-10-16 | 2021-03-02 | 泰康保险集团股份有限公司 | Key value pair region identification method and device, storage medium and electronic equipment |
| CN112465612A (en) * | 2020-11-19 | 2021-03-09 | 金蝶软件（中国）有限公司 | Receipt information processing method and device, computer equipment and storage medium |
| CN112766875A (en) * | 2020-12-29 | 2021-05-07 | 金蝶软件（中国）有限公司 | Receipt data processing method and device, computer equipment and storage medium |
| CN112835904A (en) * | 2021-02-04 | 2021-05-25 | 北京电解智科技有限公司 | Data processing method and data processing device |
| CN112967121A (en) * | 2021-02-04 | 2021-06-15 | 金蝶软件（中国）有限公司 | Image retrieval method and device and computer storage medium |
| CN113535727A (en) * | 2021-07-19 | 2021-10-22 | 北京数码大方科技股份有限公司 | Data output method and data output device of information system and electronic equipment |
| CN113656400A (en) * | 2021-07-08 | 2021-11-16 | 上海二三四五网络科技有限公司 | Feature data encoding method and device |
| CN113705183A (en) * | 2021-07-16 | 2021-11-26 | 厦门海迈科技股份有限公司 | Web service-oriented electronic form data generation and maintenance method and related equipment |
| WO2022037573A1 (en) * | 2020-08-17 | 2022-02-24 | 北京市商汤科技开发有限公司 | Form identification method, apparatus and device, and computer readable storage medium |
| CN114416235A (en) * | 2021-12-28 | 2022-04-29 | 云镝智慧科技有限公司 | Document display method and device, computer equipment and storage medium |
| CN114663207A (en) * | 2022-03-24 | 2022-06-24 | 金蝶软件（中国）有限公司 | Receipt generation method and device, computer equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104965735A (en) * | 2015-06-18 | 2015-10-07 | 北京京东尚科信息技术有限公司 | Apparatus for generating upgrade SQL script |
| CN105912723A (en) * | 2016-05-09 | 2016-08-31 | 统通信（苏州）有限公司 | Storage method of custom field |
| CN108388438A (en) * | 2018-02-07 | 2018-08-10 | 平安普惠企业管理有限公司 | System base table update method, device, computer equipment and storage medium |
| CN108829727A (en) * | 2018-05-09 | 2018-11-16 | 上海陆家嘴国际金融资产交易市场股份有限公司 | Date storage method, device, computer equipment and storage medium |
| CN109800388A (en) * | 2017-11-17 | 2019-05-24 | 车伯乐（北京）信息科技有限公司 | A kind of edit methods of JSON data, apparatus and system |
| CN110147413A (en) * | 2019-04-26 | 2019-08-20 | 平安科技（深圳）有限公司 | Date storage method, data query method, apparatus, equipment and storage medium |
| CN110292775A (en) * | 2019-07-01 | 2019-10-01 | 网易（杭州）网络有限公司 | Obtain the method and device of variance data |
| CN110399367A (en) * | 2018-04-12 | 2019-11-01 | 腾讯科技（深圳）有限公司 | Business data processing method, device, computer equipment and storage medium |
-
2019
- 2019-12-16 CN CN201911300217.3A patent/CN111177302B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104965735A (en) * | 2015-06-18 | 2015-10-07 | 北京京东尚科信息技术有限公司 | Apparatus for generating upgrade SQL script |
| CN105912723A (en) * | 2016-05-09 | 2016-08-31 | 统通信（苏州）有限公司 | Storage method of custom field |
| CN109800388A (en) * | 2017-11-17 | 2019-05-24 | 车伯乐（北京）信息科技有限公司 | A kind of edit methods of JSON data, apparatus and system |
| CN108388438A (en) * | 2018-02-07 | 2018-08-10 | 平安普惠企业管理有限公司 | System base table update method, device, computer equipment and storage medium |
| CN110399367A (en) * | 2018-04-12 | 2019-11-01 | 腾讯科技（深圳）有限公司 | Business data processing method, device, computer equipment and storage medium |
| CN108829727A (en) * | 2018-05-09 | 2018-11-16 | 上海陆家嘴国际金融资产交易市场股份有限公司 | Date storage method, device, computer equipment and storage medium |
| CN110147413A (en) * | 2019-04-26 | 2019-08-20 | 平安科技（深圳）有限公司 | Date storage method, data query method, apparatus, equipment and storage medium |
| CN110292775A (en) * | 2019-07-01 | 2019-10-01 | 网易（杭州）网络有限公司 | Obtain the method and device of variance data |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022037573A1 (en) * | 2020-08-17 | 2022-02-24 | 北京市商汤科技开发有限公司 | Form identification method, apparatus and device, and computer readable storage medium |
| CN112434555B (en) * | 2020-10-16 | 2024-04-09 | 泰康保险集团股份有限公司 | Key value pair region identification method and device, storage medium and electronic equipment |
| CN112434555A (en) * | 2020-10-16 | 2021-03-02 | 泰康保险集团股份有限公司 | Key value pair region identification method and device, storage medium and electronic equipment |
| CN112465612A (en) * | 2020-11-19 | 2021-03-09 | 金蝶软件（中国）有限公司 | Receipt information processing method and device, computer equipment and storage medium |
| CN112766875A (en) * | 2020-12-29 | 2021-05-07 | 金蝶软件（中国）有限公司 | Receipt data processing method and device, computer equipment and storage medium |
| CN112835904A (en) * | 2021-02-04 | 2021-05-25 | 北京电解智科技有限公司 | Data processing method and data processing device |
| CN112967121A (en) * | 2021-02-04 | 2021-06-15 | 金蝶软件（中国）有限公司 | Image retrieval method and device and computer storage medium |
| CN113656400A (en) * | 2021-07-08 | 2021-11-16 | 上海二三四五网络科技有限公司 | Feature data encoding method and device |
| CN113656400B (en) * | 2021-07-08 | 2024-02-27 | 上海二三四五网络科技有限公司 | Characteristic data encoding method and device |
| CN113705183A (en) * | 2021-07-16 | 2021-11-26 | 厦门海迈科技股份有限公司 | Web service-oriented electronic form data generation and maintenance method and related equipment |
| CN113705183B (en) * | 2021-07-16 | 2024-09-20 | 厦门海迈科技股份有限公司 | Web service-oriented electronic form data generation and maintenance method and related equipment |
| CN113535727A (en) * | 2021-07-19 | 2021-10-22 | 北京数码大方科技股份有限公司 | Data output method and data output device of information system and electronic equipment |
| CN113535727B (en) * | 2021-07-19 | 2024-04-09 | 北京数码大方科技股份有限公司 | Data output method and device of information system and electronic equipment |
| CN114416235A (en) * | 2021-12-28 | 2022-04-29 | 云镝智慧科技有限公司 | Document display method and device, computer equipment and storage medium |
| CN114663207A (en) * | 2022-03-24 | 2022-06-24 | 金蝶软件（中国）有限公司 | Receipt generation method and device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111177302B (en) | 2024-02-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111177302B (en) | Service bill processing method, device, computer equipment and storage medium | |
| CN109558404B (en) | Data storage method, device, computer equipment and storage medium | |
| WO2020186786A1 (en) | File processing method and apparatus, computer device and storage medium | |
| CN109408746B (en) | Image information query method, image information query device, computer equipment and storage medium | |
| CN111027295B (en) | Data processing method, device, computer equipment and storage medium | |
| US20200322159A1 (en) | Method for index-based and integrity-assured search in a blockchain | |
| US20170255708A1 (en) | Index structures for graph databases | |
| CN109597979B (en) | List table generation method and device, computer equipment and storage medium | |
| CN113010542B (en) | Service data processing method, device, computer equipment and storage medium | |
| CN112416934A (en) | hive table incremental data synchronization method and device, computer equipment and storage medium | |
| CN115544183A (en) | Data visualization method and device, computer equipment and storage medium | |
| CN112434027A (en) | Indexing method and device for multi-dimensional data, computer equipment and storage medium | |
| CN109767098A (en) | Processing method, device, computer equipment and the storage medium of product attribute | |
| CN115470156A (en) | RDMA-based memory use method, system, electronic device and storage medium | |
| CN115168499B (en) | Database table fragmentation method and device, computer equipment and storage medium | |
| CN117743299A (en) | Database migration method, device, equipment, medium and product | |
| CN115495452A (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN114860806A (en) | Data query method and device of block chain, computer equipment and storage medium | |
| CN109726178B (en) | Interactive application method and device of unstructured file, computer equipment and storage medium | |
| CN110196877B (en) | Data display method, device, computer equipment and storage medium | |
| CN112860755B (en) | Service identifier generation method, device, computer equipment and medium | |
| CN112835886A (en) | Data table field adding method and device | |
| CN115168409B (en) | Data query method and device for database sub-tables and computer equipment | |
| CN111339574B (en) | Block data processing method and device, computer equipment and storage medium | |
| CN116880927A (en) | Rule management method, device, computer equipment and storage medium |
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 | ||
| TG01 | Patent term adjustment | ||
| TG01 | Patent term adjustment |