Not Save in package

[Former Member]

Dear All,

Whenever I am doing any change in img or create anything in IMG,it is saved in other place and generate customise request number instead of saving it in package and generating workbench request number.Although I have created package through SE80 and activated it through SE38.So,I want to save my all img configuration changes and creation in package and workbench request instead of customise request.Can anybody solve this problem ???

with regards,

RANA

[Former Member]

Dear All,

Whenever I am doing any change in img or create anything in IMG,it is saved in other place and generate customise request number instead of saving it in package and generating workbench request number.Although I have created package through SE80 and activated it through SE38.So,I want to save my all img configuration changes and creation in package and workbench request instead of customise request.Can anybody solve this problem ???

with regards,

RANA

[ThomasZloch]

A fundamental misunderstanding.

Most IMG settings are table entries, these cannot be assigned to a package, as opposed to development objects. You must use customizing requests. However, somewhere in SE01 area menu, there is a way to assign a customizing request to a development request, so that you can later move all related changes together inside one request.

Thomas

[Former Member]

Dear Thomas,

Can you tell me how can I move all my changed customize request to one request ? and can I move all changed customize request to package or workbench request ?

with regards,

RANA

[alex_cook]

Howdy,

Why do you think you need to move your customizing to a workbench request or package?

As Thomas has described, that is not how customizing works, which is why Customizing request is a specific kind of transport.

As for merging all customizing requests into one you can do so by using right clicking on the transport in SE01 and using Merge Requests function.

If you want to make a Workbench request dependent on a Customizing request you can do so in SE01 (Goto -> Dependency Information) but I think it is only a warning when you release the request - it doesn't prevent the transport going through.

Cheers

Alex

[GauthamV]

You can use SE03 transaction and Merge object list functionality to create 1 new request for all your change requests.