View Function: Advanced Tab

former_member639063 · ‎2020 Nov 09

If you are one of the modelers exploring the array of functions offered by SAP Profitability and Performance Management and stumbled upon a seemingly plain function called View; curious of its functionality besides the usual ones such as projection and aggregation – then this blog post is for you.

As view is one of the most straightforward functions offered by the solution, in which I concur. In the sense that: the modeler can simply just indicate an input function with optional input selection criteria, activate and run the function then you will have your desired result projection – in addition to the manipulation that the modeler could do from the output tab. However, as much as these tabs (input and output) are essential, the real-deal can be found in View’s Advanced Tab – wherein I will be focusing on.

For starters, general information about the View function can be read here:

https://help.sap.com/viewer/56471df1959f4cfd9e3bf7a6d2d5be42/latest/en-US/23dc009edd8f4e9594e24c912d...

Pretty basic isn’t it? Now moving to the main topic, the Advanced tab section has the following settings:

Figure A.

Note: The configuration above for Advanced Tab is just a depiction of what kind of input these fields accept.

I will try my best to explain each Advanced tab settings in the next section using simple scenarios that will show their relevance and behavior when properly configured:

Top

This one is pretty direct, by indicating a number or parameter will restrict the output records coming from the input. For example, I have the following input records:

As an additional flavor, I’ve used Order by for both fields in the Output tab.

Interim results without TOP setting:

And finally, results with Top value set to 3:

The result will consider the set ordering and will respect the sequential order of the records coming from the input.

Run Parameter Precondition

For certain requirements that the modeler would need to derive from different data sources for processing, utilizing View’s Run Parameter Precondition is one approach that the modeler can explore.

For instance, I have two data sets: (1) Assumed (2) Actual.

Using Run Parameter Precondition, I can either:
1. Derive nothing (no precondition met and/or set)
2. Derive only from ‘assumed’ model table (:I_PCOND=’assumed’)
3. Derive only from ‘actual’ model table (:I_PCOND=’actual’)
4. Derive from both sources (both precondition was met)
A View function on top of these model tables will do the trick by specifying the precondition for example as shown in Figure A above. These two view functions are then called using From and Union All rules inside a Join function (JO - Data Processing) which serves as the main function to be executed.

To help you imagine what I am talking about, the function tree structure looks like this:

Note: Figure shown is from FS-PER 3.0 Visual Modeler. And for easier reference, I’ve indicated the set Parameter precondition on each View function.

Basically, if Run Parameter Precondition is set in a function View, it’s procedure will be executed only when the set parameter value is satisfied. By setting :I_PCOND = ‘assumed’ as package parameter upon run of JO – Data Processing, results will show data coming from MT – Assumed Data:

And by setting :I_PCOND = ‘actual’ as package parameter, the MT – Actual Data is used:
You might want to also check another blog post citing another scenario wherein Run Parameter Precondition feature was found essential by andrey.fedorin:

https://blogs.sap.com/2020/10/06/sap-profitability-and-performance-management-how-to-manage-sequence...

Default Type

If the Default Type is set to Default Output, if input empty and the input function’s Y-TABLE is empty, the run result will have a one line of dummy record as shown below.On the other hand, if the input function has records, it will be shown as is. Basically, the exact behavior as setting Default (none) which is the normal View functionality.

Iteration

Iteration often referred to as 'looping' is a process in order to generate a sequence of outcomes which function View is also capable. Iteration type have three options: Default (None) the succeeding settings will be grayed out as shown below:

While both For Loop and For Loop Reverse enables the looping capability of the View function. The difference using the latter is that it switches the Low and High effect in the iteration. As for Low and High fields, its values can be set using static integer value or an environment parameter.

To show you that the iteration values can be reused, I’ve assigned the Iteration Parameter I_ITER to an output field ZE_ITERATION.

After successful activation and run, each iteration value are passed on to the output field ZE_ITERATION and shown completely in the image below:

This is just one (of the simplest) example wherein a user can utilize iteration. From repetitive enrichment and calculation to mass data generation, this feature will certainly be of aid for modelers.

As additional reference of Iteration's capability, I’ve added a flowchart showing one View function that performs multiplication of ZE_AMT to the current value of the Iteration Parameter I_ITER, which goes on until the total number of iterations reaches the High value of 3.

Moreover, View can also be used as a caller for a repetitive process and/or enrichment in a chain of functions such as below:

In this scenario, as long as the Iteration logic is satisfied, the View Function will trigger the Writer that calls its child functions until the iteration parameter reaches the High limit set and will end the iteration process. But what if I am already satisfied with the enriched data mid-way before reaching the value I have set for High – which is the upper limit of my set iteration?

A soft-limit that will end the iteration cycle if a certain condition is met is basically how Early Exit Check works and will fulfill this requirement.

Early Exit Check

Another functionality coming from the View’s Advanced Tab is the Early Exit Check. Wherein a condition can be configured in the environment through ‘checks’ which the View function can use as constraint. And once this condition is met, the iteration process will be terminated.

As reference, I’ll be showing a very straightforward example on how Early Exit Check kicks-in and this just one of the many ways to use this specific functionality.

Using the first iteration example from the previous section, I have created a check with condition ZE_ITERATION = 6.

And have set this as the Early Exit Check under the Advanced Tab of the View function:

Upon running of the function, the result shows that the last value of ZE_ITERATION is 5:

As such, this feature will be useful for scenarios that requires a certain condition or fulfillment of a field’s record, without having to rely specifically on the number specified in the Low and High fields for iteration.

If you have noticed in my previous iteration examples, each iteration is being reflected in the results. This is because I have opted to use the All Iterations as the Iteration Result setting, but of course, an alternative is available which I will be discussing in a second.

Iteration Result

Given the general idea for All iterations which is a more transparent option than of its counterpart. For modeling users who prefer to see only the final processing result and do not really care about the full picture, this is where Iteration Result: Last Iteration fit. Once chosen, only the last iteration result will be shown.

I have removed the early exit check from our previous example to make it simpler (similar to our the Iteration section example). As such, the last iteration which is the value of 10 is shown as a result:

As you’ve already reached the end of my blog post, I hope that you’ve learned how SAP Profitability and Performance Management’s View Function – Advanced Tab works and find this helpful with your modeling requirements.

Thank you for taking the time.