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.
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.
| Lane | Does |
|---|---|
| Proposer | pricing analyst or sales representative: proposes lines with amount, validity and reason |
| Pricing manager | reviews the impact and approves changes within the band |
| Sales director | approves changes above the band |
| Controller | approves lines below the margin floor |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Proposal | grid of lines: material, customer or price list, current amount, new amount or percent, valid from and to, reason; upload for bulk; submit |
| S02 Impact | per 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 Approval | lines grouped by band with the impact; approve, return or change the validity; note; approvals recorded per band |
| S04 Write-back | condition records created per line with validity, previous record ended; ERP result per line; CRM price book status |
| S05 Board | changes by band and status, margin change per month, time to approve, lines returned, open quotes at old prices |
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 |
|---|---|---|
| Price condition | price conditions and the cost condition by material, customer and validity | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Customer master | the account or customer group the price applies to, with its sales organisation | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Sales order line | order lines of the last 12 months for the volume, and open lines at the old price | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Quotation | open quotations at the old price | S/4HANA · Oracle Fusion · Salesforce · Snowflake |
| Object | What changes |
|---|---|
| Price condition | condition records created per material and customer with the new amount and validity; the previous record ended the day before |
| Quotation | open quotations flagged with the new price for the owner to confirm or re-issue |
Start: A proposer submits S01 with at least 1 line whose new amount differs from the current condition.
| Step | Moves when |
|---|---|
| Proposal submitted | every line has a current price, a new amount, a valid-from date on or after tomorrow and a reason |
| Impact computed | margin and 12-month volume read within seconds; band assigned per line |
| Approved by band | within 3 percent and above the margin floor: pricing manager; up to 10 percent: sales director; below the margin floor: controller |
| Written back | condition records created with the validity; the old record ended the day before; result stored per line |
| Confirmed | records read back from the ERP; CRM price book updated; proposer informed; open quotes flagged to their owners |
| Component | Trigger → action → outcome |
|---|---|
| grd_lines | on edit → read the cost condition and the last 12 months of order quantity → show margin before and after and assign the band |
| btn_submit | on 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_approve | on click → record the approval for the band → move to the next band or to the write-back step |
| btn_write | on 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 |
| Step | Time limit and escalation |
|---|---|
| Each approval band | 2 working days, then the approver's lead is reminded |
| Write-back | due 1 working day before the earliest valid-from date; a line past it is flagged on the board |
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.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Price condition read from A004 · A005 · KONP (condition records) · PRCD_ELEMENTS; also on SAP ECC.
Open the S/4HANA page →Price condition read from Pricing REST: priceLists · priceListItems; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Price condition read from PricebookEntry · Product2; CRM.
Open the Salesforce page →Price condition read from CONFORMED.PRICE_CONDITION; 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 5 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.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
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.