CapabilityProtocols & APIsStandard ABAP, read from its artifacts

Serialisation

Turning typed in-memory data into a text or binary format such as JSON, CSV or protobuf and reading it back, including the mapping of names and types the language does not do for you. The protocol that carries the payload is a separate concern: an HTTP or OData client moves the bytes, and serialisation decides what they say.

Showing artifacts, examples and content with confirmed Standard ABAP applicability. View All ABAP

Overview

SAP SHIPS

No SAP artifact is confirmed here for Standard ABAP.

A Standard ABAP coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS

ZASIS

ABAP Architect

Writes the ABAP side of reading a JSON or XML payload from a pasted sample of it: TYPES structures and table types, a /ui2/cl_json=>name_mappings table for the names that differ, cl_ixml parsing code and tt:transform source for XML.

Sourcemurattahtaciii/abap-architect — README, Featureschecked 2026-10-01

ABAP CSV Manager

A Standard ABAP coverage assessment has not been written. View all flavors

Artifacts3

3 of 3 artifacts

ArtifactSignals

IDE extensions1

ABAP ArchitectEclipse plug-in turning JSON or XML into ABAP types and DDIC objects

Signals

Functional boundary

Packages2

ABAP CSV ManagerConfigurable CSV reader and writer for ABAP

Signals

none

ZASISRegex RuleSets that read barcode strings into named fields

Signals

Functional boundary

Details

Coverage

statecommunity only, ABAP, Standard ABAP, derived

domainProtocols & APIs

For your agent

Ref: capability:serialisation
JSON: /capabilities/serialisation.json
MCP: Connecting an agent