A method for embedding bills of lading into SAP and ITSM SaaS systems

Abstract

This invention relates to the field of computer technology, specifically a method for integrating embedded bills of lading into an SAP system and an ITSM SaaS system. This invention helps users improve their bill of lading operation experience when encountering problems while using the SAP system. By embedding a bill of lading button within the SAP system, users can submit work orders directly within SAP without needing to navigate to other systems. It also automatically fills in error information, retrieves user account information, and provides a toggleable passwordless login function, enabling users to resolve issues more efficiently.

Description

Technical Field

[0001] This invention relates to the field of computer technology, specifically a method for integrating embedded bills of lading into an SAP system and an ITSM SaaS system. Background Technology

[0002] SAP, short for "System Applications and Products," is a software name for enterprise management solutions. Users of SAP systems may encounter problems such as unfamiliarity with business processes and complex operations, leading to low work efficiency.

[0003] When users need support, they cannot complete the operation directly in the SAP system. They need to open a third-party ITSM ticketing system to fill out a ticket, describe the problem, and fill in information such as the operation that caused the problem. This results in a poor user experience, and users often cannot fill in accurate and effective problem information. As a result, the IT support department has to communicate with users multiple times to resolve the problem, which is very inefficient.

[0004] As the core management system of an enterprise, SAP systems are generally deployed on the enterprise's internal network. When interfacing with SaaS systems, not only do both systems need to develop interface development, but internal network permissions also need to be opened, which not only increases development costs but also often does not comply with the enterprise's network management standards. Summary of the Invention

[0005] To overcome the shortcomings of the prior art, this invention provides a method for integrating embedded bills of lading into SAP and ITSM SaaS systems.

[0006] To achieve the above objectives, a method for embedded bill of lading integration between an SAP system and an ITSM SaaS system is designed, characterized by the following steps:

[0007] S1, In the SAP system, add quick order button entry points to the toolbar and menu bar through a secondary development approach;

[0008] S2, when the user clicks the button, uses an ABAP-written program to obtain user information and error messages from the SAP system, encrypts them, and concatenates them into a URL;

[0009] S3 calls the corresponding link in the user's PC browser to jump to the bill of lading interface of the ITSM SaaS system and automatically fills in the bill of lading information;

[0010] Specifically, the steps include the following:

[0011] Step 1: Add a configuration table in the SAP system, define the address of the ITSM SaaS system to be redirected to in the configuration table, define the encryption key value, and define the same encryption key value in the ITSM SaaS system for information decryption;

[0012] Step 2: Add a quick order button to the SAP system, and customize the enhanced code logic to obtain the current user information of the SAP system and obtain the SAP system error information through sy-msg;

[0013] Step 3: When a user clicks the bill of lading button in the SAP system, the user information and error information obtained in Step 2 are used to construct a JSON format. The constructed user information is then encrypted using the encryption key maintained in the configuration table in Step 1, and then encrypted using the AES algorithm with 128-bit ECB mode PKCS7-PKCS5 padding. Finally, the data is byte-encoded to obtain a string.

[0014] Step 4: Obtain the redirect address maintained in the configuration table of Step 1 in the SAP system, concatenate it with the string generated in Step 3, encode it to generate a URL link, and call the user's PC browser to open the URL to redirect to the ITSM SaaS system;

[0015] Step 5: In the ITSM SaaS system, the user information and error messages redirected from the SAP system are received via the browser's URL. The system decrypts the information using the agreed-upon encryption key. Depending on the configuration in the ITSM SaaS system, the system verifies whether the user can log in without a password or needs to be redirected to the login page, and handles the situation differently. Automatic passwordless login: The ITSM SaaS system automatically matches the user based on their SAP system login name, email address, and mobile phone number. If the match is successful, the user logs in automatically; otherwise, an error message is displayed. Manual login: When a user uses the embedded order function in the SAP system for the first time, they need to log in using a mobile phone verification code. After successful login, the user's login information is retained in the browser cookie, and subsequent order submissions do not require login.

