Fwd: Re: Workflow configuration SWDD_CONFIG problems

[Susan R. Keohan]

Forwarded on behalf of marter at TELSTRA.COM
 
>David,
>There are a couple of issues with SWDD_CONFIG.  I believe both to be
>transport issues.
>
>The first issue is where all the required table
>entries are not transported. When a configuration change is saved
>in our case adding a time delay to a step) 3 table entries should be
>generated for the following tables:-
>
>SWD_HEADER, SWD_MNODES, SWD_STEPS.
>
>The generated transport however did not export out all the table
>entries when released.   OSS note 400889 corrects this problem.
>
>The second issue which I've only come accross last week is where the
>configuration is not saved because a w/flow attribute is not being set
>correctly.  I haven't taken this up with SAP yet as we have a
>workaround.  If you go into your QA environment and display the w/flow
>via the workflow builder go to the header screen (via the top hat
>button).
>
>Not sure how CRM displays the following screen so I'll give you two
>scenarios:-
>
> - Core R/3
>     You will see a screen with 6 tab pages.  Goto the tab page
>     technical information.
>
> - EBP
>     You will see a screen which has 'Version independent basic data'
>     and 'Version dependent basic data'.  Go to 'Version dependent
>     basic data' then select the tab page 'Technical information'.
>
>Check the status of the attribute 'Configuration exists'.  If it is not
>set then you have the same problem as we did. You'll find most likely
>in your dev environment that the attribute is set correctly but is not
>transported correctly to QA.
>
>Michael Arter
>SAP Workflow specialist
>
>IBM GSA
>
>
>----- Original Message -----
>From: David Weston <weston at clockwork.ca>
>Date: Monday, June 25, 2001 11:53 pm
>Subject: Workflow configuration SWDD_CONFIG problems
>
>> Hi folks,
>>
>> Was wondering if anyone has experienced glitches when migrating
>> workflowconfiguration created
>> by transaction SWDD_CONFIG.
>>
>> Here's what we've done:-
>> 1. Created a WS template in our CRM development system, version 6.
>> 2. Created a workflow configuration for that and migrated the workflow
>> configuration to the 3. Unfortunately this did not migrate
>> correctly to the QA environment so we
>> had to manually create the workflow config in QA
>>    using SWDD_CONFIG. All return codes for the transport were 0.
>> 4. Now we have our template and workflow config in QA - great you say.
>> 5. Now we make a change to the WS template in development, version
>> 7 and
>> migrate to the QA environment.
>> 6. Lo and behold when we check the associated workflow
>> configuration in QA
>> that we previously had it has not been kept by the
>>   new  version of the workflow and we have to manually create it
>> again !!
>>
>> Anyone experienced this type of fun before with SWDD_CONFIG ?
>>
>> Cheers
>> Dave Weston
>> Clockwork.ca
>>
>