Adding New Tables to the Business Partner 
With the Easy Enhancement Workbench (EEW), you can add new tables to the data model of the business partner. The fields Client and Business Partner are used as key fields in the new tables.
SAP CRM supports you in the following functions:
Integration of new tables in the business object layer and integration in the CRM WebClient user interface. The new tables can be used in the application objects Contact Person, Employee, and Account.
Availability of the new tables in CRM Field Applications
Enhancement of the data exchange in the context of CRM Middleware. To display and process the new tables in the mobile client dialog, you must carry out downstream process steps.
Availability of additional data in SAP ECC
Enhancements to the data exchange with SAP ECC in the context of CRM Middleware. For seamless data exchange with the SAP ECC customer master or the SAP business partner, downstream operations must still be carried out in SAP ECC.
Admission and update in DataSources for the SAP Business Information Warehouse (SAP BI)
For these functions, the SAP CRM system generates all objects and table entries required, as far as is technically possible.
Process
To add new tables to the business partner, use the business object Business Partner (BUPA) or Business Partner Relationship (BUPR) and create an enhancement of the type "Add New Tables". A wizard helps you to define the new table and its fields and provides you with the necessary information for every step.
First, specify another key field for the table.
For each additional field of the new table, specify the field names, data type and, if necessary, the field length.
For each field, define whether a check table should be available.
For each field, determine whether it should be transferred to SAP BI or to CRM Field Applications.
In the last screen of the wizard the system shows you an overview of the tables that you defined along with the relevant fields and their attributes.
Choose Complete to start the generation of the necessary repository objects and table entries.
Technical Implementation
There is a more detailed overview of all created objects in the object overview that is provided for each task in the EEW. There you can also find the technical names of the objects created, which you may need for follow-up activities.
Integration with the Business Partner
The Easy Enhancement Workbench creates the following repository objects and table entries:
One data element and one domain per field
The fields Client and Partner of the table BUT000 are included in the new table as key fields
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
One table structure for each enhancement
One change document object for each enhancement
One function group for each enhancement
Function modules for the BDT events
Function modules for data processing (API for reading, creating, changing, and deleting data)
Business object layer enhancements
XIF adapter enhancements for data exchange
Middleware enhancements for data exchange
Integration with the Field Applications
For integration with CRM Field Applications, the following adjustments were made for the data exchange between the SAP CRM Server and the CRM Field Applications:
If the indicator Mobile is set for a field in the new table, then the following objects or databases are enhanced by the new table and this field:
The consolidated database (CDB)
The new table is enhanced in the CDB by specific fields of CRM Mobile (for example, as a key field of a GUID, communication fields).
The sBDoc CAPGEN_OBJECT_WRITE
The sBDoc CONGEN_OBJECT_WRITE
The sBDoc EMPLOYEE_WRITE
The mapping (Mobile Bridge)
If the indicator Mobile Brief Info is set for a field, then the following objects or databases are enhanced by the new table and this field:
The consolidated database
The sBDoc CUST_HIERARCHY
The mapping (Mobile Bridge)
Integration with SAP ECC
CRM inbound and outbound are adapted accordingly to the new table.
The mBDoc for the business partner is enhanced by the new table.
Integration with SAP BI
A new DataSource is generated for each table.
Follow-Up Activities
Depending on the enhancements defined in the EEW, you must carry out the following postprocessing activities, if necessary.
Integration with the CRM WebClient User Interface
You can include enhancements for the object BUPA in the Account page and the Employee page as additional assignment blocks. You can include enhancements for the object BUPR in the pages for relationships and contact persons. The system shows the enhancements in the CRM WebClient user interface in the BSP component BP_EEW. This component contains the following views, reused by all enhancements:
BP_EEW/List: Maintenance of a BUPA enhancement in editable overview pages
BP_EEW/RelEL: Maintenance of a BUPR enhancement in the relationship detail view
BP_EEW/ContactRelEL: Maintenance of a BUPR enhancement in the contact person detail view
For each enhancement, you must create a specific configuration that the system retrieves at runtime. To include the enhancement in the applications, you must maintain the corresponding file Repository.xml. You must create an enhancement set and enhance the components BP_HEAD (for account processing), BP_CONT (for contact person processing), BP_EMPL (for employee processing), or BP_DATA (for the detail view of relationships and contact person relationships). After generating the enhancement, perform the following postprocessing steps in the Easy Enhancement Workbench:
BP_EEW_CONFIG
When you call this postprocessing step for an enhancement to object BUPA for the first time, the system generates a configuration that contains all the fields of the enhancement, for the view BP_EEW/EL. For object BUPR, you must create the configurations for the views BP_EEW/RelEL and BP_EEW/ContactRelEL. If you perform the step again, the system starts the BSP Component Workbench for component BP_EEW. There, you can individually adjust the configurations for each enhancement. You can find details about selecting the correct object subtype in the long text of the postprocessing step. The object subtype corresponds to the object name of the enhancement.
BP_EEW_REPOSITORY
Depending on which application you enhance, you need to adjust the file repository.xml. A prerequisite of this is that an enhancement set exists and that the component was enhanced. Through the execution of this postprocessing step, the system generates the adjustments.
BP_EEW_OV_CONFIG (only for object BUPA)
The new assignment block is hereby included with the enhancement in the overview page. The system calls the Component Workbench. Specify the required components. You can then adapt the configuration to the appropriate overview page. Enhancements to relationships are automatically visible in the respective detail view.
If check tables were generated for fields, then you must fill these with values from the EEW using the associated maintenance views.
You can create views in the CRM WebClient based on the enhanced business object model. To do so, use the Customizing activity
Customer Relationship Management 
UI Framework UI Framework Definition Configure User Interface 
.You can find more information about enhancement options in SAP Note 1069791.
Integration with CRM Field Applications
For integration 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 of the table 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 as well, 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 object (dropdown box) manually by using the MAS.
Integration with SAP ECC
In SAP ECC, you must manually adapt the data exchange for the integration of new tables in the data exchange with SAP ECC.
Adjustments for the Customer Master in SAP ECC
The type pool has to be enhanced by the new table.
Mapping between the BAPIMTCS and the structure of the type pool must be defined.
The posting of the data in inbound processing of the customer master in SAP ECC must be defined in the user exit AALE.
The outbound processing of the customer master in SAP ECC must be similarly enhanced.
This includes filling the complex structure and triggering outbound processing.
Adjustments for the SAP Business Partner
The copy for the complex structure must be adjusted.
Mapping between the BAPIMTCS and the complex structure must be adjusted in the event module (Plug-In: Table COM_BUPA_CALL_FU).
The posting of the data must be adjusted in the event module (Plug-In: Table COM_BUPA_CALL_FU).
The outbound of the SAP business partner must be adjusted.
This includes filling the complex structure and triggering outbound processing.
Integration with SAP BI
For data exchange with SAP BI, you must define the data targets (metadata) and the transfer rules for the newly-generated DataSource manually.
Result
You have defined the new tables and fields and 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 might be necessary.