[0016] Step Six: In the ITSM SaaS system, after verifying the user's login information, the user is redirected to the ITSM SaaS system's order page. The parsed plaintext SAP system error information is then transmitted to the user's PC browser (the front-end page of the ITSM SaaS system) via URL parameters. Upon receiving the parameters, the user's PC browser matches and fills in the code fields on the current order page, automatically retrieving key event data. Finally, the user will see the order page containing all SAP system error information, allowing them to continue operations, submit a work order, or close the page.

[0017] The secondary development method in S1 is to use the secondary development language ABAP for system development.

[0018] The addition of the quick order button in step two is achieved by modifying the system's standard program MENUSYST.

[0019] The custom enhanced code logic in step two is implemented by adding enhanced code logic by modifying the function module HELP_START.

[0020] The key data in step six includes SAP system transaction codes, page URLs, clients, system identifiers, SAP system accounts, mobile phone numbers, and email addresses.

[0021] The beneficial effects of this invention are: it helps users solve problems encountered when using the SAP system and improves the order operation experience. By embedding an order button in the SAP system, users can submit work orders directly in the SAP system without having to switch to other systems. It can also automatically fill in error information, obtain user account information, and provide a passwordless login function that can be turned on or off, so that users can solve problems more efficiently. Attached Figure Description

[0022] Figure 1 This is the overall flowchart of the present invention.

[0023] Figure 2 This is a flowchart of the passwordless login and manual login process of the present invention.

[0024] Figure 3 This is a screenshot of the embedded order form in the SAP system GUI of the present invention.

[0025] Figure 4 This is a diagram illustrating the embedded bill of lading functionality in the SAP system's Fiori terminal, as described in this invention.

[0026] Figure 5 This is a screenshot showing the effect of the SAP system embedding automatic error information input on bills of lading according to the present invention. Detailed Implementation

[0027] The present invention will be further described in detail below with reference to the embodiments.

[0028] This invention includes the following steps:

[0029] S1. In the SAP system, a quick bill of lading button is added to the toolbar and menu bar using a secondary development approach; S2. When the user clicks the button, a program written in ABAP retrieves the user information and error information from the SAP system, encrypts them, and concatenates them into a URL; S3. The user's PC browser accesses the corresponding link, redirecting them to the bill of lading interface of the ITSM SaaS system, and automatically populates the bill of lading information; See the overall flowchart of this invention. Figure 1 ,

[0030] Specifically, the steps include the following:

[0031] Step 1: Add a configuration table in the SAP system, defining the address of the ITSM SaaS system to be redirected to and defining the encryption key value. Define the same encryption key value in the ITSM SaaS system for information decryption. The example assumes the following data:

[0032] The redirect address is:

[0033] https: / / xxxx.com / SAPSystemClient / redirect?func=d3615a128ediwomn21d0

[0034] Encryption key value: zkzhnmcysadbkbbm

[0035] Step 2: Add a quick order submission button to the SAP system, and customize the enhanced code logic to obtain the current user information of the SAP system. Retrieve SAP system error information via sy-msg. The detailed process is as follows:

[0036] In the SAP system, enter transaction code [SE41], enter the corresponding system standard procedure: MENUSYST, select the status as: MEN, click the Modify button, expand the menu bar, select Help, double-click to expand, add the corresponding shortcut order key, select Toolbar -> Function Codes, activate the corresponding settings, see [link to relevant documentation]. Figure 3 and Figure 4 This provides a quick access point for SAP system operations on both the GUI and Fiori platforms. By embedding the quick order submission button in the help menu and toolbar, users can directly click the quick order submission button to submit orders within the SAP system, making it convenient for users.

[0037] Adding Enhancement Code: In the SAP system, locate the function group [SHL2], function module HELP_START, and find the corresponding enhancement location through the Repository Browser. Add the enhancement code logic. See the code example below:

[0038] Retrieve current system user information in the SAP system:

