Name: Finding and Interpreting Pipeline Verbose Logs in SAP SuccessFactors Incentive Management
Uploaded: 2021-6-25
Duration: 276 s
Description: Learn what is verbose logging and how to use it. Find a detailed demonstration on finding errors in the Pipeline Details section. Know how to trace the cause of error in the log files. Also, get to know a few best practices to review 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><div>Learn what is verbose logging and how to use it.  Find a detailed demonstration on finding errors in the Pipeline Details section. Know how to trace the cause of error in the log files. Also, get to know a few best practices to review log files.</div></div></div></div>

Finding and Interpreting Pipeline Verbose Logs in SAP SuccessFactors Incentive Management

Hello and welcome!  My name is Varsha.  In this video, I’ll discuss how to use verbose logging  to find and interpret pipeline issues in SAP Commissions.  After running a Pipeline, you can use log files to help diagnose the Commission system and rule behavior, and to browse errors, warnings, and processing statistics.  In some cases, the issues can be more difficult to find or interpret.  Let’s look at a few common issues that can be investigated with log files.  Sometimes you come across pipeline results data that are incorrect.  For example, one of the Positions is receiving an incentive payout that is the same as the Measurement.  Data or date formats are causing your output to calculate incorrectly or to have no result.  A simple mistake in a rule, such as a null value in a quota, or a variable that hasn’t been assigned.  If you experience an error or warning that you can’t identify in the user interface,  enable Verbose Logging and Rerun the Pipeline.  You can enable this option on the Advanced Logging page of the Pipeline Wizard.  It’s recommended that you filter logging by affected Position, Participant, Credit Rule, or Transaction.  When you enable logging, the size of the log files impacts the Pipeline run process and slows it down.  Look for errors displayed in red in the Stage Statistics view of the Pipeline record.  To identify which log file contains information about the error,  view the Pipeline Summary log.  In the Sales Performance Homepage, open Processing Logs.  Open the folder for the Pipeline period.  In this case, January 2021.  Open the Summary folder.  Click the Pipeline Summary.log to download the file.  Find the error in the Pipeline Summary log and identify the corresponding stage and worker.  This can be very helpful as some processes, such as Reward, can create multiple worker logs.  Go back to the list of logs and download the log file that corresponds to this stage and worker.  Let’s look at an example.  We are looking at a line in the Summary Log file that shows an evaluation error in the Reward stage.  Note the worker is Worker-zero.  This means that we can resolve this by returning to the Sales Performance Homepage,  where we can find the Reward logs.   Remember that the error is in Worker0,  so we’ll open Reward_Worker0 logfile.  We can find the related section of the file by doing a simple search.  We can clearly see that the evaluation error is in a rule called IR_Licenses Monthly Commission_AE,  and the cause is a null quota.  You can also use verbose logs to identify the cause of performance issues.  This could include very slow pipelines or worker distribution.  To do this, rerun the Pipeline.  Enable Performance Statistics on the Logging Options screen.  Performance Statistics for each file can be found in Sales Performance Home under the Profile folder.  A common issue that affects performance is distribution of workers.  A very large reporting hierarchy and plans that roll large amounts of data between positions, will use only a single worker than allow load distribution.  The Island Analysis log shows the number of microseconds used in each process.  It’s a useful log to get started with performance analysis.  Here are some best practices when it comes to reviewing log files.  See if the Pipeline run returns an error in the user interface before reviewing log files.  Run in Verbose mode only when you need to.  Filter when possible to keep the size of the log files from getting too large.  Start with the Pipeline Summary log to identify which log file contains the error details.  In this video, we learnt what is Verbose logging and how you could use it to find and interpret pipeline issues in SAP Commissions.  Thanks for watching!