SAP GUID Converter

Instantly convert between Raw (16-byte), Hyphenated (UUID), and Base64 (Compressed) SAP formats.

How SAP GUIDs Work

In the SAP ecosystem, Global Unique Identifiers (GUIDs) or Universally Unique Identifiers (UUIDs) are used extensively for primary keys in database tables (like BPEG, CRMD_ORDERADM_H).

SAP typically stores these as 16-byte raw binaries (RAW16). However, developers often encounter them in different representations depending on the interface:

  • Raw (Hex 32): The direct hexadecimal representation of the 16 bytes. Commonly seen in ABAP debuggers (variable type SYSUUID_X16).
  • Hyphenated (Standard UUID): The industry-standard RFC 4122 format (8-4-4-4-12 hex chars). This is standard for OData v2/v4 services and external APIs.
  • Base64 (Compressed): A shorter, 22-character string usually used in URLs or legacy web interfaces to save space. It encodes the 16 bytes into Base64 and strips the padding (==).

This tool handles the conversion logic automatically. It uses bitwise operations to transform the binary data between these string formats, ensuring compatibility whether you are debugging ABAP code, calling an OData service, or inspecting a payload.

Understanding SAP GUID Formats

SAP systems use Global Unique Identifiers (GUIDs) extensively for primary keys in tables like BUT000 (Business Partner) and CRM_ORDERADM_H. However, different interfaces require different formats.

Raw (16-Byte)

The internal binary format stored in the database (e.g., RAW16). Used in ABAP SQL queries and debugger variables.

0050568D25CA1ED78B8C1B4F3F8B20B2

Hyphenated (UUID)

Standard RFC 4122 format. Required for OData APIs, external integrations, and JSON payloads.

0050568D-25CA-1ED7-8B8C-1B4F3F8B20B2

Base64 (Compressed)

A 22-character string used in URLs and legacy web dynpro applications to save space.

AFBWjSXKHtJujBP5PxvAy==

Common Use Cases

  • 1Debugging OData Services: When testing Gateway services (`/IWFND/MAINT_SERVICE`), you often need to convert the raw GUID from table /IWFND/I_MED_SRH into a hyphenated UUID for the URL.
  • 2HTTP Client Traces: Analyzing payload traces in SMICM or SRT_UTIL often reveals GUIDs in Raw format, which you need to format to query in SE16N.
  • 3Integration Flows (CPI): Mapping valid UUIDs between non-SAP systems (like Salesforce) and SAP S/4HANA often requires removing hyphens or converting to Base64.