IUT 210 Master Data and Basic Functions

IUT 210 Master Data and Basic Functions

IUT210Release 463 25.09.2003

DOCPROPERTY "Material" \* MERGEFORMAT

IUT 210 Master Data and Basic Functions0-1Copyright0-2Prerequisites0-3SAP Utilities (IS-U/CCS)0-4Target group0-5Course Goals0-6Course Objectives0-7Course Content0-8Introduction1-1Introduction: Unit Objectives1-2Introduction: 11-3mySAP.com: Overview1-4Strategy: from Integration to Cooperation1-5Workplace Internet Business Framework1-6The1-7Example of an Industry Solution: IS-Utilities1-8IS-U/CCS - Integration Model1-9Cross-Application Standards1-10Organizational Structure: Terminology1-11Organizational Structures: Levels1-12Introduction: 21-13Functional Scope of the IS-U/CCS System1-14IS-U/CCS - Overview1-15Divisions1-16Introduction: 31-17IS-U Data Model1-18The IS-U House1-19Introduction: 51-20Business Scenario (1)1-21Business Scenario (2)1-22Business Scenario: Process1-23Scenario1-24Introduction: Summary1-25Customizing2-1Customizing: Unit Objectives2-2Customizing: 12-3Business Processes: ASAP Method2-4Business Processes: Overview2-5Stages of the ASAP Roadmap2-6Example Phase 1: Definition of System Infrastructure2-7Overview of Tools2-8ASAP/SAP Reference Structure2-9SAP Reference IMG2-10Transfer Scope from Q&Adb to R/32-11Tools for R/3 Project Documentation2-12Customizing: 22-13Knowledge Base of the IMG2-14Implementation Guide IMG2-15Initializing the Implementation Guide (IMG)2-16Customer-Specific Configuration of the IMG2-17Create Project IMG Manually in R/32-18Edit Project2-19User Assignment2-20Activity Log2-21Customizing: 32-22Business Procedures: Implementation Guide (IMG)2-23Examples of Customizing2-24Business Processes: ASAP Method2-25Customizing: Summary2-26Customizing Exercises2-27Solutions2-28Regional Structure3-1Regional Structure: Unit Objectives3-2Regional Structure: Business Scenario3-3Regional Structure: 13-4Postal Regional Structure (City File)3-5Elements of the Postal Regional Structure3-6Regional Structure: Address Check (1)3-7Regional Structure: Address Check (2)3-8Linking Own Data to the Regional Structure3-9Customizing: Postal Regional Structure (I)3-10Customizing: Postal Regional Structure (II)3-11Regional Structure: 23-12Political regional structure3-13Maintaining Political Hierarchy3-14Regional Structure: 33-15Company regional structure3-16Regional Structure Areas3-17Plant Determination: Plant Maintenance3-18Regional Structure: 43-19Regional Structures (1)3-20Regional Structures (2)3-21Regional Structure: Unit Summary3-22Regional Structures Exercises3-23Regional Structures: Solutions3-26Scheduling: Contents4-1Scheduling: Unit Objectives4-2Scheduling: Business Scenario4-3Scheduling: I4-4Function4-5Purpose4-6Scheduling: II4-7Elements of Scheduling4-8Schedule Master Records: Portions4-9Billing Periods4-10Schedule Master Records: Meter Reading Units4-11Portions and Meter Reading Units4-12Parameter Record4-13Parameter Record, Portion and Meter Reading Unit4-14Budget Billing Cycle/Budget Billing Frequency4-15Scheduling: III4-16Generation of Schedule Records4-17Scheduling: Annual Billing4-18Scheduling: Monthly Billing4-19Period Length with Specified Number of Days4-20Taking into Account the Factory Calendar4-21Scheduling: IV4-22Dynamic Scheduling4-23Dynamic Scheduling: Usage4-24Customizing4-25Example4-26Result4-27Manual Changes4-28Scheduling: Unit Summary4-29Scheduling: Exercises4-30Scheduling: Solutions4-33Technical Master Data5-1Technical Master Data: Unit Objectives5-2Technical Master Data: Business Scenario5-3Technical Master Data: 15-4Data Model and Integration with Logistics5-5Integration with Logistics (1)5-6Integration with Logistics (2)5-7Technical Master Data: 25-8Connection Object (1)5-9Connection Object (2)5-10Static Notes to Field Service5-11Dynamic Notes to Field Service5-12Maintenance Plant5-13Service Connection (1)5-14Service Connection (2)5-15Service Connections and Plant Maintenance5-16Service Connections: Business Processes5-17The Service Connection Process5-18Technical Master Data: 35-19Premise (1)5-20Premise: 25-21Owner Allocation in Customizing5-22Allocation of Owners to Premises5-23Owner Allocation5-24Technical Installation5-25Device Location: 15-26Device Location: 25-27Location of Device Location5-28Technical Master Data: 45-29Central Data Object: Installation5-30Utility Installation: 15-31Utility Installation: 25-32The Utility Installation5-33Installation: Billing5-34Display of Billing View5-35Time Slices: Time-Based Data5-36Installation History5-37Installation: Allocation of Load Profiles5-38Control of Billing/Meter Reading5-39Other Functions5-40Technical Master Data: 55-41Devices5-42Device Data5-43Device Info Record5-44Device Installation5-45Device Installation: Device Information Record5-46Installation Structure5-47Technical Master Data: 65-48Facts5-49Individual Installation Facts5-50Fact Hierarchy5-51Reference Values5-52Reference Values: Data Relevant to Billing5-53Technical Master Data: 75-54Point of Delivery (PoD) Definitions5-55Point of Delivery5-56Communication Types5-57Technical Master Data: 85-58The Deregulated Market: Technical View5-59The Deregulated Market: Business View5-60Ways of Modeling Business Relationships5-61Deregulation in the IS-U Data Model (1)5-62Deregulation in the IS-U Data Model (2)5-63Installation Data5-64Contract Data5-65Examples of Services5-66Point of Delivery Service in the Data Model5-67Services and Contracts5-68Service Determination5-69Automated Business Processes5-70Technical Master Data: Unit Summary5-71Technical Master Data Exercises5-72Technical Master Data Solutions5-82Business Master Data6-1Business Master Data: Unit Objectives6-2Business Master Daten: Business Scenario6-3Business Master Data: 16-4The SAP Business Partner6-5The SAP Business Partner Concept6-6SAP Business Partner6-7SAP Business Partner: The Core of SAP Solutions6-8Definition of the SAP Partner6-9SD Customer & SAP Business Partner6-10Business Partner Data6-11Business Partner Address6-12Addresses6-13Address Categories6-14Modeling Business Partner Relationships6-15Business Partner Relationships6-16Relationship Categories6-17Relationships6-18Business Master Data: 26-19SAP Business Partner Role Concept6-20Business Partner Role: Definition6-21Business Partner Roles6-22Business Partner Role: Definition (1)6-23Business Master Data: 36-24Layer model6-25Screen Structure6-26Levels of Detail - From Screen to Field6-27Customizing the Screen Structure6-28Customizing the Screen Sequence6-29Configure Screen Structure and Sequence6-30Configuring the Screen Structure/Sequence in R/36-31Field Modifications in Customizing6-32SAP Business Partner: Customizing6-33Business Master Data: 46-34Contract Account6-35Contract Account & Business Partner6-36Elements of the Customer Profile6-37Contract Account Data6-38Contract Account Categories6-39Business Master Data: 56-40Contract Account: General Data6-41Incoming Payment: Tolerance6-42Multiple Contract Accounts: Collective Payment6-43Interest Key6-44Collective Bill6-45Collective Billing: Invoicing6-46Terms of Payment6-47Account Class6-48Settlement Category6-49Account Determination6-50Account Determination: Receivables Account6-51Account Determination: Revenue Account6-52Budget billing procedures6-53Statistical Procedure vs. Debit Entry Procedure6-54Payment Plan Procedures: AMB/BBP6-55AMB vs. BBP Procedures6-56Business Master Data: 66-57Contract Account: Dunning and Payment Data6-58Dispatch Control6-59Blocking and Outsorting6-60Dunning Procedure6-61Main Company Code6-62Business Master Data: 76-63Field Modifications in the IMG6-64Future Changes6-65Business Master Data: 86-66Contract: 16-67Contract: 26-68Contract Categories6-69Contract Data6-70Joint Invoice6-71Joint Invoicing: Example 16-72Joint Invoicing: Example 26-73Business Master Data: Unit Summary6-74Business Master Data: Exercises6-75Solutions6-80Move-In7-1Move-In: Unit Objectives7-2Move-In: Business Scenario7-3Process Diagram7-4Simplified IS-U Data Model7-5Move-In: Overview7-6The Move-In Process7-7Allocation of Contract to Installation7-8Move-In: Summary7-9Move-IN Exercises7-10Move-In Solutions7-12Agent Determination8-1Agent Determination: Unit Objectives8-2Agent Determination: Business Scenario8-3Agent Determination: 18-4Agent Determination8-5Agent Determination: Basics8-6Enterprise Organization8-7Organizational Management8-8Organizational Model: Human Resources8-9Creation of an Organizational Plan8-10Position8-11Agent Determination: 28-12Tasks - Definition: 18-13Tasks - Definition: 28-14Single-Step Tasks8-15Task Profile8-16Task Profile and Organizational Plan: 18-17Task Profile and Organizational Plan: 28-18Task Profile and Organizational Plan: 38-19Task Profile and Organizational Plan: 48-20Roles8-21Actual Agent8-22Agent Determination: Standard Role - Role Categories8-23Role Categories8-24Responsibilities8-25Priorities8-26Tasks, Roles and Responsibilities8-27Role Example: Posting Agent8-28Agent Determination: 38-29Agent Determination: Overview8-30Agent Determination Process8-31Link to Regional Structure Group8-32Agent Determination: Summary8-33Agent Determination: Exercises8-34Agent Determination: Solutions8-41Summary9-1IS-U/CCS - Integration Model9-2IS-U Data Model9-3The IS-U House9-4Summary: 19-5Regional Structures (1)9-6Parameter Record, Portion and Meter Reading Unit9-7Generation of Schedule Records9-8Enterprise Organization9-9Agent Determination Process9-10Summary: 29-11Data Model and Integration with Logistics9-12The Utility Installation9-13Different Types of Business Partner9-14Contract Account & Business Partner9-15Contract9-16The Move-In Process9-17

