C_BRSOM_2020 · Question #15
Which BRIM data objects can be created or updated using Revenue Accounting Contract in SAP S/4HANA RAR? Note: There are 2 correct answers to this question.
The correct answer is B. Provider Contract C. Billable Item. In SAP S/4HANA RAR, the Revenue Accounting Contract (RAC) serves as the central revenue recognition object and integrates with BRIM by directly creating or updating Provider Contracts (B) and Billable Items (C). Provider Contracts are the governing BRIM agreements that RAR can…
Question
Which BRIM data objects can be created or updated using Revenue Accounting Contract in SAP S/4HANA RAR? Note: There are 2 correct answers to this question.
Options
- ASubscription order
- BProvider Contract
- CBillable Item
- DService Order
How the community answered
(19 responses)- A5% (1)
- B79% (15)
- D16% (3)
Explanation
In SAP S/4HANA RAR, the Revenue Accounting Contract (RAC) serves as the central revenue recognition object and integrates with BRIM by directly creating or updating Provider Contracts (B) and Billable Items (C). Provider Contracts are the governing BRIM agreements that RAR can establish or modify to reflect the contractual obligations driving revenue recognition, while Billable Items are the individual charge records that RAR can generate or update when billing-relevant revenue events occur under IFRS 15/ASC 606 rules.
Subscription Order (A) is incorrect because it is an input source to the BRIM/RAR process - created upstream in Order Management - not an object that RAR itself creates or updates. Service Order (D) is also incorrect because it originates from the Service Management module (CS/SM) and is not a BRIM data object that RAR controls.
Memory tip: Think of the flow direction - RAR receives data from Subscription Orders and Service Orders, but RAR writes to Provider Contracts and Billable Items. The two correct answers (B and C) are the downstream BRIM outputs that RAR governs, while the distractors (A and D) are upstream inputs that feed into RAR.
Topics
Community Discussion
No community discussion yet for this question.