Skip to Content
Author's profile photo Tridip Chakraborthy

the UNSPSC story for SAP Procurement folks

when SCN migrated from the old version into JIVE, I got a lot of emails from folks on where the blog for this as well as the article had disappeared. Hence, I am re-posting this blog with updated tags, so that it reaches SAP Procurement folks that want to understand the concepts behind UNSPSC and what it means to the SAP Procurement world.

Direct link to download the article:

Overview blog of the article below

SRM and Procurement consultants in most projects hear this term on and off, most business folks on the other side in the implementation are quite aware of the standards and expect that they get the most from the availability of standards that are already available in the marketplace.
In a challenging Punch-out implementation, we went the extra mile with the Vendor with the UNSPSC related mapping guidelines.
Customers often ask questions like
– How much do we Spend?
– On which products?
– From which suppliers?
….Questions can be many?

Answer is adoption to a Standard… Open Standard

Alignment with Procurement standards and following best practices helps realize bottom-line benefits and why not use something that’s an Open Standard and used by the most successful businesses. The bottom line is to exploit the most out of the electronic commerce capability that’s out there.

So going down the same storyline, I have posted a very detailed article that cuts across the concepts of UNSPSC and the way it must be used to craft complex Catalog implementation projects and also Category management initiatives in SAP Sourcing and SAP CLM. The whole idea is to provide great downstream data thats required for Spend Analytics to make those critical CPO decisions.

To make it further interesting, I have showcased below, the table of contents of my article

Link to the article

Table Of Contents

1.0 UNSPSC 101

1.1 The Basics…Introduction

1.2 What is an Open Standard?

1.3 What is Taxonomy?

1.4 UNSPSC Design

1.5 What are UNSPSC Segments?

2.0 Benefits of UNSPSC

2.1 Value of implementing UNSPSC

3.0 What it means to SAP Procurement applications

3.1 Doing it the Right way

3.2 Punch-out Catalog implementations

3.3 Another example….SAP Sourcing Category Management

4.0 Conclusion

Related Content

Do read it, benefit from it and ensure you help the customer adopt to these standards in your day to day work and challenging implementations, upgrades, roll-out’s BPR’s etc

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Hi Tridip,

      i haven't tried to pronounce it quickly recently, but it seems to be the standard in the procurement function. do you know if there are any ISO's that go with it?



      Author's profile photo Tridip Chakraborthy
      Tridip Chakraborthy
      Blog Post Author

      Hi greg can you please detail out your question



      Author's profile photo Former Member
      Former Member

      in no particular order, i'm somewhat familiar with the following ISO's:

      8859 - encoding

      17799 - security

      20222 - SWIFT

      i was wondering if UNSPSC has its own ISO or not.

      i hope this clarifies,

      thx, greg

      Author's profile photo Former Member
      Former Member

      actually, it's 20022 for swift and 27001 & 27002 for security, my mistake.

      Author's profile photo Tridip Chakraborthy
      Tridip Chakraborthy
      Blog Post Author

      Hi Greg, Gregory Misiorek

      I dont think there is any specific ISO coding in UNSPSC

      the way, we went about doing it is

      - Create / use an existing UOM in R/3 and map it to its ISO code

      - replicate that UOM to SRM

      - Map it to the Product Category using the BADI so that the UNSPSC maps to the Internal Product Category in SRM / Material Category in ECC

      The reason, you need to go with the ISO mapping that's already available, as when you punch-out for catalogs, that ISO needs to be somehow mapped b/w your SRM system and the OCI provider, so that when the item is pulled back, there are no compatibility issues

      I hope that answered your question in some form

      However, what business process you are trying to achieve would make it more easier to recommend something