Solution : https://service.sap.com/sap/support/notes/894463 (SAP Service marketplace login required)
Key words :
terms mam notification badi alm_me_010_notif ci_qmel viqmel customer extension updating customizing iqs1_fill_buffer_from_wa iqs1_fill_wa_from_buffer, prerequisites reason-------mam standard implementation clears internal buffers, update customer extension fields included, updating customer extension fields, mam notification badi, implemented badi alm_me_010_notif, customer include ci_qmel, implemented ci_qmel structure, badi customer, prerequisites--------------customer
Related Notes :
| 894158 | Necessary corrections for MAM3.0 |
| 876001 | MAM: User status of PM/CS notification tasks |
| 855894 | MAM: User status of PM/CS notification tasks |
| 840331 | MAM: Closing dates of tasks are not transferred |
| 823446 | MAM: Tasks for PM/CS notifications are not created |
| 807252 | Deactivating components that are not required |
| 781890 | Corrections for MAM 2.0 SR 5 |
| 774820 | Problems when changing notification long texts |
| 771676 | Invalid material/serial number combination |
| 760588 | Error in date when creating and changing notifications |
| 759768 | Changing technical objects in notification does not function |
| 758727 | MAM: Error in partner check when order/message created |
| 742828 | MAM: Partners not transferred during notification creation |
| 734915 | Notification header fields are deleted during change |
| 730825 | Required corrections for MAM 2.5 |
| 727542 | MAM message processing: Initial start and end of fault |
| 723380 | Mobile Asset Management 2.5 - Composite Note |
| 722892 | MAM required corrections for MAM in PI 2004.1 |
| 617494 | Mobile Asset Management 2.0 - Composite Note |