01 customer service master data scen guide en us

Version 1.600

April 2006

Scenario Guide

SAP AGNeurottstr. 1669190 WalldorfGermany

Customer Service Management: Master Data

SAP Best Practices Customer Service Management: Master Data

Copyright

© Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without

the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.

© SAP AG of 63


Contents

Master Data......................................................................................................................................... 4

Technical Master Data.....................................................................................................................4

Assumptions................................................................................................................................. 4

Connection Object........................................................................................................................ 5

Premise........................................................................................................................................ 5

Device Location............................................................................................................................ 5

Utility Installation........................................................................................................................... 5

Explanation of functions and events.............................................................................................6

System configuration considerations............................................................................................8

Master Created for the Template................................................................................................16

Business Master Data.................................................................................................................... 17

Assumptions............................................................................................................................... 17

Business Partner........................................................................................................................ 17

Explanation of functions and events...........................................................................................20

Business model.......................................................................................................................... 22

System configuration considerations / actions: Non-CCS in R/3...............................................24

Area Menu: BUPT: additional settings........................................................................................37

Area Menu: BUMR: Relationships..............................................................................................41

System configuration considerations / actions: CRM.................................................................45

System configuration considerations / actions: Non-CCS.........................................................45

System configuration considerations / actions: CCS.................................................................53

Master Data Created for the Template.......................................................................................58

Organizational Structure................................................................................................................59

Requirements/Expectations/Assumptions..................................................................................59

General explanations.................................................................................................................. 59

Explanation of functions and events...........................................................................................60

System configuration considerations / actions............................................................................60

Master Data Created for the Template.......................................................................................60

Available Screen Simplification Tools............................................................................................61

GuiXT......................................................................................................................................... 61

BDT (Business Data Toolset).....................................................................................................62

© SAP AG of 63


Master DataMaster data is data in mySAP Utilities that remains unchanged over an extended period. Master Data is divided into:

Technical Master Data (the premise information)

Business Master Data (the customer information)

The technical master data consists of:

Connection object: the service address (usually a building)

Premise: details of the service address (a unit within the connection object, 1-1 if a single family home)

Device location: the physical location of the meter or meters

Utility installation: a CCS object that stores billing and scheduling data; it maintains an historical reference for the services provided over time

The business master data consists of:

Business partner: the customer with whom the utility company does business

Contract account: the master data object that controls the financial aspects of a customer’s service - generally considered as the “account”

Utility contracts: essentially the active services of the customer at a point in time

Business and Technical Master Data are united in the Move-In process in which the service is activated and the contract is created. This construct is known as the CCS or IS-U Data Model and is the foundation of the IS-U system.

Technical Master DataTechnical Master Data in CCS includes the following objects:

Connection Object: the service address (usually a building)

Premise: the details of the service address (a unit within the connection object)

Device Location: the physical location of the meter

Utility Installations: a CCS object containing billing and scheduling data

Assumptions Static Notes will not be used at the connection object; they will be used at the device

location.

Premise-based Owner Allocation will not be implemented; we have implemented the Automatic Owner Allocation.

© SAP AG of 63


Connection ObjectA connection object is usually a building, but it can also be a property or other entity (such as a fountain or a construction site). Since a connection object is allocated an address, it links premises, device locations, and connections with the postal regional structure. The connection object is allocated to a maintenance plant for Work Management purposes; the maintenance plant corresponds to a service territory in CCS. A regional structure group is also allocated for the assignment of work centers in work order processing.

The connection object is based on the functional location of the Plant Maintenance component. A functional location in PM is created automatically when the Connection Object is created, sharing the same number or key.

In addition to the general data of the functional location, the connection object contains industry-specific data.

PremiseA premise is an enclosed spatial unit (such as an apartment or suite) to which a utility service is supplied. Several utility installations can be allocated to one premise (for different divisions: water and wastewater, for example). The premise is therefore not related to one specific division. It is allocated to a connection object and contains the address of that connection object.

In addition, you can maintain additional data about the location of the premise (for example, which floor). Premise types have been maintained for use in describing the nature or type of use of the unit.

Device LocationA device location is a place within a connection object where devices are installed. You will allocate both the address of the connection object and a particular premise to the device location, and you can enter a description to define the exact location of the devices. This means that you can use the device location to locate an installed device.

The device location, like the connection object, is based on the functional location of the Plant Maintenance component. This means that you can also use Plant Maintenance functions in the device location. The device location will serve as the technical reference object for work orders created for new properties without a meter installed. A functional location in PM is created automatically when the Device Location is created, sharing the same number or key.

Static notes to field service technicians are created for use in the device location.

Utility InstallationIn mySAP Utilities, the connection between the premise, devices, and contracts is referred to as a “utility installation” (or “installation” for short). The installation contains data relevant to billing contracts, for example the rate category and installation facts or values used in billing. The installation is not a technical construct. Multiple devices can be installed in a utility installation and in turn, the devices can comprise several registers.

At any given time, the installation is allocated to a single contract. An installation is only not allocated to a contract in exceptional circumstances (for example, installation under construction, installation vacant, and not allocated to an owner).

Scheduling determines the meter reading dates for the installation. The meter reading unit to which the installation is allocated governs these dates. The meter reading unit also links the installation to the portion in which the billing dates are defined. Rate categories are stored in the installation. When

© SAP AG of 63


the contract is billed, the rate category determines and bills the relevant rates. The data in the installation that is relevant to billing is managed historically. This means that a contract partner can be switched to a different rate category during a billing period. Price information is usually stored in the rate category facts; in exceptional cases, they can be stored in the installation facts (for example, individual prices or factor values).

The Billing Period button on the Installation toolbar contains views of all rate, meter reading, billing and device data for any and all customers allocated to that installation over time. In addition, it is at the Installation codes are entered or reasons for supply guarantee to prevent accidental disconnection. The meter reading control setting for permissible number of consecutive estimated and customer meter readings is stored on the Installation. The installation can also be blocked for meter reading order creation using the blocking functionality on the Installation.

Service Connections, or the initial data creation of the technical master data, is a vital process for the utility company when new services need to be established. Please refer to the Service Connection Process document for the details of the process; the use of the Interaction Center (or IC) for the actual creation of the objects in CCS is described below and in the Interaction Center documentation. The technical master data MUST exist prior to activation of a customer’s service with the utility company (known as “move-in” in CCS).

Explanation of functions and eventsTechnical Master Data will generally be created in a single step via a Front Office Process for Initial Data Creation. Entering minimal input values, the FOP has been configured to adopt many default values that are not seen by the agent.

Multiple transactions are processed in what appears to be a single step to the agent.

A walkthrough of the creation of technical master data using the individual transaction codes:

Connection Object:

Menu Path: Utilities Industry Technical Master Data Connection Object Create

Transaction Codes: ES55: Create Connection Object

ES56: Change Connection Object

ES57: Display Connection Object

Steps:

1. Call transaction Code: ES55

2. Click Enter and then: Enter address information

3. Clicking Enter will allow any values stored in the regional structure to default (jurisdiction code and maintenance plant).

4. SAVE: the connection object and a corresponding functional location is created in Plant Maintenance.

© SAP AG of 63


Premise:

Menu Path: Utilities Industry Technical Master Data Premise Create

Transaction Codes ES60: Create Premise

ES61: Change Premise

ES62: Display Premise

Steps:

1. Call transaction code: ES60

2. Enter the connection object number on the next screen after clicking Enter.

3. Enter additional address details: apartment number in the house number supplement field

4. Enter a premise type

5. SAVE

Device Location:

Menu Path: Utilities Industry Technical Master Data Device Location Create

Transaction Codes: ES65: Create Device Location

ES66: Change Device Location

ES67: Display Device Location

Steps:


2. Enter the connection object and premise number on the second screen after clicking Enter.

3. Enter additional information as needed to identify specific data about a meter or its actual placement

4. Enter Notes to the meter reader for the download

5. SAVE

Installation(s):

Menu Path: Utilities Industry Technical Master Data Installation Create

Transaction Codes: ES30: Create Installation

ES31: Change Installation

ES32: Display Installation

Steps:

1. An installation will be created for each service needed: water, fire and wastewater.


3. Enter a key date (as far back in time as needed for any activity)

© SAP AG of 63


4. Enter the appropriate division: note: this is the only technical master data object to be division specific.

5. Press Enter

6. Enter the premise number on the next screen

7. Enter the time dependent data needed: billing class, rate category and MRU.

8. Enter a MR Control group

9. Enter an installation type and supply guarantee reason as needed.

10. SAVE

System configuration considerationsSPRO SAP Reference IMG SAP Utilities Master Data Basic Settings Define Structure Indicator and Category of Functional Locations

Obj. Cat. For IS Str. Ind. Functional Loc. Cat. Int NR EXT NR

C (conn. Obj.) AO_GP A 03:

D (dev. Loc.) AO_GP G

Connection Object:

Define Number Ranges for Connection Objects/Device Locations

As both objects are Functional Locations in PM, they share a single number range:

01: 6100000000 to 6190000000, internal number assignment

02: A to ZZZZZZZZZZ, external number range

Define Field Selection for Connection Objects:

(The HiLi field will cause the field noted to be highlighted):

Modifiable Field Field Name Input Req Disp. Hide HiLi

Authorization Group Text

EHAUD-BEGRUTXT X

Authorization Group EHAUD-BEGRU X

County Code EHAUD-COUNC X

Description EHAUD-COUNCTXT X

Description EHAUD-PLTXT-TPLMA X

Description EHAUD-REGPERMTXT X

Description EHAUD-REGGRPTXT X

FuncLocDescription EHAUD-PLTXT X

© SAP AG of 63


Modifiable Field Field Name Input Req Disp. Hide HiLi

Maintenance Plant EHAUD-SWERK X

Name 1 EHAUD-SWERKTXT X

Pol. Reg. Str. Elem. EHAUD-REGPOLIT X

Reg. Struc. Group EHAUD-REGIOGROUP X

Reg. Structure Text EHAUD-REGPOLTXT X

SPP Reg. Str. Group EHAUD-REGIOGROUP??SPP X

Short Description HL EHAUD-SCHLWORT X

Status EHAUD-STTXTS X

Superior Func. Loc. EHAUD-TPLMA X

User Status EHAUD-STTXTU X

Define Field Selection Control for Address Data:

Only those fields selected for use on the screen are shown below. All other fields are marked as “field not displayed”.

Field Name Use of Field

Street Name Required Entry

Loc Field Proposed for maintenance (dialog window)

Postal Code Required Entry

Country Required Entry

Region Required Entry

House Number Field Proposed for maintenance on standard screen

House Number Affix Field Proposed for maintenance (dialog window)

Building Code Field Proposed for maintenance on standard screen

Floor Field Proposed for maintenance on standard screen

Jurisdiction Code Default display as proposed by address management

Premise:

Define Number Range for Premise



Define Field Selection for Premise

© SAP AG of 63


Modifiable Field Field Name Input Req Disp Hide HiLi

Additional Data EVBSD-HAUS_NUM2 X

Floor EVBSD-FLOOR X

Location Supplement EVBSD-LOZUSATZ X

Main Residence EVBSD-HPTWHNSITZ X

Number of Persons EVBSD-ANZPERS X

Owner EVBSD-EIGENT X

Premise EVBSD-VSTELLE X

Street 3 EVBSD-STR_ERG2 X

Street 5 EVBSD-STR_ERG4 X

Type of premise EVBSD-VBSART X

Define Premise Types

The premise type is being used to describe the use of the premise.

Prem. Type

Text for Premise Type

1000 Single-Family Home

1001 Multi-Family Home

1002 Apartment

1003 Condominium

1004 Office

1005 Factory

1006 Church

1007 Municipal

1008 Hair Salon

1009 Car Wash

1010 Laundromat

1011 School

1012 Retail

1013 Industrial

1014 Commercial

Allocate Divisions to Equipment Categories

No values are entered here; the object: “Technical Installation” is not included in the template.

© SAP AG of 63


Utility Installation:

Define Number Ranges for utility installations



Define Field Selection for Installation

Modifiable Fields Field Name Input Req Disp Hide HiLi

Authorization Group EANLD-BEGRU X

Base Period Category EANLD-BAPERTYP X

Billing Service Prov. EANLD-BILLING_PARTY X

Blocking Reason EANLD-ABLSPERR X

Blocking Reason Text EANNODISCONCTLD-ABLSPRRTXT

X

Deletion Indicator EANLD-LOEVM X

Deregulation Status EANLD-DEREGSTAT X

Franchise Contract EANLD-KONZVER X

Grouping Type EANLD-INSTGRTYPE

Guarantee of Supply Txt EANLD-NODISCTEXT X

Guarantee of Supply EANLD-NODISCONCT X

Industry EANLD-BRANCHE X

Inst. Type Text EANLD-ANLARTTEXT X

Inst. Type EANLD-INSTROLE X

MR Control EANLD-ABLESARTST X

No device allocation EANLD-PAUSCHAL X

Obligation to Supply EANLD-PROV_LAST_RES X

Period of previous year EANLD-BAPER_YEAR X

Previous period EANLD-BAPER_PER X

Primary Installation EANLD-MAININST X

Reference EANLD-BEZUG X

Release status EANLD-INFOREL X

Service Type EANLD-SERVICE X

Temperature Area EANLD-TEMP_AREA X

Text Service Type EANLD-SERVICETEXT X

© SAP AG of 63



Text MR Control EANLD-ALARTSTTXT X

Text for dereg. status EANLD-DEREGSTATTEXT X

Text for release status EANLDINFORELTEXT- X

Time Zone EANLD-TIMEZONEDYNP X

Time Zone Text EANLD-TIMEZONETEXT X

Voltage Level EANLD-SPEBENE X

Voltage Level Text EANLD-SPEBENETXT X

Define Reasons for Supply Guarantee

Supply Guarantee is used to prevent accidental disconnection as well as a notification of medical needs for water supply. Both conditions are documented here.

Guar. Supply Guarantee of Supply Reason

100 Dialysis patient

101 Hospital

102 Nursing Home

103 Mult-Family

104 Fire Service

105 Other: No Disconnection

Define Installation Type:

The installation type is being used to describe the service provided; it further distinguishes the service within the division.

Inst Type Text

WTR Water

MSWR Metered Sewer

USWR Unmetered Sewer

HYD Hydrant

MFIRE Metered Fire

UFIRE Unmetered Fire

Device Location:

Define Field Selection for Device Locations


EGPLD-BUT_NOTE X

BUT-STATUS X

AuthorizGroup EGPLD -BEGRU X

© SAP AG of 63



FunctLocDescrip. EGPLD -PLTXT X

FunctLocDescrip. EGPLD -HAUSTXT X

Location EGPLD -STORT X

Location addition EGPLD -STORTZUS X

Maintenance plant EGPLD -SWERK X

Name 1 EGPLD -SWERKTXT X

Premise EGPLD -VSTELLE X

Status EGPLD -STTXTS X

Text for location EGPLD -STORTTEXT X

User Status EGPLD -STTXTU X

Data Environments for the Technical Master Data Objects:

SAP Utilities Customer Service Customer Information Define Data Environment Display

Connection Object: CONNOBJ:

© SAP AG of 63


Fields displayed on the environments seen here can be altered as follows:

1. Copy an existing data environment

2. Select a node and click on the “choose” icon on the tool bar to display the Structure Node Maintenance screen.

3. Nodes can be marked as “never display”

4. Nodes can have multiple attributes defined to provide additional information on the environment

5. Colors can be modified to provide contrast and clarity to the various objects and values defined.

Premise:

© SAP AG of 63


Installation:

Device Location:

© SAP AG of 63


Device: (included here for information purposes):

Master Created for the TemplateThe results of the configuration described here is the set of technical master data describing the service territory. It can be created as a series of transaction codes or via a Front Office Process from the Interaction Center.

Reports

None are apparent.

Conversion Expectations

The master data conversion is vital to the success of the implementation; it is crucial that adequate time be dedicated to the mapping of the objects. It is also recommended that the legacy data undergo rigorous data cleansing before conversion.

Installation: you will want to set the base period category as required for your company: same period of the previous year or the previous period (the default value).

Authorization and user roles

How will you manage security in this area? Describe high-level authorization requirements. Also, make sure the team is aware of system functions and get the process owners thinking about how to control access to systems and their data.

© SAP AG of 63


Business Master Data The business master data consists of:

• Business partner

• Contract account

• Utility contracts

Assumptions

Business partner

All customer specific data, such as name, address, contact information, bank data, etc. is stored in this object. In addition, the role or the details of the customer’s relationship with the water utility is included in the record.

The business partner is the water utility’s customer.

Contract account

This object’s details include payment terms, credit terms, specific bank ID. Generally all financial information for the customer’s account is stored here. Invoicing is performed at the contract account level in CCS.

The Contract Account can be regarded as the water utility’s account.

Utility contracts

Contracts are the agreements between the water utility and the customer. They describe the type of service. There is a one-to-one relationship at any point in time between the utility installation and a contract. The contract is not created as a separate object; it is created as part of the move-in process and exists only for the length of service for a customer at a particular premise.

The contract is essentially a service: water and wastewater reflect two different services.

Business Partner

Categories

Business partners are classified according to the business partner categories “natural person,” “group,” and “organization.” The template uses organization and natural person. It is not possible to create new categories or to redefine later a Business Partner created with the wrong category.

You can store different information depending on the business partner category you choose. The rules for the structure of the name will vary as well as the presence or absence of fields related to the Business Partner Category. For example, an organization can have the legal organization of the company identified, while gender is an available field for natural person.

The master record of a business partner contains data from the following areas:

© SAP AG of 63


• Name

• Personal data

• Address, including telephone and fax numbers

You can enter other addresses in addition to the standard address. The address management component manages the addresses centrally with a uniform structure. It determines whether the addresses entered meet country-specific rules and whether the cities and streets exist in the postal regional structure.

• Bank details - More than one set of bank details can be entered (for example, different accounts for separate contract accounts)

• General data (for example, credit rating, social security number, etc.)

Roles

In SAP R/3, a business partner can assume a number of roles simultaneously. However, a business partner’s master data is stored just once in a central master record. This reduces the amount of maintenance required and prevents data inconsistency. This is known as the Central Business Partner Functionality.

CCS and the Best Practice for Water Utilities use the business partner in the following roles:

Contract partner

The ”Customer“ is an entity with whom the utility company maintains a contract for delivery and purchase of utility services.

A contract partner can be a residential customer, non-residential customer, other utility company, service provider, local authority, property owner, or third party.

Contact person

The name of the person who is designated by a contract partner to interact with the utility company: if a business partner is maintained with only this role, he cannot have a contract account allocated for services unless the role of contract partner is added to his record.

