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/abap-s4hanacloud-purchasereq-create-wrapper/abap-s4hanacloud-purchasereq-create-wrapper.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,7 @@ parser: v2
18
18
-- SAP Note 3457580 - SAP ACO - Duplicate Types for Table Parameters
19
19
-- SAP Note 3518177 - SAP ACO Proxy Improvements
20
20
-- SAP Note 3519098 - F4: fix function module value help (only relevant for SAP S/4 HANA 2023)
21
+
-- SAP Note 3565942 - ATC Checks "Usage of APIs" and "Allowed Enhancement Technologies"
21
22
22
23
## You will learn
23
24
- How to generate a wrapper interface, a wrapper class and a factory class for the `BAPI_PR_CREATE` using transaction `ACO_PROXY`.
@@ -258,28 +259,28 @@ Repeat the same steps to release the factory class you created:
258
259
259
260
>You will not release the wrapper class.
260
261
261
-
### Run ATC checks and request exemptions
262
-
> Note: The following step describes how to request ATC exemptions for your created wrapper objects. This step should only be carried out if a nonclassic API is used. An exemption does not need to be requested for a classic API. Please refer to the following [note 3565942](https://me.sap.com/notes/3565942).
262
+
### Optional Step - Run ATC checks and request exemptions
263
+
> Note: The next step is **not** required for this tutorial. It outlines the procedure for requesting ATC exemptions for your created wrapper objects, which is only applicable when using a non-classic API—**not applicable in this tutorial**. There is no need to request an exemption for a classic API. For more information, please refer to [note 3565942](https://me.sap.com/notes/3565942). This step is provided solely to illustrate the process that would be necessary if a non-classic API were used.
263
264
264
-
You will now need to run ATC checks on the objects you created and request exemptions to use the unreleased API.
265
+
> You will need to run ATC checks on the objects you created and request exemptions to use the non classic API.
265
266
266
-
To run the ATC checks right click on the `$Z_PURCHASE_REQ_TIER2_###` package and select **Run As** > **ABAP Test Cockpit With...** and select your ATC check variant. Confirm by clicking on **OK**. The result of the ATC check will appear in the ATC Problems tab. As expected, you will get ATC check errors because you are using an unreleased API:
267
+
> To run the ATC checks right click on the `$Z_PURCHASE_REQ_TIER2_###` package and select **Run As** > **ABAP Test Cockpit With...** and select your ATC check variant. Confirm by clicking on **OK**. The result of the ATC check will appear in the ATC Problems tab. As expected, you will get ATC check errors because you are using an unreleased API:
>
269
270
270
-
>Note that there are ATC checks errors for both the interface and the wrapper class. You will need to request an exemption for each of the two objects.
271
+
>Note that there are ATC checks errors for both the interface and the wrapper class. You will need to request an exemption for each of the two objects.
271
272
272
-
Right click on any one of the interface related errors in the ATC Problems tab and choose **Request Exemption**. You can then request an exemption for the whole interface by selecting `Interface (ABAP Objects)` under the `Apply exemption To` tab:
273
+
> Right click on any one of the class related errors in the ATC Problems tab and choose **Request Exemption**. You can then request an exemption for the whole class by selecting `Class (ABAP Objects)` under the `Apply exemption To` tab:
273
274
274
-

275
+
>
275
276
276
-
Click **Next**, choose a valid approver, a reason to request the exemptions and input a justification for it. Then click on **Finish**.
277
+
> Click **Next**, choose a valid approver, a reason to request the exemptions and input a justification for it. Then click on **Finish**.
277
278
278
-

279
+
>
279
280
280
-
Proceed in the same way to request an exemption for the whole wrapper class.
281
+
> Proceed in the same way to request an exemption for the whole wrapper class.
281
282
282
-
>How to maintain approvers and how to approve exemptions is beyond the scope of this tutorial. After a maintained approver has approved the exemptions, you can verify it by running ATC checks again in ADT: no issue should arise.
283
+
>How to maintain approvers and how to approve exemptions is beyond the scope of this tutorial. After a maintained approver has approved the exemptions, you can verify it by running ATC checks again in ADT: no issue should arise.
283
284
284
285
### Test released wrapper with console application in tier 1
0 commit comments