How to change dev class $TMP for the repository objects of an OData service?

Based on a question that has been asked in the followig thread How to assign OData Model and SRV to TR from Local Object $TMP  I did a little research how to change the development class $TMP for those objects. I found a useful reply by Jan de Mooij  in the following thread change of source system – any mass transaction? | SCN.

Since all the examples that I posted in SCN so far are using $TMP as a dev class I also thought that more than one user might have run into the issue of having created a cool service in $TMP and facing the problem how to transport the same into the quality or productive system landscape.

For this document I created a new user DEMOSE80 and created a project ZTEST2 using this user in the Service Builder and generated the runtime objects and registered thus the service in the backend.

Let’s first have a look which objects are created when generating the runtime objects of an OData service ZTEST2 in the backend system using SEGW.

PGMID OBJECT OBJ_NAME

R3TR  CLAS   ZCL_ZTEST2_DPC

R3TR  CLAS   ZCL_ZTEST2_DPC_EXT

R3TR  CLAS   ZCL_ZTEST2_MPC

R3TR  CLAS   ZCL_ZTEST2_MPC_EXT

R3TR  IWMO   ZTEST2_MDL                      0001

R3TR  IWPR   ZTEST2

R3TR  IWSV   ZTEST2_SRV                         0001

Beside the 4 classes you will find the Service Builder project R3TR IWPR and the service R3TR IWSV and the model R3TR IWMO.

To change these entries you can use transaction SE03 and choose “Change Object Directory Entries”.

When you click on the entry mentioned above you can select the entries that we are looking for as follows:

We will get the following dialog screen

Here you can either select a single entry and press the change object directory button (which I did for two objects) or you can select multiple entries using F6.

and then enter MASS in the OK Code field as suggested by Jan de Mooi in his comment mentioned above .

In the following dialog you have to mark the field Package and enter the name of the new dev class (here ZDEMO).

As a result all objects are now in a dev class ZDEMO that can be transported.

If you have activated the service on the hub you would have to change the following objects as well:

R3TR IWOM ZTEST1_MDL_0001_BE  , the SAP Gateway Model

R3TR IWSG ZTEST1_SRV_0001     , the SAP Gateway Service

R3TR SICF ZTEST1_SRV          , the SICF Service.

For questions about transporting SAP Gateway Services see my SCN document How to transport Fiori like applications using SAP Solution Managers Quality Gate Management

Best Regards,

Andre