0 TC "IUT 210 Master Data and Basic Functions" \l 1 \* MERGEFORMAT System R/3

Release 4.63 / IS-Utilities/Customer Care Service

August 2001

5004 4890

0.2 TC "Copyright" \l 2 \* MERGEFORMAT Microsoft , Windows , NT , PowerPoint , WinWord , Excel , Project , SQL-Server , Multimedia Viewer , Video for Windows , Internet Explorer , NetShow , and HTML Help are registered trademarks of Microsoft Corporation.

Lotus ScreenCam is a registered trademark of Lotus Development Corporation.

Vivo and VivoActive are registered trademarks of RealNetworks, Inc.

ARIS Toolset is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrcken

Adobe and Acrobat are registered trademarks of Adobe Systems Inc.

TouchSend Index is a registered trademark of TouchSend Corporation.

Visio is a registered trademark of Visio Corporation.

IBM , OS/2 , DB2/6000 and AIX are a registered trademark of IBM Corporation.

Indeo is a registered trademark of Intel Corporation.

Netscape Navigator , and Netscape Communicator are registered trademarks of Netscape Communications, Inc.

OSF/Motif is a registered trademark of Open Software Foundation.

ORACLE is a registered trademark of ORACLE Corporation, California, USA.

INFORMIX -OnLine for SAP is a registered trademark of Informix Software Incorporated.

UNIX and X/Open are registered trademarks of SCO Santa Cruz Operation.

ADABAS is a registered trademark of Software AG

The following are trademarks or registered trademarks of SAP AG; ABAP/4, InterSAP, RIVA, R/2, R/3, R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript, SAPtime, SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow, and ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names included herein are also trademarks or registered trademarks of SAP AG.

Other products, services, logos, or brand names included herein are trademarks or registered trademarks of their respective owners.

0.3 TC "Prerequisites" \l 3 \* MERGEFORMAT 0.4 TC "SAP Utilities (IS-U/CCS)" \l 3 \* MERGEFORMAT 0.5 TC "Target group" \l 3 \* MERGEFORMAT 0.6 TC "Course Goals" \l 3 \* MERGEFORMAT 0.7 TC "Course Objectives" \l 3 \* MERGEFORMAT 0.8 TC "Course Content" \l 3 \* MERGEFORMAT 1 TC "Introduction" \l 2 \* MERGEFORMAT 1.2 TC "Introduction: Unit Objectives" \l 3 \* MERGEFORMAT The term 'basic functions' refers to creating and maintaining portions and schedules (for billing and meter reading) as well as the regional structure.

The term 'master data' comprises, on the one hand, business master data (such as business partner, contract account, and contract) and, on the other, technical master data (such as the connection object, device location, and premise).

1.3 TC "Introduction: 1" \l 3 \* MERGEFORMAT The IS-U/CCS component is integrated into the SAP standard system. This means that standard functions also exist in IS-U/CCS.

1.4 TC "mySAP.com: Overview" \l 3 \* MERGEFORMAT The mySAP.com concept is composed of three areas:

The my area stands for simple access to all elements of mySAP.com. Using the results of the EnjoySAP initiative, the mySAP.com workplace provides personalized role-based system access.

The SAP area stands for the provision of business software via the Internet.

The .com area stands for SAP's Internet initiative. Business collaboration and relationships can be initiated and enhanced via the Internet.

1.5 TC "Strategy: from Integration to Cooperation" \l 3 \* MERGEFORMAT Integration in the old economy means the integration of business processes.

Enterprise Resource Planning (ERP) made SAP R/3 the worldwide standard.

Since 1996 R/3 has been E-commerce-compatible.

Advanced business technology has been integrated in the SAP products to ensure that customers are fully prepared fir future developments and do have to apply changes to their systems.

Integration in the new economy requires the integration of processes across companies.

Cooperation

More than just working together

Processes involving many users can be executed in just one step

1.6 TC "Workplace Internet Business Framework" \l 3 \* MERGEFORMAT The workplace contains links to information both within and outside of the company boundaries. You can link to:

Non-mySAP.com components and external systems via open Internet standards

mySAP.com components: standard and new web-based R/3 transactions (R/3 standard system, New Dimensions, industry solutions), reports, (such as Business Information Warehouse Reports in BW 2.0a), Knowledge Warehouse contents

mySAP.com internet services: mySAP.com Marketplace

Any other Internet or Intranet sites

1.7 TC "The "Add On" and Integration Principle" \l 3 \* MERGEFORMAT The diagram shows the positioning of the industry solution as an add-on application to the core applications. This shows the application view (not the technical view), into which the solution is integrated in the core applications.

1.8 TC "Example of an Industry Solution: IS-Utilities" \l 3 \* MERGEFORMAT The industry-specific R/3 component IS-U (Industry Solution for Utilities) was specially developed for use in the energy and utility industries. IS-U supports all aspects of business partner management and billing of deliveries and services. It maps integrated work and information flows in the utilities area.

Materials Managment is, for example, linked completely with device management in IS-U, to map ordering and warehouse management.

Billing takes into account all the billing-related needs of the utilities and waste disposal industries. Price determination takes place automatically. Sales revenue is posted automatically in financial accounting.

There is a direct link from IS-U to Cost Accounting for analysis of costs and sales revenue. Cost centers and/or orders can be automatically posted from IS-U, and costs and sales revenue can be compared in profitability analysis.

1.9 TC "IS-U/CCS - Integration Model" \l 3 \* MERGEFORMAT The cross-industry component for contract accounts receivable and payable (FI-CA) is designed for processing a large volume of postings from sales and collection activities for a large number of customers.

Additional industry-specific development for the utilities industry enable the use of the SAP standard components Plant Maintenance (PM) and Customer Service (CS)- formerly service management. This provides an optimal environment for managing service transactions. PM/CM is integrated with the following components:

SD: management of customer quotations and orders, and also execution of billing

CO: allocation and settlement of costs related to service activities

MM: processing of material requirements and goods movements related to service activities

The Asset Management (AM) component supports the management of fixed assets.

Bills for services can be transferred to the IS-U invoicing component. Additional processing on the debit side is handled by the Contract Accounts Receivable and Payable component (FI-CA).

The Materials Management component (MM) creates material master records parallel to the device categories created in IS-U. The purchase and stockholding of devices is also managed using MM.

1.10 TC "Cross-Application Standards" \l 3 \* MERGEFORMAT The integration of the standard software means that manual reconciliation of data tables from system to system is not necessary.

Workflows consist of a sequence of tasks that are processed by human agents or mechanical processing units. The flow of these tasks from one step to the next is administrated by the workflow functions. This ensures the efficient and complete execution of tasks. Agent determination is based on SAP Business Workflow functionality.

Since the scope of SAP functionality is very broad, it can complete transactions throughout the life cycle of data. For example, the system provides transactions to create a record of a piece of equipment, track its life cycle, and retire that piece of equipment from service.

1.11 TC "Organizational Structure: Terminology" \l 3 \* MERGEFORMAT The structure of a company is mapped to the SAP applications in organizational units. Certain company functions are summarized in organizational units.

Organizational units can belong to a single application (for example, a sales organization can belong to Sales and Distribution) or be allocated to several applications (for example, a plant is allocated to the Materials Management and Production Planning applications).

1.12 TC "Organizational Structures: Levels" \l 3 \* MERGEFORMAT The client is the highest-level element of all the organizational units. It corresponds to a corporation with several affiliates. All the business data of an SAP installation can be distinguished by client, if not also by lower-level organizational structures.

Example:

A company code is an independent accounting unit, such as a legally independent company. It is the central organizational element of financial accounting.

