You post an incoming payment from a customer with a residual item for a payment difference. What are the consequences? Note: There are 2 correct answers to this question.
Correct Answer: A,C
Question 12
Which of the following API types does SAP recommend to use to achieve clean core integrations? Note: There are 2 correct answers to this question.
Correct Answer: B,C
In SAP S/4HANA, achieving a clean core is a key principle of modern SAP implementations. A clean core means minimizing customizations in the core system and leveraging standard APIs for integrations. SAP provides various API types, but not all are recommended for clean core integrations. Let's analyze each option to determine the correct answers. Explanation of Each Option: B. OData * Correct : OData (Open Data Protocol) is a modern, RESTful API standard that SAP strongly recommends for clean core integrations. It is part of SAP's strategy for cloud-based and hybrid integrations and aligns with the principles of a clean core by providing standardized, lightweight, and scalable interfaces. OData APIs are used extensively in SAP S/4HANA Cloud and on-premise systems for real-time data exchange. * Reference : According to SAP documentation, OData APIs are the preferred choice for modern integrations, especially in cloud environments, as they support clean core principles by avoiding deep customizations. C. IDoc * Correct : IDoc (Intermediate Document) is a legacy integration technology that SAP still supports for specific use cases, particularly in on-premise systems or when integrating with older SAP systems. While it is not as modern as OData, it is considered a clean core-compatible integration method because it uses standard SAP interfaces without requiring modifications to the core system. IDocs are often used for batch processing and asynchronous communication. * Reference : SAP documentation confirms that IDocs are a standard integration method that can be used in clean core scenarios, especially when modern APIs like OData are not feasible. A. SOAP * Incorrect : SOAP (Simple Object Access Protocol) is an older web service protocol that SAP has largely replaced with modern RESTful APIs like OData. While SOAP is still supported in some legacy systems, it is not recommended for clean core integrations because it is less flexible and more complex compared to OData. SAP encourages customers to transition away from SOAP to more modern standards. * Reference : SAP promotes OData over SOAP for clean core integrations due to its simplicity, scalability, and alignment with modern IT architectures. D. RFC * Incorrect : RFC (Remote Function Call) is another legacy technology used for direct function module calls between SAP systems. While RFC is widely used in traditional SAP landscapes, it is not recommended for clean core integrations because it often requires custom development and deep integration into the core system. This contradicts the clean core principle of minimizing customizations. * Reference : SAP advises against using RFC for clean core integrations, as it does not align with modern integration best practices. Key References to SAP Documentation: * SAP Integration Suite Overview : Explains the role of OData APIs in modern SAP integrations and their alignment with clean core principles. * SAP Help Portal - OData Services : Provides detailed guidance on using OData APIs for cloud and on-premise integrations. * SAP IDoc Documentation : Highlights the use of IDocs as a standard integration method for specific scenarios, particularly in legacy systems. * SAP Clean Core Strategy : Describes the importance of using standard APIs like OData and IDoc to maintain a clean core and avoid customizations.
Question 13
Which of the following currency types can be defined for a specific ledger? Note: There are 3 correct answers to this question.
Correct Answer: B,D,E
Comprehensive Detailed Explanation with all SAP S/4HANA Cloud References In SAP S/4HANA, ledgers are used to manage financial accounting data and support parallel accounting requirements (e.g., local GAAP vs. IFRS). Each ledger can be configured with specific currency types to meet reporting and compliance needs. Let's analyze each option to determine which currency types can be defined for a specific ledger. Explanation of Each Option: B. 00 = Document currency * Correct : The document currency (currency type 00) is the currency in which a financial transaction is originally recorded. It is always available in every ledger because it ensures that the original transaction amount is preserved for reporting and reconciliation purposes. * For example, if an invoice is issued in USD, the document currency will be USD. This currency type is essential for maintaining accurate financial records. * Reference : According to SAP documentation, the document currency is stored in the Universal Journal (ACDOCA) and is a mandatory field for every financial posting. D. 10 = Company code currency * Correct : The company code currency (currency type 10) is the default currency of the company code. It is automatically available in every ledger and is used as the primary currency for legal reporting and balance sheet preparation. * For example, if the company code currency is EUR, all postings are converted to EUR for reporting purposes, regardless of the document currency. * Reference : The company code currency is defined during the creation of the company code and is a key component of financial reporting at the company code level. E. 30 = Group currency * Correct : The group currency (currency type 30) is used for consolidation purposes and represents the currency of the corporate group or headquarters. It can be defined for specific ledgers to support group reporting requirements, such as preparing consolidated financial statements. * For example, if the group currency is USD, financial data from multiple company codes can be converted to USD for consolidation. * Reference : Group currency is critical for external reporting under IFRS and is supported in SAP S /4HANA through ledger configuration. A. 60 = Global company currency * Incorrect : The global company currency (currency type 60) is not a standard currency type in SAP S /4HANA. While some custom implementations might use this term, it is not officially recognized in SAP documentation for ledger configuration. * Reference : SAP S/4HANA supports predefined currency types like document currency, company code currency, and group currency, but global company currency is not part of the standard configuration. C. 40 = Hard currency * Incorrect : Hard currency (currency type 40) is a special currency type used in countries with high inflation or currency instability. It is not typically defined for specific ledgers unless required by local regulations. * Reference : Hard currency is optional and is only relevant in specific scenarios, such as hyperinflationary economies. It is not a standard requirement for ledger configuration. Key References to SAP S/4HANA Documentation: * SAP S/4HANA Finance for Parallel Accounting : Explains how different currency types are used in ledgers to support parallel accounting requirements. * SAP Help Portal - Currency Types in Ledgers : Provides detailed guidance on configuring currency types for specific ledgers. * Universal Journal (ACDOCA) : Highlights that document currency (00), company code currency (10), and group currency (30) are stored in the universal journal and are essential for financial reporting. * Group Reporting in SAP S/4HANA : Describes the use of group currency (30) for consolidation purposes.
Question 14
How does the system determine the relevant accounting principle when performing foreign currency valuation?
Correct Answer: A
Question 15
What are the consequences of the activation of segment reporting in Asset Accounting? Note: There are 2 correct answe-rs to this que-stion.
