Advanced · the code behind the config
Where standard config stops, code begins.
Most of an SAP build is configuration. The gaps that config can’t reach become RICEFW objects — and this is what they actually look like. Three real objects from the cards above: an ABAP pricing routine, the OBYC account-determination table, and a CO-PA derivation rule. Switch objects, click a highlighted line to read what it does, or run an execution trace.
FRM_KONDI_WERT_601 ABAP · VOFM routine
1* FRM_KONDI_WERT_601 — VOFM pricing value routine2* Condition ZTIR · attached in V/08 · tiered volume, sibling-aware3 4FORM frm_kondi_wert_601.5 6 DATA: lv_qty TYPE komp-mgame, " rolled-up sibling qty7 lv_tier TYPE konp-kbetr. " resolved unit rate8 9* 1 · Standard conditions price one sold-to at a time —10* roll quantity up across the customer's siblings first.11 PERFORM read_sibling_qty USING komk-kunnr12 CHANGING lv_qty.13 14* 2 · Resolve which price tier that combined volume earns.15 SELECT SINGLE kbetr INTO lv_tier16 FROM ztir_scale17 WHERE vkorg = komk-vkorg18 AND qty_from <= lv_qty19 AND qty_to >= lv_qty.20 21* 3 · Return the value; SAP posts XKWERT as the condition.22 xkwert = komp-mgame * lv_tier.23 24ENDFORM.
Click a highlighted line to read what it does — and why it’s built that way.
Watch the config post.
Procure-to-Pay · MM → FI
The OBYC table above isn’t abstract — it decides the GL accounts every movement hits. Step through a purchase and watch the automatic double entry land in the ledger. GR/IR and the vendor should each clear to zero when the flow completes.
MIGO · 101Goods Receipt
→
MIROInvoice Receipt
→
F-53Outgoing Payment
Inventory / Stock
BSX 130000
3 postings · net vendor liability ฿10,700 incl. 7% input VAT