SRM 4.0 Error Messages within BADI's
tamara.elliott@kodak.com
tamara.elliott at kodak.com
Fri Nov 11 13:20:59 EST 2005
Thank you for your response, and sorry about the non-workflow questions. I
was caught up in all the other SRM workflow questions going on, and wasn't
thinking. Thanks again.
Tami Elliott
Eastman Kodak Company
Rochester, NY
(585)724-4927
"Dart, Jocelyn" <jocelyn.dart at sap.com>
Sent by: sap-wug-bounces at mit.edu
11/11/2005 12:34 PM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>
To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc
Subject
RE: SRM 4.0 Error Messages within BADI's
Ok,
1. This is NOT a workflow users group question - please direct future
questions like this to the relevant forum, e.g. on SDN
2. Your mistake is to raise the message directly in the Change BADI -
messages should NOT be raised in the Change BADI at all, you should raise
messages only in the Check BADI - passing back the message id and code via
the ET_MESSAGES table. Then both short text and long text can be viewed.
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.
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of tamara.elliott at kodak.com
Sent: Saturday, 12 November 2005 3:06 AM
To: SAP Workflow Users' Group
Subject: SRM 4.0 Error Messages within BADI's
We are using the BBP_DOC_CHANGE_BADI to check for, and display errors to
users during shopping cart creation. I am using the standard message code
- MESSAGE E001(zmsg_class) - to display the error message. Unfortunately
you are limited in the number of characters available to display a
message. I have tried using the long text portion within the SE91
transaction, but when the message appears during shopping cart creation it
does not give you the option to display the long text - only the short
text is displayed.
Is there a better way to display messages back to the users that gives you
more text capability?
We are using SRM 4.0.
Thanks.
Tami Elliott
Eastman Kodak Company
Rochester, NY
(585)724-4927
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20051111/a251b843/attachment.htm
More information about the SAP-WUG
mailing list