To help kick off this series of post, live from AXUG, I wanted to highlight a great video that dives into some of these improvements. This video has Microsoft’s own Sri Srinivasan walking us through some of these great new concepts.:

I will be diving into these area’s as a new series of post, and how these can be applied, used, affect and improve your AX 2012 investment.

That’s all I have time for now, but check back soon as a whole lot more coverage to come, including some great post-AXUG Summit articles.

Till next time!

"Visit the Dynamics AX Community Page today!"
 

See more here:
AX 2012 Performance Improvements

This is critical for enabling multiple instances of AX 2012 to function, while not increasing the need for another actual server role, virtual or not. To enable this, Microsoft has refined the steps in order to achieve this, which I’ve done now several times actually. The home page on TechNet for achieving this task can be found here.: TechNet: Install multiple instances of Reporting Services on the same computer (for use with Microsoft Dynamics AX) [AX 2012]

The steps for achieving this second instance, after doing the initial SSRS deployment, can be found as follows:

• Install the new Reporting Services instance
• Configure the new Reporting Services instance
• Modify Reporting Services configuration files
• Restart the new Reporting Services instance
• Create a new Microsoft Dynamics AX configuration
• Connect Microsoft Dynamics AX to the new Reporting Services instance
• Deploy reports to the new Reporting Services instance
• Revert to the original Microsoft Dynamics AX configuration

With this in hand, and making sure you pay special attention to the order of these steps, and follow each step correctly, you should, with relative ease, be able to install multiple instances of SSRS on the same server role, pointing to different instances of AX 2012.

I will point out, that there is a chance you could run into a possible deployment security related issues, that I wrote about in the past: AX 2012 – SSRS Security deployment issue.

Hopefully this will help someone out, who is wanting to take advantage of having multiple SSRS instances on the same windows server role, pointing to different instance of Microsoft Dynamics AX 2012.

That’s all for now, but check back soon as I continue my dive into Workflows, Performance series post, design patterns, Dynamics Ecosystem coverage, as much, much more!

Till next time!

"Visit the Dynamics AX Community Page today!"
 

Continue Reading:
AX 2012 – Install multiple instances of SSRS

Today, I wanted to focus on Microsoft Dynamics AX in the Cloud: Today & Tomorrow.. This has been a topic I have focused a lot of time and effort on in the past few years, and something that really has come to a point of reality for Microsoft Dynamics AX. This is no longer just theory and what will be. This is something real, today, and something that you need to be thinking about.

With that, MSDynamicsWorld.com is hosting it’s bi-annual virtual conferences, Decisions Fall 2011 in which I’m honored they have ask I speak at. For my part, and to the title of this post, I have recorded a session on Microsoft Dynamics AX in the Cloud: Today & Tomorrow. If you have not registed for this great, free! virtual conference, please visit the following site now, and make sure to attend the AX Day on Dec 5th.

You can connect with my session details at the following: MSDW: Microsoft Dynamics AX in the Cloud: Today & Tomorrow – By J. Brandon George. From the highlights:
“[Brandon George] will lead a session covering the concepts, technology, architecture and benefits of the partner-hosted Microsoft Dynamics AX cloud offering. He will also dive a little bit into the future with what AX v7.0, and what the cloud options will look like for future releases.”

If you look at all the sessions for AX day, for this great event, the Cloud is a hot topic. There are two other sessions along with mine, that will focus on AX in the Cloud, as well as Microsoft Dynamics ERP and the cloud. I will recommend, that you attend as many sessions as possible. Also, I will be online during the session, and be apart of the live Chat Q&A. So please, join us, and bring your thinking caps, and ask those hard questions! Any and all are welcomed!

Alright, well that’s it for right now. Check back soon, as I dive into the performance improvements for AX 2012, talk turkey around my continued focus on workflows and thier use for empowering business process modeling, and many other great topics.

Till next time!

"Visit the Dynamics AX Community Page today!"
 

More here:
Microsoft Dynamics AX In the Cloud: Today & Tomorrow

The link to the TechNet article on this topic can be found here.: How to: Configure a Report Server Scale-Out Deployment (Reporting Services Configuration)

What’s another great article to point out, and this applies to scale of services in AX 2012, is the following: Configuring network load balancing for services [AX 2012]. This link then, helps not only enable scale of reporting, but also gives us firm ‘Yes’ services, and therefore integration points, can scale out via NLB as well.

