Name: Finding and Interpreting Import Logs in SAP SuccessFactors Incentive Management
Uploaded: 2020-9-14
Duration: 292 s
Description: In this video, we'll show you how to troubleshoot data import errors. You’ll also learn best practices when it comes to reviewing log files. I’ll show you how to find and resolve errors in the user interface and how to find and interpret errors in the log files.

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><p>In this video, we'll show you how to troubleshoot data import errors. You’ll also learn best practices when it comes to reviewing log files. I’ll show you how to find and resolve errors in the user interface and how to find and interpret errors in the log files.</p></div></div></div>

Finding and Interpreting Import Logs in SAP SuccessFactors Incentive Management

Hi! My name is Lily. In this video, I’ll show you how to troubleshoot data import errors. I’ll first cover ways to find and resolve errors in the user interface. Then, I’ll show how to find and interpret errors in the log files. Logs are created and stored as text files and are accessible either in the pipeline run record or from the Processing Logs section of the Sales Performance Home page. We will look at an example of a set of transactions that have been imported into the system that have an invalid Event Type. We ran the validate And transfer process to move these Transactions into production. Once the Validate and Transfer process is complete, you can see a list of errors in the Validate stage. Details on these errors are displayed on the Errors tab. Here, we can see that that the error is caused by an invalid Event Type on the Transaction. You can also view individual import records in the Staging Table if you would like to see more detail on these errors. This may help identify the exact issue with each record that returned an error. From the Run menu,  I’ll go to Pipeline – Stage Tables From the Table Name menu, I’ll select Transaction To filter only records with errors, from the Stage Process Flag menu, I’ll select Error and click OK. Note the Event Type is outlined in red. Hovering over the Event Type shows the same error. We know from this, that the Licenses event type hasn’t been created. This can be resolved by adding the Licenses event type in the Global Values menu. Now that the issue has been resolved, the next step is to re-run the Import process with the Revalidate switch turned on. Revalidate is a process used when you’ve done an import to a stage table and received an error, after you fix the error, rerun the reimport with the revalidate switch turned on. Before you rerun the Pipeline, you will need the batch name. You can find the batch name on the far right-hand side of the Staging Table. In this case, they all have the same batch name. You can’t copy from here.  You’ll just note it down or copy it from the original process. To rerun the import and make sure that the previous errors are overwritten, I’m going to run another Pipeline. I’m going to go to the Run menu. Select Pipeline. Click the Start Pipeline icon. I’ll select Import data from stage. Then,   I’m going to enter the batch name. I’ll select Validate  I’m going to select the Revalidate checkbox. If I don’t do this, the system will ignore the errors, and nothing will get imported. Now, I’ll select Transfer. I’m also going to select Transfer valid data only if all the data is valid. I’m going to be importing Transactions and Credits, I’ll add that to the list.  From here, I’m going to keep clicking next until I get to Start. As you can see, the Pipeline is done running and was successful. Under the Validate State, I have 74 validated transactions and 74 transferred transactions. That means I had no errors. I’m going to go back to Stage Tables. I’m going to make sure I’m on Transaction. I’ll click OK to refresh. You can see that all of these are now transferred. The easiest way to tell, is to go to the far right, and you can see they’re all Transferred. I’m go to my Transactions workspace. And I can see that my Transactions are all there. I’ve shown you the importance of using the Revalidate checkbox to make sure that your files are actually revalidated if you had errors in the first run. In some cases, you may see an error that can’t be easily interpreted in the user interface. If this happens, re-run the import process with verbose logging enabled, and inspect the log files. The import process returns several log files. We’ll focus on the Validate log and the Transfer if All Valid log. The Validate log shows the details of record validation and is most likely to contain any errors that prevent your import from happening. Other log files show the results of other processes, such as Analyze Import and Transfer If All Valid. The Summary log shows a summary of all processes. This example shows a log file for an import in which duplicate records are imported in the same file, returning a Unique Constraint violation. Pos=9 refers to a Position. Correcting the duplicate record in the import file would resolve this issue. Again, after correcting the data, when re-running the import Pipeline, be sure to check the Revalidate checkbox. In this video, I showed   you how to troubleshoot data import errors. Thanks for watching!