cancel
Showing results for 
Search instead for 
Did you mean: 

Complex table rowcounts

Former Member
0 Kudos

Hi All,

I am curious to find out what sort of row counts have been experienced as working in the wild for SAP Work Manager. (6.x)

We have a project running here in Australia for a large Utilities company who have a very large and in some cases very dense (geographically) asset inventory.

For the Functional Location and Equipment complex tables this poses us some challenges as there doesn't seem to be any really good way of limiting these datasets down to what I expect are workable levels on individual devices.

We are going with recent Apple iPads as our mobile device platform so size shouldn't be a problem from a straight storage perspective. My main concerns are around performance of the app (if I have large numbers of records in these tables) and synchronisation times.

Anyone out there willing to share their experiences?

Regards

Marty

Accepted Solutions (1)

Accepted Solutions (1)

jason_latko
Active Contributor
0 Kudos

Marty,

How large a dataset are you talking about per complex table?  Tens of thousands are common.  Hundreds of thousands should also be OK on a smart device.  Millions of rows in a table might be a problem.

Jason Latko - Senior Product Developer at SAP

Former Member
0 Kudos

Hi Jason,

Thanks for the reply.

We don't have any tables where we expect millions of records. The worst at the moment looks to be ctEquipment at around 750k for the largest region.

Are there examples of this sort of size working in production on the iPad?

I'm assuming that the problems would be twofold:

1. Time needed to synchronise

2. The performance of the application with that many records

The business has processes in place where the functional location and equipment data does experience a fair amount of regular change. This is driven by automation from their GIS system. There is analysis underway right now to try and quantify this but if the delta on these two tables is large then synchronisation times could well blow out.

I am getting the feeling, from your post and some others I have spoken with, that a modern tablet like the iPad should be able to handle table sizes in the order of what we are dealing with. Certainly with 64GB of storage available we should be able to fit the data. There is still some question in my mind an the performance if screens, dropdown lists etc. It would be very nice to get some sort of confirmation on this.

Should we be considering pre-caching the data somehow in order to minimise these sync times? It would seem to be that the majority of the time spent during the synchronisation is due to the complex rules being applied for the selection of records (BAPI / ABAP execution time). Actual transmission (WiFi or 4G) would appear to account for a relatively small component of the overall sync time.

Regards

Marty

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi All,

Can anyone out there give me an idea of your max record sizes?

Work Manager on iOS would be best.

I really need to get an idea of whether our current estimated record sets (Max 460,000 records in ctLocations) for a given region is going to be doable. Jason indicates that is should be possible in his post but I'd really like to be able to hear from someone that has done this with an big dataset.

thanks in advance.

Regards

Marty

Former Member
0 Kudos

There is no max record size for complex tables.

You may want to look at this pdf that talks about Agentry and SMP Metadata Performance Tuning: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20b74700-7e95-3110-478d-aad30d74c...

Former Member
0 Kudos

Thanks for the doc. There are definitely some points in there that we will look at applying,

While I appreciate your comment about there being no official 'max record size' my question was more aimed at the operational / performance aspect. Does the application perform terribly if I have 500k records in the ctLocation table? Likewise for ctEquipment?

I understand that sync time, delta calculations etc are impacted by large record sets. What I was after was a feel for what is possible.

Our asset inventory (major electricity distribution business) has largish regions. Within some of these regions there are very large numbers of assets (think electricity poles and the equipment hanging off them for a major metropolitan city). The business is adamant that they cannot split the regions down to smaller sizes and still give their technicians the information that they are likely to need.

Do you know of any customers using Work Manager with these sorts of size record sets?

Regards

Marty

Former Member
0 Kudos

It should be find as long as you don't have use complex table look up looks on List TIle view.

If you find any screen that does feel to slow, look at the screen and see if there are any Complex Table looks up and if there are see if you can find ways to remove them by default the data, or filling it before you get to the screen.

0 Kudos

, , , and , please provide some details on this kind of sizing for customers if you have it.  Or point Marty to someone who would know how large of tables customers have been successful using.

Thanks, Mike

SAP Customer Experience Group - CEG

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Unfortunately, we typically don't track historical customer data volumes.  Unless someone remembers a project with details there isn't a source to reference for this.

Sorry,

--Bill

0 Kudos

Hi Bill,

Yes, I know it is going to be anecdotal information at best, but anything which might provide some insight to Marty is what I am looking for.  Maybe a business blueprint would hold that type of information?

Thanks, Mike

SAP Customer Experience Group - CEG

Former Member
0 Kudos

Hi Mike,

Thanks for the follow-up. Anecdotal would be fine.

We are currently in the position of having to choose either going with a vastly reduced dataset and limiting the Notification create functionality (as we won't have all assets available to select) or coming up with a completely custom solution to limit the data to that which is in a close proximity to the Work Orders that the user will have on their devices.

As you can imagine the work-around in order to get this second option to work is potentially very significant in terms of development time as we would need to determine the work orders for a user prior to the Complex Table synchronisation. This is certainly 'clunky' when compared to the way that Work Manager is supposed to function.

The new functionality in 6.2 around being able to search for an asset by way of a fetch breaks our core requirement of being able to operate in an offline mode.

Ideally I'd love to hear that someone has successfully run a production system where the ctLocation and ctEquipment tables each have in the order of half a million records. Delta on either table could be up to 5% for a given sync due to the fact that we are getting updates into SAP from the GIS system each night.

Can anyone indicate if this scenario is feasible?

Regards

Marty