Skip to Content

You know those moments where you are getting stuck and all the error messages and logging in the world

are not helping you. Well hopefully I am going to prevent that happening to you, when it comes to setting up the End-to-end Workflow test tool for Duet Enterprise.

Our environment consists of :

  • Duet Enterprise FP 1 on Support package 2
  • ECC 6.0 Ides with EHP 4 on support pack stack 2 with NW 7.01
  • PI 7.1 with EHP 1 on Support package 6
  • Sharepoint 2010

On the Duet Enterpise DVD 3 (Mat.nr. 51039540_3)  you can find the files for setting up the End-to-end workflow test tool.

Follow the instructions found in the Feature Pack 1 for Duet Enterprise 1.0 SAP Operations Guide from page 12.

For you convenience I have pasted them here at the bottom of this blog.

Unfortunately for me it did not work out of the box.

This is what I encountered when triggering the verification workflow using Tx SWU3

The parameter ‘CreateTaskRequest.ExtensibleElements.Language’ is arequired field. It cannot be null or empty.

/wp-content/uploads/2012/11/srt_util_154223.jpg

Thanks to a tip from Binson not Bison I implemented note 1385461 and a whole lot of corresponding notes that came with it.

So al right let’s try again, trigger the Workflow and ….

Next error :


“unexpected error has occured on the server. Error detail reference not set to an instance of an object.”

So why did this happen? To answer that we have to go to the Sharepoint side of things.

You would assume that with the deployment of the .wsp file from the Duet DVD everything would be in order on the Sharepoint site. And it indeed looked like it because the site https://Sharepoint/Tasks/VerificationWorkflow/default.aspx was present and the proper users were granted access to it.

SAP Diag workflow.jpg

The weird thing is that when I ran the “Diagnose configuration problems” it did not show me the verification workflow. It was not there even though it was published using Sharepoint Designer (You have to do this for your Workflow to work). This of course caused Sharepoint to react with the error message when the Gateway was presenting the Workflow.

I solved this problem by manually creating the Verification Workflow site using the “Configure new SAP Workflow task type” option.

Make sure the Task Name is set VerificationWorkflow, because this will correspond to GPW Bound type in your ECC system

Now look at those beautiful Workflows coming in.

Time for you to create something wonderful. 🙂

Nizaar Thierens



Instruction found in Operations Guide:

Using the Verification Workflow, you can run an end-to-end functionality test of the Workflow

scenario. You can send a Workflow tasks from the SAP system to a Duet Enterprise SharePoint

site. If your Outlook is configured, you will also receive an e-mail notification. You can then

take a decision on the task, and update the SAP system with your decision.

Note: Before using the Verification Workflow, ensure that Duet Enterprise is deployed and all

required configurations are done.

Install Verification Workflow

Installing the Verification Workflow comprises 3 steps, which are detailed below:

1. Deploy BCsets file in the SAP system.

2. Copy the entries from the BC set into the Customizing tables.

3. Deploy and configure the site template.

The BCsets file is located on the software DVD at \Solutions\Workflow\Workflow Configuration

Check tools\VERIFICATION_WORKFLOW.bcs. The BCsets file should be deployed on your

Supportability

SAP system. The purpose of BC Sets is to make all necessary configurations for exposing the

Verification Workflow to Duet Enterprise.

The below procedure must be followed to upload the BCsets file to any system:

1. Extract the .zip file to retrieve the .bcs file.

2. In the SAP system where the Workflow components are installed, go to transaction

scpr3.

3. Click on the Upload BC Set button. Enter the path of the .bcs file extracted in the

previous step.

4. In the Create Object Directory Entry dialog box that is displayed, enter the package name

as ‘S_OSP_WORKLIST’.

5. Click Save to save your changes.

To copy the entries from the BC set into the Customizing tables:

1. In the SAP system where the workflow components are installed, go to transaction

scpr20.

2. In the BC Set field enter ‘S_OSP_VERIFICATION_WF’ and click Activate BC Set. The

Activation Options dialog is displayed.

3. In the Select Activation mode section, select Expert Mode.

4. Click Continue Activation. The BC set is now activated.

The Site template is a pre configured Workflow site, which will enable you to get all Verification

Workflow tasks to SharePoint. The template location on the software DVD is

\Solutions\Workflow\Workflow Configuration Check tools\verificationworkflow.wsp.

1. Deploy the supplied Verification Workflow template to the Duet Enterprise portal Web

application

2. Log on to Microsoft SharePoint and navigate to the Task Center in the Duet Enterprise

portal

3. Go to the Site Settings page. Under the Duet Enterprise Workflow Actions section, click

the Activate Duet Enterprise Workflow site link.

4. In the Template Selection section go to the Custom tab, and choose the

‘VerificationWorkflow’ template.

5. On the BDC Entity Section, select the Workflow BDC model you have uploaded to your

landscape during Duet Enterprise setup.

6. In the Activation Date’ section, select the Activate now option. Click Activate.

7. Go back to the Site Settings page. Click on the Grant User Access to SAP Workflow

Tasks link.

8. Select Verification Workflow Task Type to add the new item to the list.

9. Select the user to whom the Verification Workflow tasks must be sent, and click OK.

Supportability

Run Verification Workflow

After you have installed and configured the Verification Workflow, you can run it to diagnose

for errors in the Workflow settings.

1. Log on to the SAP system where the workflow components are installed. Log on with the

user credentials that have been configured to act on the Verification Workflow tasks.

2. Go to transaction swu3. The Automatic Workflow Customizing page is displayed.

3. Click Start Verification Workflow. A task is now sent to the Microsoft SharePoint

environment.

4. Now log on to the Verification Workflow site in Microsoft SharePoint using the same

user logon credentials.

5. Click on the Business Tasks link. The task sent from the SAP system should be visible

here (step 3).

6. Click on the task link, and then click the Run Test button.

7. Log on to the SAP system again with the same user credentials, and go to transaction

swi1. This page allows you to generate a report about the Verification Workflow process.

8. Click Execute to run the report. Do not enter any parameters.

9. In the report, the first entry should be the Verification Workflow task you have just

executed. Check that the task status is completed

If the above steps 1–9 have been executed successfully, it means that the Workflow scenario is

functioning correctly from end to end.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. William Newman

    Clever idea to create a workflow to facilitate the workflow. Do you normally need to do this in Duet 2.0 or can you just perhaps increase the HTTP bandwidth to avoid time outs from Gateway to the SharePoint server?

    (0) 
    1. Nizaar Thierens Post author

      With Duet you can easily transfer SAP workflows to Sharepoint.

      The verification workflow I used is standard in SAP and a great way to test if the Workflows are making their way to Sharepoint and back again to SAP.

      No need for increasing bandwith, the payload isn’t that big.

      (0) 

Leave a Reply