Installer

This role describes an external agent with whom the utility company conducts business. An example is plumber.

General business partner

This role is stored for information purposes only and is neither a contract partner of the utility company nor a contact person or prospect: all business partners inherit this role automatically.

Employee

We are maintaining this role as many utilities use it to monitor their employees for various reasons.

SD Reference Customer:

© SAP AG of 63


The Template is configured to support the creation of an SD Reference Customer to be created simultaneously with the ISU Business Partner.

That customer can:

o Be billed for miscellaneous charges resulting from Work Orders or maintenance plans. We are not using SD (Sales and Distribution) billing in the Template, but the creation of an SD customer is required for CRM and cannot be added after the creation of an ISU Business Partner.

o Purchase goods

o A predefined reference customer is used as a template for the standard customer. The predefined reference customer created for the Template is: MUST_ALL

Business Partner Relationships

You can link business partners to one another using relationship categories. Examples include linking an organization and contact person with the “contact person” relationship category, or the “marriage” and “shared living arrangement” relationship categories.

Contract Account

A contract account groups together all of a business partner’s contracts to which the same payment and dunning data applies. The following payment transaction data is stored in the contract account:

• Bank details

• Dunning data

• Payment data

• Alternative payer, payee, bill recipient, and dunning recipient

Utility Contract

A contract is an agreement between the utility company and a business partner relating to a utility service. It forms the basis for billing (remember that the contract account is the basis for invoicing).

A contract is created in the move-in process and cannot be re-used. It exists for the period of service for a customer at a particular premise. The move-in and move-out dates define the validity period of the contract.

A contract is created for water and sewer if both services are present. In addition, if there is fire or hydrant service, there will be a contract per service.

Contract data contains the following control data for consumption billing and contract accounts receivable and payable:

• General data (such as contract account)

• Move-in and move-out data

• Data relevant to billing

© SAP AG of 63


• Account assignment data (such as the account determination ID)

A utility contract is allocated to a single contract account. You can allocate more than one contract (i.e., water and wastewater) to a contract account and then bill those services together in a single invoice.

However, only one utility installation can be allocated to each contract.

With the exception of move-in and move-out data, you can change, display, and check all the data of multiple contracts in a contract account (this applies to those contracts that have not been cancelled). You use transaction ES27 for this function; it is used where you need to change data consistently across contracts of a contract account. Alternate portion is a good example where this functionality is useful.

The move-in and move-out dates represent the beginning and end of energy supply in the division specified in the contract. If a particular utility service ends, the customer with that service is identified as moving out and the utility contract is classified as terminated.

Possible reasons for these events are as follows:

• The customer is no longer interested in the utility service. This could result in the move-out of a single service with the customer remaining an active account at that premise for other services. Fire service might be an example of this form of move-out if the option of the fire service is voluntary.

• The customer moves out of the premise. In this case, all the customer’s utility contracts are canceled (as a move-out for all contracts).

Explanation of functions and eventsThe SAP CCS system contains transactions for the creation, maintenance and display of the business master data objects. These transactions are as follows:

For Business Partner:

BP – Maintain Business Partner: this transaction code is the all-encompassing transaction code for Business Partners regardless of role. The design of the screen is new and is documented below.

FPP1 – Contract Partner Creation: this transaction creates a contract partner only. This is the most important role for a Utility Customer and will generally be created or processed from the IC with a Front Office Process.

FPP2 – Contract Partner Change

FPP3 – Contract Partner Display

FPP7 – Installer Creation: Installers (or plumbers) will be created primarily from a Front Office Process. This transaction will not be used regularly.

FPP8 – Installer Change

FPP9 – Installer Display

BUA1 – Contact Person Creation: contact persons will generally be created as part of a Front Office Process or within the Contract Partner’s screen. This set of transaction codes will not be used often.

BUA2 – Contact Person Change

© SAP AG of 63


BUA3 – Contact Person Display

FPCR1 – Display Creditworthiness: please review the Creditworthiness scenario in the Receivables and Collections blueprint.

FPCR2 – as above.

FPP2A - Activate Planned Changes: this is a report that should be run regularly to update future changes (planned changes) to the Business Partner. It should be included in the nightly batch processing.

For Contract Account:

CAA1 – Contract Account Creation: this transaction is used to create a contract account. Alternately, a front office process can be used to create a contract account. Usually, it is preferred that the user use a reference contract account to permit the common values to default into the object.

Financial information is maintained on this object.

CAA2 – Contract Account Change

CAA3 – Contract Account Display

For Contract:

ES21 – Contract Change: remember that the contract is created in the move-in processing!

1. Changing a contract is most often accomplished via a Front Office Process. By left-clicking on the contract in the Interaction Center, a context menu of actions to be performed for that data object will be displayed.

2. The agent would select the Change Contract call.

3. Changes will be made: possibly the text of the contract (entered via the MI Reference document or CRM Product allocated to the MI process), the Joint Invoice indicator or account determination ID.

4. The change will be saved, and a customer contact will be created, permitting the agent to enter free text describing the action taken.

5. Using the transaction code is similar, except that the contract must be explicitly defined. On the interaction center, the customer’s data is available for the entire data model.

ES22 – Contract Display: This function is also available from the IC as a context menu item. Generally, there will not be a contact created as a result of displaying a data model object.

ES27 – Change all contracts of a contract account: This transaction is used primarily where you need to change values across all of the contracts of a contract account. It is not called from the Interaction Center; it is always used as the standalone transaction code.

A common use is for updating the alternate portion on the contracts to affect the billing and invoicing dates without disrupting the meter reading dates derived from the MRU entered at the installation.

ES28 – Display all contracts of a contract account: as above. Display functionality only.

© SAP AG of 63


Business modelVisio Flow of the Data Model

© SAP AG of 63


System configuration considerations / actions: Non-CCS in R/3The Business Partner is configured almost exclusively outside CCS; it is configured in the Cross Application Component area of the IMG which is consistent with the Central Business Partner Concept.

SPRO → Reference IMG → Cross Application Components → SAP Business Partner→ Basic Settings→ Business Partner Roles → Properties of Business Partner Roles

In the business partner dialog you can select from all business partner roles provided. If you only want to display certain business partner roles in the selection list, you can hide the other business partner roles.

You can replace the standard title of business partner roles with customer-defined names.

In addition, you can define where the business partner role concerned is to appear in the selection list.

BP Role Standard Title Hide Position Title

BUP001 Contact Person Not selected 3 Contact Person

BUP003 Employee Not selected 2 Employee

ISUI Installer Not selected 4 Installer

MKK Contract partner Not selected 1 Utility Customer

Note: there were 5 SAP-delivered values that have been deleted: they are not roles that are for ISU.

Number Ranges and Groupings

Define Number Ranges


02: 10000 to 19999, external number assignment


XX: A to ZZZZZZZZZ, external number assignment

Define Groupings and Assign Number Ranges

Grouping Short Name Description # Range External Std. Grouping

0001 Utility Cust. # Customer Number Range

01 X

0002 0002 Ext asgmt External Number Assignment in R/3

02 X

0003 Sold To Cust # Sold To Customer Number Range

03

0005 Ext.no.assgnmnt External number assignment

02 X X

© SAP AG of 63


XX BP Ext # asgmt External Number Range: NA for use

XX X

Business Partner Types Define Business Partner Types

Partner Type: 0001

Description: Standard Customer Type

There are no “hard and Fast” rules on the use of a Business Partner type. The utility can create BP types to restrict the field grouping display (below). We have a single BP Type defined.

Field Groupings

Field Groupings are used to alter the availability or use of fields on the screens. Fields can be marked as hidden, display, optional, required or not specified. There is a hierarchy for the field use: the different fields may have different levels of use in the different configurations of field groupings; the highest level set for a field will have priority or precedence over the use of the same field in other field grouping configurations.

For example, if a field is marked “required” for one set of field groupings, and “not specified” for the configuration of another field grouping, the “required” setting will take priority. In this way, one field grouping setting can control the values set in another configuration activity.

Configure Field Groupings per Client

No entries

Configure Field Attributes per BP Roles

CONTACT PERSON (1), CONTRACT PARTNER (2), EMPLOYEE (3), and INSTALLER (4)

Data Set Field Group

Description Use:

1 2 3 4

BUA010: Addresses

62 Address: Language Key (Communication) O O O O

BUA010: Addresses

63 Address: Street O O O O

BUA010: Addresses

64 Address: P.O. Box O O O O

BUA010: Addresses

65 Address: City R R R R

BUA010: Addresses

66 Address: Postal Code R R R R

BUA010: Addresses

67 Address: District H H H H

© SAP AG of 63



Description Use:

1 2 3 4

BUA010: Addresses

68 P.O.Box Address: Postal Code and City H H H H

BUA010: Addresses

69 Address: Country R R R R

BUA010: Addresses

70 Address: Region R R R R

BUA010: Addresses

71 Address: Standard Communication Type O O O O

BUA010: Addresses

72 Address: Telephone Number O O O O

BUA010: Addresses

73 Address: Fax Number O O O O

BUA010: Addresses

74 Address: c/o Name O O O O

BUA010: Addresses

75 Address: House Number Supplement O O O O

BUA010: Addresses

76 Address: House Number Range H H H H

BUA010: Addresses

77 Address: Street 2 H H H H

BUA010: Addresses


BUA010: Addresses


