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

Explanation:

In SAP S/4HANA Cloud, when you post a journal entry to transfer balances between two customers, each line item must specify the relevant Business Partner (Customer). To select a customer, you navigate to the Business Partner field in the journal entry screen and press Tab. This action opens a list of available business partners, allowing you to choose the appropriate customer for debit or credit. This is the standard and supported method in the system for selecting business partners in journal entries.

Why the other options are incorrect:

A. Press Ctrl + Tab
→ This keyboard combination is not used for selecting business partners in SAP. It has no function in this context.

C. Double click
→ Double-clicking does not open the business partner selection list; navigation is controlled via the Tab key.

D. Choose the list from the context menu
→ The business partner list is accessed directly from the field, not via right-click context menus, making this option invalid.

This approach ensures accurate recording of transactions between customers while maintaining correct A/R balances in the system. Following the standard procedure prevents posting errors and ensures proper accounting for inter-customer balance transfers.

References:
SAP Help Portal – Post Journal Entries in SAP S/4HANA Cloud:
SAP Learning Hub – Finance: General Ledger Accounting in SAP S/4HANA Cloud.

Explanation:

When a customer database needs to be transferred to SAP support (for troubleshooting, issue resolution, or analysis), the Remote Support Platform (RSP) is the designated tool.

A. Support Launchpad ❌
SAP Support Launchpad is a portal for accessing SAP notes, incident management, and knowledge base articles.
It does not handle database transfers.

B. System Landscape Directory ❌
This tool manages system landscape information (like system IDs, connections, and configurations).
It is not used for transferring customer databases.

C. System Data Maintenance ❌
This is used to maintain system-related data for reporting and monitoring.
It does not provide functionality for database transfer.

D. Remote Support Platform ✅
RSP is specifically designed to securely transfer customer databases and logs to SAP support.
It ensures encrypted communication and compliance with SAP’s support processes.
This is the official method for consultants to send customer databases for issue resolution.

Reference:
SAP Help Portal and SAP Business One documentation confirm that Remote Support Platform (RSP) is the tool used to upload and transfer customer databases to SAP support for analysis.

Explanation:

In SAP Business One (version for SAP HANA), the requirement calls for a high-level, at-a-glance view of on-time delivery compliance (a percentage metric), with the ability to drill down into detailed, real-time statistics on deliveries, returns, and average order fulfillment time when the value is low.

A (KPI with action to advanced dashboard) is the best fit:
Create or use a Key Performance Indicator (KPI) widget (e.g., "On-Time Delivery Rate") placed in the user's cockpit for immediate visibility. KPIs display a single key metric (percentage) with goal/trend tracking and color-coding (e.g., red for low compliance). Add an action to the KPI that launches an advanced dashboard upon clicking. The advanced dashboard acts as a supplementary cockpit containing multiple pervasive dashboards and additional KPIs/charts for drill-down details (e.g., real-time views of on-time vs. delayed deliveries, returns analysis, average fulfillment days by customer/month). This provides seamless navigation from summary to granular real-time insights.

SAP provides predefined KPIs and pervasive dashboards for on-time delivery and average fulfillment days, which can be extended with custom actions.

Why the other options are incorrect:

B. A pervasive dashboard with actions to open additional pervasive dashboards:
Pervasive dashboards offer detailed visualizations but are not ideal for a simple "at-a-glance" single percentage metric. Linking to more pervasive dashboards adds layers but lacks the focused, goal-oriented summary of a KPI and is less efficient for quick compliance checks.

C. An advanced dashboard in his cockpit:
Advanced dashboards provide rich, multi-page details but are supplementary cockpits launched from KPIs/pervasive dashboards. Placing one directly in the main cockpit does not deliver a concise, glanceable percentage view first—it starts with too much detail without the high-level trigger.

References:

SAP Help Portal: "Predefined Advanced Dashboards" and "How to Work with Pervasive Analytics" – describe On-Time Delivery Rate KPI, pervasive dashboards (e.g., Avg. Ord. Fulfillment Days), and actions to launch advanced dashboards.

Explanation:

