ABAP_to_the_Future

9
BRFplus
ues from the spreadsheet the user gave you, and check that everything is in the
right column.
Some of the decision criteria you want are not fixed values but rather formulas—
for example, early age strength days must be less than or equal to 10. You cannot
achieve this in the IMG tables you used to use to make decisions, but you can
input such values in a spreadsheet, an d BRFplus will recognize them for what
they are. Therefore, before uploading the data back into BRFplus, change the cells
in the spreadsheet when they need to be formulas rather than the X in the spreadsheet.
For example, the X for MOS %age is replaced by >0. The result can be seen
in Figure 9.31.
Figure 9.31 Modified Spreadsheet Ready for Upload
Then, upload the spreadsheet back into BRFplus (via the good old Additional
Actions button), and at once you have the eq uivalent data in the decision table
(Figure 9.32).
The decision table achieves the exact same thing the ABAP code did. However, it
took only a fraction of the time to create, there was no need for a Z table and complicated
code, and there was less capa city for miscommunication—because you
used the spreadsheet you were given by the business expert as a basis for what
you uploaded to BRFplus.
Here comes the icing on the cake: With a decision table, you have two options in
the Additional Actions context menu called Check Completeness and Check
Overlap. The overlap check tells you if any rows in your table will never be chosen
in any circumstances. In Figure 9.33, this occurs twice, because—to your horror—some
of the lines are identical to each other. This is a problem; you have set
the decision table to return only one row, so if there are tw o identical lines that
392