Skip to content

Commit a7264cf

Browse files
authored
Merge pull request #2623 from AchimSeubert/main
update factory calendar, no Transport Request - no change recording
2 parents dca04a9 + 80c23e5 commit a7264cf

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

tutorials/abap-environment-use-factory-calendar/abap-environment-use-factory-calendar.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -51,9 +51,9 @@ Create your exercise package. This ABAP package will contain all the artefacts t
5151

5252
Click **Next**.
5353

54-
3. An application component is not needed. Click **Next**.
54+
3. The ABAP Package properties remain as is. Click **Next**.
5555

56-
4. Select an existing transport request or create a new one and click **Finish**.
56+
4. No transport request is necessary, as change recording is not enabled. Click **Finish**.
5757

5858
### Create a Database Table
5959

@@ -70,7 +70,7 @@ Create a database table to store the underlying data of the order application.
7070

7171
Click **Next**.
7272

73-
4. Select a transport request and click **Finish**.
73+
4. No transport request is necessary, as change recording is not enabled. Click **Finish**.
7474

7575
5. Replace the default code with the code snippet provided below (make sure to replace the placeholder ###):
7676

@@ -125,7 +125,7 @@ Use the **Generate ABAP Repository Objects Wizard** built into ADT to create a b
125125
126126
Click **Next**, review the objects that will be created, and click **Next** again.
127127
128-
5. Select a transport request and click **Finish**.
128+
5. No transport request is necessary, as change recording is not enabled. Click **Finish**.
129129
6. Publish the generated Service Binding.
130130
7. Select the entity set **`FactoryOrder`** and launch the **Preview**. Create a new factory order to get familiar with the initial state of your application.
131131
@@ -209,7 +209,7 @@ Each factory order receives a production start date and the required production
209209
<ol type="a"><li>Name: `ZFACTORYORDER_SCALAR_###`
210210
</li><li>Description: `Factory Calendar Tutorial – Scalar Function Definition`</li></ol>
211211
Click **Next**.
212-
4. Select a transport request and click **Next**.
212+
4. No transport request is necessary, as change recording is not enabled. Click **Next**.
213213
5. Choose template `defineScalarFunction` and click **Finish**.
214214
6. Replace the generated code with the following code:
215215
@@ -239,7 +239,7 @@ To link the scalar function definition to the actual logic a scalar function imp
239239
</li><li>Engine: `SQL Engine`</li></ol>
240240
Click **Next**.
241241
242-
4. Select a transport request and click **Finish**.
242+
4. No transport request is necessary, as change recording is not enabled. Click **Finish**.
243243
244244
5. Maintain `ZCL_FACTORYORDER_###=>CALCULATE_PRODUCTION_END_DATE` for the **AMDP Reference** field.
245245
@@ -259,7 +259,7 @@ You will now implement the actual logic for the scalar function, which will be c
259259
</li><li>Add interface `if_amdp_marker_hdb`</li></ol>
260260
Click **Next**.
261261
262-
3. Select a transport request and click **Finish**.
262+
3. No transport request is necessary, as change recording is not enabled. Click **Finish**.
263263
264264
4. Declare and implement a new class method as shown in the code snippet below:
265265

0 commit comments

Comments
 (0)