Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Practicing Clean Core Extensibility For SAP S/4HANA Cloud > Getting Started with SAP S/4HANA Cloud, Extensions, and Clean Core > Flashcards

Getting Started with SAP S/4HANA Cloud, Extensions, and Clean Core Flashcards

1
Q

What is a software extension?

A

A software extension is a modification or addition to the standard software to meet specific customer needs without altering the original codebase.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Why are software extensions important?

A

They provide flexibility, allowing customization to meet unique business requirements, enhancing software value.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Why did SAP reject a “frozen” codebase?

A

A frozen codebase limits adjustments and customization, leading to user dissatisfaction.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Why was a completely open codebase rejected by SAP?

A

An open codebase leads to uncontrolled changes, making maintenance and upgrades difficult and costly.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is classic extensibility in SAP?

A

Classic extensibility involves using traditional tools and techniques to customize and extend SAP software, allowing customers to adjust and add functionality to meet their unique business requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

How did classic extensibility work before the cloud era?

A

Before the cloud era, SAP provided exits at various layers (data, visual, and code) that allowed customers to add fields, commands, and custom logic to their SAP systems.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are table appends in the context of classic extensibility?

A

Table appends are used to add new fields to existing database tables, allowing for the storage and retrieval of customer-specific data.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is a screen exit?

A

A screen exit allows developers to add new fields or elements to the user interface, such as adding a “profit” field to a screen that originally only displayed “revenue” and “cost.”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What challenges were associated with classic extensibility?

A

Upgrades and patches could cause customizations to become unstable or redundant, requiring thorough testing to ensure compatibility.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Why did the approach to extensibility need to change with SAP S/4HANA Cloud?

A

In the cloud environment, all customers use the same base code and receive updates simultaneously, making traditional customization methods impractical.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is the clean core philosophy?

A

The clean core philosophy aims to maintain a modern, flexible, cloud-compliant system by keeping customer extensions separate from the standard SAP application. Extensions access SAP business objects only through well defined, upgrade-stable interfaces”.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the core aspects of SAP S/4HANA Cloud under the clean core concept?

A

The core aspects include processes, data, integration, operations, and extensibility, all maintained to be up-to-date, cloud-compliant, and optimized.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What benefits does a clean core provide to customers?

A

Benefits include easier upgrades, fast adoption of new technologies, better system security and stability, lower total cost of ownership, and permanent traceability in the system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What best practices should customers follow for clean core extensibility?

A

Customers should avoid modifying standard SAP objects, eliminate redundant enhancements, use only released APIs, leverage in-app extensibility, employ SAP Business Technology Platform for larger extensions, and use SAP Integration Suite for robust integration.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the deployment options for SAP S/4HANA Cloud?

A

Deployment options include SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition, and on-premise deployment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the migration approaches for transitioning to SAP S/4HANA Cloud?

A

Migration approaches include new implementation, system conversion, and landscape transformation, each impacting the customization and extensibility options available.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

What is the significance of the “zero modifications” policy in clean core extensibility?

A

The “zero modifications” policy ensures that the core SAP system remains unchanged, which helps maintain system stability, ease of upgrade, and compatibility with future updates.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

How does clean core extensibility benefit SAP partners?

A

It offers future-proof, cloud-ready solutions, promotes compliance with fit-to-standard practices, and reduces complexity by simplifying the consumption of out-of-the-box SAP solutions.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What are the three approaches to adopting SAP S/4HANA?

A

The three approaches are Greenfield (new implementation), Brownfield (system conversion), and Landscape Transformation (Selective Data Transition).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What is the system conversion approach?

A

System conversion, also known as the Brownfield approach, involves converting an existing SAP ERP system to SAP S/4HANA, using the current system as a template to maintain existing processes and configurations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What deployment options are available for system conversion?

A

System conversion can be used for SAP S/4HANA Cloud Private Edition or on-premise SAP S/4HANA. It is not available for SAP S/4HANA Cloud Public Edition.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What is the main goal of a system conversion?

A

The main goal is to get the core clean by converting the existing system and then reworking as necessary based on the project scope.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

What does the new implementation approach entail?

A

