2019 Feb 26 6:25 AM
Hello everyone,
I am new to ABAP technical consultant,
Actually, I got one issue from functional team, which was email is triggered to wrong person when we click on PGI button in delivery document.
Email should be sent to the customer which we maintained in Customer master -> Sales area data-> Partner function.
But Email is sending to the customers which we maintained in VBPA table for that SO number.
So, how can we maintain the VBPA table with required customer?
Hope my question is clear, else comment below for clarity.
If anyone came across this in your past days, please suggest me.
Thanks
Karthick
2019 Feb 26 8:04 AM
I think you may check out the output type routine or related workflow
2019 Feb 26 8:13 AM
Thanks for your response.
yeah, the logic to fetch the email is written under user-exit, which is getting triggered, when we click on PGI.
But,I didn't understand how do we change the customer in VBPA to trigger mail to the customer.
How VBPA entries can be changed?
2019 Feb 27 1:55 AM
From your comment above I think there are something to consider:
1. Check the determination of partner function ( SPRO / Sales & Distribution / Basic Function / Partner Determination / Set up Partner Determination ).
2. Check if there is any enhancement change the VBPA during VA01, VA02 ( like USEREXIT_SAVE_DOCUMENT_PREPARE,
USEREXIT_SAVE_DOCUMENT...).
3. For the logic fetch email from user-exit, i think you could change the logic to fetch it from customer master instead of partner function table, it simple. But i sugest to confirm above points for the cosolidation.
2019 Feb 26 11:12 AM
you mean program itself picking wrong customer for salesorder?
2019 Feb 26 11:23 AM
Hi Jagadeesh.
Thanks for your response
In the program, logic is written to fetch customer from SO, but if we modify in the SO, it is not reflecting in the VBPA table.
Will it reflect if we modify in SO??
2019 Feb 26 11:44 AM
2019 Feb 26 12:15 PM
No Jagadeesh it is not working.
See, i went to VA02 -> Header data -> Partners -> Modified Customer number and saved.
Thats all right.
It is not reflecting in VBPA table. I even tried logging out the system and still it is not updated.
Did I missed something?
2019 Mar 01 5:56 PM
Email should be sent to the customer which we maintained in Customer master -> Sales area data-> Partner function.
This is simply the screen where we can assign the related partners to a customer. This can be, for example, used to assign valid ship-to partners to one sold-to partner. Then, when someone goes in to enter a sales order, they can enter sold-to customer and then a screen will pop up asking which ship-to partner they want to chose.
This can be used to assign any partner type. To be used in the sales transactions, the partner must be configured to be referenced in the sales documents. This will take the information from the customer master and put it into sales document partners (VBPA table). Output can also be configured for any partner.
This is all just plain SD configuration and does not require any ABAP. It's not clear if your company implemented some custom ABAP program for this (it really should not be needed). If so then I'm afraid you're on your own to solve the issue because it's not standard SAP. Get help from a local SD expert.
2019 Mar 04 6:53 AM
Thanks for your useful information, Jelena.
Basically, logic is written as 'customer which we maintained in the VBPA table - for those only mail is going to trigger'.
So, User modified the Partner function details in Billing document, and expecting the mail to be triggered to that updated one and this is a negative case.
I am having a positive case also, which is having same partner details in SO and Billing document and in VBPA also. So, mail is triggering to that expected one, which is in billing document, as per user's requirement.
So that we changed in entry in SO, as it is in Billing document, to satisfy the requirement but then VBPA is not updated with changes.
That is the issue, I am facing.
If you have any ideas in this, please share.
Thanks once again:)
2019 Mar 04 7:56 PM
Sorry, I lost track of this story completely. There seem to be conflicting / unrelated statements in your last comment. Please re-read it and state more clearly (and in SAP terms) what exactly is the expectation and what is the issue.