3312969 - Custom communication scenarios: Allowed Scenarios instances - S/4HANA Cloud

• You are using S/4HANA Cloud.
• You want to create a custom communication scenario for Key User Extensibility.
• You want to edit a custom communication scenario for Key User Extensibility created before S/4HANA Cloud 2302 and you are not allowed with errors "An Error occurred in communication Arrangement YY1_CA. Communication scenario already in use".
• You want to create a custom communication scenario for Developer Extensibility.

S/4HANA Cloud

S/4HANA Cloud 2302

Key User Extensibility

Predefined communication scenarios are available for different use cases, for example the integration for employee data. Decide which scenario you are going to use to create a communication arrangement.

You can create your own custom communication scenarios using the Custom Communication Scenarios app in Key User Extensibility

You can later use to create a communication arrangement using the Communication Arrangements app. A communication scenario bundles inbound and outbound communication design-time artifacts and is a basis for communication between systems. Each communication arrangement must be based on a communication scenario.

Developer Extensibility

A communication scenario, which is created in the development system using ABAP Development Tools and transported to other systems, is a design time description of how two communication partners communicate with each other. It consists of inbound and/or outbound services as well as supported authentication methods.

It provides technical information, such as the used inbound and outbound services and their service type, for example OData or SOAP, and the number of allowed communication arrangement instances. If the scenario exposes inbound services, it specifies the authorizations that are required to execute the services.

Key User Extensibility

As of S/4HANA Cloud 2302, if you do not add an Outbound Service to the Custom Communication Scenario, the custom communciation scenario will be created with property Allowed Instances: One Instance per Scenario and Communication System

If you add an Outbound Service to the Custom Communication Scenario, then it will be created with property Allowed Instances: One Instance per Client.

The restriction to allow only one custom communication scenario per client was introduced with S/4HANA Cloud 2302.

The custom communication scenarios that have been created before that release will have the type One Instance per Client automatically.

However, if no outbound service is used the type can be changed to One Instance per Scenario and Communication System.

If you would like to change the type, there are two possible workarounds:

• Republishing the scenario.
• Adding a dummy outbound service, removing it and saving it

In this case, the type will be changed to One Instance per Scenario and Communication System. This type will allow you to create more than one communication arrangements per custom communciation scenario.

Developer Extensibility

• Allowed Scenarios instances: One instance per client

  Only one active communication arrangement can be maintained for the communication scenario in the system.

• Allowed Scenarios instances: One instance per scenario & communication system

  Multiple active communication arrangements for one communication scenario for different communication systems in one system are enabled.

Key User Extensibility - Communication Management

Key User Extensibility - Custom Communication Scenarios

Key User Extensibility - Communication Arrangements

Fiori Apps Library - Custom Communication Scenarios

Fiori Apps Library - Communication Arrangements

Developer Extensibility - Communication Management

Developer Extensibility - Service Consumption via Communication Arrangements

custom communication scenario, allowed Instances, One Instance per Client, One Instance per Scenario and Communication System, key user extensibility, developer extensibility , KBA , BC-SRV-APS-COM , Maintain Communication System and Arrangement , Problem