TopicsMaster Data objectsContract ManagementOther Processes

Middleware & Replication of BP & Technical ObjectsISU Master Data Templates & Error HandlingCRM Product configurationsTransaction Launchers and FOPsIntroduction to Product packageNew service order linksNew Identification in ICWEBPOD sets and new service location workbenchDiscussion on GSPC & Sabarmati BBPs

Bill CorrectionFinancial customer careCustomer Data environment

ISU

BP ( requires an SD Customer)Contract AccountContractInstallationConnection object,premise/podDevice,Registers,Device LocationRegional Structure

BP requiresNumber rangerolesBP type

SD customer is needed for creating service order and service notification

portionMRU

2 different number ranges for sold to party and for organizationZ2 -> 2000000 to 29999999 ( CRM Internal ), should create a External Number Range in ISU, create a Account group in SD all same Z2).PIDE transaction is needed for replication for SD customer BP Classification -> CRM -> Account Group in ECC

if you maintain indentification type, maintain it in both the sideslanguage field is mandatory in SD. Maintain it in both the sideswhatever u maintain in SD you need to maintain it in CRM

we assign the sales area template in bp

crm org -> ECC sales orgSales information - Sales org Distribution channel Division

Billing Information Pricing Account Assignment

During Initial load -> through Emigal -> ISU first (All the number ranges should be Internal Number Range)CRM External Number Range

For subsequent creation of BP make the number range as External number range in ISUand make it as Internal Number range in CRM

20000000 -> 20004215 (isu , Initial load)20004216 -> 20000999(crm, subsequent BP creation)

Org BP Integration -> to pick the Org BP Number range in CRMHRALX field = Z3BP Grouping

ISU -> BP -> Customer Master

Refer to Best Practices

Customer classification type maintain Z002 type

cook book on mdt

CRM

BPBAContract

Ibase

Regional Structure from ECC to CRM

regioanl structurestreet routing defines mru

Z2 -> 2000000 to 29999999 ( CRM Internal ), should create a External Number Range in ISU, create a Account group in SD all same Z2).

During Initial load -> through Emigal -> ISU first (All the number ranges should be Internal Number Range)

Integration of BP and Org Management

regional structure group (south Zone) regional structure (City)(District)streets

postal codes are given in city level

Learnings Number RangesCR 10, CR 100CRM MiddlewareIUT 260, IUT 255SD Customer and SD

ISU masterConnection Object, Premise,/POD

donwload category, hierarhcy in crm for PremiseCreate a number range for Connection object and POD and another number range for Premise

to create a connection object in ecc, we need a plant.Determination of Plant through MDT

Go through RKT for EHP2/EHP3.

Key account manager role -> temporary connection objects

create conn obj and pod as product type material and object family -> conn object and premiseadd isu_connobj set typeisu_pod for pod

snro for number ranges

premise gets replicated directly, (External number range in isu) from EHp2isu_numprm -> number range

isu -> master data template object families -> customer service

eprodcust -> txn for viewing mdt -> view CRM_TEMPLATE_CONOBJ

zisu_virt_attr_week_co -> Plant determination

Tax Jurisdiction code in US, mandatory

epdhier -> txn

CRMIbase both has internal number range because it is created through MDT

Create a MDT in ECC

because it is created through MDT

Business agreements

Number range for BA classBA01 -> 500000 - 5999999 (Internal) in crm and ext in eccfor maintaining custominzing without logic we maintain another number range 100000 (ext) in crm and internal in isu

mapping b/w ba class and master contract acc

we must have reference contract accounts in all systems, dev, quality and prod

ba type Z001 , z002

master contract acc is a template to fill mandatory fields which are not available in ba in crmwe need BP for master contract acc ( this is a isu BP

when u create mdt you need to release it as well

you can create collective contract account from crm from EHP2