Scribd
Upload
1 views

IES Configuration

The document provides a step-by-step guide for configuring RFC destinations and creating IES services for inbound and outbound communication in SAP. It includes instructions for setting up connection parameters, defining authorization roles, and testing services to ensure proper functionality. Additionally, it emphasizes the importance of manually maintaining connection parameters on each client and activating the capture profile in the OpenText Vendor Invoice Management Foundation.

Uploaded by

harshitkumar11102002
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
1 views

IES Configuration

The document provides a step-by-step guide for configuring RFC destinations and creating IES services for inbound and outbound communication in SAP. It includes instructions for setting up connection parameters, defining authorization roles, and testing services to ensure proper functionality. Additionally, it emphasizes the importance of manually maintaining connection parameters on each client and activating the capture profile in the OpenText Vendor Invoice Management Foundation.

Uploaded by

harshitkumar11102002
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 16

SAP Configuration

Creating RFC Destination (Outbound communication using HTTP)

1. Go to t-code: SM59 to configure a new RFC connection.


2. Create a new RFC destination of type G (HTTP Connection to External Server).

Header parameters

 RFC Destination: Technical ID of the connection


 Connection Type: Choose type G.
 Description: Enter a description for the connection.

Technical Settings tab


 Target Host: Full qualified host name of the IES service
 Port: Port of IES service which should be used to retrieve requests.
Special Options tab

 Timeout: ICM Default Timeout


 HTTP Version: HTTP 1.1
 Compression: Inactive
 Compressed Response: Yes
 Accept Cookies: No
Save your settings.

4. Run a connection test using the corresponding button in the application toolbar.
The test result should include status HTTP response 200.
Creating IES services – IESREPO and IESRESULT (Inbound Communication)

1. Run the PFCG transaction to create a role for processing inbound requests from IES.
a. Define authorization for object S_ICF (Authorization Check for ICF Access) with the
following values:
 ICF_FIELD: 'SERVICE'
 ICF_VALUE: 'OTBCINB'
b. Add the authorization for the J_6NPF_RFC object (BC RFC calls) with the values: ACTVT:
'03'.
c. Save and generate the role.
2. Run the SU01 transaction to create a user of type Service for processing inbound requests
from IES and assign the authorization role defined in Step 1.
3. Run the SICF transaction to create services for processing inbound requests from IES.

Note: Do not change any values on the selection screen and press the execute button to get to the
service maintenance screen. Services are created below a virtual host.

For example, default_host. Align with your SAP basis administrator where to create the services for
inbound requests from IES.
4. Create a new service for repository requests of type Independent Service. For example,
IES_REPO.
a. On the detail screen of the service, open the Service Data tab and define the SAP
authorization OTBCINB.
b. Switch to the Logon Data tab and set the procedure to Required with Logon Data. In the
logon data section, define the user name and the password of the service user created in
Step 2.

c. Switch to the Handler List tab and define class /OTX/PF12_CL_SERVICE_ HNDL_REPO as
handler with order number 1.
Note: If prompted for a package, select local object, or provide a valid package name.

d. Activate the service and test it.


When testing the service, an HTTP 400 error with message ‘“Failed to load resource: the
server responded with a status of 400 (Request method GET not allowed)” should be
displayed in a browser window. This is the correct reaction because the handler class
blocks HTTP GET requests. If this message is visible, the configuration of the service is
correct, and the handler class is invoked.
5. Create a new service for result requests of type Independent Service. For example,
IES_RESULT.
a. On the detail screen of the service, open the Service Data tab and define the SAP
authorization OTBCINB.

b. Switch to the Logon Data tab and set the procedure to Required with Logon Data. In the
logon data section, define the user name and the password of the service user created in
Step 2.
c. Switch to the Handler List tab and define class /OTX/PF11_CL_SERVICE_HNDL_RSLT as
handler with order number 1.

d. Activate the service and test it.


When testing the service, an HTTP 400 error with message ‘“Failed to load resource: the
server responded with a status of 400 (Request method GET not allowed)” should be
displayed in a browser window. This is the correct reaction because the handler class
blocks HTTP GET requests. If this message is visible, the configuration of the service is
correct, and the handler class is invoked.

Connection Parameters

Note: Connection parameters are client-dependent and are not transportable. Therefore, we need
to maintain connection parameters manually on each client which we want to connect to IES.

1. Go to t-code: /n/OTX/PF00_IMG and navigate to the below path,

OpenText Vendor Invoice Management Foundation  Inbound Configuration  Capture 


Information Extraction Service  Connection Parameters

2. On the Global Settings Overview screen, define connection parameters with following keys,
Note: To know the host name and port, go to t-code: SMICM and click on Services

3. Double-click Connection On-premise in the Dialog Structure. On the Connection Overview


screen, create a new entry.

Use the following parameters:

 Connection ID: Technical ID of the connection to IES


 Destination: Technical ID of the RFC destination to IES
 SSL Enabled: Select this check box if SSL should be used for the request sent from IES to SAP.
 URL Path Repository: Enter the path to the service for inbound repository requests
configured in.
Note: Do not forget to start the path with a leading slash (/).
 URL Path Result: Enter the path to the service for inbound result requests configured in “On-
Note: Do not forget to start the path with a leading slash (/).

Save the settings and return to the VIM Foundation Configuration


4. Navigate to OpenText Vendor Invoice Management Foundation  Inbound Configuration
 Capture  Information Extraction Service  Connection test.

5. Execute a connection test for the connection ID that was created in the previous steps. The
result screen should show that the connection test for all 3 services was successful.
Activate the profile:

Navigate to OpenText Vendor Invoice Management Foundation  Inbound Configuration 


Capture  Information Extraction Service Capture Profile Activation

Click on the highlighted button (Activate) to activate the profile.

You might also like