New implementation, or Greenfield approach, involves setting up a new SAP S/4HANA system without carrying over any legacy custom code or configurations from the old system, effectively starting with a clean slate.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Which deployment options can use the new implementation approach?

A

New implementation can be used for all deployment options: SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition, and on-premise SAP S/4HANA.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

What are the advantages of a new implementation?

A

The advantages include starting with a clean core by default, eliminating the need to revert modifications or adapt extensions, and potentially simplifying the migration project. It also allows for a phased rollout rather than a big bang approach.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

What is the main goal of a new implementation?

A

The main goal is to keep the core clean from the beginning by setting up the system without any legacy custom code or configurations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

What is the landscape transformation approach?

A

Landscape transformation, or Selective Data Transition, involves consolidating configuration and data from multiple ERP systems into a single SAP S/4HANA system, suitable for organizations with multiple disparate ERP systems.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Which deployment options are compatible with landscape transformation?

A

Landscape transformation can be used for SAP S/4HANA Cloud Private Edition or on-premise SAP S/4HANA.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

What scenarios is landscape transformation most suitable for?

A

It is most suitable for customers with a large number of disparate ERP systems, often due to frequent mergers and acquisitions, allowing them to consolidate these systems into a unified SAP S/4HANA environment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

Can SAP S/4HANA Cloud Public Edition use the system conversion or landscape transformation approaches?

A

No, SAP S/4HANA Cloud Public Edition only supports the new implementation approach.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

How do these transition approaches align with the clean core concept?

A

All transition approaches are compatible with the clean core concept. System conversion aims to clean the core post-conversion, new implementation starts with a clean core, and landscape transformation consolidates systems in a way that can maintain a clean core.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

What factors might influence a customer’s choice of transition approach?

A

Factors include the current state of their ERP landscape, their specific business needs, the complexity of existing customizations, and their strategic goals for using SAP S/4HANA.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

What are the two main scenarios for system conversion to SAP S/4HANA on-premise?

A

The two main scenarios are:

SAP ERP running on any database.
SAP ERP running on SAP HANA (v 1.0 or v 2.0).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

What steps are involved in converting an SAP ERP system running on any database?

A

The steps are:

  1. Replace the current non-SAP HANA database with an SAP HANA database (v 2.0).
  2. Convert the database model from SAP ERP to SAP S/4HANA.
  3. Upgrade the code by installing SAP S/4HANA code to replace SAP ERP code.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

What steps are common to both scenarios after upgrading or replacing the database?

A

After upgrading or replacing the database, both scenarios involve:

Conversion of the data model from SAP ERP to SAP S/4HANA.

A code upgrade to replace SAP ERP code with SAP S/4HANA code.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

How many system downtimes are necessary for the conversion process?

A

Only one system downtime is necessary for the entire conversion process, as the database, data, and software are converted in the same technical process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

Why is it necessary to upgrade SAP HANA v 1.0 to v 2.0 during the conversion process?

A

SAP HANA v 2.0 is required for compatibility with SAP S/4HANA, as it supports the advanced features and optimizations needed for the new data model and codebase.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
38
Q

Can you describe the technical process of system conversion for SAP ERP running on any database?

A
  1. Replacing the existing non-HANA database with SAP HANA v 2.0.
  2. Performing a data model conversion to align with SAP S/4HANA requirements.
  3. Executing a code upgrade to install and activate SAP S/4HANA code, replacing the existing SAP ERP code.
39
Q

What are the four recommended clean core workstreams for SAP S/4HANA migration?

A

The four recommended workstreams are:

Evaluate
Adapt
Review
Optimize

40
Q

What is the purpose of the ‘Evaluate’ workstream in the clean core approach?

A

The purpose of the ‘Evaluate’ workstream is to assess custom code using tools like the ABAP call monitor and the Custom Code Migration app to identify what needs to be retained, modified, or discarded.

41
Q

How is custom code adapted during the ‘Adapt’ workstream?

A

Custom code is adapted using the Quick Fix functionality within ABAP development tools for Eclipse, allowing for automatic code adjustments. Manual adaptation is done when automatic fixes are not feasible.

42
Q

