BI Starter kit 2.0

SAP BI Project Starter Kit

Accenture Delivery Suite (ADS): The foundation for Accentures industrialized methods, tools, and procedures.Accenture Delivery Suite

Accenture Methods LibraryTo support the variety of work it does, Accenture has organized a methods library, where each book is focused on a particular type of project. An engagement selects the methods that are relevant to its situation.aa

ADM Overview

ADM High-Level BasicsStagesWorkstreamsActivityTransitionPointsLink for access to Accenture ADM for Custom Development Projects:https://idcquality.accenture.com/customdevelopment/content/frameset_home.asp

ADM Activity LevelTaskTransitionPointShared Task(shaded)ValidationTask3100 Design Application

ADM Task Level

ADM Resources and GuidanceWho is responsible for creating the itemWho uses it where it is in terms of the project lifecycleTemplates and Samples of the deliverable. They represent best practice examples of how the specific deliverable should be constructed. All Deliverables in ADM provide direction on:

ADM Project Life Cycle

Navigation

Click the Next button to proceed to the next slide or jump to the appropriate slide.

Click the Back button to return to a previous slide.

Click the Home button to return to the beginning.Use the buttons to navigate the ADM lifecycle journey.

Choose your own ADM Adventure

Plan: Deliverables / ActivitiesAt this stage, your project should have the following items and complete the associated activities:Signed contract along with documented and analyzed sponsor goals / objectivesValid business case that has been reviewed and approvedDocumented project estimating factors, guidelines, assumptions, and worksheetsProject scope documented and approved by stakeholdersSolution blueprint documented, analyzed, refined, and placed under Configuration Management

Plan: Deliverables / ActivitiesAt this stage, your project should have the following items and complete the associated activities:Project work plan documented, analyzed, refined, and placed under Configuration ManagementTrack against the work planConduct verification on products and services when selecting and acquiring technology, hardware or softwareEntry / exit criteria to determine readiness to leave the plan stage and begin analysis

Plan: Deliverables / ActivitiesAt this stage, your project should have the following items and complete the associated activities:PM120* Project Management Plan PM132* Quality Management Plan PM129* Risk Management Plan PM111* Project Metrics Plan PM134* Configuration Management Plan Note: All plans must be documented, reviewed, and communicated to project team members.Link for access to description of plans and IDC Templates:https://idcquality.accenture.com/customdevelopment/content/frameset_home.asp Click on > Deliverables > View Alphabetically

Plan: Process AreasSupplier Agreement Management (SAM) : Manage the acquisition of products from suppliers for which there exists a formal agreement. Measurement & Analysis (M&A) : Develop and sustain a measurement capability that is used to support management information needs.Process & Product Quality Assurance (PPQA) : Provide staff and management with objective insight into processes and associated work products.

Plan: Decision PointProceed to the appropriate slide to learn more about a particular work stream in the Plan stage.ApplicationTechnical ArchitectureTraining & Performance SupportService Introduction

Plan: ApplicationVerify all assumptions around high-level requirements for the application by interviewing sponsors and other key stakeholders.Develop an application blueprint that provides a starting point for further analysis of the requirements and design effort.If ongoing support of the application is included, the application blueprint should also address the application maintenance solution.

Plan: Technical ArchitectureDevelop a technology blueprint that defines the various technical environments to support the applications development, testing, deployment, and operation.Perform further analysis and design of these technical environments in later stages.

Plan: Training & Performance SupportIdentify the existing organization, skills, and people affected by the new application. Analyze the changes (brought by the processes and application) and define a plan for enabling the people and organization. In the Analyze stage, conduct a more detailed organization impact assessment to identify the specific changes required to prepare people and organization for the new capability.

Plan: Service IntroductionConfirm sponsor goals and expectations are captured and communicated. Arrange for appropriate resources to act as advisors in developing solution blueprints to provide input on meeting operability requirements, facilitate the development of the best solution, and better determine how the proposed solution will impact users.Ensure the project scope definition is clarified in terms of the responsibility for providing post-implementation support via a warranty period or other agreement.

Analyze: Deliverables / ActivitiesAt this stage, your project should have the following items and complete the associated activities:Documented detailed procedures and techniques for requirements gathering and analysisRequirements gathered, documented, analyzed, refined, baselined, and placed under Configuration ManagementReview requirements for impact to scope, quality, effort, resources, time, and potential risksRequirements Traceability Matrix that can be traced bi-directionallyConduct an impact analysis when requirements change and update all documentation accordinglyEntry / exit criteria to determine readiness to leave the analyze stage and begin design

Analyze: Process AreasRequirements Development (RD) : Produce and analyze customer, product, and product-component.Requirements Management (REQM) : Manage the requirements of the project's products and product components and to identify inconsistencies between those requirements and the project's plans and work products.

Analyze: Decision PointProceed to the appropriate slide to learn more about a particular work stream in the Analyze stage.ApplicationTechnical ArchitectureTraining & Performance SupportService Introduction

Analyze: ApplicationIdentify and document application requirements and metrics. Further clarify the functional requirements via use cases. Create a functional abstraction of the application (data model, class definitions, etc.) as a starting point or first iteration for the application design.

Analyze: Technical ArchitectureUnderstand and document the technical requirements. Understand the current technical architectures. Define how application and technical elements interact. Identify the technical environment required to support the application architecture requirements. Define application programming guidelines and standards. Identify technical options for each major component. Develop an understanding of the technical security needs and considerations.

Analyze: Technical ArchitectureObtain sign-off for requirements from business owners to manage scope. Define approach to be employed for conducting product and performance tests. Validate the analysis with stakeholders and transition the technical architecture analysis to the Design Team.

Analyze: Training & Performance SupportDefine requirements that enable affected users and application support staff to effectively execute new processes and use new applications. Analyze and summarize the impact of the new processes and technologies on the organization.Define the training, performance support, and communication strategies.Identify training, performance support, role / job, and communication technical requirements, and communicate them to the Technical Team.Determine the work effort and cost estimate to execute job design, training and performance support, and communications strategies.

Analyze: Service IntroductionWork closely with the Service Introduction Lead to identify and understand operations requirements: operability, portability, ease of maintenance, documentation, etc.Involve the Service Introduction Lead in the review of the requirements document to ensure that operations requirements are fully captured.

Design:Deliverables / ActivitiesAt this stage, your project should have the following items and complete the associated activities:Documented standards, detailed procedures, and techniques for designConceptual, general, detailed, and interface design documentationSpecifications and designs for the required environments and technical architectureService Introduction PlanApplication Development Standards documented, placed under Configuration Management, and updated as neededEntry / exit criteria to determine readiness to leave the design stage and begin building

Design: Process AreasTechnical Solution (TS) : Design, develop, and implement solutions to requirements. Solutions, designs, and implementations encompass products, product components, and product-related life-cycle processes either singly or in combinations as appropriate.

Design: Decision PointProceed to the appropriate slide to learn more about a particular work stream in the Design stage.ApplicationTechnical ArchitectureTraining & Performance SupportService Introduction

Design: ApplicationCreate the application design from the requirements, use cases, and other analysis deliverables. Adapt the design to address quality requirements and technical constraints.Refine the design until it contains enough information for detailed design and build.

Design: Technical ArchitectureCreate the technical architecture design. Adapt the design to meet quality requirements, technical constraints, and performance requirements. Refine the design until it satisfies the technical requirements. Create the component and assembly test plans.

Design: Training & Performance SupportDesign a cost-effective, integrated change enablement solution that leverages training, performance support, communications, and job design to achieve successful application deployment and sustained human performance. Design a communication plan that builds awareness and understanding of forthcoming process and technology changes across various user and stakeholder groups.

Design: Service IntroductionEnsure ongoing acceptance and readiness activities are conducted in conjunction with the development project. Provide input to the Deployment Plan and Deployment Work Plan. Ensure a Service Introduction Plan that addresses the activities necessary to update the unit operations to accommodate the new application in all areas, including Operational Level Agreements with third party suppliers, is developed.

Build:Deliverables / ActivitiesAt this stage, your project should have the following items and complete the associated activities:Application Development Packages including: stored procedures, source code, and shellsEntry / exit criteria to determine readiness to leave the build stage and begin testing

Build: Process AreasTechnical Solution (TS) Level 3: Design, develop, and implement solutions to requirements. Solutions, designs, and implementations encompass products, product components, and product-related life-cycle processes either singly or in combinations as appropriate.Product Integration (PI) Level 3: Assemble the product from the product components, ensure that the product, as integrated, functions properly, and deliver the product.

Build: Decision PointProceed to the appropriate slide to learn more about a particular work stream in the Build stage.ApplicationTechnical ArchitectureTraining & Performance SupportService Introduction

Build: ApplicationRefine the application design until it is concrete and detailed enough to be implemented. Build and test the application classes and components. Integrate all the individually developed and tested components into an executable application.

Build: Technical ArchitecturePerform a detailed design of the technical architecture components and services. Build and component test the technical architecture components and services. Transition the technical architecture components and services to the Test Team.

