176120329 Sap Isu Master Datacreation

8/11/2019 176120329 Sap Isu Master Datacreation

http://slidepdf.com/reader/full/176120329-sap-isu-master-datacreation 1/33

ISU Data Creation

ISU DATA CREATION

___________________________________________________________________________________________ of 33



ISU Data Creation

Table of Contents

1 ISU Master Data Model..................................................................................................... 32 Create Business Partner (FPP1).......................................................................................43 Create Contract Account: (CAA1).....................................................................................4 Create Contract (!S2")................................................................................................... 1## Create De$ice (I%"1)......................................................................................................1&' Create Connection *ect (!S##)...................................................................................23

+ Create Pre,ise (!S'")...................................................................................................2'& Create Installation (!S3")...............................................................................................2

___________________________________________________________________________________________ of 33



ISU Data Creation

1 ISU Master Data Model

Master data in ISU is primarily divided into 2 parts.1. Business Mater data.2. Tecnical Master !ata.

Business Mater data" Business Mater data comprises of Business Partner# $ontract%ccount and $ontract data o&'ects (ic provide te customer information li)e- $ustomer %ddress- Ban) details- Payment * Ta+ details- Type of contracts etc

Technical Mater data: Tecnical Mater data comprises Premise# $onnection ,&'ect#

Installation and !evice. Tese o&'ects provide information a&out te tecnical attri&utes (icare important in calculating te consumption for &illing a particular customer. Te significanceof eac o&'ect as &een e+plained in te follo(ing capters.

Note: Before start creating te Master data it need to &e made sure tat te -egionalstructures# Ta+ codes# %ccount code# %ccount determination codes# Meter -ead Units M-U/and portions are configured.

___________________________________________________________________________________________ of 33



ISU Data Creation

2 Create Business Partner (FPP1)

Business Partner is te igest level of customer contact data from te Business Master !ataperspective. It groups all te $% aving related to one customer so tat te centrali0edmaintenance of te account is possi&le li)e maintaining te Ban) details# $redit (ortinessetc.

Fields to be considered while creating the Business Partner:

Mandatory fields:

1. Business Partner $ategory"Person# ,rgani0ation# roup

Use" determines access to certain fields &ased on te category mentionedote" $annot alter &usiness partner category later

2. %ddress3. $reate in -ole"

a. $ontract Partner" in)s te Business partner to $ompany tru $ontract%ccount * $ontract.

&. Installer" %lready connected to a $o $ode.

!tional Fields:

1. -eference customer" It elps to use te standard S! functionality.2. 4urisdiction code.

___________________________________________________________________________________________Page 5 of 33



ISU Data Creation

Data creation !rocess: Business Partner is created (it Partner $ategory" Personproviding te address and Ban) details.

1. 6nter 7n8PP1 in te command &ar.

%nd Press "#nter$.

2. Select 9Person: (ic displays te Create Person screen

___________________________________________________________________________________________Page ; of 33



ISU Data Creation

3. <igligt te =%ddress> ta& and enter

ame

%ddress details of te Business Partner.

5. $lic) on =More fields> and provide

4urisdiction $ode Tis value is dependent on te -egion tat te address &elongs to

___________________________________________________________________________________________Page ? of 33



ISU Data Creation

;. o to "Pay&ent Transactions$ ta& and provide

___________________________________________________________________________________________Page @ of 33



ISU Data Creation

Ban) details for incoming and out going payments.

?. Press "Sa'e$(

,T6" you may find tat te postal code entered returns an error. Ignore it and acceptte address/.

Ma)e a note of te Business Partner num&er in te status &ar.

Does ) Don*ts:

1. Ta+ 'urisdiction code is mandatory in places (ere te A%T is not in place for ta+calculation. Tis is necessary (ile creating te $ontract %ccount. Tis value varies (it te

State# $ountry and $ity.

___________________________________________________________________________________________Page of 33



ISU Data Creation

3 Create Contract Account: (CAA1)

$ontract %ccount groups all te contracts of a Business Partner aving same !unning andPayment data. It olds te control data Ban) !etails# Payment data# !unning data#%lternative Payer# Payee# Bill recipient# !unning -ecipient/ (ic is applica&le to all tecontracts grouped under tis contract account. $ontract account is managed using te !enIte& %ccounting in %-* %P.

Fields to be considered while creating the Contract %ccount:

Mandatory fields:

1. $ontract %ccount category"

