Production management system data initialization method, device and system, medium and equipment

Abstract

The invention discloses a production management system data initialization method, device and system, a medium and equipment. The method comprises the following steps: acquiring template data, wherein the template data has a service entity and service entity configuration data which are the same as a target object; and according to a sequence from low data logic to high data logic among the business entities in the template data, copying the template data in a layering manner to obtain target object data, and performing data initialization on the production management system by utilizing the target object data. By adopting the scheme, the data initialization efficiency of the production management system can be improved.

Description

Technical Field

[0001] This invention relates to the field of semiconductor technology, and specifically to a data initialization method, apparatus, system, medium, and equipment for a production management system. Background Technology

[0002] Production management systems are business systems that heavily rely on fundamental data. Without standardized, structured fundamental data adapted to the new entity, the system cannot match actual business processes and cannot support precise control and decision-making throughout the entire production process. Therefore, data initialization configuration is required in the production management system before a new factory or new customer goes live.

[0003] However, existing solutions for initializing data in production management systems are inefficient, thus delaying production capacity rollout and market delivery. Summary of the Invention

[0004] The problem this invention aims to solve is: how to improve the data initialization efficiency of a production management system.

[0005] To address the above problems, embodiments of the present invention provide a data initialization method for a production management system, the method comprising: Obtain template data, which has the same business entities and business entity configuration data as the target object; The template data is copied layer by layer according to the data logic between business entities in the template data from low to high, to obtain the target object data, so as to use the target object data to initialize the production management system.

[0006] In one possible embodiment, the step of copying the template data hierarchically according to the logical order of data entities in the template data from low to high to obtain the target object data includes: All business entities of the target object are layered according to data logic to obtain several layers of business entities; Following the data logic from low to high, the business entity configuration data corresponding to each layer of business entities is copied sequentially to obtain the target object data.

[0007] In one possible embodiment, the step of sequentially copying the business entity configuration data corresponding to each layer of business entities to obtain the target object data includes: Following the data logic from low to high among the business entities in the target layer, the business entity configuration data corresponding to each business entity in the target layer is copied sequentially to obtain the target object data of the target layer. The target layer is any layer of the business entity of the target object.

[0008] In one possible embodiment, the business entity configuration data corresponding to the business entity includes: system data content; the system data content corresponding to the first business entity is copied using the following method: Access the first data table corresponding to the first business entity in the template data, where the first business entity is any business entity of the target object; Save the old primary key values ​​corresponding to the configuration data of each business entity in the first data table, and set the primary key field of the configuration data of each business entity in the first data table to empty. The system data content in the configuration data of the business entity after being emptied is copied to the corresponding storage space, and the key-value mapping relationship between the old primary key value and the new primary key value of the configuration data of each business entity corresponding to the first business entity is obtained.

[0009] In one possible embodiment, the business entity configuration data corresponding to the business entity further includes: associated data content; the associated data content corresponding to the first business entity is copied using the following method: Based on the key-value mapping relationship obtained by other business entities in the layer where the first business entity is located during the replication process, or the key-value mapping relationship obtained by business entities in a lower logical order during the replication process, the associated data content is converted into a logical foreign key so as to copy the associated data content after the logical foreign key conversion to the corresponding storage space.

[0010] In one possible embodiment, the step of sequentially copying the business entity configuration data corresponding to each business entity in the target layer according to the data logic from low to high order among the business entities in the target layer to obtain the target object data of the target layer further includes: Before copying the business entity configuration data corresponding to the first business entity after it has been set to empty to the storage space corresponding to the target object, it is determined whether the business entity configuration data corresponding to the first business entity includes a time field that needs to be adjusted. When a time field that needs adjustment is included, the time field that needs adjustment is adjusted so that the adjusted time field is copied to the storage space corresponding to the target object.

[0011] In one possible embodiment, adjusting the time field that needs to be adjusted includes: Calculate the time difference between the template data creation time and the current time; Adjust the time field that needs to be adjusted based on the time difference.

[0012] In one possible embodiment, accessing the system data content corresponding to the first business entity in the template data includes: Based on the name of the first business entity, access the system data content corresponding to the first business entity in the template data.

[0013] In one possible embodiment, the plurality of business entities, in logical order from low to high, sequentially include: Field configuration layer business entities; Business entities in the business configuration layer; Basic data layer business entities; And business entities in the business data layer.

