- SAP Community
- Groups
- Industry Groups
- SAP for Utilities
- Discussions
- Emigall validation
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2008 Mar 06 5:18 PM
- SAP Managed Tags:
- Utilities
Hi,
Is there any way I can find out the validations / limitations of SAP when loading data using Emigall? For example, it is easy to find out mandatory fields by looking at table definitions or trying to manually create a business partner using the screens but how do I find out the rules for post codes e.g. GB post codes need to have format XX11 1XX or that devices need to have a meter serial number?
Secondly are there any limitations around loading meter reads e.g. must there be an actual meter read on the device before loading through Emigall?
Finally are there any documents around the amount of history one can load into SAP other than the fact that the more history you load the longer the load time?
Kind Regards,
Michelle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2008 Mar 10 1:33 PM
- SAP Managed Tags:
- Utilities
Hi Michelle!
Question 1: my best practice for finding out required fields in emigall (using partner as an example): First make a BP online (or ask the responsable consultant/key user to make you one). Based on that example, manually fill a PARTNER object in emigall and see if any other fields are required (some technical fields sometimes). I never look at DB table definitions to fill an emigall object
Question 2: you can load any meter reading onto any device in emigall. There are far less limitations than online, which in return makes it a dangerous object! (uploading a 06 meter reading without matching move-in, for example)
Question 3: There is no limit on the "amount" of history or any other data you can load, as long as your system in large enough However, I'd recommend to load as little history as accepted by the business, because every additional (year of) historic data has an impact on the migration strategy and even the functional build of a new system. For example: 10 years of installation facts history means that all rates have to be valid for ten years in the past!
Browse through service.sap.com/utilities. There's a emigall migration cookbook with some useful info on performance and size too.
Hope this helps!
Kevin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2008 Mar 10 1:33 PM
- SAP Managed Tags:
- Utilities
Hi Michelle!
Question 1: my best practice for finding out required fields in emigall (using partner as an example): First make a BP online (or ask the responsable consultant/key user to make you one). Based on that example, manually fill a PARTNER object in emigall and see if any other fields are required (some technical fields sometimes). I never look at DB table definitions to fill an emigall object
Question 2: you can load any meter reading onto any device in emigall. There are far less limitations than online, which in return makes it a dangerous object! (uploading a 06 meter reading without matching move-in, for example)
Question 3: There is no limit on the "amount" of history or any other data you can load, as long as your system in large enough However, I'd recommend to load as little history as accepted by the business, because every additional (year of) historic data has an impact on the migration strategy and even the functional build of a new system. For example: 10 years of installation facts history means that all rates have to be valid for ten years in the past!
Browse through service.sap.com/utilities. There's a emigall migration cookbook with some useful info on performance and size too.
Hope this helps!
Kevin
