You want to assign your 3 newly created company codes to the same controlling area. Which settings must be common to all the company codes? Note: There are 2 correct answers to this question.
Correct Answer: B,C
When assigning newly created company codes to the same controlling area in SAP S/4HANA, it is essential to ensure that certain settings are consistent across all company codes. The required common settings include: * Fiscal year variant: The fiscal year variant defines the financial periods and special periods used for accounting. Having a common fiscal year variant ensures that all company codes within the same controlling area follow the same financial period structure, facilitating consolidated financial reporting and management. * Operating chart of accounts: The operating chart of accounts is the primary list of accounts used for financial accounting. It must be uniform across all company codes in the same controlling area to ensure consistent financial data recording and reporting, enabling accurate internal and external financial analysis. These settings ensure that financial data is harmonized across the company codes, supporting integrated financial management and reporting. References * [25:27†Procedimiento Creacion nuevos elementos (Cta,PosLiq,Cege,Fondo,Recurrencia)v2 (1).docx] * [27:3†MEGA_Manual-de-usuario_Business-Partner_v0.pdf]
Question 32
You perform the depreciation run for your assets. For a specific asset, you would like to post the depreciation costs to a different cost center than the one specified in the asset master data. How do you achieve this?
Correct Answer: B
Question 33
You post a vendor invoice for asset acquisition without reference to a purchase order. Which accounting documents are generated?
Correct Answer: C
Comprehensive Detailed Explanation with all SAP S/4HANA Cloud References In SAP S/4HANA, when you post a vendor invoice for asset acquisition without reference to a purchase order , the system generates accounting documents based on the configured ledgers and accounting principles. Specifically, it creates: * One document per accounting principle (for parallel accounting requirements, such as local GAAP and IFRS). * One document for all accounting principles (to consolidate postings across all ledgers). Let's analyze each option to determine the correct answer. Explanation of Each Option: C. One document per accounting principle & one document for all accounting principles * Correct : In SAP S/4HANA, when posting a vendor invoice for asset acquisition without a purchase order, the system generates: * One document per accounting principle : This ensures compliance with parallel accounting requirements. Each ledger (representing a specific accounting principle) receives its own document to reflect the transaction according to the respective accounting rules. * One document for all accounting principles : This consolidates the postings across all ledgers into a single document for the leading ledger (OL). The leading ledger serves as the primary record for external financial reporting. * Reference : According to SAP documentation, this dual-document approach is a key feature of SAP S /4HANA's simplified data model, ensuring both detailed and consolidated reporting. A. One document per accounting principle * Incorrect : While this is partially true (as separate documents are generated for each accounting principle), it does not account for the additional document created for all accounting principles in the leading ledger. This option is incomplete and therefore incorrect. * Reference : SAP S/4HANA generates both individual and consolidated documents to meet parallel accounting and consolidation needs. B. One document for all accounting principles * Incorrect : This option suggests that only a single document is generated for all accounting principles. However, SAP S/4HANA also creates separate documents for each accounting principle to comply with parallel accounting requirements. This option overlooks the need for ledger-specific postings. * Reference : The system must generate separate documents for each accounting principle to ensure accurate reporting under different standards (e.g., local GAAP vs. IFRS). D. Separate documents for each and every accounting principle * Incorrect : While separate documents are generated for each accounting principle, this option fails to mention the additional document created for all accounting principles in the leading ledger. It is therefore incomplete and incorrect. * Reference : SAP S/4HANA's architecture ensures that both ledger-specific and consolidated documents are created to meet reporting and reconciliation requirements. Key References to SAP S/4HANA Documentation: * SAP S/4HANA Finance for Parallel Accounting : Explains how SAP S/4HANA handles parallel accounting requirements using multiple ledgers and generates corresponding documents. * SAP Help Portal - Universal Journal (ACDOCA) : Provides detailed guidance on how the Universal Journal supports the generation of documents for multiple accounting principles. * Vendor Invoice Posting Without Purchase Order : Describes the accounting documents generated during vendor invoice postings for asset acquisitions. * Leading Ledger and Non-Leading Ledgers : Highlights the role of the leading ledger in consolidating postings across all accounting principles.
Question 34
Which parameters can you configure on the dunning level? Note: There are 2 correct answers to this question.
Correct Answer: A,B
In SAP S/4HANA, the dunning level is a key component of the dunning process, which is used to remind customers about overdue payments. Each dunning level represents a stage in the dunning process (e.g., first reminder, second reminder, final notice) and can be configured with specific parameters to control how dunning is executed. Let's analyze each option to determine the correct answers. Explanation of Each Option: A. Days in arrears * Correct : The days in arrears parameter can be configured on the dunning level. This parameter specifies the minimum number of days an invoice or payment must be overdue before it qualifies for inclusion in the dunning run at a specific dunning level. For example, a first reminder might only include items that are 10 days overdue, while a second reminder might include items that are 30 days overdue. * Reference : According to SAP documentation, the "days in arrears" setting is a critical parameter for determining which overdue items are included in each dunning level. B. Payment deadline * Correct : The payment deadline parameter can also be configured on the dunning level. This parameter specifies the date by which the customer must make the payment to avoid further escalation (e.g., additional reminders or legal action). The payment deadline is often displayed on the dunning letter to inform the customer of the urgency of the payment. * Reference : SAP documentation confirms that the payment deadline is configurable per dunning level to provide clear instructions to the customer and ensure timely payments. C. Interest indicator * Incorrect : The interest indicator is not configured at the dunning level. Instead, it is defined at the account or transaction level to calculate interest on overdue payments. While interest calculations may influence the dunning process, the interest indicator itself is not a parameter of the dunning level. * Reference : Interest indicators are part of the interest calculation configuration and are unrelated to dunning levels. D. Line item grace period * Incorrect : The line item grace period is not a parameter that can be configured on the dunning level. Instead, it is typically defined at the company code or account level to specify a grace period for individual line items before they are considered overdue. This parameter does not directly impact the dunning level configuration. * Reference : Grace periods are managed separately from dunning levels and are not part of the dunning level setup. Key References to SAP Documentation: * SAP S/4HANA Finance for Accounts Receivable : Explains the configuration of dunning levels and their parameters, including days in arrears and payment deadlines. * SAP Help Portal - Dunning Process : Provides detailed guidance on configuring dunning levels and their impact on the dunning process. * Dunning Parameters in SAP S/4HANA : Highlights the role of days in arrears and payment deadlines in determining dunning eligibility and actions. * Interest Calculation Configuration : Describes how interest indicators are configured independently of dunning levels.
Question 35
How are pages assigned to users on the SAP Fiori Launchpad?
