AW: Binding issues 4.6c
Rick Sample
Rick.Sample at gbe.com
Tue Aug 5 11:19:24 EDT 2003
I have never deleted an old WF version. I just resync buffers, generate a new
version and begin. I resync buffers, consistency check, etc. before I transport.
If at all possible, I ensure that all old versions of the WF are completed or logically deleted
in HQ. (Which is not supposed to be an issue).
I just loose a container element from time to time in the WF Template. And some that
I do loose I have not touched in the new version. Just MIA in new transport.
>>> heinz.schmidinger at unaxis.com 8.5.2003 10:09:02 AM >>>
Hi Rick,
I got/get similar 'mystery' situations.
A WF-Container-Element isn't to be created because it should exists (meaning
of the WF-Bulider), but isn't shown. I must define it in the WF-Basics t
oget it again.
Today a have changed a WF-Definition for an half day in the dev.client,
saving and generating periodiclly.
Unfortunally I have done a testrun in an other client in the same system.
After leaving the WF-Builder and entering it again, a new version was
craeted automaticlly (I have deleted all created instances in the
test-client before !) and, very funny, all changes done before where
dispapeared in the Version saved and generated before.
My conclusion is that the buffering is a great problem while developing and
testing and you can't be careful enough in handlind Versions.
So maybe you have also lost a part of the Containerdefiniions by
inconstencies caused by the buffer-problems.
regards
Heinz
-----Ursprüngliche Nachricht-----
Von: Rick Sample [mailto:Rick.Sample at gbe.com]
Gesendet am: Dienstag, 5. August 2003 15:16
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Binding issues 4.6c
Yes. I did refresh the buffers. (First thing I do before I run my
consistency checks after transport to HQ0.)
I also created a new version in HD0 before I made changes for the new
transport..
================================================================
I have a binding issue every once and a while. Here is the what I happens.
For one WF in HD0, I have TYPEID SOS04.L_ART that does not show in the WF
Template container.
When I go to the workflow builder, it is there. Everything works fine. (WF
works, no errors in consistency check, etc.)
When I transport to HQ0, I get binding errors! TYPEID is nowhere to be found
and binging errors
between WF Def and Tasks.
I am not sure why this happens. Also, every once and a while I loose
containers in the WF Template.
They are in the Tasks and Template on HD0 but get "lost" in the transport!
I don't see a pattern or anything I am doing wrong. The only way I have been
able to fix this
in the past is to Add the containers in question to the WF Template and
transport again.
Annoying!
I need to be able to explain this other in shop as to why.
OSS note on this issue?
More information about the SAP-WUG
mailing list