OME4 Transport reqeust issues in 4.6

Question

Hi Folks,
I have to apply SPRO->OME4 customization changes into production system. In 4.6, system doesn't ask to create a transport request when a customization change is made using tcode OME4. I created a transport request using
"Table View ->Transport" option, but the problem is i don't see any objects in the transport request.
When i see an old transport request created by a different user, i see "V_024" object name. I am not sure what i doing different, which is causing not to include objects in the transport.  I also created a transport request by selection all entries and  pressing "Include in request". I noticed a messenge some thing like  "50 entries selected to included in the request" but no object is request. I am not sure, if this is normal or i am doing something wrong. Could you please, help us on how to create a correct transport request in this scenario. Thanks a lot for your help.

Answer 1

Hello rk_007,
when you perform any change in the view V_024 in transaction OME4, it a customizing change in that particular client in the system.
Recording of customizng changes in a client in a system depends on some of the following settings. They are:
1. Transaction SCC4:
Change and transport for Client specific customizing objects - when Automatic recording is chosen, any customizing changes is forced to record into a transport request.
2. In SE54, generated object, Recording routine setting - Standard recording routine -  this is the connection with the
transport tool. When this is chosen, changes in that object will be recorded into transport request.
  No, or user recording routine -  connection to transport tool is removed. So its not mandatory to record the changes into transport request.
In this case, please check what is the settings maintained in the SCC4 transaction. You can set the setting accordingly.
Then please check the setting maintained in SE54.
1) Goto Se54, choose generated objects radio button.
Display the setting
Choose the value no,or user recording routine.
Save the changes made.
You might be asked for a developer key to make this change. Please generate a developer key and make this change.
With this change, when a customizng change in this view is performed, user is not forced to record into a transport request ie. no pop for transport request is shown. Still it can be manually transported if required.
Also, as an additional information, there's the 'current setting flag' parameter. Current setting flag is used only to make the customizng object editable in a productions system (client role = Production). This does not play any role in a non productive system. For details on current setting flag refer to the note 77430.
I hope this helps
Best regards,
Tomas Black