3439117 - Activating Released SAP Inbound Services for Use in Custom Communication Scenarios

 You want to use in custom communication scenarios the SAP enabled subset of released inbound services of SAP S/4HANA Cloud Public Edition.

 SAP S/4HANA Cloud Public Edition

SAP allows a subset of the released inbound services of SAP S/4HANA Cloud Public Edition to be added to custom communication scenarios. This option is only available after the feature toggle CUSTOM_COM_SCEN_API_PILOT has been activated. This feature toggle is delivered in SAP S/4HANA Cloud Public Edition deactivated and can only be activated by SAP. To request activation of this feature toggle, please create a case in 'SAP for Me' on component CA-DMS. (Note: While creating a case on component CA-DMS, kindly add a tag ‘CUSTOM_COM’ in the subject line).

In the future, released inbound services of SAP S/4HANA Cloud Public Edition may become available for use in custom communication scenarios without the need to request activation of the feature toggle `CUSTOM_COM_SCEN_API_PILOT`. In addition, this functionality can be replaced by a successor in the future after a deprecation phase for the existing functionality and the custom communication scenarios created for the existing functionality must in this case to be adapted to the successor by the customer.

The list of available released SAP inbound services for usage in custom communication scenarios after activation of feature toggle `CUSTOM_COM_SCEN_API_PILOT` can be found in the app Custom Communication Scenarios when you click in edit mode for a custom communication scenario on the add button for Inbound Services. The list will show all available released SAP inbound services enabled for usage in custom communication scenarios. Once you click on an entry, the documentation for the inbound service will be displayed.

The number of available released SAP inbound services can be increased with future deliveries by SAP.

Please note that the necessary authorizations required for a released SAP inbound service may change with future deliveries from SAP and must be adapted by customers or partners, if applicable, within the context of the included custom communication scenarios.

Please consider that the component CA-DMS should only be used for requesting the activation of the feature toggle `CUSTOM_COM_SCEN_API_PILOT`.

If you have questions or encounter problems with any of the released inbound services, please open a case under the corresponding component of the service itself. You can find the component for a service in the app `Display Inbound Services` by searching for the inbound service ID and displaying its details.

In addition, please find below further information for some released SAP inbound services for usage in custom communication scenarios

Inbound services JOURNALENTRYBULKCREATIONREQUES_WEBI ( Journal Entry - Post (Asynchronous)) and JOURNALENTRYCREATEREQUESTCONFI_WEBI (Journal Entry - Post (Synchronous)) note 3429647 - Using APIs Journal Entry - Post (Synchronous & Asynchronous) and Operational Journal Entry Item - Read (A2X) in Custom Communication Scenario

Inbound service API_SUPPLIERINVOICE_PROC_SRV_0001_IWSG note 3430638 - OData API API_SUPPLIERINVOICE_PROCESS_SRV: Attachment handling with custom communication scenario 

Inbound service FAA_FIXED_ASSET_CHANGE_WEBI, FAA_FIXED_ASSET_CREATE_MAIN_WEBI and FAA_FIXED_ASSET_CREATE_SUB_WEBI note 3430951 - Using Fixed Asset Asynchronous SOAP APIs in Custom Communication Scenario

Inbound service API_CV_ATTACHMENT_SRV_0001_IWSG note 3439086 - Using API_CV_ATTACHMENT_SRV in Custom Communication Scenario

CUSTOM_COM_SCEN_API_PILOT , CUSTOM_COM , API_CV_ATTACHMENT_SRV_0001_IWSG , FAA_FIXED_ASSET_CHANGE_WEBI , FAA_FIXED_ASSET_CREATE_MAIN_WEBI  , API_SUPPLIERINVOICE_PROC_SRV_0001_IWSG  , JOURNALENTRYBULKCREATIONREQUES_WEBI  , JOURNALENTRYCREATEREQUESTCONFI_WEBI , KBA , CA-DMS , Document management , How To