Skip to content

Commit ffe4577

Browse files
authored
Merge pull request #190705 from paulth1/four-azure-purview-articles
edit pass: Four azure purview articles
2 parents deef863 + 3737ddd commit ffe4577

File tree

4 files changed

+240
-224
lines changed

4 files changed

+240
-224
lines changed
Lines changed: 54 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: SAP ABAP function module deployment guide - Azure Purview
3-
description: This article outlines the steps to deploy ABAP function module in SAP Server
3+
description: This article outlines the steps to deploy the ABAP function module in your SAP server.
44
author: linda33wj
55
ms.author: jingwang
66
ms.service: purview
@@ -11,116 +11,116 @@ ms.date: 03/05/2022
1111

1212
# SAP ABAP function module deployment guide
1313

14-
When you scan [SAP ECC](register-scan-sapecc-source.md), [SAP S/4HANA](register-scan-saps4hana-source.md) and [SAP BW](register-scan-sap-bw.md) sources in Azure Purview, you need to create the dependent ABAP function module in your SAP server. Azure Purview invokes this function module to extract the metadata from your SAP system during scan.
14+
When you scan [SAP ECC](register-scan-sapecc-source.md), [SAP S/4HANA](register-scan-saps4hana-source.md), and [SAP BW](register-scan-sap-bw.md) sources in Azure Purview, you need to create the dependent ABAP function module in your SAP server. Azure Purview invokes this function module to extract the metadata from your SAP system during scan.
1515

16-
This document details the steps required to deploy this module.
16+
This article describes the steps required to deploy this module.
1717

1818
> [!Note]
19-
> The following instructions were compiled based on the SAP GUI v.7.2
19+
> The following instructions were compiled based on the SAP GUI v. 7.2.
2020
2121
## Prerequisites
2222

23-
Download the SAP ABAP function module source code from Azure Purview Studio. After you register a source for [SAP ECC](register-scan-sapecc-source.md),[SAP S/4HANA](register-scan-saps4hana-source.md) or [SAP BW](register-scan-sap-bw.md), you can find a download link on top as follows. You can also see the link when new or edit a scan.
23+
Download the SAP ABAP function module source code from Azure Purview Studio. After you register a source for [SAP ECC](register-scan-sapecc-source.md), [SAP S/4HANA](register-scan-saps4hana-source.md), or [SAP BW](register-scan-sap-bw.md), you can find a download link on top as shown in the following image. You can also see the link when you create a new scan or edit a scan.
2424

25-
:::image type="content" source="media/abap-functions-deployment-guide/download-abap-code.png" alt-text="Download ABAP function module source code from Azure Purview Studio" border="true":::
25+
:::image type="content" source="media/abap-functions-deployment-guide/download-abap-code.png" alt-text="Screenshot that shows the download link for the ABAP function module source code from Azure Purview Studio." border="true":::
2626

27-
## Deployment of the Module
27+
## Deploy the module
2828

29-
### Create a Package
29+
Follow the instructions to deploy a module.
30+
31+
### Create a package
3032

3133
This step is optional, and an existing package can be used.
3234

33-
1. Log in to the SAP server and open **Object Navigator** (SE80 transaction).
35+
1. Sign in to the SAP server and open **Object Navigator** (SE80 transaction).
3436

35-
2. Select option **Package** from the list and enter a name for the new package (for example, Z\_MITI) then press button **Display**.
37+
1. Select **Package** from the list and enter a name for the new package. For example, use **Z\_MITI**. Then select **Display**.
3638

37-
3. Select **Yes** in the **Create Package** window. Consequently, a window **Package Builder: Create Package** opens. Enter value into **Short Description** field and select the **Continue** icon.
39+
1. In the **Create Package** window, select **Yes**. In the **Package Builder: Create Package** window, enter a value in the **Short Description** box. Select the **Continue** icon.
3840

39-
4. Select **Own Requests** in the **Prompt for local Workbench request** window. Select **development** request.
41+
1. In the **Prompt for local Workbench request** window, select **Own Requests**. Select the **development** request.
4042

41-
### Create a Function Group
43+
### Create a function group
4244