The controlling area is the business organizational unit in which cost accounting is carried out. Controlling area and company code generally have a 1:1 relationship. You can carry out cross-company code cost accounting by having a controlling area perform a joint cost accounting for several company codes of a company.

For Sales and Distribution, the sales organization is the central organizational unit, using which sales requirements can be controlled. The distribution channel is the element that describes how goods and services reach the customer.

In production planning and controlling, the plant is the central organizational unit. A plant is a production location, or a summary of neighboring locations with material stock, called storage locations.

A storage location is a spatial unit. Within a plant, material stocks can be managed by storage location (inventory management).

1.13 TC "Introduction: 2" \l 3 \* MERGEFORMAT 1.14 TC "Functional Scope of the IS-U/CCS System" \l 3 \* MERGEFORMAT IS-U/CCS stands for "Industry Solution Utilities - Customer Care & Service".

IS-U/CCS is a business-process-oriented sales and information system for all types of utilities and services offered by a utility company, waste disposal company and service company.

The core IS-U/CCS application is a consumption billing system that valuates both measured and flat-rate consumption and services. Services are billed and invoiced using the standard component Sales and Distribution (SD).

Additional typical uses include:

Administration and change service to ensure correct consumption billing

Transparent and optimized planning, execution of maintenance tasks, and status tracking for technical field service

Work management functionality to enable services to be carried out efficiently through the use of work orders.

1.15 TC "IS-U/CCS - Overview" \l 3 \* MERGEFORMAT IS-U/CCSCan be used in all market segments of utility companies

Can be used to manage and bill:

Residential customers

Nonresidential customers

Service customers

Prospects (potential customers)

IS-U/CCS is suitable for private and public companies of all sizes and types, such as:

Holdings with independent subsidiaries

Service companies that provide customer service on behalf of utility companies

Cooperation between utility companies resulting from deregulation

Utility companies diversifying into new business areas (such as waste disposal or energy trade)

1.16 TC "Divisions" \l 3 \* MERGEFORMAT In addition to the most common divisions, the following can be billed using the Sales and Distribution (SD) component: service orders, service contracts and sale of goods.

Divisions and services can also be processed by several utility companies. This includes cases where there are several partners and one company provides certain services for the other partners (such as joint invoicing of services on one bill).

1.17 TC "Introduction: 3" \l 3 \* MERGEFORMAT 1.18 TC "IS-U Data Model" \l 3 \* MERGEFORMAT The customer is the center of focus in the data model (SAP business partner model).

Several contract accounts can be managed for each customer; these contract accounts can also contain several billable contracts.

Each contract is allocated to a company code and a division.

The contract account can include contracts that have different company codes. Payments are handled via the leading company code, which is indicated in the contract account.

Central address management creates a link to the regional structure, which breaks down the service territory into cities, streets and street sections.

Political and company regional structures can also be defined via a link to the postal regional structure.

The connection object is linked to the regional structure by the address. A connection object can contain several premises, device locations, and connections.

The device is technically allocated to the connection object via the device location. Devices and registers are allocated to the customers via their contracts and installations for billing purposes. The installation can also be considered the division-based subdivision of the premise.

1.19 TC "The IS-U House" \l 3 \* MERGEFORMAT IS-U/CCS requires the following master data:Connection object: The link between the installation to be billed and the postal regional structure. It is usually a building, although it can also be another property, such as a piece of land or a contruction site. Premise: A spatially enclosed unit, such as an apartment or a shop floor, that is to be supplied by a utility company.Device location: Location in a connection object where devices are installed. Installation: A division-specific collection of devices, registers, and flat-rate billing values that are assigned to the same premise and are billed together. One premise can have several installations belonging to one or more divisions. SAP business partner: Person or organization doing business with a utility company. The SAP business partner must be created in the role of the contract partner.Contract: An agreement between a utility company and one of its business partners, that relates to a specific division. The contract contains control data for billing, creation of budget billing plans, and Contract Accounts Receivable and Payable accounting. Contracts for services, such as maintenance contracts, are managed by the Sales and Distribution (SD) component.Contract account: Postings to contracts or contract items with the same collection/disbursement stipulations are billed to the contract account. Contract accounts are subject to open items accounting as part of contract accounts receivable and payable (FI-CA).Service connection (optional): Technical interface to the utility company's grid.

1.20 TC "Introduction: 5" \l 3 \* MERGEFORMAT 1.21 TC "Business Scenario (1)" \l 3 \* MERGEFORMAT During this training course, we will use typical utility business processes to illustrate IS-U/CCS functions. These business scenarios will show you step by step how to model your data as master data in the system and how to customize the basic functions according to the specific requirements of your company.

In our example, the service territory of a utility company is to be extended. First of all the responsible agents integrate the new service territory into the existing regional structure and plan schedules for meter reading and billing in the new territory. Before they can process the move-ins for the new customers, they must first maintain the technical and business master data for the new business partners.

Device installation is not an integral part of the subsequent move-in processing. However, it will be briefly addressed during this course.

1.22 TC "Business Scenario (2)" \l 3 \* MERGEFORMAT In order to complete the business process Move-in of new customer, you must perform the above steps. At least one contract account must be allocated to each contract partner. The contract account may have one or more contracts. This business master data is linked to the technical master data in move-in processing.

1.23 TC "Business Scenario: Process" \l 3 \* MERGEFORMAT The business process scenario is partly predefined. To create an installation in a connection object, for example, a premise must be predefined.

1.24 TC "Scenario" \l 3 \* MERGEFORMAT Two business partners live in one connection object. Each business partner has their own apartment (that is, their own premise). Each premise has a device location. In the device location of the first-floor apartment, an electricity meter for the consumption of the first-floor apartment has been installed. It also contains a water meter for the shared consumption of both apartments and an electricity meter for shared electricity consumption in areas of the house outside the two apartments. The device location of the second-floor apartment only contains an electricity meter for consumption in that apartment. The shared consumption (water meter W1 and electricity meter E2) is billed to business partner 1. Contract account 1 includes the contracts for shared consumption, and the private electricity contract of business partner 1.

You will create the following data objects in the exercises for this course: Regional structure: City, street and street section Scheduling: Schedule records for portion and meter reading unitMaster data:1 connection object with 2 premises (apartments)

3 installations for electricity and 1 installation for water

2 business partners (owner/residential customer, residential customer)

2 contract accounts

3 electricity contracts and 1 water contract

1.25 TC "Introduction: Summary" \l 3 \* MERGEFORMAT 2 TC "Customizing" \l 2 \* MERGEFORMAT One of the most important steps involved in implementing IS-U/CCS is Customizing, which enables you to configure the system in accordance with your company's needs. The IMG (Implementation Guide) helps you to do this efficiently and enables you to monitor and document the implementation project.

2.2 TC "Customizing: Unit Objectives" \l 3 \* MERGEFORMAT 2.3 TC "Customizing: 1" \l 3 \* MERGEFORMAT 2.4 TC "Business Processes: ASAP Method" \l 3 \* MERGEFORMAT Phase 1: Project preparation - The main focus points of phase 1 are the start of the project, the setting up of the project team and the development of a plan.

Phase 2: Business Blueprint - The main focus point of phase 2 is to clarify the company's business objectives and to determine the business management requirements necessary to fulfill these objectives.

Phase 3: Realization - The aim of this phase is to realize all business management and process-related requirements on the basis of the Business Blueprint. Adjust the system step for step in two work packages: Baseline configuration and final configuration.

Phase 4: Final preparation - The aim of this phase is to complete the tests, end-user training, system management and cutover activities. All important unresolved questions are clarified in this Final Preparation phase. After successful completion of this phase, you can carry out your company operations based on the productive R/3 System.

Phase 5: Go-Live & Support - Transition from a project-oriented, preproductive environment to a succesful, productive operation.

2.5 TC "Business Processes: Overview" \l 3 \* MERGEFORMAT The ASAP roadmap conveys knowledge on how to organize and run an R/3 implementation. It represents a "step-by-step" method of implementing the R/3 system.

AcceleratedSAP (ASAP) is the wide-ranging SAP implementation solution for optimizing R/3 projects. AcceleratedSAP optimizes time, quality and the use of resources. It integrates three components: the ASAP roadmap, tools, and R/3 service and training. Together, these components support the swift and efficient implementation of the R/3 system.

The AcceleratedSAP Roadmap provides a process-oriented, clear, and precise project plan that guides you step-by-step through your R/3 implementation. The ASAP roadmap consists of 5 phases: project preparation, business blueprint, realization, final preparation, go live & support, including constant optimization.

The tools include ASAP-specific tools for supporting product management, questionnaires for the business process consultants, as well as a number of technical guides and checklists.

R/3 service and training encompasses all the consultation, training and support services, such as hotlines, remote upgrades, or archiving. These products help you standardize certain activities in order to execute them as quickly as possible.

2.6 TC "Stages of the ASAP Roadmap" \l 3 \* MERGEFORMAT Phase 1: Project Preparation - Planning and preparation of the SAP project.

