VK11/VK12 UserExit on Save
by rmsb on Saturday, March 28th, 2009 | 5 Comments
If you need to trigger some code when you are saving pricing conditions in VK11 or VK12, there is an option to do that. it’s not a standard exit, but it’s a BADI. SD_COND_SAVE_A it’s the name! This way you can trigger some code inside it. SAP Badi can be activated and edited throught these transactions: SE18/SE19.
You can call these transactions inside BADI:
CT_TIME
CT_KONH_NEW
CT_KONH_OLD
CT_KONPDB_NEW
CT_KONPDB_OLD
CT_SCALE_NEW
CT_SCALE_OLD
CT_KONDAT_NEW
CT_KONDAT_OLD
CT_VAKE
Need Help?
Post a Comment!
How do you use those transactions within the method? I want to check the sales org, for example, before the pricing condition is saved. How would I do that? What is “inside” those parameters (CT_KONH_NEW, CT_VAKE, and so on)?
On the BADI place a break point and check those structures i mention. there must be a structure with the sales organization in it.
if you need futher assistance please contact
I have a breakpoint in the BADI. I still can’t seem to find the Sales Org. I do see all of the structures that you mention, though. I can view the contents of each structure and I see fields such as: mandt, ername, kschsl, and so on, but no Sales Org. The field for the Sales Org on the actual VK11 screen is KOMG-VKORG, but the BADI does not reconginze that field, either. Any suggestions on how to get visibility to Sales Org?
Nevermind, I believe I see the Sales Org as part of a field called VAKEY within the CT_VAKE table. However, within debugger when I type CT_VAKE-VAKEY into the variable box in an effort to view the value of this field, debugger acts as if its an invalid field and displays the “lightening bolt” arrow icon, as if to indicate that you’ve asked to see a variable that is out scope.
I figued it out. Thanks for all the help.