Te contract account category determines te follo(ing contract account attri&utes"

• Ceter you are allo(ed to assign only one &usiness partner or more tan one to acontract account

• Ceter you are allo(ed to assign only one contract or more tan one

• Ceter you are allo(ed to maintain a contract account online

• Te num&er range tat is allo(ed for e+ternal or internal num&er assignment

• Ceter it is a collective invoice account ISDU/

• Ceter it is a oneDtime account

• Te editing screens or data fields tat you can use to edit te contract account

2. Tolerance roup " !ef ine te tolerance limits for incoming payments 3. $learing category" Tis references te contract account in automatic clearing postings.

It is com&ined (it te clearing type to form te )ey tat defines te clearing rules in$ontract %ccounts -eceiva&le and Paya&le.

5. Payment $ondition" Tis field defines te rules for determining due dates # incomingpayments as (ell as deadlines for outgoing payments. It is used in &usiness processesfor determining &ill due dates and &udget &illing amount due dates.

;. %ccount $lass" $lassifies contract accounts (itin a supply area.

?. %ccount !etermination I!" $aracteristic tat is com&ined (it te company code #division # main transaction and su&Dtransaction for use in determining a 7 account.

@. Bill 8orm" $ontains te 8lo( ogic of a print program in te form of a ierarcy.. -esponsi&le $ompany $ode" Te posting created (it payment to &an) clearing

accounts al(ays ta)e place in te responsi&le company code.

!tional fields:

1. %lternative payer" Tis field provides te option of coosing a different payer tat tecustomer.

___________________________________________________________________________________________Page E of 33



ISU Data Creation

Data creation !rocess:

1. 6nter 7n$%%1 in te command &ar.

Press "#nter$

Tis ta)es you to $ontract account $reate initial screen.

2. 6nter te values for

Business Partner nu&ber to (ic you (ant to attac tis $ontract %ccount

Cont( %cct Cat( Tis value elps to align te control data of te %ccount group (it tis contractaccount.

___________________________________________________________________________________________Page 1F of 33



ISU Data Creation

3. Press "#nter$.

Tis ta)es you to $ontract %ccount $reate" eneral !ata screen.

Provide values for

$ontract %ccount name

Tolerance roup

$learing $at

Payment $ondition

%ccount class

%ct !eterm.I!

Bill 8orm

___________________________________________________________________________________________ of 33



ISU Data Creation

5. o to Payment7Ta+es Ta& and enter value for

-espon.co.code

___________________________________________________________________________________________ of 33



ISU Data Creation

;. o to !unning7$orrespondence Ta& and enter values for

rouping $at

!unning Proc

___________________________________________________________________________________________ of 33



ISU Data Creation

?. Press "Sa'e$

Tis creates te $ontract %ccount (ic is seen in te status &ar.

___________________________________________________________________________________________Page 15 of 33



ISU Data Creation

4 Create Contract (ES2)

$ontracts represent te entities tat are &illed. Gou can &ill one or more contractstogeter using a contract account.

$ontracts are lin)ed to installations in ISDU and tese installations contain tecnical data

(it regard toBilling.

Fields to be considered while creating the Contract:

Mandatory Fields

1. !ivision2. $ompany $ode.3. 4oint Invoicing" <ere (e specify (eter tis contract is to &e invoiced togeter

(it oter contract and o( tis is to &e done.5. %ct !eterm I!

;. $ontract %cct" $ontract %ccount num&er


1 6nter 6S2F in te command &ar.

Press "#nter$

Tis ta)es you to $reate $ontract initial screen.

2 6nter values for

___________________________________________________________________________________________Page 1; of 33



ISU Data Creation

!ivision

$ompany $ode

Press "#nter$

Tis ta)es you to $reate $ontact screen.

3 6nter values for

6nter 4oint Invoicing

___________________________________________________________________________________________Page 1? of 33



ISU Data Creation

%cct. !etermination I!

5 Press "#nter$

Tis ta)es you to %dditional !ata ta& screen.

; 6nter values for

$ontract %ccount

___________________________________________________________________________________________Page 1@ of 33



ISU Data Creation

? Press "Sa'e$(

Tis creates te ne( contract num&er (ic is displayed on te status &ar.

Dos ) Don*ts:

a. $ontacts are automatically created during customer moveDin into a premise# so it isadvisa&le not to create te contract e+plicitly.

&. ,nly one contract can ever &e assigned to an installation at any one time.

! Create De"ice (I#1)

___________________________________________________________________________________________Page 1 of 33



ISU Data Creation

% !evice is an instrument used for measuring consumption# processing data# or controllingand protecting oter instruments.

!evices are managed in te Plant Maintenance PM/ application component as pieces ofeHuipment (it serial num&ers.

Te device num&er is created in MM (it te function oods -eceipt. %t te utility company#te device is la&eled (it tis num&er. Te device num&er can also &e generated (en youcreate a device in ISDU. Te device is identified &y a uniHue material and serial num&ercom&ination to distinguis it from oter pieces of material tat may ave te same serialnum&er. Te eHuipment num&er is te same trougout te (ole system. !evice issynonymous to 96Huipment: in Plant Maintenance.!evice can &e from one of te device category li)e meter# sensor# counter# regulator#corrector or transformer.

Fields to be considered while creating the De'ice:

Mandatory Fields

1. Material" Te oods tat are te su&'ect of &usiness activity.

2. Te Serial um&er master record is a com&ination of te material num&er and teserial num&er.

3. $ategory" D ey !istinguising individual tecnical o&'ects according to teir use.

5. 6.g. Macinery# !evice

;. $onstruct Gear" D Gear in (ic te tecnical o&'ect (as constructed

?. Aalid 8rom" D !ate from (ic time slice is valid

@. -egister roup" D roup of registers tat &elong to one or more devices.

. Inspection -elevance of !evice" D Specifies (eter te device is to &e included in asampling procedure.

!tional Fields

1. Manufacturer

2. Model um&er

3. M- -ecorded


1 6nter IJF1 in te command &ar and press "#nter$ (ic displays te $reate MaterialSerial um&er initial screen.

___________________________________________________________________________________________Page 1E of 33



ISU Data Creation

2 6nter value for

Material

$ategory

3 Press "#nter$. Tis pops up te ISU data screen.

6nter value for

+egister grou! (ill &e defaulted &ased on te material selected

Ins!ection +el( sould al(ays &e 1

%n initial meter reading can &e recorded if reHuired

___________________________________________________________________________________________Page 2F of 33



ISU Data Creation

5 Press te "Transfer$ &utton.

Tis ta)es you to $reate Material Serial um&er" IS data screen

Te screen (ill &e populated (it te values as so(n &elo(.

___________________________________________________________________________________________ of 33



ISU Data Creation

; $lic) "Sa'e$.

Te ne( !evice num&er serial num&er/ is so(n in te status &ar.

___________________________________________________________________________________________ of 33



ISU Data Creation

Dos and Don*ts

Gou can use pieces of eHuipment &y temselves pure o&'ectDrelated structuring/# or incom&ination (it te component 8unctional locations function and o&'ectDrelatedstructuring/.

$ Create Connection %&'ect (ES!!)

___________________________________________________________________________________________ of 33



ISU Data Creation

% connection o&'ect is usually a &uilding &ut can also &e a piece of property or a facility# sucas a fountain or construction site.Since an address is allocated to a connection o&'ect# te connection o&'ect lin)s premises#device locations and connections to te postal regional structure.

Te connection o&'ect is a functional location from te Plant Maintenance PM/ applicationcomponent. Terefore# maintenance is managed using te functions of te ServiceManagement PMDSM%/ component# for e+ample# if you (is to organi0e te repair andmaintenance of devices at te connection o&'ect level. Maintenance and repairs are &illedusing te Sales and !istri&ution S!/ application component.

Fields to be considered while creating the Connection b,ect:

Mandatory Fields

1. !escription" D !escription of connection o&'ect

2. Street %ddress

!tional Fields

1. $ommunication ta& K telepone# mo&ile pone# fa+# eDmail.

2. P, &o+ address

3. $omments D %ddress notes


1 6nter 7n6S;; in te command &ar.

___________________________________________________________________________________________Page 25 of 33



ISU Data Creation

Press "#nter$.

Tis (ill display te $reate $onnection ,&'ect" Initial Screen.

2 %t te $reate $onnection ,&'ect" Initial Screen# press "#nter$ (itout ma)ing anycanges.

Create Connection b,ect: -..../ screen is displayed.

3 6nter values for

%ddress

Maintenance Plant details# as &elo( Te address is te same as tat for

te Business Partner created earlier/.

___________________________________________________________________________________________Page 2; of 33



ISU Data Creation

5 Press "Sa'e$ Ignore any error message due to te postal code# and accept te address/.

ote te $onnection ,&'ect num&er in te status &ar.

Dos and Don*ts

8or eac connection o&'ect you can define any num&er of static notes. Tese can &e printedon meter reading orders# for e+ample# to give field service employees e+tra information.6+ample include L-ing Mr G:s door&ell#L LBe(are of te dog#L and so on. Gou can also sue tedynamic notes predefined in te system for e+ample LInstallation &loc)ed for meter reading#LLMeter reading already entered.L/

Create Preise (ES$)

___________________________________________________________________________________________Page 2? of 33



ISU Data Creation

-epresents a self contained unit (itin te &uilding e.g. an apartment or a sop/.Te Premiseolds specific address data. 6.g. Pro'ect# round 8loor# 3FFF <ills (ood !rive# <ills (oodBusiness Par)# $ertsey# Surrey# T1? F-S/

Te premise is an enclosed spatial unit tat is supplied (it energy# for e+ample# anapartment or factory.

Te premise is allocated to a connection o&'ect and to te address of tat connection o&'ect.% premise can ave several utility installations. Since te premise is divisionDindependent# youcan allocate electricity and (ater installations to te same premise# for e+ample.

Fields to be considered while creating the Pre&ise:

Mandatory Fields

1. $onnection ,&'ect

!tional Fields

1. ocation supplement# floor# room num&er

2. %ttri&utes K Premise type# ,(ner# o. of persons# %utori0ation group

3. otes for premises


1 6nter 6S?F in te command &ar.

___________________________________________________________________________________________Page 2@ of 33



ISU Data Creation

Press "#nter$

Tis (ill display te Create Pre&ise: Initial screen.

2 %t te $reate Premise Initial" Screen# press enter (itout ma)ing any canges.

Tis ta)es you to $reate Premise screen.

3 6nter values for

$onnection ,&'ect num&er

%ddress of te premise.

___________________________________________________________________________________________Page 2 of 33



ISU Data Creation

5 Press "Sa'e$.

Ma)e a note of te Premise num&er from te status &ar.

Do*s and Don*ts

8or eac premise you can maintain te follo(ing fields

a. %dditional street data ena&les you to manage additional information on te streetname of te connection o&'ect. Gou can also store different street names.

&. Storage data elps field service employees to Huic)ly identify premises.

* Create Installation (ES3)

%n installation groups togeter te devices# registers# and# if applica&le# reference valuestat &elong to te same division and are allocated to te same premise# and tat areterefore &illed togeter# suc as an onDpea) and an offDpea) rate meter.

___________________________________________________________________________________________Page 2E of 33



ISU Data Creation

%n installation is allocated to one contract only. In e+ceptional cases suc as aninstallation under construction or an installation (itout an o(ner/ an installation is notallocated to a contract.

Te &illingDrelevant installation data is managed historically. Tis ena&les you to cangete rate category (itin a &illing period# for e+ample# (itout any pro&lems.

Fields to be considered while creating the Installation:

Mandatory Fields

1. ey !ate" D ey !ate for Selection %ccording to TimeD-elated Aalidity

2. !ivision" D Type of utility 6lectricity or as/

3. Premise" D Premise on (ic device installation is needed

5. Aalid 8rom" D Start date of validity

;. Billing $lass" D $lassification of $ontracts (itin a division

?. -ate $ategory" D $lassification of an Installation for Billing purposes

@. M- Unit" D rouping of Installations and teir devices and registers according toregion.

. Base period $ategory: 0 !etermines (eter to use te meter reading results fromte !re'ious !eriod or te same !eriod of the !re'ious year in tee+trapolation.

!tional Fields

1. Industry" D %n industry sector is te term used to classify a company according toits main &usiness activity.

2. Temperature %rea

3. Billing 7 Meter read control relevant D M- $ontrol# Bloc)ing reason

5. !eregulation information K Service type# status


1 6nter 6S3F in te command &ar.

___________________________________________________________________________________________Page 3F of 33



ISU Data Creation

Press "#nter$(

Tis ta)es you to Create Installation: Initial Screen(

2 6nter values for

ey date

!ivision

3 Press "#nter$

Create installation screen is displayed.

___________________________________________________________________________________________ of 33



ISU Data Creation

5 6nter values for

Premise num&er.

B$lss

-ate $at M- Unit

; Press "Sa'e$.

Te ne( Installation um&er is displayed in te status &ar.

___________________________________________________________________________________________ of 33



ISU Data Creation

Dos and Don*ts

a. Te entries you ma)e in te deregulation fields of te installation affect o( tederegulation scenario is determined.

&. Gou can cange te valid fr. valid from/ date or te premise of an installation aslong as a contract as not yet &een allocated to tat installation# and no devicesave &een installed.

c. Gou can allocate a load profile to an installation. Te allocation is related to teidentification of te corresponding load profile.

d. Gou can override te general rate category (it te individual rate category of teinstallation if you ave made specific arrangements (it te customer# fore+ample/.

176120329 Sap Isu Master Datacreation

Documents

Transcript of 176120329 Sap Isu Master Datacreation