Finally, the article that brought this together today, is from the following: Microsoft Dynamics AX 2012 Reporting Services – Scale-out deployments

I recommend really review the above, and understanding the fact that, when it comes to certain roles in Dynamics AX, relating to performance and Scale, sometimes the role is meant to scale out, vs. scale up.

Also, here is a list of reporting blog post I have done recently:

• AX 2012 Reporting Architecture Model Review
• AX 2012 Reports Executing on your iPad
• Upgrading Reports for AX 2012 – Resources
• AX 2012 – Install multiple instances of SSRS
• AX 2012 – Report Programming Guide / MVC

As you can see, as the title of the post implies, reporting is for sure on the brain, for AX 2012. The idea, is to better understand the concepts, the model, the delivery options, as well now as the ability to scale out for reporting needs.

I actually, as stated earlier today, have a lot of great post that will be covering the BI story more generally, as well as specifics for AX 2012 that will build from these kinds of post. That’s all for now though, check back soon!

Till next time!

"Visit the Dynamics AX Community Page today!"

See more here:
AX 2012 – Reporting on the brain!

Recently, I started talking about Performance in AX 2012, and how this goes beyond the database layer. It’s still true, that the majority of performance is around the SQL Server, and specifically the disk I/O Sub-system speed.

However, with that said, there are some great improvements throughout the layers that make up AX 2012. Something recent that I highlighted was around Scale out of SSRS as well as Services.

Keeping with this theme, and to highlight some other area’s of performance improvements, lets move towards the code side of things. To help set the stage, lets reference a Microsoft resource: Compile into .NET Framework CIL [AX 2012].

“The Compile into .NET Framework CIL task converts your compiled application code into Common Intermediate Language (CIL) code that can be consumed by the Microsoft .NET Framework.”

With this, there are certain area’s of AX that always compile down to IL / MSIL / CIL. All of those are in reference to the .Net Framework execution. This means, that the same C# code that actually executes, is compiled down to IL. The same now, takes place for some area’s of X++. There are huge benefits in code execution when this is the case, and why this is such an important topic to understand from a performance point of view.

Keeping this in mind, there are sometimes when X++ code does not execute as CIL. Wouldn’t it be neat, if there was a way to execute code as IL, X++ code that’s not compiled down to IL? There is a way!

Enter: SysDictClass::invokeStaticMethodIL() “Runs the specified method and makes sure that the method is executed under X++ IL.”

Now there are some remarks, that need to be understood from the above reference.: “This method demands the XppILExecutePermission class and asserts both the RunAsPermission class and the ExecutePermission class. The invocation will transition to X++ IL by using the RunAs function if it is running as interpreted. If it is already running as X++ IL, the method is invoked directly.

As there may be some overhead, this method should only be used on computationally-extensive methods.

This method will not transition to IL if the current TTS level is larger than zero (unless forced) because the transaction scope does not flow across IL boundaries.”

With this in hand now, we have a way to help possibly boost performance, and execute static methods, and therefore area’s of code that could benefit from running in the IL, or chunks of Business Logic that can be statically invoked or kicked off. This is a nice little gem of knowledge to keep handy, when your facing down performance issues, and really need to squeeze all the resource juice you can out of a process.

Well that’s all for now, but check back soon as a whole lot more to come. Till next time!

"Visit the Dynamics AX Community Page today!"
 

View post:
AX 2012 – Performance and IL – invokeStaticMethodIL

Now with that Microsoft Dynamics AX 2012 Cumulative Update 1 has been released. You will need PartnerSource access to get it. It can be downloaded from the following.: Cumulative Update 1 for Microsoft Dynamics AX 2012

I can’t cover the details of what all this fixes, as it’s released under: The information in this article is provided to you in accordance with your Confidentiality Agreement

I can however say, that after reviewing the list there is a lot of fixes around upgrades, with some functional area specific fixes. This CU1 is a must, and this brings a good time to point out in Microsoft Dynamics AX 2012, the new Update process.

In the past, you would have to take and, say wanted to install multiple updates. Well you would run the RTM Setup, and then perform any updates. That’s not the case anymore! Now you can take updates, and place them within the Update folder of the network shared AX 2012 install location.

Next time you need to setup something, single setup process, and the CU1 will be applied as part of that install.