Phase 2: Business Blueprint - Creation of the Business Blueprint document. This is a detailed description of the results from the workshop held to determine the company's business process requirements. This document gives you a general overview of how the company would like to represent its business processes in the SAP System.

Phase 3: Realization - Configuration of the business and process requirements using the Business Blueprint in the SAP System. The system is configured in two work packages: Baseline configuration (main scope) and final configuration.

Phase 4: Final Preparation - Execution of tests and user training, system management and data transfer, in order to meet the prerequisites for productive operation. All important unresolved questions are clarified in this Final Preparation phase. After this phase has been successfully completed, you can carry out your company operations based on the productive SAP System.

Phase 5: Go Live & Support - Transition from a project-oriented, preproductive environment to a successful, productive operation.

2.7 TC "Example Phase 1: Definition of System Infrastructure" \l 3 \* MERGEFORMAT An infrastructure with three systems is the ideal solution for most customers:

Testing of developments is unrestricted.

Implementation of system upgrades is possible without restricting the productive operation.

Using a separate quality assurance system, it is possible to integrate developments and to check the consistency of objects that are to be transported, before they appear in the productive system.

This three-system solution supports the R/3 System landscape. The document R/3 System Infrastructure - System and Client Deployment Strategy was based on the following conceptions:

Development, quality assurance and productive operation all take place in separate data environments.

A client with consistent data can usually be restored if data is lost.

Transport systems for the set up and maintenance of the system infrastructure are predefined.

The infrastructure supports the import of existing business data from a legacy system.

2.8 TC "Overview of Tools" \l 3 \* MERGEFORMAT 2.9 TC "ASAP/SAP Reference Structure" \l 3 \* MERGEFORMAT In the Q&A database, the SAP reference structure is a graphical representation of the R/3 system. How to best map the R/3 system is an important topic for discussion for all the participants in an R/3 implementation project.

The SAP reference structure is a hierarchical structure containing all the elements required to create the business blueprint. It contains partial structures such as company areas, scenarios, process groups, and processes. In turn, elements such as questions, IMG activities, and organizational units are allocated to these structure elements.

The SAP reference structure supports you in identifying the specific requirements of your company and selecting the functions required to map these requirements in the SAP system.

Why use the SAP reference structure?

It is a simple way of getting to know the functions and processes of the R/3 system.

It minimizes the risk and effort behind the analysis of your requirements and the creation of a business blueprint.

In the R/3 system, the reference IMG is used as a structure for Customizing. It contains all the Customizing activities that must be performed in order to configure the R/3 system.

2.10 TC "SAP Reference IMG" \l 3 \* MERGEFORMAT The SAP Reference IMG contains the Customizing activities defined in the R/3 System.

2.11 TC "Transfer Scope from Q&Adb to R/3" \l 3 \* MERGEFORMAT During the Business Blueprint phase of the project, several detailed workshops take place, during which the project team define the general and detailed scope. This scope is stored in the Q&A database (Q&Adb). The Project IMG is generated based on the scope and is derived from ASAP. To transfer the Q&Adb to the R/3 System, proceed as follows:

Administration -> Transfer Scope Settings -> To R/3 System Only the project leader is authorized to transfer the scope of the Q&Adb.

A dialog box is displayed to verify that a network connection to the corresponding R/3 server is established. When the SAP Logon window appears, select the R/3 System. If the R/3 login data was maintained in the user profiles of the Q&Adb, the user data appears automatically in the next step. In case this was not done, enter the required data or choose the System tab page, which displays the data last used by the user. Then log on to the R/3 System. Enter the password. When you have entered the name of the Project IMG (step 2 above), the scope data of the Q&Adb is transferred to the R/3 System.

Generation of the Project IMG and views (automatically in background) can last several hours, according to the project scope. An R/3 message confirms the completion of the stack processing.

Both generated views consist of IMG activities with and without assignments in the IMG.

2.12 TC "Tools for R/3 Project Documentation" \l 3 \* MERGEFORMAT In the ASAP Roadmap documentation, SAP recommends which documentation tools can be used for which project activities.

The following tools are available for R/3 implementation:

Q&Adb including Issue Management System used for requirements analysis, problem documentation and for user and project documentation.

External modeling tools for graphical process modeling

IMG documentation of the Customizing settings:

Microsoft Word or SAPscript Editor are used to document the Customizing settings.

Forms are available for documentation in Microsoft Word.

Several documents can be created for each setting.

The documentation is:

Cross-client

Transportable

2.13 TC "Customizing: 2" \l 3 \* MERGEFORMAT 2.14 TC "Knowledge Base of the IMG" \l 3 \* MERGEFORMAT The IMG is a component-oriented structure of the R/3 Customizing settings.

The attributes of Customizing activities are:

Mandatory - required for the transaction to run

Optional - not required for the transaction to run

Not relevant - settings delivered by SAP that do not require customizing

Critical - the basic activities for the R/3 integration process

Not Critical - the activities that are independent of the important integration processes

Release reference - ability to view IMG activities specific to an R/3 release upgrade

Organizational reference - ability to view IMG activities specific to an organizational unit (such as plant and company code)

Countries - default settings that can be changed to be country-specific

2.15 TC "Implementation Guide IMG" \l 3 \* MERGEFORMAT The documentation structure is identical for all activities.

Implementation projects are planned in project management and their status determined.

Detailed documentation can be created for each IMG activity.

There is a translation function for language-dependent fields in Customizing transactions. You can select and change the language as required. The fields can be translated into several languages at one time.

2.16 TC "Initializing the Implementation Guide (IMG)" \l 3 \* MERGEFORMAT The purpose of this activity is to create a project IMG. Use project IMGs for your project planning and to control your Customizing. When you set up your project IMGs or release projects, ensure that you retain the standards defined in the process flows work package under the project documentation task for using status indicators, for scheduling and documentation.

The project IMG can be generated in two ways:

Manually. This is the more common method. The consultant chooses the IMG components for configuration in accordance with the scope of the project.

Automatically from the Q&A database. This is a new function that automatically transports the scope settings from the Q&A database to the R/3 project IMG. See also the accelerators named above.

2.17 TC "Customer-Specific Configuration of the IMG" \l 3 \* MERGEFORMAT For the realization, you can divide the scope of the Reference IMG into different projects, which in turn are assigned to Project IMGs.

Once the Project IMG is created, one or more views can be generated. You can specify in the views how you want to structure your Project IMGs. The following can be processed in the Project IMG: Customizing transactions, project-specific and cross-project documentation, and project management information. Do this for each view and/or all view combined.

From Release 4.6, it is possible to create views the IMG link. Use this function to transfer the project scope determined in the Q&Adb to the R/3 System. The views generated using the IMG link contain all the Customizing activities that are assigned to the processes set in the scope.

The IMG link does not generate Project IMGs. Project IMGs must first of all be generated in the R/3 System. The IMG link is used to generate and display processes with/without assignments or all views for a Project IMG.

2.18 TC "Create Project IMG Manually in R/3" \l 3 \* MERGEFORMAT You can specify the project scope in two ways in the Scope tab page:

By manually selecting the nodes in the Reference IMG

If you specify the project scope by selecting structure nodes, specify the structure of your Project IMG at the same time. The Customizing project only contains functions that you wish to implement.

By choosing application components and countries

You can assign whole activity areas in your Project IMG to certain countries by selecting application components and countries. The Customizing project contains all the Customizing activities that you need for an integrated system.

2.19 TC "Edit Project" \l 3 \* MERGEFORMAT The project team member makes the settings in the Customizing projects and documents the individual steps of the R/3 implemenetation, using status and note maintenance.

To do this, he/she performs project functions based on the projects contained in his/her worklist.

The system displays the data for the relevant view (if you insert the IMG link) or the (manually created) project for editing.

On the left hand side of the screen are the IMG and Customizing activities.

On the right hand side of the screen is the description for the selected Customizing activity. All the general project data (such as start date and anticipated end date) is displayed below, along with the team member's name and keywords that are allocated to this project. In the lower part of the screen are the types of documentation for the IMG project that are available for the documentation of Customizing activities.

2.20 TC "User Assignment" \l 3 \* MERGEFORMAT R/3 Customizing is based on two clearly defined user roles: Project team member and project leader. This structures and organizes R/3 implementation activities. Each role has specific areas of responsibility.

Customizing project team members make Customizing project system settings and document project progress.

Any number of project team members (R/3 users) can be assigned to each project. The project leader makes these assignments in project management.

The project leader can assign either one user, or all employees in the Project team members tab, to a project. The project then appears in the Customizing worklist of the assigned team members.

2.21 TC "Activity Log" \l 3 \* MERGEFORMAT The activity log (AL) records all changes that are made to an IMG activity. You are able to identify, for instance, who modified a specific Customizing parameter, and what the old value was. The AL ability to capture any alterations made to settings, makes it an optimal tool for investigating Customizing change history.

The CCSV allows detection of settings discrepancies between a BC Set and a system. The AL provides a change log of changes made to the settings.

