Purchase Requisition Standard Workflow - Container Data Decla ration

[Dart, Jocelyn]

Hi Abby,
This workflow actually requires you to use release strategies WITH classification.
It won't work if you don't use classification.  I wouldn't worry too much
about the config table it's using - very many customers are already using
this workflow successfully, and in any case some of the config tables
are shared by the with/without classification scenarios.
Plus the definition of the container element is just that - a definition - where
the content comes from is an entirely different matter.
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Abby Dywan [mailto:abby.dywan at us.pwcglobal.com]
Sent: Monday, 30 September 2002 6:42 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Purchase Requisition Standard Workflow - Container Data
Declaration
 
 
Hi all -
 
I have a question I was hoping someone could answer.  In the standard
purchase wflow (#0000038) there is a container element called ReleaseCode.
The data element it references is RM06B-FRGAB, which in turn references the
configuration table T161E - Setting up a release procedure without
classification.
 
Is there a reason it points at this config table instead of the config
table for setting up a procedure WITH classification (T16FC?)  And if so,
are there problems involved in using this workflow when we are setting up
release procedures with classification?  This is what we are trying to
do... I'm just not certain why the data declaration in the container is set
up this way and was hoping for some advice.
 
If anybody has any information, I would appreciate it.
 
Thanks very much!
Abby
_________________________________________________________________
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.