[0014] In one possible embodiment, prior to obtaining the template data, the method further includes: Receive template instruction information and target object instruction information; Based on the template indication information, the template data is obtained from the corresponding storage space; And based on the target object indication information, determine the storage space corresponding to the target object data.

[0015] This invention also provides a data initialization device for a production management system, the device comprising: The acquisition unit is adapted to acquire template data, wherein the template data has the same business entity and business entity configuration data as the target object; The copying unit is adapted to copy the template data layer by layer according to the data logic between business entities in the template data from low to high order, so as to obtain the target object data.

[0016] This invention also provides a production management system, which includes the production management system data initialization device described above.

[0017] This invention also provides a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the steps of any of the methods described above.

[0018] This invention also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that can run on the processor, and the processor executes the steps of any of the methods described above when running the computer program.

[0019] Compared with the prior art, the technical solution of the embodiments of the present invention has the following advantages: By applying the solution of this invention, template data is obtained. Since the template data contains the same business entities and configuration data as the target object, the target object data can be obtained by copying the template data. This improves the data initialization efficiency of the production management system compared to configuring all data from scratch. Furthermore, when copying the template data, it is copied layer by layer according to the logical order of the business entities in the template data from low to high to obtain the target object data. This ensures the correctness of the logical dependencies between the target object data. Compared to simply copying the data itself without considering the data logic, this further improves the usability of the target object data and reduces the time required for subsequent adjustments to the target object data, thereby further improving data initialization efficiency. Attached Figure Description

[0020] Figure 1 This is a flowchart of a data initialization method for a production management system according to an embodiment of the present invention; Figure 2 This is a flowchart of another production management system data initialization method in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of a data initialization device for a production management system according to an embodiment of the present invention. Detailed Implementation

[0021] Traditionally, when initializing data for a production management system, all data is usually configured from scratch, which is not only time-consuming but also prone to errors, resulting in low configuration efficiency and delays in production capacity implementation and market delivery.

[0022] To address this problem, this invention provides a data initialization method for a production management system. This method obtains target object data by copying template data, effectively improving the data initialization efficiency of the production management system. Furthermore, when copying the template data, it is copied layer by layer according to the logical order of business entities within the template data from lowest to highest, thereby further improving data initialization efficiency.

[0023] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0024] Reference Figure 1 This invention provides a data initialization method for a production management system, which may include the following steps: Step 11: Obtain template data, which has the same business entities and business entity configuration data as the target object.

[0025] In practical implementation, the target object can be a target factory or a target customer. That is, before a new factory or new customer uses the production management system, the data initialization scheme in this embodiment of the invention is used to initialize the production management system. The production management system can transform abstract production plans into actionable work processes and tasks, and monitor and trace the entire production process in real time, ensuring efficient, compliant, and high-quality production. The production management system can be applied to multiple fields, such as the semiconductor industry, automotive parts manufacturing, and electronic product manufacturing.

[0026] In practice, the template data can be obtained through any legal and compliant means. This template data can have the same application scenario or domain as the target object. For example, when the target object is semiconductor plant A, the template data can be the initialization data used by the production management system when it is applied in semiconductor plant B.

[0027] Specifically, the template data should have the same business entities and configuration data as the target object. The business entity is an abstract model of a "thing" or "object" with independent business significance in a real-world business scenario; it is the core carrier for storing business data and carrying business logic in the system. Simply put, a business entity transforms concrete things in a factory or business process into a "data model" within the system. Each business entity corresponds to a data table in the system, and the attributes of the business entity correspond to the fields of the data table.

[0028] Taking a semiconductor factory as an example, processes, products, suppliers, and inventory orders can each be considered as a business entity. Each business entity corresponds to a data table in the system, and each data table can contain multiple records, with each record serving as a business configuration data entry.

[0029] In one embodiment of the present invention, the production management system can provide a template database, and the target database serves as a storage space for template data, capable of storing multiple template data.

[0030] At this point, before acquiring the template data, the method may further include: receiving template indication information. The received template indication information may include an identifier for the template data, thereby allowing the determination of the template data to be acquired based on the template indication information.

[0031] Template instruction information can be received in various ways. For example, it can be received through an interactive interface, thereby identifying the identity of the template data to be obtained and querying the template data from the template database, thus meeting the data initialization needs of diverse target objects.

[0032] In one embodiment of the present invention, the production management system may further provide a target object database, which serves as a storage space for target objects and can store target object data for multiple target objects.

