SAP service calling method based on financial platform

Abstract

The invention belongs to the field of SAP systems, and particularly discloses an SAP service calling method based on a financial middle table, which comprises the following steps of: eliminating a personalized customization part, concluding and defining public core functions of the SAP system, and dividing a plurality of public core function types; independently packaging each function module of each common core function type; carrying out secondary packaging on the packaged function module based on standard function configuration information selected in advance; carrying out service registration on the SAP system on a financial platform; and the shared financial platform calls each function module of the SAP system by calling the registration service on the financial platform. According to the method, the fusion difficulty of the SAP system to the financial platform is reduced, so that the calling difficulty is reduced, the calling performance stability is improved, and efficient calling is realized.

Description

Technical Field

[0001] The present invention belongs to the field of SAP systems, and in particular relates to a SAP service calling method based on a financial middle station. Background Art

[0002] The financial management system with "SAP system + financial system" as the core has efficiently integrated and optimized the allocation of various resources in the information and intensive stage to promote the development of financial management. With the changes in business and the improvement of technical means, in order to solve the problem of interconnection and interoperability, it is necessary to integrate the core business and capabilities of SAP finance and output them to the platform-based, service-oriented, unified and stable "middle platform system".

[0003] However, the SAP system is intricately linked with many external systems, and the modules within SAP itself are highly correlated and logically complex. In addition, the functional modules in the SAP system often contain a large amount of personalized customization content. These customizations make it difficult for SAP systems between different companies to implement standardized service calls, resulting in high requirements on the skills of practitioners and long transformation time in the process of integrating the SAP system into the middle-office system, which in turn increases the difficulty of calling the SAP system and leads to unstable calling performance. Summary of the invention

[0004] To solve the above problems, the present invention provides a SAP service calling method based on the financial middle platform, which simplifies the system structure, reduces the difficulty of integrating the SAP system into the financial middle platform, thereby reducing the calling difficulty, improving the calling performance stability, and realizing efficient calling.

[0005] The technical solution of the present invention is a SAP service calling method based on a financial middle station, comprising the following steps: Eliminate the personalized customization part, summarize and define the common core functions of the SAP system, and divide them into several common core function types; Each functional module of each common core functional type is encapsulated independently; The packaged functional modules are repackaged based on the pre-selected standard functional configuration information; Register the SAP system as a service on the financial middle platform; The shared financial platform calls the various functional modules of the SAP system by calling the registration service on the financial middle platform.

[0006] In an optional embodiment, the common core function types include accounting voucher class functions for processing accounting vouchers, budget management class functions for processing budget management, procurement management class functions for processing procurement management, accounts receivable management class functions for processing account clearing transactions, monthly and annual settlement class functions for processing asset settlement, and asset management class functions for processing asset management.

[0007] In an optional implementation, the functional modules for independently encapsulating accounting voucher functions include an accounting voucher prefabrication functional module, an accounting voucher simulation functional module, an accounting voucher posting functional module, an accounting voucher write-off functional module, and an accounting voucher query functional module; The function modules for independently encapsulating budget management functions include budget maintenance and release function module, budget control verification function module, budget occupation and release function module, and budget execution query function module; The functional modules for independently encapsulating procurement management functions include the settlement history synchronization functional module, the invoice verification prefabrication functional module, the invoice verification posting functional module, and the order settlement locking functional module; The functional modules for independently encapsulating the transaction management functions include the residual clearing function module, the partial clearing function module, the standard clearing function module, and the clearing voucher reset function module; The function modules that independently package the monthly and annual settlement functions include the monthly settlement function module of the project in progress, the account balance query function module, and the asset depreciation operation function module; The functional modules that independently encapsulate asset management functions include asset card creation function module, asset transfer function module, asset message function module, and asset merger and splitting function module.

[0008] In an optional implementation, the packaged functional modules are repackaged based on pre-selected standard functional configuration information, specifically including configuring the following functional information for each functional module: Configure network access information, including using TCP / IP technology, using three-way handshake to establish a connection, and transmitting messages after segmentation; Configure data packaging information, including using JSON data format; Configuration data feedback information, including configuration common feedback information; Configuration construction management information, including inventory management of microservices and unified management of logs; Configure permission management information, including unified authorization management on the shared financial platform; Configure master data conversion information, including sampling the master data conversion method on the SAP side.

[0009] In an optional implementation, registering the SAP system as a service on the financial middle platform specifically includes: The unified service portal of the SAP system is built through the cloud service bus to complete the registration of the secondary packaged functional modules on the financial middle platform.

[0010] In an optional implementation, a unified service portal of the SAP system is constructed through a cloud service bus to complete the registration of the secondary packaged functional module on the financial middle platform, specifically including: Register the SAP system unified service entry address to the cloud service bus; The addresses generated by the cloud service bus are uniformly registered in the primary cloud service bus. The primary cloud service bus address is the universal interface address of the primary SAP system. Configure the interface code of each functional module.

