FK05 - BADI / U Exit / Enhancements on SAVE-COMMIT

[former_member599326]

Hi,

I want to know if there is any BADI / U EXIT / Enhancement available for tcode FK05 on SAVE commit.

I found below BADI / u exit.

BADI - VENDOR_ADD_DATA

BADI - VENDOR_ADDRSCR_CHG

User Exit - ZXF05U01

But above BADI / u exit triggers on pressing save button immediately i.e. before commit.

I want enhancement which will get triggered after commit to database happened so that I can perform next activity e.g. update table in CRM.

Pl. help.

Regards,

[Former Member]

I doubt that there is an exit that runs exactly after all changes have been saved.

How about implementing your logic in an update function module and call it in UPDATE TASK from one of the exits you mentioned? This way it will only take effect if the vendor master is actually updated (a COMMIT WORK is issued by the transaction).

[raymond_giuseppi]

What will you do after the update?

• If you only use simple SQL statements (e.g. insert into a custom Z table), embed your code in an FM UPDATE TASK (V2 - delayed start) that you can trigger AT SAVE, CALL FUNCTION ZXXXX IN UPDATE TASK.
• If you need a COMMIT or a new LUW (e.g. calling a BAPI), embed your code in an RFC enabled FM that you can also trigger AT SAVE, CALL FUNCTION ZXXXX IN BACKGROUND UNIT (or, obsolete, TASK).

In both cases, the registered FM will be executed once the FM update task (V1) are completed.