Typical SAP RAR Support Tickets and Their Root Causes

Anyone who supports SAP Revenue Accounting and Reporting (RAR) notices that tickets repeat: contract numbers and symptoms change, but the causes fall into a few patterns. Recognizing those patterns is what turns incident handling into problem management – in ITIL terms, moving from the interruption itself to the cause, or potential cause, of one or more incidents.

1. "The Order Is Not in RAR"

Symptom: A sales document cannot be found in the revenue accounting item monitor, or no new items appear after a change.

Typical root causes:

• The item is not marked as relevant for revenue accounting, or the integration between the sending application and RAR is not active.

• Revenue accounting item classes and their generated interfaces are inconsistent – a known pattern after upgrades, when the interfaces need to be regenerated.

• In classic inbound processing, the logical system is not assigned to the sender component, so the transfer fails in the queue before anything reaches RAR.

• Accounting principles are not configured or not assigned to the company code.

Where to look: configuration of item classes and accounting principles, integration settings, and the transfer queue – not the contract.

2. Items Stuck in Raw or Error Status

The most frequent ticket family overall. Items remain raw when transfer checks fail, for example because an invoice references an order item that is not yet processable, or a profitability segment cannot be derived. Since this topic has its own article, we only note the support angle here: group these items by cause and fix the cause, not each item.

3. Errors After Changes in the Source Document

Symptom: Items that processed fine suddenly fail after a change in the operational system.

Typical root causes: Changes after processing – rejected order lines, new items, price changes – create conditions RAR cannot reconcile with the existing contract. A typical example is an error about more than one main condition type for an item, appearing after sales order lines were rejected following RAI processing.

Where to look: the change history of the source document and the sequence in which items reached RAR. Field corrections in the monitor are possible only for fields defined as modifiable in Customizing, and every change is logged.

4. Missing Standalone Selling Prices

Symptom: Processing fails with a message that SSP information for a performance obligation is missing, for example the SSP currency.

Typical root causes: The SSP rules – usually maintained in BRFplus – do not cover a new product, a new combination of attributes, or a currency. The root cause is often a process gap: a new offering went live without its SSP being defined.

Where to look: SSP rule tables and the process that maintains them. Under ASC 606, SSP is an accounting judgment; support should fix the technical setup and route the pricing question to the accounting owner.

5. Revenue Posting Run Errors

Symptom: The posting run ends with errors, such as a transfer account that cannot be found.

Typical root causes: Gaps in account determination – often for a new company code or an untested combination. These tickets cluster around period end.

Where to look: account determination rules for the affected combination. Fix the rule, rerun, and add the combination to regression tests.

6. The Next Period Cannot Be Opened

Symptom: Opening the next revenue accounting period fails because reconciliation keys for the posting period are not closed.

Typical root causes: Steps of the close were not completed – postings outstanding, transfers not finished, or keys left open after an error. The ticket is a symptom of a close sequence problem.

Where to look: the status of reconciliation keys and the preceding posting steps. The close sequence itself is covered in our checklist article.

7. Consistency Check Findings

Symptom: The consistency monitor flags contracts, for example with an error indicating an incorrect amount after allocation.

Typical root causes: Data inconsistencies created by earlier corrections, program errors, or interrupted processing. Recurring findings point to a process or enhancement issue.

Where to look: the contract's processing history and the relevant SAP Notes for the error category.

8. "Why Is Revenue Different From What We Expected?"

Symptom: No error at all – the business simply does not understand the result. A revenue schedule still shows amounts for a performance obligation whose revenue was reversed and suspended; a cumulative catch-up appears; an allocation looks wrong.

Typical root causes: Usually correct system behavior that nobody explained: review reasons that suspend posting, allocation effects across performance obligations, or contract modification logic. Sometimes a genuine defect.

Where to look: the contract, its review status, and the ASC 606 logic behind it. These tickets need someone who can translate system results into accounting language.

9. Custom Programs Around RAR

Many landscapes run custom upload programs, lifecycle programs, or audit reports around RAR. From our support work, tickets here usually follow changes elsewhere: new contract types, new fields, or upgrades. The root cause is often missing regression testing of the custom layer. Lessor leasing scenarios in RAR deserve particular attention, since modifications and terminations touch both revenue and asset accounting.

Turning Patterns Into Prevention

• Classify every ticket by root cause, not only by symptom.

• Open a problem record when a pattern repeats.

• Feed fixes into regression tests, especially for account determination and SSP rules.

• Use automation carefully: in a human-governed model, AI can classify tickets and draft root-cause analyses, while people approve corrections.

The Bottom Line

Most RAR tickets trace back to a handful of root causes: integration setup, source document changes, SSP rules, account determination, close sequence, and unexplained but correct behavior. Support teams that analyze these patterns – and fix them structurally – spend less time on recurring incidents and more on keeping revenue reliable under ASC 606.

Related terms: Revenue Accounting Item · Standalone Selling Price · BRFplus

Related articles: Revenue Accounting Items: Processing and Error Handling

Seeing the same RAR tickets every month? Talk to our experts.