Hi,
I am sorry I cant seem to figure this one out....
Perhaps the generel info below will be of some help...
The function module called up at event 1025 reports changes to contract accounts to interested applications, for example, if a change to fields of the contract account should trigger a follow-up action.
The event is triggered both during contract account changes in dialog or direct input (at BDT event DSAVE) and when using BAPIs. Simultaneously changing several contract accounts generates an individual call of the event per contract account.
The import structure IS_FICA_CHANGES makes the status of the monitored fields of the contract account concerned available both before and after the change.
Notes
Programming Restrictions
To ensure the consistency of the system, note that you must not use the following language elements in events:
COMMIT WORK
ROLLBACK WORK
CALL FUNCTION 'DEQUEUE ALL'
Deletion of locks that you have not set yourself.
If you update additional data in an event and use the construction PERFORM commitroutine ON COMMIT to do this, note that:
At the end of the commitroutine, all internal tables from which data was updated must be initialized again to prevent a duplicate update in the next call.
A PERFORM rollbacktroutine ON ROLLBACK must also be called. In the rollbackroutine initialize the same data that is initialized at the end of the commitroutine.
If you want to carry out checks in an event, when you issue messages, note that background processing of the process terminates with warning messages. You should therefore avoid issuing warning messages if possible. However, you should definitely issue warning messages if the value of SY-BATCH is initial.
Parameters
IS_FICA_CHANGES
IV_UPDTASK
Regards
Olivia
