Skip to content

Before You Process: What Happens in SAP

Whose user posts the change, what SAP records, what costs quota, which records are skipped, and the rules MDM keeps whatever happens.

Draft brief for authors. Replace with the final text; keep the concept-page structure.

Page type: Concept · Audience: Processor

Contains: whose user posts (named user or integration user; the confirmation says which); SAP's change documents; every record sent costs one unit of quota, accepted or rejected; records SAP already holds as staged are skipped (no quota); a change to a record SAP does not know is skipped; an operation SAP already shows as done is skipped; the description language and units follow your language; creates, deletes and operations are never sent twice.

Related information: concept-identity, concept-quota, concept-safety-rules, processing-now.

Source in the product repository: customer guide §5, decisions D42, D97 (SkipUnchanged), D162.

Last updated: