Sunteți pe pagina 1din 14

Documentation Header

Document

CRM.DOC.011L Creating AET in SAP CRM 7.0

Description

Step by Step for creating AET in SAP CRM

Responsible

Abhijit Nath

Reviewer

Last Change Description


Version

Modified in

Responsible

Modification

1.00

09.Jul.2014

Abhijit Nath

Component Creation

Version

1.00

Kaushik Mazumder

Table of Contents
1. Document Objective......................................................................................................................... 3
2. Document Detail............................................................................................................................... 4
3. Version Change Log....................................................................................................................... 14

1.

Document Objective

This document is basically created for CRM Functional Resources which requires not much technical knowledge
to create fields using AET as compared to EEWB.
AET is also considered less risky as compared to EEWB as deletion of the extension fields is very easy to use by
Functional consultants with less complexity & easy to create one.

2.

Document Detail

Step by step approach for creating New field using AET in SAP CRM.
Step 1:
The First Step requires some basic settings and some authorization requirement to enable AET work in the CRM
system.
Decide on the Package name and Generation prefix (optional) for extension of the enhancement.
Set it in the system using the transaction AXTSYS. The Namespace is automatically derived from the above
information. This is a onetime activity.
Alternative path for the defining the system settings in the SPRO transaction
SPRO->SAP Reference IMG->Customer Relationship Management->UI Framework->UI Framework Definition>Application Enhancement Tool->Define System Settings.

Step 2:
For Accessing the AET in Web UI, it needs to be firstly enable in the Configuration Mode in the below SPRO
setting
Personalize->Settings->Personalize Settings path from web user interface.
Check mark the Enable Configuration Mode check box option under Configuration mode and save it.

Note: - The user should have authorization to SAP object CONFMOD to avail this in personal settings.

Once the configuration mode is enabled, the Show Configurable Areas icon would be displayed for the user on
his WEB UI screens.

Now we can use AET from any screen by clicking the above icon for show configurable Areas, as the area turns
blue color and can be editable to create AET fields as seen below.

Step 3:
This step will help in creation of a new field as per the requirement from business requirement.
For example in the below example the Service Order screen is being modified as per the requirement.
Procudural Steps to be performed in Web UI:
1. Go to the desired transaction view in WEB UI.

2. Click on the Show Configurable Areas icon of the transaction which enables all AET supported configurable
views in the current WEB UI screen within dotted frames.
3. Click on the corresponding dotted frame for the view to add the new custom field.

4. The AET tool opens up the View configuration (which has the integrated UI configuration tool) pop up window
displaying all the configurations available for the selected view (both standard and custom).

5. Now click on the Create Field button to create new custom field first and then add it to all the configurations
required.

6. The AET tool would now display a pop-up with all supported Business Objects for the current selected view.
Select the desired business object from the list as per the business requirement.
7. Once the Business Object has been selected, the AET would now give the pop-up for supported Sub-objects
(Part of BO) of the selected business object, like ORDERADM_H Header had been selected as per our example.
And package as per the requirement and then press OK .

8. After the field details page is popped up enter the details for the Field Label: Name of the Field that needed to
be put and Field Type: as per the requirement.

9. Enter the deails in the drop down list (Example :Option 1, Option 2 and Option3 in below case )for the option to
be visible under the Field created (Example: Test Field for below case )
The tool also provides options to provide DropDown Listbox for the new field created as well as the Translation for
all the text entered for the field

Now select the enhancement (ZEXT000003) that had been created in earlier step from the list & press Save and
generate button.

10. Prompt for the TR is displayed. Enter the TR and proceed

11. Now the status is in green when this enhancement is active & ready to be used

12. The enhancement with the extension field would be created.

13. Once the enhancement has been saved and generated, it gets added to the available fields list. You can
create a new custom configuration if required, or else if the configuration already exists for your scenario you can
select it from the displayed list in the web ui config tool (from GUI or AET). Then the newly created field would be
displayed in the Available Fields list, from where you can add it to the Displayed field to be displayed in the
WEB UI view .This process of adding the new field to the ui configuration can be done either from the WEB UI
AET tool or from the GUI BSP component UI config tool.
Once we have the field enhancement created, create the custom configuration either from GUI or UI AET tool
(initial screen) and add the newly created field from the Available Fields list to the Displayed Fields list
,changing the Field Label if required.
14. Now this is available in the Service Order for the Field that we had created with the dropdown Option 1
Selected as per the inputs given.

15. Save the configuration and port the custom TR using transaction scc1 to the desired testing client to test.
The AET field created would be added to the BOL structure and other related structures and tables automatically.
If you had opted for Mobile, the related CDB tables are also populated with the field.

Version Change Log


Version

Modified in

Responsible

Modification

1.00

28.Feb.2008

Name

Component Creation