Transporting Web Dynpro ABAP Objects (Comp, Application, SICF service)

[Amey-Mogare]

Hi,

I want to know if there is special care to be taken while transporting Web Dynpro ABAP object from Dev box to Quality Box.

In my D-Q-P systems, we do normal ABAP objects transport (FM, Reports etc)

But I have never transported WDA objects before. So I would like to know if there is any special care/steps to be followed.

Also, for WD application, I had to create SICF service. It is in separate TP.

Would I be able to run the application in next box?

Thanks and regards,

Amey Mogare

[thomas_jung · Accepted solution]

In general, there is nothing special about transporting Web Dynpro ABAP development objects. The only thing different to consider is the SICF node. Like any other SICF node, the new nodes are transported into the next system as deactive. You have to manually activate them after transport. This is done as a security precaution.

>Also, for WD application, I had to create SICF service. It is in separate TP.

Would I be able to run the application in next box?

Are you asking if you will be able to run the WDA Applicaiton without the SICF Service Node? If so, the answer is no. The Service Node entry is required to be able to run any SICF based application.

[Amey-Mogare · Accepted solution]

Thank you for valuable reply Thomas.

So only thing about SICF is that I need to manually activate Web Dynpro Application after I transport TP for WD Comp and SICF service?

Thanks and regards,

Amey Mogare

[thomas_jung · Accepted solution]

>

> Thank you for valuable reply Thomas.
> 
> So only thing about SICF is that I need to manually activate Web Dynpro Application after I transport TP for WD Comp and SICF service?
> 
> Thanks and regards,
> Amey Mogare

No. All the development objects are delivered active. WDA Applications don't require activation. What will be inactive will be the SICF Node for the Application. All SICF nodes (BSP, ITS, Custom Nodes, etc) are always delivered inactive after transport. You have to go into transaction SICF and activate them.

[Former Member · Accepted solution]

Please Ignore this Post ---> problem identified

I have an additional question to this topic:

I have an application where I putted the SICF entry into a transport and released it to QA-System.

But the SICF-Node is not there.

In development system, the node is diplayed as IC_VE_ABRUFLAGER. When I open the service name ist displayed as G4184135 with an alternative Name IC_VE_ABRUFLAGER.

These data come from the table ICFSERVICE.

IN QA-System the Entry is also in ICFSERVICE, but it is not getting displayed in SICF.

Any Ideas ?

Best regards, Matthias

Edited by: Matthias Drescher on Jul 13, 2011 1:19 PM