cancel
Showing results for 
Search instead for 
Did you mean: 

Duet workflow configeuration

Former Member
0 Kudos

Hi,

We have configured duet workflow & implement a simple test workflow to test the same.

After executing the workflow and the scheduled programs we get the following error in slg1 :

"

Exception of type CX_SY_REF_IS_INITIAL has occurred. See details for more information

Exception of type CX_SY_NO_HANDLER has occurred. See details for more information

An unexpected exception occurred in the event handler with ID '/IWCNT/WF_WI'

Exception of type CX_SY_REF_IS_INITIAL has occurred. See details for more information

Exception of type CX_SY_NO_HANDLER has occurred. See details for more information

An unexpected exception occurred in the event handler with ID '/IWCNT/WF_WI'

An exception has occurred

"

Any help would be appreciated.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

How did you configure WF in Gateway? Did you use the Wizard or did you manually perform the configuration steps?

Where do you see these errors (in Gateway or in the SAP Backend system)? What are the other messages in SLG1 right above the error message? Those might give use a clue on where the problem lies.

You can also check the following (assuming these error message are from the Gateway system):

Transaction SPRO --> Reference IMG --> SAP NetWeaver --> Gateway --> Generic Channel Development --> Outbound Flow --> Events --> execute the following two steps

1) Event Handler IDs and Association to Consumer Types

Here, verify that you have an entry for /IWCNT/WF_WI and the associated consumer should be SHAREPOINT_INT

2) Event Handler Implementation

Locate entry /IWCNT/EI_SEH_SEND_WF_WI and click the Display button. Make sure that this Enhancement Implementation is activated and the Runtime Behavior should say "Execution depends on runtime filter values".

Cheers, Alex

Former Member
0 Kudos

Hi,

We have configured workflow through the wizard.

And we have a single sap SCL and backend system.

The settings mentioned by you are already in place in spro.

the messages before these in slg1 are :

Log for Workflow Pattern Framework

The Workitem : 000001733456 is not customized

Status Transition info could not be fetched for appl: WOMA

Stat-Tra call failed.Workitem update into SOSP_T_BKT_PERFM failed : WIID: 00000173456 RCPID:XXX

IH request for WIID:000001744171/RCPID:burkens/GPWOBJ-TYP:TASK ; BND/OPTYP:create succesful

Former Member
0 Kudos

Hi,

Looks like there is some customizing missing in your ERP backend system. Check the following:

1. Open transaction SIMGH.

2. Select the Workflow Pattern Customization IMG.

3. Select Workflow Pattern Customization and click the Execute icon.

4. Select your application and double-click Action.

Here you should see a list of status codes. If this list is empty then click on the Copy actions from Workflow Management button. Also scroll to the right and verify that some of the entries have the active flag (no change required, only verify).

If the list is populated then let me know how many entries and maybe also copy a couple of samples into the thread.

Cheers, Alex

Former Member
0 Kudos

Hi Alex,.

thanks for the response.

The customization is in place in SIMGH.

We have added 2 status codes for creation and approval.

we are getting following error message in srtutil:

Value SRT: Unsupported xstream found: ("HTTP Code 302 : Found")

Edited by: sap_wiz on Jan 24, 2012 2:17 PM

Former Member
0 Kudos

Hi,

I would still copy the pre-delivered entries via the Copy actions from Workflow Management button, just to make sure you are not missing any other entries.

As for the 302 error, can you tell from the SRTUTIL log if this is an error issued by SharePoint's obaworkflowservice.asmx web service? If so, please provide more details on how you set up the logical port for consumer proxy TaskflowWebServiceSoap.

Cheers, Alex

Answers (0)