OSS Note Reply - It is By Design ?

In BPC you may encounter the need to do currency conversion by business rules.  In the Net Weaver Platform when using business rules, SAP delivers a program for currency conversion.  It is indeed a good program and gives great flexiblity to customers that want detailed control over currency conversion and currency effects on forecasts.

In the Microsoft Platform and even in the Net Weaver platform there remains standard script logic forms of currency conversion, but in many cases this is significantly limiting.

In our planning scenarios we often encounter plans that have 15 month rolling plans or other planning features that  span fiscal years or calendar years.  For example we might have planning for January to December for 2011 and also include the first three months of 2012.  As the months roll by we add a new month of forecast to the plan so we are often if not always entering LC in periods that are in two different years.

In our default logic we want currency conversion and in the case above using business rules, the system simply is built to ONLY convert the LOWEST NUMBERED year and its related time periods.  SAP says this is by design.  The work around is a performance hit relative to a better approach.

We say, yes it may be by design but as is often the case with SAP development, the design makes no practical business sense and limits customer use of the business rules process and code.

We urge SAP to not simply reply to notes with "it is by design" but also consider the design as perhaps meaningfully flawed in real world applications.

The currency conversion program in Net Weaver that engages currency conversion and business rules use is by design flawed.