BUA010: Addresses

80 Address: Building Abbreviation O O O O

BUA010: Addresses

81 Address: Floor O O O O

BUA010: Addresses

82 Address: Room Number H H H H

BUA010: Addresses

83 Address: External Address No. H H H H

BUA010: Addresses


BUA010: Addresses

85 Address: Company Postal Code H H H H

BUA010: Addresses

86 Address: Remarks O O O O

BUA010: 89 Address: Time Zone H H H H

© SAP AG of 63



Description Use:

1 2 3 4

Addresses

BUA010: Addresses

92 Address: House Number O O O O

BUA010: Addresses

93 Location for Tax Calculation R R R R

BUA010: Addresses

94 Address: Regional Structure Group H H H H

BUA010: Addresses

95 Address: Other Communication Data (Pushbutton) D D D D

BUA010: Addresses

115 Address: Internet Mail Address O O O O

BUA010: Addresses

120 Address: Transport Zone H H H H

BUA010: Addresses

122 Address: Alternative Address H H H H

BUA010: Addresses

123 Address: P.O. Box Without Number H H H H

BUA010: Addresses

124 Address: Alternative Country H H H H

BUA010: Addresses

125 Address: Alternative Region H H H H

126 Address: Alternative Location H H H H

BUA010: Addresses

127 Address: Undeliverable to Street Address H H H H

BUA010: Addresses

128 Address: Undeliverable to P.O.Box Address H H H H

BUA010: Addresses

139 Address: Dependent -> Independent (Button) H H H H

BUA010: Addresses

140 Address-Indepndnt Comm.Data: Country for Telephone H H H H

BUA010: Addresses

141 Addr.-Indep. Communicn Data: Tel.,Area Code+ Conn. H H H H

BUA010: Addresses

142 Addr.-Indep. Communicn Data: Telephone, Extension H H H H

BUA010: Addresses

143 Addr.-Indep. Communicn Data: Country for Fax No. H H H H

BUA010: Addresses

144 Addr.-Indep. Communicn Data: Fax, Area Code+ Conn. H H H H

© SAP AG of 63



Description Use:

1 2 3 4

BUA010: Addresses

145 Addr.-Indep. Communicn Data: Fax No., Extension H H H H

BUA010: Addresses

146 Addr.-Indep. Communicn Data: Internet Mail Address H H H H

BUA010: Addresses

147 Address-Independent Communicn: Standard Comm. Type H H H H

BUA010: Addresses

148 Addr.Indep.Comm.Data: Other Comm. Data(Pushbutton) H H H H

BUA010: Addresses

149 Addr.-Indep.Comm. Data: Indep.-> Dependent(Button) H H H H

BUA010: Addresses

1350 BP Address: Time-Dependent Usages H H H H

BUA010: Addresses

2463 Address: Mobile Telephone O O O O

BUA010: Addresses

2464 Address-Indep.Communication Data: Mobile Telephone H H H H

BUA010: Addresses

2465 Addr.-Indep. Comm. Data: Country for Mobile Phone H H H H

BUP010: Central Data

3 Partner Type R R R R


5 Search Terms O O O O


8 Form of Address


12 Authorization Group O O O O


16 External Partner Number H H H H


17 Salutation H H H H


18 Data Origin Type H H H H


19 Language H H H H


23 Business Activity H H H H


24 Person: Other Last Name H H H H

BUP010: 25 Person: First name, Last Name R R R R

© SAP AG of 63



Description Use:

1 2 3 4

Central Data


26 Person: Academic Title O O O O


27 Person: Name Affix (e.g.Title of Nobility) H H H H


28 Person: Name Affix H H H H


29 Person: Correspondence Language H H H H


30 Person: Complete Name Line H H H H


31 Person: Date/Place of Birth H H H H


33 Person: Gender H H H H


34 Person: Nationality H H H H


35 Person: Marital Status H H H H


36 Person: Occupation/Group H H H H


37 Person: Employer O O O O


38 Person: Birth Name H H H H


39 Person: Death Date H H H H


40 Person: First Name O O O O


41 Person: 2nd First Name / Middle Name H H H H


42 Person: Country of Origin H H H H


43 Person: Initials of Person H H H H


44 person: Name Formatting N N N N


45 Organization: Name 1 H O H O

© SAP AG of 63



Description Use:

1 2 3 4


46 Organization: Name 2 H H H H


47 Organization: Name 3 + 4 H H H H


48 Organization: Legal Form O O O O


50 Organization: Legal Entity H H H H


51 Organization: Date Founded N N N N


52 Organization: Date of Liquidation N N N N


53 Organization: International Location Number H H H H


55 Group: Name H H H H


56 Group: Partner Group Type H H H H


90 Business Partner: Remarks O O O O


289 VIP Customer O O O O


290 Undesirable Customer N N N N


291 Deletion Data N N N N


292 Date of Death H H H H


380 Vendor: Sales Equalization Tax H H H H


391 FSCM: Biller Direct H H H H


1751 Partner Grouping N N N N

BUP020: Bank Details

9 Bank Details O O O O

BUP020: Bank Details

1344 Bank Chains (Pushbuttons) H H H H

BUP030: 20 Payment Cards H H H H

© SAP AG of 63



Description Use:

1 2 3 4

Payment Cards

BUP050: Identification

21 Identification Numbers O O O O

BUP160: Status

10 Central Block H H H H

BUP160: Status

11 Central Archiving Flag H H H H

BUP160: Status

137 Not Released O O O O

BUP160: Status

138 General Status: User Status H H H H

BUTX01: Tax Numbers

114 Numbers for Taxes and Reporting O O O O

FLVN00: General Vendor

Data

380 Vendor: Sales Equalization Tax H H H H

ISU010: ISU Data

400 IS-U: Contract account class O O O O

ISU010: ISU Data

410 IS-U: Employee classification H H H H

ISU010: ISU Data

411 IS-U: Driver's licence O O O O

ISU010: ISU Data

412 IS-U: work center H H H H

ISU010: ISU Data

413 IS-U: Social insurance O O O O

ISU010: ISU Data

414 IS-U: Driver's licence - country and region O O O O

ISU010: ISU Data

415 IS-U: Welfare office H H H H

ISU010: ISU Data

425 Category for alternate payee H H H H

ISU010: ISU Data

426 Bank details and payment method for payee H H H H

ISU010: ISU 427 G/L account for payee H H H H

© SAP AG of 63



Description Use:

1 2 3 4

Data

ISU010: ISU Data

447 IS-U: Release status for business partner data O O O O

ISU010: ISU Data

448 IS-U: Clerk determination ID H H H H

ISU010: ISU Data

449 IS-U: Classification H H H H

ISU010: ISU Data

450 VIP O O O O

R = Required

H = Hidden

D = Display

O = Optional

N = Not Specified

Configure Field Attributes per Activity

CREATE

CHANGE

DISPLAY: all three activities have the same values: the fields are indicated as “Not Specified”. The field grouping values defined at the role level will have the actual desired use established for the various fields.

Configure Field Attributes per Business Partner Type

0001: Standard BP Role

The field grouping values are all set to “Not Specified”.

Screen Configuration

Configure Screens

The screens have been configured or developed via the BDT: Business Data Toolset. Please refer to the documentation for using that tool for more information.

Authorization Management

Maintain Authorization Groups

SAP delivered value only: 0001: Basic Authorization Group

Maintain Authorization Types

Nothing Maintained

Define Field Groups Relevant to Authorizations

© SAP AG of 63


No entries maintained: to be determined during the Implementation

Generate and Assign Authorizations

This IMG activity takes you to role maintenance: part of the implementation process

Address Determination

Define Transactions

Only one entry provided by SAP:

ZZDFLT: Standards

Define Address Type

Addr. Type Short Name Name Several Issue

0001 Correspondence Address for Correspondence X

0002 Delivery Delivery Address

CON_OBJECT Object address Connection Object Address X

Assign Transaction to Address Type

Transaction: ZZDFLT is assigned to: CON_OBJECT

Forms of Address → Maintain Forms of Address

(Titles are not activated for the BP in the current settings)

Key Title Person/Org/Group Gender

01 Ms. P Female

02 Mr. P Male

03 Mrs. P Female

04 Company O Gender not known

05 Mr. and Mrs. G Gender not known

06 Dr. P/O Gender not known

07 Rev. P Gender not known

Data Origin → Maintain Data Origin Type

(Data Origin field is hidden in the current settings for the BP screens)

Origin Short Name Description

0001 Legacy data Legacy data transfer

0002 Purchased Purchased address dataset

0003 Legacy Data 2 Transf. of Legacy Data frm Legacy Syst.2

SAP maintained settings are displayed

© SAP AG of 63


Identification Numbers

Define Identification Categories

SAP delivered entries are maintained:

Identification Description Display Only

BUP001 Dun & Bradstreet Number (none are selected)

BUP002 Commercial Register Number

BUP003 Register of Associations Number

BUP004 Public Register of Cooperatives Number

FS0001 Identity card

FS0002 Passport

Define Identification Types

ID Type Description BP Category

BUP001 Dun & Bradstreet Number Organization

BUP002 Commercial Register Number Organization

BUP003 Register of Associations Number Organization and Groups

BUP004 Public Register of Cooperatives Number Organization and Groups

FS0001 Identity card Persons

FS0002 Passport Persons

Note that in the SAP delivered entries the ID Types match the ID Categories.

