Skip to content

Commit ef7e9f9

Browse files
julieplummer20julieplummer20
authored
Added _000 suffix to field name (#18965)
* Automatic commit: Move 'abap-s4hcloud-procurement-po-customlogic-tracing' from QA to Production * Automatic commit: Move 'abap-environment-create-http-service' from QA to Production * Automatic commit: Move 'abap-display-data-queries' from QA to Production * Automatic commit: Move 'abap-environment-create-http-service' from QA to Production * Automatic commit: Move 'abap-environment-custom-entity-debug' from QA to Production * Automatic commit: Move 'abap-s4hcloud-procurement-po-customlogic-tracing' from QA to Production
1 parent 2cb80ac commit ef7e9f9

1 file changed

Lines changed: 8 additions & 10 deletions

File tree

‎tutorials/abap-s4hcloud-procurement-po-customlogic-tracing/abap-s4hcloud-procurement-po-customlogic-tracing.md‎

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ author_profile: https://github.com/julieplummer20
1818
- In SAP Fiori launchpad, you have the following authorizations:
1919
- **`SAP_BR_PURCHASER`** for the app **Create Purchase Order - Advanced**
2020
- **`SAP_BR_ADMINISTRATOR`** for **Custom Logic Tracing** and **Custom Logic**
21-
- You have created a custom field using Key User extensibility **`yy1_zhdrprnt2_pdh`**
22-
- In Custom Logic, you have created a `BAdI` implementation `YY1_FILLHEADERCUSTOMFIELDS` in the business context and `BAdI` definition **Modify Purchase Order Header (`MM_PUR_S4_PO_MODIFY_HEADER`)**
21+
- You have created a custom field using Key User extensibility **`yy1_zhdrprnt2_pdh_000`**
22+
- In Custom Logic, you have created a `BAdI` implementation `YY1_FILLHEADERCUSTOMFIELDS_000` in the business context and `BAdI` definition **Modify Purchase Order Header (`MM_PUR_S4_PO_MODIFY_HEADER`)**
2323

2424

2525

@@ -39,7 +39,7 @@ Throughout this tutorial, the placeholder `###` or `000` is used. Always replace
3939

4040
!![step1a-open-custom-fields](step1a-open-custom-fields.png)
4141

42-
2. Change to the **Custom Logic** tab, search for the `BAdI` implementation **`YY1_FILLHEADERCUSTOMFIELD`**.
42+
2. Change to the **Custom Logic** tab, search for the `BAdI` implementation **`YY1_FILLHEADERCUSTOMFIELD_000`**.
4343

4444
!![Link text e.g., Destination screen](step1b-custom-fields-tabs.png)
4545

@@ -57,13 +57,11 @@ You can now see the Published Logic and Draft Logic, if they exist, relevant to
5757
[ACCORDION-BEGIN [Step 2: ](Add custom logic)]
5858
1. Comment out any existing code.
5959

60-
2. In the custom logic for the field **`yy1_zhdrprnt2_pdh`**, copy the following code.
61-
This code will copy the content from a standard field, `purchaseorder-supplyingplant` into the custom field, **`yy1_zhdrprnt2_pdh`**, where `supplyingplant` is filled.
60+
2. In the custom logic for the field **`yy1_zhdrprnt2_pdh_000`**, copy the following code.
61+
This code will copy the content from a standard field, `purchaseorder-supplyingplant` into the custom field, **`yy1_zhdrprnt2_pdh_000`**, where `supplyingplant` is filled.
6262

6363
```ABAP
6464
IF purchaseorder-supplyingplant is not initial.
65-
purchaseorderchange-yy1_zhdrprnt2_pdh = purchaseorder-supplyingplant.
66-
endif.
6765

6866
```
6967

@@ -124,7 +122,7 @@ You are now ready to trace the effects of your custom code when a purchase order
124122
| Group | **001**
125123
| Company code | **1010**
126124

127-
> If you check the custom field **`YY1_ZHDRPRNT2_PDH`**, it is now filled with the same value as Supplying Plant, **1010**.
125+
> If you check the custom field **`YY1_ZHDRPRNT2_PDH_000`**, it is now filled with the same value as Supplying Plant, **1010**.
128126
129127
!![step2c-fill-org-data](step2c-fill-org-data.png)
130128

@@ -156,13 +154,13 @@ You are now ready to trace the effects of your custom code when a purchase order
156154

157155
!![step5a-finish-trace](step5a-finish-trace.png)
158156

159-
2. Open the trace. In **Trace Hierarchy**, choose the last call of `BAdI` implementation `YY1_FILLHEADERCUSTOMFIELD`.
157+
2. Open the trace. In **Trace Hierarchy**, choose the last call of `BAdI` implementation `YY1_FILLHEADERCUSTOMFIELD_000`.
160158
(This is necessary because the `BAdI` implementation is called several times.)
161159
Then choose the parameter **Purchase Order**.
162160

163161
!![step5b-choose-purchase-order](step5b-choose-purchase-order.png)
164162

165-
3. Scroll right down to the field **`YY1_ZHDRPRNT2_PDH`**. Check that its value = **1010**.
163+
3. Scroll right down to the field **`YY1_ZHDRPRNT2_PDH_000`**. Check that its value = **1010**.
166164

167165
!![step5c-choose-custom-field](step5c-choose-custom-field.png)
168166

0 commit comments

Comments
 (0)