Build: Training & Performance SupportDevelop a cost-effective, integrated change enablement solution that leverages training, performance support, communications, and job design to achieve successful application deployment and sustained human performance. Develop communication materials that build awareness and understanding of forthcoming process and technology changes across user and stakeholder groups. Create a skill and knowledge assessment plan to ensure training and performance support work effectively. Support the client transition to new job designs.Assist with identifying and implementing the impacts / changes to Human Resources (HR) processes.

Build: Service IntroductionEnsure ongoing acceptance and readiness activities are conducted in conjunction with the development project. Provide input to the Deployment Plan and Deployment Work Plan. Ensure a Service Introduction Plan that addresses the activities necessary to update the unit operations to accommodate the new application in all areas, including Operational Level Agreements with third party suppliers, is available.

Test:Deliverables / ActivitiesAt this stage, your project should have the following items and complete the associated activities:Test plan, test conditions, expected results, and test scripts to test the applicationEntry / exit criteria to determine readiness to leave the test stage and begin deployment

Test: Process AreasVerification (VER) Level 3: Ensure that selected work products meet their specified requirements. Validation (VAL) Level 3: Demonstrate that a product or product component fulfills its intended use when placed in its intended environment. Product Integration (PI) Level 3: Assemble the product from the product components, ensure that the product, as integrated, functions properly, and deliver the product.

Test: Decision PointProceed to the appropriate slide to learn more about a particular work stream in the Test stage.ApplicationTechnical ArchitectureTraining & Performance SupportService Introduction

Test: ApplicationPrepare and execute the assembly test to ensure classes and components work correctly when integrated.Prepare and execute the product test to ensure each application meets the functional requirements and that all applications work together. Prepare and execute the performance test to ensure the application meets all the performance-related metrics, such as response time, availability, load / throughput, and reliability. Prepare and execute the user acceptance test.

Test: Technical ArchitectureConduct the assembly test to ensure technical components work correctly once assembled. Conduct the product test to ensure the overall technical architecture meets all the functional requirements. Conduct the performance test to ensure the technical architecture meets all performance-related metrics, such as response time, availability, and load / throughput. Properly implement the technical architecture design and ensure the infrastructure can support the development, execution, and operations environments. Ensure the new technical architecture integrates properly.

Test: Training & Performance SupportImplement communications that promote user and stakeholder buy-in.Execute the training development test and training pilot to assess training and performance support effectiveness. Identify and perform required fixes for training and performance support materials.Prepare deployment logistics for training and performance support. Support the transition to new job designs.Identify impacts / changes to the Human Resources (HR) processes required to support new organization and assist with implementation.

Test: Service IntroductionPrepare for application deployment.Ensure the unit is ready to support the application.Integrate with Support Team.Complete transition of the application to the permanent Support Team. Complete knowledge transfer from Application Development Team members to Support Team members.

Deploy:Deliverables / ActivitiesAt this stage, your project should have the following items and complete the associated activities:Physical asset and resource deployment needs documented and reviewedHandover documentation created and approvedDocumented deployment approach and detailed proceduresConduct configuration auditsPhysically migrate changes to productionPerform installation verificationEntry / exit criteria to determine readiness to leave the deployment stage

Deploy: Process AreasProduct Integration (PI) Level 3: Assemble the product from the product components, ensure that the product, as integrated, functions properly, and deliver the product.

Deploy: Decision PointProceed to the appropriate slide to learn more about a particular work stream in the Deploy stage.ApplicationTechnical ArchitectureTraining & Performance SupportService Introduction

Deploy: ApplicationWork closely with the application team to monitor progress in preparing application for deployment. Work with the Technical Team to prepare the training environment.Monitor product testing and user acceptance testing. Confirm what is and is not included in each application release so the team can convey the right message.Ensure the data is correct for the target deployment audience and customization requirements are complete. Clarify all known bugs and the plan for fixing.Ensure the training environment is ready with the correct data populated. Confirm the contact person responsible for responding to questions.

Deploy: Technical ArchitectureWork with the Technical Architecture Team to ensure the plan and procedures for setting up the production and operating environments are ready. Complete the following items:Confirm all the necessary planning and preparation for installing production and operating environments were completed. Confirm all the technical infrastructure customization requirements for the target deployment site were fulfilled. Identify a contact person from the Technical Architecture Team for any questions related to these environments. Ensure the installation, configuration, and testing documentation contains any changes experienced during the actual set-up and operational readiness testing.Review the business contingency plan thoroughly.

Deploy: Training & Performance SupportWork with the Training and Performance Support Team to ensure the training, performance support, and communication materials are ready, logistics are set up, trainers are enabled, and participants are confirmed. Complete the following items:Confirm the training and performance support products were tested and are ready for use. Confirm who to train and when.Confirm that the necessary training logistics were set up before the training begins. Confirm that trainers and coaches (if used) are ready and available for conducting the sessions.Confirm the communication materials readiness, the communication sender, list of recipients, and the time to send the communications.

Deploy: Service IntroductionEnsure all the agreed hand-off documentation is provided including system documentation and sign-offs indicating user and applicable acceptance.Actual handover of support from development to the application management team generally happens on graduated basis. Two areas for consideration are the scheduling of the handover tasks and procedures for backing out the system in the case of unsuccessful deployment. Deployment of operational / application support staff to the relevant development areas during acceptance and readiness activities will be invaluable in this respect.

Choose your own ADM AdventureAll project stages have now been reviewed.Continue on to the following slides to learn about organizational processes.

As IsReport InventoryKey Business Questions AnsweredBI Business Events (PL101)BI Functional Designs(AP350)BI Technical Designs(AP450)BI Development List (AP250)BI System Test (TE580, TE583)BI Training DeliverablesBI Batch StreamBest Practices / Business ContentBlueprint & PlanningDesign & BuildTestTraining & Business ReadinessVolume / PerformanceTestUser Acceptance TestBI Unit TestBI SecurityBI Methodology

BI Methodology Blueprint & PlanningAs IsReport InventoryKey Business Questions AnsweredBest Practices / Business ContentBlueprint & Planning Review what the company does today Interrogate for Key Calculations, Hierarchies, Characteristics Identify which ones relevant post SAP Transformation Assign Business Events Interview Sr. Management to identify current key business information gaps Validate if SAP Transformed processes will be able to support requirements If yes, incorporate in Business Events If no, communicate back to Sr. Management and decide if process reengineering is required Look for opportunities to incorporate Industry Best practices in terms of metrics Leverage Consultants prior experience Use SAP Business Content as an accelerator BI Business Events (PL101) Breaks down a business requirement into 3 components (Master Data, Transaction Data, Data Retrieves) Drives all other phases of the project

BI Methodology Design & BuildBI Functional Designs (AP350)BI Technical Designs (AP450)BI Development List (AP250)Design & Build Documents a Solutions Defines the Business requirements, key questions answered etc Identifies for the developer the technical requirements (Cube(s), ODS(s), Data Source(s), etc) Translate the functional requirements into technical designs Will consist of a technical design for all BW Development objects Contains the inventory of all the development objects and links them to the Business events The Development List will be the source for project status updatesUnit Test This Test will be conducted in Development box Functional Specification writer documents the approach and what needs to be tested Developer conducts the Unit Test, documents the results and reviews with Functional owner Must pass functional requirements before transporting to Q

BI Methodology TestingSystem Test (TE580, TE583)Volume / Performance TestUser Acceptance TestTest Through End-To-End Testing of BI Solution Functional Specification writer to document Test Cases and Test Sets in Test Director This test ensures the stability of the software from a Volume and End User perspective Driven by the Basis Team Final validation with the key end users prior to go live

BI Methodology Training & Business ReadinessBI Training DeliverablesTraining & Business Readiness Use the Business Events to design the content (MD, TD, DR) aspect of the trainingBI Batch StreamBI Security Define BI Batch Stream using Visio Flows Work with Business to: Map Reports to Roles Map Roles to Authorization Objects End Users to Roles and Authorization Values

BI - Design TemplatesAP350 Functional DesignAP450 Technical Design

Functional Specification Design Document (AP350)

Project

Accenture Transformation

Work Stream

Business Intelligence

Process

Title

Type

Functional Specification

Document Identifier (Business Event Number)

Complexity

Medium

Approval Authority for

Functional Design Document Approval


Name

Signature

Date

Revision History

Author

Version

Rev. date

Summary of Changes

Section

Page

Transport Summary

Transport #

Description

Related Customizing Activity

Date

Table of Contents

41.Info Cube Overview

41.1Naming

41.2Description

41.3List Of Reports

52.Business Functionality Overview

52.1Business Functionality

52.2Security Considerations

52.3Business Dependencies

52.4Process Chain Considerations

52.5Assumptions

52.6Pictorial View Overall business flow diagram

63.Info Cube Specifications

63.1Data Mapping and Conversion

63.2Info Cube Specifications

74.Other Detailed Specifications

74.1Process/Data Flow Diagram

74.2Frequency and Volume

74.3Change Log

74.4Test Specifications

85.Approvals

85.1Business Approval

1. Info Cube Overview

1.1 Naming

Technical Name

Display Name

1.2 Description

1.3 List Of Reports

2. Business Functionality Overview

2.1 Business Functionality

2.2 Security Considerations

2.3 Business Dependencies

2.4 Process Chain Considerations

2.5 Assumptions

2.6 Pictorial View Overall business flow diagram

