Learn, Practice, and Improve with SAP C_BRU2C_2020 Practice Test Questions

Explanation:

The Subscription Order Management (SOM) component in SAP S/4HANA Service handles the entire lifecycle of subscription orders, from initial customer interaction through fulfillment. The order capturing process specifically refers to the front-end sales consultation phase where a customer service representative or sales agent interacts directly with the customer. During this phase, the primary activity is to understand customer requirements and provide guidance on available service offerings, rate plans, and subscription options. This advisory role helps customers select the most appropriate products that match their needs before any technical configuration or order submission occurs. The process focuses on customer interaction and decision support rather than technical system configuration.

❌ Why Other Options Are Incorrect

A. Configure rate plan and its services
– This is incorrect because rate plan configuration is a backend product management activity performed in SAP Convergent Charging and the product master by specialized product managers or configurators. Sales agents do not have access or authorization to modify technical rate structures during customer interactions.

B. Monitor order status
– This is incorrect as order monitoring occurs after order submission, not during the capture phase. Once the order is released to fulfillment, the Order Distribution Infrastructure (ODI) handles status updates, and agents can track progress through subsequent monitoring tools.

D. Update order and contract status
– This is incorrect because status updates are automatically triggered by system events during order fulfillment and contract activation. Manual status updates by agents during the capture phase are neither required nor standard practice.

Reference
According to SAP BRIM documentation and training materials (BR230 - Overview of SAP Billing and Revenue Innovation Management), the subscription order management process follows a clear sequence: Sales Consultation (advising customers on offerings) → Order Capturing (entering selected products) → Order Submission (releasing for fulfillment). The advisory role during order capture is explicitly documented as the initial step where customer needs are assessed against available service catalogs before any technical processing begins.

Explanation:

The money is initiated by the customer and only enters the SAP system after the funds have been successfully received in the company's bank account. Because the cash is already "in hand" before the payment is posted in FI-CA, there is no risk of the bank "returning" the transaction due to insufficient funds or invalid account details. Any errors (like an incorrect reference number) are handled via the Payment Lot or Clarification List, not the Returns Lot.

Why the Other Options are Incorrect

A. Checks:
These are high-risk "Paper" payments. A check can be posted in SAP upon receipt, but the bank may later reject it (e.g., "Non-Sufficient Funds"). This requires a Returns Lot to reverse the clearing and reopen the receivable.

B. Credit Card Collections:
These are "Pull" payments involving an external clearinghouse. If a transaction is authorized but later declined or disputed (chargeback) during the settlement phase, it must be processed as a return to reflect the loss of funds.

D. Debit Memos (Direct Debit):
Like checks, these are "Pull" transactions. The company instructs the bank to collect funds. If the customer’s bank rejects the request (e.g., account closed), the system must use a Returns Lot to undo the payment and potentially trigger a dunning block.

References
SAP Learning Hub - AC240 (Contract Accounts Receivable and Payable): Section on "Returns Processing."
SAP Help Portal: FI-CA -> Transactions -> Returns.

Explanation:

In SAP Convergent Invoicing (CI), Discount Base Items (DBIs) are generated during the Billing process, not during the rating or invoicing stages.

The billing engine evaluates the Billable Items (BITs) stored in the system. If a billing rule or a discount configuration (such as a volume-based discount or a cross-item rebate) is active, the system calculates the relevant amount and generates a Discount Base Item. This item serves as the foundation for calculating the final discount amount that will eventually appear on the invoice.

Why the Other Options are Incorrect

A. Creation of a charged item:
This occurs in SAP Convergent Charging (CC). While CC can apply "Charging-level" discounts, "Discount Base Items" are a specific technical construct of SAP Convergent Invoicing used for post-rating discounts (e.g., multi-service bundles).

B. Rating of a consumption item:
Rating simply converts consumption data into a price (a Billable Item). Discounts triggered at this stage are usually embedded directly into the BIT price rather than creating separate DBI records for later calculation.

D. Creation of an invoicing document:
Invoicing is the final step that takes already calculated billing units and groups them into a legal document. By the time you reach Invoicing, all discounts (DBIs) must have already been processed and converted into final Billable Items to be included in the total.

References
SAP Learning Hub - AC235 (SAP Convergent Invoicing): Unit regarding "Billing Processes and Discount Structures."

Explanation:

In SAP FI-CA, a manual payment lot is used to group and process incoming payments that aren't received via automated electronic files. The lifecycle of a payment lot follows a strict technical sequence to ensure financial integrity.

A. Enter the items:
This is the initial manual task. You must enter the payment details for each transaction, including the amount, the bank data, and selection criteria (such as a contract account number or document number).