[0033] At this point, before acquiring the template data, the method may further include: receiving target object indication information. The target object indication information may include the identity identifier of the target object, thereby allowing the determination of the storage space corresponding to the current target object based on the target object indication information, so as to accurately store the target object data and improve the accuracy and efficiency of subsequent data initialization of the production management system using the target object data.

[0034] Step 12: Copy the template data layer by layer according to the data logic between business entities in the template data from low to high order to obtain the target object data, so as to use the target object data to initialize the production management system.

[0035] In practical implementation, the data required for data initialization in a production management system includes not only the data itself but also the logical dependencies between data. These logical dependencies are manifested through logical foreign key dependencies. Therefore, when copying template data, it is essential to copy not only the template data itself but also ensure the accuracy of its logical foreign keys.

[0036] The essence of a logical foreign key is a "business association agreement on field values," rather than a physical binding at the database level. Direct copying will cause "primary key duplication" and "failure of the association relationship," thus rendering the target object data obtained through copying unusable. For example, the associated data content of a production order table is "material ID=101," while in the target object data, the ID of the material table is regenerated as 301. If "material ID=101" from the production order table is directly copied, this primary key value does not exist in the new material table, and the logical foreign key relationship will be completely invalidated.

[0037] Therefore, in embodiments of the present invention, when copying template data, the template data is copied layer by layer according to the data logic between business entities in the template data from low to high. Layering means that all business entities of the target object are divided into layers according to data logic.

[0038] Specifically, in one embodiment, all business entities of the target object can be layered according to data logic to obtain several layers of business entities. Then, the business entity configuration data corresponding to each layer of business entities can be copied sequentially according to the data logic from low to high to obtain the target object data.

[0039] In practice, the number of business entity layers can be set according to the actual situation. For example, after layering all business entities of the target object according to data logic, the data logic can be arranged from low to high as first-level business entities, second-level business entities, third-level business entities, and fourth-level business entities. Among them, the first-level business entities are the business entities at the lowest level of data logic, and the fourth-level business entities are the business entities at the highest level of data logic.

[0040] The lowest-level business entity in the data logic is the most basic, root-level foundational data in the entire data system, independent of other data and referenced by higher-level data. This level of business entity configuration data is the starting point for all logical dependencies, with no lower-level dependencies. The configuration data of the second-level business entities depends on, or can reference, the first-level business entities. The configuration data of the third-level business entities depends on, or can reference, both the first and second-level business entities. The configuration data of the fourth-level business entities depends on, or can reference, all of the first, second, and third-level business entities.

[0041] In practice, the business configuration data of the first-level business entity can be copied first, then the business configuration data of the second-level business entity, then the business configuration data of the third-level business entity, and finally the business configuration data of the fourth-level business entity. This ensures the correctness of the logical dependencies.

[0042] In practice, there are usually more than two business entities in the same data logic layer. In this case, for multiple business entities in the same data logic layer, in order to further ensure the correctness of the logical dependencies, they can also be copied in the order of data logic from low to high among the business entities in that layer.

[0043] Specifically, taking the business entity at any level of the target object as the target layer as an example, when copying the template data corresponding to the target layer, the business entity configuration data corresponding to each business entity in the target layer can be copied sequentially according to the data logic from low to high among the business entities in the target layer to obtain the target object data of the target layer.

[0044] Taking a semiconductor factory as an example, all business entities within the factory are layered according to data logic. The data logic, from lowest to highest, can be categorized as follows: field configuration layer business entities, business configuration layer business entities, basic data layer business entities, and business data layer business entities. Among these: The business entities in the field configuration layer can include: custom fields, custom forms, numbering rules, and other business entities related to field configuration. When copying the corresponding template data, you can first copy the business entity configuration data for custom fields, then copy the business entity configuration data for custom forms, and finally copy the business entity configuration data for numbering rules.

[0045] The business entities in the business configuration layer can include: user group permissions, filtering schemes, user interface configurations, dashboard configurations, custom event triggering rules, and other business entities related to business configuration. When copying the corresponding template data, the configuration data of the business entities such as user groups, filtering schemes, user configurations, dashboard configurations, custom events, and permission configurations can be copied sequentially.

[0046] The basic data layer business entities can include: units, defective items, processes, process routes, products, customers, suppliers, and other business entities related to actual production. The business data layer business entities can include: work orders, work reports, inventory orders, and other business entities related to business data. When copying the corresponding template data, the configuration data of the business entities—units, defective items, processes, process routes, customers, suppliers, and products—can be copied sequentially.

