1 / 9

Key Solution Manager Documentation

Key Solution Manager Documentation. Fit Gap Document Process Definition Document Functional Specification Document Configuration Form Technical Specification Document Change Request Form Test Problem Report Other documentation Additional Documents Master Data Standards

noelani-eaton
Download Presentation

Key Solution Manager Documentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Key Solution Manager Documentation • Fit Gap Document • Process Definition Document • Functional Specification Document • Configuration Form • Technical Specification Document • Change Request Form • Test Problem Report Other documentation • Additional Documents • Master Data Standards • Security Design Change

  2. Key Document Types in Solution Manager Naming Standard: <MKT>_<TEAM>_<DOCTP>_<SQ>_<DSCRP> MKT = Market TEAM = Functional Team DOCTP = Document Type Abbreviation SQ = Sequence (if more than 1 doc required) DSCRP = Description Example: Z_RPO1_FIN_GAP_01_Invoice Report FitGap Document • Description / Purpose • A blueprint document that follows the REQ (if REQs are in use), that clarifies the details of the requirement and SAP impacts. • The GAP defines the solution and solution alternatives, which may include the identification of process, configuration, or code changes • Abbreviation • GAP • Document Types in SolMan • ZGAP • ZGP1 • When • Business Blueprint • What Level in the BPH? • Underneath the REQ, if exists • Process • Any level possible • Tab • Project Documentation • Pre-Requisite • PIRT Review Workshop • REQ (if in use) • Approvals • Market Functional • GCOE Functional

  3. Key Document Types in Solution Manager Naming Standard: <MKT>_<TEAM>_<DOCTP>_<PROC> MKT = Market TEAM = Functional Team DOCTP = Document Type Abbreviation PROC= Process Name as in BPH Example: Z_RPO1_OPS_PDD_Purchase Order Processing Process Definition Document • Description / Purpose • A representation of the current process definition, that is initially created in blueprint but updated throughout the project and during sustain • Includes a process model from ARIS, and a process narrative describing the process and local variations. • Abbreviation • PDD • Document Types in SolMan • ZPDD • When • Business Blueprint • Updated in All other Phases • What Level in the BPH? • Process, 1 per • Tab • Project Documentation • Pre-Requisite • PIRT Review Workshop (100% PDDs updated) • GAP only if changes identified • Approvals • Market Functional • Sector Functional • GCOE Functional

  4. Key Document Types in Solution Manager Naming Standard: <MKT>_<TEAM>_<DOCTP>_<RICEFNAME> MKT = Market TEAM = Functional Team DOCTP = Document Type Abbreviation RICEFNAME= Name of the WRICEF Example: Z_RPO1_FIN_FSI_SHIP CONFIRM To EDI Functional Specification Document • Description / Purpose • A business and functional description of the WRICEF or BI development. Includes system characteristics and other information such as complexity and priority • Abbreviation • FSD, generally • FSR, FSI, FSE, FSF, FSW, FSB specifically • Document Types in SolMan • ZFSR, ZFSI, ZFSE, ZFSF, ZFSW, ZFSB • When • Business Blueprint • Updated in other phases if change request • What Level in the BPH? • Directly under the GAP • Process • Any level possible • Pre-Requisite • GAP • PDD • Approvals • Market Functional, Onsite Development Coordinator • Sector Functional • GCOE Functional, GCOE Technical

  5. Key Document Types in Solution Manager Naming Standard: <MKT>_<TEAM>_<DOCTP>_<SQ>_<IMGOBJ> MKT = Market TEAM = Functional Team DOCTP = Document Type Abbreviation SQ = Sequence (if more than one is required) IMGOBJ = IMG Object Name Example: Z_RPO1_FIN_GCF_01_Define Correspondence Type Configuration Form • Description / Purpose • A blueprint document that describes the design of configuration. Some objects are considered global configuration and some local, based on a global / local list. • PIRT provides starter configs to help accelerate configuration documentation • Abbreviation • GCF and LCF • Document Types in SolMan • ZGCF • ZLCF • When • Business Blueprint • What Level in the BPH? • Process Step • Tab • Configuration • Pre-Requisite • PDD • GAP if for change • Approvals • Market Functional • GCOE Functional

  6. Key Document Types in Solution Manager Naming Standard: <MKT>_<TEAM>_<DOCTP>_<RICEFNAME> MKT = Market TEAM = Functional Team DOCTP = Document Type Abbreviation RICEFNAME= Name of the WRICEF Example: Z_RPO1_FIN_TX1_SHIP CONFIRM To EDI Technical Specification Document • Description / Purpose • A detailed document for a RICEF or BI • Abbreviation • TSD, generally • TSD and TSB to differential BI • Document Types in SolMan • ZTSD, ZTX1, ZTSB • When • Realization Construct • What Level in the BPH? • Directly under the FSD • Process • Any level possible • Tab • Project Documentation • Pre-Requisite • FSD • Approvals • GCOE Global Delivery • GCOE Technical

  7. Key Document Types in Solution Manager • Naming Standard: • <MKT>_<TEAM>_<DOCTP>_<ALM>_<DSCRP> • MKT = Market • TEAM = Functional Team • DOCTP = Document Type Abbreviation • ALM = ALM QC defect/change number • OVSD or GSM # if hypercare or sustain • DSCRP = Description • The following attributes need to be filled in: • Technical Name = RICEF Number • Testing Phase = FUT, SIT, UAT, etc from drop down • RICEF Development Impact = Y if requires development changes, N if it doesn’t • *If related to a RICEF, the RICEF # should be added to the technical name field in SolMan as well • Example: Z_RPO1_FIN_CRF_01_Invoice Report Change Request Form • Description / Purpose • A post-blueprint document that identifies and approves changes to the existing blueprint design (process, developments, configuration). • Works in conjunction with other design documents. May required PMO review on major changes • Abbreviation • CRF • Document Types in SolMan • ZCRF • When • After Blueprint • What Level in the BPH? • Under PDD or FSD • Process • Tab • Project Documentation • Pre-Requisite • Blueprint Sign-off • Approvals • Depends on nature of change, see document flows

  8. Key Document Types in Solution Manager • Naming Standard: • <MKT>_<TEAM>_<DOCTP>_<ALM>_<DSCRP> • MKT = Market • TEAM = Functional Team • DOCTP = Document Type Abbreviation • ALM = ALM QC defect/change number • OVSD or GSM # if hypercare or sustain • DSCRP = Description • The following attributes need to be filled in: • Technical Name = RICEF Number • Testing Phase = FUT, SIT, UAT, etc from drop down • RICEF Development Impact = Y if requires development changes, N if it doesn’t • *If related to a RICEF, the RICEF # should be added to the technical name field in SolMan as well • Example: Z_RPO1_FIN_TPR_334_Inv Rpt Wrong Values Test Problem Report • Description / Purpose • A post-blueprint document that describes the detailed configuration or development defect as a result of testing, and the changes or steps needed to resolve the defect in SAP. • For integration testing, TPRs will be created after a defect is logged in a standard testing tool such HP Quality Center. • Abbreviation • TPR • Document Types in SolMan • ZTPR • When • After Blueprint • What Level in the BPH? • Under PDD or FSD • Process • Tab • Project Documentation • Pre-Requisite • FUT completed • If Integration testing, QC defect is required first • Approvals • Market Functional • GCOE Functional

  9. Global Ways of Working Extract for Document Status FlowsAvailable in PO1 eRoomhttps://teamwork.pepsico.com/eRoom/PI-SAP/RussiaPhase1C/0_f698b

More Related