You are on page 1of 5

Adding New Fields in Business Partner

Purpose
You can add new fields to the central table BUT000 of business partner using the
Easy Enhancement Workbench (EEW).
SAP CRM supports the following functions:
The integration of the new fields into the SAP GUI and People-Centric UI interfaces
For the SAP GUI user interface we revert to the Business Data Toolset (BDT).
Availability of the new fields in the CRM Field Applications
Extensions to 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 the new fields in SAP R/3
Extensions to data exchange with SAP R/3 in the context of CRM Middleware. For seamless
integration, downstream operations still have to be carried out in SAP R/3.
Admission and update of new fields in Data Sources for the SAP Business Information Warehouse
(SAP BW)
For seamless integration, downstream operations still have to be carried out in the SAP BW.
For these functions, the system automatically generates all objects and table entries
required.
Process Flow
...
1. To add new fields to the business transaction, use the business object CRM Business
Partner (BUPA) and create an extension of the type Add New Fields. A wizard helps you define
the individual extensions and provides you with the necessary information for each step.
2. For each field, you must define the field name, data type and, if necessary, the field length.
3. For each field, you must specify whether a check table is to be available.
4. For each field, you must also specify whether it is to be transferred to SAP BW or to CRM Field
Applications.
5. In the last wizard screen, the system shows you an overview of the fields you defined, together
with their associated attributes.
6. To start generation, choose Complete.
Technical Implementation
For extensions to the business partner, the EEW uses the Customizing include
structures CI_EEW_BUT000 and CI_EEW_BUT000_X (update toolbar).
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 will also find the technical names of the
created objects, which you might require for postprocessing.
Integration with the Business Partner Dialog
Among others, the EEW creates the following repository objects and table entries for
integration with the CRM Business Partner dialog:
One data element and one domain per field
The API and screen structures required for each extension
Check tables and associated maintenance views for selected fields, if necessary, through which
the check tables must be filled with values in post processing.
The check tables are now generated for the CRM Server only, and not for the CRM Field
Applications.
One function group for each extension
A function module for each field for the PBO and PAI, in which is specified what happens to the
fields in PBO or PAI
Function modules for the BDT periods DLEV1, DSAVB, ISDST, ISSTA and XCHNG
Function modules for data processing (API for reading, creating, changing, and deleting data)
A BDT view for each field for the user interface SAP GUI
One or several BDT sections for each extension
A BDT section can include a maximum of 10 BDT views.
Depending on the situation, a BDT screen for the user interface SAP GUI
During the first extension of the business partner, a new BDT screen (tab page) is created. Each
BDT section can include a maximum of 10 BDT views If the number of ten BDT sections for each
BDT screen is exceeded, then the EEW generates a new BDT screen.
A new tab page for each extension for the user interface People-Centric UI
Integration with CRM Field Applications
If the indicator Mobile is set for a field, then the following objects are extended 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 this field, then the following objects are
extended by this field:
Table SMOKNA1SHT in the CDB
The associated sBDoc CUST_HIERARCHY
The Mapping (Mobile Bridge)
Integration with SAP R/3
For integration with SAP R/3, the following adjustments were made for the data
exchange between an SAP CRM and an SAP R/3:
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 R/3 for the R/3 Customer Master:
In SAP R/3 3.1, the type pool was extended by the include CI_CUST (including field DUMMY1)
and CI_CUST_X.
During data exchange between SAP CRM and SAP R/3, it is assumed that the Customizing-
include structure CI_EEW_BUT000 and the Customizing-include structure CI_CUST have the
same composition and may only differ in the number of fields. The data types and sequence of
fields must match.
In SAP R/3, conversion of the BAPIMTCS to the complex structure of the SAP R/3 is extended
accordingly in both directions for the R/3 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 R/3 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 extended using the EEW by a field that already
exists in the R/3 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 R/3 analogously to the SAP CRM Customizing-include structures
CI_EEW_BUT000 and CI_EEW_BUT000_X in order to enable data exchange with
the R/3 customer master.
Adjustments in SAP R/3 for the SAP Business Partner:
In SAP R/3 4.6C, the copy of the complex structure of the SAP CRM was extended by the include
CI_EEW_BUT000.
During data exchange between SAP CRM and SAP R/3, it is assumed that the Customizing-
include structure CI_EEW_BUT000 and the Customizing-include structure CI_CUST have the
same composition and may only differ in the number of fields. The data types and sequence of
fields must match.
In SAP R/3, conversion of the BAPIMTCS to the complex structure of the SAP R/3 is extended
accordingly in both directions for the SAP Business Partner.
Integration with SAP BW
The new fields in table BUT000 are included automatically in the DataSource 0BPARTNER for
integrating with SAP BW.
Postprocessing
Depending on the extensions defined in the EEW, you must carry out the following
postprocessing activities, if necessary.
Integration with the Business Partner Dialog
If check tables were generated for fields, then you must fill these with values from the EEW using
the associated maintenance views.
To define user-defined checks in the new fields in the dialog, you must manually create a function
module. For more information, see the BDT Manual, Chapter 4.1 Additional Check for Existing
View.
You can adjust the generated BDT views and BDT segments in the SAP GUI to your specific
requirements by using the Visual Configuration Tool (VCT). You should make this adjustment after
completing various extensions.
Integration with CRM Field Applications
For the data exchange with the CRM Field Applications, the following postprocessing
activities must be carried out:
You must transfer the table extensions in the CDB and the changes to the sBDocs to the Mobile
Clients by using the Client Console.
To display or maintain the fields in the Mobile Clients 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 be able 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 object (Dropdown Box) manually by using
the MAS.
Integration with SAP R/3
For the data exchange with SAP R/3, the following postprocessing activities must be
carried out:
You must create the Customizing include structures CI_CUST and CI_CUST_X in SAP R/3
If fields that are not contained in table KNA1 and IDOC segment E1KNA1M are to be exchanged
with SAP R/3, then you must manually adjust the data exchange with the R/3 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 your own posting of the data in the R/3
customer master in the User Exit AALE. This procedure has the advantage that the
business partner is already posted in SAP R/3 as a customer.
Integration with SAP BW
For the data exchange with SAP BW, the following post processing activities must be
carried out:
You must manually define data targets (metadata) and transfer rules for the extended Data Source
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 R/3 or SAP BW, nor carry out user-defined
table entries, post processing might be necessary.