[0039] READ TABLE lt_addtel INTO ls_addtel INDEX 1.

[0040] IF sy-subrc = 0.

[0041] DATA(lv_telephone) = ls_addtel-telephone."phone number

[0042] ENDIF.

[0043] READ TABLE lt_addsmtp INTO ls_addsmtp INDEX 1.

[0044] IF sy-subrc = 0.

[0045] DATA(lv_e_mail) = ls_addsmtp-e_mail."email address"

[0046] ENDIF.

[0047] DATA(lv_loginname)=|"loginName":"|&&sy-uname&&|"|.

[0048] DATA(lv_email) =|"email":"|&&lv_e_mail&&|"|.

[0049] DATA(lv_phone) =|"phone":"|&&lv_telephone&&|"|.

[0050] Obtain SAP system error information via sy-msg

[0051] DATA(1v_msgid) = sy - msgid.

[0052] DATA(1v_msgty) = sy - msgty.

[0053] DATA(1v_msgno) = sy - msgno.

[0054] DATA(1v_msgU1)=sy-msgul

[0055] DATA(1v_msgu2) = sy - msgu2.

[0056] DATA(1v_msgu3) = sy - msgU3.

[0057] DATA(1v_msgU4) = sy - msgu4.

[0058] DATA(1v_title) = sy-title.

[0059] Step 3: When a user clicks the Bill of Lading button in the SAP system, the user information and error message obtained in Step 2 are used to construct a JSON format. Using the encryption key maintained in the configuration table in Step 1, the constructed user information is encrypted using the AES algorithm with 128-bit ECB mode PKCS7-PKCS5 padding, and then byte-encoded to obtain the string. An example is shown below:

[0060] Assume the user information in the SAP system is as follows:

[0061] Username: feedback, Email: feedback@SAPsystems.com, Mobile Number: 13911112222

[0062] The error message was: No valid personnel information found.

[0063] Using the above information, construct the following JSON format string:

[0064] {"loginName":"feedback","email":"feedback@SAPsystem.com","phone":"13911112222","description":"Message content: Material 1132132132"} Message number: M3305","SAP system_code":"DM21"}

[0065] Using the encryption key value defined in step one, the above string information is encrypted using the AES algorithm with 128-bit ECB mode PKCS7-PKCS5 padding, and then byte-encoded to obtain the following string:

[0066] WJIAlGBkoi+0wDdWyrazEGyUJ4tOWq9Vunufor / 3G7wnMsp09IA8wB4MEjy2mG4ZqdPRzPxdkRZb1MxlyaGp2Ot0Y2vkAuigX zMJ0xZ9 / NnrrI5RIkcRJQRnvtqI3uVD8n / pLki4DWwYfanL6 / +Ff+Mrn7VzAiOdQscqgcZly5oq4GWuN1Gev6KH7Jfw8FWXam pY6D7wJprrMjHGJYMlwCDR7BOjIi5njbIlvdszA64=

[0067] emt6aG5tY3lzYWRia2JibQ==

[0068] Step 4: Retrieve the redirect address maintained in the configuration table of Step 1 in the SAP system, concatenate it with the string generated in Step 3, encode it to generate a URL link, and call the user's PC browser to open the URL to redirect to the ITSM SaaS system. An example is shown below:

[0069] The string generated in step three is appended as a parameter to the URL defined in step one. The parameter name is echo. After appending, the URL is encoded using URLEncode to generate the URL link.

[0070] https: / / xxxx.com / SAP system Client / redirect? func=d3615a128ediwomn21d0&echo=WJIAlGBkoi+0wDdWyrazEGyUJ 4tOWq9Vunufor / 3G7wnMsp09IA8wB4MEjy2mG4ZqdPRzPxdkRZb1MxlyaGp2Ot0Y2vkAuigXzMJ0xZ9 / NnrrI5RIkcRJQRnvtqI3uVD8n / pLki4DWwYfanL6 / +Ff+Mrn7VzAi OdQscqgcZly5oq4GWuN1Gev6KH7Jfw8FWXampY6D7wJprrMjHGJYMlwCDR7BOjIi5njbIlvdszA64=