[0011] In an optional implementation, the shared financial platform calls the various functional modules of the SAP system by calling the registration service on the financial middle platform, specifically including: The shared financial platform calls the general interface address of the SAP system through the financial middle platform, and adds the code parameter to the URL to specify the interface code of the function module to be called to complete the call of the corresponding service.

[0012] In an optional embodiment, the method further comprises the following steps: Select the target data in the SAP system to be synchronized to the financial center; Configure the synchronization mode of the target data.

[0013] In an optional implementation, the synchronization mode of the configured target data includes a real-time synchronization mode for newly added services and a small batch online synchronization mode for existing data.

[0014] The SAP service calling method based on the financial middle platform provided by the present invention has the following beneficial effects compared with the prior art: first, the personalized customization part is eliminated, the common core functions of the SAP system are summarized and defined, and its functional modules are independently packaged to achieve standardized processing of SAP system services and reduce the professional skills requirements for practitioners. At the same time, the personalized customization part in the SAP system is eliminated, and only the common core functions are retained to simplify the system structure, which not only makes it easier to integrate the SAP system into the middle platform system, but also significantly shortens the time for system transformation, improves work efficiency, improves transformation efficiency and accuracy, and thus improves service call stability. In addition, the packaged functional modules are secondary packaged based on the pre-selected standard functional configuration information to achieve standardized functional packaging and improve the performance after service packaging. By registering the service on the middle platform system, centralized management and unified calling of the packaged functional modules can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions of the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0015] Figure 1 The present invention provides a flowchart of a method for invoking a SAP service based on a financial middle station.

[0016] Figure 2 It is a schematic diagram of each functional module of each common core functional type.

[0017] Figure 3 This is a schematic diagram of the shared financial platform calling framework.

[0018] Figure 4 This is a diagram of accounting document service call.

[0019] Figure 5 This is a diagram of the project budget control service call. DETAILED DESCRIPTION

[0020] In order to enable those skilled in the art to better understand the scheme of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0021] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art of the present invention. The terms used in the specification of the present invention herein are only for the purpose of describing specific embodiments and are not intended to limit the present invention.

[0022] Figure 1 This is a flowchart of a SAP service calling method based on a financial middle platform provided by an embodiment of the present invention. According to different requirements, the order of the steps in the flowchart can be changed, and some can be omitted.

[0023] like Figure 1 As shown, the method includes the following steps.

[0024] S1, remove the personalized customization part, summarize and define the common core functions of the SAP system, and divide them into several common core function types.

[0025] This embodiment first disassembles the SAP core functions. In order to meet the requirements of various applications on the shared financial platform for the core functions of the SAP system, it is necessary to remove the personalized customization parts and define and disassemble the common core functions. The common core function types defined in this embodiment include accounting voucher functions for processing accounting vouchers, budget management functions for processing budget management, procurement management functions for processing procurement management, accounts receivable management functions for processing clearing transactions, monthly and annual settlement functions for processing asset settlement, and asset management functions for processing asset management.

[0026] S2, each functional module of each common core functional type is independently encapsulated.

[0027] Figure 2 It is a schematic diagram of each functional module of each common core functional type, such as Figure 2 As shown, the functional modules for independently encapsulating accounting voucher functions include an accounting voucher prefabrication functional module, an accounting voucher simulation functional module, an accounting voucher posting functional module, an accounting voucher write-off functional module, and an accounting voucher query functional module.

[0028] The functional modules that independently encapsulate budget management functions include budget maintenance and release functional module, budget control verification functional module, budget occupation and release functional module, and budget execution query functional module.

[0029] The functional modules that independently package the procurement management functions include the settlement history synchronization functional module, the invoice verification prefabrication functional module, the invoice verification posting functional module, and the order settlement locking functional module.

[0030] The functional modules that independently encapsulate the accounts receivable and payable management functions include the remaining account clearing function module, the partial account clearing function module, the standard account clearing function module, and the account clearing voucher reset function module.

[0031] The functional modules that independently package the monthly and annual settlement functions include the monthly settlement function module of the project in progress, the account balance query function module, and the asset depreciation operation function module.

[0032] The functional modules that independently encapsulate asset management functions include asset card creation function module, asset transfer function module, asset message function module, and asset merger and splitting function module.

[0033] S3, re-packaging the packaged functional modules based on pre-selected standard functional configuration information.

[0034] During the service packaging process, it is necessary to select multiple technical aspects, such as network access, data packaging, data feedback, construction management, authority management, master data conversion, etc. Different standards are used for the selection of various modules and services, which will affect the performance after service packaging. In this embodiment, the service transformation of the SAP system includes the selection of 6 aspects, including network access capability, data packaging capability, data feedback capability, construction management capability, authority management capability, and master data conversion capability.

