Testing protocol ZCRQ 119868 / Issue 126 correction/adjustment to the

BRFPlus application used for high-level configuration inside the TCT

Background

The ZCRQ request above was placed to request a modification to the BRFPlus
application used by BWTS for the Turbo Customizer Tool (TCT) application inside SAP.
The modification involves creation of two new high-level logic controls (decision
tables) which each set the value of a specific characteristic used to select the
correct variant for the turbine housing volute in a TCT application model.

The set value in the third characteristic is later used by TCT configuration
automation during the application of the filter values to the configuration structure
(i.e. configuration explosion). In the original solution concept which will be tested
here, both of the new controls are identically structured in terms of inputs
characteristics and values, although each outputs to a different /separate output
characteristic and value.

The process flow chart shown below may be used as a shorthand explanation for the
concept as it was (thus far) realized within the SAP DU1 system.

Thus the plan requires a decision table

Characteris
tic 1 Value which allows columns for each of the
- Input
characteristics names as well as the
Characterist values which lead to the selection of a
ics 3/4 particular third characteristic name +
Value -
Output value (in total 6 columns per table).

Characteris
tic 2 Value
The reason why two separate decision
- Input
tables were created was simply to track
the different processes separately since
both affected output characteristics utilize the same two input characteristics. Thus,
for the purpose of ease of finding and separating one set of directing values
(characteristics 3 and 4) from the other, we simply created two tables. Although
theoretically, from a functional standpoint, the contents of both tables together with
their outputs could have been stored in one large single decision table.

From the original documentation provided to us by the requestor, Alexander

Umlauff, we needed to create the following columns as inputs and outputs within the
new decision tables based on the following example layout.

The first input characteristic is the P-Family of the turbine wheel itself. New P-
families are created by core science matching on an as-needed basis when existing
thermodynamic contours and volutes need to be optimized. The characteristic
which has been used up to now to specify the TW P-family is TSWP01.
 The second input characteristic is the D5
diameter characteristic for a turbine wheel.
The D5 diameter characteristic used within
the TCT application up to now was / is
TSD503.

The other two columns which appear in the

two tables above B_Base and D_CME
represent the output characteristics of each
of the two decision tables. The meaning of
these two characteristics is shown in the
illustration below

B_B (B_Base) refers to the gap between the end of the blade flat and the surface of
the interior of the housing and D_CME refers to a diameter drawn circularly from
within the blade of the wheel. Both of these characteristics needs to be specified as
well in order for a standardized TH contour to be identified/found.

As a result of the requirement, two new characteristics were created in DU1 using
CT04. These were TSBB01 and TSDC01. Below are screenshots of the newly
created characteristics
and

Within BRFPlus, the following objects were created

The following BRFPlus decision tables were created to support the new high-level
process

The decision tables will be used to make a determination about the values used and
to be set in characteristics TSBB01 and TSDC01. The structure of one of the two
decision tables is shown below

Because the elements Char_DERIV and Value_DERIV already existed before this
change was started (and were actively used in the decision table DT2_Derivation_1),
there was no need to create additional new output characteristic elements. The two
output characteristic elements were used instead in the step coming after the
decision table (within the rule). Details for how this build in to the existing rule flow
is shown below
and the new decision tables were called out in rules as shown below

It should be noted that the instructions for insertion in to the structure Result-
LT_Derivation_Out after processing of the new decision tables use exactly the same
format/procedure as the existing rule for decision table DT2_Derivation_1 and thus,
the selected characteristics and values should follow the same path and automation
as existing automation (no new programming needed).

Test data was added to both of the two decision tables and the VIEW_CLUSTER
customizing used for the application UI was updated using SE54 to display the new
characteristics within the others area of the application UI for both the wastegate
and VTG characteristic layouts of the TCT.
Within the PSM structures themselves, changes were also made to allow testing and
verification of the concept to proceed. The changes were made using change
master ID 990000001363. This change master includes the objects shown below (as
of testing)

Thus we see that a new structure node for turbine contours has been added (this
was added based on a separate standard structure change to add contours which
needed a new characteristic). The values used to select the contour will also lead to
the selection/setting of the two new characteristic values which will (in turn) lead to
the selection of a turbine volute. The entire process flow is shown below in the table
from Alexander Umlauff
Thus we needed to set up regular dependencies on variants which use the new
characteristics as selection criteria (hopefully will be pulled from others). The
changed/added dependencies are shown below

With completion of all of the above activities, we should be able to perform a simple
testing in order to verify the following

1. That the new characteristics are displayed properly within the application UI
(based on their area assignments).
2. That the new high-level 2:1 characteristic tables function as they are
supposed to do (i.e. when characteristics are set, then the derived
characteristic and value are set in the others area as this should take place).
3. That the new LL dependencies work as they are supposed to for both the
volutes and turbine contours structure nodes, and assigned variants are found
correctly (utilizing the new characteristic TSHS01 spring/direct force [N]).

If these three tests are successful, then a further transport in to the QU1 system will
be requested. In addition, we will set up a meeting and demo the functionality with
Alex and ask for more exact definition information regarding the new characteristics.

Testing

We start testing by opening the application UI for the model WASTEGATE_PC and
checking the layout of the characteristics there.
and then

and then

and then

From within the application UI, we select the model for wastegate turbochargers
If we look at the application UI more closely, we see the following characteristics
displayed as shown

The new spring/direct force on the TW characteristic is shown within the TURBINE
section of the UI, Good!

The two new characteristics B_B and D_CME have been added to the Others
section of the application UI as expected - Good! Now we will test the high-level
changes. Based on the outlined table entries made below, we will attempt to set a
value for the B_B gap characteristic.

First we set TSD503 to 35

Then we set the P-Family characteristic TSWP01 to P28

If we look at the TSBB01 characteristic field in others, we see the following

Ooops! Error! No value was set. Also, when we review the messages section of
the application UI, we see the following

Ooops! Error! No message was sent for the new high-level rule having been
triggered. Thus, it appears as though it is not being triggered at all. We go back in
to BRFPlus to run the new high-level rule set through the simulator in that system

and then
and then we set the input values used in the test just now as test inputs for the
simulation and run it

and then
Whoops! Error! There are two separate result lines which are returned by the
same set of input values. This is not a single result! Maybe this is what caused the
problem. We will delete one of the two lines -

and then

and then we save and activate the changed table.

and then

and then

Good! The change was accepted and activated. We close the previous application
UI web session and reopen it in a new browser window. We open the
WASTEGATE_PC model a second time and evaluate the characteristics as before.
This time, when we check the others characteristics area afterwards, it looks as
shown below
Whoops! Error! It is the same error as before. No value was set. This can either
mean that no values are being detected / loaded in to the decision table in the first
place, or that the output is being blocked or ignored. We return to the BRFPlus
application in DU1 to try another solution.

Inside BRFPlus we try one other solution, we click on the rule we created and click
on the ruleset for the process and click on the check button to see if it is consistent

and receive the following output

Now we can no longer load the application UI at all. Error! The system is
dumping.

We will need to talk with the IT about troubleshooting the problem online within
DU1. Now if we attempt to use the application, we only get DUMPs!