[0071] emt6aG5tY3lzYWRia2JibQ==

[0072] Step 5: In the ITSM SaaS system, the user information and error message redirected from the SAP system are received via the browser's URL. This information is decrypted using the agreed-upon encryption key. Depending on the configuration in the ITSM SaaS system, the system verifies whether the user can log in without a password or needs to be redirected to the login page, handling each case differently: Automatic passwordless login: The ITSM SaaS system automatically matches the user based on their SAP system login name, email address, and mobile phone number. If a match is successful, the user logs in automatically; otherwise, an error message is displayed. Manual login: When a user uses the embedded order function in the SAP system for the first time, they need to log in using a mobile phone verification code. After successful login, the user's login information is retained in the browser cookie. Subsequent order submissions do not require login. Example:

[0073] The system's corresponding function can be queried using the parameter 'func' in the URL, and a decision on whether passwordless login is required can be made based on the user's configuration.

[0074] If login-free access is required, the JSON string in step three is obtained by AES decryption using the `echo` parameter in the URL:

[0075] {"loginName":"feedback","email":"feedback@SAPsystem.com","phone":"13911112222","description":"Message content: Material 1132132132"} Message number: M3305","SAP system_code":"DM21"}

[0076] Extract the loginName, email, and phone values. In the ITSM SaaS system, query for users with the same login name based on loginName. If no users are found, query for users with the same email and phone number. Once a user is found, log in directly to the corresponding user. See [link to documentation]. Figure 2 .

[0077] Step Six: In the ITSM SaaS system, after verifying the user's login information, the user is redirected to the ITSM SaaS system's order submission interface. The parsed plaintext SAP system error information is then transmitted to the user's PC browser (the front-end page of the ITSM SaaS system) via URL parameters. Upon receiving the parameters, the user's PC browser matches and fills in the code fields on the current order submission interface, automatically retrieving key event data, reducing the user's workload. Finally, the user will see an order submission interface containing all SAP system error information, allowing them to continue operations, submit a work order, or close the page. An example is shown below:

[0078] In step five, after verifying user login, an HTTP 302 status request is returned, redirecting the ITSM SaaS system's PC front-end page to the corresponding bill of lading page, carrying SAP system error information. This SAP system error information is the JSON data parsed in step four; after removing user information, the remaining information is appended to the URL as parameters. For example, the URL appended from the JSON in step four would be:

[0079] https: / / xxxx.com / incident?func=d3615a128ediwomn21d0&description=Message content: Material 1132132132 Message number: M3305 & SAP system_code=DM21

[0080] The URL after URL encoding is:

[0081] https: / / xxxx.com / incident?func%3Dd3615a128ediwomn21d0%26description%3D%E6%B6%88%E6%81%AF%E5%86%85%E5%AE%B9%EF%BC%9A%E7%89%A9%E6%96%991132132132%3Cbr%3E%E6%B6%88%E6%81%AF%E5%8F%B7%EF%BC%9AM3305%26SAPsystem_code%3DDM21

[0082] The front-end retrieves parameters from the URL, such as "description" and "SAP system_code" in this example, and populates the fields in the bill of lading interface based on the "code". See [link / reference]. Figure 5 .

[0083] The secondary development method in S1 is to use the secondary development language ABAP for system development.

[0084] The addition of the quick order button in step two is achieved by modifying the system's standard program MENUSYST.

[0085] The custom enhanced code logic in step two is implemented by adding enhanced code logic by modifying the function module HELP_START.

[0086] The key data in step six includes SAP system transaction codes, page URLs, clients, system identifiers, SAP system accounts, mobile phone numbers, and email addresses.