43-
In Object Navigator select **Function Group** from the list and type its name in the input field below (for example, Z\_MITI\_FGROUP). Select the **View** icon.
45+
1. In **Object Navigator**, select **Function Group** from the list and enter a name in the input box. For example, use **Z\_MITI\_FGROUP**. Select the **View** icon.
4446

45-
1. In **Create Object** window, select **yes** to create a new function group.
47+
1. In the **Create Object** window, select **yes** to create a new function group.
4648

47-
2. Specify an appropriate description in the **Short text** field and press button **Save**.
49+
1. Enter a description in the **Short Text** box and select **Save**.
4850

49-
3. Choose a package which was prepared in the previous step **Create a Package** and select **Save**.
51+
1. Select a package that was prepared in the **Create a Package** step, and select **Save**.
5052

51-
4. Confirm a request by pressing icon **Continue**.
53+
1. Confirm a request by selecting **Continue**.
5254

53-
5. Activate the Function Group.
55+
1. Activate the function group.
5456

55-
### Create the ABAP Function Module
57+
### Create the ABAP function module
5658

57-
1. Once the function group is created, select it.
59+
1. After the function group is created, select it.
5860

59-
2. Select and hold (or right-click) on the function group name in repository browser, and select **Create**, then **Function Module**.
61+
1. Select and hold (or right-click) the function group name in the repository browser. Select **Create** and then select **Function Module**.
6062

61-
3. In the **Function Module** field, enter `Z_MITI_DOWNLOAD`. Populate **Short text** input with proper description.
63+
1. In the **Function module** box, enter **Z_MITI_DOWNLOAD**. Enter a description in the **Short Text** box.
6264

63-
When the module has been created, specify the following information:
65+
After the module is created, specify the following information:
6466

65-
1. Navigate to the **Attributes** tab.
67+
1. Go to the **Attributes** tab.
6668

67-
2. Select **Processing Type** as **Remote-Enabled Function Module**.
69+
1. Under **Processing Type**, select **Remote-Enabled Module**.
6870

69-
:::image type="content" source="media/abap-functions-deployment-guide/processing-type.png" alt-text="Register sources option - Remote-Enabled Function Module" border="true":::
71+
:::image type="content" source="media/abap-functions-deployment-guide/processing-type.png" alt-text="Screenshot that shows registering the sources option as Remote-Enabled Module." border="true":::
7072

71-
3. Navigate to the **Source code** tab. There are two ways how to deploy code for the function:
73+
1. Go to the **Source code** tab. There are two ways to deploy code for the function:
7274

