Is there a user exit, badi, bapi, etc... that is executed AFTER the save of a production order? We are currently using one (ZXCO1U06) but this is before the save. The issue is we are predicting the next production order number and, so far, it hasn't caused an issue (we are creating an idoc before the save, in this exit, but we need the production order number for this idoc) with an production order number being duplicated.
Right now I am determining the next PO# as follows:
SELECT SINGLE NRLEVEL INTO W_NRLEVEL FROM NRIV
WHERE OBJECT = 'AUFTRAG'
AND NRRANGENR = '14'.
IF SY-SUBRC = 0.
W_NRLEVEL = W_NRLEVEL - 20.
W_AUFNR_RANGE = W_NRLEVEL+8(12).
SELECT AUFNR INTO TABLE T_AUFNR FROM AUFK
WHERE ( AUFNR >= W_AUFNR_RANGE AND AUFNR < C_UPPER_RANGE ).
IF SY-SUBRC = 0.
SORT T_AUFNR DESCENDING BY AUFNR.
READ TABLE T_AUFNR INDEX 1.
T_AUFNR-AUFNR = T_AUFNR-AUFNR + 1.
W_NEXT_AUFNR = T_AUFNR-AUFNR.
SHIFT W_NEXT_AUFNR RIGHT BY 1 PLACES.
OVERLAY W_NEXT_AUFNR WITH C_ZEROS.
ENDIF.
ENDIF.
I would imagine that it would be possible for me to determine the PO# and then, before the PO gets saved, another PO is created which will take the next available number (Which will be the number that I determined and planned on using). I hope this makes sense. Basically the question is, is there such this as a user exit, badi, bapi, etc... which is called after a save.
Davis