[0087] Using this invention, users can directly click the quick order button in the SAP system to submit orders, which is convenient for users and eliminates the need to switch to other systems. It can also automatically fill in error information and obtain user account information. After clicking the embedded order, it will automatically obtain key data of the event form, such as the SAP system transaction code (GUI), page URL (Fiori), client, system identifier, SAP system account, mobile phone number, email, etc., and automatically fill them into the order page, reducing the workload of users submitting orders. It also provides a passwordless login function that can be turned on or off, so that users can solve problems more efficiently.

Claims

1. A method for integrating embedded bills of lading into an SAP system and an ITSM SaaS system, characterized in that: Includes the following steps: S1, In the SAP system, add quick order button entry points to the toolbar and menu bar through a secondary development approach; S2, when the user clicks the button, uses an ABAP-written program to obtain user information and error messages from the SAP system, encrypts them, and concatenates them into a URL; S3 calls the corresponding link in the user's PC browser to jump to the bill of lading interface of the ITSM SaaS system and automatically fills in the bill of lading information; Specifically, the steps include the following: Step 1: Add a configuration table in the SAP system, define the address of the ITSM SaaS system to be redirected to in the configuration table, define the encryption key value, and define the same encryption key value in the ITSM SaaS system for information decryption; Step 2: Add a quick order button to the SAP system, and customize the enhanced code logic to obtain the current user information of the SAP system and obtain the SAP system error information through sy-msg; Step 3: When a user clicks the bill of lading button in the SAP system, the user information and error information obtained in Step 2 are used to construct a JSON format. The constructed user information is then encrypted using the encryption key maintained in the configuration table in Step 1, and then the AES algorithm with 128-bit ECB mode PKCS7-PKCS5 padding is used to obtain the string. Step 4: Obtain the redirect address maintained in the configuration table of Step 1 in the SAP system, concatenate it with the string generated in Step 3, encode it to generate a URL link, and call the user's PC browser to open the URL to redirect to the ITSM SaaS system; Step 5: In the ITSM SaaS system, the user information and error messages redirected from the SAP system are received via the browser's URL. The system decrypts the information using the agreed-upon encryption key. Depending on the configuration in the ITSM SaaS system, the system verifies whether the user can log in without a password or needs to be redirected to the login page, and handles the situation differently. Automatic passwordless login: The ITSM SaaS system automatically matches the user based on their SAP system login name, email address, and mobile phone number. If the match is successful, the user logs in automatically; otherwise, an error message is displayed. Manual login: When a user uses the embedded order function in the SAP system for the first time, they need to log in using a mobile phone verification code. After successful login, the user's login information is retained in the browser cookie, and subsequent order submissions do not require login. Step Six: In the ITSM SaaS system, after verifying the user's login information, the user is redirected to the ITSM SaaS system's order page. The parsed plaintext SAP system error information is then transmitted to the user's PC browser (the front-end page of the ITSM SaaS system) via URL parameters. Upon receiving the parameters, the user's PC browser matches and fills in the code fields on the current order page, automatically retrieving key event data. Finally, the user will see the order page containing all SAP system error information, allowing them to continue operations, submit a work order, or close the page.

2. The method for integrating an SAP system with an ITSM SaaS system into an embedded bill of lading, as described in claim 1, is characterized in that: The secondary development method in S1 is to use the secondary development language ABAP for system development.

3. The method for integrating an SAP system with an ITSM SaaS system into an embedded bill of lading, as described in claim 1, is characterized in that: The addition of the quick order button in step two is achieved by modifying the system's standard program MENUSYST.

4. The method for integrating an SAP system with an ITSM SaaS system into an embedded bill of lading, as described in claim 1, is characterized in that: The custom enhanced code logic in step two is implemented by adding enhanced code logic by modifying the function module HELP_START.

5. The method for integrating an SAP system with an ITSM SaaS system into an embedded bill of lading, as described in claim 1, is characterized in that: The key data in step six includes SAP system transaction codes, page URLs, clients, system identifiers, SAP system accounts, mobile phone numbers, and email addresses.

Images