[0035] Specifically, repackaging the packaged functional modules based on pre-selected standard functional configuration information includes the following steps.

[0036] S3.1, configure network access information, including using TCP / IP technology, using three-way handshake to establish a connection, and transmitting messages after segmentation.

[0037] Using TCP / IP technology, a three-way handshake is used to establish a reliable connection, the message size is automatically cut, and the data transmission is reliable.

[0038] S3.2, configure data packaging information, including using JSON data format.

[0039] The JSON data format is selected because it can directly express the data structure, the overall structure is compact, the file is small, the transmission and parsing system overhead is smaller and more convenient.

[0040] S3.3, configuration data feedback information, including configuration common feedback information.

[0041] Only common feedback information is agreed upon. Since the agreement is simple and clear, the standard is easier to implement, which is more conducive to simplifying the preliminary work and facilitating rapid practical application.

[0042] S3.4, configure construction management information, including inventory management of microservices and unified management of logs.

[0043] Based on the inventory management of microservices, logs are managed in a unified manner for easy centralized review.

[0044] S3.5, configure authority management information, including unified authorization management on the shared financial platform.

[0045] Unified authorization management on the financial platform facilitates the unification of SAP microservices and financial platform microservices.

[0046] S3.6, configure master data conversion information, including sampling SAP-side master data conversion methods.

[0047] The master data conversion on the SAP side is adopted. Since SAP has a comparison relationship between the master data from MDM and financial platform and the SAP master data, the conversion efficiency in SAP is high and it is externally friendly.

[0048] It should be noted that, on the premise of completing the first step of function decomposition, the above configuration information is selected in the service process to complete the secondary packaging of the service.

[0049] S4, register the SAP system as a service on the financial middle platform.

[0050] This embodiment performs service registration on the middle-office system to realize centralized management and unified calling of packaged functional modules. This embodiment builds a unified service portal of the SAP system through the cloud service bus to complete the registration of the secondary packaged functional modules on the financial middle-office, which specifically includes the following steps.

[0051] S4.1, register the SAP system unified service entry address to the cloud service bus.

[0052] S4.2, the address generated by the cloud service bus is uniformly registered in the first-level cloud service bus. The first-level cloud service bus address is the universal interface address of the first-level SAP system.

[0053] S4.3, configure the interface code of each functional module.

[0054] Exemplarily, the unified service entry address of the SAP system is registered on the provincial service bus (CSB / APIC); after completing this step, the address generated by the provincial service bus is uniformly registered on the first-level CSB. The first-level CSB address is the universal interface address of the SAP system of the corresponding provincial and municipal companies; when the platform applications call the SAP universal interface address, they add the code parameter to the URL and specify the specific interface code to be called to complete the call of the specific service.

[0055] S5, the shared financial platform calls the various functional modules of the SAP system by calling the registration service on the financial middle platform.

[0056] In this embodiment, the shared financial platform calls the general interface address of the SAP system through the financial middle platform, and adds a code parameter to the URL to formulate the interface code of the function module to be called, so as to complete the call of the corresponding service.

[0057] Figure 3 This is a schematic diagram of the shared financial platform call framework. This embodiment focuses on the core capabilities of SAP, based on the microservice and micro-application architecture of the shared financial platform, and encapsulates the core capabilities of the SAP system into services and registers them in the financial middle platform, integrating them into the financial middle platform architecture. The applications on the financial platform trigger the functions of the SAP accounting module by calling the services registered with SAP, and realize business processing such as voucher production, budget control, and invoice verification.

[0058] Taking accounting voucher service as an example, Figure 4This is a diagram of the accounting voucher service call. By encapsulating the SAP voucher generation function and registering the service in the financial middle platform, the financial voucher generation service is provided for various applications on the platform. Each application uses the platform voucher generation information to call the middle platform voucher generation service to generate accounting vouchers.

[0059] Taking project budget control as an example, Figure 5 This is a diagram of the project budget control service call, which involves two links: project budget occupation and project budget release. When business personnel use the general accounting application in the financial middle office to initiate a project cost accounting application, the general accounting application calls the budget occupation service registered in the financial middle office to realize the project budget commitment occupation. When the user completes the financial accounting, the budget release service registered on the platform side is called to release the occupied committed budget and actually consume the project budget.

[0060] S6, select the target data in the SAP system to be synchronized to the financial center, and configure the synchronization mode of the target data.

