Академический Документы
Профессиональный Документы
Культура Документы
0 Applications
Scope: This Guideline describes which actions are necessary for customers to extend
CRM applications in an easy way by adding their own fields. This guideline is only
valid for the applications described using the People-Centric UI.
Current Version: 1.3, 9th of May 2003
CI 1
CI 1
UI
BSP-Application
Access Class
API
CI 1
CI 1
The picture shows the principle for a CRM Application using the people-centric UI.
The anchor object of extensions is the Application object (for example, Activity
Header) containing a Customizing Include. The relevant database table also includes
this Customizing Include, as well as API structures and one or more suitable screen
structures.
Care is taken that the Customizing Include is mapped directly between those places.
All fields that belong to a Customizing Include of a screen structure are displayed
automatically in the people-centric UI with a default behavior (visible, editable). If a
field is not to be visible on a particular screen, it can be switched off using the CRM
Designer Tool.
1.2 Restrictions
There are some restrictions to this very simple and lean approach:
Fields appear on predefined screens, they cannot be moved to other screens.
It is only possible to add fields (1:1 relationship), not tables
CRM Middleware BDocs are not automatically extended (exceptions are
mentioned below)
Migrating manual extensions to Customizing Includes is not supported currently
CRM Designer is a WYSIWYG, graphical Tool used to alter the screen layouts of any CRM
application. The Advanced Search Area, Detail Area and List Area of a CRM application can be
altered to suit customer specific needs.
1.3.5 Example
You wish to maintain a personal risk factor for customers (technically: Business
Partners) of an insurance company. For that purpose, just create a domain (for
example, ZPERSRISK) with predefined risk values (for example, LOW,
MEDIUM and HIGH) and a data element (for example, ZPERSRISK as well)
with a describing text (for example, personal risk factor).
Then create an Include called CI_EEW_BUT000, containing a field (for example,
ZZPERSRISK) with your data element:
Customizing Include
BDoc
Remarks
Business Partner
Business Transaction
Business Transaction Item
Activity Header
CI_EEW_BUT000
CI_EEW_ORDERADM_H
CI_EEW_ORDERADM_I
CI_EEW_ACTIVITY_H
CI_EEW_ACTIVITY_I
X
X
X
X
X
1)
CI_EEW_OPPORT_H
CI_EEW_LEAD_H
CI_EEW_PRODUCT_I
CI_EEW_FINPROD_I
X
X
X
X
CI_EEW_SALES
CI_EEW_SHIPPING
CI_EEW_BILLING
CI_EEW_ORGMAN
CI_EEW_PRICING
X
X
CI_EEW_PRICING_I
CI_EEW_SCHEDLIN
X
X
CI_EEW_SERVICE_I
CI_EEW_CUSTOMER_H
X
X
2)
CI_EEW_CUSTOMER_I
2)
Activity Item
Opportunity
Lead
Transaction Item - Product
Transaction Item - Financing
Product
Business Transaction - Sales
Set
Business Transaction Shipping Set
Business Transaction - Billing
Set
Organizational Unit Set
Business Transaction Pricing
Parameter Set
Transaction Item - Price
Business Transaction Item Schedule Line
Transaction Item - Service
Transaction - Additional
Extension
Transaction Item - Additional
Extension
SDB - Symptom
SDB - Solution
Marketing element: Basic data
Marketing element: Execution
Installed Base (header)
Installed Base Component Addition/Specialization
Remarks:
CI_EEW_ISMP
CI_EEW_ISOL
CI_EEW_MKTPL_BDINC
CI_EEW_MKTPL_CHINC
CI_EEW_IBIB
CI_EEW_IBSP
CI_EEW_ACT_CATEGORY_EXT
CI_EEW_IBU_CP_EXT
CI_EEW_CHANNEL_COMM_EXT
CI_EEW_CMSS_DRG_SETTYP_EXT
CI_EEW_CRMT_CMG
CI_EEW_MPK_READING_WRK
CI_EEW_MPK_MPOINT_WRK
CI_EEW_ACTIVI
TY_I_UI
3)
3)
X
X
+UI