SAP MDG · UTILITIES
How does SAP MDG process a supplier EFT update submitted from an external supplier portal, including staging-table processing, duplicate entries, and approval in My Change Requests
Supplier EFT updates from an external portal are staged first, then picked up by a background job, converted into a Change Request, and finally approved in My Change Requests - Monitoring before the BP bank data is updated.
Supplier EFT updates from an external portal are staged first, then picked up by a background job, converted into a Change Request, and finally approved in My Change Requests - Monitoring before the BP bank data is updated.
The documented MDG flow for a supplier EFT update from an external supplier portal is: submit the request, verify the staging-table record in SE16N, let the background job in SM37 process it, then approve the Change Request in My Change Requests - Monitoring.
Process flow
- Log in to the External Supplier Portal and submit a bank update request for an existing supplier Business Partner.
- Verify the integration creates a new record in the configured bank-update integration staging table using SE16N.
- Submit another request for the same Business Partner before the first record is processed and confirm another staging entry is created.
- Execute or wait for the scheduled background job that picks up the staging-table entry.
- Verify the staging entry is processed successfully, the CR number is written back, and an email notification is sent to the approver.
- Log in to Fiori launchpad with the BP approver user ID and password.
- Open My Change Requests - Monitoring.
- Filter to To be processed by me and open the Change Request list item.","Use Check to validate the data, then approve the Change Request.","Navigate to the Business Partner search page and confirm the bank data is updated as expected."],
SE16NMaintain Business Partner/BP tcode fiori tile
Verify the integration staging table entry created by the portal submission.
SM37Scheduled background job processing the integration staging-table entry
Monitor the job that picks up and processes the staging record.
Fiori app
Review and process the Change Request created from the portal submission.
Fiori app
Open the request details before approval.
Referenced tables
| Object | Purpose |
|---|---|
Configured bank-update integration staging table | Holds incoming supplier EFT/bank update requests before background processing. |
USMD1210 | Stores Change Request notes; used in the related ABAP utility example. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- How to test supplier bank/EFT updates from an external supplier portal in SAP MDG?
- What is the end-to-end flow for external supplier portal bank update requests in MDG?
- How do I verify duplicate EFT update entries and CR approval in MDG?
Possible questions
- Which transaction code or app is used to verify the staging table?
- What background job processes the EFT update request?
- How do I check the change request in My Change Requests - Monitoring?
- How do I validate that the BP bank data was updated after approval?
- keywords":["SAP MDG","Business Partner","Supplier EFT","External Supplier Portal","staging table","SE16N","SM37","My Change Requests - Monitoring","Display Change Requests","Change
- solution_summary":"Supplier EFT updates from an external portal are staged first, then picked up by a background job, converted into a Change Request, and finally approved in My
- short_answer":"The flow is: portal submission → staging table entry in SE16N → background job in SM37 processes the record → Change Request appears in My Change Requests -" ,
- preview_answer":"The documented MDG flow for a supplier EFT update from an external supplier portal is: submit the request, verify the staging-table record in SE16N, let the
- detailed_answer":"TC43 documents an end-to-end supplier EFT update scenario in SAP MDG. The request is first submitted from the External Supplier Portal, stored in the configured
- process_steps":["Log in to the External Supplier Portal and submit a bank update request for an existing supplier Business Partner.","Verify the integration creates a new record in
- configurations":[{"tcode":"SE16N","path":"Maintain Business Partner/BP tcode fiori tile","purpose":"Verify the integration staging table entry created by the portal submission."},{
- tables":[{"name":"Configured bank-update integration staging table","purpose":"Holds incoming supplier EFT/bank update requests before background processing."},{"name":"USMD1210","
- code_sample":{"title":"Example ABAP pattern to add a Change Request note and trigger downstream processing logic","note":"General guidance — verify in your SAP release and
- code":"METHOD add_crequest_note.\n\n DATA:\n lv_ts TYPE timestamp,\n ls_creq_note TYPE usmd1210,\n ls_crequest TYPE usmd_s_crequest.\n\n TRY.\n CALL METHOD
- type":"object"}]}