You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tutorials/mob-app-mao-erp-app-create/mob-app-mao-erp-app-create.md
+47-52Lines changed: 47 additions & 52 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ In this mission you will learn how to create and update an SAP Mobile Services a
46
46
47
47
1. Execute the transaction **`/MERP/CPMS_APPCREATE`** from the SAP GUI, then select your required variant (i.e., `SAP&SAM_<version>`).
48
48
49
-
2. Fill in the **Admin API**, **SCC Location Id** and **Virtual Host**. Please ensure the **Background Job User** will maintain authorization to run the Usage Metering background job (parameter info below). To use an RFC Destination to create the app instead of the **Admin API** please see Step 4 (optional). The app is created as the Metrics Host by default, to set up the app as the Metrics Sattelite please see Step 7. Then execute the transaction.
49
+
2. Fill in the **Admin API**, **SCC Location Id** and **Virtual Host**. Please ensure the **Background Job User** will maintain authorization to run the Usage Metering background job (parameter info below). To use an RFC Destination to create the app instead of the **Admin API** please see Step 4 (optional). The app is created as the Metrics Host by default, to set up the app as the Metrics Satellite please see Step 6. Then execute the transaction.
50
50
51
51

52
52
@@ -67,7 +67,7 @@ In this mission you will learn how to create and update an SAP Mobile Services a
67
67
|**Client**| Used to set `sap-client` header for Mobile Services Mobile Destinations. Defaulted to current System Client. |
68
68
|**Background Job User**| Used to schedule the Usage Metering background job with a daily frequency. If no user is provided, then the user executing the transaction is used. Please ensure the **Background Job User** will maintain authorization to run the background job. |
69
69
|**Client Role**| Used by the Metrics report to determine user counts (i.e., 0 user counts sent for non-productive systems). Defaulted to System Client Role defined in transaction SCC4. Stored in MAIF Product Table. |
70
-
|**Satellite System**| See step X to use Satellite Systems. |
70
+
|**Satellite System**| See Step 6 to use Satellite Systems. |
71
71
72
72
>**WARNING:** Any change that may affect the offline configuration (e.g., a new entity type is added to your mobile app configuration, or the **Defer Batch Response** setting is changed for the **OData Service Technical Name** provided when generating the offline configuration) will require you to update the offline configuration in Mobile Services and reset your mobile app. See Step 2.5 to update.
73
73
@@ -126,60 +126,59 @@ In this mission you will learn how to create and update an SAP Mobile Services a
126
126
| :-----------| :----------- |
127
127
|`sap-client`| Your client (i.e., **`800`**) |
128
128
129
-
5. From your app's **Mobile Connectivity** feature, select the **Service Keys** tab. You should see a Service Key with the properties below. The Key should be automatically maintained as the `X-API-Key` property in the Additional Properties of the Usage Metering Middleware Server which we will review in Step 3.7.
129
+
5. From your app's **Mobile Connectivity** feature, select the **Service Keys** tab. You should see a Service Key with the properties below. The Key should be automatically maintained as the `X-API-Key` property in the Additional Properties of the Usage Metering Middleware Server which we will review in Step 3.9.
| Alias |**`<system><client>`** (i.e., **`PRD001`**) |
134
-
| Roles |**`sap_application_metering`**|
135
-
| Type |**`API Key`**|
131
+
| Field Name | Value |
132
+
| :--------- | :---- |
133
+
| Alias |**`<system><client>`** (i.e., **`PRD001`**) |
134
+
| Roles |**`sap_application_metering`**|
135
+
| Type |**`API Key`**|
136
136
137
-
6. From your app's overview screen, if you select the **Offline Access** feature you should be able to display and edit the offline configuration. If the offline configuration is missing, then please see Step 7.
137
+
6. From your app's overview screen, if you select the **Offline Access** feature you should be able to display and edit the offline configuration. If the offline configuration is missing, then please see Step 8.
138
138
139
139
7. From your app's overview screen, select the **APIs** tab to view the onboarding QR code which you can scan from the SAP Service and Asset Manager mobile app.
140
140
141
141
8. We will now check the Usage Metering Middleware Server. Execute transaction **/SYCLO/ADMIN** from the SAP GUI to open up the MAIF Admin Panel. Navigate to **Administration** > **Server Management**. Select the Middleware Server with the name noted in Step 2.4. If the Usage Metering Middleware Server is missing then please see Step 8.
142
142
143
143

144
144
145
-
9. Verify that the Middleware Server has the following **Basic Info** and **Additional Properties**. If the Middleware Server's **Basic Info** or **Additional Properties** are not as expected then please see Step 8.
145
+
9. Verify that the Middleware Server has the following **Basic Info** and **Additional Properties**. If the Middleware Server's **Basic Info** or **Additional Properties** are not as expected then please see Step 9.
10. To verify that the Usage Metering Background Job is scheduled, please execute transaction **SM37** from the SAP GUI and search for the job name noted in Step 2.4. If the background job is missing, then please see Step 9.
171
-
170
+
10. To verify that the Usage Metering Background Job is scheduled, please execute transaction **SM37** from the SAP GUI and search for the job name noted in Step 2.4. If the background job is missing, then please see Step 10.
172
171