[0047] In practical applications, each business entity can include multiple business configuration data entries. Each business entity configuration data entry can consist only of system data content. This system data content can include: the business entity's old primary key value and the business entity's attribute characteristic data. The old primary key value is automatically generated for the business entity's configuration data in the template data's data table. The business entity's attribute characteristic data records the business entity's business attributes. For example, the attribute characteristic data for wafer materials can include: code = SEM-WA-001, specification = 12 inches, type = monocrystalline silicon, storage requirement = cleanroom constant temperature, etc.

[0048] In practical implementation, in the template database, the business entity configuration data for each business entity can correspond to a table. Each table can be identified by the name of the business entity, and the table records the business entity configuration data. Taking the first business entity as an example, when copying the system data content of the first business entity, the first data table corresponding to the first business entity can be found in the template data first. Then, the old primary key values ​​corresponding to the configuration data of each business entity in the first data table are saved, and the primary key fields of the configuration data of each business entity in the first data table are set to null. Thus, the system data content in the nulled configuration data of the business entity is copied to the corresponding storage space, and the key-value mapping relationship between the old primary key values ​​and the new primary key values ​​of the configuration data of each business entity corresponding to the first business entity is obtained.

[0049] When copying the system data content of the first business entity, the first data table can be accessed through the name of the first business entity. Since the first data table may contain multiple business entity configuration data entries, before copying each entry, the primary key value of that entry can be saved and set to null. After the system data content in the business entity configuration data is copied to the first data table in the target object's database, the first data table in the target object's database will generate a new key value for the copied business entity configuration data. This new key value serves as the identity identifier for that business entity configuration data in the target object. Subsequently, a key-value mapping relationship is established between the old and new primary key values ​​of the business entity configuration data for use in subsequent logical dependency conversions during copying.

[0050] For example, if the old primary key value of a business entity configuration record in the work order data table is 2270978, when copying this business entity configuration record, first preserve the old primary key value, then set the primary key field in the first data table to null, and finally copy the modified business entity configuration record to the corresponding position in the first data table of the target object database. At this point, the first data table in the target object database will generate a new key value of 2 for the copied business entity configuration record. Therefore, the key-value mapping relationship between the old and new primary key values ​​of the business entity configuration record can be represented as (2270978, 2).

[0051] In some embodiments, each business entity configuration data may further include associated data content. Associated data content refers to data content that represents the associated ID. For example, in the template data, the associated data content for the business entity "Wafer Production Order" may include: Material ID=1001 (associated with wafer materials), Production Line ID=201 (associated with lithography production line), and Process Route ID=301 (associated with wafer processing technology).

[0052] For associated data content, during copying, logical foreign key conversion can be performed on the associated data content based on the key-value mapping relationships obtained during the copying process of other business entities at the same layer as the first business entity, or the key-value mapping relationships obtained during the copying process of business entities at a lower logical level. This allows the associated data content after logical foreign key conversion to be copied to the corresponding storage space. For example, when copying the associated data content of the "Wafer Production Order" business entity, the material ID, production line ID, and process route ID can be converted into new key values ​​based on the previously obtained key-value mapping relationships. This allows the associated data and system data content to be copied together to the data table corresponding to "Wafer Production Order" in the target object database. This reduces the time required for subsequent manual modification of logical dependencies, lowers the probability of errors in logical dependencies, and further improves the efficiency and accuracy of data initialization.

[0053] In some embodiments, business entity configuration data may also include time fields, such as creation time, upgrade time, and planned execution time. To improve configuration efficiency, time fields in business entity configuration data that require adjustment can be automatically adjusted using a computer.

[0054] Specifically, before copying the business entity configuration data corresponding to the first business entity after it has been set to empty to the storage space corresponding to the target object, it can be determined whether the business entity configuration data corresponding to the first business entity includes a time field that needs to be adjusted. If it includes a time field that needs to be adjusted, the time field that needs to be adjusted is adjusted so that the adjusted time field is copied to the storage space corresponding to the target object.

[0055] In practice, a list of time fields requiring time adjustment can be pre-defined, containing the names of all time fields that need adjustment. For any business entity, after obtaining its content, it can be determined whether the business entity contains any time fields requiring adjustment based on its field definition types. If it does contain time fields requiring adjustment, such as those defined as date or time, then the time fields are adjusted before the business entity configuration data is copied to the storage space corresponding to the target object.