For already existing instances, or installs you will need to apply. One final note on this, the build before the CU1 being applied is: 6.0.947.00 and the build after the CU1 being applied will be: 6.0.947.61.

That’s all for now, but check back soon and often as more to come! Till next time!

"Visit the Dynamics AX Community Page today!"

Continue Reading:
Cumulative Update 1 for Microsoft Dynamics AX 2012

First it’s very important to understand what it means for having data published as OData feeds, coming out of Microsoft Dynamics AX 2012. This starts with a query object within AX, as shown below.:

This is the basis for an OData feed being published, as it’s similar the base for Document Services in AX 2012. This is were we stop though, and go a different path from Doucment services, for enabling these feeds. From here, we need to take and go into the Application Workspace, and navigate to: Organization Administration > Setup >Document Management > Document Data soruces.

From here, we need to take and add a new entry. If we do not do this, then nothing will show as active in our list of possible OData feeds. In order to create go to File and then new to create a new document. Once you have the screen up, you should then select the data source type of Query, and select the query we created from the drop down. After that we click “Activate”.

At this point, AX system service called ODataQueryService will be what publishes our new query document source we just setup. To test this out, you can open up a IE window, and type the following (Assumes your on the AOS): http://localhost:8101/DynamicsAx/Services/ODataQueryService/

When you do this, and Atom list of queries, that you have security rights too, will appear to work with. That’s it for enabling a query to be published as an OData feed. We can start working with this right away yes?

Well, like all great baking stories there are little things that you need to understand so the final product comes out tasty and delicious!

So say, and in the real world this will be the case, that you have Excel and PowerPivot installed on a seperate machines from your AOS. Well if this is the case, and you wanted to work with your published OData feeds from the seperate machine, you might think, ok so instead of using localHost I would use the actual server name.

Wrong! This will cause a 400 Bad Request to be generated, and the reason is the implementation of OData does not allow the use of named servers. You have to use the IP Address of the server in which the ODataQueryService is being published from. So the correct format, to access this from a remote server, or just really separate server than that which the AOS is running is as follows: http://xxx.xxx.xxx.xxx:8101/DynamicsAx/Services/ODataQueryService/

Now of course, any good cook knows that you replace the xxx with the actual values of the ip address itself, however for good measure I point that out to you here.

Doing this, we are actually able to take and see the WSDL, after logging into the box when prompted for our AD creds. You do have to login the first time with your AD creds, however after that you should be fine.

Now that we have our WSDL showing up, we can launch into PowerPivot, and click to add Feed data sources.

Make sure to take and enter into the URI the same format as you did before, and click test connection. This should come back ready for your use, and hit next. In doing so we should see our new query document data source from within AX 2012, being published and therefore able to be consumed as an OData feed.

Now that we have this, we can work with our Query document data sources from within PowerPivot to create some wonderful self-service BI goods! It’s pretty powerful stuff to be able to do this, and this adhere’s to the security model within AX. Therefore if you have rights to a query then you will see it. Otherwise, you will not see it.

Well that’s all for now, I hope you have enjoyed the cooking theme use throughout this post. Till next time!

"Visit the Dynamics AX Community Page today!"

See more here:
AX 2012, PowerPivot and a Dash of OData Feeds

With the launch event for Microsoft Dynamics AX 2012 around the corner, I thought it would be great to gain insight from the two Microsoft partners, Sunrise Technologies and Edgewater Fullscope on this big event.

I virtually, sat down with John Pence, President of Sunrise Technologies (www.sunriseconsult.com). [JP/Sun]

(John Pence)

As well as John Scandar, EVP Edgewater Fullscope. [JS/EFS]

(John Scandar)

I wanted to pick their brains a little, and get their thoughts on Dynamics AX 2012, the launch event, and why Microsoft Dynamics AX 2012 is the new Safe bet in the ERP landscape.

Without further ado, here is the result of the interview:

Microsoft presents Dynamics AX 2012 as the Powerfully Simple ERP solution. What does that mean for prospective Microsoft Dynamics AX customers? How does that message translate to what Sunrise Technologies and Fullscope offer their Microsoft Dynamics AX clients?

[JP/Sun]: The core value that Dynamics AX 2012 begins is a powerful, robust ERP system that is also elegant, easy to learn, and adaptable. Making something complex simple to use is the pinnacle of great software engineering. Sunrise and Fullscope will present a series of dynamic examples that will illustrate the power of Dynamics AX 2012, while demonstrating the ease of use and intuitive nature of the system.