[0061] In an optional implementation, in order to ensure that the business is not affected, part of the data is migrated to the middle office system. However, after several years of business accumulation, a huge amount of data has been stored in the SAP system. This embodiment configures the synchronization mode of the target data including a real-time synchronization mode for new business and a small batch online synchronization mode for existing data, to optimize and adjust the manual retransmission program for business and financial data, and to achieve small batch online synchronization of existing data to the business and financial library, thereby reducing the workload of offline manual sorting of existing data and improving switching work efficiency. In an optional implementation, data synchronization involves the following data scopes: 1. Project date; 2. WBS; 3. Purchase order; 4. Work order; 5. Internal order; 6. Account settings in purchase vouchers; 7. Purchase voucher historical details; 8. Material vouchers; 9. Service confirmation; 10. Storage material consumption list; 11. Storage material consumption dump list; 12. Engineering material activation information.

[0062] The above disclosure is only a preferred embodiment of the present invention, but the present invention is not limited thereto. Any non-creative changes that can be thought of by a person skilled in the art, as well as several improvements and modifications made without departing from the principle of the present invention, should fall within the protection scope of the present invention.

Claims

1. A SAP service calling method based on a financial middle station, characterized in that: The following steps are involved: Eliminate the personalized customization part, summarize and define the common core functions of the SAP system, and divide them into several common core function types; Each functional module of each common core functional type is encapsulated independently; The packaged functional modules are repackaged based on the pre-selected standard functional configuration information; Register the SAP system as a service on the financial middle platform; The shared financial platform calls the various functional modules of the SAP system by calling the registration service on the financial middle platform.

2. The SAP service calling method based on the financial middle station according to claim 1 is characterized in that: The common core function types include accounting voucher functions for processing accounting vouchers, budget management functions for processing budget management, procurement management functions for processing procurement management, accounts receivable management functions for processing account clearing transactions, monthly and annual settlement functions for processing asset settlement, and asset management functions for processing asset management.

3. The SAP service calling method based on the financial middle station according to claim 2 is characterized in that: The functional modules for independently encapsulating accounting voucher functions include accounting voucher prefabrication functional module, accounting voucher simulation functional module, accounting voucher posting functional module, accounting voucher write-off functional module, and accounting voucher query functional module; The function modules for independently encapsulating budget management functions include budget maintenance and release function module, budget control verification function module, budget occupation and release function module, and budget execution query function module; The functional modules for independently encapsulating procurement management functions include the settlement history synchronization functional module, the invoice verification prefabrication functional module, the invoice verification posting functional module, and the order settlement locking functional module; The functional modules for independently encapsulating the transaction management functions include the residual clearing function module, the partial clearing function module, the standard clearing function module, and the clearing voucher reset function module; The function modules that independently package the monthly and annual settlement functions include the monthly settlement function module of the project in progress, the account balance query function module, and the asset depreciation operation function module; The functional modules that independently encapsulate asset management functions include asset card creation function module, asset transfer function module, asset message function module, and asset merger and splitting function module.

4. The SAP service calling method based on the financial middle station according to claim 3 is characterized in that: The packaged functional modules are repackaged based on the pre-selected standard functional configuration information, specifically including configuring the following functional information for each functional module: Configure network access information, including using TCP / IP technology, using three-way handshake to establish a connection, and transmitting messages after segmentation; Configure data packaging information, including using JSON data format; Configuration data feedback information, including configuration common feedback information; Configuration construction management information, including inventory management of microservices and unified management of logs; Configure permission management information, including unified authorization management on the shared financial platform; Configure master data conversion information, including sampling the master data conversion method on the SAP side.

5. The SAP service calling method based on the financial middle station according to claim 4 is characterized in that: Register the SAP system on the financial platform for services, including: The unified service portal of the SAP system is built through the cloud service bus to complete the registration of the secondary packaged functional modules on the financial middle platform.

6. The SAP service calling method based on the financial middle station according to claim 5 is characterized in that: The unified service portal of the SAP system is built through the cloud service bus to complete the registration of the secondary packaged functional modules on the financial middle platform, including: Register the SAP system unified service entry address to the cloud service bus; The addresses generated by the cloud service bus are uniformly registered in the primary cloud service bus. The primary cloud service bus address is the universal interface address of the primary SAP system. Configure the interface code of each functional module.

7. The SAP service calling method based on the financial middle station according to claim 6 is characterized in that: The shared financial platform calls the registration service on the financial platform to call various functional modules of the SAP system, including: The shared financial platform calls the general interface address of the SAP system through the financial middle platform, and adds the code parameter to the URL to specify the interface code of the function module to be called to complete the call of the corresponding service.

8. The method for calling a SAP service based on a financial middle station according to any one of claims 1 to 7, characterized in that: The method further comprises the following steps: Select the target data in the SAP system to be synchronized to the financial center; Configure the synchronization mode of the target data.

9. The SAP service calling method based on the financial middle station according to claim 8 is characterized in that: The synchronization modes for configuring target data include real-time synchronization mode for new services and small-batch online synchronization mode for existing data.

Images