Handles changes to bank details, addresses, terms and blocks on customer and supplier records with evidence, a callback, four-eyes approval and write-back to the ERP and the CRM.
Today a request to change a supplier's bank account arrives by email and is typed into the ERP by the person who has the authorisation that day. The evidence sits in the mailbox, and the CRM record is updated in a separate step.
A buyer or account manager picks the record, chooses the field group and enters the new value beside the current one, with the reason and the evidence. The master data steward verifies the evidence and records a callback to the contact number already on the record; for bank details the supplier or customer also confirms the change on the portal screen with a one-time code. A second person approves: finance for bank details, sales operations or the category lead for terms and blocks. The app then writes the change through the ERP change interface, updates the CRM account within a minute, and keeps the before and after values with the change document number.
| Lane | Does |
|---|---|
| Requester | raises the change with the reason and the evidence |
| Master data steward | verifies the evidence, records the callback, checks the format rules |
| Approver | finance for bank details; sales operations or the category lead for terms and blocks |
| Supplier or customer | confirms a bank or address change on the portal screen with a one-time code |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Change request | record search, field group (bank, address, terms, contact, block), current value beside the new value, reason, evidence upload; submit |
| S02 Verification | evidence viewer, callback record with the number on file and the outcome, format checks (IBAN check digits, postal code), sanctions re-screen for a new bank country; verified or returned with a note |
| S03 Approval | change summary, risk flags: new bank country, first change in 3 years, open invoice value, open orders; approve or reject with a note |
| S04 Partner confirmation | portal screen: the requested change shown, confirm with the one-time code sent to the contact on file |
| S05 Write-back result | values written, change document number from the ERP, CRM sync status; before and after |
| S06 Log | changes by record, field group, requester, approver and date; filters; export for audit |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Supplier master | supplier records: bank details, addresses, payment terms, block status | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Customer master | customer records: addresses, terms, sales organisation data, block status | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Purchasing contract | agreements with the partner affected by a terms change | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Sales order line | open orders with the customer affected by an address or block change | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Object | What changes |
|---|---|
| Supplier master | bank details, address, terms or block changed through the vendor change interface; change document number stored |
| Customer master | address, terms or block changed through the customer change interface; the CRM account updated within a minute |
Start: A requester submits S01 with a new value that differs from the current value.
| Step | Moves when |
|---|---|
| Request submitted | new value differs from the current value; evidence attached for bank and address changes |
| Verified | steward records the callback outcome and the evidence check; format rules pass |
| Partner confirmed | portal confirmation with the one-time code for bank and address changes |
| Approved | a second person, apart from the requester, approves: finance for bank details |
| Written back | values changed in the ERP and the CRM; change document stored; requester and partner informed |
| Component | Trigger → action → outcome |
|---|---|
| fld_new_value | on change → compare with the current value and the format rules → show the risk flags, require evidence for bank details |
| btn_verify | on click → record the callback to the number on file and the evidence check → open S03 for the approver, start the 1-day clock |
| btn_confirm_code | on submit → check the one-time code sent to the contact on file → mark the change partner-confirmed, enable the write-back |
| btn_write | on click → call the vendor or customer change interface → store the change document number, update the CRM account, close the request |
| Step | Time limit and escalation |
|---|---|
| Verification | 1 working day, then the master data lead is reminded |
| Approval | 1 working day, then the approver's lead is copied |
| Partner confirmation | 3 working days, then the request returns to the requester |
Names, places and figures are illustrative; the pattern is the catalogue's.
At 11:20 a buyer in Singapore received an email asking to move a supplier's payments to a new bank account and raised the request with the letter attached. Wei, the master data steward, called the supplier's finance contact on the number on file at 14:00; the contact knew of a change, to a different bank than the letter named. Wei returned the request, the supplier confirmed the correct account on the portal screen the next morning with the one-time code, finance approved at 10:30, and the vendor record changed in SAP and the CRM within a minute. The log showed the attempted change, the callback and every step taken.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Supplier master read from LFA1 · LFB1 · LFM1 (business partner in S/4); also on SAP ECC.
Open the S/4HANA page →Supplier master read from Procurement REST: suppliers · supplierSites; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Supplier master read from Account (RecordType = Supplier); CRM.
Open the Salesforce page →Supplier master read from CONFORMED.VENDOR; lakehouse.
Open the Snowflake page →Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 4 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of SAP S/4HANA, Oracle Fusion Cloud, Salesforce, Snowflake, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.