What is the goal of the ‘Review’ workstream?

A

The goal of the ‘Review’ workstream is to examine legacy modifications to determine which are obsolete, unused, irrelevant, or can be replaced, ensuring only necessary code is carried forward.

43
Q

What are the key steps in the Custom Code Migration app process?

A

The key steps are:

Collect
Aggregate
Upload
Adjust
Create
Remove

44
Q

Why might some traditional extensions be unnecessary in SAP S/4HANA?

A

Some extensions may be unnecessary because SAP S/4HANA may now cover the original functional purposes of those extensions or the business processes have changed, rendering them obsolete.

45
Q

How does SAP recommend finding and evaluating unnecessary custom code?

A
  1. Collection and aggregation of extension usage data.
  2. Determination of extensions that can be removed via custom code analysis.
  3. Preparation of backup and restoration procedure.
  4. Verification of desired app functionality with the extension removed.
  5. Deletion of the extension during system conversion.
46
Q

What tools are used for collecting extension usage data?

A

The tools used are Usage and Procedure Logging (UPL) and the ABAP Call Monitor (transaction code SCMON).

47
Q

How does the ABAP Call Monitor differ from UPL?

A

The ABAP Call Monitor provides information on the caller of the ABAP code in addition to collecting execution data, whereas UPL only logs the execution of ABAP code.

48
Q

Why is it recommended to run the preferred data collection tool in the production system?

A

It is recommended to ensure that actual usage by end users is recorded, which is crucial for accurate evaluation of the extensions.

49
Q

How long should the data collection tool be run for optimal results?

A

SAP recommends running the tool for 6–18 months, including at least one year-end closing.

50
Q

What transaction code is used to aggregate and manage collected usage data?

A

Transaction code SUSG is used for this purpose.

51
Q

What are the two options for performing custom code analysis?

A

The options are:

Using the SAP Fiori app Custom Code Migration.

Using the ABAP test cockpit available in ABAP development tools for Eclipse.

52
Q

How does the SAP Fiori app help in identifying unused extensions?

A

It identifies unused extensions based on usage statistics collected by UPL and the ABAP Call Monitor.

53
Q

What is the importance of preparing a backup and restoration procedure for custom code?

A

It ensures that deleted code can be restored if needed in the future, addressing concerns about permanently losing potentially useful customizations.

54
Q

What is one cost-effective backup option provided by SAP for custom code?

A

The Git-enabled Change and Transport System (gCTS), which uses an external Git repository to store unused code.

55
Q

What must be done if a restored enhancement is needed in production?

A

The restored code must undergo ABAP checks and testing, using tools like ATC, before being transported to production.

56
Q

What role does the SAP Fiori app Custom Code Migration play during the deletion of extensions in system conversion?

A

It generates a transport request containing all enhancements to be deleted, and the Software Update Manager tool prompts for this request during the conversion process to delete the relevant development objects.

57
Q

Why is custom code adaptation necessary when migrating from SAP ERP to SAP S/4HANA?

A

Custom code adaptation is necessary because there are significant differences between the data model and the code base of SAP ERP and SAP S/4HANA. Extensions that are retained or restored need to be adapted to fit the new system’s architecture and functionality.

58
Q

What are the two forms of custom code adaptation?

A

The two forms are:

Automated Custom Code Adaptation
Manual Custom Code Adaptation

59
Q

Why is it recommended to create a sandbox system for custom code adaptation?

A

It is recommended to create a sandbox system to test the conversion before performing it on the actual production system. This sandbox should mimic the production system to ensure accurate testing and adaptation of custom code.

60
Q

What are the challenges associated with maintaining the SAP ERP system during the migration project?

A

The challenges include potential differences between the production system and the sandbox system used for testing due to ongoing maintenance and support activities in the SAP ERP system.

61
Q

What are the three potential solutions to handle the differences between the production system and the sandbox system?

A

The three potential solutions are:

Development freeze
Double work
Solution Manager retrofit

62
Q

Why is the Solution Manager retrofit the preferred solution?

A

Solution Manager retrofit is preferred because it allows for the synchronization of changes between the SAP ERP system and the sandbox system, avoiding the need for a development freeze or double work.

