Building an ERP integrated business data migration system

Abstract

Provides an integrated data migration system for ERP systems. A means for reading a migration object, a means for selecting an API according to the data, An ERP integrated data migration system that has a means for editing and saving templates that are compatible with APIs, a means for inputting data into the templates to register and update ERP data, and a means for taking a log of the process from inputting the data to registering and updating it.

Description

[Technical Field]

[0001] The present invention relates to the construction of a business data migration mechanism for enterprise resource planning (ERP), and more particularly to the construction of an integrated data migration mechanism for ERP. [Background technology]

[0002] In recent years, integrated business systems have been developed and used to centrally manage a company's core business. Well-known examples include SAP ECC6.0 and SAP S / 4HANA, but in these systems, data migration objects are not categorized by business area, and registration templates are managed separately for each migration object, resulting in different data entry operations.

[0003] Therefore, the data migration task for ERP systems requires collaboration between specialized consultants who are familiar with ERP systems and the business users in charge of the current system who manage the business data. However, due to differences in their understanding and perspectives, input errors and rework often occur in the migration data preparation task, which is a major obstacle to the progress of the data migration task.

[0004] Furthermore, while ERP systems are equipped with a function for registering initial business data, they do not support update functions. This is because business data migration is a one-time task in which large amounts of business data (master data, unreconciled transaction data) accumulated in existing business systems are initially registered in the new ERP system, as it is necessary to ensure continuity of the target business operations between the old and new systems when a new ERP system is introduced. For this reason, while initial registration functions are generally available, update functions for modifying migrated data are not provided as standard specifications.

[0005] However, in order to ensure the accuracy of the initial data while efficiently progressing work on-site during ERP implementation projects, an update function for migrated data is required. Because ERP system data is a company's core business integration system, ensuring consistency between each migrated data object is a top priority. Therefore, in order to correct some data errors, it is essential that specialized consultants plan, implement, and monitor the disposal of erroneous data, differential re-migration, and data entry order adjustment. In some cases, this can require initializing the already-built ERP system and re-executing the migration tasks.

[0006] There have been inventions of methods for converting data between ERP and other systems (for example, Patent Document 1), but these involve converting ERP format data into other companies' formats, and then converting the other companies' formats back into ERP format. This requires that a separate conversion system be created for each company, and is therefore not versatile.

[0007] Furthermore, because the data migration methods provided by ERP systems are specialized for system users, if a business user needs to perform master data maintenance or input large amounts of transaction data after the ERP system has been put into production, the data migration mechanism cannot be reused. For this reason, it is commonly understood in the industry that a dedicated program for each project should be developed as a tool for maintaining business data, making full use of the APIs provided by the ERP system.

[0008] Given the above background, ERP system data migration is the most important issue when implementing an ERP system. Data migration failures due to flaws in the current data migration system or lack of coordination or collaboration between participating personnel often occur, and in some cases this can become a major social problem, such as halting a company's manufacturing, sales, and shipping operations.

[0009] Therefore, there was a need for a data migration system that could manage data migration tasks from the perspective of business users and perform data migration to the ERP system in an integrated, centralized, and comprehensive manner. [Prior art documents] [Patent documents]

[0010] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-99070 Summary of the Invention [Problem to be solved by the invention]

[0011] We provide a data migration mechanism when implementing an ERP system. [Means for solving the problem]

[0012] (1) A system capable of centralized and comprehensively managing the migration of initial business data during the implementation of an ERP system. This system includes a means for centralized management of migration objects, a means for selecting corresponding APIs according to the migration data, a means for editing and saving templates corresponding to each API, a means for inputting data into the corresponding templates and registering and updating data in the ERP system, and a means for recording a log of the process from inputting the data to registering and updating the data. Here, "centralized and comprehensive management" means "integrating ERP APIs and corresponding add-on programs into a single program and managing them in a centralized and comprehensive manner." More specifically, this refers to the comprehensive, integrated management of over 80 types of SAP APIs and their corresponding add-on programs in a single program. Similar functions and extensions based on the above concept are also within the scope of the claim. (2) An integrated data migration mechanism for the ERP system described in (1) that includes a registration and update module for data objects required for ERP business data migration. (3) The ERP system integrated data migration mechanism of (1) above, in which the format that can be uploaded to the ERP system is Excel format. Here, the ERP system integrated data migration mechanism refers to a mechanism or system that migrates data that has been integrated to be compatible with the ERP system. (4) An ERP system data migration mechanism (3) that provides a means for inputting data via Excel. (5) The ERP system integration data migration mechanism described in (1) allows users to select APIs from a list managed for each business area. [Effects of the Invention]

