Naming
Names are decided once, in lib/naming.js, when 11ty builds ddic.json. The Rust build only checks them.
| ABAP | Rust | Rule |
|---|---|---|
Standard table KNA1 | sap::Kna1 | Module sap, UpperCamelCase struct |
/ACME/CONSENT | acme::Consent | The namespace becomes a module; slashes can’t appear in Rust names |
ZSD_ORDER_LOG | z::ZsdOrderLog | Z and Y objects go in module z |
Field KUNNR | kunnr | snake_case |
Field /ACME/GPC | acme_gpc | Namespace joined with _ |
Field TYPE | type_ | 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
| Table | ABAP field | Rust field |
|---|---|---|
KNA1 | /ACME/GPC | acme_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.