3. Info Cube Specifications

3.1 Data Mapping and Conversion

3.2 Info Cube Specifications

4. Other Detailed Specifications

4.1 Process/Data Flow Diagram

4.2 Frequency and Volume

4.3 Change Log

Date

Description of the Change

4.4 Test Specifications

Unit Test Information

Expected Results

Actual Results

SAP Client where tested

Date Test was Performed

Tester Name

5. Approvals

5.1 Business Approval

***End of Document***

AP3503

Page 5 of 8

Last Modified: 3/26/2007

Header

Technical Specification Design Document

ProjectAccenture Transformation

Work StreamBusiness Intelligence

Process

Title

Type

Document Identifier (Business Event Number)

Complexity

Approval Authority For Technical Design Document

NameSignatureDate

Revision History

Defect / Requirement IdDate of ChangeUser Making ChangeDescription of Change

&CGA Technical Specification&A

&L&8&F &A&D &TStatus: Formalized For ACT Approval &R&8&P &N

InfoObject_List

NEW OR CHANGEINFOOBJECTTYPETECHNICAL NAMEREFERENCE OBJECT TECHNICAL NAMESHORT DESCRIPTION(MAX 20)LONG DESCRIPTION(MAX 60)DATA TYPE NAMEDATA LENGTH NUMBERCONVERSION ROUTINE NAMEEXCEPTION TO BEX SETTINGS STANDARDSMASTER DATA INDICATORTEXT INDICATORHIERARCHY INDICATORTIME DEPENDENT INDICATORAUTHORIZATION OBJECT INDICATORINFOOBJECTINFOSOURCE WITH DIRECT UPDATEINDICATORINFOOBJECT CHARACTERISTICIS A DATA TARGET INFOPROVIDERINDICATORINFOOBJECTEXPORT DATASOURCEINDICATORCOMPOUNDING INFOOBJECT TECHNICAL NAME-1BUSINES DEFINITIONBUSINES RULESCOMMENTS


&L&8&F &A&C&8&D&R&8Page &P of &N

Field Type CHAR = characteristic TIME = time characteristic KF = key figure NAV = navigational attribute COMP = Compounding ATR = Attributes Hier = Hierarchy

Unit unit of measure or currency for KF



InfoProvider_And_Mstr_Data_List

NEW OR CHANGEOBJECT TYPE CODETECHNICAL NAMEOBJECT TEMPLATE TECHNICAL NAMESHORT DESCRIPTION(MAX 20)LONG DESCRIPTION(MAX 60)SOURCESYSTEMNAMEDELTA OR FULL LOADOBJECT ROW CNTDELTA ROW CNTPREDICTED GROWTHROW CNTBEX ENABLED ODS INDICATORINFOAREA TECHNCIAL NAMESTARTROUTINEINDICATORINFOSPOKE FILE NAME OR TABLENAMEINFOSPOKEEXPORT FILE DIRECTORYCOMMENTS

&CGA Technical Specfication&A




Start_Routine_List

TARGET TECHNICAL NAMESOURCE SYSTEM NAMESOURCE TECHNICAL NAMETRANSFER RULE OR UPDATE RULEINFOSOURCE TECHNICAL NAME(IF TRANSFER RULE)START ROUTINE PSEUDO LOGIC(This is not a copy and paste of ABAP code)LOOKUP OBJECT TECHNICAL NAME-1LOOKUP OBJECT TECHNICAL NAME-2LOOKUP OBJECT TECHNICAL NAME-3LOOKUP OBJECT TECHNICAL NAME-4LOOKUP OBJECT TECHNICAL NAME-5COMMENTS





Src_to_Comm_Struc_Detail

TARGETINFOSOURCETECHNICALNAMETARGETOBJECTTECHNICALNAMETARGETINFOOBJECT TECHNICALNAMETARGETINFOOBJECT LONGDESCRIPTIONDATASOURCETECHNICALNAMESOURCESYSTEMTABLENAMESOURCESYSTEMFIELDNAMETRANSFER RULE PSEUDO LOGIC

&CGA Technical SpecificationSource-to-Communication Structure&A




InfoProvider_Detail

TARGETTECHNICALNAMETARGETINFOOBJECT TECHNICALNAMETARGETINFOOBJECT LongDESCRIPTIONPRIMARY KEY AND INDEXESCUBE DIMENSIONSHORT DESCRIPTIONNAVIGATIONAL INDICATORSOURCEOBJECTNAMESOURCEINFOOBJECTNAMETRANFORMATIONTYPEMOVE TYPEUPDATE RULE PSEUDO LOGIC

&CGA Technical SpecificationInfoProvider Detail&A




Instructions

Worksheet TabNameWorksheet ColumnNameInstructions

Header---------------------Track changes to the tech spec

InfoObject_List---------------------List all new and changed InfoObjects and key figures which are part of the tech spec. Infoobjects and key figures which are being resued do not need to be listed.

InfoObject_ListNEW OR CHANGEState whether this is a new object or an existing object which is being changed

InfoObject_ListINFOOBJECT TYPEEnter the type of Infoobject: CHAR=Characteristic KF=Key Figure TIME=Time UNIT=Unit LANG=Language

InfoObject_ListTECHNICAL NAMEList the technical name of the object

InfoObject_ListREFERENCE OBJECT TECHNICAL NAMEIf there is a reference InfoObject then list the technical name

InfoObject_ListSHORT DESCRIPTIONList the short description for the object, maximum is 20 characters

InfoObject_ListLONG DESCRIPTIONList the long description for the object, maximum is 60 characters

InfoObject_ListDATA TYPE NAMEEnter the data type of the objectCHAR = character NUMC = Numbers DATS= Date TIMS=TimestampFor Key Figures, enter the type and data type combination: example: Number-Dec, or Number-FLTP

InfoObject_ListDATA LENGTH NUMBEREnter the length of the object for CHAR types

InfoObject_ListCONVERSION ROUTINE NAMEIf using a conversion routine, enter the name of an existing routine or describe the pseudo logic of the routine to be created

InfoObject_ListEXCEPTION TO BEX SETTINGS STANDARDSList any exceptions to the InfoObject BEx configuration standards

InfoObject_ListMASTER DATA INDICATORIndicate with a Y if this InfoObject will be a master data object

InfoObject_ListTEXT INDICATORIndicate with a Y if this InfoObject will have text

InfoObject_ListHIERARCHY INDICATORIndicate with a Y if this InfoObject will have a hierarchy

InfoObject_ListTIME DEPENDENT INDICATORIndicate with a Y if this InfoObject will have any time dependent settings

InfoObject_ListAUTHORIZATION OBJECT INDICATORIndicate with a Y if this InfoObject is an authorization object

InfoObject_ListINFOOBJECT INFOSOURCE WITH DIRECT UPDATE INDICATORIndicate with a Y if this InfoObject is an InfoSource with direct update

InfoObject_ListINFOOBJECT CHARACTERISTICIS A DATA TARGET INFOPROVIDERINDICATORIndicate with a Y if this InfoObject characteristic is a data target/InfoProvider

InfoObject_ListINFOOBJECT EXPORT DATASOURCE INDICATORIndicate with a Y if this Master Data InfoObject will have a master data export datasource

InfoObject_ListCOMPOUNDING INFOOBJECT TECHNICAL NAME-1List the technical names of InfoObjects used for compounding. One object per column 1-5

InfoObject_ListBUSINESS DEFINITIONEnter the business definition for the object

InfoObject_ListBUSINESS RULESEnter the business rules for the objects in the form of pseudo logic

InfoObject_ListCOMMENTSEnter any additional cooments about the InfoObject that shouyld be considered in the review

InfoProvider_And_Mstr_Data_List---------------------List all new and changed Infoproviders and master dataInrfoObjects objects which are part of the tech spec. List: MASTER DATA INFOOBJECT, INFOSPOKE, INFOSOURCE, TRANSACTION ODS, STANDARD ODS, INFOSET, MULTIPROVIDER, INFOCUBE

InfoProvider_And_Mstr_Data_ListNEW OR CHANGEState whether this is a new object or an existing object which is being changed

InfoProvider_And_Mstr_Data_ListOBJECT TYPE CODEEnter type of object using the following terms: MASTER DATA, INFOSPOKE, INFOSOURCE, TRANSACTION ODS, STANDARD ODS, INFOSET, MULTIPROVIDER, INFOCUBE

InfoProvider_And_Mstr_Data_ListTECHNICAL NAMEList the technical name of the object

InfoProvider_And_Mstr_Data_ListOBJECT TEMPLATE TECHNICAL NAMEIf the design of this object is an extact replica of another object, list the technical name of the reference object.

InfoProvider_And_Mstr_Data_ListSHORT DESCRIPTIONList the short description for the object, maximum is 20 characters

InfoProvider_And_Mstr_Data_ListLONG DESCRIPTIONList the long description for the object, maximum is 60 characters

InfoProvider_And_Mstr_Data_ListSOURCE SYSTEM NAMEEnter the source system name. Examples: PRD, PRA, CDB, MERGED

InfoProvider_And_Mstr_Data_ListDELTA OR FULL LOADFor phyiscal objects, list whether this is delta or full load