73-
a. From the main menu, upload the text file you downloaded from Azure Purview Studio as described in [Prerequisites](#prerequisites). To do so, select **Utilities**, **More Utilities**, then **Upload/Download**, then **Upload**.
75+
1. On the main menu, upload the text file you downloaded from Azure Purview Studio as described in [Prerequisites](#prerequisites). To do so, select **Utilities** > **More Utilities** > **Upload/Download** > **Upload**.
7476

75-
b. Alternatively, open the file, copy its content and paste into **Source code** area.
77+
1. Alternatively, open the file and copy and paste the contents in the **Source code** area.
7678

77-
4. Navigate to the **Import** tab and create the following parameters:
79+
1. Go to the **Import** tab and create the following parameters:
7880

79-
a. P\_AREA TYPE DD02L-TABNAME (Optional = True)
81+
1. *P\_AREA TYPE DD02L-TABNAME* (**Optional** = True)
8082

81-
b. *P\_LOCAL\_PATH TYPE STRING* (Optional = True)
83+
1. *P\_LOCAL\_PATH TYPE STRING* (**Optional** = True)
8284

83-
c. *P\_LANGUAGE TYPE L001TAB-DATA DEFAULT \'E\'*
85+
1. *P\_LANGUAGE TYPE L001TAB-DATA DEFAULT \'E\'*
8486

85-
d. *ROWSKIPS TYPE SO\_INT DEFAULT 0*
87+
1. *ROWSKIPS TYPE SO\_INT DEFAULT 0*
8688

87-
e. *ROWCOUNT TYPE SO\_INT DEFAULT 0*
89+
1. *ROWCOUNT TYPE SO\_INT DEFAULT 0*
8890

8991
> [!Note]
90-
> Choose **Pass Value** for all of them
91-
92-
:::image type="content" source="media/abap-functions-deployment-guide/import.png" alt-text="Register sources option - Import parameters" border="true":::
92+
> Select the **Pass Value** checkbox for all the parameters.
9393
94-
5. Navigate to the "Tables" tab and define the following:
94+
:::image type="content" source="media/abap-functions-deployment-guide/import.png" alt-text="Screenshot that shows registering the sources option as Import parameters." border="true":::
9595

96-
`EXPORT_TABLE LIKE TAB512`
96+
1. Go to the **Tables** tab and define *EXPORT_TABLE LIKE TAB512*.
9797

98-
:::image type="content" source="media/abap-functions-deployment-guide/export-table.png" alt-text="Register sources options - Tables tab" border="true":::
98+
:::image type="content" source="media/abap-functions-deployment-guide/export-table.png" alt-text="Screenshot that shows the Tables tab." border="true":::
9999

100-
6. Navigate to the **Exceptions** tab and define the following exception: `E_EXP_GUI_DOWNLOADFAILED`
100+
1. Go to the **Exceptions** tab and define the exception *E_EXP_GUI_DOWNLOADFAILED*.
101101

102-
:::image type="content" source="media/abap-functions-deployment-guide/exceptions.png" alt-text="Register sources options - Exceptions tab" border="true":::
102+
:::image type="content" source="media/abap-functions-deployment-guide/exceptions.png" alt-text="Screenshot that shows the Exceptions tab." border="true":::
103103

104-
7. Save the function (press ctrl+S or choose **Function Module**, then **Save** in the main menu).
104+
1. Save the function by selecting **Ctrl+S**. Or select **Function module** and then select **Save** on the main menu.
105105

106-
8. Select the **Activate** icon on the toolbar (ctrl+F3) and select **Continue** button in dialog window. If prompted, you should select the generated includes to be activated along with the main function module.
106+
1. Select the **Activate** icon on the toolbar and then select **Continue**. You can also select **Ctrl+F3**. If prompted, select the generated includes to be activated along with the main function module.
107107

108-
### Testing the Function
108+
### Test the function
109109

110-
When all the previous steps are completed, follow the below steps to test the function:
110+
After you finish the previous steps, test the function:
111111

112-
1. Open Z\_MITI\_DOWNLOAD function module.
112+
1. Open the **Z\_MITI\_DOWNLOAD** function module.
113113

114-
2. Choose **Function Module**, then **Test**, then **Test Function Module** from the main menu (or press F8).
114+
1. On the main menu, select **Function Module** > **Test** > **Test Function Module**. You can also select **F8**.
115115

116-
3. Enter a path to the folder on the local file system into parameter P\_LOCAL\_PATH and press **Execute** icon on the toolbar (or press F8).
116+
1. Enter a path to the folder on the local file system in the parameter *P\_LOCAL\_PATH*. Then select the **Execute** icon on the toolbar. You can also select **F8**.
117117

118-
4. Put the name of the area of interest into P\_AREA field if a file with metadata must be downloaded or updated. When the function finishes working, the folder which has been indicated in P\_LOCAL\_PATH parameter must contain several files with metadata inside. The names of files mimic areas which can be specified in P\_AREA field.
118+
1. Enter the name of the area of interest in the **P\_AREA** field if a file with metadata must be downloaded or updated. After the function finishes working, the folder indicated in the *P\_LOCAL\_PATH* parameter must contain several files with metadata inside. The names of files mimic areas that can be specified in the **P\_AREA** field.
119119

120-
The function will finish its execution and metadata will be downloaded much faster in case of launching it on the machine which has high-speed network connection with SAP server.
120+
The function finishes its execution and metadata is downloaded much faster if it's launched on the machine that has a high-speed network connection with the SAP server.
121121

122122
## Next steps
123123

124124
- [Register and scan SAP ECC source](register-scan-sapecc-source.md)
125125
- [Register and scan SAP S/4HANA source](register-scan-saps4hana-source.md)
126-
- [Register and scan SAP Business Wareouse (BW) source](register-scan-sap-bw.md)
126+
- [Register and scan SAP Business Warehouse (BW) source](register-scan-sap-bw.md)

0 commit comments

Comments
 (0)