Академический Документы
Профессиональный Документы
Культура Документы
SAP Analysis for oce is the de-facto tool for spreadsheet-based reporting on Business Objects in Excel. It can also be used for your planning
applications .If you have cubes available in your backend system to planning, then Analysis for Oce also allows for implementing a wide range of
planning scenarios on a report.
Below , we have showcased a planningapplication built with Analysis for Oce report using Input Ready Query in BW using BI Integrated Planning.
Herethe user will be able to select one or several source lines in a data (query) and can execute a predened planning function on these records in
the report. This also allows writing values back to the cube for persisting the data. A step by step process is shown below to showcase how this can
be done.
We will need a input ready query which is then used to build the planning application. Here we have used a simple query on a Planning cube . A
planning cube is a must because only a planning cube will allow write back of data that is required for planning applications.
Key gures which are to be changed/edited in Analysis for Oce must be checked for Input-Ready. Below is the screenshot highlighting the option.
http://visualbi.com/blogs/sapbusinessobjects/biintegratedplanninganalysisforoffice/ 1/6
6/5/2017 BIIntegratedPlanningusingBExQuery+AnalysisforOfficeVisualBISolutions
Key gures which are to be changed/edited in Analysis for Oce must be checked for Input-Ready. Below is the screenshot highlighting the option.
Also, the query should be selected for the object to change it during navigation. There is an option to select this under Query Properties. Save the
query.
Now the Query is all set , we can now go to Analysis for Oce to see how to enable the same.
Go to the Analysis tab and choose Settings -> Advanced Settings. Make sure that the box for planning features is checked.
Open the same query in AO and create a report. Enable the cube for load mode to enable planning
http://visualbi.com/blogs/sapbusinessobjects/biintegratedplanninganalysisforoffice/ 2/6
6/5/2017 BIIntegratedPlanningusingBExQuery+AnalysisforOfficeVisualBISolutions
This results in not being able to perform planning function as shown below
Note: Whenever the Planning Sequence/Planning Function is executed, the Info Provider property should be set to the below shown option
http://visualbi.com/blogs/sapbusinessobjects/biintegratedplanninganalysisforoffice/ 3/6
6/5/2017 BIIntegratedPlanningusingBExQuery+AnalysisforOfficeVisualBISolutions
On doing this, data target is switched to Interactive Planning. On the Analysis Components tab of the report, make sure the data source and Input
Enabled option is checked.
Going back to the Analysis for Oce report, now that planning is possible, edit the key gure values and hit save in Planning Ribbon.
http://visualbi.com/blogs/sapbusinessobjects/biintegratedplanninganalysisforoffice/ 4/6
6/5/2017 BIIntegratedPlanningusingBExQuery+AnalysisforOfficeVisualBISolutions
Record is now transferred to the cube. To check that, go back to the cube and choose rst option in real-time load behavior.
Recalculate
If the base values get changed , then all the changed values get checked for consistency ,if the changed data entries are correct, the recalculated
data is available. The totals are updated and the new values are visible in all other components of the workbook. The recalculation is executed for
all data sources in the workbook that are available in the selected planning system.
The PlanDataTransfer command from the API method SAPExecuteCommand can be used to recalculate planning data.
Save
Once the data is changed and if the changed data entries are correct, it is saved in the data sources and a message is displayed that the data was
saved. The saving is executed for all data sources in the workbook that are available in the selected planning system.
The PlanDataSave command from API method SAPExecuteCommand can be used to save planning data.
Lock Cells
Input-ready crosstab and total cells in Analysis can be locked. A locked cell cannot be changed manually when the crosstab is recalculated. The
locked cells are unlocked automatically on executing a planning function or sequence.
Back
This option undos all changes since the last save of the data. The undo is executed for all data sources in the workbook that are available in the
selected planning system.
PlanDataReset command from API method SAPExecuteCommand can be used to achieve the same.
With this option, you undo all changes since the last successful recalculation of your data. The undo is executed for all data sources in the workbook
that are available in the selected planning system.
The PlanDataClientReset command from API method SAPExecuteCommand can be used to revert to the last recalculated state of your planning
data.
With SAP moving to an embedded Planning model , you can look at implementing these planning functions in your Analysis for Oce workbooks
and move to an embedded BI model which helps in maintaining close alignment with the SAP roadmap. Also because the transaction data and
planning data are available in the same system , it becomes easy to implement these scenarios and make your system landscape leaner.
http://visualbi.com/blogs/sapbusinessobjects/biintegratedplanninganalysisforoffice/ 5/6
6/5/2017 BIIntegratedPlanningusingBExQuery+AnalysisforOfficeVisualBISolutions
Search
http://visualbi.com/blogs/sapbusinessobjects/biintegratedplanninganalysisforoffice/ 6/6