63
Q

What tools can project teams use for automated custom code adaptation?

A

Project teams can use:

The SAP Fiori app Custom Code Migration (available on SAP S/4HANA or the SAP Business Technology Platform, ABAP environment)

ABAP test cockpit, part of ABAP development tools for Eclipse

64
Q

How does the Quick Fix functionality help in automated custom code adaptation?

A

The Quick Fix functionality, integrated with ABAP test cockpit, automatically fixes and activates ABAP code to conform with SAP S/4HANA changes.

65
Q

What should be done if code cannot be adapted automatically?

A

Code that cannot be adapted automatically must be adapted manually, following a suggested process for analysis and adaptation based on relevant SAP Notes and organizing adaptation teams accordingly.

66
Q

What is the suggested process for manual custom code adaptation?

A

The suggested process includes:

Using the SAP Fiori app SAP Readiness Check Tool to identify relevant SAP Notes.

Differentiating between SAP Notes that specify technical code corrections and those requiring specialized application knowledge.

Organizing adaptation teams based on the nature of code changes.

Specializing developers in certain types of code changes where possible.

67
Q

How should the time required for manual custom code adaptation be communicated to stakeholders?

A

Instead of determining an exact length of time, a time range estimate should be communicated to project migration stakeholders to set realistic expectations.

68
Q

What precaution should be taken when backing up custom code that is being deleted?

A

A backup and restoration procedure should be designed, possibly using the Git-enabled Change and Transport System (gCTS) or other backup systems, ensuring that restored code undergoes ABAP checks and testing before being transported to production.

69
Q

What is a direct modification in the context of SAP systems?

A

A direct modification is a change made directly to an SAP object, either as part of an SAP Note directive or to directly alter the object’s behavior.

70
Q

What constitutes an indirect modification in SAP systems?

A

Indirect modifications encompass:

Copies of SAP objects (“clones”)
Implicit enhancements at “begin” and “end”
Class-method overwrites

71
Q

Which tools can be used to identify code that falls under direct or indirect modifications?

A

The tools used include transaction codes SPDD, SPAU (or SPAU_ENH), and the clone finder tool.

72
Q

What is the foundational principle of clean core in the context of SAP S/4HANA migration?

A

The foundational principle of clean core is a zero modification approach, aiming to eliminate unnecessary modifications to ensure a clean, maintainable system.

73
Q

How should the project team approach legacy modifications, copies, and implicit enhancements?

A

The project team should proceed as if all such code will be eliminated, validating this approach through analysis to determine if modifications are obsolete, unused, irrelevant, or replaceable.

74
Q

What are the common findings when analyzing legacy modifications during migration?

A

Common findings include:

Obsolete modifications: Identical to an SAP version and no longer needed.

Unused modifications: According to usage statistics, these modifications are not used.

Irrelevant modifications: Not necessary, such as rare indexes on SAP S/4HANA.

Replaceable modifications: Capable of being redesigned as key user (in-app) extensions.

75
Q

What should be done if a modification is required to support business functionality and cannot be redesigned under SAP S/4HANA extensibility options?

A

If a modification is necessary and cannot be redesigned, the customer should contact SAP for advice on how to proceed.

76
Q

What is the purpose of using transaction codes SPDD and SPAU during the SAP S/4HANA migration?

A

Transaction codes SPDD and SPAU (or SPAU_ENH) are used to identify and manage modifications and enhancements that need to be addressed during the migration process.

77
Q

How can the clone finder tool be helpful in the migration process?

A

The clone finder tool helps identify copies of SAP objects, allowing the project team to review and decide whether these clones are still necessary or can be eliminated.

78
Q

What should be the next step if the project team determines a modification is obsolete or unused?

A

If a modification is determined to be obsolete or unused, it should be systematically removed from the system to maintain a clean core.

79
Q

How does the SQL Monitor tool help in performance optimization?

A

The SQL Monitor tool helps identify expensive SQL statements and their corresponding ABAP objects. By highlighting inefficient queries, developers can focus on optimizing these specific areas to improve overall system performance.

80
Q

What is the primary decision customers need to make when migrating to SAP S/4HANA?

A