[0013] According to the present invention, the initial business data migration to the ERP system is managed in an integrated, centralized and comprehensive manner, the registration and update functions are complete, and business users can continue to operate it as business data maintenance even after the system is put into production. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram showing an overview of the present invention. [Figure 2] FIG. 2 is a diagram showing the screen configuration of the present invention. [Figure 3] FIG. 3 is a flowchart of obtaining a migration object. [Figure 4] Figure 4 is a table that defines the hierarchy and contents of the migration objects. [Figure 5] FIG. 5 shows the hierarchy and contents of an actual migration object. [Figure 6] FIG. 6 is a flowchart of template maintenance. [Figure 7] FIG. 7 shows the selection screen for creating an actual template. [Figure 8] FIG. 8 is a table that defines the template maintenance screen. [Figure 9] FIG. 9 shows an actual template maintenance screen. [Figure 10] FIG. 10 is a diagram showing a table in which migration data is prepared in an actual template. [Figure 11] FIG. 11 is a flowchart showing the migration data entry. [Figure 12] FIG. 12 shows a selection screen for inputting actual migration data. [Figure 13]Figure 13 shows the context check simulation input screen for actual migration data. [Figure 14] FIG. 14 is a diagram showing the data update module function arrangement. [Figure 15] FIG. 15 is a flowchart showing the process log display. [Figure 16] FIG. 16 is a selection screen showing the actual processing log. [Figure 17] FIG. 17 is a diagram showing the actual data input process log. DETAILED DESCRIPTION OF THE INVENTION

[0015] ERP (Enterprise Resource Planning) includes functions for the integrated management of a wide range of business areas. For example, ERPs that include multiple functions such as financial accounting, management accounting, sales and distribution, purchasing and procurement, inventory and warehouse management, production management, human resources management, and project management are well known. Specific product names include SAP S / 4HANA, Oracle ERP Cloud, and Microsoft Dynamics 365, with SAP having the largest global market share and being adopted by many large companies.

[0016] However, in order to input a large amount of data, including initial business data, into an ERP system all at once, They must be registered and updated according to the specifications of the APIs (for example, S / 4HANA function modules, BAPIs, IDOCs, etc.) established in the ERP system. Function modules and BAPIs are "a group of APIs that come standard within SAP ERP" and are created using ABAP (Advanced Business Application Programming), SAP's proprietary language. The content of BAPIs is almost the same as standard function modules, but while function modules only operate within SAP ERP, BAPIs can be called from external systems.

[0017] API stands for Application Programming Interface, and is an interface that allows applications to exchange functions and data with each other. In the SAP system domain, this corresponds to "function modules" and "BAPIs." The purpose of using APIs is to ensure that large volumes of data are registered and updated in bulk and accurately according to the definitions in the ERP system database. However, to effectively activate the APIs provided by the ERP system, it is essential to create add-on programs according to the parameters defined in the API.

[0018] An add-on program is generally a program that adds new functions to existing software or applications, but here it refers to an extension program developed to meet a company's unique business requirements that cannot be met with the standard ERP (SAP) functions. Add-on programs are programmed by specialized consultants using a special programming language (ABAP) on the ERP system platform, and the business user sequentially reads data records from prepared data files (text files, Excel files, etc.), converts and maps them to API parameters in the program, and finally activates the API to input data. A mechanism for logging the results of each input is also required.

[0019] However, creating a corresponding add-on program for every migration object in an ERP system requires a huge amount of work, and it is not a realistic solution to quickly update the specifications of the add-on program to match frequently changing data migration requirements.

[0020] This invention enables the migration of business data from ERP systems in an integrated, centralized, and comprehensive manner using a single program. Traditionally, when implementing an ERP system, migration objects were managed separately and not grouped by business area, and the migration operations for each were not standardized, forcing developers to rely on specialized consultants. Here, a migration object is a grouping of target data types when migrating data to an SAP system. For example, item data, customer data, etc., each fall under the category of migration object.

[0021] Furthermore, ERP only supported a data entry function as a data migration mechanism, and did not support an update function. To implement the update function, it was necessary to create and use an add-on program using the API specified by the ERP system for each migration data object. However, because the specifications of the APIs provided by ERP systems differ depending on the business area, specialized consultants had to research, analyze, implement, and test the target APIs each time according to the customer's data migration requirements to ensure the effectiveness of the API.

[0022] Furthermore, even if business users wanted to create add-on programs, they would have difficulty doing so on their own because the ERP system uses its proprietary programming language, ABAP, and would need to hire an expert. However, while some ABAP programming may be possible using generative AI, it is still preferable for an expert to check the program.

[0023] This invention provides a program that allows business users to easily complete data migration by utilizing functions such as selection, preparation, check, input, and tracking of target business migration data on a single integrated screen, even without employing experts with such advanced skills.

[0024] Furthermore, it is not limited to the scope of initial business data migration, and even after the ERP system is put into production, it has functions for continuous operation such as master data maintenance for each business area and input of large amounts of transaction data. For example, data such as customer master and purchase master usually needs to be entered one by one, but by using the mechanism of this invention, large amounts of data can be registered and updated in a lump.

[0025] The program of the present invention is roughly divided into three parts. The process involves creating a migration data collection template, inputting migration data, and checking the processing log (Figure 1). First, a business user reads the migration data objects from a pre-prepared migration object management table and creates a migration template (Excel format) that meets the migration data requirements. The migration template is created according to the API parameter items defined for each migration object.

