I've been tasked with detecting whether or not the reference number is being repeated for a given vendor in any previous Entry Sheet during sheet creation in ML81N. If the reference number duplication is discovered the SAVE is supposed to be stopped so the user can potentially correct their data entry error or abort the save due to duplicate invoicing.
I'm new-ish to ABAP so I've been digging and discovered that user exit EXIT_SAPLMLSR_001 seems to best fit my needs; I get the EKKO and ESSR records for the transaction which allow me to implement my logic, and I can issue a message that the condition has been discovered.
My problem is stopping the SAVE. I've traced a little beyond the user exit but things get confusing so it's time to ask for help.
Is there convenient way to interrupt the action without quitting ML81N entirely? Should I be using another method, such as a different user exit or BAdI (but I don't know anything about BAdIs yet), to do this?
Thanks in advance,
Greg
Here's the logic I injected into EXIT_SAPLMLSR_001. I am hoping there's a simple change I can add to the middle to alert the tcode to stop saving. I'm also aware the loop iterates a few extra times given more than one duplicate found, but baby steps!
DATA: vendor LIKE ekko-lifnr,
purdocno LIKE ekko-ebeln.
if sy-tcode = 'ML81N' and sy-ucomm = 'YES'.
* Check for a Ref# match in existing sheets
SELECT ebeln INTO purdocno FROM essr WHERE xblnr = i_essr-xblnr AND loekz <> 'X' AND ebeln <> i_essr-ebeln.
* Having the match we now look at the vendor # to see if it is the same
SELECT lifnr INTO vendor FROM ekko WHERE ebeln = purdocno.
IF vendor = i_ekko-lifnr.
* abort!
MESSAGE ID 'RP' TYPE 'W' NUMBER '016' WITH 'Reference provided has been used by this vendor before!'.
* e_edit doesn't seem to do much for me...
e_edit = 'X'.
exit.
ENDIF.
ENDSELECT.
ENDSELECT.
ENDIF.
Bluesky