InfoProvider_And_Mstr_Data_ListOBJECT ROW CNTFor phyiscal objects, enter the number of rows that will be in the object. How this is communicated is flxible, such as rows per year. If not know, list assumptions and best guesstimate

InfoProvider_And_Mstr_Data_ListDELTA ROW CNTFor phyiscal objects, enter an estimated number of rows per delta

InfoProvider_And_Mstr_Data_ListPREDICTED GROWTH ROW CNTDescribe the predicted growth of the object in terms of the number of rows over time

InfoProvider_And_Mstr_Data_ListBEX ENABLED ODS INDICATORIndicate with a Y if this ODS is BEX Enabled

InfoProvider_And_Mstr_Data_ListINFOAREA TECHNICAL NAMEEnter the technical name for the infoarea of the object

InfoProvider_And_Mstr_Data_ListSTART ROUTINE INDICATORIndicate with a Y if there is a start routine for this object

InfoProvider_And_Mstr_Data_ListINFOSPOKE FILE OR TABLE NAMEEnter the name of the Infospoke file or table name

InfoProvider_And_Mstr_Data_ListINFOSPOKE EXPORT FILE DIRECTORYEnter the directory name of the Infospoke file

InfoProvider_And_Mstr_Data_ListCOMMENTSEnter any additional cooments about the InfoObject that shouyld be considered in the review

Start_Routine_List---------------------A list of each start routine reference in the InfoProvider_Master_Data_List

Start_Routine_ListTARGET TECHNICAL NAMEEnter the technical name for the target InfoProvider

Start_Routine_ListSOURCE SYSTEM NAMEEnter the source system name.

Start_Routine_ListSOURCE TECHNICAL NAMEEnter the technical name for the source InfoProvider

Start_Routine_ListTRANSFER RULE OR UPDATE RULEEnter the type of start routine: TRANSFER RULE or UPDATE RULE

Start_Routine_ListINFOSOURCE TECHNICAL NAMEEnter the technical name for the InfoSource if this has transfer rules

Start_Routine_ListSTART ROUTINE PSEUDO LOGICIf the start routine is new or changing, enter the generalized pseudo logic which is a summary of the code that will be built. Do not enter the code for the start routine

Start_Routine_ListLOOKUP OBJECT TECHNICAL NAME-1List the technical names of the Infoproviders used in lookups. One object per column 1-5





Start_Routine_ListCOMMENTSEnter any additional comments which may be helpful for the review

Src_to_Comm_Struc_Detail---------------------This section captures the detail for each communication structureMaster Data Infoobjects and the attributes go in this sectionCopy and create one tab for each object. Enter a row for each of the InfoObjects contained in the target communication structureOnly enter source objects where there are transformations or the names are different than the targetIf more than one source is used to load a separate InfoObject, then create a new row for each source system and repeat the target information.

Src_to_Comm_Struc_DetailTARGET INFOSOURCE TECHNICAL NAMEEnter the InfoSource technical name of the target object

Src_to_Comm_Struc_DetailTARGET OBJECT TECHNICAL NAMEEnter the object technical name of the object

Src_to_Comm_Struc_DetailTARGET INFOOBJECT TECHNICAL NAMEEnter the InfoObject technical name of the object

Src_to_Comm_Struc_DetailTARGET INFOOBJECT SHORT DESCRIPTIONEnter the InfoObject short description

Src_to_Comm_Struc_DetailNAVIGATIONAL INDICATORIndicate with a Y if this InfoObject will be navigational

Src_to_Comm_Struc_DetailDATASOURCE TECHNICAL NAMEEnter the DataSource technical name

Src_to_Comm_Struc_DetailSOURCE SYSTEM TABLE NAMEEnter the name of the table from the source system

Src_to_Comm_Struc_DetailSOURCE SYSTEM FIELD NAMEEnter the name of the field from the source system table

Src_to_Comm_Struc_DetailTRANSFER AND UPDATE RULE PSEUDO LOGICenter the generalized pseudo logic which is a summary of the code that will be built. Do not enter the exact code.If it is a straight move then enter MOVE

InfoProvider_Detail---------------------This section captures the detail for each InfoProvider, except InfoSets. See special Instructions for Infosets below.Replace the name of the tab with the object technical nameEnter a row for each of the InfoObjects contained in the target structureOnly enter source objects where there are transformations or the names are different from the targetIf more than one source is used to load a separate InfoObject, then create a new row for each source system and repeat the target information.

Infosets and Multiproviders: Document Infosets and Multiporviders in the Technical Design Overview with a diagram of the objects being joined and a summary of the logic to join the objects.

InfoProvider_DetailTARGET TECHNICAL NAMEEnter the technical name of the target object

InfoProvider_DetailTARGET INFOOBJECT TECHNICAL NAMEEnter the InfoObject technical name of the object

InfoProvider_DetailTARGET INFOOBJECT SHORT DESCRIPTIONEnter the InfoObject short description

InfoProvider_DetailPRIMARY KEY AND INDEXESEnter PK for each column which is part of the Primary KeyUse the same index name for all columns in a compounded indexLabel all columns which have additional indexes with INDEX1, INDEX2, etc.Indicate the sequence of fileds in a compounded index ex: INDEX1-1, INDEX1-2

InfoProvider_DetailCUBE DIMENSION SHORT DESCRIPTIONIf the object is a cube, enter the short description of the dimension

InfoProvider_DetailNAVIGATIONAL INDICATORIndicate with a Y if this InfoObject will be navigational

InfoProvider_DetailSOURCE TECHNICAL NAMEEnter the technical name of the source

InfoProvider_DetailSOURCE INFOOBJECT NAMEEnter the technical name of the source InfoObject

InfoProvider_DetailTRANFORMATION TYPEEnter the type of transformation MOVE CONSTANT ABAP

InfoProvider_DetailMOVE TYPEEnter the type of Move: ADD OVERWRITE

InfoProvider_DetailUPDATE RULE PSEUDO LOGICEnter the generalized pseudo logic which is a summary of the code that will be built. Do not enter the exact code.


&L&8&F &A&D &TStatus: Formalized For ACT Approval &R&8&P of &N

MBD00097816.psd

MBD001C9E8E.psd

MBD000F7D4C.psd

MBD001C226C.psd

MBD000F7D4A.psd

MBD000F7D4B.psd

MBD000ED353.psd

MBD000807DA.psd

MBD0008F796.psd

MBD0005F6B8.psd

MBD0007AF50.psd

Plan - DeliverablesPL081 Stakeholder Goals and ExpectationsPL101 RequirementsPL103 Solutions MetricsPL123 Current Capability AssessmentPL131 Tailor Waiver Decision MatrixPL134 Waiver RequestPL140 Supplier SelectionPG305 Selection ScorecardPG331 Cost/Benefit AnalysisPG339 Recommendation MemoPL150 Solution BlueprintPL151 Application BlueprintPL153 Technology BlueprintPL155 Training and Performance Support BlueprintPL161 Change PlanPL170 Delivery StrategyPL171 Development StrategyPL172 Sourcing StrategyPL173 Procurement StrategyPL174 Iteration StrategyPL175 Transition StrategyPL177 Piloting StrategyPL178 Testing StrategyPL179 Deployment StrategyPL181 Technology Capacity PlanPL201 Requirements Traceability MatrixLink for access to description of plans and IDC Templates:https://idcquality.accenture.com/customdevelopment/content/frameset_home.asp Click on > Deliverables > View Alphabetically

Project Management - DeliverablesPM095 Initial EstimatePM110 Project PlanPM111Project Measurement Plan PM123 Resource Management Plan PM127 Supplier Management Plan PM129 Risk Management Plan PM132 Quality Management Plan PM133 Project Communications Plan PM134 Configuration Management PlanPM136 Records Management PlanPM137 Knowledge PlanPM139 Issues Management PlanPM191 Project Scope DefinitionPM221 Work PlanPM222 Schedule and MilestonesPM223 Resource PlanPM224 Detailed EstimatePM225 BudgetPM226 Deliverable Responsibility MatrixPM227 Team Organization ChartPM228 Security PlanPM246 Team CharterPM262 Roles and ResponsibilitiesPM263 Project Orientation and Training MaterialsPM264 Roll On / Roll Off FormsPM266 Training Needs MatrixPM289 Entry / Exit criteriaPM291 Review DocumentationPM293 Peer Review CriteriaPM294 Peer Review Feedback FormPM295 Quality Assurance MemoPM297 Process and Product Quality Assurance Report PM298 Sign-off SheetPM320 Project Management ReportsPM323 Project Staffing Report PM325 Project Status ReportsPM327 Issue LogPM328 Change Control LogPM329 Risk LogPM331 Decision Analysis and Resolution ReportPM581 Change Request PM583 System Investigation RequestPM698 Project Closure Report

