Enhancements

[Former Member]

Hai all

I am fresher preparing for the interviews, can somebody help me to through some light on enhancements in implementation and support with some examples.''kindly help me its very urgent"

[Former Member · Accepted solution]

Hi Alekhya

Creating, Editing, and Deleting Enhancement Implementations

Purpose

Enhancement implementations are created and changed by means of forward navigation.

· For explicit enhancement options, enhancement implementations are created for the related enhancement spots.

· For implicit enhancement options, enhancement implementations are created directly.

The appropriate tool for the respective enhancement technology is opened automatically.

Procedure

...

1. Start the Object Navigator (SE80).

2. Display the package in which an enhancement implementation is defined, or is to be created.

If you want to

Then

Create an enhancement implementation

The method is different for explicit and implicit enhancement options. For an explicit enhancement option, select the enhancement spot in the Object Navigator, and choose Implement in the context menu. For an implicit enhancement option, call the Enhancement Builder in the relevant tool (ABAP Editor, Function Builder, Class Builder) for executing an enhancement.

Then, in the dialog box that appears, continue with the following steps:

...

1. Enter a name for the (simple) enhancement implementation.

2. Enter a short text for the (simple) enhancement implementation.

3. Select a composite enhancement implementation, or create a new one.

4. Choose Creation of Enhancement (Enter).

The subsequent process depends on the enhancement technology of the enhancement spot.

Edit an enhancement implementation

...

1. Select the package and expand it.

2. Expand the Enhancements node.

3. Expand the Enhancement Implementations node.

4. Select the desired enhancement implementation.

5. Select Change from the context menu.

If you only want to display the enhancement implementation, choose Display.

Delete an enhancement implementation

...

1. Select the package and expand it.

2. Expand the Enhancements node.

3. Expand the Enhancement Implementations node.

4. Select the desired enhancement implementation.

5. Select Delete from the context menu.

Enhancement Spots:

Definition

The enhancement spots are used to manage explicit enhancement options. Enhancement spots carry information about the positions at which enhancement options were created. One enhancement spot can manage several enhancement options of a Repository object. Conversely, several enhancement spots can be assigned to one enhancement option.

Use

You create an explicit enhancement option when processing a Repository object with the relevant tool by creating an enhancement spot element definition at a point where this is possible. This enhancement option can then be called at different points using enhancement spot element calls. The enhancement spot element definition and the corresponding enhancement spot element calls make up the definition of an enhancement option. For example, when editing an ABAP program with the ABAP Editor, you can define explicit enhancement options in the form of the ENHANCEMENT-POINT statement, which also represents the element definition and element call.

Each enhancement spot element definition must be assigned to at least one enhancement spot. For this, an enhancement spot element definition is assigned one or more simple enhancement spots, which in turn are assigned to at least one composite enhancement spot. Simple and composite enhancement spots are Repository objects that form a tree-like structure, where the leaves and branches represent simple and composite enhancement spots respectively. A simple enhancement spot is always assigned to exactly one enhancement technology (ABAP source code enhancement or BAdI).

Composite enhancement spots are used for the semantic grouping of simple enhancement spots. A composite enhancement spot contains either one or more simple enhancement spots and/or one or more composite enhancement spots of the relevant type. You can use composite enhancement spots to combine simple enhancement spots into meaningful units:

Enhancement spots are processed with the Enhancement Builder tool, which is integrated in the ABAP Workbench. The Enhancement Builder’s hierarchical display of the enhancement spots in a system indicates enhancement possibilities (that is, enhancement options) to developers.

Enhancement Options

Definition

Enhancement options are positions in Repository objects where enhancements can be made. These options are either explicitly defined (by the developer) or exist implicitly. Explicit enhancement options are generally defined in a central initial system. Enhancements are made in follow-on systems.

Use

Explicit enhancement options can currently be defined by:

● Explicitly flagging source code points or sections in ABAP programs. For an enhancement, these can be enhanced or replaced by source code plug-ins.

● Including Business Add-Ins (BAdIs) in ABAP programs. These programs are then enhanced by object plug-ins with predefined interfaces.

Explicit enhancement options are managed by enhancement spots and enhanced by enhancement implementations.

Currently, implicit enhancement options are:

