Contract Sap Rar Jobs in Chicago, IL (NOW HIRING)

SAP RAR - SD Integration Consultant 

Onsite (expense paid)

12+ Months

RAR info: SAP RAR-SD integration refers to the technical and functional linkage between SAP''s Revenue Accounting and Reporting (RAR) module and SAP Sales and Distribution (SD), and it''s exactly what''s underpinning the marketing-program revenue process Prakash described in that meeting.

Why the integration exists

RAR was built to implement IFRS 15 / ASC 606 revenue recognition rules, which require that revenue be recognized based on the transfer of control of goods or services, not simply on invoicing. Many transactions can be recognized immediately in the period they''re billed, but others need to be spread over time or reallocated across bundled elements. That''s precisely the distinction Prakash drew: direct customer sales are recognized as billed and never touch RAR, while marketing-program revenue must be deferred and recognized systematically over a defined period, so it flows through RAR.

How the data moves from SD into RAR

The integration works by treating standard SD documents (sales orders, contracts, deliveries, and billing documents) as sources of Revenue Accounting Items, commonly called RAI. When a relevant SD transaction occurs, either at order creation, goods issue, or billing, SAP generates an inbound processing (BRFplus-driven) message that RAR consumes. Each RAI is classified by a source type (order-based or invoice-based) and mapped into RAR''s own objects: performance obligations, fulfillment items, and the overall revenue accounting contract.

For example, when a marketing-program sales order is created in SD, SD passes contract-level data such as pricing conditions, quantities, and delivery terms to RAR. RAR then determines the performance obligations embedded in that contract, for instance the underlying product, a bundled marketing credit, or a service commitment, and calculates the standalone selling price (SSP) for each. If the contract includes multiple elements sold together at a combined price, RAR performs price allocation, splitting the total transaction price across performance obligations based on relative SSP, which is where RAR earns its value over plain SD pricing.

As fulfillment events occur, a goods issue, a partial delivery, or a periodic service rendering, SD sends fulfillment RAIs to RAR. RAR matches these against the performance obligations and recognizes revenue according to the applicable pattern, either point-in-time recognition tied to a specific fulfillment event, or time-based recognition spread ratably across a service period. This is almost certainly the mechanism used for the marketing programs Prakash mentioned, since marketing incentives, rebates, or bundled promotional elements are common cases requiring revenue deferral and ratable recognition rather than immediate booking.

Billing documents from SD generate a separate class of RAI as well, since invoicing establishes the contractual price and triggers reclassification between contract asset and contract liability in RAR. RAR then posts the recognized revenue, deferred revenue, and any contract asset/liability entries to FI, keeping the SD-driven operational transaction and the accounting-compliant revenue recognition cleanly separated but reconciled.

Configuration components involved

On the SD side, this relies on condition-based or item-category-based rules that flag which sales document types and item categories are RAR-relevant, so the system knows which transactions to route as RAIs versus which stay purely in SD/FI without deferral. On the RAR side, configuration includes RAI processing classes, contract combination rules for how multiple SD documents group into a single revenue accounting contract, performance obligation type determination, and the SSP determination method, whether it''s list price, cost-plus-margin, or an override procedure.