Application - DeliverablesAP203 Project GlossaryAP250 RICEFD InventoriesAP251 Master Data InventoryAP253 Report InventoryAP254 Web Template InventoryAP256 Conversion InventoryAP257 Interface InventoryAP258 Data Target InventoryAP260 Integration Conceptual DesignAP263 System Activity DiagramAP265 Key Data ObjectsAP267 System Data Flow DiagramAP350 RICEF Functional DesignAP351 Functional Design Master DataAP353 Functional Design Report AP354 Functional Design Web TemplateAP356 Functional Design ConversionAP357 Functional Design Interface AP360 Logical Data ModelAP362 Data VolumesAP365 Logical Data Model DefinitionAP366 Logical Data Model DiagramAP450 RICEF Technical Design BE TemplateAP451 Technical Design Master DataAP453 Technical Design Report AP454 Technical Design Web TemplateAP456 Technical Design ConversionAP457 Technical Design InterfaceAP458 Technical Design Data TargetsAP460 Physical Data ModelAP465 Physical Data Model DefinitionAP466 Physical Data Model DiagramAP481 Interface AgreementAP490 BI Naming StandardsAP491 Key User and Query Development StrategyAP500 Portal Strategy and ApproachAP510 Functional Design PortalAP520 Technical Design Portal

Testing - DeliverablesAssembly / Product TestingTE483Common Test DataTE580Test PlanTE582Test ApproachTE583Test ScenariosTE584Test Conditions and Expected ResultsTE585Test Cycle Control SheetTE586Test ScriptTE598Test Closure MemoPerformance TestingTE483Common Test DataTE580Test PlanTE582Test ApproachTE583Test ScenariosTE584Test Conditions and Expected ResultsTE585Test Cycle Control SheetTE586Test ScriptTE598Test Closure MemoUser Acceptance TestingTE483Common Test DataTE580Test PlanTE582Test ApproachTE583Test ScenariosTE584Test Conditions and Expected ResultsTE585Test Cycle Control SheetTE586Test ScriptTE598Test Closure Memo

Deploy - DeliverablesDP211Deployment PlanDP221Deployment Work PlanDP418 Contingency PlanDP424 Go Live Preparation Action PlanDP428 Go Live Support PlanDP512 Migration ApproachDP514 Migration ProceduresDP517 Migration Request FormDP663 Training EvaluationDP679 Client Readiness Sign-offDP693 Go Live Evaluation (Lessons Learned)DP699 Handover Documents

Training & Perf Mgmt - DeliverablesTR220 Organizational Impact AssessmentTR222 Organizational Impact MatrixTR227 Organizational Impact SummaryTR233 Performance AssessmentTR241 Training and Performance Support StrategyTR251 Communication StrategyTR320 Job DesignTR322 Job DescriptionTR324 Role DescriptionTR325 Role/Metrics MatrixTR326 Role/Skills MatrixTR327 Team DesignTR335 Training DesignTR337 Training PlanTR345 Performance Support DesignTR355 Enablement Communication PlanTR363Training and Performance Support Development StandardsTR366Organization Staffing PlanTR420Organization Transition MaterialsTR422Organization Transition PlanTR427Organization Transition TrackingTR435Training MaterialsTR445Performance Support MaterialsTR455Communication MaterialsTR463Maintenance and Support PlanTR583 Simulation Scenario

Service Introduction - DeliverablesSI201 Support Requirements MatrixSI221 Support Impact StatementSI291 Compliance ReportSI321 Service Introduction PlanSI549 Unit Readiness Status ReportSM197 Service Level Agreement

Technical Arch - DeliverablesTA223Application Architecture SpecificationTA230Technical Architecture SpecificationTA243Application Development StandardsTA275TCO AnalysisTA277Technology Implementation PlanTA345Development Environment DesignTA350Execution Environment DesignTA365Operations Environment Service DesignTA423Installation and Configuration GuideTA433Technology Policies and Procedures

BI Design - Approach RequirementsReportsMaster DataTransaction Data Split up the requirements in logical smaller chunks to start Research on SAP Business Content, KX, past project implementations for similar scope and designed solutions Be Resourceful Contribute to BI COE repository to leverage it later

BI Design The decision treeBusiness Content (MD, TD, DR)Custom Development(MD, TD, DR)RequirementsDesign / DevelopmentReady to goCustomisationStandard Objects to be customizedCustom objects to be built

Technical design from a poorly documented functional design- At times you will have very less information to start. Use the attached Functional requirements to design technical designs Focus on asking the right questions Make assumptions but should be able to defend yourselfAddressable spendsLeads

PAGE

December 16, 2005

Version 1.2

Computer Associates

One Computer Associates Plaza

Islandia, NY 11749

Functional Specification Design Document

Project

CA Transformation

Work Stream


Process

Procure-to-Pay

Title

Addressable Spend

Type

Document Identifier

TD_200_20

Complexity

Medium




Name

Signature

Date

Robert Schipf

GIS Lead

Tanvir Manjur

Development Lead

Marco Nunez

Solution Architect

Andrew Sinclair

Business Lead

Revision History

Author

Version

Rev. date

Summary of Changes

Section

Page

Sujoy Banerjee

1.0

09/11/05

Intitial Submission

Lalit Verma

1.1

10/19/2005

General Revision

Lalit Verma

1.2

11/28/2005

Revision for the Process Flow Diagram

Sujoy Banerjee

1.2

12/16/2005