Customers need to decide whether to use a system conversion (Brownfield approach) or a new implementation (Greenfield approach) for their SAP S/4HANA migration project.

81
Q

How does the proportion of customers adopting a system conversion compare to those choosing a new implementation?

A

Surveys indicate that the proportion of customers adopting a system conversion versus a new implementation is 50/50.

82
Q

What are Compatibility Packs in the context of SAP S/4HANA migration?

A

Compatibility packs allow customers to adapt their existing business processes to new SAP S/4HANA processes in a nondisruptive manner. They permit the use of classic ERP functionalities for a period of time, facilitating incremental adoption of new business processes.

83
Q

Why does SAP recommend against a “lift and shift” approach for custom code in a new implementation-based system?

A

SAP strongly recommends against a “lift and shift” approach because customers still need to undergo the same removal and adaptation process, as well as performance optimization. Using this approach can lead to higher project migration costs than what is necessary.

84
Q

Which of the following are different types of scope that exist for software?

A
Overlapping

B
Delivered

C
Required

D
Specific

A

B
Delivered

C
Required

D
Specific

Correct. The different types of scope that exist for software are Delivered, Required, and Specific.

85
Q

Which of the following are the stack layers that classical extensibility refers to?

A
Data

B
Visual

C
Key User

D
Middle

A

A
Data

B
Visual

D
Middle

Correct. The stack layers that classical extensibility refers to are visual, data, and middle.

86
Q

Which of the following are the three possibilities for a customer to implement SAP S/4HANA?

A
System conversion

B
Third-party cloud

C
New implementation

D
System landscape transformation

A

A
System conversion

C
New implementation

D
System landscape transformation

Correct. To implement SAP S/4HANA, the three possibilities are a new implementation, a system conversion, or a system landscape transformation.

87
Q

Which of the following are tools that can be used for custom code usage data?

A
ABAP development tools for Eclipse Quick Fix

B
ABAP call monitor

C
Custom Code Migration app

D
Usage and procedure logging (UPL)

A

B
ABAP call monitor

D
Usage and procedure logging (UPL)

Correct. The following tools can be used for custom code usage data: Usage and procedure logging (UPL) and ABAP call monitor.

88
Q

Which of the following are tools that can be used to adapt custom code manually or automatically?

A
Custom Code Migration app

B
ABAP development tools for Eclipse Quick Fix

C
SAP Notes

D
SAP Readiness Check Tool

A

A
Custom Code Migration app

B
ABAP development tools for Eclipse Quick Fix

Correct. The Custom Code Migration app and ABAP development tools for Eclipse Quick Fix can be used to adapt custom code manually or automatically.

89
Q

Which of the following are reasons why software extensions are needed?

A
Performance optimization

B
Customized business processes

C
Desired customer outcomes

D
Flexibility

A

B
Customized business processes

C
Desired customer outcomes

D
Flexibility

Correct. Software extensions are needed for desired customer outcomes, customized business processes, and flexibility.

90
Q

Which of the following tools can be used to analyze the performance of individual SQL statements?

A
SQL Trace

B
ABAP call monitor

C
ABAP test cockpit as part of ABAP development tools for Eclipse

D
SQL Monitor

A

A
SQL Trace

D
SQL Monitor

Correct. SQL Trace and SQL Monitor can be used to analyze the performance of individual SQL statements.

91
Q

Which of the following are types of indirect modifications?

A
Changes pursuant to an SAP Note

B
Implicit enhancements

C
Clones of SAP objects

D
Class method overwrites

A

B
Implicit enhancements

C
Clones of SAP objects

D
Class method overwrites

Correct. Clones of SAP objects, implicit enhancements, and class method overwrites are types of indirect modifications.

92
Q

Which of the following are recommended clean core workstreams?

A
Custom code adaptation

B
Review of copies

C
Simplification item checks

D
Custom code evaluation

A

A
Custom code adaptation

B
Review of copies

D
Custom code evaluation

Correct. Custom code evaluation, custom code adaptation, and review of copies are recommended clean core workstreams.

93
Q
A

Practicing Clean Core Extensibility For SAP S/4HANA Cloud (4 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions