PackagePackagetypeA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

codepage

A polyfill class, ZCL_ABAP_CODEPAGE, that converts strings to binary and back behind one interface, where Clean Core blocks CL_ABAP_CODEPAGE and older systems lack CL_ABAP_CONV_CODEPAGE.

SAP's CL_ABAP_CODEPAGE handled string-to-binary conversion for formats such as XML or JSON, but Clean Core now blocks its use, and the class it points to instead, CL_ABAP_CONV_CODEPAGE, is not present in older systems. ZCL_ABAP_CODEPAGE wraps the conversion behind one interface, with to() and from() methods that round-trip a string through binary, so the same call works whichever class the system underneath actually allows. It carries its own round-trip unit test and depends, for its tests only, on two other abapify projects, assert and throw.

Facts

Latestv1.15.0ReleasedLast pushLicenceMIT

Where it sits

Lives in
Provides
ABAP Cloud readinessABAPABAP Cloud readinesscapabilityWhether code can run in ABAP Cloud — released APIs only, no direct table access, no obsolete statements — and what to do with the code that cannot.

Who is behind it

abapifyabapifyOrganisationMaintains this
In the atlas: maintains 9
@abapify
maintainerPetr PlenkovPersonContributes to this
In the atlas: contributes to 13
@ThePlenkov
1 contributor

What it declares

Every artifact

Type
Package
Origin
Independently maintained

As a package

Where it runs
does not say
Distributed through
does not say

Connections2

README

quoted from abapify/codepage under MIT, read
abapify/codepage/README.mdOn GitHub

Codepage polyfill

It never happened and it happened again. Clean core requires a new class for code page and the old class is not allowed.

Why?

CL_ABAP_CODEPAGE was a class SAP introduced long time ago and it was efficiently handling string <-> binary conversion for UTF-8 documents such as XML or JSON or whatever else.

We can see that is still present in a new ABAP documentation snippets. image

However it turned out to be one more example when "Clean Core" concept simply prevented us from using this class: The use of Class CL_ABAP_CODEPAGE is not permitted

image

So what should we use instead? Well there is another nice class which we can use: CL_ABAP_CONV_CODEPAGE

Introducing one class in a new environment which is not present in the old environment prevents us from reusing the code. Polyfill approach allows us to use one class which will work in any system.

ZCL_ABAP_CODEPAGE

Rountrip example from the unit test

data(test) = |This is a sample string|.
" String to xstring ( to codepage )
data(lv_binary) = zcl_abap_codepage=>to( test ).
" Xstring to string ( from codepage )
assert( zcl_abap_codepage=>from( lv_binary ) )->eq( test ).

Test Dependencies

MIT, read

History

Latest

v1.15.0

  1. v1.14.0

  2. v1.13.1

  3. v1.13.0

  4. v1.12.2

  5. v1.12.0

  6. v1.11.1

  7. v1.11.0

  8. v1.10.2

  9. v1.10.1

  10. v1.9.0

  11. v1.8.1

  12. v1.8.0

  13. v1.7.0

  14. v1.6.0

  15. v1.5.0

  16. v1.4.0

  17. v1.3.8

  18. v1.3.7

  19. v1.3.6

  20. v1.3.5

  21. v1.3.4

  22. v1.3.3

  23. v1.3.2

  24. v1.3.1

  25. v1.3.0

  26. v1.2.0

  27. v1.1.0

  28. v1.0.0

  29. v0.6.0

  30. v0.5.3

On npm
7,736,394downloads per week, npm
Weekly downloads for codepage26 complete calendar weeks from 2026-04-20 to 2026-10-18; the latest total is 7736394.20 Apr – 26 Apr: 11,116,35327 Apr – 3 May: 10,259,6914 May – 10 May: 10,599,67011 May – 17 May: 11,149,91518 May – 24 May: 11,206,03725 May – 31 May: 10,637,9561 Jun – 7 Jun: 9,320,1838 Jun – 14 Jun: 11,813,83515 Jun – 21 Jun: 12,408,84122 Jun – 28 Jun: 11,659,37229 Jun – 5 Jul: 11,320,1246 Jul – 12 Jul: 11,187,64313 Jul – 19 Jul: 12,226,17520 Jul – 26 Jul: 12,357,82427 Jul – 2 Aug: 12,809,1393 Aug – 9 Aug: 12,932,25410 Aug – 16 Aug: 11,100,45817 Aug – 23 Aug: 13,180,67724 Aug – 30 Aug: 13,436,18731 Aug – 6 Sept: 11,983,0827 Sept – 13 Sept: 9,835,39314 Sept – 20 Sept: 12,397,19921 Sept – 27 Sept: 15,559,41928 Sept – 4 Oct: 16,405,4385 Oct – 11 Oct: 13,774,40712 Oct – 18 Oct: 7,736,394
ABAP Cloud readiness
  1. abap-cloud-guiReport-style programming model for abap2UI5 on ABAP Cloudfrom ABAP
  2. Modernization Agents for SAP on AWSAWS agents for ABAP, PI/PO and BW modernisation workfrom ABAP
  3. ROSAMCP server answering whether SAP objects are released for ABAP Cloudfrom ABAP
  4. Cloudification RepositorySAP's list of released APIs for SAP Cloud ERP with successorsfrom ABAP
  5. code pal for ABAP — Cloud EditionClean ABAP check set for ABAP Cloudfrom ABAP
  6. Clean-Core.ioHosted workspace redrawing custom ABAP as BPMN and grading itfrom ABAP
  7. Clean Core MeasurementReports Clean Core ATC results per system as Level A to D KPIsfrom ABAP
  8. ABAP Select ConverterConverts classic Open SQL SELECTs to released CDS entitiesfrom ABAP
  9. abap-system-fieldsInjectable wrapper for SY fields and date functions in ABAP Cloudfrom ABAP
  10. Cloudification Repository ViewerBrowser form over SAP's Cloudification Repository for ABAP Cloudfrom ABAP

Details

Sources3
Added by handdiscovered herechecked
github.com/git://github.com/SheetJS/js-codepage.gittree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
latestv1.15.0
first release
releases and cadence31, ~33d median
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, operations-and-runtime
abaplint
issues under its own abaplint configuration0
lines90
statements46
objects2
files3
analysed, main
abaplint version2.120.84
Contributors1

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:abapify-codepage
JSON
/artifacts/abapify-codepage.json
MCP
Connecting an agent