We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-log-sd] Additional email address on sold to party

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by llewis
on Oct 5 at 1:05 PM
Mark this reply as helpfulMark as helpful
We had the same issue - which has many common circumstances where one would want to use. Such as - send a customer a quote by email and have many contacts for the same customer to select from. Output conditions are useless here as it is dynamic output.

We used the customer contacts assigned in XD02 - table KNVK Customer Master Contact Partner. This is also tcode VAP1

Then we had to do some ABAP work to present the list of contacts to user when they issue output in VA22 etc. We also allow to create/edit contacts from here so salesperson need not have access to XD02, VAP1.


My opinion, standard SAP for email and output is lame. So buy your ABAP lunch.

---------------Original Message---------------
From: user_201
Sent: Tuesday, October 05, 2010 11:14 AM
Subject: Additional email address on sold to party

> I am working on an enhancement. My client has multiple email address they need to enter for a given sold to party, in order to be able to send out order confirmation, invoice, etc., out to the customer that way. The first email address is already stored in the system in the customer master (under "General Data" --> Communication section). There is only room for one email address in standard SAP. Where else would be a logically good place to put additional email addresses? Please note that the order confirmation might not go to the same invoice as the invoice, for example.

__.____._
Copyright © 2010 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Related Content
White Papers

In the Spotlight
Toolbox.com for iPhone: Ask Questions & Get Answers Anywhere. Use the New iPhone App
_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language