Application Enhancement tool (AET) SAP CRM 7.
AET – Introduction The AET tool is integrated into the CRM UI Configuration tool Custom fields/Tables can be addded in the UI without any additional development Custom fields/Tables can be added without deep technical knowledge Dropdown list can be added and DDIC check table and search help can be assigned to fields in the tool The custom field can be made available in the search and result, Mobile, BW Reporting, OLTP Reporting and R/3 Adapter Existing fields can be reused across applications The SAP Note 1251796 contains a standard PFCG role that contains all the authorizations required to use AET AET - Overview How to Enable the Configuration Mode in UI Before using AET the UI Configuration Mode needs to be enabled from the “Personalize” link on the the header area of the UI This will enable the “Show Configurable Areas” and “Configure Page” buttons on the workcenter pages
The prefix is optional and is to be used if new enhancements are used in several development systems. because the UI components for table enhancements need a special interface. Namespace and genration Prefix for custom fields and UI component for tableenhancements Enter the package name and prefix to be used for new enhancements.Transaction Code AXTSYS is used to enter the package name. for the current logical system.
. The generation namespace is automatically derived from this information. you need to create the UI component for table enhancements in this Customizing activity. Note : You cannot use UI components that have been created in the BSP component workbench. Therefore.
For example if you want to create a custom field in object SERVICE_ORDER open a service order in UI and click on the Configure Page button. To Add a custom field or table in an application open that application and click on the “Configure Page” button. add a table. This will display the list of Configurable Areas you can confugure. change an existing custom field and delete an existing custom field Also you can reuse an existing field from another enhancement object. When the Expert Mode is chossen the Package and Namespace will be editable.In Order to create a field in a particular application Open that application and click on the “Show Configurable Areas” button.
You can add a custom field.The list of BO can bee seen in the transaction code AXTREG.
The Part of Business Object needs to be chooses where the field will reside. For example if the BO Part CUSTOMER_H is chooses the field would be updated in the data base table CRMD_CUSTOMER_H and BOL Object BTCustomerH
field ID(only in expert mode).Other wise a new data element is created for the field with a autogenerated name. Once finished click “Back” and “Save and Generate” to generate the extension and add the field
. Define the label. R/3 Adapter.length for the field. Mobile. Enable the field for BW.Assign Check table. OLTP reporting Also in expert mode you can specify reference dala element which would be used to create the field. search helps and create drop down values.You can Select a data type.
Note : For adding table a BSP components needs to be created first using the AXTSYS transaction code You can edit field labels. You can add a new custom table using AET. else you can directly edit the field details in the custom field block. external interface flags.Note : Make sure to restart the session after field generation before attempting anything else in AET tool. search options. check tables and search helps. Also you can also mark a field for deletion You can either click on the extension hyper link to go to the details page to edit. Failed/Error (red) or Not Yet Generated (yellow). This table would be created as table with relation to the Order Header or Item table and the correcsponding BOL relation with BTAdminH/BTAdminI would ne created. drop down list box values. translation. Successful (green). The status column shows the current staus of the extension.
Button lets you select any available reusable field in the system. it is copied over to the new application. no new enhancement is created and If a reusable field is based on a different enhancement place.If a reusable field is based on the same enhancement place.
AET – Troubleshooting
.The ‘Add Reusable Field‘.
it will not be transported along with the field.
There are some standard reports on AET troubleshooting like… AXT_EXT_ANALYZE – Shows the field definition.Here you can enable the R/3 Adapter. Type) of an extension.The AET tool makes use of many tables for maintaining the details of fields and system settings like. the generated objects. Data Type. AXT_EXT_CHANGE_PACKAGE – To change the package of an extension AXT_EXT_ACTIVATE_LOCAL – This report is to generate OLTP Reporting structures in the destination systems since OLTP Reporting data related to a custom field is generated always in local packages. AXT_EXT_RESET – Unlocks extensions which ran into errors and can’t be manually edited from the tool. Search Help etc AXT_RUN_BO_PART – Contains mapping of each extension field id with Extension BO and Extsniosn BO Part. AXT_DATATYPE – Contains the allowed data types of AET and the implementaion class of each of them. Increse the number of custom fields that can be appened to standard BO. AXT_BEHAVIOR – Contains the Extensibility Field Behavior types and their implementation class. Length. Note : You can check for the tables with names AXT* . AXT_RUN_FIELDDEF – Contains the details Runtime field definition(e.. Data Element name. They are all related to AET. status and error messages AXT_EXT_GENERATE – troubleshooting in SAP Gui than that report can be used to trigger generation process conveniently from SAP Gui without the need to switch from one UI to another. AXT_EXTENSION_ST – Contains the detailed status of each extension.
. AXT_EXT_PART_DTL – Contains the details of each extension life Field ID.g. This comes and standard delivered. Mobile enhancement for a BO.
Enhancements Registry – Transaction Code AXTREG maintains all enhancement objects..