Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Naming

Names are decided once, in lib/naming.js, when 11ty builds ddic.json. The Rust build only checks them.

ABAPRustRule
Standard table KNA1sap::Kna1Module sap, UpperCamelCase struct
/ACME/CONSENTacme::ConsentThe namespace becomes a module; slashes can’t appear in Rust names
ZSD_ORDER_LOGz::ZsdOrderLogZ and Y objects go in module z
Field KUNNRkunnrsnake_case
Field /ACME/GPCacme_gpcNamespace joined with _
Field TYPEtype_Rust keywords get a trailing _

Every field keeps its ABAP name on the wire through #[serde(rename = "…")], so a record reads and writes unchanged. Two ABAP names that would become the same Rust name stop the build.

Names in this book that needed more than lower-casing

TableABAP fieldRust field
KNA1/ACME/GPCacme_gpc
/ACME/CONSENT(table)acme::Consent

Shopify and YouTube names

The naming rules for the BigQuery transfers (Shopify Admin GraphQL objects, YouTube Channel and Content Owner reports) and the fields that join them across sources are in What is ABAP? → API reference naming.