SAP Landscape Strategy.docx

SAP Landscape Strategy.docx

《SAP Landscape Strategy.docx》由会员分享，可在线阅读，更多相关《SAP Landscape Strategy.docx（41页珍藏版）》请在冰豆网上搜索。

SAPLandscapeStrategy

Entergy

SAPEnvironmentStrategy,

Managementand

Control

（TheSMCDocument）

Version1.0

TableofContents

Introduction4

Objective4

Approach4

Assumptions4

SAPChangeOverview6

Concepts6

SAPBasics:

InstancesandClients6

Changes:

ClientDependentandClientIndependent6

TransportSystem7

TheDevelopmentPath8

Landscape9

NamingConventions9

SAPSystemID9

ClientID9

LandscapeStrategy11

SAPSystems11

SYSTEMINVENTORY12

SYSTEMESTABLISHMENT12

SAPClientOverview13

PLY-PlayboxSystem13

DDVandRDV-DevelopmentSystems14

DQAandRQA–QualityAssuranceSystems15

DPSandRPS-ProductionSupportSystems16

DPDandRPD-ProductionSystems16

SAPChangeControl17

ChangeTypes17

CustomDevelopment/Enhancement（ClientIndependent）17

Modifications（ClientIndependent）17

Configuration/Customization（ClientDependent）18

Authorizations（ClientDependent）18

ABAPQueries（ClientDependent）19

SAPScript19

SAPForms（PrintWorkbench）19

Corrections（ClientIndependent）19

ChangeSchedule19

CustomObjects&Modifications&Corrections（ClientIndependent）20

Configuration（ClientDependent）20

ClientManagement20

KeepingtheSystemsSynchronized21

ReleasingTransports21

TransportingStrategy22

DevelopmentPhase（Pre-Live）23

LivePhase23

TheChecklogScript24

ClientCompares24

DevelopmentRoles&Responsibilities25

ConfiguratorResponsibilities25

DeveloperResponsibilities25

ObjectModification25

CTSAdministratorResponsibilities26

Transport/CorrectionVerification26

Maintainthetransportsystem26

Release/exporttransports.27

Performimports.27

Maintaintheintegrityoftheclientsacrossthelandscape.27

DataDictionaryAdministrator（DDA）27

TechnologyResponsibilities28

ClientExports28

ClientRefresh28

DBExport/Import28

LandscapeIntegrity28

Appendix29

Terminology29

SystemLandscape29

SAPSystem29

SAPSystemIdentification29

Client29

Customizing29

Development29

TechnicalSettings30

WorkbenchOrganizer30

SystemGroup30

ConsolidationRoutes30

DevelopmentClasses30

SystemChangeOptions30

ClientAttributes31

PLY-PlayboxSystem31

DDVandRDV-DevelopmentSystems31

DQAandRQA–QualityAssuranceSystems32

DPTandRPT–ProductionTestSystems33

DPDandRPD-ProductionSystems33

Introduction

Objective

1.TheobjectiveofthisdocumentistoprovideanoverviewandstrategyfortheSAPEnvironmentfromdevelopmentphasethroughtotheproductivesystem.

2.Thisdocumentisintendedtoprovideimplementationteamswithanunderstandingoftheenvironmentinwhichtheywillwork,howdatawillbeenhancedandmovedthroughdifferentphasesoftheproject,therolesandresponsibilitiesofdifferentgroups,andthedetailedproceduresforcontrollingtheenvironment.

Approach

TheTechnologyTeam’sprimaryapproachtoSAPenvironmentmanagementistousethefacilitiesprovidedbySAP’sCorrectionTransportSystem（CTS）tooltoensureeffectivechangemanagement.TheenvironmentoutlinedinthisdocumentprovidesaframeworkfortheuseofCTS.Inthisenvironment,developerswillusethedescribedguidelinestochangethesystem,theDataDictionary/DatabaseAdministrator（s）willmakeanynecessarymodificationstotheSAPDataDictionary,theCTSAdministrator（s）willexecuteandverifythemovementofobjectsandconfigurationdata,andtheTechnologyTeamwillprovideoverallsupport.

Theguidingprinciplefortheentireapproachtoenvironmentmanagementisflexibility.Thepoliciesandproceduresoutlinedinthisdocumentwillbere-evaluatedandadjustedasneededthroughthelifeoftheproject.

Assumptions

TheSAPLandscapeStrategyproposedinthisdocumentissupposedtoaddressthefollowingbusinessscenario:

⏹all4statescurrentlyservedbyEntergy:

Arkansas,Louisiana,MississippiandTexas.

⏹all5jurisdictionscurrentlyservedbyEntergy:

Arkansas,Louisiana,Mississippi,TexasandNewOrleans.

⏹phasedconversionapproach

Date

State

#ofMeters

Jun-01

Texas

350K

Jul-01

Arkansas

670K

Jan-02

Louisiana

790K

Oct-02

MississippiandNewOrleans

1050K

⏹deregulatedenvironment,withdistributionandretailasseparatebusinessunits,inArkansas,TexasandLouisiana.

⏹regulatedenvironmentinMississippiandNewOrleans.

Consideringallabovementionedbusinessrequirements,therewillbetwoSAPlandscapes:

onefordistributionandanotherforretail.

SAPChangeOverview

Concepts

SAPBasics:

InstancesandClients

