Integrating the Address Controller

Prerequisites

You use the People Centric UI for your application.

Procedure

In this chapter you will find an overview of the steps the application has to take in order to include the address controller in the UI. The steps are as follows (names given in the form [text] are arbitrary, but have to be the same in all instances with the same text):

1. Create a subclass of the abstract model access class template CL_BSP_MODEL_ACCESS_ADDRESS.

   Throughout this document, we will call this subclass CL_BSP_APPLICATION_ADDRESS.

2. In the class CL_BSP_APPLICATION_ADDRESS, implement the method GET_ADDRESS_KEY.

   In this method, the application provides for each object key the corresponding address ID, consisting of address type, address number/handle plus eventually person number/handle.

3. In the class CL_BSP_APPLICATION_ADDRESS, implement the method ADDRESS_IS_CREATED.

   This method will be called to notify the application that a newly created address was written to the BAS memory for the first time. For more information, refer to Creating an Address.

4. In transaction CRMC_BLUEPRINT, under IMG activity CRM UI: Blueprint Tables  Application Elements  Application Set  Model Access for your application, maintain the following entries:

   Structure name	Access Class
   CRMT_BSP_ADDRESS	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADTEL	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADMOB	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADDRESS_PRFCOMM	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADFAX	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADTLX	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADSMTP	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADRML	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADRFC	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADPRT	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADURI	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADSSF	CL_BSP_APPLICATION_ADDRESS
   CRMT_BSP_ADPAG	CL_BSP_APPLICATION_ADDRESS

5. In transaction CRMC_BLUEPRINT, under IMG activity CRM UI: Blueprint Tables  Application Elements  Application Set  Model Access for your application, maintain the following entries:

   Structure name	Access Class	Reference Application
   SPACE	SPACE	ADDR_DETAIL

6. In transaction CRMC_BLUEPRINT, under IMG activity CRM UI: Blueprint Tables  Application/Layout  Define Layout for your application, maintain the following entries:

   View:	<Your View>
   Event:	[NAV_ADR]
   Position:	<Position of the address controller in the application>
   Screen Variant:	<Your screen Variant>
   Scrn Elmnt Type:	Multi ODC
   Field Group:	ADR_DETAIL
   Toolbar Group:	ADR_DETAIL
   Tab Group:	[TAB_APPL]
   Search Grp:	SPACE
   Docu Class:	SPACE
   Object ID:	SPACE

7. In transaction CRMC_BLUEPRINT, under IMG activity CRM UI: Blueprint Tables  Application Elements  Tab Strip  Tab Strip  Assign Events for your tab [TAB_APPL], maintain the following entry:

   View:	<Your View>
   Sequence:	<Position in your tab>
   Event:	[NAV_ADDR]
   Multigroup	ADR_DETAIL

8. In transaction CRMC_BLUEPRINT maintain the following entries under IMG activity Design of People-Centric UI  View  Navigation: Log Messages  Assigning Log Messages to a Navigation for your application:

   Message ID:	SPACE
   Message number:	SPACE
   Context :	<The context of the address controller within your application>
   Message Group:	ADR_DETAIL
   Object Name:	SPACE
   Field Name:	SPACE
   Event:	[NAV_ADDR]
   Screen Position:	<The screen position of the address controller>
   Action Event:	SPACE

   The value entered under Context here must be identical to the value the method GET_ADDRESS_KEY of class CL_BSP_APPLICATION_ADDRESS returns.

9. Adapt the coding of your own model access classes.