System Requirements 

The different functions for Campaign Management have different system requirements of the software components. The table below specifies the minimum release level required for each software component. The functions listed will be explained in greater detail later on in the documentation.

Software component Function	SAP IS-U/CCS	SAP BW	SAP CRM
BW extraction of marketing-relevant data (non-parallel selection in SAP IS-U)	4.63	2.1C	3.0
BW extraction of marketing-relevant data (parallel selection in SAP IS-U)	4.64	3.0B	3.0
CLTV analysis for utility contracts	4.63	3.0B
Creation of consumption history in IS-U, from bill documents or installation facts	4.71
Segmentation and campaign execution by technical objects	4.63	3.1 Content (BI Content 3.3 Add-On)	4.0
Bill supplement in SAP GUI	4.63		3.0
Bill supplement in the People Centric UI	4.64		2004 Service Industry Extension

The current plug-in must also be installed in the IS-U system.

Each software component, namely SAP IS-U/CCS, SAP BW, and SAP CRM has one client. These clients are linked via Remote Function Call (RFC) destinations.

The IS-U client and the CRM client are created as source systems in SAP BW. Each of these source systems requires a user with administrator authorization. Changes to the repository and cross-client Customizing must also be permitted.

You must have set up the IS-U/CRM business partner integration. See the notes on business partner replication in the IS-U/CRM Integration of Residential Customers documentation in the Help Portal under the Internet address http://help.sap.com → Documentation → mySAP Business Suite → CRM 4.0 Service Industry Extension → Industry-Specific CRM ® Service Industries ® Utilities ® Sales Processing for Residential Customers.

Note that a business partner must have the same number in SAP IS-U and SAP CRM. For each internal number range in one system (number range object BU_PARTNER), an external number range with the same number area must be created in the other system and allocated to a grouping (TB001 table). During the data exchange, the system automatically selects a grouping that is allocated to this number range.

Set up the areas in such way, that there is enough space for a long-term operation.

The regional structure must be maintained in the IS-U system. You can import the regional structure from an external source using a transfer program (see OSS note 132948). We recommend that you maintain an identical regional structure in the CRM system. To do this, the regional structure must be copied from SAP IS-U to SAP CRM via initial download (see OSS note 366034). Changes to the regional structure can be imported into SAP IS-U via the same process (meaning that you must repeat the initial download to SAP CRM).