ABAP_to_the_Future

Backend Tasks: Creating the Model Using SAP Gateway 13.3
To start, you may have heard it said that talking to yourself is a sure sign of madness.
Given that logic, then, your SAP system needs to be mad in order for any
SAP Gateway services to work. You’re going to set things up so that your system
can indeed talk to itself if it so desires.
First, you need to set up a system alias, which is a human-friendly name for the
RFC destination (SAP system) where SAP Gateway lives. In this case, LOCAL means
that SAP Gateway is installed and running on the same SAP ERP system where the
business data lives, as opposed to some separate hub system.
The system alias is set up via the IMG. You know that IMG menu paths tend to
change frequently, so the path in this example won’t look like the one in your system,
but if you do a search for “system alias”, then you should find some entries
called Manage SAP System Aliases and from there be able to create an entry
called LOCAL to connect to the current system (Figure 13.12).
Figure 13.12 Creating a System Alias
In Figure 13.12, on the left of the screen, select some boxes to say that your SAP
Gateway system is installed locally and not on a hub (so you don’t need an RFC
destination to reach that hub). On the right of the screen, enter the details of the
system (system ID and client number) where the SAP Gateway system resides,
which is the same as the system in which the SAP data lives.
Figure 13.13 SAP Gateway Configuration Settings
You’re halfway there; there’s one more configuration setting needed to enable
your SAP system to talk to itself. In the IMG, navigate to SAP NetWeaver 폷 Gateway
Service Enablement 폷 Backend OData Channel 폷 Connection Settings to
SAP NetWeaver Gateway 폷 SAP NetWeaver Gateway Settings . (What a nice,
simple path to follow.)
575