old method

Former Member — Sat, 22 Dec 2007 07:51:19 GMT

I'm a bit surprised...

Code:

----

FORM USEREXIT_PRICING_PREPARE_TKOMK *

----

This userexit can be used to move additional fields into the *
communication table which is used for pricing: *
TKOMK for header fields *
This form is called from form PREISFINDUNG_VORBEREITEN. *

----

FORM USEREXIT_PRICING_PREPARE_TKOMK.

TKOMK-zzfield = xxxx-zzfield2.

TKOMK-KUNRE = XVBPA_RE-KUNNR.
TKOMK-KUNWE = XVBPA_WE-KUNNR.
TKOMK-KNRZE = XVBPA_RG-KUNNR.

PERFORM XVBPA_SELECT USING 'VE'.
TKOMK-VRTNR = XVBPA-PERNR.

PERFORM XVBPA_SELECT USING 'SP'.
TKOMK-SPDNR = XVBPA-LIFNR.

PERFORM XVBPA_SELECT USING 'AP'.
TKOMK-PARNR = XVBPA-PARNR.

ENDFORM.this i found in RV60AFZZ

changing this subroutine means changing standard SAP code... it's not like UserExit includes...

could somebody get me out of my shock and explain what's that and how to deal with such things???

__________________

Re: old method

Former Member — Sat, 22 Dec 2007 12:30:04 GMT

Hi,

That's the old way userexits were done. You either put your code directly in the form, or add an include statement and put your code in the (Z or Y) include.

V old - certainly was old when I was working on 3.1H - might be from R/2 or the 3.0D days....

SD exits are still quite often done this way (since if it isn't broken there's no need to fix it!)

Cheers,

siva

topic old method in Application Development and Automation Discussions

old method

Re: old method