Additional details for BUS2014

[Dart, Jocelyn]

All call the change document function modules such as CHANGE_DOCUMENT_READ etc.
Jocelyn.
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Corrin, Mat
Sent: Friday,3 September 2004 5:28 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Additional details for BUS2014
 
Hi Paul,
 
You can usually get the type of info that you require from the change document tables (CDHDR & CDPOS). You could put the code to read this data into an attribute of your business object or you could create a new method to do it and then call a task that uses this method from your workflow.
 
Cheers,
 
Mat.
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
McGhghy, Paul
Sent: 02 September 2004 16:14
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Additional details for BUS2014
 
 
Hello All Workflow Developers,
 
We are currently using workflow to sent mail when changes are made that require someone to proceed to the next operation in the process.  We use release strategies for purchase contracts for release at the contract level and not at the line item level.  Workflow for the send mail is using BO BUS2014.  The users would like to have details of what was changed on the contract that triggered the requirement for the release.  We only have the release triggered if a material price was changed or if the terms change.  They would like a message that shows:  Material 'XYZ' price changed from '3.00' to '2.59' effective 9/1/04.  What is the best was to get the details added since they are not in BUS2014.
 
Thanks,  Paul
 
 
__________________________________________________________________________
This e-mail and the documents attached are confidential and intended
solely for the addressee; it may also be privileged. If you receive this
e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos Origin group
liability cannot be triggered for the message content. Although the
sender endeavours to maintain a computer virus-free network, the sender
does not warrant that this transmission is virus-free and will not be
liable for any damages resulting from any virus transmitted.
__________________________________________________________________________