This page is not a part of an official Int4 documentation.
Knowledge Articles

Configure SAP PI/PO Environments and RFCs

Configure Development and Production Environments for SAP PI/PO Connectivity

Those activities should be done by Security Expert or Basis Expert

 

  1. Create the development RFC destination (Type G)

0f52a679a5df4d22924737f4df73404b?workflows_screenshot=true
  • Go to transaction SM59.

  • Create a new destination of type G (HTTP connection to external server).

  • Name it according to your naming convention for the environment.

  • Enter the required:

    • Host

    • Port

    • User used for authentication

    • Path should remain empty

  • Save the destination.

  • Run a connection test to confirm the technical connection works.

image-20260521-111537.png


This test checks connectivity, not user authorization.


 

  1. Add the development environment in the configuration app

image-20260521-084531.png


  • Open the Fiori Launchpad.

  • Go to the Configuration application.

  • Use Find Environment and create a new environment entry.

  • Enter:

    • Environment name for development

    • Description

    • Select the relevant checkbox for the SAP PI/PO setup

  • Save the entry.

  • Return to the configuration wizard and confirm that new environment-specific options now appear.

 

  1. Assign the development destination and verify connectivity

cce0d727427748b594e074988d59435a?workflows_screenshot=true
  • In the wizard, open the development environment setup.

  • Click Customize.

  • Select the previously created RFC destination from the list.

  • Continue and run the connectivity check.

  • Confirm the status is green.

  • Repeat the check for any remaining development-related entries.

  • Use Check Connectivity to verify all selected entries return a successful ping.

 

  1. Create the production RFC destination (Type G)

9ec5b13695604ebdab0cddc22803fdcc?workflows_screenshot=true
  • Create another Type G RFC destination for production.

  • Follow the same naming convention, but use the production identifier.

  • Reuse the same host and port if there is no separate production system.

  • Switch to the security/properties section.

  • Maintain the user and password for production access.

  • Save the destination.

 

  1. Add the production environment in the configuration app

image-20260521-084900.png


  • Go back to Landscape Configuration and Define Environments.

  • Create a second environment entry for production.

  • Enter:

    • Environment name for production

    • Description

    • Select the relevant SAP PI/PO checkbox

    • Enable the Production checkbox

  • Save the entry.

  • Return to the configuration wizard and confirm the production-specific settings now appear.

 

  1. Assign the production destination and validate it

  • image-20260521-085145.png

    In the wizard, assign the existing production destination.

  • Run the connectivity check.

  • Confirm the response is successful.

  • For production, only the essential activities are needed:

    • Maintain logical port for PI/PO API web service proxy /INT4/CO_IFTT_ADAPTER_MSG_MONI

    • Maintain logical port for PI/PO API web service proxy /INT4/CO_IFTT_INTEGRATED_CONFI

    • Maintain logical port for PI/PO API web service proxy /INT4/CO_RECEIVER_DETERMINATIO

  • Verify connectivity for each required item.