C_S4CFI sample questions & answers

Steinweg Antriebe, a German automotive OEM rolling out finance across several plant company codes, is mid-implementation on SAP S/4HANA Cloud Public Edition with a three-system landscape. During a fit-to-standard workshop the finance lead asked a junior consultant to add a new document type and adjust a finance organizational setting so a test cycle could begin in the test system the same afternoon. To save time, the consultant logged into the test system directly and tried to create the document type there, then reported that the test system would not let the change be saved as a regular configuration entry, only as a temporary local edit. Meanwhile, the same setting that was already configured for the productive line could not be altered, because the implementation workspace is locked while productive operations continue. The workspace still shows the original configuration line as the active line, and the requested change has not appeared in any transport queued for the landscape. The finance lead now needs the change available in test so the cycle can run, without disturbing the running productive configuration, and without abandoning fit-to-standard discipline by hand-keying settings system by system.

Which approach correctly delivers the requested configuration change while preserving clean-core and landscape governance?

Helvetia Pharma, a Swiss pharmaceutical manufacturer preparing for go-live, is finalizing General Ledger master data on SAP S/4HANA Cloud Public Edition. A goods-receipt/invoice-receipt clearing account was created earlier in the project, but it was set up without open-item management active, so it was treated as an ordinary balance account. During integration testing, several procurement postings have already hit the account through goods receipts and supplier invoices, so it now carries a non-zero balance with matched and unmatched items mixed together. The accounting team reports that they cannot clear matched goods-receipt and invoice-receipt items against each other, and the reconciliation view shows the account behaving as a running balance rather than a clearable account, leaving open quantities impossible to age. A consultant attempts to switch on open-item management on the existing master record so the items can finally be matched, and finds the change is rejected by the system. The finance lead needs the account to support item-by-item clearing in time for go-live, while keeping the already-validated test postings traceable in the audit trail rather than simply discarding them.

What is the correct way to make the clearing account support open-item management given its current state?

Maple Harvest Grocers, a Canadian grocery retail chain with hundreds of suppliers, runs a scheduled automatic payment program twice weekly to settle supplier invoices on SAP S/4HANA Cloud Public Edition. A batch of due invoices for one regional produce supplier was expected in today's payment proposal but did not appear, even though the invoices are posted, approved through workflow, and past their baseline date. The accounts payable clerk confirms the invoices are not blocked at line or header level and the supplier is not on payment hold, and other suppliers in the same run paid normally. Reviewing the proposal log, the team sees this supplier's items listed as not selected, with a note that no valid payment route could be determined. The supplier was onboarded only last week for electronic transfer, and the bank details were entered on the business partner record and verified. The clerk re-ran the proposal with a later payment date to widen the window, but the same invoices were still excluded. The finance lead needs the payments to flow in the next run without forcing manual single payments for each invoice.

What is the most likely root cause and the correct corrective action so these invoices are selected in the next payment run?

Corrente Energia, a Brazilian electric utility billing millions of consumers, manages overdue receivables on SAP S/4HANA Cloud Public Edition using a configured dunning procedure with several dunning levels. A large group of commercial customers carries overdue customer down payments collected ahead of connection works, and finance wants those amounts included in dunning notices, but the latest dunning run never raised the dunning level for those items. The dunning run completed without error, the affected customers are well above the configured minimum amounts, and the down-payment items are clearly past their due date. The collections analyst confirms the standard open invoices for the same customers were dunned correctly in the same run and reached the expected levels, so the procedure itself is executing. Inspecting the dunning data, the analyst sees the down-payment items present on the customer accounts but flagged as not dunning-relevant. A colleague proposes simply raising the dunning level manually on each affected customer so the notices go out this cycle, while the finance lead wants a configuration fix that makes every future run handle these items automatically.

Which action correctly causes the overdue down-payment items to be dunned by the standard run going forward?

Aéronef Composites, a French aerospace components manufacturer with a large fixed-asset base, runs parallel valuation on SAP S/4HANA Cloud Public Edition with separate accounting principles for local statutory reporting and for group IFRS reporting. An asset under construction for a new tooling line was capitalized, and an acquisition value was posted that finance intended to apply to the group IFRS accounting principle only, because the statutory principle uses a different capitalization timing under local rules. After posting, the asset accountant reviews the asset values in the asset explorer and finds the acquisition reflected under both accounting principles, which distorts the statutory depreciation base and the resulting depreciation forecast. The posting completed successfully and produced a document, so no error or warning was raised at entry. The accountant confirms the asset class, useful life, and depreciation terms were all set correctly for both principles. The finance lead now needs the acquisition to affect only the group IFRS principle and must correct the entry that has already posted to both, without disturbing the unrelated capitalization postings already recorded on the same asset.

What went wrong and how should the accountant post acquisitions that must affect only one accounting principle?

Lion City Specialty Chemicals, a Singapore specialty chemicals producer reporting to an overseas parent, uses an extension ledger on SAP S/4HANA Cloud Public Edition to capture management-view adjustment postings on top of its standard ledger. As part of the month-end close, the controlling team posted several reclassification adjustments to the extension ledger to re-present certain costs for internal management reporting, and then ran a management report expecting it to show only those adjustments. Instead, the report returned the full base operational results plus the adjustments combined, and the team concluded the extension ledger was misconfigured because it appears to "duplicate" the base ledger data already held in the standard ledger. A junior consultant, under time pressure to close, proposes rebuilding the extension ledger as a separate standalone ledger so it holds only the adjustment figures and nothing else. The finance lead wants the management report to isolate the adjustment delta while keeping the extension ledger's design intact, and first needs to know whether the ledger is actually misconfigured at all.

How should the situation be interpreted and resolved so the management report reflects the intended adjustment view?