Added the list of Transports (bid # CR001035)

Transport Summary

Transport #

Description


Date

DB1K900268

R406:BIW:TD_200_20_20_Addressable Spend

bid # CR001035

12/12/2005

Table of Contents


41.1Naming

41.2Description





52.4Historical Data

52.5Assumptions

52.6Outstanding Issues / Questions:




63.2Other Info Cube Specifications

63.3Data Flow Diagram


73.5Business Process Specifications



1.1 Naming

Technical Name:

ZMTB_C08

Display Name:

Addressable Spend Cube

1.2 Description

The Addressable Spend Cube is used to capture and analyze all spending by vendor and material group posted on R/3. This cube combines data from General Ledger and Purchase Orders for SAP ECC to give management the ability to report on all spend/costs by geography, vendor or commodity.

Note: This InfoCube reports spending for the purchase orders for which invoice has been received. The purchase orders without the invoice receipt are reported in this cube. The following Purchase Order Document Types are relevant for Addressable Spend Analysis.

It answers the following key business questions:

Addressable spend

Trending spend over by Company Code, Cost Center, Purchasing Group, Material Group, Spend Group etc?

Who are CAs the Top N vendors by material group?

What are my spend by Diversity Attributes?

What is the total spend for a Global Vendor?

Reporting is limited to the data that is in R/3, so there is no need to extract information from legacy systems.

Points for Consideration:

Reporting output data will be limited to 65,000 lines in excel (BEx Analyzer).

R/3 Data, Data Sources and Extractors

Data Modeling and Reporting

The following are the key Addressable Spend reports that are delivered from BW:



Cube

Description

End User

Attributes & Hierarchies

Addressable Spend

(History: N/A)

(Frequency: Daily)

(Source: SAP R/3)

Support Purchasing Spend Analysis

Finance

Purchasing

The Addressable Spend Cube captures and analyzes all purchase related spending. We are able to drill down to analyze spend by Geography, Vendor attributes and hierarchies, Diversity, and SIC.


SAP BW is a read only environment. Security considerations for addressable spend are implemented by using roles and authorizations in SAP BW to restrict the view of company spend. The reporting is secured by the authorizations on Purchase Order Document Type.


Spend information are only sourced from SAP ECC 5.0 and have been approved purchase orders from SRM.

2.4 Historical Data

Not Applicable.

2.5 Assumptions

The data is extracted to BW cube from ECC only and not from legacy.

The data is extracted daily once from R/3 to BW.

The currency translation is to be done in the ECC system and BW reports the results.

D&B Attributes are stored in BW and are used for Diversity Reporting.

2.6 Outstanding Issues / Questions:

Need to define where/how budgets for purchasing/spend will be sourced and mapped (out of scope for Release 3)


The following file CA MTB P2P Process Flow.vsd contains the level 1 and level 2 process flows for the Procure to Pay process area for MTB. The current location of the file can be found at:

\\usilfs57\CA Transformation\MTB\Release 3\Design\Process Flows\Procure to Pay



Not applicable since no data is being converted from the legacy systems to BW. Data is coming to BW directly from R/3.

3.2 InfoCube Specifications

The following are the key dimensions that are available in the addressable spend cube:

3.3 Data Flow Diagram

Proposed Architecture for Addressable spend Line Items

(Custom Solution)


The data is to be updated on a daily basis.

3.5 Business Process Specifications

The addressable spend information is loaded once per day and is extracted from the sources systems through a delta process. The pre-requisites for loading this cube are:

The daily batch processing is through process chains.


Unit Test Information

Expected Results

Select a document in ECC 5.0 from FB03, note the purchasing document #

Make sure the record selected is a record which would have run in the extract process

Ensure the selected document can be seen in the ZMTB_O04 ODS and the resultant entry is also present in the ZMTB_C08 cube (Addressable Spend Cube).

Actual Results

The selected purchasing document number for the test has been matched to the ZMTB_O04 ODS and present in the ZMTB_C08 cube


DR2-020

DB2-010


09/09/2005

Tester Name

Sujoy Banerjee

Test results document

TEST RESULTS DOCUMENTED

DATE OF TEST: 09/09/2005

RESULT OF TEST:

Accounting Document: 5100000046

Fiscal Year: 2006

Company Code: 1001

In ECC 5.0 (DR2 Client 020):

Accounting document display using Transaction FB03.

In BW (DB2 Client 010):

G/L Line Item ODS:

Search for record in ZMTB_O04 (G/L Line Item ODS) using the following criteria:

Accounting Document: 5100000046

Item: 2

Fiscal Period/Year: 005/2006

Company Code: 1001

Please note the following information for this record:

Purchasing Document Number (EBELN): 4500000020

Item Number of purchasing Document (EBELP): 20

G/L Account: 0000222001

Transaction Type: RMRP

Posting Key: 86

Addressable Spend Cube:

The above document is also present in the ZMTB_C08 (Addressable Spend Cube).

CONFIDENTIALITY STATEMENT

The information in this document contains trade secrets and commercial information that are privileged or confidential and may not be disclosed unless such disclosure is required by federal or state law or regulations. In any event, persons to whom the information is disclosed must be informed that the information is privileged or confidential and may not be further disclosed by them. These restrictions on disclosure will apply equally to all future information supplied to you which is indicated as privileged or confidential.



PAGE

November 9th, 2006

Version 1.9

Computer Associates


Islandia, NY 11749


Project

CA Transformation

Work Stream


Process

Lead-to-Quote

Title

Leads

Type

Document Identifier

TD_400_10

Complexity

Medium




Name

Signature

Date

Andre Pimentel - GIS Lead

/ Andrew Sinclair Business Lead

Marco Nunez

Solution Architect

Revision History

Author

Version

Rev. date

Summary of Changes

Section

Page

Olivia Valerie

1.1

10/11/2005

Intitial Submission

Olivia Valerie

1.1

12/16/2005

Added Transport Information (BID # CR001035)

Olivia Valerie

1.2

12/28/2005

Removed transport information and added new list. This is the transports that should have gone for the November release ((bid# CR001035)

Olivia Valerie

1.3

01/09/06

Added transport information for BID# CR001119, Defect# 18772

Olivia Valerie

1.4

02/23/06

Add unit testing information and transport information for defect 21054, 20853 (BID # CR001571).

Olivia Valerie

1.5

03/06/2006

Added unit testing information and transport information for defect 20088 (BID # CR001616)

Olivia Valerie

1.6

03/08/06

Added unit testing information and transport information for defect 21463 (BID # CR001755)

Olivia Valerie

1.7

03/20/06

Added transport and unit testing information for defect 21618 (BID # CR001878).

Olivia Valerie

1.8

09/05/06

Added Section 1.3 for XM3 changes (CR:2825832).

1.3

Heather Heusel

1.9

11/9/06

Adding section 1.4 for XM5 changes related to marketing reports

1.4

Transport Summary

Transport #

Description


Date

DB1K900303

R406:BIW:TD_400_10_30_CRM Lead Management

BID # CR001035

12/14/2005

DC2K900201

R3:BIW:TD_400_10_ACTIVATING_0CRM_LEAD_I

BID # CR001035

8/18/2005

DC2K900205

R3:BIW:TD_400_10_ACTIVATING_0CRM_LEAD_H

BID # CR001035

8/18/2005

DC2K900225

R3:BIW:TD_400_10_ACTIVATING_0CRM_TGBPCT

BID # CR001035

8/18/2005

DC2K900271

R3:BIW:TD_400_10_ACTIVATING_0CRM_TRPR_ATTR

BID # CR001035

8/18/2005

DC2K901188

R3:BIW:TD_400_10_ACTIVATING_0CRM_LEAD_H

BID # CR001035

9/10/2005

DC2K901233

R3:BIW:TD_400_10_20_Saving 0CRM_OPPT_H

BID # CR001035

9/10/2005

DB1K900501

R406:BIW:DR_400_10 BEx Leads Queries DEF#18772

BID # CR001119

DB1K900878

R406:BIW:DR_400 BEx Auth_var_OrgUnit DEF#20853,21054,20237

BID # CR001571

DC1K901066

R406:BIW:TD_400_10_10_UserExit 0CRM_LEAD_H DEF#20088

BID # CR001616

DB1K900997

R406:BIW:DR_400 BEx LTQ Leads-Opp Terr DEF#21375,21463,21618

BID # CR001755

DB1K901113

R406:BIW:DR_400_20_Fix_NCV_Webtemplate::DEF#21463,21618

BID # CR001878

DB1K902524

XM3:BIW:2825832:TD_400_10:Add_PMFKEY_SALES_ORG_CUBE

CR:2825832

DB1K902508

XM3:BIW:2825832:DR_400_10:Add_Various_FLDS_Leads_RPTS

CR:2825832

Transport Revision added to CTP

11/10/06

CTP Document Cross-References

Document Name

Author

Comments

AP350_CTP_BI_Leads_TD_400_10_XM1_V1.0.doc

Olivia Valerie

CR:2825832

Table of Contents


51.1Naming

51.2Description

81.3XM3 Modifications and Enhancements

91.4XM5 Modifications and Enhancements





122.4Assumptions








154.3Change Log


29Unit Testing for defect 20853



47Unit Testing for defect 21463 (Reopened)


1.1 Naming

Technical Name

ZLTQ_C01

Display Name

CRM Lead Management

1.2 Description

The Lead solution will provide analytical information sourced from SAP CRM.

This data will be used for the following purposes:

1) To measure the success and efficiency of leads that have been created within a certain period or generated via a specific channel (e.g. via campaigns or the Internet).

2) Number of leads that are assigned to each sales representative and the status of those leads

In SAP, all transactions are made up of header and line item data. The current business process being configured for leads will have both header and line item data or just header data In order to address leads reporting, the data that is extracted into the Lead management cube will contain three types of data:

1) Lead Header Data

2) Lead Item Data

3) Lead Master Data (ZLEADHEAD) - This has been created to logically replicate header level fields into item level records. The master data fields are:

Duration Lead

No. of Changes in Lead Qualification Level

No. of Activities: Leads

Number of Document Headers

Accepted By Sales

Lead Origin

ORGUNIT_EmployeeResponsible

ORGUNIT_SalesRep

Status Profile

User Status

Current Catalog: Reasons

Current Code Group Reasons

Current Code: Reasons

CRM Marketing Element

Reason

B2N2V need

Direct/Indirect

The approach of breaking the data out into header, item and master data was taken in order to provide more meaningful reporting results when combining header and item level info, thus avoiding the occurrence of blank cells and potential misleading totals (double counting). The reports that were generated for lead management have been broken out into header and item analysis reports.

The Cube will be enhanced to bring in the following information so that analysis can be done on the following:

1) Material (i.e. Brand, IDC, Gartner attributes)

2) Industry Sector

3) State

4) Country

5) Territory Attributes (i.e. Territory Area, Territory Region)

The cube will also be enhanced to include the following date Info Objects:

Calendar Day This is based on the lead creation date

Calendar Year/Month This is based on calendar day

Calendar Year/Quarter - This is based on calendar day

Calendar Year/Week - This is based on calendar day

Calendar Year - This is based on calendar day

Fiscal Year/Period - This is based on calendar day

Fiscal Year - This is based on calendar day

Half Year - This is based on calendar day

This cube will provide the answers to the following key business questions:

What are the counts of my leads by Customer, Sales Force, and Territory for a given period of time?

What are all my leads associated with a given Campaign?

How leads have been generated per Campaign?


Points for consideration:

The priority field (data element CRMT_IMPORTANCE) has been configured as a required entry to hold the values Direct and Indirect. This field will be used to report on distribution channel.

On a Lead the user must enter the product itself on the line item.

On a Lead there is the possibility of having header data and no item related information.

As a business process when there is line item data for a lead, the lead will contain one item but the configuration does NOT limit the user to entering only one line item.

Reporting output data will be limited to 65,000 lines.

A lead will contain one employee responsible and one sales representative.

The following field label need to occur in BW to reflect the changes that were made to the field label names in CRM screen:

Data Element

Field Name

New Label

CRMT_IMPORTANCE

IMPORTANCE

Direct/Indirect

CRMT_LEAD_TYPE

LEAD_TYPE

Lead Origin

CRMT_SOURCE

SOURCE

B2N2V Need

CRM Data, Data Sources and Extractors:

Data sources/extractors that were used from CRM for this cube are:

1) Data Source: 0CRM_LEAD_H Leads Header

Description: This InfoSource contains the leads header data from CRM

Extractor: CRMT_BW_LEAD_H

Business Event Number: TD_400_10_10

2) Data Source: 0CRM_LEAD_I - Leads Item

Description: This InfoSource contains the leads items data from CRM

Extractor: CRMT_BW_LEAD_I

Business Event Number: TD_400_10_20

The extractor was enhanced to include the following:

Field

SAP Field

SAP Table

Catalog

ZZCATALOG

CRMD_SRV_SUBJECT

Code

ZZCODE

CRMD_SRV_SUBJECT

Code Group

ZZCODEGRP

CRMD_SRV_SUBJECT

User Status

ZZSTATUS

CRM_JEST

Personnel Number

ZZ_PERNR

HRP1001

Personnel Number

ZZ_PERNR1

HRP1001

Status Profile

ZZPROC

CRMC_PROC_TYPE

ODS Objects:

ZLTQ_O01 CRM Lead Header Data

Business Event No: TD_400_10_10

ZLTQ_O02 CRM Lead Item Data

Business Event No: TD_400_10_20

