App catalogue Master data and governance

Price and condition change approval

Takes proposed price changes with their margin and volume impact through approval bands and writes the condition records to the ERP and the CRM price book with the right validity.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 ProposalscreenS02 ImpactscreenS03 ApprovalscreenS04 Write-backscreenS05 Boardscreendh_pricePrice conditiondh_customerCustomer masterdh_soSales order linedh_quoteQuotationS/4HANAA004 · A005 · KONPS/4HANAKNA1 · KNB1 · KNVVS/4HANAVBAK · VBAP · VBEPS/4HANAVBAK · VBAProws 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.
5 days
of configuration to a production-grade version
estimate
5
screens, desktop and mobile
catalogue
4
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
2
clocks with escalation
catalogue
What it does

Today, and with the app

Today a price change is a spreadsheet emailed to the pricing manager, approved in a reply, and keyed into condition records line by line at the end of the month. The CRM price book follows a week later, and open quotes carry the old price.

A pricing analyst or a sales representative proposes changes for materials and customers, price lists or customer groups, with the new amount and the valid-from date, one line at a time or by upload. Within seconds the app reads the cost condition and the last 12 months of order quantities, shows the margin before and after, the annual revenue effect and the open orders and quotes at the old price, and assigns each line an approval band. The pricing manager, the sales director and the controller approve their bands on one screen. On approval the app creates the condition records through the released interface, ends the previous record the day before, updates the CRM price book and flags the open quotes to their owners.

Who takes part

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

LaneDoes
Proposerpricing analyst or sales representative: proposes lines with amount, validity and reason
Pricing managerreviews the impact and approves changes within the band
Sales directorapproves changes above the band
Controllerapproves lines below the margin floor
Screens

5 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 Proposalgrid of lines: material, customer or price list, current amount, new amount or percent, valid from and to, reason; upload for bulk; submit
S02 Impactper line: cost, margin before and after, 12-month volume, revenue and margin change; open orders and quotes at the old price; band per line and for the proposal
S03 Approvallines grouped by band with the impact; approve, return or change the validity; note; approvals recorded per band
S04 Write-backcondition records created per line with validity, previous record ended; ERP result per line; CRM price book status
S05 Boardchanges by band and status, margin change per month, time to approve, lines returned, open quotes at old prices
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
Price conditionprice conditions and the cost condition by material, customer and validityS/4HANA · Oracle Fusion · Salesforce · Snowflake
Customer masterthe account or customer group the price applies to, with its sales organisationS/4HANA · Oracle Fusion · Salesforce · Snowflake
Sales order lineorder lines of the last 12 months for the volume, and open lines at the old priceS/4HANA · Oracle Fusion · Salesforce · Snowflake
Quotationopen quotations at the old priceS/4HANA · Oracle Fusion · Salesforce · Snowflake

Written back

ObjectWhat changes
Price conditioncondition records created per material and customer with the new amount and validity; the previous record ended the day before
Quotationopen quotations flagged with the new price for the owner to confirm or re-issue
The flow

From the trigger to the last write

THE FLOW · PRICE AND CONDITION CHANGE APPROVAL1Proposal submittedevery line has a currentprice, a new amount, avalid-from date on or aftertomorrow and a reason2Impact computedmargin and 12-month volumeread within seconds; bandassigned per line3Approved by bandwithin 3 percent and abovethe margin floor: pricingmanager; up to 10 percent:sales director; below themargin floor: controller4Written backcondition records createdwith the validity; the oldrecord ended the daybefore; result stored perline5Confirmedrecords read back from theERP; CRM price bookupdated; proposer informed;open quotes flagged totheir owners
Each step and the criterion that moves it.

Start: A proposer submits S01 with at least 1 line whose new amount differs from the current condition.

StepMoves when
Proposal submittedevery line has a current price, a new amount, a valid-from date on or after tomorrow and a reason
Impact computedmargin and 12-month volume read within seconds; band assigned per line
Approved by bandwithin 3 percent and above the margin floor: pricing manager; up to 10 percent: sales director; below the margin floor: controller
Written backcondition records created with the validity; the old record ended the day before; result stored per line
Confirmedrecords read back from the ERP; CRM price book updated; proposer informed; open quotes flagged to their owners
Actions, clocks and measures

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

ComponentTrigger → action → outcome
grd_lineson edit → read the cost condition and the last 12 months of order quantity → show margin before and after and assign the band
btn_submiton click → check every line for a valid-from date on or after tomorrow and a reason → route the proposal to the first approver of its highest band
btn_approveon click → record the approval for the band → move to the next band or to the write-back step
btn_writeon click → call the condition record interface per line → end the old record, store the new record's key, update the CRM price book, notify the proposer

Clocks

StepTime limit and escalation
Each approval band2 working days, then the approver's lead is reminded
Write-backdue 1 working day before the earliest valid-from date; a line past it is flagged on the board

Measures

changes approved within 2 daysmargin change per monthlines returned for correctionconditions written before the valid-from dateopen quotes at the old price
A day with the app

Illustrative

Names, places and figures are illustrative; the pattern is the catalogue's.

On Tuesday at 10:00 Kenji, a pricing analyst in Osaka, uploaded 140 lines for the April list price change, an average rise of 4 percent. The impact screen showed 12 lines below the margin floor and 3 customers with open quotes at the old price, so he adjusted 4 lines before submitting at 10:40. The pricing manager approved 128 lines that afternoon, the controller approved the rest on Wednesday, and the condition records reached SAP on Thursday evening with a valid-from date of 1 April. The CRM price book carried the same amounts on Friday morning, and the board showed 2 days from proposal to approval.

illustrative scenario · Price and condition change approval
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

Condition recordA dated price entry in the ERP for a material and a customer, customer group or price list.
Margin floorThe lowest margin percentage a price may carry before the controller has to approve it.
Approval bandThe size of a change, in percent and against the margin floor, that decides who approves it.
Questions

How long does it take to have this running?

About 30 minutes to a first running screen on your live rows, and 5 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?

Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.

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.