Enhance Your Visualization and Analytical Capabilities for Accounts Receivable Aging Using SAP Lumira

  • by Anurag Barua, Independent SAP Advisor
  • August 7, 2015
Learn how a Fortune 500 company leveraged the visualization and ad hoc analytical capabilities of SAP Lumira to get a holistic view of its Accounts Receivable (A/R) and plan for effective remedial action to shorten the receivables cycle.
Learning Objectives

Reading this article, you will learn how to:

  • Prepare your source data prior to extracting it to SAP Lumira
  • Extract the data
  • Do basic and advanced navigation for analysis
  • Do advanced visualization and analysis using value-added features such as calculated or measured dimensions
Key Concept
SAP Lumira takes SAP BusinessObjects Business Intelligence (BI) self-service to a different level by making it easy for businesses to extract, prepare, and present data to business users in a highly visual manner, thereby helping accelerate analysis, trend-spotting, and, ultimately, speedy decision making.

Company XYZ, a Fortune 500 global manufacturing company, has long been plagued by poor collection of accounts receivable (A/R). In other words, XYZ regularly has large open A/R balances. This situation is called aging in financial accounting jargon and over time leads to understatement of income.

To analyze the data, my company recommended to XYZ that it take a manageable subset of receivables data from the vendor receivables table (BSID) of the production instance of the SAP ERP Central Component (ECC) 6.0 system. For the purposes of the prototype, it made the most sense to download the data dump to Microsoft Excel. Depending on the selection criteria you have used, you might end up with a large volume of data containing millions of rows. Because you know your data best and since this is a proof of concept (POC), you may want to limit it to one or two fiscal years or one or two company codes.

Now that the data is downloaded, I want to make sure that sensitive information is masked (in this case the customer name). For the actual customer POC, I keep it intact because analyzing by customer is one of the key criteria.


Anurag Barua

Anurag Barua is an independent SAP advisor. He has 23 years of experience in conceiving, designing, managing, and implementing complex software solutions, including more than 17 years of experience with SAP applications. He has been associated with several SAP implementations in various capacities. His core SAP competencies include FI and Controlling FI/CO, logistics, SAP BW, SAP BusinessObjects, Enterprise Performance Management, SAP Solution Manager, Governance, Risk, and Compliance (GRC), and project management. He is a frequent speaker at SAPinsider conferences and contributes to several publications. He holds a BS in computer science and an MBA in finance. He is a PMI-certified PMP, a Certified Scrum Master (CSM), and is ITIL V3F certified.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.