Parked Documents

Becker Stephan (extern) Stephan.Becker.ext at mchw.siemens.de
Tue Feb 11 10:39:39 EST 2003


Hi Monique,
 
As mentioned before, there is at least one large OSS note that explains the workings of workflow upgrades, which I would urge you to read. This explains the most common problems. In general terms, as long as you follow those guidelines, you shouldn't have huge problems.
The copied production system is a different matter. You will need to analyse the system (sm22/st22), RFC (sm58), event (swel/swels), and workitem (swi1) logs to see where things go wrong. It could be something trivial like the user logon info for WF-BATCH is different in QA than PROD (see sm58), but it could be more complex.. hard to jughe from the distance..
 
Hth,
Stephan
 
-----Original Message-----
From: Stephens, Monique S L [mailto:moniques at bcm.tmc.edu]
Sent: Dienstag, 11. Februar 2003 16:20
To: Becker Stephan (extern)
Subject: RE: Parked Documents
 
We bounced the system but the QA environment still does not seem to post the
parked documents once it completes the workflow process.  Have you had any
experience when upgrading to another version and not encountering any issues
with documents in workflow?
 
Monique Stephens
 
-----Original Message-----
From: Becker Stephan (extern) [mailto:Stephan.Becker.ext at mchw.siemens.de]
Sent: Monday, February 10, 2003 11:51 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Parked Documents
 
Monique, clear the buffers manually (eg $buf or another method your Basis
guys will know) and try again.
Stephan
 
-----Original Message-----
From: Stephens, Monique S L [mailto:moniques at bcm.tmc.edu]
Sent: Montag, 10. Februar 2003 17:19
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Parked Documents
 
Below is an excerpt of what our Basis group did:
 
changed the logical system.
 
Here is what takes place:
 
        We copy the production system to Q/A
 
        we change the logical system to QDSCLNT400
 
        So hence when you try to Approve/Close a PO that was created in
        Production you get the message PDSCLNT400......
 
        What I have done is change the Logical System to PDSCLNT400
 
        Now since this table is buffered, we have to bounce the system
        (which I did not).
 
Our central users are concerned that the documents will not post when we
upgrade next week.  So, we took a copy of Production on 12/16/02 to get our
QA box.  We have two QA boxes and one box was left alone while the other one
had the logical system changed.
 
Monique Stephens
 
-----Original Message-----
From: Becker Stephan (extern) [mailto:Stephan.Becker.ext at mchw.siemens.de]
Sent: Monday, February 10, 2003 9:51 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Parked Documents
 
Hi Monique,
 
Please explain your sentence "We tried to change the logical
client to Production on QA so that the workflow can be validated." What
exactly are you doing there? If you point the RFC destination to production,
then you would actually execute the workflow on production, based on the
definition in QA.. that can only fail, and may destroy production, so I
would stay well clear of that!!
 
On general terms, there are OSS notes for upgrading productive workflows,
and if you REALLY want to test an upgrade, copy production onto a new
system, upgrade it under laboratory conditions, and then do it for real
afterwards..
 
Hth,
Stephan
 
-----Original Message-----
From: Stephens, Monique S L [mailto:moniques at bcm.tmc.edu]
Sent: Montag, 10. Februar 2003 15:32
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Parked Documents
 
We are about to upgrade from 4.0B to 4.6C.  We have a lot of documents
currently in workflow (purchase orders and FI documents).  Are there going
to be any issues when we upgrade to 4.6C with these documents that are still
in workflow?  We have tried to test this in our QA environment.  But, the
original documents are stored in Production.  We tried to change the logical
client to Production on QA so that the workflow can be validated.  However,
documents still did not post after completing the workflow process.  This
could be due to the fact that other tables were not pointing to the
appropriate client.
 
Any help would be greatly appreciated.  I have sent e-mails to the user
group before but no one has ever responded.
 
Monique Stephens
SAP Analyst
Baylor College of Medicine
713-798-1349
713-798-1326 (FAX)
 


More information about the SAP-WUG mailing list