SAP Knowledge Base Article - Preview

1861180 - Collecting an end to end trace in BI Platform 4.x - customer instructions and best practice [Video]


  • A known workflow in a browser based client (eg. Central Management Console / CMC, BI Launchpad / BILP) causes an issue in the BI Platform
  • It is required to generate an End-To-End trace (E2E)

 "Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."



  • SAP BusinessObjects Business Intelligence Platform 4.x (BI 4.2 / 4.3)


SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.0, feature pack 3 ; SAP BusinessObjects Business Intelligence platform 4.1 ; SAP BusinessObjects Business Intelligence platform 4.2


end 2 end, diagnotics, logging, root cause analysis, diagnostics, GLFViewer, steps, tracelog, sap_log_level, sap_trace_level, debug, workflow, tskba, tlkba, bidep, biserver, biadmin , KBA , htkba , biadmin , bidep , biserver , tskba , tlkba , vkba , bpkba , bi4 , landscape report , gscnawest_video , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , BI-BIP-PER , Performance investigation , BI-RA , Reporting, analysis, and dashboards , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.