AsimpleSAPsystemisknownasanSAPInstance.VisualizeanSAPInstanceasitsowncopyofSAPjustasifitwereanyotherprogram.Eachinstancehasitsowndatabase,binaryfiles,dataetc.TheSAPInstanceisidentifiedbyaSystemID（）.TheSystemIDisauniqueidentifierforanSAPinstanceanddatabasewithinthesystemlandscape.

WithineachSAPInstance,thereareclients.Clientsareself-containedunitsinSAPInstanceswithseparatemasterrecordsandtheirownsetofdata.TheClientIDisa3digituniqueidentifierwithinanSAPSystem.

WhenonelogsintoSAP,onemustspecifyboththeinstanceandclienttheyarelogginginto.

AdiagramwiththesetofSAPinstancesproposedforEntergycanbeseenonpage11.AnotherdiagramdescribingtheproposedSAPclientswithineachSAPinstancecanbeseenonpage13.

SeeTerminology,onpage29,forfurtherinformationonbasicSAPterminologyandconcepts.

Changes:

ClientDependentandClientIndependent

ChangestoanSAPenvironmentcanbeclassifiedinoneoftwocategories:

ClientIndependent&ClientDependent.Asthenamesindicate,ClientDependentChangesaffectonlyoneclientinanSAPinstance.Thesechangesaretypicallytodata,aseachclientmaintainsitsownset.ClientIndependentChangesaffectalltheclientswithinanSAPinstance.ThesechangesareusuallyABAPprogramsandDataDictionarychangeswithinthesystem.TheoverallperspectiveofanSAPinstanceregardingthemajorcategoriesofclientdependentandindependentdataisdepictedinFigure1below.

Figure1-ClientDependentandClientIndependentData

Note:

Whenobjectsaremigratedacrosssystems,theyhaveatargetinstanceandtargetclientassociatedwiththetransport.ClientIndependentObjectswillchangetheentireinstance（alltheclients）,regardlessoftheclientspecifiedinthetransport.Clientdependentchangesmustbeappliedtoeachclientinthetarget（recipient）system.

TransportSystem

Thetransportsystemisusedtotransferobjects（programs,customizingconfiguration）fromoneSAPsystemtoanother,oroneinstanceclienttoanotherbygroupingobjectstogetherinatransport（alsoreferredtoasaChangeRequest）.Transportscontainalistofobjectstobemigrated.

SAPhasbuiltinfunctionalitytotrackchangesmadetoitssystemandrecordthesechangesintransports.Thisisaccomplishedviatheworkbenchorganizerandthecustomizingorganizer（Transactions:

SE09&SE10）.DevelopmentandCustomizinginSAParefullyintegratedwiththesetwotools,andprovidedtheworkisbeingdoneintheappropriateclientsprescribedinthelandscapestrategy,changestothesystemwillbeautomaticallyrecorded.

Changerequestshelpmanagedevelopmentefforts.Asaconsequenceofincludingdevelopmentobjectsinatransport,theobjectsbecomeprotected（locked）fromotherdevelopersmodifyingthesameobject.Forthemostpart,whenworkingondevelopmentobjects,SAPassignsatransportrequesttotheobjectbeingworkedon.Eachchangerequesthasanowner,andonlytheownermayworkontheobjectlockedbythechangerequest.Thisensuresthatnotwopeopleworkonthesamedevelopmentobjectatthesametime.Inorderforsomeoneelsetobeginworkonthesameobject,thechangerequestfortheobjectmustbereleased,thusreleasingthelockontheobject.（Analternativemethodistochangeownershipofthechangerequest,thenlockingthepreviousownerout）.

Changerequestsalsomanageconfigurationefforts.Theyprovideamechanismfortrackingallchangestoconfiguration.Statuscanbecheckedonthetransportstoseewhichpieceshavenotbeenmigratedalongthedevelopmentpath.（seebelow）

Atransportmigrationcanbeseenashavingtwophases:

anexportandanimportphase.Whenallworkontheobjectsinthechangerequesthavebeencompleted,thetransportisreleasedfromthedevelopmentsystem.Releasingatransportinitiatestheexportphase.Exportingcausesallthechangestotheobjectsinthetransporttobewrittenouttoafileintheoperatingsystem.Thisfilecontainsasnapshotoftheobjectsinthetransportatthetimethetransportwasreleased.Nowtheobjectsareunlocked,freeforsomeoneelsetoworkon.Thesecondphaseistheimportintotherecipientsystems.ThisimportisdoneattheOperatingSystemlevel.

ExportingandImportingoftransportsinthesamesequenceonrespectivelysourceandtargetsystemsiscriticaltoensurethecorrectsynchronizationofsuchsystems.KeepingtheSystemsSynchronized,onpage21,providesdetailedinformationonproposedprocedurestoaddressthisissue.

TheDevelopmentPath

DevelopmentProjectsarenottypicallycarriedoutinasinglesystem,butinaseriesofsystemsspanningdevelopmenttotesttoproductionsystems,dependingonprojectsize.Adevelopmentenvironmentismaintainedtoensuretheintegrityoftheproductionsystem.Changestoaproductionsystemshouldbecreatedandtestedbeforetheyaremadeontheproductionenvironmenttopreventerrorsfromenteringthefinalsystem（especiallywhenProductionislive!

）.Thisprojecthasdefinedamigrationpaththatallconfigurationanddevelopmentchangesmustfollowtoreachtheproductionenvironment.Thisdevelopmentpathis