CN112379920A - Compatible method, integrated platform and storage medium for integrated software in ERP system - Google Patents
Compatible method, integrated platform and storage medium for integrated software in ERP system Download PDFInfo
- Publication number
- CN112379920A CN112379920A CN202011285258.2A CN202011285258A CN112379920A CN 112379920 A CN112379920 A CN 112379920A CN 202011285258 A CN202011285258 A CN 202011285258A CN 112379920 A CN112379920 A CN 112379920A
- Authority
- CN
- China
- Prior art keywords
- software
- erp system
- integrated
- platform
- description file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 230000010354 integration Effects 0.000 claims abstract description 41
- 239000000463 material Substances 0.000 claims abstract description 32
- 230000003993 interaction Effects 0.000 claims abstract description 7
- 238000004891 communication Methods 0.000 claims description 16
- 238000006243 chemical reaction Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 3
- 230000000007 visual effect Effects 0.000 claims description 3
- 230000009286 beneficial effect Effects 0.000 abstract description 3
- 230000006870 function Effects 0.000 description 39
- 230000008569 process Effects 0.000 description 8
- 230000002159 abnormal effect Effects 0.000 description 7
- 238000007726 management method Methods 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 4
- 239000004606 Fillers/Extenders Substances 0.000 description 3
- 230000009471 action Effects 0.000 description 3
- 238000011160 research Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000012805 post-processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/73—Program documentation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Library & Information Science (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a compatible method of integrated software in an ERP system, which comprises the following steps: acquiring material data of the ERP system; judging whether the integrated software in the material data is compatible; if not, determining a description file corresponding to the integration software with compatible exception from the integration platform; the description file is a functional component generated based on a description word contract corresponding to the integration platform; and accessing the description file into the ERP system. The method and the system have the advantages that the application software is uniformly limited by the integration platform, the stability of information interaction between the application software and the ERP system can be guaranteed, meanwhile, the application can be rapidly expanded, the ERP system can be rapidly updated in an iterative mode, and the service management requirement is met. The application also provides an integrated platform and a computer readable storage medium, which have the beneficial effects.
Description
Technical Field
The present application relates to the field of service management, and in particular, to a compatible method, an integrated platform, and a storage medium for integrated software in an ERP system.
Background
ERP (enterprise Resource planning) is an enterprise Resource plan, which is established on the basis of information technology and integrates information technology and advanced management ideas. According to the ERP system, if a material data source is an integrated drawing, the types and versions of integrated software are many, and the existing solution is that when new integrated software and a new integrated software version need to be supported, technicians are arranged to conduct research aiming at interfaces of the new integrated software and the new integrated software version, relevant information is read out, and the information is led into the ERP system. In other words, when the ERP system needs to introduce new integrated software and new integrated software versions, the original ERP system cannot support the new integrated software and new interfaces, and research and development needs to be performed on the new software and the new interfaces, so that along with the acceleration of the update speed and the increase of types of application software, the research and development support performed on each new integrated software and new software version greatly reduces the upgrade efficiency of the ERP system, and is not beneficial to the system upgrade of the ERP system.
Disclosure of Invention
The application aims to provide a compatible method, an integration platform and a computer readable storage medium for integrating software in an ERP system, which can support new version software or new software with minimum change cost.
In order to solve the above technical problem, the present application provides a compatible method for integrated software in an ERP system, and the specific technical solution is as follows:
acquiring material data of the ERP system;
judging whether the integrated software in the material data is compatible;
if not, determining a description file corresponding to the integration software with compatible exception from the integration platform; the description file is a functional component generated based on a description word contract corresponding to the integration platform;
and accessing the description file into the ERP system.
Optionally, the determining whether the integrated software in the material data is compatible includes:
judging whether the integrated software in the material data is a new version software or a new software;
and if the integrated software is a new version of software or new software, executing a step of determining a description file corresponding to the integrated software with compatible exception from the integrated platform.
Optionally, before the obtaining of the material data of the ERP system, the method further includes:
defining a descriptor contract of the integration platform;
the descriptor contract includes key attributes, key descriptions, standard interface formats, and description file formats.
Optionally, after defining the descriptor contract of the integration platform, the method further includes:
receiving new version software or new software;
carrying out format conversion on the new version software or the new software based on the description word contract to obtain a description file in the description file format;
adding the description file to the integration platform.
The present application further provides an integrated platform of an application component, comprising:
a communication component for acquiring application software;
the data contract component is used for carrying out format conversion on the application software based on the descriptor contract to obtain a description file;
and the software access component is connected with the ERP system, and accesses the description file to the ERP system.
Optionally, the software access component includes:
the system comprises a standardization unit for providing standard functional components, an application access unit for providing software support components, an application form interaction unit for providing visual components and an extension unit for providing non-standard functional components.
Optionally, the communication component is further configured to access a public cloud platform, and the public cloud platform is a shared platform of the EPR system.
Optionally, the integrated platform further includes:
a universal software development kit for providing an instruction manual describing the word compact.
Optionally, the integrated platform further includes:
a contract definition component for defining or updating the descriptor contract.
The present application also provides a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method as set forth above.
The application provides a compatible method of integrated software in an ERP system, which comprises the following steps: acquiring material data of the ERP system; judging whether the integrated software in the material data is compatible; if not, determining a description file corresponding to the integration software with compatible exception from the integration platform; the description file is a functional component generated based on a description word contract corresponding to the integration platform; and accessing the description file into the ERP system.
When integrated software compatible with abnormity exists in determined material data, description files of the abnormal software are acquired from an integrated platform in a gathering mode, functions of the integrated software are added to an ERP system in the form of the description files, adaptation does not need to be developed for the abnormal software, the function adaptation of the abnormal software can be completed only by means of the integrated platform with a unified description word contract, the application software and the ERP system can be guaranteed to be stable in information interaction through unified limitation of the integrated platform, meanwhile, application can be rapidly expanded, the ERP system can be guaranteed to be rapidly upgraded in an iteration mode, and business management requirements are met.
The present application further provides an integrated platform and a computer-readable storage medium, which have the above-mentioned advantages and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a compatible method for integrating software in an ERP system according to an embodiment of the present application;
fig. 2 is a schematic physical structure diagram of an integration platform according to an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The present application further provides an integrated platform of an application component, comprising:
a communication component for acquiring application software;
the data contract component is used for carrying out format conversion on the application software based on the descriptor contract to obtain a description file;
and the software access component is connected with the ERP system, and accesses the description file to the ERP system.
The communication component is mainly used for acquiring application software, and the specific structure of the communication component is not limited herein, and the communication component may be a network port so as to acquire application software released on a network or application software in a database. And the device can also be a data transmission port to acquire application software on other devices. It should be particularly noted that the communication component may directly connect to ISVs (Independent Software developers), that is, directly obtain corresponding application Software from a release platform of an Independent Software developer, which is beneficial to updating the application Software in real time. In addition, the communication component can also be directly connected with a software project hosting platform and used for directly acquiring application software on the hosting platform so as to expand software in the integrated platform.
In addition, the communication component can also be used for accessing a public cloud platform, and the public cloud platform is a shared platform of the EPR system. It should be noted that the public cloud platform is not used for acquisition of application software, but for sharing of different ERP systems. The integration platform disclosed by the embodiment is used for upgrading or adding application software to an ERP system, and different EPR systems have the requirement, and can be butted with the integration platform disclosed by the embodiment to realize iterative updating of the ERP system per se and meet the support of new software or new version software. Namely, the communication component accesses the public cloud platform, meanwhile, the ERP systems access the public cloud platform, and updating iteration of the application software of the communication component is achieved by means of the public cloud platform. Of course, on the basis of the present embodiment, those skilled in the art may also adopt other platforms or networks similar to the public cloud platform, which should be within the protection scope of the present application.
From the above, it can be seen that the communication component, as an important component of the integration platform, not only needs to acquire application software, but also can undertake the communication function between the ERP system and the integration platform. It is to be noted, however, that in this process, the communication component does not perform the transfer of the description file.
The data contract component is the core of the integrated platform and aims to convert the format of the application software based on the descriptor contract. It should be noted that, in this step, the application software refers to a functional application, that is, one application software may be composed of a plurality of functions, and each function may obtain one description file after being converted by the descriptor contract format. In the integrated platform, however, different functional applications belonging to the same application software are still stored in the relationship between the application software and the function. For example, an excel table and a word document belong to two different applications, both of which include a copy function, but actually, because application software is different, it is obvious that codes corresponding to execution functions are different when the excel table and the word document are applied in an ERP system, and the copy function in the word cannot be directly applied to the excel table, or can be used but has abnormal problems such as messy codes. At this time, for the copy function in the excel table and the word document, after format conversion of the data contract component in the integrated platform, the obtained description files are also different, and the respective obtained description files can be stored in respective corresponding storage spaces belonging to the excel table and the word document. In addition, the same application software has different versions and different functions, and taking word documents as an example, the word documents comprise 2003 versions and 2020 versions, and generally the software can be compatible with the old version, but the old version of software is difficult to be compatible with the new version or even cannot be compatible with the new version of software. If the word document in the ERP system only supports 2003 edition, the ERP system is obviously not suitable for the current application environment, at this time, format conversion is carried out on corresponding functions in 2020 edition of the word document to obtain a description file based on the description word contract, and the description file is stored in an integrated platform, and then the ERP system can directly use the description file to carry out function upgrade.
The description word contract mainly comprises key attributes, key description, standard interface format and description file format. The key attribute and the key description refer to corresponding attributes and functions of the function, the standard interface format is the limitation of a description word contract on application, the description file format can be various, and different EPR systems adopt different formats, so that the configurable description file format can correspondingly exist in various forms, such as json, XML, characters or character strings and the like, which can be used as the description file format. The descriptor contract is defined on a class, and ensures the assumed conditions to be obeyed by class implementers (i.e. the integration platform in the embodiment), class users (i.e. the ERP system) and class extenders (referring to software extension operations when the application software is newly added). The descriptor contract specifies the constraints that a class consumer must adhere to before using the class, and this constraint is also a constraint that class implementers and class extenders must adhere to when using the class. The descriptor contract includes 3 types of constraints.
(1) Invariance: invariants are predicates that are true for all instances of the class. Invariants are constraints related to classes or interfaces. Invariants are typically used to account for consistency constraints between class attributes.
(2) Precondition: is a predicate that must be true before the operation is called. Preconditions are associated with a particular operation to account for constraints that a class consumer must satisfy before invoking a service.
(3) Post-processing conditions: is a predicate that must be true after the call operation. The postconditions are associated with a particular operation and are used to illustrate the constraints that the class implementer and class extender must satisfy after invoking the service.
The descriptor contract may be implemented by a contract definition component for defining or updating the descriptor contract.
The software access component is used for accessing the description file into the ERP system, namely configuring the description file for the ERP system. It should be noted that the access process is equivalent to copying a description file to the ERP system, and when the integration platform interfaces multiple EPR systems through a public cloud platform, multiple ERP systems may simultaneously own the same description file.
After the ERP system owns the description file, the support of the corresponding function of the description file can be realized. It is readily understood that the present embodiment default ERP system may parse and support the description file. And in fact, the description file may be understood as a program or code corresponding to the developed software function. However, because the description file is adapted based on the unified description word contract, the corresponding function extension or function update does not need to be developed for the ERP system, and the description file can be directly used as a code or a program corresponding to the function extension or function update, so that the update period of the ERP system is greatly shortened.
Meanwhile, on the basis of the embodiment, a close corresponding relationship does not exist between the ERP system and the application software, that is, the application software does not need to adapt to the ERP system, but only needs to perform format conversion according to the descriptor contract. Meanwhile, each EPR system can also perform function expansion or function updating of the application software based on the descriptor contract, and the application software is more convenient and faster to access.
On the basis of the embodiment, the software access component may include the following units:
the system comprises a standardization unit for providing standard functional components, an application access unit for providing software support components, an application form interaction unit for providing visual components and an extension unit for providing non-standard functional components. Of course, the software access component may also include a user experience unit, a detection and update unit, and the like. Each unit contains a software function description file of a corresponding function, for example, a standardized unit can contain a description of rape in the past of the conventional function, an application form interaction unit can contain a related description file of the form function, and the like.
A plurality of units are configured in the software access component so as to classify and manage the description files of the functions, and the system iteration requirement of the EPR system can be adapted more quickly.
Further, more preferably, the integration platform may further include a universal software development kit for providing an instruction manual describing the word contract. The general software Development kit, i.e. the general sdk (software Development kit), may contain relevant documents, paradigms, tools, etc. that assist in developing software.
On the basis of the integrated platform, the ERP system can be quickly constructed, namely material data contained in the ERP system, such as finance, budget, assets, projects, contracts, purchases, bids, stocks, plans, sales, production and manufacture, equipment, engineering, electronic commerce, human resources, administrative offices, analysis and decision, management functions, business processes, data query, user interface styles and the like, can be determined, so that description files of corresponding functions can be directly selected from the integrated platform, one-key configuration of application software in the ERP system is realized, and the development period of the ERP system is shortened.
The following describes a compatible method for integrating software in an ERP system according to an embodiment of the present application, and the compatible method described below and the integration platform described above may be referred to correspondingly.
Referring to fig. 1, fig. 1 is a flowchart of a compatible method for integrated software in an ERP system according to an embodiment of the present application, where the specific technical solution of the compatible method for integrated software in an ERP system is as follows:
s101: acquiring material data of the ERP system;
the method aims to obtain the material data of the ERP system, the representation mode of the material data is not limited, and generally, more integrated drawings are adopted by the ERP system. The material data comprises the type and version of the integrated software contained in the ERP system. Further, interface information of each integrated software may be included.
It should be noted that the material data obtained in this step is the latest material data of the ERP system, that is, the latest material data of the ERP system is obtained on the current ERP system. In addition, the material data does not necessarily contain all integrated software of the ERP system, and may only contain integrated software that the ERP system needs to be extended or updated.
S102: judging whether the integrated software in the material data is compatible; if not, the step S103 is entered;
the step aims to judge whether the integrated software is compatible, namely whether the integrated software is available in the ERP system, and specifically mainly judges whether the integrated software in the material data is a new version software or a new software, and if the version of the integrated software is updated, the situation that the original function cannot be supported may occur. And the new software generally needs to be expanded in function, that is, the current EPR system may not meet the support of the function corresponding to the material data acquired in S101.
If the new version software does not exist in the material data, the new software does not exist, which indicates that the application software in the ERP system does not need to be updated at this time, and the subsequent steps do not need to be executed at this time.
S103: determining a description file corresponding to integration software with compatible exception from an integration platform;
in this embodiment, the default integration platform includes a description file corresponding to the integration software with compatible exceptions, and the description file should be generated at least before this step is executed. The description file is a functional component generated based on the description word contract corresponding to the integration platform. The description document has been described above in the integrated platform, and is not repeated here, and both can be referred to each other.
In this step, only the integrated software with the compatible exception needs to be determined, and when the corresponding description file is searched, the material list obtained in step 101 should be referred to. When the ERP system updates the application software, the application software is not necessarily updated to the latest version or all functions, so when the description file is determined, the determination should be strictly determined according to the software functions and version information described in the bill of materials.
In this step, the corresponding description file may be determined directly by the software access component described above.
S104: and accessing the description file into the ERP system.
The step aims to access the description file to the ERP system so as to realize the updating of the application software of the ERP system. It should be noted that after the description file is accessed to the ERP system, the ERP system may continue its business functions. If the new version software or the new software is researched, developed and adapted, the ERP system cannot perform the service function or the service of the ERP system is influenced in the research, developed and adapted process, obviously, the time required for accessing the description file into the ERP system is far shorter than the research, developed and adapted process, so that the time required for updating the integrated software of the EPR system can be greatly reduced, and the service influence on the ERP system is reduced.
It should be noted that, by default, before the embodiment is executed, the integration platform is already built, that is, the definition of the descriptor contract of the integration platform is completed, and meanwhile, the integration platform completes format conversion of the description file for the new version software or the new software, and stores the description file to the integration platform.
According to the embodiment of the application, when integrated software compatible with abnormity exists in material data, the description file of the abnormal software is acquired from the integrated platform in a gathering mode, the functions of the integrated software are added to the ERP system in the form of the description file, adaptation does not need to be developed aiming at the abnormal software, the function adaptation of the abnormal software can be completed only by means of the integrated platform with a unified description word contract, the stability of information interaction between the application software and the ERP system can be guaranteed through unified limitation of the integrated platform on the application software, meanwhile, the application can be rapidly expanded, the ERP system can be rapidly updated in an iteration mode, and the service management requirements are met.
Referring to fig. 2, fig. 2 is a schematic diagram of a physical structure of an integrated platform provided in an embodiment of the present application, which may have a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 622 (e.g., one or more processors) and a memory 632, and one or more storage media 630 (e.g., one or more mass storage devices) for storing applications 642 or data 644. Memory 632 and storage medium 630 may be, among other things, transient or persistent storage. The program stored on the storage medium 630 may include one or more modules (not shown), each of which may include a sequence of instructions operating on a computing device. Still further, the central processor 622 may be configured to communicate with the storage medium 630 to execute a series of instruction operations in the storage medium 630 on the computing device 600.
The control device 600 may also include one or more power supplies 626, one or more wired or wireless network interfaces 650, one or more input-output interfaces 658, and/or one or more operating systems 641, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
The steps in a compatible method for integrating software in an ERP system described in fig. 1 above may be implemented based on the structure shown in fig. 2.
The present application also provides a computer readable storage medium having stored thereon a computer program which, when executed, may implement the steps provided by the above-described embodiments. The storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the system provided by the embodiment, the description is relatively simple because the system corresponds to the method provided by the embodiment, and the relevant points can be referred to the method part for description.
The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A compatible method for integrating software in an ERP system is characterized by comprising the following steps:
acquiring material data of the ERP system;
judging whether the integrated software in the material data is compatible;
if not, determining a description file corresponding to the integration software with compatible exception from the integration platform; the description file is a functional component generated based on a description word contract corresponding to the integration platform;
and accessing the description file into the ERP system.
2. The compatibility method of claim 1, wherein determining whether the integrated software in the material data is compatible comprises:
judging whether the integrated software in the material data is a new version software or a new software;
and if the integrated software is a new version of software or new software, executing a step of determining a description file corresponding to the integrated software with compatible exception from the integrated platform.
3. The compatible method according to claim 1, before obtaining the material data of the ERP system, further comprising:
defining a descriptor contract of the integration platform;
the descriptor contract includes key attributes, key descriptions, standard interface formats, and description file formats.
4. The compatible method of claim 3, further comprising, after defining the descriptor contract for the integration platform:
receiving new version software or new software;
carrying out format conversion on the new version software or the new software based on the description word contract to obtain a description file in the description file format;
adding the description file to the integration platform.
5. An integrated platform of application components, comprising:
a communication component for acquiring application software;
the data contract component is used for carrying out format conversion on the application software based on the descriptor contract to obtain a description file;
and the software access component is connected with the ERP system, and accesses the description file to the ERP system.
6. The integration platform of claim 5, wherein the software access component comprises:
the system comprises a standardization unit for providing standard functional components, an application access unit for providing software support components, an application form interaction unit for providing visual components and an extension unit for providing non-standard functional components.
7. The integrated platform of claim 6, wherein the communication component is further configured to access a public cloud platform, the public cloud platform being a shared platform of the EPR system.
8. The integration platform of claim 6, further comprising:
a universal software development kit for providing an instruction manual describing the word compact.
9. The integration platform of claim 6, further comprising:
a contract definition component for defining or updating the descriptor contract.
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 a compatible method of integrating software in an ERP system according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011285258.2A CN112379920A (en) | 2020-11-17 | 2020-11-17 | Compatible method, integrated platform and storage medium for integrated software in ERP system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011285258.2A CN112379920A (en) | 2020-11-17 | 2020-11-17 | Compatible method, integrated platform and storage medium for integrated software in ERP system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112379920A true CN112379920A (en) | 2021-02-19 |
Family
ID=74584994
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011285258.2A Pending CN112379920A (en) | 2020-11-17 | 2020-11-17 | Compatible method, integrated platform and storage medium for integrated software in ERP system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112379920A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030212766A1 (en) * | 2001-10-17 | 2003-11-13 | Giles Gary W. | Manufacturing method and software product for optimizing information flow |
| US20070150490A1 (en) * | 2005-12-22 | 2007-06-28 | Sap Ag | Items on workplaces |
| CN101840334A (en) * | 2010-04-16 | 2010-09-22 | 中国电子科技集团公司第二十八研究所 | Software component service packaging method |
| CN102567838A (en) * | 2010-12-30 | 2012-07-11 | 中国移动通信集团公司 | Collaborative development system and collaborative development method |
| CN111427610A (en) * | 2020-03-25 | 2020-07-17 | 山东浪潮通软信息科技有限公司 | Method, device, equipment and readable medium for integrating third-party services |
-
2020
- 2020-11-17 CN CN202011285258.2A patent/CN112379920A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030212766A1 (en) * | 2001-10-17 | 2003-11-13 | Giles Gary W. | Manufacturing method and software product for optimizing information flow |
| US20070150490A1 (en) * | 2005-12-22 | 2007-06-28 | Sap Ag | Items on workplaces |
| CN101840334A (en) * | 2010-04-16 | 2010-09-22 | 中国电子科技集团公司第二十八研究所 | Software component service packaging method |
| CN102567838A (en) * | 2010-12-30 | 2012-07-11 | 中国移动通信集团公司 | Collaborative development system and collaborative development method |
| CN111427610A (en) * | 2020-03-25 | 2020-07-17 | 山东浪潮通软信息科技有限公司 | Method, device, equipment and readable medium for integrating third-party services |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11789715B2 (en) | Systems and methods for transformation of reporting schema | |
| US8671222B2 (en) | Systems and methods for dynamically deploying an application transformation tool over a network | |
| US10481884B2 (en) | Systems and methods for dynamically replacing code objects for code pushdown | |
| US8739150B2 (en) | Systems and methods for dynamically replacing code objects via conditional pattern templates | |
| US8898627B2 (en) | Systems and methods for applying rules to transform objects of an application | |
| US8572566B2 (en) | Systems and methods for analyzing changes in application code from a previous instance of the application code | |
| US8549514B2 (en) | Distributing customized software products | |
| US9405532B1 (en) | Integrated cloud platform translation system | |
| US8706771B2 (en) | Systems and methods for analyzing and transforming an application from a source installation to a target installation | |
| KR101795844B1 (en) | Runtime system | |
| US20230244465A1 (en) | Systems and methods for automated retrofitting of customized code objects | |
| EP2779582B1 (en) | Automatic mobile application discovery and integration in a mobile telecommunication device | |
| US20040068715A1 (en) | System and method for migration of software | |
| CN109117164B (en) | Micro-service updating method and system based on difference analysis of key elements | |
| US10901804B2 (en) | Apparatus and method to select services for executing a user program based on a code pattern included therein | |
| CN115794214B (en) | Application module metadata management method, device, storage medium and apparatus | |
| Kano | Kachako: A Hybrid-Cloud Unstructured Information Platform for Full Automation of Service Composition, Scalable Deployment and Evaluation: Natural Language Processing as an Example | |
| CN112379920A (en) | Compatible method, integrated platform and storage medium for integrated software in ERP system | |
| US20050137846A1 (en) | On-demand creation of Java locale source | |
| CN109299004B (en) | Method and system for analyzing difference of key elements | |
| US9369352B1 (en) | Method of capturing server and operating system metrics for virtual to physical topology reporting | |
| WO2011041246A1 (en) | Systems and methods for analyzing and transforming an application from a source installation to a target installation | |
| CN117111994A (en) | Project operation method and device | |
| CN114924721A (en) | Code generation method and device, computer equipment and storage medium | |
| CN117806652A (en) | Component conversion system construction method, component conversion method, device and electronic equipment |
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 |