Master Data Basic Functions D3

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 28

SAP IS-Utilities Training

Basic Functions and Master Data

July 2007
Master Data Integration with R/3 Component
IS-U Device management VS. Plant Maintenance

• The connection object is a functional location from the Plant


Maintenance (PM) application component with category A:
Connection object

• Go to transaction code ES57 and IL03 to display the object in


the 2 different view.
Master Data Integration with R/3 Component
IS-U Device management VS. Plant Maintenance

• The device location is a functional location from the Plant


Maintenance (PM) application component with category G: IS-
U Device Location

• Go to transaction code ES67 and IL03 to display the object in


the 2 different view.
Master Data Integration with R/3 Component
IS-U Work Mgmt VS.
Service Mgmt

Maintenance and
service (such as
initial creation of a
connection, or
malfunction repair)
are managed using
the functions of the
Customer Service
(CS-WM)
component.
Master Data Integration with R/3 Component
IS-U Customer services
VS. Sales and
Distribution

When a contract partner


is created, the standard
Sales and Distribution
(SD) component
customer is also created
in the background. With
this SD customer role,
quotations can be
created where services
can be billed in SD.
Master Data Integration with R/3 Component

Contract Account Business Partner SD SOLD-TO-PARTY

SAP - IS-U/CCS
Regional
Contract
Structure

Connection PM FUNCTIONAL
Installation Premise
Objects
LOCATION

Device Device Location Connection

PM EQUIPMENT PM FUNCTIONAL PM EQUIPMENT SAP R/3


LOCATION
Initial Data Creation – Execute Move-In
During initial data creation, you enter all technical data and data relevant to billing for a new

premise, which many contain several utility installations from different divisions. This involves:

•Create connection object

•Create premise

•Create installation (including rate category data and individual facts)

•Create device location

•Install devices

•Maintain other data relevant to billing (for example, register relationships)

Integration

After initial data creation of a premise, you can process a customer move-in using the Move-

In/Out (ISU-CS-BT-IO) component.


Execute Move-In
Business
Business
Master Data To create a move-in, you require one
Master Data
Business Partner or more installations that are vacant
on the desired move-in date.
• In the case of an initial move-in,
Contract Account ensure that you have completed
initial data creation, including
creation of the installation(s).
Contract • Devices can (but do not have to) be
installed and allocated before move-
Technical in.
Technical
Master
MasterData
Data
Installation • If one of the installations is already
allocated to a contract, this allocation
Apartment 1 Premise must be reversed. To do this,
process a move-out. An installation
can only be allocated to one contract
Connection Object at any given time.
Execute Move-In

Via transaction code

EC60 – Move-in/out
Master Data changes - Execute Move-In
During move-in processing,
• One or more contracts are created to commence on the specified move-in date.

• The installations you specified at the start of processing are allocated to these
contracts. (Note: If the move-in date is in a period in which one of the installations
has already been billed then the move-in cannot be created.)

• You can save changes to business partner and contract account data as
scheduled changes. This means that the changes are not activated until a future
date.

• The tax jurisdiction code of the connection object address is copied to all the
contracts of the move-in document, as well as to all the business partner addresses
that were automatically created through the move-in.
Data relationship

Partner
Connection object
1:N
1:N
1:1

Contract account 1:1 1:1

1:N Premise Device location


1:1
1:1 1:N 1:N
Contract
1:1 1:1
1:1 1:N
Installation Device
1:1 1:1
1:N
1:1
1:N
Sector
1:1
Meter Reading Unit Portion
1:N
MDT and MDG
• Master data templates (MDTs)
and the master data generator
(MDG) are tools used in SAP IS-
U to automatically create master
data.
• Accelerate new data creation
process by using a template
application that allocates fixed
values to fields in a given object.
• This restricts number of fields
that can be individually
maintained.
• The MDT enables creation and
change IS-U master data using
the MDG.
Master Data Templates (MDTs)
• Template for creation of master data.
• Allocated to a MDT category, which determines structure of the templates
and determines what objects system creates or changes.
• Defines mandatory, optional fields in master data creation or change for
each corresponding master data.
• Fixed value could be defined for fields if required. Similarly, manually
maintained values are also allowed in the template.
Master Data Generator (MDG)
• Integrated to the master data templates (MDTs)
• Record fixed values (constant) from the definition of MDTs.
• Transfers the manually entered values from MDTs.
• Eventually MDG uses all the values to maintain the corresponding objects
of the IS-U Data model
R/3 Company Structure
Introduction to Customizing
The goal to customizing is…
• To implement R/3 quickly, economically and securely
• To adjust functions to the individually requirements of your company
• To support project control and documentation
• To minimize the implementations activities needed

The benefits of IMG is…


• Step by step guide
• Detailed implementation guide on each step
• Unified procedures for all
• Reduction of implementation times
• Customizing settings are transported
Introduction to Customizing
To access the IMG path….
Introduction to Customizing
In customizing, it is possible to….
• Define data structure and hierarchies
• Maintaining tables
• Setting up screen display and screen fields
• Defining number ranges
• Defining notes
Regional Structure
IMG path
Portioning and Scheduling
IMG path
Cross Application Business Partner
IMG path
IS-U Business Partner
IMG path
Contract Account
IMG path
Contract
IMG path
Connection Object
IMG path
Premise
IMG path
Installation
IMG path
Device Location
IMG path

You might also like