Customer Workflow-Task substituted during Upgrade

[Pollard, Bruce]

Ute,
 
Customer developed Tasks all begin with a "9" and the first 3 digits, =
the Prefix, is based on your client and system.  The chance that SAP =
would have a 9XX standard task delivered is remote, however stranger =
things have happened.  Normally the tasks we deliver are tasks that are =
specific to an Application area and don't begin with a 9, as this is =
the customer name space.  The 9 series of tasks that we do deliver, if =
any, are for training scenarios, and it sounds like the SAP solution is =
to simply remove/recreate this task, giving it a different numbering.  =
Sounds like you have already solved your problem locally,
 
Cheers,
Bruce
 
> Bruce Pollard
> Senior Consultant
> SAP Consulting - NetWeaver Practice Unit
> SAP America
>=20
> 5555 Glenridge Connector, Glenridge Highlands One
> Atlanta, GA 30342
> T   404.943.3025
> M  678.525.3679
> F   404.943.2882
>=20
> E   bruce.pollard at sap.com
> http://www.sap.com
>=20
 
 
-----Original Message-----
From: "Schr=F6der, Ute Marion" [mailto:UteMarion.Schroeder at REWE.de]
Sent: Thursday, July 31, 2003 9:03 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Customer Workflow-Task substituted during Upgrade
 
 
Hi All,
 
I'=B4ve got a problem here, that I've already reported to OSS,
however, someome at SAP, trying to help me solve the difficulties needs
further information.
 
Ok, the problem is:
We have a since 4.6B which uses different Standardtasks, there ist for
example task 90000029,
in 46B everything works all right.
Now we've upgraded our development system to 4.70 and here it comes,
spomeone at SAP has also developed a task named TS90000029, now the two
tasks, the standard one and the one from us, the customer, overlay each
other,
so that neither of them work as they ought to.
 
On the customer side we've solved the problem by creating a new =
"standard
task" with a new number in our old system, this task works as the =
customer
needs it,
it has been transported to 4.70 and included in the Workflow instead of =
the
broken task. So, the customer workflow is allright once again.
 
Now SAP and us are searching how-to fix the SAP task, that does no =
longer
work and that cannot be transported into the system due to us having no
older version of it.
 
Has anyone come across this before?
 
Advice extremly important.
 
Thanx=20
 
Ute=20