[JS/EFS]: In a nutshell, Microsoft Dynamics AX 2012 is simple to learn and use so you can deliver value faster, take advantage of business opportunities, and drive user involvement and innovation across the organization.

The word SAFE is used by Sunrise and Fullscope to describe Microsoft Dynamics AX 2012. What do you mean by Microsoft Dynamics AX 2012 is the SAFE choice? What should prospective clients expect from an ERP solution that is Safe, Powerful, Agile, and Simple?

[JP/Sun]: Safety is at the very core of every ERP decision. Will this vendor still be here in 15 years? Will the software keep up with the rush of technological innovation over that time span? Will I be able to adapt and grow my business without the software holding me back? Without a doubt, Microsoft Dynamics AX 2012 represents the safe and powerful choice for business. Is any vendor better positioned to adopt their ERP solution to future changes in technology? I think the answer is very clear. Microsoft will be leading the technology charge and Dynamics AX 2012 will be integrated seamlessly into that future.

Can a company feel safe in their software investment with Dynamics AX 2012? Absolutely! With a single, low cost server license a company has access to any module, language, and capability within Dynamics AX 2012. Adding a new sales division internationally? Dynamics AX 2012 protects your business by including multi-company, multi-language, and multi-currency in the same license and instance. No need to deploy a new system because of the new geography.

Expanding into new lines of business? Dynamics AX 2012 protects you by including all the functionality you need to diversify your business. As your business grows you simply add new users to the existing system. The user types are tailored by the actual job preformed, so you never over pay for a new user. The system can scale to meet the most demanding needs of large, multi-national organizations, but is simple enough for a start-up to implement quickly.

Safety in business means managing for the long term. Microsoft Dynamics AX 2012 insures that your software can keep you safe as your business grows, expands, and diversifies.

[JS/EFS]: “Safe” means a lot of things, including free from danger or risk; healthy; and even extends to phrases like a “safe bet.” Safe was once used in reference with a career, and selecting an ERP system was easy when money was no object – just make the system work. Times have changed, and the definition of safe has changed.

Every week you can read about a failed ERP system or hear about such a failure via the grapevine or from another colleague. Manufacturers and distributors spend millions of dollars over the lifespan of an ERP system. The decision to buy a new system or upgrade to a new one is a serious financial commitment and can mean the difference in building or breaking a career for the teams involved with the project. And then there are shareholders — if you are a publicly traded company, your shareholders expect results from technology investments, not excuses.

When planning our launch events, we liked the connotations of “safe” when applied to a business context and specifically an ERP environment. Microsoft Dynamics AX 2012, backed by the corporate strength of Microsoft and leading Dynamics AX implementations partners Fullscope and Sunrise, is a safe bet for your business.

How?

• Global companies can enable entities across a multisite, global organization to share the same systems and business rules in order to streamline business processes, business intelligence (BI), and reporting at lower costs and with faster deployment.

• Large enterprises can execute a two-tier ERP strategy so they can standardize on a single solution to manage operations across multiple sites and connect to the headquarters’ ERP system—while lowering costs and increasing agility.

• Organizations with legacy systems can standardize multiple disparate systems requiring different IT skill sets and lacking consistent interface and reporting capabilities on a common solution that can be rapidly adopted and easily supported.

• Growing companies can create, adapt, extend, and streamline business processes quickly and easily to gain competitive advantage and accommodate aggressive growth—for example, adding new sites or acquisitions—in an uncertain economic environment.

• Midsize businesses can benefit from an enterprise-class solution and rapidly implement industry-specific and core ERP capabilities to meet their specialized needs.

These things can translate into a safe, healthy, sound, less risk ERP solution — and we thought that sounded like a good idea for our customers.

In a paragraph or two, explain why Microsoft Dynamics AX 2012 is a generational shift in ERP?

[JP/Sun]: Dynamics AX 2012 is a completely new way to think about an ERP system. Prior to Dynamics AX 2012, ERP systems have been large, separate applications designed to run “on” the surrounding technology of the servers, databases, email systems, etc. They were one more bolted on app that was just larger and more complex than the others.

Dynamics AX 2012 has truly been designed to live “within” the computing ecosystem of Microsoft technologies. The application takes full advantage of all the other aspects of Microsoft’s solutions such as databases, office communications, information worker tools, etc. to create a simpler, more powerful solution for a business.

