Adding New Fields to the Business Partner 
You can add new fields to the central table BUT000 of the business partner using the Easy Enhancement Workbench (EEW).
SAP CRM supports you in the following functions:
Creating new fields that you can then integrate into the CRM WebClient user interface by using the configuration tools The new fields can be used in the application objects Contact Person, Employee, and Account.
Availability of new fields in CRM Mobile
Enhancement of the data exchange in the context of CRM Middleware. To display the new fields in the dialog, downstream operations still have to be carried out on the mobile clients.
Availability of new fields in SAP ECC
Enhancements to the data exchange with SAP ECC in the context of CRM Middleware. For seamless integration, downstream operations still have to be carried out in SAP ECC.
Admission and update of new fields in DataSources for SAP NetWeaver Business Intelligence (SAP BI)
For seamless integration, downstream operations still have to be carried out in SAP BI.
As far as a check table exists, value help is also available for the generated fields.
For these functions, the system automatically generates all objects and table entries required.
Process
To add new fields to the business partner, use the business object Business Partner (BUPA) and create an enhancement of the type "Add New Fields". A wizard helps you define the individual enhancements and provides you with the necessary information for each step.
For each field, you must define the field name, data type and, if necessary, the field length.
For each field, define whether a check table should be available.
For each field, you must also determine whether it should be transferred to SAP BI or to CRM Field Applications.
In the last wizard screen, the system shows you an overview of the fields you defined, together with their associated attributes.
To start generation, choose Complete.
Technical Implementation
For enhancements to the business partner, the EEW uses the Customizing include structures CI_EEW_BUT000 and CI_EEW_BUT000_X (update toolbar).
In the object overview, which is made available for each task in the EEW, you can find a detailed overview of all the objects created. There you can also find the technical names of the created objects, which you might require for postprocessing.
Integration with the Business Partner
Among others, the EEW creates the following repository objects and table entries for integration with the CRM business partner:
A data element and a domain for each field
The required APIs, including interface structures, for each enhancement
If necessary, check tables and associated maintenance views for selected fields, through which the check tables must be filled with values in postprocessing
The check tables are now generated for CRM Enterprise only, and not for the CRM Field Applications.
One function group for each enhancement
Function modules for data processing (API for reading, creating, changing, and deleting data)
Integration with CRM Field Applications
If the indicator Mobile is set for a field, then the following objects are enhanced by this field:
Table SMOKNA1 in the CDB
Table SMOMITABT in the CDB
The associated sBDoc CAPGEN_OBJECT_WRITE
The associated sBDoc CONGEN_OBJECT_WRITE
The associated sBDoc EMPLOYEE_WRITE
The mapping (Mobile Bridge)
If the indicator Mobile Brief Info is set for a field, then the following objects are enhanced by this field:
Table SMOKNA1SHT in the CDB
The associated sBDoc CUST_HIERARCHY
The mapping (Mobile Bridge)
Integration with SAP ECC
For integration with SAP ECC, the following adjustments were made for the data exchange between SAP CRM and SAP ECC:
Adjustments in SAP CRM:
The fields included in the Customizing-include structure CI_EEW_BUT000 are received and processed by CRM inbound processing.
The fields included in the Customizing-include structure CI_EEW-BUT000 are filled by CRM outbound processing and, if changed, the change indicator is set for each field in the Customizing include structure CI_EEW_BUT000_X.
The conversion of the complex structure in SAP CRM to the BAPIMTCS in the R/3-Adapter of CRM Middleware has been enhanced in both directions by the Customizing include structures.
Adjustments in SAP ECC for the customer master:
In SAP R/3 3.1, the type pool was enhanced by the include CI_CUST (including field DUMMY1) and CI_CUST_X.
During data exchange between SAP CRM and SAP ECC, it is a prerequisite that the Customizing-include structure CI_EEW_BUT000 and the Customizing-include structure CI_CUST have the same setup and may only differ in the number of fields. The data types and sequence of fields must match.
In SAP ECC, the conversion of the BAPIMTCS to the complex structure of SAP ECC was enhanced accordingly in both directions for the customer master.
In the event of the Customizing-include fields occurring in the IDOC segment E1KNA1M, this IDOC segment is filled automatically in R/3 customer master inbound processing, taking the update toolbar into account, and the data is then posted in the batch input.
The customer master outbound processing fills the Customizing-include structure CI_CUST and the update toolbar in the event of there being identically-named fields in table KNA1.
If the business partner in SAP CRM is enhanced using the EEW by a field that already exists in the SAP ECC table KNA1 and in the IDOC segment E1KNA1M assigned to it, only the two Customizing-include structures CI_CUST and CI_CUST_X must be created in SAP ECC analogously to the SAP CRM Customizing-include structures CI_EEW_BUT000 and CI_EEW_BUT000_X in order to enable data exchange with the SAP ECC customer master.
Adjustments in SAP ECC for the SAP business partner:
In SAP R/3 4.6C, the copy of the complex structure of SAP CRM was enhanced by the include CI_EEW_BUT000.
During data exchange between SAP CRM and SAP ECC, it is a prerequisite that the Customizing-include structures CI_EEW_BUT000 in SAP CRM and in SAP ECC have the same setup and may only differ in the number of fields. The data types and sequence of fields must match.
In SAP ECC, the conversion of the BAPIMTCS to the complex structure of SAP ECC was enhanced accordingly in both directions for the SAP business partner.
Integration with SAP BI
The new fields in table BUT000 are included automatically in the DataSource 0BPARTNER for integration with SAP BI.
Postprocessing
Depending on the enhancements defined in the EEW, you must carry out the following postprocessing activities, if necessary.
Integration with the CRM WebClient
If check tables for fields have been generated, then you must fill them with values out of the EEW by means of the relevant maintenance views.
You can include the fields in the CRM WebClient user interface. To do so, use the Customizing activity
Customer Relationship Management 
UI Framework UI Framework Definition Configure User Interface 
.
Integration with CRM Field Applications
For data exchange with the CRM Field Applications, the following postprocessing activities must be carried out:
You must transfer the table enhancements in the CDB and the changes in the sBDocs to the mobile clients by using the Client Console.
To display or maintain the fields in the mobile client’s dialog, you must adjust the Business Object Layer and the UI Layer accordingly with the Mobile Application Studio (MAS).
If a new field is to be used as a distribution criterion in the CRM Middleware Administration Console, then you must define it as a distribution criterion in the Administration Console.
To use check tables for the new fields on mobile clients too, you must adjust the check tables, the sBDocs, and the data exchange between the CRM Server and CRM Field Applications. You must create the corresponding dialog objects (dropdown box) manually by using the MAS.
Integration with SAP ECC
For the data exchange with SAP ECC, the following postprocessing activities must be carried out:
You must create the Customizing include structures CI_CUST and CI_CUST_X in SAP ECC.
If fields that are not contained in table KNA1 and IDOC segment E1KNA1M are to be exchanged with SAP ECC, then you must manually adjust the data exchange with the SAP ECC customer master. You must distinguish between two cases:
Mapping of the new field to a field in E1KNA1M is possible.
In this case, you must program the mapping in the user exit BALE.
Mapping of the new field to a field in E1KNA1M is not possible.
In this case, you must program the mapping and your own posting of the data in the SAP ECC customer master, in the user exit AALE. This procedure has the advantage that the business partner is already posted in SAP ECC as a customer.
Integration with SAP BI
For the data exchange with SAP BI, the following postprocessing activities must be carried out:
You must manually define data targets (metadata) and transfer rules for the enhanced DataSource 0BPARTNER.
Result
You have defined one or several fields for the business partner. The system has generated the necessary repository objects and table entries in SAP CRM. Since SAP CRM can neither generate objects in SAP ECC or SAP BI, nor carry out customer-specific table entries, postprocessing may be necessary.