[0056] In practical implementation, when adjusting the time field that needs adjustment, the time difference between the template data creation time and the current time can be calculated first. This time difference is equivalent to the offset of the time field. Then, the time field that needs adjustment is adjusted based on this time difference, so that the time field in the business entity configuration data copied to the target object is offset backward by this time difference. This reduces the time required for subsequent manual modification of the time field and further improves data initialization efficiency. For example, if the template data creation time is January 1, 2025, and the current time is January 1, 2026, the creation time in the business entity configuration data to be copied can be modified to January 1, 2026.

[0057] In practice, batch processing can be used to process multiple business entity configuration data entries in batches, allowing data to be inserted into the storage space corresponding to the target object in stages, thereby improving data replication efficiency. For example, 800 business entity configuration data entries can be replicated simultaneously.

[0058] Figure 2 In another embodiment of the present invention, a data initialization method for a production management system may include: Step 21: Determine whether the template data exists and whether the target object is in a data receiving state.

[0059] In practical implementation, before initializing the production management system data for any target object, it's necessary to first determine whether the template data exists and whether the target object exists. Determining whether the template data exists refers to checking if the specified template data exists in the template database, and whether the template data stored in the template database is real, valid, and legal. Determining whether the target object is in a data receiving state refers to checking whether storage space has been created for the target object in the target object's database, and whether the target object's data is in a cleared state. Only target objects in a data receiving state are allowed to copy data.

[0060] If the template data does not exist or the target object is not in a data receiving state, then steps 22 to 24 will be stopped.

[0061] Step 22: Obtain template data, which has the same business entities and business entity configuration data as the target object.

[0062] For step 22, please refer to the description of step 11 above for implementation details, which will not be repeated here.

[0063] Step 23: Copy the template data layer by layer according to the data logic between business entities in the template data from low to high order to obtain the target object data.

[0064] For step 23, please refer to the description of step 12 above for implementation details, which will not be repeated here.

[0065] Step 24: Initialize the production management system using the target object data.

[0066] In practice, after obtaining the target object data, the target object data can be loaded to complete the data initialization of the production management system. After data initialization, the production management system can operate normally.

[0067] As can be seen from the above, the solution of this invention, which initializes the production management system based on pre-configured template data, can effectively improve data initialization efficiency. Furthermore, during the copying of template data, data is copied hierarchically based on the data logic between business entities, and the mapping relationship between old and new primary key values ​​is automatically maintained, with real-time logical foreign key conversion, thereby ensuring the accuracy of the data logic. In addition, during the copying of template data, time adjustments can be automatically performed for time fields that require adjustment, maintaining relative time relationships, thereby further improving data initialization efficiency.

[0068] To enable those skilled in the art to better understand and implement the present invention, the apparatus, testing system, electronic device, and computer-readable storage medium corresponding to the above method are described in detail below.

[0069] Reference Figure 3 This invention also provides a production management system data initialization device 30, which may include: an acquisition unit 31 and a copying unit 32. Wherein: The acquisition unit 31 is adapted to acquire template data, which has the same business entity and business entity configuration data as the target object. The copying unit 32 is adapted to copy the template data layer by layer according to the data logic between business entities in the template data from low to high order, so as to obtain the target object data.

[0070] The acquisition unit 31 and the copying unit 32 can be implemented with reference to the above description of steps 11 to 12, and will not be repeated here.

[0071] This invention also provides a production management system, which may further include the production management system data initialization device 30 described in the above embodiments.

[0072] This invention also provides a computer-readable storage medium having a computer program stored thereon, the computer program being executed by a processor to implement the steps of any of the above methods.

[0073] In specific implementations, the computer-readable storage medium may include ROM, RAM, disk, or optical disk, etc.

[0074] This invention also provides an electronic device, which includes a memory and a processor. The memory stores a computer program that can run on the processor, and when the processor runs the computer program, it performs the steps of any of the methods described above.

[0075] Regarding the modules / units included in the various devices and products described in the above embodiments, they can be software modules / units, hardware modules / units, or a combination of both. For example, for various devices and products applied to or integrated into a chip, all of their modules / units can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits; for various devices and products applied to or integrated into a chip module, all of their modules / units can be implemented using hardware methods such as circuits, and different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The components can be implemented using software programs that run on the processor integrated within the chip module. The remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into the terminal, each of its components / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or in different components within the terminal. Alternatively, at least some modules / units can be implemented using software programs that run on the processor integrated within the terminal, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits.