Reporting

The following are the key reports that will be delivered from BW:

Report Name

Technical Name

Business Event Number

CA: Lead Management: History Reporting Hdr Analysis

ZLTQ_C01_GLOBAL_Q20

DR_400_10_60

CA: No. of Leads by Emp Resp/Sales rep/Trans. Creator (Hdr)

ZLTQ_C01_GLOBAL_Q021

DR_400_10_30

CA: Leads Generated by Campaign Hdr Analysis


DR_400_10_40

CA: Leads: Efficiency reporting Hdr Analysis


DR_400_10_50

CA: Leads in Open Status not touched in N days (Hdr)


DR_400_10_20

CA: Leads Generated by Campaign Itm Analysis


DR_400_10_80

CA: No of Leads by Emp Resp/Sales Rep/Trans. Creator (itm)


DR_400_10_70



Cubes

Description

End Users


Leads

(History: N/A)

(Frequency: Daily)

(Source: SAP CRM)

Support Leads/Demand Generation and Campaign Effectiveness analysis

Sales

Marketing

Customer Master Data Attributes & Hierarchies

Material Detail

Sales Force Hierarchy

Territory Hierarchy

Time / Geography

What is lead?

A business transaction which describes, stores, updates, and manages the potential interest of (and interaction with) a business partner over a certain timeframe.

Leads are used to qualify a business partner's interest in a particular product or in making a purchase, with the aim of both establishing and then subsequently influencing this interest.

Once a lead has reached a certain status, it can be passed on to "Sales" as decision support for creating an opportunity. This is accomplished by changing the status on the lead to Accepted by Sales.

In CA, Leads are generated through:

Call-me-button (There will be an interface between the CA website and SAP. The data in CRM will be uploaded real-time. The timeframe to call a client back on the call-me-button is 15 minutes.)

Web downloads (This will be uploaded into CRM once a day)

External Lists (CA purchase these lists from different vendors)

Leads data will be extracted daily from SAP CRM to the BW Lead cube. The data that the user will be looking at will have a one day lag between the transactional system and BW.


Please refer to the following document for the BI security solution:

\\..\..\BI\Release 3\Security\ AP250_BI_Security.doc


Transactional data will be loaded after master data has been loaded.

2.4 Assumptions

While reporting on BEx, MS Excel limitations will apply (e.g., number of rows 65,000). User can access BEx web reporting to see more rows in one run. But for performance reason its recommended to filter the output.

We will need Campaign, Call List, Activity, Lead, Opportunity, Quote, Sales, and Revenue for overall CRM analysis.

On a lead there will be one employee responsible and sales representative.


File Location: \..\LTQ\Release 3\Global Design\LTQ Global Design Deliverables Pkg - Signed Off\LTQ20 Lead Mgmt\ LTQ20 Lead Mgmt - Process Flows.vsd



This is not applicable since no data is being converted from the legacy systems to BW. Data will be coming to BW directly from CRM.

3.2 Info Cube Specifications

The following are the Key Dimensions available in the Lead Management cube:

4. Other Detailed Specifications

4.1 Process/Data Flow Diagram


A nightly job will be scheduled on daily basis. The process of loading, Indexing, collection of statistical data, etc will be integrated with BW Process Chain Technology.

4.3 Change Log


Unit Test Information (CRM Lead Header Data ODS ZLTQ_O01)

Expected Results

Select a document in CRM by doing the following:

1) Menu path: Marketing -> Leads -> Maintain Leads.

2) Click button

Make sure that the document that is selected is a record which would have run in the extract process. Ensure the selected document can be seen in the ZLTQ_O01 ODS and the resultant entry is also present in the ZLTQ_C01 cube.

Actual Results

The selected lead header document number for the test has been matched to the ZLTQ_O01 ODS and present in the ZLTQ_C01 cube.


DC2-020

DB2-010


10/18/2005

Tester Name

Olivia Valerie

TEST RESULTS DOCUMENTED

DATE OF TEST: 10/18/2005

RESULT OF TEST:

In CRM (DC2-020):

Menu path: Marketing -> Leads -> Maintain Leads

Transaction: CRMD_BUS2000108 Maintain Leads

Transaction No. 40000000


DB1-010

QB1-100


03/08/2006

Tester Name

Olivia Valerie

Defect

21463

