C_BRU2C_2020 · Question #65
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 A. Provider contract D. Billable item. In SAP BRIM/RAR integration, the Revenue Accounting Contract (RAC) acts as a downstream orchestrator that can create or update Provider Contracts (A) - which represent the formal contractual relationship in Subscription Order Management - and Billable Items (D) - which are the…
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
- AProvider contract
- BSubscription order
- CService order
- DBillable item
How the community answered
(54 responses)- A72% (39)
- B19% (10)
- C9% (5)
Explanation
In SAP BRIM/RAR integration, the Revenue Accounting Contract (RAC) acts as a downstream orchestrator that can create or update Provider Contracts (A) - which represent the formal contractual relationship in Subscription Order Management - and Billable Items (D) - which are the transactional charge objects in Convergent Invoicing that trigger billing events based on recognized revenue or contract modifications.
Why B and C are wrong: Subscription Orders (B) and Service Orders (C) are upstream source documents - they feed data into the RAR process, triggering creation of the Revenue Accounting Contract. RAR does not write back to create or modify them; the flow is one-directional from those objects into RAR.
Memory tip: Think of it as "RAR talks back to BRIM in two ways - the contract (Provider Contract) and the charge (Billable Item)." Everything else (Subscription Order, Service Order) flows into RAR, not out of it. If it sounds like an input to a sales or field-service process, RAR doesn't create it.
Topics
Community Discussion
No community discussion yet for this question.