regd. change document objects

[vijay srikanth]

Hi,

You're absolutely right JOcelyn. Actually there's a predefined change 
document object called DEBI???? Who would have known?? It is for the 
transaction XD05......Did I spend time finding it...? :-) Anyway
thanks all.....


Regards,
Vijay


>From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
>Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>Subject: RE: regd. change document objects
>Date: Mon, 26 Sep 2005 19:10:44 +0800
>
>Yes you can link them.
>Sounds like you have
>
>a) Not found the customer master change document object
>
>b) Not set up your own change doc correctly so that the key of your
>object matches the key of the
>business object.  Plus I think there's another table to fill in relating
>the business object to the change doc object.
>
>Suggest you have a harder look for the real customer master change doc -
>i.e. the one using table KNA1.
>
>Regards,
>Jocelyn Dart
>Senior Consultant
>SAP Australia Pty Ltd.
>Level 1/168 Walker St.
>North Sydney
>NSW, 2060
>Australia
>T   +61 412 390 267
>M   + 61 412 390 267
>E   jocelyn.dart at sap.com
>http://www.sap.com
>
>The information contained in or attached to this electronic transmission
>is confidential and may be legally privileged. It is intended only for
>the person or entity to which it is addressed. If you are not the
>intended recipient, you are hereby notified that any distribution,
>copying, review, retransmission, dissemination or other use of this
>electronic transmission or the information contained in it is strictly
>prohibited. If you have received this electronic transmission in error,
>please immediately contact the sender to arrange for the return of the
>original documents.
>Electronic transmission cannot be guaranteed to be secure and
>accordingly, the sender does not accept liability for any such data
>corruption, interception, unauthorized amendment, viruses, delays or the
>consequences thereof.
>Any views expressed in this electronic transmission are those of the
>individual sender, except where the message states otherwise and the
>sender is authorized to state them to be the views of SAP AG or any of
>its subsidiaries. SAP AG, its subsidiaries, and their directors,
>officers and employees make no representation nor accept any liability
>for the accuracy or completeness of the views or information contained
>herein. Please be aware that the furnishing of any pricing information/
>business proposal herein is indicative only, is subject to change and
>shall not be construed as an offer or as constituting a binding
>agreement on the part of SAP AG or any of its subsidiaries to enter into
>any relationship, unless otherwise expressly stated.
>
>
>-----Original Message-----
>From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
>Of vijay srikanth
>Sent: Monday, 26 September 2005 7:54 PM
>To: sap-wug at mit.edu
>Subject: regd. change document objects
>
>Hi Jocelyn,
>
>We can link a change docu. object to a business object event. Can we
>also
>link custom
>change document objects to a business object event. I created a custom
>change document object and a custom business object. When I link the
>both in  SWEC, It says "NO KEY INFORMATION FOR CHANGEDOCUMENT OBJECT
>ZCUSTBLOCK(which is the change docu. object name)".  Thanks for the help
>in
>advance.
>
>Regards,
>Vijay
>
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>_______________________________________________
>SAP-WUG mailing list
>SAP-WUG at mit.edu
>http://mailman.mit.edu/mailman/listinfo/sap-wug