Web Interface Transport Process

[Former Member]

Hello

I am hoping to get some sort of consensus as to the best / preferred method to maintain and transport BPS web interfaces. I realise that there are already responses to similar questions but there doesn't seem to be concensus or an SAP documented process for this. If there is SAP documentation on this then I would be very happy for someone to point me in the right direction.

The solutions / methods so far seem to be:

1 - Create your web interface and assign it to a transportable package straight away and then assign a transport request at all transport prompts. The effect of this is that any other user who wants to modify the web interface in the future has to be assigned a transport task under the initial request that was created.

2 - Create your web interface and assign it to the $tmp package. This allows all project members to modify the interface until it is ready to be transported for testing. At this stage the web interface is copied to a new web interface and assigned a proper transportable package and the transports generated.

3 - Create your web interface and assign it to $tmp package. Use se80 to reassign the development package and transport the BSP application when ready. However any subsequent transports of the same BSP application from se80 entails making some sort of minor text change or something to generate a transport request.

I am unfimilar with the se80 transport process so forgive me if my assumption is incorrect.

An issue with step 1 that prompted this query was that if you generate a transport when you first create a web interface and subsequently delete that transport. When you generate a new transport some objects such as MIME do not appear to be reattached. It is issues like this I hope to have a clear idea of how to proceeed.

I hate having the feeling that when I'm transporting that I may have left something behind.

Anyway I look forward to hearing from you all and achieving some sort of consensus as to what the best / preferred way to handle BPS web interface maintenance is and their subsequent transport.

Regards

Mark

[Former Member]

No takers

I admit it is not the most interesting of topics.

[Former Member]

Hi,

It would be better to keep note of the objects list, before deleting the request. When the new request is created, you could manually add/edit those noted down objects that were not captured in the new request.

HTH,

Regards,

Nataraj.

[Former Member]

Hi Natarajan

Thank you for your response.

Your suggestion is how we are currently handling the situation.

Regards

Mark

[Former Member]

the best option is to create a web interface in $tmp package the first time and then copy to a new one during which u will create a request and then move it across.

later, even if you want to change the web interface you can as well do it and all mime objects would get attached.thats how we have been handling the web transports.

[Former Member]

Hi Saggi guru

Thank you for your response.

Can you please elaborate abit more on the second part of your reply.

If you change a web interface what is your process? Being as it has now been assigned a development class and transported how do you get it to automatically assign the mime and all other objects? Do you recopy the template to $TMP to change and then recopy back over the original?

Thank you for your response in advance.

[Former Member]

Once you copy a web interface from local to a dev class and create a request when it prompts you all objects are attached to it.Once you transport and find out you want to make minor changes open the web interface and this time after changes when you save it a new request would be prompted.Create a request and move it across.You should be fine this way.