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

Explanation:

In SAP S/4HANA Cloud Sales, discount groups control how pricing conditions (like discounts or surcharges) are applied. Sometimes, you may want to exclude certain discount groups for specific objects in pricing.

B.Item Master (Material Master in S/4HANA)
You can maintain discount exclusions at the item level, meaning a particular product can be excluded from certain discount groups.

This is useful when a product should not participate in certain promotional or customer-specific discounts.

D.Pricelist
A pricelist can also define which discount groups to include or exclude.
By excluding discount groups at the pricelist level, you ensure that certain discounts do not apply to specific pricing lists, regardless of the customer or item.

Why not the others?

A.Business Partner Master:
While you can assign discount groups to customers, exclusion of discount groups specifically is not maintained here; it's more about applying discounts, not excluding them.

C.Marketing Document:
Discount exclusions are not maintained at the document level. Pricing in the document references master data and pricelists, which control the actual discount behavior.

Reference:
SAP Help Portal – Define Discount Groups and Exclusions: SAP S/4HANA Cloud Sales Documentation
SAP Learning Hub – Pricing in SAP S/4HANA Cloud: Discounts and Surcharges.

Explanation:

A. Management Method On Every Transaction ✅
This setting requires the system to record the serial number at every transaction (goods issue, delivery, sales, etc.).
It guarantees full traceability of each item across the supply chain.
Without this, you might only track items at limited points (e.g., release only), which doesn’t meet the requirement of tracking both warehouse exit and customer delivery.

B. Management Method: On Release Only ❌
This optio
n only records serial numbers when items are released from inventory. It does not provide tracking at delivery to the customer, so it fails the requirement.

C. Manage Item by: Batches ❌
Batch management groups items into lots (e.g., production runs, expiration dates).
It allows tracking at the batch level, not the individual item level.
Since the company wants individual tracking, batches are insufficient.

D. Manage Item by: Serial Numbers ✅
Serial numbers uniquely identify each item.
This is essential for individual tracking, ensuring that each piece can be traced from warehouse to customer.
SAP documentation confirms that serial number management is the correct method for tracking individual items.

References
SAP Help Portal: Working with Serial Numbers — explains how serial numbers uniquely identify items and enable tracking across transactions.

Explanation:

To continue legacy document numbers seamlessly in a new SAP Business One system without breaks or gaps, SAP recommends two standard methods during implementation:

D (Primary series + change starting number):
In a fresh company database, the default Primary series starts at 1 for each document type. Before posting any document, navigate to Administration → System Initialization → Document Numbering, double-click the document type row, and update the First No. (starting number) to the next number after the last legacy one (e.g., legacy ended at 5000 → set to 5001). This enables automatic, gap-free continuation once live documents are created. The change is only possible before the first document is posted; afterward, the starting number locks.

A (Manual numbering series):
Select the built-in Manual series in the document header (dropdown). This allows direct entry of exact legacy numbers when inputting historical/open documents (e.g., during data migration or cutover). It requires the "Document – Manual Numbering" authorization and ensures original numbers are retained for continuity, compliance, or reporting. The system prevents duplicates by skipping conflicts in future auto-numbering.

Why the other options are incorrect:

B. Define a new series starting with the next legacy number:
Creating an additional series starts a separate range. Future documents use this new series, but it does not maintain one continuous sequence from legacy → primary, leading to a perceived or actual break in the logical numbering flow.

C. Use the primary series with a prefix for the legacy numbers:
Adding a prefix (e.g., "LEG-") alters the number format, breaking exact continuity with legacy numbers and creating visual/functional inconsistency.
These approaches follow SAP best practices for legacy continuity.

References:

SAP Learning: "Implementing Document and Master Data Numbering" – explicitly covers editing Primary series starting number before first document and using Manual series for exact legacy numbers.

Explanation:

In SAP S/4HANA Cloud, capacity planning for production is managed through Resource Master Data, not material or employee master data. Resources are categorized by type (e.g., Labor, Machine) and define available capacity for scheduling in routings and production orders. A Machine Resource models equipment like a calibration machine, while a Labor Resource represents human operators like technicians, enabling precise capacity checks and scheduling.

Why other options are incorrect:

A & D (Item Master Data):
Item/master material data is for materials consumed or produced, not for planning capacity. Machines and employees are not inventory items.

C (Forecast for technician):
Forecasts are for material demand planning, not for scheduling individual labor capacity in production operations. Labor resources are the direct objects for operational capacity planning.

References:
SAP Best Practices scope item J10 (Production Engineering and Operations) details resource setup.
Configuration via “Manage Resources” app (SAP Fiori ID F2012).
Core PP concept: Resources are assigned to routing operations for capacity scheduling in production orders.

Explanation:

In SAP S/4HANA Cloud, the Aging Date (often referred to as the Key Date) serves as the reference point or "snapshot" date for the report. The system calculates the age of an open item by determining the number of days elapsed between the document's specific date (usually the Net Due Date) and this Aging Date. If an invoice is due on January 1st and the Aging Date is set to January 31st, the report identifies that debt as 30 days old.

Analysis of Incorrect Options

Option A (The due date of the transaction):
This is incorrect because the Due Date is a static attribute of the specific invoice. While the report uses the Due Date as the starting point for the calculation, it is not the "Aging Date" itself. The Aging Date is the variable "as of" date chosen by the user to run the report.

Option B (The age interval in which the debts are distributed):
This refers to Aging Buckets or Aging Periods (e.g., 30, 60, or 90 days). These intervals represent the structure of the report's columns where debts are sorted once their age has been calculated using the Aging Date.

References
SAP Learning Hub (S4C60):
"Sales Processes in SAP S/4HANA Cloud Public Edition." This course details how the Digital Core handles receivables and real-time reporting.

Explanation:

In SAP S/4HANA (and accounting in general):
Revenue accounts reflect sales revenue earned by the company.

Transactions that increase revenue:
When yo
u post an Accounts Receivable (A/R) invoice, you are recording a sale to a customer. This credits the revenue account (increases revenue on the financial statements) and debits A/R (increases what the customer owes you).

Why not the others?

A. Incoming payment
→ This decreases A/R (the customer pays) but does not affect revenue, because revenue was already recognized when invoiced.

B. Capitalization
→ This affects asset accounts, not revenue. It converts expenses into assets.

D. A/R credit memo
→ This reduces revenue because it is essentially a refund or reduction in sales.

Reference:
SAP S/4HANA Finance – Revenue Recognition and Posting Logic: SAP Help Portal
SAP Learning Hub – Accounts Receivable and Revenue Accounting.

Explanation:

In SAP semantic layer views (used in reporting and analytics), dimensions are descriptive, categorical fields that allow you to slice and filter data. They are not aggregated measures but rather attributes that provide context.

A. Posting date ✅
Dates are classic dimensions because they allow analysis across time (e.g., monthly sales, yearly trends).
You can group or filter transactions by posting date.

B. Item code ✅
Item codes identify products or materials.
As a categorical attribute, they are used to break down measures (like sales quantity or revenue) by product.

C. Item quantity ❌
This is a measure, not a dimension. It represents a numeric value that can be aggregated (sum, average, etc.).

D. Document total ❌
Also a measure, since it represents monetary values that are aggregated in reporting.

📘Reference
SAP documentation on Semantic Layer Views explains that:
Dimensions = descriptive attributes (e.g., dates, codes, categories).
Measures = numeric values for aggregation (e.g., quantities, totals).