App catalogue Master data and governance

Customer and supplier master change

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.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 Change requestscreenS02 VerificationscreenS03 ApprovalscreenS04 Partner confirmationscreenS05 Write-back resultscreendh_vendorSupplier masterdh_customerCustomer masterdh_contractPurchasing contractdh_soSales order lineS/4HANALFA1 · LFB1 · LFM1S/4HANAKNA1 · KNB1 · KNVVS/4HANAEKKO · EKPOS/4HANAVBAK · VBAP · VBEProws stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on S/4HANA. Other systems have their own page.
4 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
4
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

Process app: lanes and boxes first, then screens per box, then roles, then the criteria on each arrow

LaneDoes
Requesterraises the change with the reason and the evidence
Master data stewardverifies the evidence, records the callback, checks the format rules
Approverfinance for bank details; sales operations or the category lead for terms and blocks
Supplier or customerconfirms a bank or address change on the portal screen with a one-time code
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Change requestrecord search, field group (bank, address, terms, contact, block), current value beside the new value, reason, evidence upload; submit
S02 Verificationevidence 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 Approvalchange summary, risk flags: new bank country, first change in 3 years, open invoice value, open orders; approve or reject with a note
S04 Partner confirmationportal screen: the requested change shown, confirm with the one-time code sent to the contact on file
S05 Write-back resultvalues written, change document number from the ERP, CRM sync status; before and after
S06 Logchanges by record, field group, requester, approver and date; filters; export for audit
Data handlers

4 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Supplier mastersupplier records: bank details, addresses, payment terms, block statusS/4HANA · Oracle Fusion · Salesforce · Snowflake
Customer mastercustomer records: addresses, terms, sales organisation data, block statusS/4HANA · Oracle Fusion · Salesforce · Snowflake
Purchasing contractagreements with the partner affected by a terms changeS/4HANA · Oracle Fusion · Salesforce · Snowflake
Sales order lineopen orders with the customer affected by an address or block changeS/4HANA · Oracle Fusion · Salesforce · Snowflake

Written back

ObjectWhat changes
Supplier masterbank details, address, terms or block changed through the vendor change interface; change document number stored
Customer masteraddress, terms or block changed through the customer change interface; the CRM account updated within a minute
The flow

From the trigger to the last write

THE FLOW · CUSTOMER AND SUPPLIER MASTER CHANGE1Request submittednew value differs from thecurrent value; evidenceattached for bank andaddress changes2Verifiedsteward records thecallback outcome and theevidence check; formatrules pass3Partner confirmedportal confirmation withthe one-time code for bankand address changes4Approveda second person, apart fromthe requester, approves:finance for bank details5Written backvalues changed in the ERPand the CRM; changedocument stored; requesterand partner informed
Each step and the criterion that moves it.

Start: A requester submits S01 with a new value that differs from the current value.

StepMoves when
Request submittednew value differs from the current value; evidence attached for bank and address changes
Verifiedsteward records the callback outcome and the evidence check; format rules pass
Partner confirmedportal confirmation with the one-time code for bank and address changes
Approveda second person, apart from the requester, approves: finance for bank details
Written backvalues changed in the ERP and the CRM; change document stored; requester and partner informed
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
fld_new_valueon change → compare with the current value and the format rules → show the risk flags, require evidence for bank details
btn_verifyon 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_codeon submit → check the one-time code sent to the contact on file → mark the change partner-confirmed, enable the write-back
btn_writeon click → call the vendor or customer change interface → store the change document number, update the CRM account, close the request

Clocks

StepTime limit and escalation
Verification1 working day, then the master data lead is reminded
Approval1 working day, then the approver's lead is copied
Partner confirmation3 working days, then the request returns to the requester

Measures

changes completed within 2 daysbank changes with a recorded callbackrequests returned for evidencechanges by field group per monthopen requests by stage
A day with the app

Illustrative

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.

illustrative scenario · Customer and supplier master change
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

Four-eyes approvalA change takes effect only when a second person, apart from the requester, approves it.
CallbackA phone call to a contact number already on the record, made before a bank change is accepted.
Change documentThe ERP record of who changed which field, from which value to which, and when.
Questions

How long does it take to have this running?

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.

Which system does it run on?

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.

Who takes part from outside the company?

Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

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.