Ace C_BRU2C_2601 with Free SAP BRIM System Questions 2026

Step-by-Step Execution:

1. Navigate to the File menu, select New, and then choose Consumption Item Mapping.
2. Select the existing Consumption Item Class from SAP Convergent Invoicing that you want to map and click OK.
3. Navigate to the File menu, select Save, and then choose In the Database.
4. Click Yes when the system prompts you to create both the consumption item mapping and the chargeable item mapping.
5. Select the appropriate catalog to store the new objects and click Save.

Example Values:

• Consumption Item Class: HRB4
• Target Catalog: O2C

Expected Result: A new consumption item mapping is created alongside a corresponding chargeable item class, formally defining the structure of the incoming usage data for the rating process.

Quick Mistakes:

• Attempting to manually add new custom fields directly to the chargeable item class in SAP Convergent Charging instead of adding them first to the consumption item class in SAP Convergent Invoicing.
• Trying to delete a property from the chargeable item class after it has been saved to the database (only adding new properties is permitted during an update).

Exam Insight: Validates knowledge of the BRIM integration landscape, emphasizing that SAP Convergent Invoicing is the leading system for defining the structure of usage data records, and Convergent Charging merely mirrors that structure via mappings.

Step-by-Step Execution:

1. Open the ABAP Editor and run the program RFKKBIXBITSAMPLE.
2. Execute the program with the specified variant to generate test data.
3. Enter your contract account group number and ensure the billable item class is set appropriately.
4. Choose the menu option to execute with the variant and check the generation log.
5. Navigate to the SAP Fiori launchpad and open the Display Billable Items app.
6. Enter your contract account number and execute to monitor the generated billable items.

Example Values:

• Program: RFKKBIXBITSAMPLE
• Billable Item Class: PBLW
• Subprocess: BSDA
• Amount: EUR 30

Expected Result: Three billable items are successfully generated and visible on your contract account, preparing it for the downstream billing process execution.

Quick Mistakes:

• Running the report for a billable item class with a final status of productive, as test data generation is restricted only to non-productive or locally productive classes.
• Forgetting to review the generation log file to confirm the actual number of generated items.

Exam Insight:

• Testing billing configurations heavily relies on standard reports like RFKKBIXBITSAMPLE to quickly simulate source events.
• Understanding how to bypass external charging system integration for manual test data generation is a crucial skill for SAP CI process validation.

Step-by-Step Execution:

1. Start the SAP Fiori Cash Journal app (transaction FPCJ) for your assigned cash desk and branch.
2. Post an initial deposit to the cash desk by entering the Company Code, Currency, Amount, and Cash Payment account.
3. Record an incoming cash payment by selecting the Business Partner and entering the payment amount to clear open receivables.
4. Choose Cash Desk Closing to initiate the day-end reconciliation process.
5. Enter the actual cash amounts using the Currency Unit Sheet for bank notes so that the calculated difference is zero.
6. Close the cash desk to confirm the day-end closing and prevent further postings for the day.

Example Values:

• Deposit Amount: 1000 EUR
• Clearing Account: 10010000 Cash Payment
• Cash Payment Amount: 1000 EUR

Expected Result: The cash payments are posted successfully, open items are cleared, and the cash desk status changes to "Closed with No Difference."

Quick Mistakes:

• Forgetting to close the cash desk at the end of the day, leaving the balance open and preventing proper financial reconciliation.
• Failing to allocate the exact physical currency units in the Currency Unit Sheet, causing a discrepancy between target and actual balances.

Exam Insight:

• Tests the knowledge of cash journal operations, including cash desk structures, deposits, and the mandatory day-end closing procedures.
• Highlights that the cash journal offers a role-based authorization concept and enables evaluations based on payment type, currency, and cash desk.

Step-by-Step Execution:

1. Open the Maintain Contract Account app and create a new master contract account for the headquarters.
2. Set the Contract Account Category to indicate it is a collective bill contract account.
3. Open the existing subsidiary contract account and enter the newly created headquarters contract account into the Collective Bill Account field.
4. Execute a standard billing and invoicing process for the subsidiary contract account to generate an invoicing order for the collective bill.
5. Open the Execute Invoicing - Business Partner app and select the dedicated collective invoicing process.
6. Enter the headquarters' master contract account number and execute the run to generate the collective invoice.

Example Values:

• Headquarters Cont. Acc. Cat: YC (FI-CA Collective Bill Contract Account)
• Subsidiary Coll. Bill. Acc.: CA##M (Headquarters Account)
• Subsidiary Invoicing Process: Z3
• Collective Invoicing Process: Z2

Expected Result: The individual invoices of the subsidiaries are successfully consolidated into a single collective invoicing document assigned to the headquarters' master contract account, lifting the clearing restrictions on the subsidiary items.

Quick Mistakes:

• Forgetting to process the standard invoicing run for the subsidiary first, which is required to generate the COLBI source documents for the collective run.
• Attempting to bundle source documents that have different due dates into a single collective invoicing unit without adjusting grouping rules.

Exam Insight:

• Tests the understanding of the master data hierarchy required for collective billing.
• Validates knowledge of the two-step execution process (individual invoicing creating COLBI source documents, followed by the execution of the collective invoicing function INV_COLLBILL).

Step-by-Step Execution:

1. Navigate to the File menu, select New, and choose Pricing Macro.
2. Define the rating context properties for the macro's input and define the generated properties for its output.
3. Configure the macro's internal tree logic by adding a Mapping Table Introducer component.
4. Assign the resulting value to your generated output property using the Out Property Update component.
5. Save the Pricing Macro to the database.
6. Open your charge's price plan, right-click where the logic is needed, and add a Macro Operator component.
7. Select your newly created Pricing Macro in the Macro Operator definition tab and map the required input and output properties.

Example Values:

• Output Property Name: Computed Amount
• Input Property: Service Level Agreement

Expected Result: A reusable pricing macro is saved to the database and successfully linked to a charge's price plan, allowing the charge to execute the macro's logic and retrieve the calculated price.

Quick Mistakes:

• Attempting to change the signature (input or output properties) of a pricing macro after it has already been saved to the database.
• Forgetting to explicitly update the output properties using the Out Property Update component inside the macro.
• Forgetting to assign a function (such as the Free function) to complete the macro from a syntax perspective when it is used merely as an operator.

Exam Insight:

• Evaluates the ability to build modular, reusable price plan logic using macros.
• Tests the critical understanding that macro signatures become immutable after saving, requiring you to copy and replace the macro if input/output changes are needed.