● Specific options in ABAP programs – such as the end of the program – which can be enhanced by source code plug-ins.

● Parameter interfaces of function modules, which can be enhanced with parameters.

● Attributes and parameter interfaces of global classes, which can be enhanced with attributes or parameters.

Implicit enhancement options always exist and do not require enhancement spots. They are also enhanced by enhancement implementations.

Explicit Enhancement Options in ABAP Source Codes

Use

In ABAP programs, you can select either a position or a program section as an explicit enhancement option. Source code plug-ins for an enhancement are either entered at such a position or they replace the selected section.

An explicit enhancement option of an ABAP program is part of the program. It is thus assigned to the package of the program and not necessarily to the package of the enhancement spot to which it belongs.

Activities

· To mark a position in an ABAP program as an explicit enhancement option, use the following ABAP statement:

ENHANCEMENT-POINT enh_id SPOTS spot1 spot2 ...

· To mark a section in an ABAP program as an explicit enhancement option, use the following ABAP statement:

ENHANCEMENT-SECTION enh_id SPOTS spot1 spot2 ...

...

END-ENHANCEMENT-SECTION.

Using enh_id, you define the name of the enhancement option or the source code enhancement. After SPOTS, the enhancement option must be assigned to at least one (simple) enhancement spot. For a detailed description of the statements, refer to the ABAP keyword documentation.

An enhancement spot for source code enhancements is created using forward navigation from within the ABAP Editor. The statements can either be entered directly or generated by selecting Enhancements ® Create Enhancement.

After the program has been saved, the enhancement option is managed by the Enhancement Builder, and can only be deleted using the function Enhancements ® Remove Enhancement.

During program generation, the source code plug-ins that are in the current system for the assigned enhancement implementations and have the switch status stand-by or on, are included at this position or they replace the selected section.

Business Add-Ins (BAdIs)

Definition

SAP Business Add-Ins (BAdIs) are one of the most important technologies used to adapt SAP software to specific requirements. BAdIs were introduced with Release 4.6 and replace function module exits. This technology is not limited to SAP applications. BAdI calls can be integrated in customer applications. These can then be enhanced by other customer applications. In the various SAP applications, BAdI calls are implemented at places where enhancements are appropriate. In the SAP ERP system, there were already approximately 5,000 BAdIs before Release 7.0.

Use

As of Release 7.0 of the SAP NetWeaver Application Server ABAP (SAP NetWeaver 7.0), BAdIs are part of the Enhancement Framework, where they represent explicit enhancement options.

We call these BAdIs classic BAdIs. In addition to their integration in the Enhancement Framework, BAdIs from Release 7.0 onwards differ from classic BAdIs particularly with regard to the fact that they are supported directly by the ABAP runtime environment through ABAP statements.

For more information about BAdIs, see:

BAdIs Concept

Definition of BAdIs

Calling BAdIs

Implementing BAdIs

BAdIs - Documentation

BAdIs - Migration of Classic BAdIs

BAdIs - More Information

Enhancement Implementations

Definition

The enhancement implementations manage the enhancements of the enhancement options, both explicitly and implicitly.

In the same way that we differentiate between enhancement options and their management in the case of enhancement spots, we also differentiate between the actual enhancement and its management in the case of enhancement implementations.

Use

An enhancement is managed by assigning one or more simple enhancement implementations to an enhancement spot of a concrete enhancement spot element definition. Conversely, every simple enhancement implementation belongs to exactly one enhancement spot. A simple enhancement implementation can have one or more enhancement implementation elements, which are assigned to the enhancement spot element definitions of the enhancement spot. A simple enhancement implementation must be assigned to at least one composite enhancement implementation:

Simple and composite enhancement implementations are Repository objects that form a tree-like structure, where the leaves and branches represent simple and composite enhancement implementations respectively.

Therefore, to implement the actual enhancement, one or more enhancement implementation elements are assigned to an enhancement spot element definition of an explicit or implicit enhancement option.

You can assign source code plug-ins, defined between ENHANCEMENT and ENDENHANCEMENT in an ABAP program, to an enhancement option defined using ENHANCEMENT-POINT. These source code plug-ins are inserted into the code unchanged if the switch is in the relevant position.

