Tips on SAP SCM & Spend Performance Management from Kimberly-Clark's implementation

by The Tip Doctor

December 12, 2012

What is Spend Performance Management, and why, when and how do companies put this solution into place? Kimberly-Clark's Brian Bleck and Matt Boughton shared their experiences with the why's and how's of SPM in a detailed session on SAP's offering -- taking the audience from evaluation and use case to implementation tips and post-implementation concerns.

This session, "Case Study: How Kimberly-Clark Implemented a Global Spend Analytics Platform and Gained Control of Spend Data in Less than 20 Weeks", was presented by SAPinsider's Logistics and Supply Chain Management 2012 conference. The following tip is an overview of SPM and some quick implementation concepts, taken from their longer, detailed session:

Core Components of SPM Solution

  • Spend data extraction
    • From SAP and Non-SAP sources
  • Master and transactional data
  • SPM Data Model and Reporting/User Interface
    • Standard content/Business Intelligence data model
    • Adobe Flex user interface
    • Handles all language character sets – Unicode-based
  • Data Standardization and Enrichment
    • Spend Classification to a taxonomy
    • Supplier Enrichment
    • Supplier Normalization
    • Language conversion supported by DSE and Bristlecone services

SPM ERP Extractors Will Give You a Start on Acquiring Data

  • For SAP systems, there are SAP delivered extractors for:
    • SAP ERP: 4.6C, 4.7, ECC 5.0, and ECC 6.0
  • The starter kit can be downloaded from SAP Note 1239883
  • Pay very special attention to the exclusion of data
    • You DO NOT want all PO and Invoice data
    • Exclude by GL, vendor account group, material type, etc.
    • Exclude Employee data; exclude or separate Intercompany spend

NOTE: Extractors are a “starter kit.” You will need to customize them based on exact data requirements, your particular design and to obtain satisfactory performance. 

Base Steps to Configure and Run the Extractors

  • SM30 (ZSA_FFCUSTTABL): Configure the output directory,  filename and delimiter (technical)
  • SM30 (ZSA_D_FLDVAL): Maintain the exclusion table
  • SM30 (ZSA_GLSPLIT): Maintain spend split table (optional)
  • Z_SA_DEPD: Review the metadata and generate the extractor program
  • Z_SA_EXTR: Select and run the extractor for a chosen object
  • Z_SA_OBJ_SCHE: Schedule the extractor on the background

Key Performance Issues to Address

  •  SAP ERP Extractors and data load
    • Be current on all SPM patches to obtain data load improvements
    • Partitioning of InfoCubes; create the right indexes to support loads and SAP
  • ERP data extraction
  • User Interface log in
    • Application launch time – SAP Note 1584145 – reduce reads on table 0PM_PS_ITEM_DET during log in
  • Returning reporting results back to the User Interface
    • Java Memory usage dependent on the number of cells (rows * columns) returned to the screen
    • Set a cell limit. After this cell limit is reached users receive a “limit exceeded” message.
    • Set up appropriate filters and train users to use them!
    • Remove ability to drill down to detailed reporting (transactions)
    • Fits strategic message of the application

For more on SPM, be sure to attend the upcoming Logistics & Supply Chain Management 2013 conference in Las Vegas, March 19-22.  You can read the Kimberly-Clark case study from InsiderPROFILES here.

An email has been sent to:

More from SAPinsider


Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!