Rfc destination workflow_local_400 can't be reached, by ABAP programme CL_SWF_RUN_WIM_LOCAL===CP!! Dumps are raised in ST22!!

[Former Member]

Hi All,

We are getting the folloging Dump  Unable to read RFC destination WORKFLOW_LOCAL_400.

As we have done system refresh activity, we have copied the data from Production 400 client to quality 400.

After that we have done client copy from Quality 400 client to 210 client and we have BDLS in 210 client for Logical name conversion.

We have changed the RFC connection in SM59 to WORKFLOW_LOCAL_210. But still event is triggering the WORKFLOW_LOCAL_400.

Can you please tell us where I can change the entry WORKFLOW_LOCAL_400 to WORKFLOW_LOCAL_210. So the the event is trigger correctly by taking WORKFLOW_LOCAL_210.

Regards,

Avadhesh,

+91 8095225536

[Ranjith418 · Accepted solution]

Hi Avadhesh,

Please go to swu3 and chose option

Maintain Runtime Environment -> Configure RFC Destination

You can re execute this option. please find the documentation for rfc configuration for swu3 below.

Configure RFC Destination

Component

SAP_BASIS: SAP Business Workflow/WebFlow

Execution

Automatic/Manual

Function

The workflow runtime system always executes its tRFC (transactional RFC) calls on the logical destination WORKFLOW_LOCAL_xxx (xxx stands for the three-digit number of the client).

The workflow runtime system only operates within one client. The naming for the logical destination guarantees that these names are unique across the system.

If you carry out this activity automatically, the logical RFC destination WORKFLOW_LOCAL_xxx is created (if it does not already exist). The user WF-BATCH (system user) is assigned to this destination.

If you belong to the SUPER user group, and the WF-BATCH user does not exist, it is created and automatically gets the maximum authorization of the current user (SY-UNAME). This function is to be performed once by a user who belongs to the SUPER user group.

If you perform this activity manually, you can maintain another system user and another password.

If you want to restrict the authorization of the system user, proceed as follows:

• Set plan version in role SAP_BC_BMT_WFM_SERV_USER
  This role contains the authorization object PLOG (personnel planning). Assign your active plan version to the Plan Version field and generate the authorization profile.

• Assign role SAP_BC_BMT_WFM_SERV_USER
  Use user maintenance to remove the assignment to all roles and profiles and assign the single role SAP_BC_BMT_WFM_SERV_USER.

• Add application-specific authorizations
  Also assign the system user all application-specific authorizations that are required to execute your active workflows.

[Former Member · Accepted solution]

Hi Jacob,

I tried in SWU3 tcode to reconfigure the RFC desinations, but

This error I am facing.

Please let me how can I re configure the RFC destinations.

Regards,

Avadhesh.

[Ranjith418 · Accepted solution]

Hi Avadhesh,

please let us know the error that you face.

Thanks,
Ranjith

[former_member195313]

For the RFC Destination "Workflow_Local_XXX" you should go to transaction SWU3 and

execute “Configure RFC Destination” selection which is under “Maintain Runtime Environment”

TRFC SM58 Error "Name or Password is incorrect" for Workflow_Local_ | SAPBASISINFO

[Former Member]

hi avadesh,

maybe this could help you:

http://help.sap.com/saphelp_nw70/helpdata/en/a0/28e937a5caba6ee10000009b38f842/frameset.htm

or:

(Zitat aus Text help.sap.com)

You can access this function by choosing Tools → Business Workflow → Development → Utilities → Automatic Workflow Customizing (SWU3)

and set up the logical rfc - connection again with the right name.

also check thu user zb. wf-batch

br

julius

[former_member144433]

Hi Sharma,

Each time you perform a client copy, you will

have to run SWUB to create the proper RFC destination for that client.

The client copy does not copy the RFC information. This information

is client-independent, a client copy (on the same machine) of this

information would not be useful (because it is a client independent

table). Additionally, copying this information in the case of a

remote client copy would not be useful because the RFC destinations

/definitions of one system may not apply to another. To correct your

problem of the missing RFC destination, again, you can run SWUB or

go to SWU3 and run the option for reconfiguring the RFC destination

once more. The workflow runtime system will look for

WORKFLOW_LOCAL_<Client #> first (which is unique to a client). If it

cannot find this, it will then look for the RFC destination of

WORKFLOW_LOCAL.

This information gets deleted during a client copy as the relevant

table, SWWCUSTOM, is class L (see note 2857).  The way you are currently

dealing with it is correct, using SWU3 after the client copy.  However,

a way to speed this process up is to copy the client and run a recorded

CATT via the report RSSTARWC in the background. Execute the

transaction SWU3 in the CATT.

So please create your RFC Destination and it should work fine.

Thank You.

Regards,

Deepika

[Former Member]

Hi Deepika,

We have tried SWUB t code and tried to execute.

It is giving the following dump.

Please let me know, how can I reconfigure the RFC destinations

Regards,

Avadhesh.