‎2007 Jun 08 3:34 PM
Hi Experts,
Can anyone please tell me if there is a BAPI for the Tcode FD32 to block a
customer who exceeds his credit limit?
Thanks
Dany
‎2007 Jun 08 3:42 PM
Hi Dan,
Please check this FM CREDITLIMIT_CHANGE.
Regards,
Ferry Lianto
‎2007 Jun 08 3:53 PM
‎2007 Dec 07 6:45 AM
if both KNKA and KNKK are updated.
use this FM CREDITLIMIT_CHANGE.
if either KNKA or KNKK is updated.
use FM KLIM_WRITE_DOCUMENT
below is a simple example.
REPORT ZTEST.
TABLES:t014,t014t.
INCLUDE ff02lcdf.
INCLUDE ff02lcdv.
PARAMETERS:kunnr LIKE knkk-kunnr,
kkber LIKE knkk-kkber.
START-OF-SELECTION.
END-OF-SELECTION.
CLEAR:t014,yknka,knka,yknkk,knkk.
SELECT SINGLE * FROM t014 WHERE kkber = kkber.
IF sy-subrc = 0.
*XF02C = t014-waers.
xf02c = t014-waers..
ENDIF.
objectid = kunnr.
tcode = 'FD32'.
utime = sy-uzeit.
udate = sy-datum.
username = sy-uname.
upd_knkk = 'U'.
SELECT SINGLE * FROM knka INTO yknka WHERE kunnr = kunnr.
IF sy-subrc = 0.
MOVE yknka TO knka.
ENDIF.
SELECT SINGLE * FROM knkk INTO yknkk WHERE kunnr = kunnr AND kkber = kkber.
IF sy-subrc = 0.
MOVE yknkk TO knkk.
knkk-klimk = '543.23'.
knkk-ctlpc = 'SG2'.
MODIFY knkk.
ENDIF.
IF ( upd_knka NE space )
OR ( upd_knkk NE space )
.
CALL FUNCTION 'KLIM_WRITE_DOCUMENT ' IN UPDATE TASK
EXPORTING
objectid = objectid
tcode = tcode
utime = utime
udate = udate
username = username
planned_change_number = planned_change_number
object_change_indicator = cdoc_upd_object
planned_or_real_changes = cdoc_planned_or_real
no_change_pointers = cdoc_no_change_pointers
o_yknka = yknka
n_knka = knka
upd_knka = upd_knka
o_yknkk = yknkk
n_knkk = knkk
o_xf02c = *xf02c
n_xf02c = xf02c
upd_knkk = upd_knkk.
ENDIF.
CLEAR planned_change_number.
‎2010 Nov 18 10:47 PM
Aheadjava,
Why not use "KLIM_WRITE_DOCUMENT" even if both tables needs modification ?
José