Ansicht
Dokumentation

Logical destination now client-specific ( RELNWF_30E_LOG_DESTIN )

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Short text

Logical destination now client-specific

Description

For internal communication the Workflow runtime system needs a logical destination.

Previously one logical destination with the name WORKFLOW_LOCAL was used in all clients. This caused problems because the user assigned had to exist in every client with the same password.

A separate logical destination is now created for each client under the generated name WORKFLOW_LOCAL_. The user assigned then needs to exist only locally in one client.

Setting up the logical destination is supported by an associated activity in the implementation guide.

Damage caused to data by errors

Software/hardware requirements

Installation information

The previous system behavior remains unchanged. It is not mandatory to convert the previous logical destination.

However, we recommend that you perform the conversion.

To do this, use the corresponding customizing activity in every client.

A new logical destination is created for every client with the previous user.

Create logical destination for tRFC

Effects on System Administration

Effects on Customizing

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

CPI1466 during Backup   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 1855 Date: 20240523 Time: 042241     sap01-206 ( 28 ms )