Before you can use the Activity Log, you have to make certain it is activated properly in your system. Two switches need to be set for the tool to monitor Customizing changes:

The first switch is located at the table level - in the technical settings of a table in the Data Dictionary. This switch is preset by SAP, to monitor Customizing tables whose change history should be logged. With Release 4.6, 90 percent of Customizing tables are preset to log.

The second switch is located at system level. With the profile parameter rec/client, you can turn on table logging for a specific client or for the whole system. If you select a specific client, all Customizing that is made in this client and all client-independent Customizing is recorded. If table logging is turned on for the whole system, all Customizing changes in the system are traced.

The AL recognizes Customizing changes to the database interface. It is therefore impossible to change Customizing data without leaving a trace in the AL. Consequently, the activity log contains a complete history of all Customizing changes and is a perfect tool for auditing purposes.

2.22 TC "Customizing: 3" \l 3 \* MERGEFORMAT 2.23 TC "Business Procedures: Implementation Guide (IMG)" \l 3 \* MERGEFORMAT The IMG is a check list for the Customizing activities required for an SAP implementation project. The IMG is structured in a hierarchy.

The structure of the IMG and the IMG administration tools, such as resource management or MS project connection, enable the project team to process the Customizing activities according to a structure.

2.24 TC "Examples of Customizing" \l 3 \* MERGEFORMAT 2.25 TC "Business Processes: ASAP Method" \l 3 \* MERGEFORMAT 2.26 TC "Customizing: Summary" \l 3 \* MERGEFORMAT 2.27 Customizing Exercises TC "Customizing Exercises" \l 3 \* MERGEFORMAT

Unit: CustomizingTopic: Procedure Model and IMG

At the end of this exercise, you will be able to:

Display an IMG Project and use the search function.

Display the Customizing area of the IMG for IS-U.

Display the Customizing area of the IMG for FI-CA

As a member of the implementation project team, you would like an overview of the progress of the Master data subproject.

1-1Which views belong to the Master data project (210)? Choose Tools AcceleratedSAP Customizing Project Management1-2Where do you define premise types in Project 210?1-3What do you use voltage levels for?1-4Which employee is responsible for entering the voltage levels and which work status has been allocated to the transaction?

1-5Display the activities that make up the IS-U/CCS master data in the SAP Reference IMG. Which activities have corresponding release notes?

1-6Display the areas in which you can establish settings for the Contract Accounts Receivable & Payable (FI-CA) component in the SAP Reference IMG. 2.28 Solutions TC "Solutions" \l 3 \* MERGEFORMAT

Unit: CustomizingTopic: Procedure Model and IMG

1-1In the SAP menu, choose Tools AcceleratedSAP Customizing Project Management.Search for the Master Data project 210. Select the project and choose Display. To branch to the Project IMG, press the Project IMG pushbutton. To branch to the Project IMG, press the Project IMG pushbutton.

1-2 In the Project IMG, choose SAP Utilities Master Data Premise Define Premise Types.

If you do not know where the premise types are in the hierarchy, choose the Find pushbutton to search the node titles. Enter the search term and choose Continue.

To define the premise types, double-click on the IMG Activity icon for this line.

For information about a symbol, simply position the cursor over the symbol.

1-3 Choose SAP Utilities Master Data Utility Installation Define Voltage Levels.

Double-click on the documentation icon for the IMG activity, to call up the documentation for the Define Voltage Levels line.1-4 Call up the status information for Define Voltage Levels by clicking on the Status information icon. Note that this is only possible when you are editing projects.You can display, change or maintain the status information. The person responsible is displayed on the Employee tab, in the display area Assigned employees. To request the status information you can also highlight the entry (the object is highlighted in color) and press the right mouse key. You can call up the status information from here.

