SAP Note 26714 - Workflow customizing prerequisites

Symptom:

The following symptons can occur when customizing has not been fully completed:

• Popup to request the active plan variant is displayed every time a workflow maintenance transaction is called (PFWS, PFWF, PFTS, PFT)

• No workflow templates available

• Message OL:810 when an object method is carried out

• Message SR:027 in the RFC queue (transaction SM58).

At the end of this note there is a description of how to collect a report that verifies the workflow customizing. If you are having problems with workflow in a new system it is a good idea to run this verification report before proceeding further.

Additional key words

..

Cause and prerequisites

Customizing has not been completed.

Solution
Sympton: Popup requesting the active plan variant is displayed every time the workflow maintenance transaction is called.

Reason: The active plan variant has not been defined.
Solution: Configure an active plan variant. This is done via workflow basic customizing. Route: General basis -> Workflow management -> basic data ->Set active plan version

Sympton: No workflow templates available.

Reason: The workflow templates have not been copied into your client or they have not been activated (automatic after 3.0B).
Solution: Execute the report RHWFACTI with the test flag on. If no entries exist you must copy the templates from client 0. If templates do exist but have not been activated you can activate them by switching the test flag off and executing the report again.

Sympton: Message OL:810 when an object method is carried out. This can lead to the workflow being created with no step-protocol.

Reason: No logical destination has been defined for this client.
Solution: Call transaction BD54 to create a logical system name and then use transaction OY25 to assign it to this client.

Sympton: Message SR:027 in the RFC queue (transaction SM58).

Reason: The WORKFLOW_LOCAL Logical Destination has not been configured.
Solution: Define a Logical Destination using customizing. Route: General basis -> Workflow management -> basic data -> Create local destination for tRFC.

Customizing verification report.
In 3.0B, the transaction SWU3 can be used to verify the workflow customizing. This is available on SAPSERV3 as pre-release functionality. Do not collect the patch if you have release 3.0B or higher!
To collect the program from sapserv3:
You will find the correction in the directory /dist/permanent/Note.0026714, transport request P30K034639 (you can find a description of the import procedure in note 13719).