Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

Use/Purpose:

We had a scenerio that the existing Input Ready Query is having thousands of rows which shows the existing planned values and then at the end a Input ready line where new budget plan values can be entered.

For entering any plan values users had to scroll till the end of the Workbook, which they found very difficult.

Hence the Client asked us to show only the Input ready line in the workbook for the same set of query selection.

Proposed Solution:

This involves the below steps

  • Maintain a new value for one of the field which is to be used for the initial query restriction.
  • While saving the planned data, the new value of the field used in the query restriction will get reposted with the original value of the field where data is saved at the back end cube using the standard planning function type - Repost.

Procedure:

The Existing query is having a set of restrictions. One of the restrictions is with respect to the Version Field. This Version Field is restricted with a value “0” for which data is available in the cube.

Now the report shows all the data available in the cube for the existing query selection and the Input ready line at the end.

Now as per the Client requirement we should show only the input ready line, all the existing lines is to be hidden. But when the user plans the values are to be again saved for the same set of selections that are used in the existing query restriction.

For this purpose we maintained one more value for the Version Field, and we restricted the Version field in Query with respect to this new value replacing the existing value.

Now create a Planning function with type repost.

For the Filter restriction to the Planning function, a corresponding planning filter is created.

A planning filter is created with the same set of restrictions used in the query with the Version restriction containing both the existing value “0” and the new value “P”.

Below is the planning function where the From Value is the Initial value restricted at query end and To Value is the value to which the data will be saved in the back end cube.

A corresponding planning sequence is created which contains the respective planning filter and planning function.

Now In the Front End Workbook behind the “SAVE” button the above Planning Sequence is inserted, as shown below.

When the user after planning the data and clicks “SAVE” at the back end the values are reposted from Version – the initial restricted query version to Version – the version of data in the back end cube.

Thus Workbook displays only the Input Ready line though there are huge data in the backend cube for the same selection.

2 Comments
Labels in this area