In SAP S/4HANA Cloud Public Edition, system behavior and UI elements are controlled through UI adaptation and configuration templates, not by direct customizing or authorization changes. To remove the Payment Wizard from all forms, you must use a UI configuration template to hide the corresponding UI button or tile. This ensures the function is hidden at the presentation layer across the relevant apps.

Why other options are incorrect:

B: Form settings typically control layout or printing, not UI menu visibility for transactional functions like the Payment Wizard.

C: Removing authorizations would restrict access but not hide the function from the UI, and it would affect only users without authorization—not remove it completely.

D: There is no “general settings” option in S/4HANA Cloud to globally hide specific transactional functions like the Payment Wizard.

References:
SAP Help: “Configure UI Adaptation” and “UI Configuration Templates” in the SAP S/4HANA Cloud application help.

Explanation:

In SAP (and specifically within the context of the C_TB120_2504 exam, which aligns with SAP Business One logic for this question), Internal Reconciliation is the process used to match and clear open credit items (like payments) against open debit items (like invoices) within the same account.

When a company pays a vendor in advance, a "Payment on Account" or "Down Payment" is created as an open item in the vendor’s ledger. Later, when the actual invoices are received and posted, they also appear as open items. To "connect" them and ensure the vendor balance is accurate, an accountant must perform an internal reconciliation. This process matches the credit (payment) with the debits (invoices), effectively "clearing" them from the open items list.

Analysis of Incorrect Options

A & B (Bank Account Reconciliations):
These are incorrect because they deal with matching the company’s internal bank ledger against the physical bank statement (external data). While the payment appeared in the bank statement, the act of linking that payment specifically to vendor invoices happens in the subledger (the vendor's account), not the bank account.

D (External reconciliation for vendor master data):
This is incorrect because external reconciliation involves comparing your company's records with an external statement provided by a business partner (like a vendor statement sent by mail). Internal reconciliation is the specific tool used to knock off internal open items against each other.

Reference

SAP Business One Curriculum (TB1200): The section on "Internal Reconciliation" explains that while many reconciliations happen automatically (e.g., when a payment is made directly against an invoice), manual internal reconciliation is required for "Payments on Account" or advance payments to link them to subsequent invoices.

Explanation:

In SAP S/4HANA Cloud, data ownership controls who has responsibility for business documents and business partners. When the “Business Partner and Document” method is selected:

Ownership assignment logic:
The system first checks the business partner master data to see if an owner is assigned.
If no owner exists in the business partner master, the system then assigns ownership based on the document owner, i.e., the user creating the sales document (in this case, the sales quotation).
This ensures that every document has a responsible owner, even if the business partner itself has no assigned owner.

Why not the other options?

A. Based on the company relationship
→ Company relationship affects organizational assignments, not individual document ownership.

B. Based on the business partner contact
→ Contact persons in the business partner record are used for communication, not for ownership rules.

C. Based on the sales employee’s authorizations
→ Authorizations control access, not ownership assignment.
This rule ensures that the sales quotation is always properly assigned, maintaining clear responsibility for sales processes.

References:
SAP Help Portal – Data Ownership in SAP S/4HANA Cloud:
SAP Learning Hub – Sales: Business Partner and Document Ownership Rules

Explanation:

In SAP Business One, when you create a new G/L account, you can define it either as a title account or as a posting account.
Title accounts are used only for structuring the chart of accounts (like headers or grouping accounts).
They cannot be used for postings in journal entries.
Therefore, if the accountant mistakenly defined the new G/L account for employee bonuses as a title, it will not appear in the journal entry window.

Why the other options are incorrect

A. Relevant for cost accounting ❌
This setting only determines whether the account is included in cost accounting reports.
It does not affect whether the account appears in the journal entry window.

C. Wrong drawer ❌
Placing the account in a different drawer (Assets, Liabilities, Expenses, etc.) does not prevent it from appearing in journal entries.
It only affects classification in the chart of accounts.

D. Account type set to Other ❌
"Other" is still a valid posting account type.
It would still appear in the journal entry window unless it was defined as a title.

Reference
SAP Business One Help Portal: Chart of Accounts — explains that title accounts are non-posting accounts used for grouping, while active accounts are available for journal entries.