ERPCorp SAP FICO Blog

Our blog series on the most common SAP Controlling pitfalls and how to avoid them continues this week. SAP Controlling 2013 speaker Paul Ovigele discusses the most common pitfall is from his perspective.

The Controlling Profitability Analysis (CO-PA) module has been around about 15 years, and its original purpose was to enable businesses to produce market segment profitability reports predominantly based on sales data. It is particularly useful to users in the Finance and sales departments as it allows you to perform profitability analysis according to several dimensions (customer, product, country, salesperson etc.) and its real-time functionality aids quick and effective decision making. However, one pitfall of the Controlling module is the inability to automatically reconcile the CO-PA module with the General Ledger.

This week we are starting a new blog series on the most common SAP Controlling pitfalls and how to avoid them. SAP Controlling 2013 speaker Tanya Duncan is up first.

In my opinion, the most common Controlling pitfall is choosing design alternatives without understanding the ramifications. Controlling is an interesting and, in my opinion, more fun module compared to Finance and other SAP modules. It is more flexible in how you achieve requirements, but it also requires attention to building a robust, sustainable design.  

Our blog series on the most common SAP Controlling pitfalls and how to avoid them continues this week. SAP Controlling 2013 speaker Martin Munzel discusses the most common pitfall is from his perspective.

A common error I have found in companies using SAP CO is that they were trying to make some of the submodules do things they are not designed for.