In which type of extensibility is the SAP Business Technology Platform used to host a custom extension?
Answer : C
Comprehensive and Detailed in Depth Explanation:
SAP BTP hosts external extensions in S/4HANA Cloud.
C: Correct. Side-by-side uses BTP for custom apps.
A, B, D: Incorrect. These are in-app or different approaches.
A fixed asset you ordered is delivered but is not activated. What could be the reason?
Answer : C
If you cannot find a prepackaged solution process that addresses integration requirements, where would you look?
Answer : B
Comprehensive and Detailed in Depth Explanation:
Prepackaged solutions are centralized for easy access.
B: Correct. Business Accelerator Hub offers integration content.
A, C, D, E: Incorrect. These provide tools or info, not solutions.
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.
Answer : A, C
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.
What provides a foundation for the SAP Cloud ERP where integrations and extensions live?
Answer : D
Comprehensive and Detailed in Depth Explanation:
SAP BTP underpins SAP S/4HANA Cloud extensibility.
D: Correct. BTP hosts integrations and extensions.
A, B, C: Incorrect. These are tools or environments, not the foundation.
Which editing options are available in the dunning proposal list?
Note: There are 3 correct answers to this question.
Answer : A, C, D
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.
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.
Answer : A, B
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.