Key Concepts
Tasks and staging, the identity SAP sees, changes and quota, editions and releases, languages, and the safety rules MDM never breaks.
Draft brief for authors. Section page. Short explanation pages the task topics link to instead of repeating the theory.
In this section
- Tasks, Staging and RecordsThe staging area as a safe copy, one Task per upload and object, the statuses, and typed rows versus file rows.
- The Identity SAP SeesWhether SAP records a change under your own user or under the integration user, how to tell which applies, and what it means for authorizations and change documents.
- Changes and QuotaWhat costs a unit of your add-on's quota, what does not, where to see the use, and what happens at the limit.
- Editions and ReleasesPublic Edition versus Private Edition, how MDM detects your release and applies only what it knows for certain, and what differs for you.
- Languages: The App, the Template and SAPThe app language, the language MDM sends to SAP, descriptions stored per language, units per language, and files prepared in one language and used in another.
- What MDM Never DoesThe rules MDM keeps whatever happens: never sends a create, delete or operation twice, never retries an unknown outcome by itself, never guesses, never changes SAP on an upload or an edit.
Last updated: