2010 Oct 28 4:15 PM
Hi all,
I have a situation where I've got single connection object (a hospital) with hundreds of devices installed.
I migrated the data for this hospital and I end up with several hundred device locations, relating to the devices. I was able to technically install the devices.
When I go to look at this connection object in ECENV_CO though, I get an error "Data environment is incomplete: too many objects" (Message no. ECN30)
It sounds like it's simply a display type error, which I'm hoping it is. My concern is that there may be a limitation somewhere around a corner waiting to bite me when I try to use these installations and bill / invoice.
This can't be altogether uncommon - does anyone know if there's a limitation anywhere regarding # of devices or installations? Or, if you have had a similar scenario would you please share whether it was successful or not, and if unsuccessful what was the ultimate cause and resolution?
Thanks in advance for your insights.
Regards,
CN
2010 Oct 30 8:33 PM
CN:
Your problem is one of performance - for call center functions, showing all data is not usually desirable due to runtime problems. Additionally, billing performance is lessened with more complex data models. But they are normal scenarios in the solution. One person's large is another's small. there is no one size fits all approach, no one all encompassing solution.
regards,
bill.
2010 Oct 29 11:52 AM
Dear C N,
I checked the message you mentioned and you're right it's a kind of display error. It says "If there are more than 100 objects on one level then no more dependent objects were selected for the corresponding object". So, I assume you have more than 100 objects (installation, device, etc.) in your connection object. But one thing I have to say about this issue is that I have been working with high number of data even with more than you mentioned, and never had problems. So, I don't think you should worry about the limitations. Yet again, there may be a limitation which I didn't know. My proposal to you is to run tests with high number of devices, installations, etc. For your convenience you can use MDT (Master Data Template) to create the technical master data in an easy manner.
Hope it helps,
Regards,
Eren
2010 Oct 29 3:02 PM
Thanks Eren for sharing your experience.
Yes, we will be testing our scenarios for sure.
I just wanted to benefit from knowledge of the experts out here who have implemented various systems and scenarios also.
CN
2010 Oct 30 8:33 PM
CN:
Your problem is one of performance - for call center functions, showing all data is not usually desirable due to runtime problems. Additionally, billing performance is lessened with more complex data models. But they are normal scenarios in the solution. One person's large is another's small. there is no one size fits all approach, no one all encompassing solution.
regards,
bill.
2010 Nov 01 3:05 PM
Thanks Bill for that info. I had not thought in terms of performance, and of course that makes total sense.