OpenUI5

No words to express my happiness. SAP AG, the world leader in enterprise software and software-related services with locations in more than 130 countries has release its first open source software – openUI5(HTML5- future of SAP frontend).

You can see demo kit of OpenUI5 here

Intro

So now this JavaScript library named “OpenUI5” (the Open-Source-licensed version of SAPUI5) has left its SAP niche and stepped into public.

A bit of History

Even though UI5 is only now stepping out into the Open Source space, it has in fact been developed and matured for years (initially under the codename “Phoenix”, hence the bird-like logo). So don’t expect a beta.

SAP has been using UI5 in a couple of products already, most notably the family of “Fiori” applications revealed earlier this year (see https://experience.sap.com/fiori for information and screenshots). Decoupling UI development (where customers expect frequent iterations to follow web UI trends and to get support for the newest devices) from backend updates (where typical SAP customers expect to run the same version for many years without expensive and disruptive upgrades) has been a major driving force behind the development and adoption of UI5. As well as the desire for a UI technology which is more standards-based, flexible and extensible than before and at the same time still fulfills all the stability, accessibility and security standards required from business software.

How and why is “OpenUI5” different from “SAPUI5”?

“OpenUI5” is the free version available under the Apache 2.0 Open Source license.

“SAPUI5” is the version that may only be used by SAP customers with a certain kind of license. (It’s still free for them, but they have paid some other SAP product.)

The good news is: most importantly, the entire core of “OpenUI5” and “SAPUI5” (containing all central functionality) is identical. The most-commonly used control libraries, containing the vast majority of all existing controls, are identical. All of this can now be used freely, when using OpenUI5.

What SCN would suggest is:

  • go to the OpenUI5 web page and explore it from there.
  • if you are into code, study the small mobile app (not in IE9 and lower due to cross-domain issues) and try to understand how it works. Should not be too hard, actually, it’s just 1-2 screens of code but already giving you master-detail page animations, data binding etc.
  • if you rather want to try it right away, check out the demo apps
  • if you prefer understanding the concepts first, start with the Developer Guide which describes loads of things from the first steps to really advanced topics

Willing to start working with openui5?? then clickhere

Start learning here or here

How to install a basic development environment for SAP UI5? browse here or here

Source: http://scn.sap.com/community/developer-center/front-end/blog/2013/12/11/what-is-openui5-sapui5

 

Advertisements

Difference between se01,se09 and se10 in sap

Confused with transport transactions in sap?? 😦

Here comes with some explanation..

In earlier SAP releases, SE09 and SE10 used to cover different areas:

  • SE09 was used for workbench/development transports
  • SE10 was used for customizing transports

Nowadays, both transactions are the same (they use the same report internally).

Additionally, SE01 is an extended transaction that combines SE09 and SE10 features, but adds a lot of additional ones such as displaying specific transport requests without knowing the assigned user names or searching based on clients.

Workbench request is for transporting objects like Programs, Function moduels etc basically Repository objects.

Where as customization requests are for transporting Customization data entered into customizatio tables from one system to another.

Workbench requests record changes made to ABAP Workbench objects.

There are local and transportable Workbench requests. (Local Workbench requests have the target system <space>.)

The package of the object and the transport route settings in the Transport Management System determine whether changes are recorded in a local or a transportable Workbench request.

Changes to Customizing settings are recorded in Customizing requests.

In simple words,

Workbench requests are used by ABAPers while creating or changing the Repository objects.

Customizing requests are used by Functional Consultants while creating or changing the Customizing settings. Like Creating Enterprise Structure Etc.

Precisely..

##################################################

Customizing request

Customizing requests contain changes to client-dependent tables.

Workbench request

Workbench requests contain changes to client-independent tables.

##################################################