The ID Types can be proposed as the default value when inputting the identification information.

Tax Number Categories → Maintain Tax Number Categories

An entry specific to Germany was deleted: there are no values maintained.

Status Management → Define Status Profile for User Status

None are maintained for the template

Natural Persons

Name Components → Maintain Academic Titles

One title is maintained: Dr.

(Academic titles are currently not displayed in the Template settings)

Name Components → Maintain Name Affixes

No suffixes (or affixes) are maintained

Name Components → Maintain Name Prefixes

No prefixes are maintained

Name Components → Maintain Name Formatting Rules

© SAP AG of 63


US is maintained:

Title → First Name → Middle Initial → Last Name

Marital Statuses → Maintain Marital Status

SAP Standard Settings:

0 Single

1 Married

2 Separated

3 Divorced

4 Widowed

(This field is indicated as hidden, but the values are defined as a reference for future use).

Occupations → Maintain Occupations

No entries are maintained

Organizations

Organizations → Maintain Industry Solution Systems and Industries

No entries are maintained

Organizations → Maintain Legal Forms

Legal Form Description Short Name

01 Joint-Stock Company (corporation) Inc

02 Limited Liability Company Ltd

03 Partnership limited by shares LP

04 Limited partnership LP

06 General partnership OHG

These settings from SAP have been retained

Organizations → Maintain Legal Entity

None are maintained

Groups

Not defined for the Best Practice for Water Utilities

Extensibility

SAP Business Partner is designed to allow enhancements, because screen structure and screen sequences are defined in control tables. Program logic can be installed by using defined interfaces.

You can enhance the business partner by way of attributes, new tables and BP roles. You also have the option of enhancing the field checks delivered by SAP.

© SAP AG of 63


You can find further information about these enhancement options in the Developers' Manual for the Business Data Toolset (see Application Help -> SAP Business Partner (SAP BP) -> Business Data Toolset).

Business Partner Relationships

Basic Settings

Basic Settings → Define Number Ranges

01: 10000000 to 19999999

Basic Settings → Properties of Business Partner Relationship Categories

Rel. Category

Title Hide Name from BP 1 View Name from BP 2 View

BUR001 Contact Person Rel.ship Has Contact Person Is Contact Person For

BUR002 Activity Partner Has Activity Partner Is Activity Partner For

BUR003 Shared Living Arrangement

Has Shared Living Arrangement Members

Belongs to Shared Living Arrangement

BUR004 Marriage Is Married To

BUR006 Alias (Identity) Is Identical To

BUR010 Employee Relationship Has the Employee Is Employee of

BUR011 Responsible Employee Has the Employee Responsible

Is the Employee Responsible For

BUR013 Replacement Relationship

Is Replaced By Replaces

BURC01 Shareholder Relationship Is Shareholder Of Has Shareholder

FS0010 Customer - CS Rep.

(defined name: Major Account-CS Rep)

is represented as customer by

(defined name: Has major account rep)

Is Customer Service Rep. for Customer

(defined name: Is account rep for major account)

FSB002 Parent company/subsidiary

Is subsidiary of Is parent company of

Other settings provided by SAP were deleted using transactions from the Area Menus: BUPT and BUMR. That information follows the IMG settings described here.

The “names” displayed in the last two columns above can be replaced easily by customer names in the configuration settings.

The selection list of relationship types displays in alphabetical order by default. You do have the option of displaying in a customer defined sequence. We have maintained the default alphabetical list.

Basic Settings → Define Relationship Types

© SAP AG of 63


None defined: SAP provided relationship categories are not defined further into relationship types. If you have defined your own categories, you have the option to further distinguish the categories into types.

The template is using SAP delivered relationship categories

Field Groupings → Configure Field Attributes for Each Client

No entries maintained

Field Groupings → Configure Field Attributes for Each BP Relationship Category

All values set to Not Specified

Field Groupings → Configure Field Attributes for Each BP Role Definition Category


Field Groupings → Configure Field Attributes for Each Activity


Authorization Management → Define Field Groups Relevant to Authorizations

No entries are defined

Contact Person

Contact Person → Define Departments

SAP settings are maintained. To be defined on the implementation.

Contact Person → Define Functions


Contact Person → Define Powers of Attorney


Contact Person → Define VIP Indicator

Entries defined for the template:

M: Major Account

H: High Profile Account

B: Board Member

It is suggested that the utility company review how it distinguishes special customer groups if they use this indicator. To be defined on the implementation.

External Data Transfer

No changes to standard SAP settings

Data Cleansing

No changes made to standard SAP settings

Area Menu: BUPT: additional settingsTransaction Code: BUSI: Activities:

© SAP AG of 63


This transaction permits the company to alter SAP delivered settings for the message to be displayed in an authorization check.

SAP settings are maintained.

Transaction Code: BUS1: Applications:

SAP settings are maintained: no Template specific settings are made.

Transaction Code: BUS23: Data Sets

SAP defined settings are maintained: no Template specific settings are made

Transaction Code: BUSG: Tables

A list of the Business Partner Tables with technical details: function modules are defined

SAP delivered entries are maintained

Screen Layout: Transaction Codes:

BUS2: Field Groups:

BUS3: Views:

BUS4: Sections:

BUS5: Screens:

Transaction Code: BUS6: Screen Sequences: all of these transactions are part of the BDT (Business Data Toolset) used to combine fields in the sequence specified for the template for Business Partner and Contract Account.

Events

Transaction CodeBUS7: Business Data Toolset

Transaction Code: BUPA_EVENTS:

SAP delivered events for processing: no changes made

GUI Functions

Transaction Code: BUS8: Standard Functions

SAP settings are maintained

Transaction Code: BUS9: Additional Functions


Assign Database Field

Transaction Code BUSB: Screen Field → DB field


Transaction Code: BUSB_DI: Direct Input Field → DB Field


© SAP AG of 63


Field Grouping

Transaction Code: BUSC: Field Grouping Criteria


Transaction Code: BUSJ: Field Grouping per Activity:

Same as above in the IMG

Transaction Code: BUSO: Field Grouping per BP Category:

Same as above in the IMG

Transaction Code: BUSH: External Applications

New Interface

Transaction Code: BUS_HDRID: Header IDs


Divisibility

Transaction Code: BUSD: BP Roles

Role Description Update Procedure

Screen Selection

Valid BP Categories

BP # Field Selection

MKK Contract Partner Do not update

Not specified Person and Organization

None selected for hiding

BUP001 Contact Person Do not update

Do not display Person None selected for hiding

BUP003 Employee Do not update

Do not display Person None selected for hiding

ISUI Installer Do not update

Not specified Person and Organization

None selected for hiding

1. All data sets can be viewed per role.

2. The applications defined per role (the applications defined in a previous transaction)

3. Screen sequences can be viewed per role

4. Views are listed as a sub-set, but the maintenance can only be done via BP Roles Data Sets

5. Subheader IDs can be defined

Note: Changes made here are to hide BP roles that are not included in the template as described above.

Transaction Code: BUSE: BP Role Groupings

No values will be maintained for the template

Transaction Code: BUS10: Search Help


Transaction Code: BUSF: Application Transactions

© SAP AG of 63



Where-Used List

Business Partner:

Transaction Code: BUSWU01: Define Structure

Transaction Code: BUSWU02: Define Views

Transaction Code: BUSWU03: Assign Process to a View

Business Partner Addresses:


BP Bank Details:


BP Payment Cards:


SAP settings are maintained for all above from the “where-Used List”

Transaction Code: AOBJ: Archiving

Not maintained for the Template

© SAP AG of 63


Area Menu: BUMR: Relationships

Transaction Code: BUSM: Differentiation Categories


Transaction Code: BUSN: Activity Categories

SAP Settings are maintained

Transaction Code: BUS0: Applications, Objects


Transaction Code: BUBX: Activities


Transaction Code: BUBD: Applications


Screen Layout

Transaction Code: BUBN: Field Groups

Transaction Code: BUBE: Views

Transaction Code: BUBF: Sections

Transaction Code: BUBG: Screens

Transaction Code: BUBH: Screen Sequence: these transactions are part of the BDT: Business Data Toolset.

BUBI: Events


BUBM: Tables


GUI Functions

Transaction Code: BUBJ: Standard Functions

Transaction Code: BUBK: Additional Functions


Assign DB Field

Transaction Code: BUBL: Assignment of Screen Field DB Field

Transaction Code: BUBL_DI: Assignment of DI Field DB Field


Field Grouping

Transaction Code: BUBO: Criteria

Transaction Code: BUBY: Activity (Control)

© SAP AG of 63



External Interface

Transaction Code: BUBZ: External Applications

No values are maintained

Transaction Code: BUBA: Relationship Categories

Defined in the IMG and in the BDT.

Transaction Code: BUBB: Role Definition Categories


Customizing

Transaction Code: BUB9: Maintain Number Ranges

Defined in the IMG node.

Field Grouping

Transaction Code: BUBP: Relationship Categories

As above: from the IMG: all values have the setting: Not Specified

Transaction Code: BUBQ: Role Definition Categories

No entries defined

Transaction Code: BUBR: Activities

No entries defined

Transaction Code: BUBS_FRG: External Applications

No entries defined

Transaction Code: BUBU: Relationship Types

A node in the IMG: no entries maintained

Transaction Code: BUBT: Role Definition Types

A node in the IMG: no entries maintained

Contact Person

Transaction Code: BUR0: Department

Transaction Code: BUR1: Function

