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]

Hi folks,

I've just a problem with transporting a Web Interface to a BPS application from DEV- to Q-System. I tried two different way:

• Development of a Web Interface in $TMP. Collecting the generated BSP-Pages into a transport request.

=> Error after transport from DEV to Q-System: "Error with initialization or error on BSP page" and "Internal error: NO_METADATA_AVAILABL".

=> First assumption: No MIMEs-directory in the BSP. Therefore it was created manually and all MIMEs where imported. But: Same Error

=> Second assumption: In BPS_WB the Web Interface to the collected BSP is missing on Q-System. Even if this comprehensible: Is this the reason for the error?

• Second try: Copy of the complete Web Interface into a new Web Interface in the needed package and transport request.

=> Error after transport from DEV to Q: "Error with initialization or error on BSP page" and "Internal error: NO_METADATA_AVAILABL".

=> Again: MIMEs-directors was missing to the BSP. Again manually created. But: same error.

=> In the Q-System even the copied Web Interface is missing. Why? Shouldn't it be there in BPS_WB after the transport?

For me it seems to me that the transport of a web Interface to a BPS-application was successfull if it is shown in the BPS_WB after the transport. But: What is to do to get it there?

I appreciate your help! Thank you.

Regards,

Carsten

[Former Member]

Hi Carsten,

d

id you manage to solve the problem. I got the same message and can't figure out the solution.

Thanks a lot.

Pavel

[Former Member]

Hi,

if someone is intrested, the problem was in missing data rows in following tables:

UPWB_MDATA

UPWB_MDATAT

UPWB_DATA

Hence the solution is to transport the content of those tables.

P.