AET vs.

EEW - How to Guide - Wiki@SAP

Page 1 of 3

Functionality Comparison
AET Overall Scope Only field extensions are possible in CRM 7.0. Almost all CRM applications are covered, some ERP applications are enabled as well(BSi2011). Table Extensibility is of WEBCUIF 7.0 EhP1 Calculated fields can be created (EhP1/EhP2) Features Extensions can be used in CRM WebUI. Extensions are available on DB and within application logic. CRM Interactive Reports can be enhanced. FPM integration is available (EhP2) The following external interfaces can be enhanced: - R/3: extension of R/3 adapter, - Mobile: extension of Mobile Sync BDoc and CDB tables - BW: extension of BW DataSource - XIF adapter (extended by default) Data flow scenarios Data flow reuse scenarios can be defined by the application and implemented by customers. E.g. copy extension fields of sales order to billing document & transfer data. However there's currently only one scenario defined and important scenarios are missing. Contact application development if needed. No cross system functionality yet. If needed please contact product owner. Integrated with CRM WebUI Configuration tool. The field creation and the corresponding UI configuration are done in the same place. Easy to use and intuitive for Power Users (Administrators). Could also be used by business users (no deep technical knowledge is Extensions can be used in WebUI, PC UI and SAP GUI. Extensions are available on DB and within application logic. The following external interfaces can be enhanced: - R/3: extension of R/3 adapter + Generation in ERP - Mobile: extension of Mobile Sync BDoc and CDB tables - BW: extension of BW DataSource - XIF adapter (extended by default) EEW Both field and table extensions are possible. Only few applications are covered in CRM and ERP or SRM.

Some application specific data flow scenarios are supported. E.g. create oneOrder table extension out of product settype and enable dataflow. Not all of them are implmeneted for AET

Cross System Generation Tools

Remote extension of order base table in ERP when extending CRM Sales Order. Some manual steps are still required. SAP GUI based. There is no integration with UI Configuration Tool (has to be started separately). EEW is for users with deep technical knowledge.

Target audience

file://C:\Users\d041307\Desktop\viewpage.action.htm

27.07.2011

AET vs. EEW - How to Guide - Wiki@SAP

Page 2 of 3

required). Homogeneity Value Helps Consistent behavior across all applications (for example the same data types are supported in all applications). Custom Drop Down List Boxes can be defined for each field (as part of the field definition. Easy assignment of existing check tables and search helps for each field. Easy translation of labels and DDLB values in the tool (part of the field definition). Use custom fields as search criteria and search result by simply selecting an option in the field definition. Usage of standard transport system for generated objects. Allows creation of extensions for a given application in different namespaces and packages (except BP) Extension include approach allows multi-layer extensibility. Although some application specific tables still not allow it. TA AXTSYS allows definition of standard package for all applications. AET allows up to 3 development systems in a system landscape, reaching the same production system, via specificaion of a generation prefix in AXTSYS EEW or manually created fields are accessible in read only mode. A basic migration of some EEW field extensions to AET field enhancements is possible (EhP1). Inconsistent behavior and capabilities across different applications (for example different data types are supported in different applications). It is only possible to assign new and existing check tables and search helps to fields in some applications Manual Design Layer adjustment are necessary. Translation has to be done separately in SE63. Some applications allow search automatically but do not provide control over that. Usage of standard transport system for generated objects. Most applications are based on customer includes that do not support usage of different namespaces. In the case of table extensions there is a limit on the namespaces / multi-layer extensions. Supports the notion of projects. TA EEWC is used to define roles and RFC connections to other systems. The Package and Namespace are assigned in Projects. EEW allows only one development system within a single system landscape. Works with EEW extensions only.

Translation Search Software Logistic

System Setup

Tool Compatibility

Technical Comparison
AET Overall Scope Universal but flexible approach for field extensibility. Table extensibility will be added in EhP1. More extensibility categories can be added. Flexible Generation Framework exists. It is optimized with respect to performance (parallel generation). EEW The scope is application specific. A configurable wizard for field extensions exists. Flexible Generation Framework exists with performance gaps. Cross system generation possible.

Generation

file://C:\Users\d041307\Desktop\viewpage.action.htm

27.07.2011

AET vs. EEW - How to Guide - Wiki@SAP

Page 3 of 3

Restricted to the current system. Field extension technique Tools Mainly extension includes with some exceptions The tool is CRM WebUI based. It is possible to run AET either standalone or embedded in the UI Configuration. Extensibility of applications with other UI technologies is possible, but with UI configuration navigation. Software Layer Models WEBCUIF Comprehensive flexible Model describing all extensible Business Objects, their relations to UIs, BOL objects and generation steps. Non WEBCUIF/BOL apps can be registered as well. Low, mainly model registration and development rules. Provides extension metadata to applications. Complete runtime (Buffer, API, GenIL) for table extensions (as of EhP1). Has WEBCUIF plugins for rendering tasks. Restricted to Workbench requests. Extensions are defined cross-client. Transport of metadata fully supported. ABA Only simple model to facilitate application wizard selection. Mainly customer includes SAP GUI based.

App. Dev. Effort Application Runtime

High - if the configurable field wizard does not fit, Tool UI plugin and generation control need to be done by application development. No runtime components. All generated objects are part of application runtime.

Software Logistics

Both Workbench and Customizing transports possible. Extension definition is client specific (generation is not). No transport of Metadata (only with workaround).

Recommendations
It is clearly recommended to use the AET for new enhancements, if it is supported in the installed release. The EEWB is still supported in order to allow maintenance of existing extensions and for special cases which are not supported by the AET. A migration of EEWB field extensions is supported from eHP1 (but is not always possible).

file://C:\Users\d041307\Desktop\viewpage.action.htm

27.07.2011