Hi SAP Community,
I’m encountering an issue during the “Prepare” step of an asset value posting migration using LTMOM and the Data Migration Cockpit. We’ve built a custom LTMOM solution around the BAPI BAPI_FIXEDASSET_OVRTAKE_POST to migrate asset postings (similar to AS92 functionality). We upload a custom data template, but the process fails at the Prepare stage with the error: “Cannot save message to application log; see long text.”
The long text provides minimal information:
Diagnosis The application tried to save a message to the application log, but some information about the message is missing. This means that the message cannot be saved to the application log. The following information is available: Message type = E Message ID = Message number = 000 System Response Cannot save message to application log.
- Field Mapping: I’ve reviewed the field mapping in LTMOM, but I’m unsure which specific fields are required for the application log itself. Could someone please provide a list of the essential fields that must be mapped for logging purposes (e.g., LOG_ID, OBJECT, MESSAGE_TYPE, MESSAGE_ID, MESSAGE_NUMBER, MESSAGE_TEXT)? Do these need to be mapped even if I’m not actively using the application log?
Could anyone offer suggestions on what might be causing this error and how to resolve it? Any insights into the required field mappings for the application log in LTMOM would be greatly appreciated. If you’ve experienced a similar issue, please share your solution.
Thanks in advance for your help!
Regards
Ramiwal
This error occurs before the BAPI is called, indicating a problem with the migration framework itself. I suspect it’s related to missing or incorrect field mappings related to the application log.