Transaction Code: BUR2: Power of Attorney

Transaction Code: BUR3: VIP ID

All above are described in the corresponding IMG activities above.

Marriage

Transaction Code: BUR4: Property Regime

SAP Settings are maintained: the values describe the distribution of property: NA for our Template

© SAP AG of 63


Creating the SD (Sales and Distribution) Reference Customer

Explanation: SAP maintains the Central Business Partner Concept where a single Business Partner can be maintained for the various roles he/she has within a company. However, there is no direct integration of the SAP Central Business Partner and the SD (Sales and Distribution) Customer.

The solution is to create an SD Reference Customer simultaneously when a CCS Business Partner is created.

Even where SD is not implemented, it is recommended that each Business Partner have the SD customer created for future use and as needed in the Work Management module.

Steps involved:

1. The essential part of the SD structure must be created:

SPRO → IMG → Enterprise Structure → Definition → Sales and Distribution → Define, copy, delete, check sales organization

2. Choose: Define Sales Organization: New Entries

For our purposes, the Sales Organization was created with the same key as the Company Code for the water company: 1000. An existing Sales Organization was copied and the American values were added:

Currency was defined as USD for US dollar.

The Sales Organizational Calendar was identified as: US.

3. Distribution Channel:

SPRO → IMG → Enterprise Structure → Definition → Sales and Distribution → Define, copy, delete, check Distribution Channel

A single Distribution Channel is defined: 01: Distribution Channel 01

4. Assign sales organization to company code

Enterprise Structure → Assignment → Sales and Distribution → Assign sales organization to company code

Company Code 1000 was allocated to Sales Organization 1000

5. Assign distribution channel to a sales organization

Enterprise Structure → Assignment → Sales and Distribution → Assign distribution channel to sales organization

Sales Organization 1000 was allocated to Distribution Channel 01

6. Assign division to sales organization

Enterprise Structure → Assignment → Sales and Distribution → Assign division to sales organization

Sales Organization 1000 was allocated to Divisions 10 and 20

7. Set Up Sales Area

Enterprise Structure → Assignment → Sales and Distribution → Set Up Sales Area

Sales Organization 1000 is allocated Distribution Channel 01 which is in turn allocated to Divisions 10 and 20.

8. Assign Sales Office to Sales Area

© SAP AG of 63


Enterprise Structure → Assignment → Sales and Distribution → Assign Sales Office to Sales Area

Sales Organization 1000 and Distribution Channel 01 are allocated to Divisions 10 and 20

9. Assign sales organization – distribution channel - plant

Enterprise Structure → Assignment → Sales and Distribution → Assign sales organization - distribution channel – plant

Sales Organization 1000 is allocated to Distribution Channel 01 and plant 1000

10. Define Common Distribution Channels

Sales and Distribution → Master Data → Define Common Distribution Channels

SOrg. DChl. Description Dch-Conds

Description Dch-Cust/Mt Description

1000 01 Distr. Channel 01

01 Distr. Channel 01

01 Distr. Channel 01

11. Define Common Divisions

Sales and Distribution → Master Data → Define Common Divisions

SOrg. Dv Description DivCon Description DivCust Description

1000 10 Water 10 Water 10 Water

1000 20 Wastewater 20 Wastewater 20 Wastewater

12. Creating the Reference Customer: the SD customer can be created for each company code: for the template, the SD Reference Customer is created for company code 1000 only.

13. The number range for object: CUSTOMER (use: SNUM and enter this object) must be set to XX for external number assignment when the SD customer is created. Afterwards, the number range for account group 0001/DEBI will be reset to an internal number assignment.

14. The goal is to have a corresponding SD customer created for every ISU Business Partner with the same number assigned.

Cross Application Components → SAP Business Partner → Basic Settings → Number Ranges and Groupings

Define Number Ranges:

Number range 01 is the standard internal number range to be used AFTER the SD Reference customer has been created.

Number range XX is the external number assignment used for the creation of the SD customer.

Define Groupings and Assign Number Ranges

The grouping 0001: Utility Customer # is assigned to number range 01 for all regular uses. This allocation must be changed to XX for the creation of the SD reference customer and then set back after the reference customer has been created.

15. Create Number Ranges for Customer Accounts

Financial Accounting Accounts Receivable and Payable Preparations for Creating Customer Master Data Create Number Ranges for Customer Accounts

Maintain the same number ranges as described above for Customer

© SAP AG of 63


16. Assign Number Ranges to Customer Account Groups

Financial Accounting Accounts Receivable and Payable Preparations for Creating Customer Master Data Assign Number Ranges to Customer Account Groups

Sold-To Party and DEBI are assigned to number range 01 except during the creation of the SD Reference Customer when they are temporarily assigned to number range: XX

17. Define Account Groups and Field Selection for Customers

Logistics General → Business Partner → Customers → Control → Define Account Groups and Field Selection for Customers

Access the record for 0001 (sold-to) and DEBI: both will need to set to an external number assignment temporarily for the creation of the SD Reference Customer and then have the number range reset to 01: internal number assignment.

Note: you may have to manipulate the number ranges: both must have the same starting point or status of the current number, or last assigned number.

18. After setting the number ranges to external, Create the Customer via transaction code: XD01: Create for Company Code (1000), Sales Organization (1000), Distribution Channel (01), and Division (10). Use the alpha-character name selected: MUSTXXX is a common convention.

Enter data as commonly done for a Business Partner and save.

Set the number range back to internal and the process is complete. This is a one-time process; it is done as a preliminary step and does not have to be repeated.

The reference customer is set as required in the creation process of the Business Partner and the value must be entered on the BP creation screen: it can be configured to default.

System configuration considerations / actions: CRMThe CCS system is the controlling system. This means that all Business Partners are created and maintained in CCS. The creation of new business partners and the maintenance of existing business partners are performed in CCS and then replicated to CRM.

As a result, many of the Business Partner configuration activities are not performed on the CRM side. IMG activities are almost identical to those already documented above.

One setting that must be made is the assignment of all Business Partner number ranges as external number assignments. This is because a number that is internally assigned in CCS must have the same number in CRM. This is accomplished by this combination of internal number assignment in CCS with the external number assignment in CRM.

System configuration considerations / actions: Non-CCSThe contract account is an object configured in Contract Accounts Receivable and Payable in the Financial Accounting node of the IMG.

SPRO → Reference IMG → Financial Accounting → Contract Accounts Receivable and Payable → Contract Accounts → Number Ranges and Contract Account Categories → Define Number Ranges


02: A to ZZZZZZZZZZZZ, external number assignment

Configure Contract Acct Categories and Assign Number Ranges

Application Area: R (utilities)

© SAP AG of 63


Contract Account Category: 01

Account Category Text: FI-CA Contract Account Category

Only One Business Partner Allowed: selected

Contract Account is a Collective Contract Account: not selected

Contract Account is a One-Time Account: not selected

Internal Number Range: 01

External Number Range: 02

Online Maintenance not Permitted: not selected

Only One Contract Permitted: not selected

Customer/Vendor: nothing selected

Field Modifications → Configure Field Attributes for Contract Account Category

For Contract Account Category: 01

Field Group Description Use

3 Account type Not Specified

5 Business partner address Not Specified

7 Validity date on data screens Not Specified

10 Account name (several BPs) Hide

12 Account number in legacy system (several BPs)

Not Specified

19 Account name (unique BP) Not Specified

20 Account Number in Legacy System (Unique BP)

Not Specified

21 Company Code Group Not Specified

22 Deletion flag Not Specified

23 Standard Company Code Not Specified

25 Alternative bill recipient Not Specified

26 Jurisdiction code Displayed

27 Withholding Tax Hide

28 Alternative contract account for collective bills

Hide

29 Jurisdiction code address Hide

30 Alternative dunning recipient Not Specified

31 Processing block Not Specified

32 Grouping keys for dunning notices

Not Specified

33 Dunning procedure Not Specified

34 Fiscal tax category (Argentina) Hide

© SAP AG of 63



35 Country supplied (for tax notifications)

Hide

40 Alternative Payer Hide

42 Bank details ID for incoming payments

Not Specified

43 Incoming Payment Method Not Specified

50 Alternative Payee Hide

52 Bank details ID for outgoing payments

Hide

55 Outgoing payment methods Not Specified

60 Contract Account: Remarks Not Specified

80 Tolerance Group Not Specified

90 Correspondence procedure Hide

91 Correspondence dunning procedure

Hide

100 Material requirements planning group

Hide

102

Relationship business partner to contract account

Hide

103 Additional days for cash management

Hide

104 Clearing category Not Specified

105 Reference number Hide

106 Authorization group Not Specified

107 Contract Account Used for Payment

Hide

108 Interest Key Not Specified

110 Own Bank Details Hide

111 UK Payment Reference Hide

120 Company ID Hide

130 Dunning block Not Specified

134 Incoming Payment Locks Not Specified

138 Outgoing Payment Locks Not Specified

139 Interest Lock Not Specified

140 Credit card number (incoming Hide

© SAP AG of 63



payment)

142 Credit card number (outgoing payment)

Hide

143 Clearing Restriction Not Specified

144 Posting block Not Specified

146 Billing Block Not Specified

147 Correspondence-dunning lock Hide

150 Alternative correspondence recipients

Hide

152 Alternative correspondence recipient (standard)

Hide

155 Tax Exemption (Argentina/Italy) Hide

170 Tax Category 1: Business Partner