This allows the ERP system to move beyond just providing an integrated data model of the business, but really powering the real work flows of how the business operates, and doing it in a way that will stay current as all the technologies evolve in the future. In short, Microsoft Dynamics AX 2012 is a powerful, but safe and low risk approach to a company’s technology needs.

[JS/EFS]: The combination of scale, functionality and role-tailored access are big game changers in the ERP world. Given Dynamics AX 2012’s integration to other Microsoft products, it allows customers to really be more productive in an unprecedented way.

How can Manufacturing / Distribution companies specifically benefit from what comes with this next major release of Microsoft Dynamics AX? (What are some specific business value additions that exist only in Dynamics AX 2012 that apply?)

[JP/Sun]: Manufacturing and distribution have become global work flows for all companies, large or small. Dynamics AX 2012 is uniquely designed to handle that global operation in a single instance for all the global processes of a business. The application supports multiple languages, currencies, and companies in a single instance, with just the base license of the software.

The application has “global intelligence” built-in to the application and security model. Employees, vendors, and customers are automatically presented information in the language and currency that makes sense to them, while still maintaining corporate control of the entire enterprise. This is a game changer for companies that today must use different systems around the globe to manage their supply chains.

[JS/EFS]: Manufacturers in particular should be very excited about this release because it supports true mixed mode operations. Microsoft Dynamics AX 2012 allows a customer to use one ERP system to manage operations across all of their product lines.

For example, a manufacturer could produce a variety of products with different manufacturing modes (lean, kanban, process, discrete, etc.). Unlike other solutions that force you to choose one primary way to run your business, Dynamics AX 2012 is very flexible and lets a customer choose the best operational mode based on the product line. No more driving a square “process” peg into a round “discrete” hole.

What makes Sunrise Technologies, and Edgewater Fullscope stand out as premier partners?

[JP/Sun]: At Sunrise we only focus on Dynamics AX. We have become a leading reseller by focusing on making our customer’s great ideas actually work in the real world. We are experts at turning the powerful tools provided by Microsoft into great implementations for our customers. Our focus will always be on turning the best ERP system in the market, into the best solution for our customers.

[JS/EFS]: Fullscope focuses primarily on Microsoft Dynamics AX. We’ve sold it to over 200 customers, and 90% are process and discrete manufacturers. Our consultants are seasoned experts who know manufacturing, which leads to smoother implementations that provide measurable value for our customers.

We also use our deep manufacturing experience to develop additional solutions that run on top of Dynamics AX to solve specific industry challenges, as well as general needs like data collection or FDA validation of manufacturing software and the manufacturing process. Fullscope has won the Dynamics AX partner of the year award twice and the worldwide manufacturing partner of the year award twice.

The company is a Microsoft Gold Certified Enterprise Resource Planning Partner, and is certified by AMR in process and discrete manufacturing.

I would personally like to thank both John Pence and John Scandar in this effort, and taking the time to give us some insights around the launch event that will be taking place on Thursday, September 8, 2011 as well as later dates for other cities.

As this event gets closer, I will dive into more specific content, on what will be covered, and help give some insight into what you can expect.

That’s all for now, but check back soon; a lot more to come! Till next time!

Just in case you missed it, you can use the following to go and register now for the event… Just a click and your ready to go!

"Visit the Dynamics AX Community Page today!"

View the original here:
Insights from Top Partners on the Microsoft Dynamics AX 2012 Launch on Sept. 8th

Today’s focus for this area, will be around DataContracts, a look into a simple one, as well as working with collections through SysEntryPoint methods, or Operations of service contracts, for DataContracts.

With that, we left of in Part I, with the showing the basic parts that make up a given custom service. This includes: an X++/Xpp class, that represents the logic of exposed business logic through SysEntryPoint tagged methods. Then we have a service node, that is tied to said class, with the ability to turn SysEntryPoint methods into operations. Finally we have a Service Group node, that the new custom service resides in, as a publishing point so the service can be consumed.

Now that we have this base understanding, lets look at what we would most likely be making use of, through such SysEntryPoint service operations.

When you think of Services, and specifically WCF services, then you start to also think in terms of DataContracts. This did not exists prior to AX 2012, however has been a major part and concept of WCF, since WCF was introduced back in .Net 3.0 days.

