on 05-10-2010 9:59 AM
Dear expert,
I release a notification using BAPIs:
BAPI_ALM_NOTIF_TASK_RELEASE
BAPI_ALM_NOTIF_SAVE
BAPI_TRANSACTION_COMMIT
the notification can be released successfully, but the I found the fields"changed by", "changed date" and "changed time "
could not be updated.
If I use trx IW22, everything was ok.
Could you please tell how to deal with it?
best regards
Hello,
These BAPIs can not update that field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You will have to call BAPI_ALM_NOTIF_DATA_MODIFY or other FM to change the notification header data, since the other two BAPI that you have used are very specific in nature and doesn't update the header information.
Regards
Narasimhan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Thank you for your reply. I tested as you told, but it's not working.
The tasks in the notification can be released using those BAPIs, however the "changed by", "changed on", "time of change"fields
still could not be updated.
If I release tasks by clicking green flag icon(release), everything was OK.
Best regards
Edited by: Stephen Wang on May 11, 2010 2:05 PM
Edited by: Stephen Wang on May 11, 2010 2:08 PM
Stephen,
I thought you were referring to the header of the notification.This is the one that will not be updated, when using these BAPI.
If you are changing the task associated to the notification at the header level, these BAPI should work and the changed by , changed on and changed at should get updated at the task level, when using these BAPI. I did write a quick custom code to check this out on ECC 6.0 and they work perfectly.
Please check the OSS notes for help on these BAPI.
Regards
Narasimhan
User | Count |
---|---|
110 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.