3. Defining the RFC Destination in SAP

3. Defining the RFC Destination in SAP


For the e-commerce system to be able to write data in SAP, the RFC destination must be defined. This is a proprietary SAP interface for communications between SAP systems and external programs, such as ONIBEX's E-Commerce system. That is, data transactions are not limited to obtaining data from the server, but records can also be inserted; SAP can act as either Client or Server in an RFC call.


In order to configure the RFC in SAP, you need to know several parameters of the Web page to which you will be exchanging information, such as: URL, Port,  RFC type, route, version of the protocol to use, etc.


ROUTE: IDOC Interface / Application Link Enabling (ALE) > Communication > Create RFC Connections

T-Code: SM59


When accessing this transaction, the following screen will appear:



Figure-5 T-Code SM59 Initial Screen

Click over the HTTP Connections to External Server or Type G folder, and then press the “Create New” icon to create a new entry. The RFC Destination screen appears as shown in Figure-6.

 


Figure-6 Fields necessary to establish communication.


Then fill in the boxes in red:


  1. RFC Destination. – Type in the target system ID, in this case: ECOMMERCE


  1. Description 1.- Short text to describe what the connection is about: E-Commerce Portal.


  1. Target Host. –IP address of the server in which the E-Commerce Portal is installed.


  1. Service NO.- Port used for communication: 80



  1. Path Prefix: Path where the app is located: /demos/CUSTOMER/api/




Figure -7 RFC Destination screen filled in with typical data 


In the following tab, the configuration is left as shown in Figure-8:



Figure-8:    Logon & Security tab


Finally, the Special Options tab should look as shown in the following Figure-9:



Figure-9: Special Options tab

Lastly, test the communication to verify if the E-commerce backend responds to SAP, for this click on “Test Connection”.  If communication is successful, the following screen should be displayed:



Figure-10 Screen with successful connection test with external system.





    • Related Articles

    • 4. Port definition for iDoc processing in SAP

      Along with the previous two sections of Logical Distribution Model and RFC Destination Definition, a recipient port must be configured for iDOC processing. iDOCs are standardized documents like EDI (Electronic Data Interchange) documents that SAP ...

    • 5. SAP Partner profile definition idocs

      To proceed with this part of the configuration, the logical system definition in SAP and port definition for iDoc processing in SAP must have been previously defined since next steps are configuring the different types of messages as shown in ...

    • 2. Logical system definition in SAP

      ALE ensures a distributed but integrated SAP installation. To implement the distribution of business application processes, one needs to build a complete Logical Distribution Model of the system. Within the framework of this configuration, it is ...

    • 15. Complete SAP Object List Specification

      In the previous sections of this systems integration series, iDOCs were already defined in a more non-limiting explanatory manner. This article defines the lists of messages, programs, functions, web services, and in general all improvements to the ...

    • Convertir pedidos con ALFANUMÉRICOS a Pedidos confirmados en SAP

       Ir al Pedido con AlfaNúmerico En la sección de ESTADOS cambiarlo primero a al ESTADO (1) "Pendiente Revisión" Después, cambiar al siguiente ESTADO (2): SOLICITUD De esta manera, el pedido en automático es confirmado en SAP y se convierte de forma ...