It’s a similar concept, in that the point of a DataContract is what the name implies, to offer a Contract, with set Properties or Attributes, that govern the interaction of the consumer and the service, for exchanging data. Mouth full huh?

So lets look at what enables a basic DataContract. First, a DataContract is an X++ class. Like the SysEntryPoint metadata tag for service operations, there are several metadata tags that enable a DataContract to exists. These metadata tags, or attribute tags define to AX what the purpose and point of a class, and it’s methods are meant to be.

In turn AX 2012 can use this information, when the times comes to generate the Artifacts that enable the usage of said elements.

So lets look at a simple example. What we will do is create a DataContract class, and set that is has two Attributes or Properties, Name, Account. To do this, we need to create a new class, and within the Class declaration add DataContractAttribute metadata tag, as shown below.

Simply adding that given tag, will now enable this class to be used as a DataContract within AX 2012 and outside of AX 2012, when being exposed as part of a Service Operation.

Since we need to attributes, lets now take and add two class scope, private variables to the class declaration of our new DataContract.

Now that we have our class context, private Str variables, we can reference these in creating our attributes for the DataContract, as shown below.

You will notice that for each of these, we have to declare the give methods as DataMemberAttribute, so that for the given generation of the WCF Artifacts and WSDL, AX can know which methods on the DataContract are meant to act as such, and which are not.

On this same topic, you will also notice I supplied the Name, and Account in text as part of the DataMemberAttribute tag. The reason I do this, is so that those consumes outside of AX will see these as properties of the DataContract as Name and Account, vs. parmName and parmAccount.

Since properties don’t exist in AX, we make use of the parm method concept that you see in the above pictures.

Now looking at our class from a higher level, we see that we declared the given element as a DataContractAttribute at it’s class declaration, and then each property or DataMemberAttribute is declared using the parm Method concept.

That’s It! Now you have a DataContract that can be used within a given AX Service Operation.

Lets do exactly that, with taking and creating a Service class, a SysEntryPoint that will represent an operation, and have it to where the DataContract is the required parameter of the method signature.

Now, if we took and deployed this as a service, contained within a service group, we would have a service operation called doWork that would require us to pass in the idbDataContract to operate off of.

That’s pretty straight forward and easy huh? What about working with a collection, say a List of DataContracts? Now that is not as well documented yet, however very possible. This is enabled through the use of the AifCollectionTypeAttribute, as shown below.

Now, first thing you should notice is that we can have multiple metadata attributes applied to a given method, using , (commas) to separate the attribute tags. Next this AifCollectionTypeAttribute is an animal of it’s own, lets me say that.

So what we are doing here is declaring the Parameter Name that will be used as part of this collection. Second, we are declaring the type of the parameter, which happens to be a class and finally we are telling AX what will live in this list, which happens to be our idbDataContract we created earlier.

The idea that this whole AifCollectionTypeAttribute enables, is because of the fact that X++ is not a strongly typed language, however when working with collections we have to give a strongly type collection. This is what we are doing when we work with the AifCollectionTypeAttribute. We are giving the generator of the artifacts a way to describe and create for use by external consumers, to interact with collection types, from X++.

So there you go, we now know how to take and create a basic custom service, a data contract and work with a collection of data contracts within AX and to expose that to the outside world.

My part of this series, I will show how these are called from within AX and outside of AX, and look at the differences and some other important supporting information in this area.

I hope you can see too, that this is the build up that we first touch upon as the vision some years ago in this post, Microsoft’s strategy and vision for Dynamics AX and SOA, and one that we have been covering ever since.

That’s all for now, check back soon as more to come! Till Next time!

"Visit the Dynamics AX Community Page today!"

Continue Reading:
Microsoft Dynamics AX 2012 – A Dive into Services, Custom Services (Part II)

What is the vacant period? Well, the SAP code is looking at the date when the device was installed and the validity periods of the contracts for that installation. In the case of the migration contract, it is not using the move-in date for that contract but it is using the legacy move-in date for that contract. Then if there is a vacant period which overlaps the base period the system basing the estimate on, the vacant period is subtracted from the whole base period. In other words, SAP considers that in a vacant period the consumption is zero.

So next time you cannot explain the way SAP calculated an meter reading estimate it can be worhwhile to check this side of the estimation equation.

If you are having an interest in SAP IS-U you can check out my sap-isu community at http://www.sap-isu.net .

Originally posted here:
SAP ISU: Legacy Move In Date on the contract