1-5 In the SAP menu, choose Tools AcceleratedSAP Customizing Project Management or Edit Project.Choose Goto ( SAP Reference IMG. To expand the SAP Utilities node, click on the [(] symbol.Position the cursor on Master Data and choose Edit Expand subtree from the menu bar. You now have an overview of all subnodes and activities. Double-click on the IMG activity documentation icon to call up one of the activities.

Choose Additional information ( Release notes ( Show icons. An information icon appears next to all activities for which release notes are available.1-6 In the SAP menu, choose Tools AcceleratedSAP Customizing Project Management or Edit Project.Choose Goto ( SAP Reference IMG. To expand the Financial Accounting node, click on the [(] symbol.Position the cursor on Contract Accounts Receivable and Payable and choose Edit Expand subtree from the menu bar. You can now see all subnodes and settings possibilities for Contract Accounts Receivable and Payable.

3 TC "Regional Structure" \l 2 \* MERGEFORMAT 3.2 TC "Regional Structure: Unit Objectives" \l 3 \* MERGEFORMAT 3.3 TC "Regional Structure: Business Scenario" \l 3 \* MERGEFORMAT The new development area in IDES Inc.'s service territory has not been entered yet in the postal regional structure. In the exercises for this chapter, you will extend the postal regional structure accordingly.

3.4 TC "Regional Structure: 1" \l 3 \* MERGEFORMAT 3.5 TC "Postal Regional Structure (City File)" \l 3 \* MERGEFORMAT The regional structure (city file) is integrated in central address management. However, it can be called separately. SAP supplies an empty regional structure. For more information see OOS note 132948.

Once the postal regional structure is maintained completely, the addresses of IS-U objects can be allocated to the different elements of the structure (city, street, street section, P.O. box).The address elements are stored centrally in the system, and appear only once in the system as a data record. This guarantees that the spelling and layout of addresses is always correct, and that the address is identical in every transaction that uses it: for example, if the street 'Main Street' is maintained in the system, it must always be entered this way (this means that if you enter the street using the slightly differently spelled 'Maine Street', the system would not find the address during a search).

To be able to employ the address check tool, you must maintain the country-specific table V_005_B. By double-clicking the appropriate country, you branch to the Country Field Checks view . There you activate the address check by setting the City file active and Street-specific postal code indicators . These settings must be active for central address management to check the address of newly created data objects and for it to react with an appropriate warning if incorrect entries are made or if addresses have not been entered yet.

If one city has several postal codes, we recommend that you maintain the city districts. You must structure the city districts in such a way that each one contains only one postal code. This guarantees that the system automatically proposes the correct postal code with the corresponding city when the street (and if necessary, the house number) is entered.

3.6 TC "Elements of the Postal Regional Structure" \l 3 \* MERGEFORMAT Regional structure grouping integrates elements of the regional structure (cities, streets, and street sections). The agent determination function of IS-U, for example, utilizes this integration of the regional structures.

Franchise contract:

This is a contract between a utility company and the municipality regarding franchise tax. It refers to one single division and is managed according to the company code.

All franchise contracts between the utility company and the municipality are listed in the postal regional structure under city.

Calorific value district:

Part of the supply grid for gas. The calorific value for gas is the same throughout a calorific value district.

Water hardness/pressure area:

Parts of a service territory with approximately the same degree of water hardness/water pressure.

Temperature area:

Parts of a service territory with approximately the same air temperatures. You use this to weight degree days and for thermal gas billing.

Air pressure area:

Parts of a service territory with approximately the same air pressure. Used in thermal gas billing.

3.7 TC "Regional Structure: Address Check (1)" \l 3 \* MERGEFORMAT In the customer enhancements for city and street you can store your own check logic.Use enhancement SZRS0001 for your own checks at city level and enhancement SZRS0002 for your check logic at street level. The SAP enhancement for checking for duplicate city or street entries can be found in the IMG for SAP Utilities.

As of release 4.6B, central address management has open interfaces that you can use for the products of external (third-party) service providers. The interfaces are implemented using the Business Add-Ins (BAdIs) listed below (for more information on these interfaces, see OSS note 176559).

ADDRESS_CHECK - enables you to integrate additional postal address checks using external tools. These checks then operate automatically in all applications using central address management.

ADDRESS_SEARCH - enables you to perform an error-tolerant search for addresses, as well as a duplication check.

ADDRESS_UPDATE - used for updating search indices. You must use this interface if you intend to use the search functionality of the ADDRESS_SEARCH BAdI. You can also use ADDRESS_UPDATE in a different context, namely to have the system react to your saving address data.

In addition to these BAdIs, the interfaces also provide additional tools used to postal checks and error-tolerant duplicate searches. These include programs that compare data when changes are regularly made to the postal reference data, or module for building external search indices.

3.8 TC "Regional Structure: Address Check (2)" \l 3 \* MERGEFORMAT You can define your own check routine in enhancement SZRS0003. This enables you to have the system carry out additional checks when you maintain addresses (for the business partner or connection object, for example).

3.9 TC "Linking Own Data to the Regional Structure" \l 3 \* MERGEFORMAT Enhancement EE0200001 (IS-U data determination from address) enables you to determine your own data for storage in the regional structure at the city and street level.

The SAP enhancement for determining data from the regional structure can be found in the IMG.

3.10 TC "Customizing: Postal Regional Structure (I)" \l 3 \* MERGEFORMAT 3.11 TC "Customizing: Postal Regional Structure (II)" \l 3 \* MERGEFORMAT 3.12 TC "Regional Structure: 2" \l 3 \* MERGEFORMAT 3.13 TC "Political regional structure" \l 3 \* MERGEFORMAT In the political regional structure, you model political/administrative units in an hierarchical structure. By means of the address in the postal regional structure, you can allocate elements of the political structure to IS-U master data (to the connection object or business partner, for example).

To maintain elements of the political regional structure, you must first define the hierarchy levels you require. Only then can you allocate elements to the hierarchy elements (for example allocate the element "New York" to the hierarchy level "City").

3.14 TC "Maintaining Political Hierarchy" \l 3 \* MERGEFORMAT You can define your political regional structure hierarchy entirely according to your requirements.

You can only delete a hierarchy level if no elements are allocated to it. If elements have already been entered, you must delete them before you can delete the hierarchy level.

3.15 TC "Regional Structure: 3" \l 3 \* MERGEFORMAT 3.16 TC "Company regional structure" \l 3 \* MERGEFORMAT You use the core component Organizational Structure to organize your service territory according to company criteria.

For example, in the IMG you can define regional structure groups according to geographical aspects. These regional structure groups can be used to control agent determination in that they enable you to distribute certain tasks according to specific regions (for example, meter reader for the regional structure group "City center"). Since regional structure groups can be linked to the postal regional structure at city or street level, a postal allocation of the defined regional structure groups is also possible.

3.17 TC "Regional Structure Areas" \l 3 \* MERGEFORMAT Regional structure areas are composed of regional structure groups. Regional structure areas are required for plant determination in the Work Management component.

The stored plants are then allocated to the respective service objects during plant determination. In this slide, the maintenance planning plant P001 is responsible for all regional structure groups of the regional structure area A (006, 007, 008).

3.18 TC "Plant Determination: Plant Maintenance" \l 3 \* MERGEFORMAT In Customizing, you must first define regional structure areas to which a certain maintenance planning plant for processing service orders is to be allocated. This allocation is then applied directly to the application component Work Management by means of a standard role.

Example:To determine the correct plant for work orders, you need to store the following data in Customizing:

Service object Regional structure area

Maintenance plantDevice replacement 0001

0001Device replacement 0002

0002

In this example, the service object device replacement has been allocated to maintenance plant 0001 via regional structure area 0001. It is allocated to plant 0002 via regional structure 0002 (south west).

3.19 TC "Regional Structure: 4" \l 3 \* MERGEFORMAT 3.20 TC "Regional Structures (1)" \l 3 \* MERGEFORMAT The standard SAP component Central Address Management (CA-GTF-ADR) uses the postal regional structure to check and allocate addresses.

Since both the political and the company regional structures are linked to the postal regional structure, there is an indirect link between the political and company regional structures.

3.21 TC "Regional Structures (2)" \l 3 \* MERGEFORMAT The different regional structure categories are not limited to the same physical space. For example, one element of the company structure can overlap with several parts of the postal structure.

3.22 TC "Regional Structure: Unit Summary" \l 3 \* MERGEFORMAT 3.23 Regional Structures Exercises TC "Regional Structures Exercises" \l 3 \* MERGEFORMAT Unit: Regional StructuresTopic: Political Regional Structures

At the end of this exercise, you will be able to: Display information about the political regional structure. Explain the hierarchy steps of the political regional structure.

Before carrying out initial data creation for the customers you have acquired with the new service territory, you need to verify whether the political regional structure of the new service territory already exists in the system and then add new entries as necessary.

1-1Display the hierarchy of the political regional structure in the system. 1-2Create the city Savannah-0## (where 0## is your group number) as a new element of the political regional structure in the state of Georgia. The city should have the districts "South" and "North". 1-3Display the elements of the political regional structure in the system and check that Savannah-## is among them. 1-4List three characteristics of a political regional structure:

1___________________________________________________________

2___________________________________________________________

3___________________________________________________________

Exercises

Unit: Regional StructuresTopic: Postal Regional Structures

At the end of this exercise, you will be able to: Give information about the postal regional structure. Create new elements. Display the customizing area of the IMG for regional structures.

Before carrying out initial data creation for the customers you have acquired with the new service territory, you need to verify whether the political regional structure of the new service territory already exists in the system and then add new entries as necessary.

2-1You new customer has just moved to the city of New York. 2-1-1Determine whether New York City is already represented in the postal regional structure. 2-1-2If New York City already exists in the system, what postal codes have been created for it? 2-1-3 What districts have been created for the city of New York?

2-2Another customer informs you that she is moving to the new service territory Savannah-0xx, which has not yet been entered in your postal regional structure.

2-2-1Create the new city Savannah-0xx with the assignment number PC0206A0xx (0xx is your group number) in your postal regional structure.

Allocate three different postal codes to the city. Link the new city with the regional structure element Savannah-0xx, which you defined in the previous exercise.2-2-2Assign the city the city districts Savannah-0xx-South and Savannah-0xx-North. Create different postal codes for the two city districts.

2-2-3Which Customizing entries do you use to determine the format of the postal code? Which path do you use to reach this setting?

2-3Now that you have maintained the regional structure, you can create the street where your customer has moved.

2-3-1Add a new street to the city Savannah-0xx Assign the street the number PC0207A0## (0## is your group number). The street is to be located in the city district Savannah-0xx-South.2-3-2In the street you have created, the odd house numbers from 100 to 200 have a different postal code. Allocate a different postal code to these houses.

2-3-3Can there be more than one street with the same name in the system? If so, how can the system distinguish between them?

2-4List three characteristics of the postal regional structure:

1___________________________________________________________

2___________________________________________________________

3___________________________________________________________

2-5True or false?2-5-1A franchise contract has been created for New York City.

2-5-2You need the calorific value district for thermal gas billing.

2-5-3You can allocate different temperature areas to a city.

2-6Display the Customizing functions for the regional structure.

2-7Specify the path you use in Customizing to find the calorific value districts.

2-8What other dependent Customizing activities affect the temperature area?

3.24 Regional Structures: Solutions TC "Regional Structures: Solutions" \l 3 \* MERGEFORMAT Unit: Regional StructuresTopic: Political Regional Structures

1-1Go to the SAP Easy Access menu and choose:

Utilities Industry ( Regional Structure ( Political ( Display Hierarchy.Enter US (United States) in the Country field and choose Enter. The hierarchy of the political regional structure appears.1-2Go to the SAP Easy Access menu and choose:Utilities Industry ( Regional Structure ( Political ( Maintain Elements.Enter US (United States) in the Country field and choose Enter.Place the cursor on Political Regional Structure and choose Edit SYMBOL Expand subtree from the menu. Place the cursor on the State of Georgia line and choose Political Regional Structure ( Create.Enter the city Savannah-0## in the table and choose Create. A dialog box appears where a number of different hierarchy levels are possible. Select the Cty (city) field.

Place the cursor on your new entry, Savannah-0##, and choose Political Regional Structure ( Create.Now enter the city districts Savannah-0xx-North and Savannah-0xx-South in the table and choose Create.

Save your entries.

1-3Go to the SAP Easy Access menu and choose:Utilities Industry ( Regional Structure ( Political ( Display Elements.

Enter US (United States) in the Country field and choose Enter.Place the cursor on Political Regional Structure and choose Edit ( Expand subtree from the menu. Search for Savannah-0xx (choose Edit ( Find from the menu). Enter the data and choose Find.

For information about the color legends, choose Utilities ( Color legend.

1-41___________________________________________________________

It organizes the service territory from an administrative viewpoint.2___________________________________________________________

It has freely definable hierarchies and elements.3___________________________________________________________

It provides a link to the addresses of data objects (such as connection objects and business partners) via the postal regional structure).Solutions

Unit: Regional Structures

Topic: Postal Regional Structures

2-1

2-1-1Go to the SAP Easy Access menu and choose:

Utilities Industry ( Regional Structure ( Postal ( City ( Display.

Place the cursor on the City field and call the F4 help. Place the cursor on New York City and choose Copy. Enter US (United States) in the Country field; enter EN (English) in the Language field. Choose Continue.The display screen for New York City appears. This means that New York City already exists in the regional structure.

An external number was allocated to the cities.

2-1-2In the city display screen, choose Goto ( Postal codes.

A table appears containing the postal codes of New York City.2-1-3In the display screen, choose Goto ( Districts.

A table appears containing the city districts of New York City. Postal codes are already allocated to the city districts.2-2

2-2-1Go to the SAP Easy Access menu and choose:Utilities Industry ( Regional Structure ( Political ( City ( Create.Enter the external number PC0206A0## in the City field. Choose Continue. The Create City screen appears. Enter Savannah-0## in the City field.

Choose Goto ( Postal Codes. Enter three different postal codes. Choose Goto ( Create Postal Codes. The Usage dialog box appears. Select the Dely post. code field and save your entries. Allocate the postal codes to your city and then save.

In the Regional Structure Group field, use the F4 help to copy the entry for the city district North.

Call the F4 help in the Pol. reg. str. (political regional structure) field and search for the city you have created, Savannah-0## Place the cursor on your entry and choose Copy. Save your entries.

You can also create the city using a city that already exists in the system as a template. Note that you can maintain IS-U-relevant default values at this point, which you can also call in subsequent transactions (for example air pressure area and temperature area).

2-2-2Go to the SAP Easy Access menu and choose:Utilities Industry ( Regional Structure ( Postal ( City ( Change.

Enter the external number PC0206A0## in the City field. Choose Continue. The Change City screen appears.

Choose Goto ( Postal Codes. Enter a number in the City district field. Enter Savannah-0xx-South and Savannah-0xx-North in the District name field. Call the F4 help in the Postal Code field. A table appears containing all the postal codes allocated to the city. Place the cursor on a postal code and choose Copy. Save your entries.2-2-3Go to the SAP Easy Access menu and choose:Tools ( AcceleratedSAP ( Customizing ( Project Management ( Goto ( SAP Reference IMG.

Choose Global Settings ( Set Countries ( Set Country-Specific Checks. Place the cursor on US and display the entry. Country-specific settings appear, including those for the format of postal codes.2-3

2-3-1Go to the SAP Easy Access menu and choose:Utilities Industry ( Regional Structure ( Political ( Street ( Create.Enter the number PC0207A0## in the Street field. Choose Continue. The Create Street screen appears. Enter a street name of your choice in the Street Name field. Choose Continue.

Make sure that you type the street name the way you want it to appear in all future transactions, since this is the text against which all entries will be checked in central address management.

Call the F4 help in the District field, place the cursor on the city district you require and choose Copy. Note that the system now automatically allocates the postal code of the city district to the street.

Note fields such as Reg. str. grp (regional structure group) and Jurisdct. code (jurisdiction code). Move the cursor to these fields and choose F1 (field help) for more information.Note that any settings you make here overwrite the default settings at city level. To display the default settings at city level, choose the green arrow next to the city field.

Save your entries.

2-3-2Go to the SAP Easy Access menu and choose:Utilities Industry ( Regional Structure ( Postal ( Street ( Change.Enter the number PC0207A0## in the Street field. Choose Continue. The Change Street screen appears. Choose Goto ( Post. Street Section.

Enter the house number range in the HsNo. from and HsNo to fields. In the House no.ID (house number ID) field, choose indicator 1 for odd house numbers. Enter a different postal code in the PostalCode field. Call the [F4] help to view possible entries.

Note that you can only specify postal codes that have already been created in the system for the city. If necessary, you may have to create additional postal codes for the city in a new session.

Save your entries.

2-3-3Yes. Streets are identified using a unique number (which can be allocated internally or externally), so that a regional structure can accommodate two or more streets with the same name in the same city.

2-41___________________________________________________________

The postal regional structure organizes the service territory according to postal criteria.2___________________________________________________________

It links different elements of the regional structure (such as political regional structure).3___________________________________________________________

It has predefined hierarchy levels (city, city district, street, and street section) which cannot be changed or supplemented.2-5

2-5-1False. To check this:Go to the SAP Easy Access menu and choose:Regional structure ( Postal ( City ( Display. Choose New York City and then Enter.The Franchise contract field group is in the Display City screen.

2-5-2True. To confirm this. place the cursor in the Cal. val. dist.(calorific value district) field (in the IS-U/CCSU data area) and choose F1 for more information.To view any other possible entries, choose the [(] button next to the field.2-5-3True. To check this:Go to the SAP Easy Access menu and choose:Regional Structure ( Postal ( Street ( Display. Place the cursor on the Street field and call the F4 help. Select the street by doubling clicking on it.Place the cursor on the Temp area (temperature area) field. (in the IS-U/CCSU data area) and then press [F1] for more information.2-6Go to the SAP Easy Access menu and choose:

Tools ( Accelerated SAP ( Customizing ( Project Management

The Customizing: Execute Project screen appears. Choose Goto ( SAP Reference IMG.

Open the SAP Utilities node by selecting the [(] icon.

Choose Basic Functions ( Regional Structure ( Postal Regional Structure (or Political Regional Structure).Call the documentation on the Postal Regional Structure IMG activity by double-clicking on the documentation icon.

Also choose Basis ( Basis Services ( Address Management ( Regional Structure/City File.2-7Go to the SAP Easy Access menu and choose:Tools ( Accelerated SAP ( Customizing ( Project Management The Customizing: Execute Project screen appears. Choose Goto ( SAP Reference IMG.

Open the SAP Utilities node by selecting the [(] icon.Choose Contract Billing ( Special Functions ( Gas Billing ( Calorific Value ( Define Calorific Value Districts.

2-8Go to the SAP Easy Access menu and choose:Tools ( Accelerated SAP ( Customizing ( Project ManagementThe Customizing: Execute Project screen appears. Choose Goto ( SAP Reference IMG.

Open the SAP Utilities node by selecting the [(] icon.What other dependent Customizing activities affect the temperature area? Define temperature area.

Define average degree day coefficients.

Define degree day coefficients. Choose Device Management ( Meter Reading ( Weighting Procedures ( Degree Day Weighting. Maintain monthly gas temperatures measured. Maintain daily gas temperatures measured.Choose Contract Billing ( Special Functions ( Gas Billing ( Calorific Value ( Define Calorific Value Area.

4 TC "Scheduling: Contents" \l 2 \* MERGEFORMAT 4.2 TC "Scheduling: Unit Objectives" \l 3 \* MERGEFORMAT 4.3 TC "Scheduling: Business Scenario" \l 3 \* MERGEFORMAT All the contracts in the new development area are to be billed once a year at the start of July. For this to happen, you need to create a new billing portion in which you can define the relevant control data. Later, you can assign all the contracts of all the business partners living in the new development area to this billing portion. To organize meter readings, you generate meter reading units containing specifications for meter reading order creation schedules. In a later step, you assign installations to meter reading units as appropriate.

4.4 TC "Scheduling: I" \l 3 \* MERGEFORMAT 4.5 TC "Function" \l 3 \* MERGEFORMAT Meter reading orders are created in the IS-U/CCS component Device Management and contain register-related data and useful information for the meter reader.

You use meter reading orders to control how your business partners' energy consumption is measured. Meter reading orders can be output as follows:

Download to external meter reading devices (MDE devices)

- As printed customer meter-read cards

- As meter reader forms to serve as a basis for meter reading by your utility company.

Once the energy consumption has been measured, the meter reading results are input to the system and checked for their plausibility (validated). Only then can the business partner be billed for the energy that has been consumed. In scheduling, you define the length of the billing period for all the contracts assigned to a particular billing portion (a billing period of 12 months, for example).

If you wish to charge using the budget billing method, you define the number of budget billings and their cycle in scheduling (one budget billing a month for 11 months, for example).

4.6 TC "Purpose" \l 3 \* MERGEFORMAT Schedule records are used to manage specific dates, including meter reading dates, billing dates, and budget billing due dates.

To be able to generate schedule records for meter reading and billing, you must have defined the corresponding schedule records. In the meter reading units, you define general data for meter reading (for example define June 25 as the start of the meter reading period). In the portion, you determine the basis for billing scheduling (for example define June 30 as the end of the billing period). Note: All dates specified in a portion or meter reading unit are displayed in full, that is with a year as well as the relevant day and month. The day and month displayed still apply the generation of schedule records, regardless of the year displayed. That means if you create a portion and specify June 30 1998 as the end of the billing period then June 30 also applies for 1999, 2000, 2001 etc.To generate schedule records for later periods, you do not need to change the data in the portion. When you generate schedule records, you always determine an interval.

4.7 TC "Scheduling: II" \l 3 \* MERGEFORMAT 4.8 TC "Elements of Scheduling" \l 3 \* MERGEFORMAT The schedule master records stored in the portion or in the meter reading unit are used to generate the schedule records for billing or meter reading.

Budget billing dates are controlled via the parameter record.

4.9 TC "Schedule Master Records: Portions" \l 3 \* MERGEFORMAT In a portion, you group together contracts of all business partners in a part of your service territory (for example, the city district "south") for which the same billing conditions are to apply (for example, annual billing for residential customers on June 30 each year).

4.10 TC "Billing Periods" \l 3 \* MERGEFORMAT Billing on a daily basis/billing that is dependent on a key date is determined in the individual rate steps. Special procedures, such as those during a move-in/out, can be defined in Customizing under Period Controlling.

4.11 TC "Schedule Master Records: Meter Reading Units" \l 3 \* MERGEFORMAT Control of the meter reading is linked to the technical master data by means of the installation. All devices (registers) installed in an installation are allocated to this meter reading unit automatically.

In the postal regional structure, you can store meter reading units as default values at the city and street levels; these meter reading units are then proposed as the default value when you create an installation.

4.12 TC "Portions and Meter Reading Units" \l 3 \* MERGEFORMAT A portion normally has several meter reading units, which are structured on a regional basis and/or from the point of view of scheduling.

The meter reading units of a portion do not have to be in close proximity to one another. Their grouping can also depend on other factors, such as billing conditions.

Example:

Portions A and B represent different city districts consisting almost entirely of households (that is, residential customers). The meter reading units of these portions are structured in such a way that they correspond to the daily work quota of the meter reader.

Since other meter reading cycles and billing conditions apply to nonresidential customers, major customers (industrial and business groups) within the area concerned are allocated to a separate portion (C). This portion consists of three meter reading units that are not in close proximity to each other. They are "islands" inside portions A and B.

The utility company bills residential customers by turns: portion A is billed on 6/15; portion B is billed on 7/15.

Nonresidential customers are billed monthly, that is, portion C is billed on 6/15, 7/15, and so on.

4.13 TC "Parameter Record" \l 3 \* MERGEFORMAT Even if you do not wish to charge budget billings, a parameter record is required for technical reasons; you must specify the parameter record in the corresponding portion. In this dummy parameter record, you specify that no budget billings are charged (budget billing cycle = 0).

Budget billing intervalIf you calculate the billing period length (budget billing plan period) in days then the budget billing interval specifies how many days after the start of the period the first budget billing plan item is calculated. The system gradually determines other budget billing plan items using this interval.

4.14 TC "Parameter Record, Portion and Meter Reading Unit" \l 3 \* MERGEFORMAT Mobile Data Entry:In the MDE number field in the meter reading unit, you can enter the number of the PC to which the meter reading data is to be downloaded in the case of mobile data entry.If you use this field, that is, if you carry out meter readings using an MDE device, then only devices that are read by MDE can be allocated to the meter reading unit concerned.

You can easily check schedule master records and parameter records in the system. This function can be used for several portions or meter reading units at the same time.

4.15 TC "Budget Billing Cycle/Budget Billing Frequency" \l 3 \* MERGEFORMAT The budget billing period corresponds to the billing period. If the end of the billing period (in accordance with the schedule record) has been defined as December 31 then the new billing period, and therefore the new budget billing period, begins on January 1.

When you maintain the portion you enter all permissible combinations of budget billing cycle and number of budget billings. However, all these combinations must be contained in the parameter record.

A permissible combination refers to any pair of numbers for the budget billing cycle and number of budget billings where the product is smaller than or equal to the billing period (= period length and period category).

Example:Period length: 12 months; start of period: 08/01/00

Budget billing cycle 01/number of budget billings 11 =>

budget billing: 08/30/00

2. budget billing: 09/30/00 etc.

11.budget billing: 06/30/01

Budget billing cycle 01/number of budget billings 12 =>

budget billing: 08/30/00 etc.

12.budget billing: 07/30/01

Budget billing amounts can also be requested in cases where billing is carried out monthly.

4.16 TC "Scheduling: III" \l 3 \* MERGEFORMAT 4.17 TC "Generation of Schedule Records" \l 3 \* MERGEFORMAT Schedule records can be generated for portions and meter reading units separately, or they can be generated together for all meter reading units of a portion.

When you generate the schedule records you must specify the time period for which the dates are required.

You can easily check the generated schedule records (meter reading and billing dates, due dates, and so on) by choosing Schedule record => Analysis. This function can be performed for several portions or meter reading units at the same time. Choose the names of the portions and meter reading units in such a way that the objects are easy to select/access later.

4.18 TC "Scheduling: Annual Billing" \l 3 \* MERGEFORMAT End of billing period: This is the date on which the portion is to be billed for the first time. This date, together with the length of the billing period (that is, the period length), determines the date of the next billing (start of the next billing period = end of the billing period + 1 day).

The scheduled billing date is the date on which the contracts belonging to a portion are billed. This takes the SAP calendar into account.

The end of the meter reading period corresponds to the end of the billing period, and is used as a basis for defining dates of subsequent meter reading periods.

The scheduled meter reading date is the date on which the schedule specifies the register is to be read. It is also the date for which periodic meter readings are generated in scheduling. It forms the basis for calculating the expected consumption during meter reading order creation; it also acts as the final date for determining the budget billing amount.

4.19 TC "Scheduling: Monthly Billing" \l 3 \* MERGEFORMAT To generate schedule records (starting in July 2000) for the above schema, the following settings are needed: Portion: - End of billing period:

08/03/00 - Scheduled meter reading date:08/01/00 - Period length:

1 month Meter reading units

No. 1 No. 2 No. 3 - End of meter reading period*: 8/3/00 8/3/00 8/3/00 - Scheduled meter reading date: 6 => 4 => 5 =>

* When the meter reading unit is created, the end of the meter reading period is automatically adjusted to correspond to the end of the billing period.

4.20 TC "Period Length with Specified Number of Days" \l 3 \* MERGEFORMAT The above example illustrates the interplay of the schedule records for portions and meter reading units. If a portion has a period length that you have determined by specifying a specific number of days then the Budget billing interval field takes control of the requested budget billing.

4.21 TC "Taking into Account the Factory Calendar" \l 3 \* MERGEFORMAT Taking the factory calendar into accountSelecting the Include FacClr (Include factory calendar) field means that the factory calendar specified in the portion is taken into account when the day-based period length is calculated in work days. If non-working days fall within the period that is to be calculated then the end of the billing period is pushed back accordingly.

4.22 TC "Scheduling: IV" \l 3 \* MERGEFORMAT 4.23 TC "Dynamic Scheduling" \l 3 \* MERGEFORMAT If you implement dynamic scheduling, you must first establish the controlling parameters in Customizing. The functions are then activated here. Make sure you mark the Dynamic Scheduling field as active; otherwise the dynamic scheduling fields are not displayed in the portion and meter reading unit screens.

There is also a menu option for processing dynamic scheduling.

4.24 TC "Dynamic Scheduling: Usage" \l 3 \* MERGEFORMAT 4.25 TC "Customizing" \l 3 \* MERGEFORMAT 4.26 TC "Example" \l 3 \* MERGEFORMAT 4.27 TC "Result" \l 3 \* MERGEFORMAT In this example, meter readings are put back from January to February because there are only 19 work days in January.

In March, there are 23 workdays. Therefore, meter readings are brought forward from April. However, you can prevent meter readings being brought forward when you define the controlling parameters in Customizing.

4.28 TC "Manual Changes" \l 3 \* MERGEFORMAT You can manually change the automatically planned meter readings after they have been set. In this example, there are to be no meter readings performed on February 3rd. You can also restrict this postponement to individual meter readings only.

You have to specify the new date of the postponed meter readings. You can also configure the system so that all subsequent meter readings are postponed correspondingly.

4.29 TC "Scheduling: Unit Summary" \l 3 \* MERGEFORMAT 4.30 Scheduling: Exercises TC "Scheduling: Exercises" \l 3 \* MERGEFORMAT

Unit: SchedulingTopic: Portions, Meter Reading Units, and Parameter Records

At the conclusion of this unit, you will be able to: Describe the relationship between portions, meter reading units and parameter records.

In scheduling you can define and control the meter reading and billing schedules in your service territory. Two or more installations to be read on the same date form a group called the meter reading unit, whereas two or more contracts to be billed on a given date form a group called a portion. Budget billing is controlled via the parameter record, which contains all information relevant to the budget billing cycle and budget billing due dates.

1-1True or false?1-1-1Portions contain the schedule master records for billing.1-1-2You cannot create portions unless there is a meter reading unit.1-1-3The meter reading units in a portion must all be in close proximity to one another.1-1-4You cannot create a portion unless there is a parameter record.1-1-5 When you maintain a portion, you must enter all permitted combinations of budget billing cycles and number of budget billing amounts.1-1-6Budget billing dates are controlled by the portions.1-1-7Portions group together contracts that are to be billed together.1-1-8Only one meter reading unit can be allocated to a portion.1-1-9Meter reading units group together installations that are to be read together.Exercises

Unit: SchedulingTopic: Generation of Schedule Records

At the conclusion of this unit, you will be able to: Create schedule master records for portions and meter reading units. Generate schedule records.

All the contracts for the new customers in your new development area are to be billed on the same date. To model this in the system, you must create a new portion. But first you must define permissible budget billing cycles and dates in a parameter record.

2-1First create the schedule master records (portion and meter reading unit). The billing period should start on July 1 and should last for exactly one year. Installments for budget billings should be paid monthly and bimonthly; there should be a total of eleven in the billing period for monthly installments, and five for bimonthly installments. There should be a month between the final invoice for one year and the first budget billing installment in the following year (the next billing period). The debit entry/printing of the budget billings should take place on the 15th of each month.

2-1-1First create the parameter record PC04A0## (where 0## represents your group number). The parameter record should allow both monthly budget billing payments and budget billing payments every two months.

2-1-2Now create a portion PC04A0##. Enter an end date for the billing period and a statistical allocation date.2-1-3Now create meter reading unit PC04A0##. The meter reading orders should be created 20 working days before the meter reading is due. Choose a form for the cover sheet and the meter reading order. The meter should be read by an employee from the utility company.

2-2Generate schedule records for the por