When using the Local SAP S/4HANA Database Schema migration approach, what is the maximum file
size?
Note: There are 2 correct answers to this question.
A, B
Explanation:
Comprehensive and Detailed in Depth Explanation:
The Local SAP S/4HANA Database Schema approach in the Migration Cockpit uses staging tables to
load data, with file size limits defined by SAP to ensure performance and stability.
Option A (160 MB per file): Correct. Individual files uploaded to staging tables have a maximum size
of 160 MB, as per SAP’s technical specifications.
Option B (160 MB per ZIP file): Correct. When files are compressed into ZIP format, the total size limit
remains 160 MB, accommodating multiple files within this constraint.
Option C (100 MB per ZIP file): Incorrect. The limit is 160 MB, not 100 MB, for ZIP files.
Option D (100 MB per file): Incorrect. The limit for individual files is 160 MB, not 100 MB.
Reference:: SAP S/4HANA Cloud Migration Cockpit Technical Guide, "File Upload Specifications" (SAP
Help Portal).
How can you migrate data to S/4HANA Cloud Public Edition?
A
Explanation:
Comprehensive and Detailed in Depth Explanation:
Data migration to SAP S/4HANA Cloud Public Edition is facilitated through the Migration Cockpit,
with specific supported methods.
Option A (With XML or CSV templates): Correct. The Migration Cockpit supports file-based migration
using predefined XML or CSV templates, which users populate with legacy data for upload.
Option B (With Core Data Services): Incorrect. Core Data Services (CDS) are used for data modeling
and reporting in SAP S/4HANA, not for data migration.
Option C (With the zero downtime service): Incorrect. Zero downtime is a deployment strategy for
upgrades, not a data migration method.
Option D (With a separate SAP HANA database): Incorrect. While SAP HANA underpins S/4HANA, a
separate database is not a migration method; the Migration Cockpit uses integrated staging tables or
files.
Reference:: SAP S/4HANA Cloud Data Migration Guide, "Supported Migration Approaches" (SAP Help
Portal).
When processing manual incoming payments, which of the following options can be used to manage
payment differences?
Note: There are 3 correct answers to this question.
C, D, E
Explanation:
Comprehensive and Detailed in Depth Explanation:
In SAP S/4HANA Cloud Financial Accounting, managing payment differences during manual incoming
payments is a key Accounts Receivable process.
Option C (Residual payment): Correct. Residual payments allow the remaining open amount
(difference) to be posted as a new open item, clearing the original invoice partially.
Option D (Partial payment): Correct. Partial payments reduce the open invoice amount without
clearing it fully, leaving the balance open.
Option E (Payment on account): Correct. Payments can be posted to the customer’s account without
clearing specific invoices, often used when the payment cannot be matched.
Option A (Individual value adjustment): Incorrect. This relates to bad debt provisioning, not payment
difference management.
Option B (Return payment): Incorrect. This is not a standard SAP term for handling differences; it
implies reversing a payment, not managing variances.
Reference:: SAP S/4HANA Cloud Financial Accounting, "Manual Payment Processing" (SAP Help
Portal).
You post and match an incoming payment to the incorrect customer account. How can you correct
the mistake?
B
Explanation:
Comprehensive and Detailed in Depth Explanation:
Correcting an incorrect payment posting in SAP S/4HANA Cloud involves reversing the erroneous
clearing and reprocessing the payment.
Option B (Reset the clearing and reverse the document): Correct. Using the "Reset Cleared Items"
function (e.g., via app "Manage Customer Line Items"), you can reset the clearing, then reverse the
payment document (FB08 or Fiori app "Reverse Document") and repost it to the correct customer.
This is the standard process.
Option A (Change the customer on the payment document): Incorrect. Posted documents cannot be
directly edited to change the customer; SAP locks master data fields post-posting.
Option C (Issue a credit memo to the customer): Incorrect. A credit memo addresses overpayments
or returns, not misapplied payments.
Option D (Contact the customer through correspondence): Incorrect. This is an operational step, not
a system correction method.
Reference:: SAP S/4HANA Cloud Financial Accounting, "Correcting Payment Postings" (SAP Help
Portal).
Which editing options are available in the dunning proposal list?
Note: There are 3 correct answers to this question.
A, C, D
Explanation:
Comprehensive and Detailed in Depth Explanation:
The dunning proposal list in SAP S/4HANA Cloud (accessed via the "Manage Dunning" app) allows
users to adjust dunning notices before they are finalized.
Option A (Change the dunning charges): Correct. Users can modify dunning fees/charges in the
proposal to reflect specific agreements or policies.
Option C (Edit dunning blocks at account level): Correct. Dunning blocks can be set or removed at the
customer account level to prevent or allow dunning.
Option D (Edit dunning blocks at line item level): Correct. Blocks can also be adjusted for specific
open items, offering granular control.
Option B (Editing the dunning texts): Incorrect. Dunning texts are predefined in configuration (e.g.,
via "Define Dunning Procedure") and cannot be freely edited in the proposal list.
Option E (Change the dunning level of an open item): Incorrect. Dunning levels are system-calculated
based on overdue days and the dunning procedure, not manually editable in the proposal.
Reference:: SAP S/4HANA Cloud Financial Accounting, "Dunning Process Overview" (SAP Help
Portal).
When processing payments, what are possible functions of reason codes?
Note: There are 3 correct answers to this question.
B, C, D
Explanation:
Comprehensive and Detailed in Depth Explanation:
Reason codes in SAP S/4HANA Cloud Financial Accounting are used to handle payment differences
and automate related processes.
B: Correct. Reason codes can trigger automatic posting of residual items to predefined G/L accounts
(e.g., write-off accounts).
C: Correct. They control the G/L account assignment for residuals, ensuring accurate financial
reporting.
D: Correct. Reason codes can influence the type of payment notice (e.g., partial payment
notification) sent to customers.
A: Incorrect. Sales orders are unrelated to payment processing reason codes.
E: Incorrect. Payment reminders are part of dunning, not directly tied to reason codes.
Reference:: SAP Help Portal - "Reason Codes in Accounts Receivable."
Which of the following fields are maintained on the general data segment of the customer business
partner?
Note: There are 2 correct answers to this question.
A, C
Explanation:
Comprehensive and Detailed in Depth Explanation:
The general data segment of a customer business partner in SAP S/4HANA Cloud is maintained at the
business partner level, not company code-specific.
A: Correct. Communication language is set in the general data (e.g., BP role FLCU01).
C: Correct. Payment method is part of general payment data, applicable across company codes
unless overridden.
B: Incorrect. Bank key is maintained in the payment transactions tab, not general data.
D: Incorrect. Company code is specific data, not part of the general segment.
Reference:: SAP Help Portal - "Business Partner Maintenance in SAP S/4HANA."
Which field can be changed in a posted invoice?
Note: There are 3 correct answers to this question.
B, D, E
Explanation:
Comprehensive and Detailed in Depth Explanation:
In SAP S/4HANA Cloud, posted invoices have limited editable fields due to audit and integrity rules.
B: Correct. Profit center can be changed via "Change Document" (FB02 equivalent in Fiori).
D: Correct. Line item text is editable post-posting for descriptive purposes.
E: Correct. Reference field can be updated for tracking purposes.
A: Incorrect. Invoice amount is locked after posting to maintain financial integrity.
C: Incorrect. Payment terms are fixed post-posting unless reversed.
Reference:: SAP Help Portal - "Editing Posted Documents."
What are the effects of a goods issue posting?
Note: There are 2 correct answers to this question.
A, B
Explanation:
Comprehensive and Detailed in Depth Explanation:
A goods issue in SAP S/4HANA Cloud (e.g., via "Post Goods Issue" app) impacts inventory and
accounting.
A: Correct. It generates an accounting document (e.g., Dr. COGS, Cr. Inventory).
B: Correct. Inventory value decreases due to stock reduction.
C: Incorrect. Invoices are linked to billing, not goods issue.
D: Incorrect. Goods issue reduces, not increases, inventory value.
Reference:: SAP Help Portal - "Goods Movement in Inventory Management."
At which point in the integrated sales process is a balance sheet-relevant accounting document
created?
D
Explanation:
Comprehensive and Detailed in Depth Explanation:
In the SAP S/4HANA Cloud sales process, balance sheet-relevant postings occur when inventory is
affected.
D: Correct. Goods issue posts to inventory and expense accounts (e.g., Dr. COGS, Cr. Inventory),
impacting the balance sheet.
A, B, C: Incorrect. These steps (confirmation, quotation, sales order) are preliminary and do not
generate accounting documents.
Reference:: SAP Help Portal - "Order-to-Cash Process."