CA: Open Leads not touched in 'N' days (Hdr) (ZLTQ_C01_GLOBAL_Q024 in QB1 before change:

CA: Open Leads not touched in 'N' days (Hdr) (ZLTQ_C01_GLOBAL_Q024 in DB1 after change:

CA: No.of Leads by Emp Resp/Sales rep/Trans. Creator(Itm) - ZLTQ_C01_GLOBAL_Q026 in QB1 before change:

CA: No.of Leads by Emp Resp/Sales rep/Trans. Creator(Itm) - ZLTQ_C01_GLOBAL_Q026 in DB1 after change:

CA: No.of Leads by Emp Resp/Sales rep/Trans. Creator(Itm) - ZLTQ_C01_GLOBAL_Q026 in DB1 after change:

CA: Leads Generated by Campaign - Itm Analysis - ZLTQ_C01_GLOBAL_Q025 in DB1 after change:

CA: Leads : Efficiency Reporting - Hdr Analysis - ZLTQ_C01_GLOBAL_Q023 in DB1 after change:

CA: Leads Generated by Campaign - Hdr Analysis - ZLTQ_C01_GLOBAL_Q022 in DB1 after change:

CA: No.of Leads by Emp Resp/Sales rep/Trans. Creator(Hdr) - ZLTQ_C01_GLOBAL_Q021 in DB1 after change:

CA: Lead Management : History Reporting - Hdr Analysis - ZLTQ_C01_GLOBAL_Q020 in DB1 after change:

CA: Open Leads not touched in 'N' days (Hdr) (ZLTQ_C01_GLOBAL_Q024) in QB1 before the change. The Sales Organization bucket is missing CA Territory Geography, CA Territory Area and CA Territory Region:

CA: Open Leads not touched in 'N' days (Hdr) (ZLTQ_C01_GLOBAL_Q024) in DB1 after the change. The Sales Organization bucket now has CA Territory Geography, CA Territory Area and CA Territory Region:

***End of Document***





Technical designs from a detailed specUse the attached designs to develop technical designs

Accounts Receivable Invoice Billing Focus on the functional requirements and the approach Do not get lost in detailing. High level design is goodPersonnel Administration

PAGE

November 20, 2006

Version 2.7

Computer Associates


Islandia, NY 11749


Project

CA Transformation

Work Stream


Process

Manage The Business

Title

Accounts Receivable

Type

Document Identifier

TD_300_30

Complexity

Medium




Name

Signature

Date

Andre Pimentel

GIS Lead

Tanvir Manjur

Development Lead

Marco Nunez

Solution Architect

Andrew Sinclair

Business Lead

Revision History

Author

Version

Rev. date

Summary of Changes

Section

Page

Jags Devaram

1.0

4-27-2005

Initial Version

Christine L Hoffmann

1.1

5-11-2005

Updated original version to contain flows and be consistent with other designs.


1.2

7-11-2005

Added/deleted additional fields required for the a/r extractors.


1.3

7-12-2005

Updated with characteristics.


1.4

7-26-2005

Updated attribute 9 and 10 field and table names.


1.5

8-4-2005

Added AP Transaction cube to scope.

Lalit Verma

1.7

10-3-2005

Included the Reports and UTP in the documentation

Sujoy Banerjee

1.7

12-16-2005

Added the lits of Transports (bid # CR001035)

Satish Voona

1.8

12-28-2005

Updated list of Transports(bid # CR001035)

Sujoy Banerjee

1.9

01-06-2006

Added Unit test for Defect 18467 (bid # CR001107)

Sujoy Banerjee

2.0

02-02-2006

Added Unit Test for defect 19877 (bid# CR001410)

Val Feldbaum

2.1

02-23-2006

Added Unti Testing and Comments Deffect 20446

Val Feldbaum

2.2

03-23-2006

Added Unti Testing and Comments Deffect 22255

Sivakumar Thiyagasamadram

2.3

06/05/2006

Added a new section related to CR 2703042

3.3, 3.3.1

Page 9


2.4

06/15/2006

Added a new section related to CR 2703042

33, 3.3.1

Page 9


2.5

06/26/2006

Added a new section related to CR: 2772821

33, 33.1

Page 9

Donna Marie Borbe

2.6

09/15/2006

Added 0PROJECT to ZMTB_C01

1.2,

Donna Marie Borbe

2.7

Remove 0PROJECT, 0S_ORD_ITEM, ZCONTRACT from ZMTB_C01, Remove update rules to these fields, Added 0CUST_SALES into ZMTB_C01 and made query changes turning Customer Group 1-5, Attributes 1-10 into navigational attributes. Updated CFS Reports

1.2, 4 (New Section)

Pages 5 and 12

Transport Summary

Transport #

Description


Date

DB1K900266

R406:BIW:TD_300_30_70_AR Transactions

bid # CR001035

12/13/2005

DB1K900265

R406:BIW:TD_300_30_40_AR Payment Behavior

bid # CR001035

12/13/2005

DB1K900264

R406:BIW:TD_300_30_20_AR Line Items

bid # CR001035

12/13/2005

DR2K900055

R3:BIW:TD_300_ACTIVATING_0FI_AR_4

bid # CR001035

7/27/2005

DR2K900059

R3:BIW:TD_300_ACTIVATING_0FI_AR_10

bid # CR001035

7/27/2005

DR2K900452

R3:BIW:TD_300_30_ACTIVATING_0FI_AP_6

bid # CR001035

8/15/2005

DB1K900466

R406:BIW:BEx transport for ZMTB_C01 DEF#18467

bid # CR001107

01/06/2006

DB1K900692

R406:BIW:DR_300_30_230 BEx MTB Report Config Chg DEF#19877

bid # CR001410

02/02/2006

DB1K900871

R406:BIW:DR_300_30_280 ZMTB_C01_Q5011 DEF#20446

bid # CR001544

02/23/2006

DB1K900872

R406:BIW:DR_300_30_110: ZMTB_O01_Q1002_1 DEF#20446

bid # CR001544

02/23/2006

DB1K901199

R406:BIW:DR_300_30:AR Reports Var Name change DEF#21211

Bid # CR2656493

03/23/2005

DB1K901617

RPS:BIW:CR 2703042TD_300_40:Accounts Receivable Changes

CR # 2703042

06/12/2006

DB1K901620

RPS:BIW:2703042:DR_300_40:Accounts Receivable Changes

CR # 2703042

06/12/2006

DB1K901669

RPS:BIW:CR 2703042 DR_300_40:Accounts Receivable Changes

CR # 2703042

06/15/2006

DB1K901757

RPS:BIW:2772821:DR_300_40:Accounts Receivable Query Changes

CR# 2772821

06/26/2006

DB1K902856

XM3:BIW:CR2845470:DR_300_30:ModifyZMTB_C01

CR# 2845470

09/15/2006

DB1K902858

XM3:BIW:CR2845470:DR_300_30:ModifyCFSWebTemplateCreateBEx

CR# 2845470

09/15/2006

DB1K903516

RPS:BIW:2908782:TD_300_30: RemoveSvcFieldsAR

CR:2908782

11/13/2006

DB1K903518

RPS:BIW:2908782:TD_300_30: RemoveSvcUpdateRulesAR

CR:2908782

11/13/2006

DB1K902144

RPS:BIW:CR:2908782:Accounts Receivable Query Changes: 2

CR:2908782

11/13/2006

DB1K903434

RPS:BIW:ENH:CR2908782ARCustomerGroup

CR:2908782

11/13/2006

Table of Contents


41.1Naming

41.2Description





72.4Assumptions












1.1 Naming

Technical Name:

ZMTB_C01, ZMTB_C02, ZMTB_C11

Display Name:

Accounts Receivable Line Items Cube, Accounts Receivable Payment History Cube, Accounts Receivable Transaction Cube

1.2 Description

Accounts Receivable Solution comprises of 3 InfoCubes.

Accounts Receivable Line Item InfoCube (ZMTB_C01) has the line item transaction data of Accounts receivables extracted from SAP R/3 (ECC 5.0). This cube provides Accounts Receivable Accounting Open line items and Cleared line items. Based on this we can generate several reports like Open item aging report, days to pay report and complete A/R activity report (invoices, credits and payments) for each customer. This infocube had been enhanced with billing information to report results by Sold-to and Billing Type.

0PROJECT was eliminated from the AR Line Items Cube because AR is not populated at this level in ECC. It will not be possible to see receivables by project id.

Accounts Receivable Payment History InfoCube (ZMTB_C02) has the customer payment behavior data extracted from SAP R/3 (ECC 5.0).

Accounts Receivable Transactions InfoCube (ZMTB_C11) has the customer balance, debits and credits extracted from SAP R/3 (ECC 5.0). Based on this we can generate several reports like Customer Balance Overview and DSO report.

Together, they provide answers to the following key business questions:

What is my Aging for certain Customers / Geography / Time?

What is my DSO for certain Customers / Geography / Time?

What are my Top N invoices by Customers / Geography / Time?

What are all my open items for a certain Customer / Geography / Time?


Points for Consideration:

Reporting output data will be limited to 65,000 lines in excel (BEx analyzer).

Collectrix will still be used to generate reports based on territory or manager or collector for the domestic business.

International business will use their own process (AS-IS) for the A/R reports to collect the payments from customers.

All open A/R balances are to be brought into R3.

Inter company billings will occur.

R/3 Data, Data Sources and Extractors

The datasources for the Accounts Receivable Solution are as following:

1. Data Source: 0FI_AR_4

Description: Customers: Line Items with Delta Extraction

Extractor: DTFIAR_3


Description: Customer Payment History Using Delta Method

Extractor: DTFIAR_10


Description: Accounts Receivable: Transaction Figs w. Delta Extraction

Extractor: DTFIAR_1

ODS Objects:

ZMTB_O01 - FIAR: Line Item

ZMTB_O02 - FIAR: Payment History

ZMTB_O10 - FIAR: Transaction

Additional fields included to report on:

Field

SAP Field

SAP Table

Fields around Customer master data:

Recon Account

AKONT

KNB1

Payment History Record

XZVER

KNB1

House bank

HBKID

KNB1

Lockbox

LOCKB

KNB1

Dunning Procedure

MAHNA

KNB5

Dunning Clerk

BUSAB

KNB5

Dunning level

MAHNS

KNB5

Dunning block

MANSP

KNB5

Accounting clerk

BUSAB

KNB1

Credit Limit

KLIMK

KNKK

Customer Group

KDGRP

KNKK

Risk Category

CTLPC

KNKK

Credit Account

KNKLI

KNKK

Attribute 9

KATR9

KNA1

Attribute 10

KATR10

KNA1

Industry key

BRSCH

KNA1

Fields around Project Services master data:

Project Definition

PSPID

Fields around Billing master data:

Distribution Channel

VTWEG

RF02D

Bill To Party

PKUNRE

Sold To Party

KUNAG

Payer

KUNRG

Reporting

The following are the key reports delivered from BW:

Customers: Overview (Loc.Curr.) (ZMTB_C01_Q1001)

Customers: Overview (Grp.Curr.) (ZMTB_C01_Q1007)

Days to Pay Analysis (Local Currency) (ZMTB_C01_Q5001)

Days Overdue Analysis (with Aging Buckets) - Loc.Curr. (ZMTB_C01_Q5005)

Days Overdue Analysis (with Aging Buckets) - Grp. Curr. (ZMTB_C01_Q5006)

List of Open Items for Due Date Analyses (ZMTB_O01_Q0001)

Top N Overdue Invoices (ZMTB_O01_Q1002_1)

Customers: Payment History (ZMTB_C02_Q0001_1)

Customer Balance Overview (Loc. Curr) (ZMTB_C11_Q0001)

Customer Balance Overview ( Group Curr ) (ZMTB_C11_Q0002)

Customers: DSO Analysis for a Period - Local Currency (ZMTB_C11_Q5001)

Customers: DSO Analysis for a Period - Group Currency (ZMTB_C11_Q5002)

Terms Offered (Loc.Curr.) (ZMTB_C01_Q0001)

Analysis of Due Dt. for Net Payment (Overview) - Loc.Cur (ZMTB_C01_Q1005)

Analysis of Due Dt. for Net Payment (Overview) - Grp.Cur (ZMTB_C01_Q1006)

Days to Pay Analysis (Local Currency) (ZMTB_C01_Q5001)

Days to Pay Analysis (Group Currency) (ZMTB_C01_Q5002)

SAM Report - Grp.Curr. (ZMTB_C01_Q5007)

Top N Overdue Credit Memos (ZMTB_O01_Q1003_1)

List of Customer Line Items (ZMTB_O01_Q0002)

Customers: Arrears for Payment w/o Cash Discnt (Credit M) (ZMTB_C02_Q1002_1)

List of Cleared/Paid Invoices (ZMTB_O01_Q1004)

List of Open/Partial Payments (ZMTB_O01_Q1005)

CA: List of Open Payments & Credits (ZMTB_C01_Q5009)

CA: Payment Report by Dunning Clerk (ZMTB_C01_Q5010)

CA: Overdue Invoices with amount >= N (ZMTB_C01_Q5011)

CA: Cash Forecasting Report (ZMTB_C01_Q5008)

CFS: Outstanding Services Invoices in Local Currency (ZMTB_C01_GLOBAL_Q004)

CFS: Outstanding Services Invoices in Group Currency (ZMTB_C01_GLOBAL_Q003)



Cube

Description

End User


A/R Line Item Cube

(History: NA)

(Frequency: Daily)

(Source: SAP R/3)

Support accounts receivable and collection analysis.

Finance

Collections

Sales Managers


Credit Controlling Areas

A/R Payment Behaviour

(History: NA)

(Frequency: Daily)

(Source: SAP R/3)

Support accounts receivable and collection analysis.

Finance

Collections

Sales Managers



A/R Transactions Cube

(History: NA)

(Frequency: Daily)

(Source: SAP R/3)

Support Customer

Finance



Once the customer billing is done in SAP R/3 accounting documen

Date post:	24-Nov-2015
Category:	Documents
Upload:	rahulagrawal
View:	240 times
Download:	26 times