This guide walks you through connecting your SAP system through Makini Link.
Set aside about 15 minutes once your SAP Basis team has set up the user. This connection works with SAP ECC and S/4HANA systems that you run yourself. You'll need your SAP system's connection details, the client number, and an SAP user for Makini.
Nothing needs to be installed in SAP. Makini only calls standard function modules (RFCs and BAPIs) that SAP ships with every system. There's no transport to import and no custom code to add.You'll need your SAP Basis team. They create the user, give it the right authorizations, and know your system's connection details. If that isn't you, send them this guide.Use a user made just for this connection. Everything Makini reads, it reads with this user's authorizations, and anything it changes in SAP is recorded under this user. A personal login mixes your own activity with the connection's, and the connection stops working when that person leaves. A dedicated user avoids both.Most SAP systems sit on your own network. If your system can't be reached from the internet, you'll turn on Connect to on-prem system via VPN/Firewall on the same form in Step 3. Have your network details ready, or your network team nearby.
Ask your SAP Basis team to create a user for Makini in the client you want to connect, and give it:
RFC authorization (S_RFC) for the function groups Makini calls
Table display authorization for the tables Makini reads
HR (personnel) tables are authorized separately in SAP, and many companies choose not to grant them because payroll data sits in the same tables. That's fine: if the user can't read them, the connection still works without them.Keep the username and password somewhere safe for a moment. A password manager is best.
Your Basis team already has these written down. You need:
How to reach the system. Makini accepts the same notation SAP GUI and SAP's own connection files use:
a host name, for example sap.example.com (instance number 00)
a host name and instance number, for example sap.example.com:01
a host name and gateway port, for example sap.example.com:3201
a SAProuter string, for example /H/router/S/3299/H/sap.example.com
a message server and logon group, for example /M/sap.example.com/S/3601/G/PUBLIC
or the system's web address, for example https://sap.example.com:44300. Use this only if the /sap/bc/soap/rfc service is active in SICF on your system.
The client: the three-digit SAP client number that holds your data
Encrypted RFC: whether your SAP gateway requires SNC. Most don't. If yours does, ask for the SNC name of the SAP server.
SAP server: the connection details from Step 2, exactly as your Basis team wrote them
Client: already filled in with 100. Change it to your client number if it's different, and keep any leading zeros.
SAP user: the user from Step 1
Password: that user's password
2.
Under Advanced settings there are two optional fields:
Logon language: set to English by default. It decides which language descriptions and other texts come across in, so pick the language your team uses in SAP.
SNC name of the SAP server (only if your gateway requires encrypted RFC): leave it empty unless your Basis team told you SNC is required. If it is, paste the SNC name they gave you.
3.
If your SAP system isn't reachable from the internet, turn on Connect to on-prem system via VPN/Firewall and fill in your network details.