E. Close the lot:
Once all items are entered, the lot must be "Closed." This prevents any further items from being added and changes the status of the lot to indicate it is ready for the final posting run.

C. Post the lot:
This is the final execution step. Posting the lot triggers the actual G/L updates and clears the open items on the customer accounts. Without this step, the money remains in a "suspense" or "pre-posted" state.

Why the Other Options are Incorrect

B. Set the status to "completed":
This is a distractor. "Completed" is a system-generated status achieved after a lot has been fully posted and all items are cleared. You do not manually "set" this status as a task; the system assigns it.

D. Assign the items to open receivables:
While you provide selection criteria during entry, the automatic clearing proposal handles the assignment during the posting run. Manual assignment is only required if an item falls into the "Clarification List" because the system couldn't find a match.

References
SAP Learning Hub - AC240 (Contract Accounts Receivable and Payable): Unit on "Incoming Payments" and "Payment Lots.

Explanation:

To define individual discounts that are calculated during invoice processing in SAP Convergent Invoicing, you must activate the appropriate invoicing function within an invoice process. The specific invoicing function for individual discounts is CHARGE_DISC2 (Individual Charges and Discounts).

❌ Why Other Options Are Incorrect

A. Invoice function
– While technically close, this is incorrect because "invoice function" refers to the specific technical function (like CHARGE_DISC2) itself. However, you must activate this function within an invoice process – the function alone cannot be activated independently.

C. Invoice category
– Invoice categories classify source documents for selection during invoicing but have no role in discount configuration or calculation.

D. Invoice type
– Invoice types determine document classification and numbering but do not control discount calculation logic or activation.

Reference
According to SAP documentation, the configuration path is: Financial Accounting → Contract Accounts Receivable and Payable → Convergent Invoicing → Invoicing → Invoicing Processes → Additional Functions. Here you assign charge/discount keys to the invoicing process to activate discount calculation during invoice processing

Explanation:

In SAP Subscription Order Management (SOM), when you need to modify a specific product characteristic—such as an attribute defined in the SAP Variant Configuration (VC) model—you must use the Configuration Change process. This process allows you to adjust specific parameters (e.g., bandwidth speed, storage capacity, or a service level) that were selected during the initial sale without changing the actual product ID itself.

This process creates a new Contract Item in the background with a new time slice, ensuring that the history of the previous configuration is preserved for accurate billing and reporting.

Why the Other Options are Incorrect

A. Product Change:
This is used when the customer wants to switch to an entirely different Product ID (e.g., upgrading from a "Basic Plan" to a "Premium Plan"). It involves a mapping of the old product to the new one, rather than just adjusting a characteristic of the current one.

B. Change Contract Account Assignment:
This is a header or item-level administrative change used to point the contract to a different FI-CA Contract Account for billing purposes. it does not affect the technical attributes of the service.

C. Change Technical Resources:
This process is specific to technical identifiers, such as changing a MAC address, IP address, or SIM card number. While these are "characteristics" in a broad sense, they are managed via the Technical Resource management framework in SOM, not the product configuration.

References
SAP Learning Hub - S4C80 (SAP S/4HANA Subscription Order Management): Unit on "Subscription Contract Changes."

Explanation:

In SAP Convergent Invoicing (CI), the billing process groups Billable Items (BITs) into billing documents based on specific criteria. To ensure financial and legal consistency, the system applies Hard Aggregation (grouping by default) on fields that define the core identity of the receivable.

B. Business partner:
A billing document is a legal subledger entity tied to a specific entity. You cannot combine multiple customers into a single billing document.

C. Billing process:
This field defines how the items are processed (e.g., periodic billing vs. ad-hoc). Items belonging to different billing processes cannot be mixed because they may follow different selection and grouping rules.

E. Contract account:
This is the foundational link to FI-CA. Since payments and dunning are managed at the contract account level, all items in a single billing document must point to the same account to ensure correct financial posting.

Why the Other Options are Incorrect

A. Billable item type:
This field is used to classify the source or category of the item (e.g., usage vs. recurring charge). By default, different BIT types can be grouped into the same billing document unless you explicitly configure a "Grouping Variant" to separate them.

D. Billing subprocess:
Subprocesses are used to further divide billing within a main process. While they are often used for separation, they are not part of the mandatory hard-coded grouping criteria by default. You have the flexibility to group multiple subprocesses into one document if your configuration allows it.

References
SAP Learning Hub - AC235 (SAP Convergent Invoicing): Unit on "Billing Functions" and "Selection and Grouping of Billable Items."