An introduction to Web Dynpro – Part 2

Accenture is Leader in the World for SAP

 

TAKE NOTE(Insights into the SAP solution and technology)


Accenture is Leader in the Worldwide Implementation of SAP

In the recently published “IDC MarketScape: Worldwide SAP Implementation Ecosystem 2012 Vendor Analysis” report, Accenture has been named a leader in worldwide implementations of SAP solutions.

“Our designation by IDC as a leader in worldwide implementation services for SAP solutions is a powerful testament of our global skills and capabilities in key areas such as cloud, mobility and database technologies, combined with our broad industry knowledge,” said the global managing director of SAP business for Accenture. “We are particularly focused on developing innovative analytics solutions based on the SAP HANA platform as more and more clients look to take advantage of the speed and performance offered by in-memory computing.”

“We are committed to maintaining our industry-leading position in support of SAP solutions globally and continuing to build on new platforms like SAP HANA.”

The IDC MarketScape report studied 12 of the largest systems integrators for SAP applications. Each of these companies currently sport extensive global services portfolios. Evaluation of these vendors followed a robust and detailed framework which takes into account the ability of the vendor to address specific criteria.

The IDC research framework gave prominence to those factors with the maximum potential to propel the vendor forward within the market.

“Accenture is one of the leading implementers and innovators of SAP globally, with a strong practice in large-scale business transformation, business process improvement, value delivery and application outsourcing,” according to the IDC Marketscape. “With more than 36,500 SAP practitioners worldwide, Accenture delivers and supports a full range of industry-specific business services for large-scale implementations that span multiple solutions including Core ERP, lines of business (SCM, HCM, etc.), and emerging technology areas such as analytics, HANA, mobility and cloud.”

“Accenture’s global delivery network, proprietary assets and solutions, and Innovation Centers for SAP deliver solid expertise and high performance to the firm’s clients,” the source added.

Accenture is one of the premier management consulting, technology services and outsourcing companies and currently serves clients in more than 120 countries

 

UNDER DEVELOPMENT(Information for ABAP Developers)

An introduction to Web Dynpro – Part 2

The Web Dynpro development environment

You can build Web Dynpro applications using one of two development tools: SAP NetWeaver Developer Studio (NWDS) for Java, or the ABAP Development Workbench, familiar to all ABAP developers…..

READ MORE

 


 

Q&A(Your Questions answered)

Q. What is the difference between Static classes and instansiated? Is one better than the other?

A. This seems to be the 64K dollar question these days. Even at work where I am, there are developers asking this all the time.

Let’s start with understanding the difference between the two components.

– Instance components, that is, instance attributes, instance events, and instance methods, can be addressed only via instances of the class (objects).

– Static components, that is, static attributes, static events, and static methods. The static components of a class can be addressed not only using an object but also using the name of the class, so it can be used independent of an instance of the class.

So here is the general answer for the first part of your question in summary … A class that only contains static components and no instance components is referred to as a Static class. When used, a global static class is loaded with its class pool like any ABAP program into the current internal session once and cannot be deleted from it explicitly. The static methods (which are declared via CLASS· METHODS) of a class cannot be redefined in subclasses.

What does this really mean? Is there a rule?

Well if we look at the “Official” ABAP Programming Guidelines published by SAP, the rule is  “Preferably use objects instead of static classes. If you don’t want to have a multiple
instantiation, you can use singletons.”
A Singleton is another Object design Pattern that forces only one instance of an object. For a better understanding of this design pattern, I would suggest you read Design Patterns: In Object-Oriented ABAP.

What it means can be detailed out as follows….

If no real object-oriented design exists, meaning multiple instantiation is not wanted explicitly. You should still prefer object creation to the use of static classes for the reasons outlined below:

(1) Static classes, are implicitly loaded the first time they are used, and the static constructor, if available, is executed. They remain in the memory as long as the current internal session exists. Therefore. if you use static classes, you cannot actually control the time of initialization and have no option to release the memory occupied by the attributes again as soon as the class function is no longer required.

(2) Another important argument that speaks against the use of static classes is the limited functionality of the static constructor in comparison to an instance constructor. A static constructor has no parameter interface and cannot propagate any exceptions, which is why you cannot always respond appropriately to an error situation in the static constructor, and this results in a runtime error in extreme cases. However, the exceptions of an instance constructor can be handled.

(3) By using static classes, you spoil your polymorphism options. Which are actually provided by object-oriented programming. On the one hand, you cannot redefine static methods; on the other hand. There is no access via reference variables, the other “pillar· of polymorphism. Even if you initially don’t plan to overwrite the behavior of a method later on using inheritance or redefinition, this request frequently arises in the course of the further development

There can be exceptions. Classes that only cover trivial functionality can still be implemented as static classes. Here, you must precisely assess whether one of the aspects mentioned
above has any effect
. The necessity for a class constructor can be an indicator. As soon as a static class requires a nontrivial class constructor to provide the desired functionality, I tend to use instantiated objects instead.

If you have a technical question you’d like answered, post the question to our facebook pagewww.facebook.com/itpsapinc

Pin It on Pinterest

Share This

If you enjoyed this post, why not share it with your friends!