Change Doc Objects and Business Objects

Griffiths, Mark mark.griffiths at sap.com
Thu Dec 18 05:20:07 EST 2003


Look at the release strategy customising.  I think it is on the Release indicator settings screen.
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Cristiana D'Agosto
Sent: Donnerstag, 18. Dezember 2003 10:06
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Change Doc Objects and Business Objects
 
 
Mark,
 
can you please elaborate when you said 'The other thing you could look at is changing your release strategy
indicators to re-trigger the release if changes occur' - that could be the
clue for my problem with Purchase Order (I know you were talking about
PReq though).
 
Thanks and regards
 
Cristiana
 
 
 
 
 
Smith Elizabeth <Elizabeth.Smith at lai.ie>
Sent by: SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
18/12/2003 08:09 PM
Please respond to "SAP Workflow Users' Group"
 
 
        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        Re: Change Doc Objects and Business Objects
 
 
 
Mark,
 
Firstly, when I try to use transaction SWED I get a warning not to change
anything as this is SAP data. Secondly, a synopsis of what I'm trying to
do. My workflow is triggered when the Purchase Requisition is created. The
creator's Line Manager gives an unvalued implicit approval to the PR which
then goes to Materials Admin for pricing & sourcing. I want to protect
against significent changes taking place after the LM has given approval
and before MA receive the workitem. MA prices the PR and does the initial
release to invoke the Release Strategy. If a significent change is made at
this point the Release Strategy handles it. I want to trigger an event if
the PR quantity is changed but as I said in my original posting I get an
incompatibility error in transaction SWEC. I've found oss note 101623 the
short text of which is "Incompatibility of change docs & business
objects". Should I apply this note?
 
Fred,
 
Unfortunately in version 3.1I Business Object BUS2105 is not available!
 
Any other ideas?
 
Regards
Elizabeth
 
-----Original Message-----
From: Griffiths, Mark [mailto:mark.griffiths at sap.com]
Sent: 12 December 2003 13:24
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Change Doc Objects and Business Objects
 
 
To get this to work you need to use txn SWED and enter a structure with
the correct key in the 'Change Document key with structure' field.  To
populate the key you then need to use a function module to read the change
document tables and you insert this in the Function Module column.  It
takes a bit of work but you should be able to do it.
 
If SWED doesn't exist in 3.1 then try looking for table SWECDOBTYP
 
The other thing you could look at is changing your release strategy
indicators to re-trigger the release if changes occur.
 
Regards,
 
Mark
 
SAP UK
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Smith Elizabeth
Sent: Freitag, 12. Dezember 2003 12:45
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Change Doc Objects and Business Objects
 
 
Hello all!!
 
I logged this call last week and I got no responses.
 
I want to trigger an event when a change is made to a Purchase
Requisition. Change Documents are written when the change is made but
when I try setting up the event in transaction SWEC I get an error 'Key
for change doc. object BANF and business object type BUS2009 are
incompatible'.
 
We are on version 3.1I.
 
Since I logged my last call I've found an oss note 101623 applicable to
our current version.
However, it is very vague and I still don't know if it is the answer to
my problem.
 
Please help!!
 
Elizabeth Smith
Lufthansa Technik Airmotive Ireland.
 
 
Visit our Web Site: www.lufthansa-airmotive.com
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender.
**********************************************************************
 


More information about the SAP-WUG mailing list