Downtime Announcement: Please note the SAP Community Wiki will be unavailable due to a system upgrade on Thursday, September 24th between 6 and 7 AM CEST
Skip to end of metadata
Go to start of metadata

To ensure successful service deliveries including the Integration Repository, the following prerequisites have to be fulfilled.

282126_MultipleChecklist_R_blue.pngRelease Dependency

Import using Excel Template

If you like to use the Excel Template for importing interface information into Integration Repository, Solution Manager on SP05 or higher is required.

Value Helps for Interface Attributes

To make full use of the value helps which are available for most attributes it is necessary to have RFC TMW or READ destinations in place to the managed systems which contain the source data.

Interface Search and Mass Maintenance

For using the Interface Search and Mass Maintenance app, SP09 or higher on Solution Manager is required.

Import Interface from SAP PI/PO Enterprise Service Repository

To use the integration of SAP PI/PO Enterprise Service Repository, SP03 or higher on Solution Manager is required.

Integration Directory of SAP PI/PO 

To use the integration of SAP PI/PO Integration Directory, SP10 or higher on Solution Manager is required.

Interface Discovery for IDoc

For using Interface Discovery for IDoc, SP08 or higher is required. In addition, the Managed System which is used for the extraction needs to be on ST-A/PI 01T_731/700 SP01 or higher and ST-PI 740/700 SP09 or higher.

Interface Discovery for qRFC

The technology qRFC in Interface Discovery is available since SP08 of Solution Manager. On the Managed System used for the extraction, ST-A/PI 01T_731/700 SP01 and ST-PI 740/700 SP09 is required. Furthermore, the note 1042040 needs to be implemented in the Managed System.

Interface Discovery for Web Service

The technology Web Service in Interface Discovery is available as standard since SP10 of Solution Manager ( Downport available for SP08 and SP09 ). On the Managed System used for the extraction, ST-A/PI 01T_731/700 SP01 is required. Furthermore, the prerequisite notes needs to be implemented in the Managed System and Solution Manager ( SP08, SP09 ).

Interface Discovery for RFC using Unified Connectivitiy

The technology RFC in Interface Discovery is available as standard since SP11 of Solution Manager. On the Managed System used for the extraction, ST-A/PI 01U is required. Further, the managed system should be on SAP_BASIS 740 SP5 or above.

S/4HANA ATC Check using Custom Code Analysis

If you plan to use the S/4HANA ATC Check from Custom Code Analysis, a system with SAP_BASIS 751 or higher is required.

Notes

The following notes have to be implemented in Solution Manager / Managed System.

Solution Manager

SP112912923 - INR: Collective Note for Integration Repository SP11
SP102912869 - INR: Collective Note for Integration Repository SP10

SP09

2937680 - INR: Collective Note for Integration Repository SP09

SP08

2833165 - INR: Collective Note for Integration Repository SP08

2800542 - INR: Excel Export for Interface Discovery

SP07

2664328 - IFDOCU: Interface Details changeable although read-only authorization provided

2668114 - IFDOCU: Import in Solution Documentation returns "Error while saving of attribute values"

2800542 - INR: Excel Export for Interface Discovery

2557971 - INR: Downport of Integration Repository Tools to SP07

SP06

2592191 - Advance Corrections IFDocu SM 7.2 ST720 delivered with SP07

2664328 - IFDOCU: Interface Details changeable although read-only authorization provided

2668114 - IFDOCU: Import in Solution Documentation returns "Error while saving of attribute values"

SP05

2592191 - Advance Corrections IFDocu SM 7.2 ST720 delivered with SP07

2668114 - IFDOCU: Import in Solution Documentation returns "Error while saving of attribute values"

Managed System (ST-A/PI)

01U_700 / 01U_731 SP 0

1042040 - extended qRFC monitoring

2936751 - INR: Collective Note for Interface Discovery (ST-A/PI 01U SP00)

01T_700 / 01T_731

Valid for Support Packages

01T_700

01T_700
SAPKITAB7V
SAPKITAB7W

01T_731

01T_731
SAPKITAB9V
SAPKITAB9W

1042040 - extended qRFC monitoring

2769657 - INR: Interface Discovery for IDoc

2799079 - INR: Enhancements for Interface Discovery for IDoc

01T_700 / 01T_731

Valid for Support Packages

01T_700

SAPKITAB7X

01T_731

SAPKITAB9X

1042040 - extended qRFC monitoring

2877574 - INR: Collective Note for Interface Discovery (ST-A/PI 01T SP03)

Only valid with SAP Basis 740 SP11 or higher

2920553 - INR: Collective Note for Webservice Discovery (ST-A/PI 01T SP03 and SAP_BASIS 740 SP11 or higher )


Authorizations

 

The Interface Documentation can only be accessed if appropriate authorizations are available. This includes the authorizations to view and maintain Solution Documentation itself. 

Please use template user BPO_ADM_<SID> to have authorizations to Solution Documentation in your Solution Manager. In addition, user needs authorization to the Function Module RFC_READ_TABLE with authorization object S_RFC and activity 'Execute'. This is used for fetching value helps in Integration Repository.

Customer Attribute Maintenance

In order to enable maintenance of custom-specific content your user must have authorization S_TCODE with value AGS_DCM_CUST_IFDOCU in Solution Manager. This authorization is assigned to standard roles SAP_SM_SL_ADMIN and SAP_SM_SL_EDIT_BPMN.

Integration Repository Tools