[0076] While the present invention has been disclosed above, it is not limited thereto. Any person skilled in the art can make various modifications and alterations without departing from the spirit and scope of the invention; therefore, the scope of protection of the present invention should be determined by the scope defined in the claims.

Claims

1. A production management system data initialization method characterized by, The method comprises the following steps: acquiring template data, wherein the template data has the same business entities and business entity configuration data as the target object; copying the template data in a hierarchical manner according to the data logic from low to high between the business entities in the template data, to obtain target object data, and initializing the production management system with the target object data.

2. The production management system data initialization method of claim 1, wherein, The step of copying the template data in a hierarchical manner according to the data logic from low to high between the business entities in the template data, to obtain target object data, comprises the following steps: hierarchically arranging all the business entities of the target object according to the data logic, to obtain a plurality of layers of business entities; copying the business entity configuration data corresponding to each layer of business entities in sequence according to the data logic from low to high, to obtain the target object data.

3. The production management system data initialization method of claim 2, wherein, The step of copying the business entity configuration data corresponding to each layer of business entities in sequence, to obtain the target object data, comprises the following steps: copying the business entity configuration data corresponding to each business entity in the target layer in sequence according to the data logic from low to high between the business entities in the target layer, to obtain the target object data of the target layer; the target layer is any layer of business entities of the target object.

4. The production management system data initialization method of claim 3, wherein, The business entity configuration data corresponding to the business entity comprises system data content; the system data content corresponding to the first business entity is copied by the following method: accessing a first data table corresponding to the first business entity in the template data, wherein the first business entity is any business entity of the target object; saving the old primary key values corresponding to the business entity configuration data in the first data table, and setting the primary key fields of the business entity configuration data in the first data table to be empty; copying the system data content in the business entity configuration data after being set to be empty to the corresponding storage space, and obtaining the key value mapping relationship between the old primary key values and the new primary key values of the business entity configuration data corresponding to the first business entity.

5. The production management system data initialization method of claim 4, wherein, The business entity configuration data corresponding to the business entity further comprises associated data content; the associated data content corresponding to the first business entity is copied by the following method: performing logical foreign key conversion on the associated data content based on the key value mapping relationship obtained in the copying process of the other business entities in the layer where the first business entity is located, or the key value mapping relationship obtained in the copying process of the business entities in a lower layer in logical order, to copy the associated data content after the logical foreign key conversion to the corresponding storage space.

6. The production management system data initialization method of claim 4, wherein, The step of copying the business entity configuration data corresponding to each business entity in the target layer in sequence according to the data logic from low to high between the business entities in the target layer, to obtain the target object data of the target layer, further comprises the following steps: before copying the business entity configuration data corresponding to the first business entity after being set to be empty to the storage space corresponding to the target object, judging whether the business entity configuration data corresponding to the first business entity comprises a time field that needs to be adjusted; when the time field that needs to be adjusted is included, adjusting the time field that needs to be adjusted, and copying the adjusted time field to the storage space corresponding to the target object.

7. The production management system data initialization method of claim 6, wherein, The step of adjusting the time field that needs to be adjusted comprises the following steps: calculating a time difference between the template data creation time and a current time; adjusting the time field to be adjusted based on the time difference.

8. The production management system data initialization method of claim 4, wherein, The system data content corresponding to the first business entity in the template data comprises: Accessing the system data content corresponding to the first business entity in the template data based on the name of the first business entity.

9. The production management system data initialization method of claim 2, wherein, The several layers of business entities comprise, in a logical order from low to high: a field configuration layer business entity; a business configuration layer business entity; a basic data layer business entity; and a business data layer business entity.

10. The production management system data initialization method of claim 1, wherein, Before the template data is obtained, the method further comprises: receiving template indication information and target object indication information; obtaining the template data from a corresponding storage space based on the template indication information; and determining a storage space corresponding to the target object data based on the target object indication information.

11. A production management system data initialization apparatus characterized by comprising: The method comprises: an obtaining unit adapted to obtain template data, the template data having the same business entities and business entity configuration data as a target object; a copying unit adapted to copy the template data in a hierarchical manner according to a logical order of data between business entities in the template data from low to high, to obtain target object data.

12. A production management system characterized by comprising: The production management system data initialization device comprises the device according to claim 11.

13. A computer readable storage medium having stored thereon a computer program, characterized in that The computer program is executed by a processor to implement the steps of the method according to any one of claims 1 to 10.

14. An electronic device comprising a memory and a processor, said memory having stored thereon a computer program capable of running on said processor, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1 to 10.

Images