Hide


Hide

198 Biller Direct: Event Control Hide

199 Biller Direct: Notification Type Hide

203 Indicator: standing order Hide

204 Indicator: no payment form Hide

205 Manual outsorting for invoicing Not Specified

206 No. of documents to be outsorted manually

Not Specified

207 Outsorting Check Group for Invoicing

Not Specified

210 Addit. bill to partner of account Not Specified

211 Currency Hide

212 Payment term Not Specified

213 Account class Not Specified

215 Account determination characteristic

Not Specified

216 Application form Not Specified

217 Language key Not Specified

221 Add. dunning Hide

222 Shipping control for alternate dunning recipient

Hide

223 Shipping control for alternate Not Specified

© SAP AG of 63



bill-to party

224 Business area Hide

225 Shipping control for business partner

Hide

226 Move-in/out dunning procedure Not Specified

230 Technical regional structure group

Hide

231 Business regional structure group

Hide

233 BB request for cash payment/direct debit

Hide

240 Indicator: billing procedure active

Hide

241 YAP participation Hide

242 Bill aggregator Hide

600 CIS show bankruptcy process Not Specified

Field Modifications → Configure Field Attributes per Activity

All three activities have the same settings as defined below:

Field Group Description Use:

3 Account type Not Specified

5 Business partner address Not Specified

7 Validity date on data screens Not Specified

10 Account name (several BPs) Not Specified

12 Account number in legacy system (several BPs)

Not Specified

19 Account name (unique BP) Not Specified

20 Account Number in Legacy System (Unique BP)

Not Specified

21 Company Code Group Required

22 Deletion flag Not Specified

23 Standard Company Code Not Specified

25 Alternative bill recipient Not Specified

26 Jurisdiction code Not Specified

27 Withholding Tax Not Specified

28 Alternative contract account for Not Specified

© SAP AG of 63


collective bills

29 Jurisdiction code address Not Specified

30 Alternative dunning recipient Not Specified

31 Processing block Not Specified

32 Grouping keys for dunning notices

Not Specified

33 Dunning procedure Required

34 Fiscal tax category (Argentina) Not Specified

35 Country supplied (for tax notifications)

Not Specified

40 Alternative Payer Not Specified

42 Bank details ID for incoming payments

Not Specified

43 Incoming Payment Method Not Specified

50 Alternative Payee Not Specified

52 Bank details ID for outgoing payments

Not Specified

55 Outgoing payment methods Not Specified

60 Contract Account: Remarks Not Specified

80 Tolerance Group Not Specified

90 Correspondence procedure Not Specified

91 Correspondence dunning procedure

Not Specified

100 Material requirements planning group

Not Specified

102

Relationship business partner to contract account

Not Specified

103 Additional days for cash management

Not Specified

104 Clearing category Not Specified

105 Reference number Not Specified

106 Authorization group Not Specified

107 Contract Account Used for Payment

Not Specified

108 Interest Key Not Specified

110 Own Bank Details Not Specified

111 UK Payment Reference Not Specified

120 Company ID Not Specified

© SAP AG of 63


130 Dunning block Not Specified

134 Incoming Payment Locks Not Specified

138 Outgoing Payment Locks Not Specified

139 Interest Lock Not Specified

140 Credit card number (incoming payment)

Not Specified

142 Credit card number (outgoing payment)

Not Specified

143 Clearing Restriction Hide

144 Posting block Not Specified

146 Billing Block Not Specified

147 Correspondence-dunning lock Not Specified

150 Alternative correspondence recipients

Not Specified

152 Alternative correspondence recipient (standard)

Not Specified

155 Tax Exemption (Argentina/Italy) Not Specified


Not Specified


Not Specified

198 Biller Direct: Event Control Not Specified

199 Biller Direct: Notification Type Not Specified

203 Indicator: standing order Not Specified

204 Indicator: no payment form Not Specified

205 Manual outsorting for invoicing Not Specified

206 No. of documents to be outsorted manually

Not Specified

207 Outsorting Check Group for Invoicing

Not Specified

210 Addit. bill to partner of account Not Specified

211 Currency Not Specified

212 Payment term Not Specified

213 Account class Not Specified

215 Account determination characteristic

Not Specified

216 Application form Not Specified

© SAP AG of 63


217 Language key Not Specified

221 Add. dunning Not Specified

222 Shipping control for alternate dunning recipient

Not Specified

223 Shipping control for alternate bill-to party

Not Specified

224 Business area Not Specified

225 Shipping control for business partner

Not Specified

226 Move-in/out dunning procedure Not Specified

230 Technical regional structure group

Not Specified

231 Business regional structure group

Not Specified

233 BB request for cash payment/direct debit

Not Specified

240 Indicator: billing procedure active

Not Specified

241 YAP participation Not Specified

242 Bill aggregator Not Specified

600 CIS show bankruptcy process Not Specified

Field Modifications → Define Field Groups for Authorization Check

No entries

Contract Account Relationships → Define Contract Account/Business Partner Relationships

Account Relationship: 01

Description: Account Holder

AH checkbox: selected: the single relationship defined is that of account holder.

Activate Additional Checks for Master Data Changes to Business Partner

BP Table: not activated

Check Dependencies of Business Partner Changes: activated

Spool Aggregation at Job Level Required: not activated

Note Functions → Define Note Types

No changes made to SAP delivered settings

Data Transfer

No changes made in any of the 4 IMG activities: standard SAP settings present

Archiving

© SAP AG of 63


No changes made to SAP delivered settings

Define Account Determination IDs for Contracts

Company Code

Division Account Determination ID

Text

1000 10 01 Residential

1000 10 02 Commercial

1000 10 03 Industrial

1000 10 04 Municipal

1000 10 05 Wholesale

100 10 06 Fire

2000 20 01 Residential

2000 20 02 Commercial

2000 20 03 Industrial

2000 20 04 Municipal

Define Account Determination IDs for Contract Accounts

Account Determination ID Text

01 Residential

02 Non-Residential

03 Muncipal

04 Fire

05 WholeSale

System configuration considerations / actions: CCS

SAP Utilities → Master Data → Business Master Data → Business Partner

The contract is the only object specifically configured and created in CCS; it results with the completion of a move-in.

The SAP system allows for fields to be hidden on the screens. Additionally, fields can be made required, optional or read only.

Business Partner:

Settings for Creating Standard Customers → Maintain Parameters for Creating Reference Customer in Standard System

Role Category: MKK (contract partner)

Naming Convention: MUST

© SAP AG of 63


System Action if Customer already exists: checkbox is selected

System action if Customer missing when required: checkbox is selected

Number Range: 03

Redundant Customer is required for business partner: not selected

Address Where-Used: CON_OBJECT

Ref. Customer: MUST_ALL (to be created in each client: master data)

Contract Partner → Define Account Categories

Key for Account Categories

Text:

1000 Residential

2000 Commercial

3000 Industrial

4000 Employee

5000 Municipal

6000 Hydrants

7000 Fire Service Only

8000 Major Account

Account Categories will be used most often at the contract account rather than the business partner but they are configured here (they can be entered at the Business Partner level or the Contract Account level, as we have done here)

Contract Partner → Define Agent ID

No values are established here.

Installer → Define Types of Installation Companies

10: Plumber

20: Builder

Installer → Define Work Fields of Installation Companies

SAP delivered settings:

01 Being processed

02 In planning/being processed

03 In planning

Installer → Define Installer License Types

SAP delivered settings:

01 Normal license

02 Temporary license

03 Special license

© SAP AG of 63


Installer → Define Installer Status

01 License submitted

02 License being processed

03 License distributed (installer is active checkbox is selected)

04 License being checked (installer is active checkbox is selected)

Installer → Define Primary Utility Company

No values are defined: the Utility using the Template could define their company here

Contract:

Define Number Ranges for Utility Contracts

Number Range 01: From: 3100000000 to 319999999, internal number assignment

Define Search Help for Utility Contracts

No changes made here

Define Tabs for Utility Contracts

Layout ZSAP: Best Practice for Water Utilities Contract Layout, was created with a single tab: Service Data (vs. the three standard tabs in layout SA).

The tab contains the field groups:

S0001: General Contract Data (contains: contract account number, text for contract, MID from legacy, etc)

S0010: Move-In and Move-Out Data

S0004: Billing Data (JI Indicator, manual outsort, etc.)

S0012: Account Assignment Data

S0008: Notes

After the tab has been defined, it is necessary to assign this as the default layout for the object:

SAP Utilities → Basic Settings/Enterprise Structure → Define Default Layout for Tabs

Application: ISUCONTRCT has layout ZSAP allocated. The contract has been reduced to a single tab for the Best Practice for Water Utilities.

Define Notes for Utility Contracts

No configuration done for this node.

Define Field Selection for Utility Contracts

Modifiable Field Field Name Use

Account determin. ID EVERD-KOFIZ REQ

Altern. start month EVERD-PYPLA HIDE

Alternative portion EVERD-PORTION INPUT

Assigned to prof. segment EVERD-COPAKONT HIDE

© SAP AG of 63



Authorization Group EVERD-BEGRU INPUT

BFamount credit EVERD-BFA_CRED_STAT HIDE

BMamount receivable EVERD-BFA_DEB_STAT HIDE

Bill manually EVERD-MANABR HIDE

Billing Lock EVERD-INVLOCKR INPUT

Billing block reas. EVERD-ABRSPERR INPUT

