At a glance
Number of RMA (Return Material Authorisation) Sales Orders created in the period. The volume side; pair with Credit Memo Value for $.
| What it counts | COUNT(SO WHERE order_type = RMA) in window. |
| Currency | n/a. |
| Time window | 30D vsP |
| Alert trigger | up >20% vsP |
| Sentiment key | returns_trend |
| Roles | owner, operations |
Calculation
Calculated automatically from your Oracle ERP Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US Fortune 500 retailer on Oracle ERP Cloud. 30D window.| This period | Prior | |
|---|---|---|
| RMA SO count | 384 | 348 |
| Return rate vs orders shipped | 8.0% | 7.6% |
- 10% increase vsP, just below 20% alert. Watching.
- Pair with reason codes to see if quality / sizing / shipping issues spiking.
- Per-SKU drill identifies problem products.
- Per-channel distinguishes commerce returns from B2B.
- Cross-reference Credit Memo Value for $ impact.
Sibling cards merchants should reference together
| Card | Why pair |
|---|---|
| Credit Memo Value | Dollar side. |
| Margin Erosion Alerts | High-return SKUs erode margin. |
Reconciling against the vendor’s own dashboard
Where to look in Oracle ERP Cloud:Order Management → Manage Orders filter type RMA OTBI → Order Management Real TimeWhy our number may legitimately differ:
| Reason | Direction | Why |
|---|---|---|
| RMA vs cancelled | Either | Card excludes cancelled. |
| Card | Notes |
|---|---|
| Commerce return cards | Numerator on commerce side. |