ABAP_to_the_Future

Enhancing Custom Reports with ABAP2XLSX 11.2
the SAP system to respond to incoming messages from the Internet. If a spreadsheet
can send a message via a URL and SAP can respond to such a message, then
you have all the building blocks in place to achieve what’s needed.
In this section, you will kill two bird s with one stone. The primary focus is on
enabling hyperlinks from out of Excel into SAP, but this means that you have to
touch on the basics of using the ICF. In fact, you will learn about setting up the
ICF settings first; the section will end with the ABAP2XLSX coding that you need.
Setting Up the ICF for Hyperlinks
It should not come as too much of a life -changing shock to find out that ICF settings
are made using Transaction SICF. Wh en you run that transaction, you will
see a tree structure, as shown in Figure 11.14, with the headings in an endearing
mixture of English and German.
Figure 11.14 Transaction SICF
In essence, each node in the tree corresponds to a part of the incoming URL, so if
you add a node under the SAP/BC node, then the URL should contain the words
sap/bc. This will become more obvious when you start to build up the URL from
within SAP a bit later.
As it turns out, SAP is expecting you to want to call a transaction from outside of
SAP and has provided a handy home from which you can create a custom service
to handle the incoming call. The path to this service (i.e., what nodes you navigate
to in the tree before creating your own custom entry) is shown at the top of Figure
11.15.
497