Business Area EVERD-GSBER HIDE

Business place EVERD-BUPLA HIDE

CO Acct Assignment EVERD-COKEY HIDE

Cancel. time unit EVERD-KUENPER HIDE

Cancellation Date EVERD-KUENDDAT HIDE

Cancellation Reason EVERD-CANCREASON_NEW HIDE

Cat. BBExtrapolation EVERD-EXTRAPOLWASTE HIDE

Contr.from leg.syst. EVERD-VREFER INPUT

Contract Class EVERD-CONTRACTCLASS HIDE

Contract invoiced EVERD-FAKTURIERT DISP

Cust.cont.conclusion EVERD-VABSCHLKND HIDE

Debtor BB request EVERD-ABSLANFO HIDE

Deletion indicator EVERD-LOEVM DISP

Description TE643T-TEXT50 INPUT

Dunning Procedure EVERD-MAHNV INPUT

End EVERD-VENDE HIDE

From EVERD-INVLOCKRVON HIDE

Invoicng Serv. prov. EVERD-INVOICING_PARTY HIDE

Joint Invoicing EVERD-GEMFAKT REQ

Jurisdiction Code EVERD-TXJCD DISP

MID from legSys. EVERD-EINZDAT_ALT INPUT

Manual OS in Billing EVERD-MANOUTSORT INPUT

Move-in/out dun prc EVERD-MAHNVUMZ INPUT

No BB amt adjustmt EVERD-ABSMNANP HIDE

No. canc. time units EVERD-KFRIST HIDE

No. outsortings EVERD-OUTCOUNT INPUT

No. ren. time units EVERD-VERLAENG HIDE

On-Site Bill. Group EVERD-OSB_GROUP HIDE

© SAP AG of 63



Outline Contract EVERD-OUCONT HIDE

Outsorting chk group EVERD-AUSGRUP INPUT

Overriding BB cycle EVERD-ABSZYK HIDE

PS start date EVERD-PS_STARTDAT HIDE

Payment Class EVERD-SERVPROV_PAY HIDE

Payment plan type EVERD-PYPLT HIDE

Personnel Number EVERD-PERSNR HIDE

Plant/company cons. EVERD-EIGENVERBR HIDE

Prepayment Contract EVERD-PPM_CONTRACT HIDE

Processing status EVERD-BSTATUS HIDE

Reason contr. change EVERD-SSWTCREASON INPUT

Reason for release EVERD-ABRFREIG INPUT

Reg. Struct. Grp. EVERD-REGIOGROUP HIDE

Renewal date EVERD-VBISDAT HIDE

Renewal time unit EVERD-VERPER HIDE

Rule group EVERD-RULEGR HIDE

SP reference no. EVERD-SRVPRVREF HIDE

Sales document VERD-SALESDOCUMENT HIDE

Sales employee VERD-SALESEMPLOYEE HIDE

Sales partners EVERD-SALESPARTNER HIDE

Service Provider EVERD-SERVICEID HIDE

Start EVERD-VBEGINN HIDE

Starting month EVERD-PYPLS HIDE

Stat. group for con. EVERD-STAGRUVER HIDE

Text TE770T-TEXT HIDE

Text TE191T-TEXT30 DISP



Text for contract EVERD-VBEZ INPUT

Time customer EVERD-VABSCHLKNDTI HIDE

To EVERD-INVLOCKRBIS HIDE

Utility cont.concl. EVERD-VABSCHLEVU HIDE

© SAP AG of 63


Define Processing Status

Not in use: SAP standard settings are displayed

Define Contract Classes

No values are defined.

Master Data Created for the TemplateThe Master Data objects needed for the Move-In reference documents will be created as part of the template.

The SD Reference Customer must be created as well as any master data for the SD component.

Reports

Most utilities require reports of active customers sorted by various criteria:

Town

Customer class or type

Amount of bills

Conversion Expectations

Conversion of the master data is one of the most important considerations in the migration process:

How will you merge accounts?

Do you convert inactive accounts/inactive properties?

How much data cleansing is needed for a good conversion process?

Much detail is needed to provide the mapping of legacy fields to SAP fields.

Forms

None

Interfaces

Not applicable.

Authorization and user roles

How will you manage security in this area? Describe high-level authorization requirements. Also, make sure the team is aware of system functions and get the process owners thinking about how to control access to systems and their data.

© SAP AG of 63


Organizational Structure

Requirements/Expectations/AssumptionsYour company’s organizational plan in SAP is a comprehensive and dynamic model of the organizational units in your company, including the HR structure.

In the typical organizational plan, you can see:

The organizational structure of the company

The individual positions and the reporting structure

The various job categories

The work centers where the tasks assigned to the jobs and positions are carried out.

Assumptions:

1. We have developed an organizational structure to support the assignment of the single CIC Profile designed and for the routing of the workflow tasks. An entire company is not modeled.

2. If the company already has R/3 Human Resources, the CCS implementation will have to work cooperatively with that department as they typically own the organizational structure.

General explanationsThe organizational plan comprises organizational units and all of their interrelationships.

Organizational Units represent logical business units in your company and can be structured to build a hierarchy that represents your company as a whole. They are designated to carry out a specified set of functions within the company.

The organizational plan can have any number of organizational unit levels.

The organizational plan contains positions that are linked to the organizational units. Positions can have one or more holders assigned to them, and holders can be assigned to more than one position. Positions are the individual employee assignments within a company.

Positions are specific to your company. Multiple positions may perform similar or identical job tasks. Each position typically represents one holder, but can include more than one. A position inherits the job’s tasks, but can have further tasks defined unique to that position.

Holders are responsible for particular tasks and are one of the following:

Users: someone with a SAP system user ID

Person: someone in your company without an SAP user ID

Only Users can be assigned to carry out workflow tasks.

Jobs are elements in the organizational structure that describe tasks. Jobs can occur in a number of different positions. Jobs are a general classification for a set of tasks and should not be confused with positions. A job can be held by any number of people in your company.

An example of a job may be a secretary within the company. A corresponding position would be Secretary for Marketing.

Tasks are individual activities performed in a company. An example: taking phone calls, responding to correspondence, etc. When you assign tasks to a position or job, you define the duties that must

© SAP AG of 63


be carried out by the holders of the position or job. Tasks can also be assigned to organizational units or work centers.

Explanation of functions and events1. The first step in creating an organizational structure is to create a root organizational unit. The

transaction code: PPOCE is used for the creation process, while PPOME is used for any changes or updates.

2. Create the additional organizational units needed: you are building the high level hierarchy representing your company.

3. Create the jobs: Organizational units and jobs can be created in any subsequent order, but both must exist prior to the creation of positions. Jobs may already be defined in the job index or can be created after the organizational unit has been created.

4. Create the positions after the appropriate jobs have been created in the job index.

5. Assign tasks once the positions and jobs are defined.

6. Holders are then assigned to the positions, not the jobs.

System configuration considerations / actionsThe Organizational Structure is master data, it is not created as part of an configuration activity.

Master Data Created for the TemplateAll elements of the organizational structure are master data.

Reports

The Easy Access Menu for Human Resources → Organizational Management → Info System → element of the organizational plan → contains a number of delivered reports for use with the Organizational Plan.

© SAP AG of 63


Available Screen Simplification Tools

GuiXTGuiXT allows you to simplify transactions in R/3 without having to modify them. You can hide screen elements that you do not need, or add elements such as checkboxes, pushbuttons, graphics, and documentation if this is beneficial to your system.

Features:

Customize R/3 transactions by changing screen elements and adding new elementso Set default values for input fieldso Suppress screen elements (fields, pushbuttons, frames, etc)o Change texts of screen elementso Add quick infoso Add imageo Rearrange fieldo Add pushbuttono Change entry fields to radiobutton groups

Flexible customizingo Changes are possible for all transactionso Not restricted to preconfigured customizing techniques (e.g. customizing tables for field

control, user or system parameters) Changing screen layout does not interfere with program logic

o No modifications of screens necessary Full R/3 functionality is always available

o Can be activated and deactivated on the fly

How it works:

For each R/3 screen, you define one or several layout variants (scripts) by using a simple scripting language

You store these scripts on your PC At run time, GuiXT merges the screen scripts with the R/3 standard screen layout

GuiXT for Best Practice for Water Utilities:

Can be used for master data transactions with one screen layout (installation, connection object, etc)

Instructions on how to use GuiXT can be delivered with the template

Note: Additional info can be found in SAPNet Alias “SAPGUI”

© SAP AG of 63


BDT (Business Data Toolset)The BDT is a central control tool for maintaining master data and simple transaction data. In addition to maintenance, it also supports maintenance with direct input and/or function modules

Features:

Screen and screen sequences can be configured by drag & drop using the Visual Configuration Tool (VCT)

Changes can be transported SAP standard configuration can be reactivated at any time Dialog parts can be Configuration options

o Sort fields in different order, even between screenso Merge screenso Change sequence of screenso Change frame title and screen title

How it works:

For applications build on BDT, screen configuration is possible The layout of the fields can be changed using VCT Changes can then be saved as configuration requests

BDT for Best Practice for Water Utilities:

Applicable for the following master datao Central Business Partnero Contract Account

Note: Additional information can be found in SAPNet Alias “Utilities” under Product Information > ISU-CCS > General > Cookbooks and Guidelines > Business Data Toolset – Developer’s Manual

© SAP AG of 63

01 customer service master data scen guide en us

Documents