Ansicht
Dokumentation
RCOD_CHECK_E2E_CONNECTIVITY - E2E Connectivity Check (please click the i button for further info)
RFUMSV00 - Advance Return for Tax on Sales/Purchases SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Purpose
To check the end to end connectivity from S/4HANA to CFC system.
While setting up the connection between your SAP S/4HANA system to SAP Cloud for Customer system via middleware (HCI or PI) there was no way of doing an automated check before enabling an actual data replication to make sure that the connection settings and authorizations are correct.
This report brings in this desired feature. When you execute this report if all connectivity settings including the authentication and authorization between the SAP S/4HANA system, middleware system and SAP Cloud for Customer system is successful then the report returns a success message for E2E connectivity. Else the report captures the exceptions and failures where ever it occurs and return it via the application log.
Integration
Prerequisites
Features
This report consumes the proxy CO_CODERINT_CONNECTIVITY_CHECK configured in SOA management to trigger a synchronous webservice call to your SAP Cloud for customer system via the middleware. The connection between the ERP system and middleware is established based on the credentials provided in the default port for the consumer proxy. If the synchronous call is successful then an application log mentioning successful status is returned and in any other case the application log will contain the relevant information on where and what error has occurred.
A success status of the report run implies a proper bidirectional communication set up between the S/4HANA system and middleware and also between the middleware and SAP CFC system.
Selection
Standard Variants
Output
Activities
The consumer proxy CO_CODERINT_CONNECTIVITY_CHECK is configured in the SOA management of your S/4HANA system and you need to create and maintain a default port for the proxy via which it can communicate to the middleware. The default logical port will have the access and authorization details to the middleware and also details of the service interface to be called.
When you click EXECUTE from the report screen the call is made to the middleware system with the information maintained in the logical port of the consumer proxy. Then if the authentication and authorization with the middleware system is successful, middleware system forwards the call to the SAP Cloud for Customer system. If the authentication and authorization between the middleware system and SAP Cloud for Customer system is successful then the report returns a success message for E2E connectivity. Else the report captures the exceptions and failures where ever it occurs and return it as an application log under log object 'COD_ERP_E2E_CONN'.
You can also view the application log at a later point also via transaction SLG1 by filtering on log object 'COD_ERP_E2E_CONN'.
- In case of PI the objects are available in the Process Integration Scenario 'COD_ERP_End2EndConnectivityChec'.
- In case of HCI we use the iFlows 'com.sap.scenarios.erp2cod.simpleconnectivity' & 'com.sap.scenarios.cod2erp.simpleconnectivity'.
When you execute the report it checks for a default logical port configured for the mentioned consumer proxy in SOA Management. If found the details are displayed in the screen. If no default port is maintained for the proxy service a new port can be created and set as default port via the report screen by entering the details in the field and clicking GENERATE. If a default port is already existing the report provides options to change the various access and authorization parameters, but will not allow you to create another default port via the report.
Click 'REFRESH' if you had accidently changed some entry in the screen do not intend to modify the default port with these values. When you click GENERATE the settings for the default logical port gets overwritten with the values entered in the screen.
Note: - The EXECUTE will perform E2E connectivity check using the settings maintained in SOA Management against the default port for the service consumed ignoring any changes made in this screen which is not GENERATED.
- Logical Port - Name of the logical port in SOA Management for the consumer proxy used for checking E2E connectivity.
- URL Access Path - Middleware service path URL for webservice call.
- In case of SAP NetWeaver Process integration (PI) the service path can be obtained from sender agreement
which should be of format :- /XISOAPAdapter/MessageServlet?senderParty=&senderService=
&receiverParty=&receiverService=&interface=ConnectivityCheckConsumer&interfaceNamespace=http%3A%2F%2Fsap.com%2Fxi%2FCODERINT
- In case of HCI :- /cxf/S4/C4C/SimpleConnect
- Computer Name - Name of computer of above PI / HCI system.
- URL Port - Port number of the URL. For PI the port can be obtained from SMICM or ICM admin. For HCI it can be set to 443.
- URL Protocol - Protocol for webservice call. For example HTTP/HTTPS.
- Proxy Host - Name of proxy host if a proxy is used for the http connection (optional)
- Proxy Port - Port number of proxy host if a proxy is used for the http connection (optional)
- Proxy User - Name of user if a proxy is used for the http connection (optional)
- Proxy - Password - Password for the user if a proxy is used for the http connection (optional)
The logon is possible either via certificate. Mark radio button SSL Client Certificate and select a certificate from the drop down.
or via User & Password. Mark radio button Basic Authentication and enter User & Password in the fields provided.
If the displayed configuration is fine click 'Execute' to run the connectivity check. A detailed application log of the check is then displayed.
Example
RFUMSV00 - Advance Return for Tax on Sales/Purchases BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 6571 Date: 20240520 Time: 115951 sap01-206 ( 131 ms )