173
172
174
173
11. Execute transaction **/SYCLO/CONFIGPANEL** from the SAP GUI to open up the MAIF Configuraiton Panel. Navigate to **Mobile Application Configuration** > **System Components**. You should see a system component with the properties below.
175
174
176
175

177
176
178
-
| Field Name | Value|
179
-
| :---------------| :---------------------- |
177
+
| Field Name | Value |
178
+
| :--------- | :---- |
180
179
| System Component |**`MS_UNIFIED_SERVER`**|
181
-
| System Role |**`Host`**|
182
-
| Active Flag | Selected|
180
+
| System Role |**`Host`**|
181
+
| Active Flag | Selected |
183
182
184
183
12. To ensure the Metrics Requests are sent successfully execute transaction **SE38** and execute program **`/MFND/CORE_CLOUD_METRICS_PROG`**. Provide `SAP_SERVICE_ASSET_MANAGER` in `Product Technical Name` and execute.
185
184
@@ -214,11 +213,11 @@ In this mission you will learn how to create and update an SAP Mobile Services a
10. You may now use the generated **Server GUID** instead of the **Admin API** in Step 2.2 . You may use F4 Help on the **Admin API or Middleware Server GUID** field of the MS App Create transaction to search for the created Middleware Server.
255
254
@@ -285,27 +284,27 @@ In this mission you will learn how to create and update an SAP Mobile Services a
285
284
286
285
7. Navigate to the **Administration** > **Server Management** section.
287
286
288
-
8. Select the Middleware Server with the name noted in Step 2.4. If the Usage Metering Middleware Server is missing then please see Step 8.
287
+
8. Select the Middleware Server with the name noted in Step 2.4. If the Usage Metering Middleware Server is missing then please see Step 9.
289
288
290
289
9. Update the **RFC Destination** and click **Save**.
291
290
292
291

293
292
294
293
### Optional Feature 3 - Set up Satellite Systems
295
294
296
-
1. Please ensure app has been created and reviewed (steps 2 and 3) in the host system.
295
+
1. Please ensure app has been created and reviewed (Steps 2 and 3) in the Host System.
297
296
298
-
2.Please follow steps 1 and 2.1 then return to this step. Check `Sattelite System`. The `Host RFC Destination` may be provided to create middleware server in the host system used to get the metrics from the sattelite system. If you do not provide the `Host RFC Destination` please ensure you manually create the middleware server in the host system.
297
+
2.Follow Steps 1 and 2 and Check `Satellite System` before executing. The `Host RFC Destination` may be provided to create middleware server in the Host System used to get the metrics from the Satellite System. If you do not provide the `Host RFC Destination` please ensure you manually create the middleware server in the Host System.
299
298
300
299

301
300
302
-
3. Please take note of the **Middleware Server** created on the host system with RFC.
301
+
3. Please take note of the **Middleware Server** created on the Host System with RFC.
303
302
304
303

305
304
306
-
4.Execute transaction **/SYCLO/ADMIN** from the SAP GUI to open up the MAIF Admin Panel. Navigate to the **Administration** > **Server Management** section.
305
+
4.In the Host System execute transaction **/SYCLO/ADMIN** from the SAP GUI to open up the MAIF Admin Panel. Navigate to the **Administration** > **Server Management** section.
307
306
308
-
5. Select Middleware Server noted above. Manually create Satellite Middleware Server if not created automatically via RFC in the previous step. Edit the middleware server and provide an RFC Destination to the Satellite System.
307
+
5. Select Middleware Server noted above. Create Satellite Middleware Server if not created automatically via RFC in the previous step. Edit the middleware server and provide an RFC Destination to the Satellite System. Ensure the RFC authentication is automatic.
309
308
310
309
**Basic Info**
311
310
@@ -331,15 +330,11 @@ In this mission you will learn how to create and update an SAP Mobile Services a
12. To ensure the Satellite Metrics are gathered successfully execute transaction **SE38** and execute program **`/MFND/CORE_CLOUD_METRICS_PROG`** in the host system. Provide `SAP_SERVICE_ASSET_MANAGER` in `Product Technical Name` and execute.
333
+
12. To ensure the Satellite Metrics are gathered successfully execute transaction **SE38** and execute program **`/MFND/CORE_CLOUD_METRICS_PROG`** in the Host System. Provide `SAP_SERVICE_ASSET_MANAGER` in `Product Technical Name` and execute.
335
334
336
335
**Successful Output**
337
336

338
337
339
-
13. If Satellite RFC Destination authorization is not automatic, please sign into satellite system when prompted.
340
-
341
-
13. Upon successful execution, we can check the MAIF Product Table in the satellite system. Execute transaction **SE16** and display table `/SMFND/D_SAPPROD`. Check field `HAS_METER_SERV` is set and field `METER_SERV_TS` is updated.
0 commit comments