[0026] The business users of the current system then organize the collected business migration data according to the migration template, and finally input the collected migration data into the specified program, where the organized migration data is registered and updated in the ERP system according to the API specifications for that function. Because the migration template created here strictly adheres to the API rules specified in the ERP system, the migration data organized in accordance with it meets the business migration requirements. After input, a log is saved, so if an error occurs, the problem can be identified and addressed (Figure 2).

[0027] The overall system is configured as shown in Figure 2. First, the migration objects are read from the management table (migration object library) as shown in Figure 3. The migration object management table consists of six levels, divided into area, business area, data type, data object name, operation type, and transaction code (Figure 4). The definitions for each level are also shown in Figure 4. To select or upload an object, you can press the round clock mark in the upper left of the screen, or select it from the header menu (not always shown).

[0028] Only a portion of the data object names are shown. Double-clicking a transaction code will take you to the corresponding transaction screen. A transaction is a unit or data that groups multiple processes together, and in this case refers to the operation of registering and updating transaction data in SAP. Another advantage is that you can jump to the template creation screen from the program name of this migration object library, allowing you to intuitively select an API based on its function (Figure 5).

[0029] Next, a migration template for inputting data is created (Figure 6). Templates retrieved from the template management table can be edited, or edited templates can be saved or deleted. To edit a template, the appropriate API is selected from the selection screen. If this is the first time, a table with all items displayed and check boxes for adding or deleting items will be displayed, or a predefined template will be displayed, and the business user can select the items required to meet their migration requirements (Figures 8 and 9).

[0030] The API definition data has been broken down into items that can be selected individually; checking the square box to the left of an item in the top of Figure 8 or the box on the left side of Figure 9 selects that item and adds it to the template as an item, as shown in the bottom of Figure 8. In the example in the figure, when vertically arranged items are selected, the selected items are displayed in the table in the same vertical order, but this format is not necessary, and any mechanism will do as long as the selected items are properly reflected in the table.

[0031] The selected items are reflected in the migration template and can be downloaded as an Excel file. Conversely, you can remove items from an existing template by unchecking the square box. In the template downloaded to an Excel file (Figure 10), lines 1 to 6 are used as the API control item area, and lines 7 and onwards are used as the migration data maintenance area.

[0032] To input migration data (Figure 11), select online execution (specifying an Excel file) or background execution (specifying a server file) from the migration data input selection screen (Figure 12).

[0033] When running online, the contents of the Excel file are displayed on the screen and a context check is performed on the migration data. The context check process includes item definition length, domain check, amount, date item, and null item. If there is a problem with the context check, the data is not entered, the relevant item in the Excel file is corrected, the file is uploaded again, and a context check is performed. The context check is performed until there are no more check errors, and once there are no more problems, the migration data is entered. The migration data is sent to the ERP server (not shown) and registered.

[0034] Additionally, a pre-data entry simulation processing function will also be implemented to check the consistency of the migrated data. Pre-data entry simulation refers to a simulation process that executes the API once to check the consistency of the data (for errors in master data, etc.) when data is entered using the API, but does not commit the process to the database, but is instead performed to check the entered data.

[0035] However, it is possible to not restrict data input processing regarding simulation errors, or it is also possible to specify specifications that restrict it. The input method can be both online and background, and in the case of background processing requests, a data input log confirmation function is also implemented at any time.

[0036] In anticipation of large-volume data import, it is also possible to specify a server file directly in the background from the selection screen for importing migration data (Figure 12). In this case, the context check function is processed in background mode, a processing log is recorded, and if a context check error occurs in even one item, the data import process is stopped. This can also be achieved by changing the specified item value or using the update API, as in the data update function (Figure 14).

[0037] Checking the migration data log (Figure 15) When migration data is entered, the return value or message from the ERP system's API is logged. The migration data logging unit is based on the API execution unit, with the start and end clearly indicated, and the number of processed items, successful items, and error items counted and output. Business users can specify the processing log on the migration data log selection screen (Figure 16) to display a screen (Figure 17) where they can inquire about the execution log, and it is also possible to download it in Excel if necessary. [Industrial Applicability]

[0038] The present invention can be used by companies (including manufacturing and service industries) that are introducing ERP systems.

Claims

1. A system that can comprehensively and centrally manage business data migration and / or updates at the time of ERP system implementation and after initial data registration, A means for reading a migration object selected from a migration object management table; a means for reading from a template management table a template in which API definition data corresponding to the selected API is broken down into items and each item is selectable, and displaying the template on a screen; A means for editing the template according to the input and saving or deleting it from the template management table; A means for inputting the input migration data into the template and registering or updating the database of the ERP system; A means to take a log of the data from inputting it into the template to registering and updating it in the ERP system and display it on the screen. An integrated data migration mechanism to ERP systems.

2. 2. The ERP data migration system of claim 1, comprising an API for a given migration object.

3. The ERP data migration system of claim 1, wherein the format that can be uploaded to the ERP system is Excel format.

4. The ERP system data migration mechanism of claim 1, which is provided with a means for inputting data via Excel.

5. The ERP system data migration mechanism of claim 1, which allows APIs to be selected from a list managed for each business area.

Images