Role SAP_SM_BPOINR_DISPLAY has to be assigned for display of Integration Repository Tools. This is valid for Solution Manager SP11 onwards. 

Role SAP_SM_BPOINR_EXE is needed for executing Integration Repository Tools in Solution Manager SP11 onwards.

Import Interface from SAP PI/PO Enterprise Service Repository

The user must have at least authorization SAP_XI_DISPLAY_USER_J2EE to be authorized to call the ESR from Solution Manager.

Integration Directory of SAP PI/PO 

For the RFC destination from Managed System Configuration in Solution Manager, the user maintained in the SM_*_READ destination to PI/PO must have authorization S_RFC with function module SXMS_PF_GET_AUDIT_DATA_AGG assigned.

Interface Discovery

From ST-A/PI 01U SP00 onwards, Authorization Object SM_BPM_DET is needed for access to Interface Discovery. Please check under below technologies for more details on the authorization. 

All the necessary authorizations needed for ST-A/PI 01U SP00 onwards are included in role SAP_BPM_INT_DIS for access to Interface Discovery .

Technology IDoc

  • From ST-A/PI 01U onwards, for the authorization object SM_BPM_DET, field values APPARA_MS = INR and OBJECT_MS = IDOC_DISC are required.

Technology qRFC

  • To execute the steps for qRFC discovery, Developer authorization is required ( S_DEVELOP ). 

  • From ST-A/PI 01U onwards, for the authorization object SM_BPM_DET, field values APPARA_MS = INR and OBJECT_MS = QRFC_DISC are required. 

Technology Web Service

  • From ST-A/PI 01U onwards, for the authorization object SM_BPM_DET, field values APPARA_MS = INR and OBJECT_MS = WS_DISC are required.

Technology RFC using Unified Connectivity

  • From ST-A/PI 01U onwards, for the authorization object SM_BPM_DET, field values APPARA_MS = INR and OBJECT_MS = RFC_DISC are required.

Service Activation

Services to activate in transaction SICF in Solution Manager

BSP_IFDOCU_MM 

Interface Search and Mass Maintenance

WDA_AGS_DCM_EXT_IMPORT

To import interfaces to Integration Repository

AGS_DCM_IFDOCU_SRV

Odata Service for Integration Repository:

Then go to transaction /n/IWFND/MAINT_SERVICES and assign system alias "LOCAL_SM" to service AGS_DCM_IFDOCU_SRV

AGS_DCM_INR_SRV

Odata Service for Integration Repository for Solution Manager SP10 onwards:

Then go to transaction /n/IWFND/MAINT_SERVICES and assign system alias "LOCAL_SM" to service AGS_DCM_INR_SRV


283290_Low-throughput_R_blue.pngTool Specific 

In order to check the prerequisites and execute the service preparation, remote access to Solution Manager and the relevant Managed Systems is required.

Import Interface from SAP PI/PO Enterprise Service Repository

The PI/PO system to be used has to be configured as Managed System in Solution Manager.

In addition, you have to provide an HTTP destination to the relevant PI / PO system in transaction SM59. This HTTP destination must follow the naming convention SOL_DIR_ESR_<SID> with <SID> as the extended system ID of the PI / PO system. Provide the Target Host and the Service No. of the system, and enter /rep in the Path Prefix field of the destination. Finally, enter basic authentication data (user and password). 

Integration Directory of SAP PI/PO 

The SAP PI/PO system must be connected to the Solution Manager as Managed System and RFC destinations should be maintained

There must be a Logical Component Group including the PI/PO system in system role „Production System“ of the solution-branch combination you plan to use. 

You need two HTTP Connections to External Services which targets the PI system. The first HTTP destination should target the PI/PO ESR. Please use the description above from the ESR integrationIn addition, you need a second HTTP destination without any path prefix and where Basic Authentication is maintained. This HTTP destination to External Server should follow this naming convention: SOL_API_<system id>. 

Logical Ports must be created in Solution Manager to connect to the different Web services of the PI/PO system. The required logical ports depend on the PI/PO installation type. For more details on creation on Logical Ports, please check here.

List of Web Services used:

    • Dual Stack installation
    • SenderAgreementIn 
    • ReceiverAgreementIn 
    • CommunicationChannelIn 
    • ReceiverDeterminationIn 
    • InterfaceDeterminationIn
    • IntegrationProcessIn 
    • JAVA-only installation
      • IntegratedConfigurationIn 
      • CommunicationChannelIn

Before importing the interfaces using Solution Administration Import, you need to create Logical Component Groups for all senders and receivers.

Interface Discovery for Web Service (SP10 onwards)

SAP Basis on the managed system should be 740 SP11 or higher

Interface Discovery for RFC using Unified Connectivity (SP11 onwards)

UCON should be set to active in the managed system. For more details on setting up UCON, please check this.

S/4HANA ATC Check using Custom Code Analysis

As the legacy ECC system (in most cases) and Solution Manager are not on this SAP_BASIS level, we propose to use any available S/4HANA instance as hub system. This could be a sandbox instance available in your landscape.

The hub system needs to be connected via RFC to the to-be-scanned system. In addition, the hub system should be configured as Managed System on Solution Manager to enable data transfer of the ATC results.

In the hub system, we need access to transaction ATC to create run variants, schedule the run and access the results. On the to-be-scanned system, we need access to transaction SCI for creating the object set which will be scanned in the ATC run.

Further information is available on this SAP Blog.

Integration in SAP Readiness Check 2.0

Please refer to the blog to find details about Integration topic in SAP Readiness Check 2.0.

  • No labels