Enhancement implementations are processed with the Enhancement Builder tool, which is integrated in the ABAP Workbench. The Enhancement Builder’s hierarchical display of the enhancement implementations in a system shows the enhancements made in a system.

An enhancement implementation describes the enhancement of a Repository object at one or more enhancement options. An enhancement implementation element always belongs to exactly one enhancement option. However, several enhancement implementation elements can be assigned to an enhancement option. The enhancement implementation element contains the actual enhancement – for example, a source code plug-in contains the source code to be added. However, an enhancement implementation element contains no information concerning at which positions of a Repository object the enhancement options were created. Composite enhancement implementations are used for the semantic grouping of simple enhancement implementations. A composite enhancement implementation contains either one or more simple enhancement implementations and/or one or more composite enhancement implementations of the relevant type. You can use composite enhancement implementations to combine simple enhancement implementations into meaningful units.

The position of a Switch Framework switch assigned to the package of an enhancement implementation specifies whether or not an enhancement is taken into account in a system.

The link will help u more

http://help.sap.com/saphelp_nw2004s/helpdata/en/83/43e040e136742ae10000000a155106/content.htm

SUPPORT

Why SAP Support is Important

It boggles the mind how companies can spend hundreds of thousands, and even millions of dollars implementing SAP, and yet, once they are live, they cut budgetary funds for supporting their post go live environment. Months, and even years after the go-live, companies are struggling from a support perspective because CIO's didn't push for a support budget or properly plan for life after live. Typically, the effects are disastrous, and are felt from both an organizational and user perspective. These include:

? No Competency Center or support strategy formed
? Running the system with antiquated or sub-standard processes
? Diminished buy in from the user community of the solution
? User frustration, bitterness and feelings of abandonment
? Delay in business benefit realization

SAP Support is important because it is the missing link for long term SAP success. And, when the Support Team is strategically focused and aligned with business objectives, chances for long term success drastically improve. Overall, SAP support is the foundation for driving functionality enhancements and SAP knowledge to the user community. No matter what your current situation is, it is never too late to take the necessary steps to optimize SAP and surrounding business processes, boost user satisfaction, and improve overall business results.

Why Blog About SAP Support

From a personal perspective, I have been actively engaged in delivering and selling SAP support for the past 4 years. Over this time, I have come to realize that some common misconceptions, as well as general apathy, exist in the market regarding the topic of SAP support. In addition, while many companies have a vision to provide best-in-class support service to their organizations and capture the ROI envisioned at the project's outset, few have had success turning the vision into reality.

The purpose of this blog is twofold: To de-bunk the common myths and axioms that exist today about SAP support - from both an executive and user perspective, and to help educate folks on the power and impact that a functional and harmonized SAP support Team can have on driving business value to the entire organization. At a minimum, I hope this blog will help the SAP community better understand the fundamental principles required for support success.

SAP Tickets - What Is That?
Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error.

The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the right solution in right time.This is the job of the support consultant.

The issues or the tickets(problems) which are arised is taken care of on priority basis by the support team consultants.

The work process in support projects are given below for your reference.

1. The customer or the end user logs a call through any tool or by mail (RADIX).

2. Each one of the support team is a part of support group.

3. Whenever a customer logs a call he /she has to mention to which work group (by name).

4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None)

5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR(Transport Request through the basis admin)

6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process.

These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client.

An example:

:

Tickets in SD can be considered as the problems which the end user or the employee in the company face while working on R/3. Tickets usually occur during the implementation or after theimplementation of the project. There can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.

To begin with , we should give "TICKET" to you for not knowing it.

Here is an eg of a ticket raise:

End user is not able to

1. Create Sales order for a customer from a New plant , since shipping point determination is not happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING).

He raises a ticket and the priority is set in one of the below:

1. Low 2. Medium 3. High.

Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.

You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.

Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support.

Reward if useful to u

Message was edited by:

narendran vajravelu

null

[Lakshmipathi]

Hi Alekhya

Check the links

http://help.sap.com/saphelp_47x200/helpdata/en/9b/c2b9375e62545ce10000009b38f889/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/9b/c2b9375e62545ce10000009b38f889/frameset.htm

Thanks

G. Lakshmipathi