cancel
Showing results for 
Search instead for 
Did you mean: 

The creation of device local data objects - Unable to find generated object

Former Member
0 Kudos

Hi all,

I get an error when I try to generate an ESDMA containing a "Device Local" data object.

I have created a "Device Local" data object containing a very simple node structure. The object is "active" and everything seems to work fine, until I generate the ESDMA. The following error is shown : Unable to find generated objects in repository.

The esdma is generated without problems, when I remove the device local data object.

I hope you have some ideas of what the issue might be.

Best regards,

Nima

Accepted Solutions (0)

Answers (1)

Answers (1)

sivasatyaprasad_yerra
Active Contributor
0 Kudos

Can you check if the objects present in SAP BASIS 7.10 are generated completely?

Generation of these objects are mandatory for ESDMA generation to be successful.

Goto SDOE_WB and search for SAP BASIS 7.10 Software component version and generate all the objects if not generated.

Regards,

Siva.

Former Member
0 Kudos

Hi Siva

Actually i am working on this problem together with Nima and the problem is not related to SAP Basis objects.

The problem is in SDOE_WB, with the SWCV. Creating a Data object of type LOCAL DEVICE and a NODE. If you add a field/s and then activate, and look in Generated objects The Table object is not generated (only the structure and the table type). At this point there are no syntax/error messages.

If we try to generate an esdma using the ESDMA design time, using this SWCV, it fails, with the message, Unable to find generated objects, in the repository. That is it is looking for the Table object that was not generated in sdoe_wb. This is only a problem with creating a data object of type DEVICE LOCAL, every other type of DO is fine.. I assume it is an SAP error.

Former Member
0 Kudos

Actually I was just informed that data object type DEVICE LOCAL cannot be used with co-innovation architecture.

rgds

James

Former Member
0 Kudos

Yes, that is true. There is a workaround, which includes defining your custom device objects (XML) within the sup-db.xml.