WebDynpro Java DC throwing build error after migration from 7.0 to 7.3

[Former Member]

Hi

We have migrated WebDynpro java dc from 7.0 to 7.3, after migrating when we rebuild & build the DC, it is having build error.

NetWeaver Developer Studio 7.3 SP08 PAT0011

Error is coming in custom controller as:

[wdgen] [Error]ContextAttribute 'AAA.structureElement': All attributes of the corresponding context node have to be bound to fields of a dictionary structure Hint:Remove the corresponding attribute

[wdgen] [Error]ContextAttribute 'BBB.structureElement': All attributes of the corresponding context node have to be bound to fields of a dictionary structure Hint:Remove the corresponding attribute

[wdgen] [Error]ContextAttribute 'CCC.structureElement': All attributes of the corresponding context node have to be bound to fields of a dictionary structure Hint:Remove the corresponding attribute

[wdgen] [Info] Component //WebDynpro/Component:com.ab.psl.pp.misc.XXXComp could not be generated

[wdgen] [Error] Generation failed due to errors (9 seconds)

Please help in resolving the error.

Thanks

Akanksha

[govardan_raj · Accepted solution]

Dear Akansha ,

The error clearly shows that context attributes are binded to some structure , so is this dc having any rfcs ?

and those node or attributes are binded to struture of the rfc ?

Regards

Govardan

[Former Member · Accepted solution]

Hi Govardan

Yes we have models created in this dc and binding is also present..still the error is there

Regards

Akanksha

[govardan_raj · Accepted solution]

Hi Akanksha ,

Right click the model and you get an option to migrate to rfc 2 , and before that please configure r/3 i.e for importing rfc we give jco details , r/3 server details ,.

then build and rebuild the dc ,

Regards

Govardan

[Former Member · Accepted solution]

Hi Govardan

We are not migrating to ARFC2, we will still be using arfc1.

Regards

Akanksha

[govardan_raj · Accepted solution]

Hi Akanksha ,

I dont think it is possible to use arfc1 , because in 7.31 we have arfc2 .

Regards

Govardan

[ErvinSzolke · Accepted solution]

Hi,

as of 711 ARFC1 is deprecated, see this guide

Using an Adaptive RFC 2 Model in Web Dynpro for... | SCN

Also please review whether you did the migration as described in

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40af00ad-8080-2a10-88b5-cc4cec99d...

The guide is addressing migration to 710, but the procedure is the same.

Perhaps this thread will be useful to you as well:

Regards,
Ervin

[Stefan-EA · Accepted solution]

govardan raj wrote:

Hi Akanksha ,
I dont think it is possible to use arfc1 , because in 7.31 we have arfc2 .


Regards
Govardan

Its still possible to use ARFC1 in NetWeaver 7.3/7.31/7.4. The ESS 633 SAP business package uses ARFC1.

[Former Member · Accepted solution]

Hi

I have followed proper steps for migration except we are still using ARFC1, and will be using the same.

Now I'm getting error in IPrivate views for few context nodes as:

node.currentXXXelement();  >> currentXXXelement is not defined for IWDNode.

though I can see the node in view context and I tried redoing the mapping also.

Regards

Akanksha

[govardan_raj · Accepted solution]

HI ,

in view context and component controller context , please check all attribute type are properly defined ,

cross check all the attributes .in all views context nodes.

Regards

Govardan

[Former Member · Accepted solution]

Hi

My issue got solved, I did the following things step by step :

1) Searched for typedAccesRequired="false" and removed it from wherever it exit

2) Redid the context mapping between used model and custom controller

3) Close project > open project > Reload > Rebuild > Build

Regards

Akanksha