Name: Understanding Data Load Monitor in SAP Marketing Cloud
Uploaded: 2019-8-30
Duration: 197 s
Description: In this video, you'll learn how to use Data Load Monitor to trace import warnings and errors, and how to rerun an import after resolving the root cause.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div><div><div>In this video, you'll learn how to use Data Load Monitor to trace import warnings and errors, and how to rerun an import after resolving the root cause. </div><div><br></div><div><br></div></div><br></div><br></div></div></div></div></div>

Understanding Data Load Monitor in SAP Marketing Cloud

As a marketing administrator, you need to ensure that data flows into the SAP marketing Cloud system correctly. Here's how we support you in safeguarding the quality of data imports. Let's see how you can use the data load monitor to trace import warnings or errors, and rerun an import after having resolved that root cause. The monitor evaluates asynchronous data import, and on this screen, list all the messages that occurred in the system, such as error messages and success confirmations. This provides you, as an administrator with a to do list that you can work through message by message. Use the visual filtering to narrow the list down for an explanation of all available sort and filter options. Watch the analytical live page Video. Let's pick this morning. It's about an invalid phone number format in the source data. To view the details, click here. The diagnosis says the leading plus or zero zero is missing. This needs to be corrected in the data source. Let's take another example. This time we'll use the more detailed filtering. Let's check for errors due to missing origins. There are multiple search filters available. For example, we can search for origin in the message text field. Then to narrow the hit list down, we can search on the import service name. And there we have it. Message number 27. How about missing origin errors? For the details about the origin error. Click here. The page provides a message summary. Clicking the import header ID navigates you to the import monitor for further analysis of the selected data. Import. Watch the video checking the data load for more insight on this. For now, we'll use the data preview to identify the missing origin. Okay, the fail data record identifies the origin that is missing. The next step is to configure the missing origin in the system. Once this is done, we can restart the data import. Close the data preview and return to the data load monitor. Press restart all to Re-import. All data sets where the missing origin was detected. Data import is running now. Reset the filters to view the full list of data import messages. No more messages about missing origin. Excellent. We recommend that you regularly check the data load messages to keep a clean desk, and to safeguard the quality of your data imports.