SAP MDG · REPLICATION INBOUND
How do I implement the main SAP MDG inbound proxy method flow for customer, vendor, STA, CRA, or supplier-change classes?
Use the interface method as the entry point, then follow the class’s main stages in order: create or refresh the change request, validate the inbound payload, write the log, and then update ERP or send notifications. The catalog explicitly identifies this pattern for customer, vendor, STA, CRA, and supplier-change inbound classes.
Use the interface method as the entry point, then follow the class’s main stages in order: create or refresh the change request, validate the inbound payload, write the log, and then update ERP or send notifications. The catalog explicitly identifies this pattern for customer, vendor, STA, CRA, and supplier-change inbound classes.
The inbound proxy catalog shows a consistent runtime pattern across the ZCL_SI_* classes: start with the interface method, then create or refresh the MDG change request, validate the payload, write logs, and finally update ERP or trigger a notification. For customer and vendor inbound, the method names are documented explicitly; STA, CRA, and supplier-change classes follow the same general structure with their own entity-specific helpers.
Process flow
- Call the proxy interface method first.
- Create or refresh the MDG change request.
- Validate the inbound payload.
- Write logs in a dedicated method.
- Update ERP or send a notification after successful processing.
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is the runtime sequence in SAP MDG inbound proxy classes?
- Which methods belong to the inbound proxy processing stages in ZCL_SI_* classes?
- How should I structure validation, logging, and ERP update logic in an MDG inbound proxy?
Possible questions
- How do I implement the main SAP MDG inbound proxy method flow for customer, vendor, STA, CRA, or supplier-change classes?
- What is the runtime sequence in SAP MDG inbound proxy classes?
- Which methods belong to the inbound proxy processing stages in ZCL_SI_* classes?
- How should I structure validation, logging, and ERP update logic in an MDG inbound proxy?
- Can you show an ABAP example for the inbound proxy pattern?