Upload
manoj-kr-singh
View
79
Download
9
Tags:
Embed Size (px)
DESCRIPTION
BPC 10.0 NW Transports Overview & Config v1.1
Citation preview
BPC 10.0 Netweaver: Landscape Management & Sustainment
May 2012
Technology Stack, Transports & Sustainment Roles
Summary & Contents
The information in this presentation summarizes content provided in other decks and conversations related to BPC. The content addresses the following topics as they relate to BPC:
BPC 10.0 Overview: Current Framework & Upcoming Changes
Landscape Management: Transports, File Structures and Processes
Administration & Sustainment: Business and Technical Roles
Update Process Flow Diagram: Diagram illustrating Decision Tree for determining where to perform different BPC updates
2
BPC 10.0 NETWEAVER OVERVIEW
SAP Solutions, Technology Stack, & Future Changes
3
SAP Solutions: Summary View
4
This diagram presents a summary view of SAP’s solution offerings. It is intended to provide context for BPC and the other EPM tools within the SAP solution offerings. The diagram is based upon discussions with SAP team members, diagrams such as the one on the next slide and other SAP-related materials including. It is not intended to address all products and services from SAP, e.g. EIM and Data Warehousing.
SAP Business Analytics Solutions
5
Strategy Management
Planning, Budgeting, and Forecasting
Profitability and Cost Management
Financial Consolidation
Enterprise Performance Management
Disclosure Management
Data Warehousing Data Mart Solutions High-performance Analytic Solutions
Data Warehousing
Reporting and Analysis
Dashboards and Visualization
Data Exploration Mobile
BI Platform
Business Intelligence
Enterprise GRC Access Risk Management
Global Trade Services
Continuous Transaction Monitoring
Governance, Risk, and Compliance
Data Services
Master Data Management
Event Processing
Content Management
Enterprise Information Management
Information Governance
Analytic Applications
By LoB
Service, Sales, and Marketing
Procurement
Supply Chain
Finance
Sustainability
IT, HR, and more…
By Industry
Financial Services
Public Sector and Healthcare
Manufacturing
Consumer Products
Retail and Telco
Utilities and more….
Current Technology Framework
6
BPC 10.0 NW Technology
Tiers
Changes in BPC 10.0
Several changes have occurred BPC and its underlying technology in the newest release – v10.0. Key changes include the following:
User Interface
BPC Excel will utilize a new framework for viewing and working with data using Microsoft® Excel
Enhanced interface will be shared across multiple tools in the EPM 10 suite – enabling users to work in multiple EPM tools
Infrastructure
.NET server will not be required for BPC 10
HANA will be supported
Analysis and Mobility Enhancements
Increased integration with BusinessObjects tools including dashboards (Xcelsius)
Enhanced data availability using mobile devices including iPad, Blackberry Playbook and others – including ability to modify data
7
LANDSCAPE MANAGEMENT
BPC Transport Settings and Recommendations
8
Overview
The information in this section details transport and file management strategies for BPC Netweaver 10.0. The contents of this document are based upon prior project experience, SDN blogs and SAP publications on the topic including:
SAP BPC 10.0 Operations Guide
BPC 10 Admin Guide – Section 5 – Software Change Management. NOTE – this document can be accessed via the SAP Marketplace
The goal of the landscape management process is twofold:
Enable the business to operate efficiently within BPC
Enable the sustainment team to effectively support the business and the system
9
BPC Transport Fundamentals
New to BPC 10.0 Transports:
Transports can be done at a MUCH more granular level (it is no longer required to transport the entire application set (model))
When creating the transport, the user selects what is to be transported, even down to individual reports/input schedules
Whole cubes (Models) can be transported for initial setups
10
BPC Transport Fundamentals
Only metadata about the appset is transported to the target system
BPC objects (dimensions, applications and other configurations) are not transported to the target system – just the metadata that describes them and the objects are built in the destination system
Transports use shadow tables to gather metadata definitions necessary to create or modify items in the target system
Environments must be offline for transports to complete properly
Create Transport – source environment set MUST be offline
Import Transport – target environment set MUST be offline
11
BPC Transport Fundamentals
Things to avoid when using transports to manage landscapes
Do not use standard BW transports to transport BPC objects – custom BW objects are an exception as described on slide 19
Do not change the structure or definition of BPC related data model objects in BW (RSA1) including Environments, Models, dimensions, properties
Do not change the data model in target systems
12
BPC Transport Fundamentals
There are two types of BPC Transports in 10.0:
Normal Mode – This mode is used to create a new BPC 10.0 Environment or modify an existing one. It will result in the creation/moving of objects from a source system to a destination system.
Delete Mode – This mode is used to delete objects from an existing destination system. Objects that can be deleted are:
• Model
• Dimension
• Data Manager Package
• Data Manager Package Group
• Data Manager Package List
*NOTE – due to the newness of BPC 10.0, the new Transport process, and the lack of detailed documentation, some assumptions are made regarding the Delete Mode functionality.
13
BPC Transports: Transport Mode: Normal Transport
Used for creating and modifying objects.
Environmental objects that support Normal Mode:
14
BPC Transports: Normal Transport Mode
Environment
Entire Environment is recreated in destination system
Models
Individual Models (subsets of an Environment) can be transported
This will include all dimensions, reports, etc. associated with a Model
Work Status
Configuration transported only; data locks records are not transported
Data discarded in target system after changes to application model transported
Data Manager-related objects
DM Data Files
DM Package Link
DM Package
DM Files
DM Package Group
Data files are NOT transported
15
BPC Transports: Normal Transport Mode
Journal Templates
Not currently implemented at Philips
Best practice is to back up journals data prior to each transport using the data manager package
Note that changes to the journals template definition may result in a loss of journal detail data
Data Access Profiles
BPC Data Security Access Profiles
Environment Configuration
Entire Environment is recreated in destination system
Task Profile
BPC Security Task access
Report Files (includes Input Schedules)
Can select down to individual Reports/Input schedules
Reports in destination are over-written with new version
16
BPC Transports: Normal Transport Mode
Teams
BPC Team definitions
Individual members assigned to the team are not transported
Library
Available, but not currently used by Philips
Reports and books published to the Web Portal Library are transported
Book Template
Available, but not currently used by Philips
Templates created for book publication are transported
BPF Template
Business Process Flow Template is transported but not activated instances
Controls
Available, but not currently used by Philips
Control Business Rules are transported
17
BPC Transports: Table Entries & Data Model Objects
Business Rules
Currently used at Philips for Currency Conversion and Account Transformation (Cash Flow Statement)
Model Configuration
Transports the configuration of the model – Dimensions, secured dimensions, etc.
Dimensions
Hierarchy
Dimension members
Dimension properties
Report Templates
Drill Through
Not currently implemented at Philips
Drill through queries are transported
Script Logic Files
BPC Script files used to do background processing
18
BPC Transports: Custom Objects
Custom BW Objects must be transported using standard BW transports.
Sample objects developed directly in BW includes:
Process Chains
InfoObjects
BAdI’s
ABAP Code
Not included in BPC transports
Care must be taken to select only the custom objects when using BW transports – including BPC objects in a BW transport may result in errors during future transports
19
BPC Transports: Reference Information
20
UJS_ACTIVATE_CONTENT Use to activate BPC objects during installation
This is mandatory step for initial set-up (installation of BPC) and needs to be performed in every landscape
Also use to delete most entries in UJ* data tables for a given appset – see the blog on this topic at http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17532
Previously-used UJ* commands no longer used in BPC 10.0:
UJT_TRANS_CHG
UJT_TRANS_FIL
UJT_DLT_TRANS_DATA
UJT_CHECK_TABLE_ENTRIES
BPC Transports: Reference Information
Reference SAP Note 1415296 (“BPC Transport and Installation Troubleshooting Summary”) if you encounter transport issues
Search other notes related to transports in the “EPM-BPC-NW-TRA” application area
21
BPC TRANSPORTS CONFIGURATION
Philips Healthcare
22
BPC TRANSPORTS PROCESS
Philips Healthcare
23
Overview
This document addresses the steps required to transport BPC application sets from DEV to QA (quality) and Dev to PRD.
The BPC Transport process consists of three steps:
1. Transport Collection – Done in the Dev environment
2. Transport Release – Readies the Transport Objects to loading into the Target system
3. Import – Loading the BPC Objects into the Target system
Oct-13
24
DEV to QA
Each transport to QA requires completion of the following items in the order shown:
Complete development and unit testing
Collect and release transport to allow it to be transported to the target environment
Detail steps in following section
Request BPC approval from the system owner
Request ABAP / BAdI approval
Only required if back-end changes are involved
Oct-13
25
DEV to QA (cont.)
Each transport to QA requires completion of the following items in the order shown:
AFTER RECIEPT OF APPROVALS, request completion of transport
Include approval emails
Wait for confirmation from SAP Transports team - [email protected]
Log in to the QA environment to confirm changes are reflected in the target system
Oct-13
26
Dev to PRD
Each transport to Prod requires completion of the following items in the order shown:
Complete test cases
Coordinate with business to complete yourself or have the business complete
Run full set of test cases for initial transport
Rerun selected test cases for changed functionality
Create new test cases for enhancements
Document test case results
Add screen shots and notes to test case templates
Email PM confirmation of successful test case completion
Include supporting test case documents
Oct-13
27
CREATING TRANSPORTS
Philips Healthcare
28
Steps to Create and Release Transport 1. When doing a transport, make sure that DEV appset is set to “Not Available” before creating the transport. The target system (QA or Prod) needs to also have the appset set to “Not Available” before the transport is imported into that system.
2. Go into BI back-end system and enter transaction RSA1
Click on the button Transport Connection
Oct-13
29
Steps to Create and Release Transport 3. Click on SAP Transport, then click Object Types
4. Chose More Types and expand the Environment type
Oct-13
30
Steps to Create and Release Transport 5. Double-click Select Objects and a list of BPC Environments available for transport will be shown
6. Select the BPC Environment PHILIPS_PLANNING and click Transfer Selections
Oct-13
31
Steps to Create and Release Transport 7. The Objects highlighted below are available for transport within BPC
Oct-13
32
Steps to Create and Release Transport 8. An Object can be checked or unchecked based on the need of the Object to be transported.
NOTE – for Input Schedules and Reports only the top-level folder (i.e. Input schedules) should be transported. NOT 1. Develop, 2. uat, etc.
Oct-13
33
Steps to Create and Release Transport 9. Development/Test folders will not be transported based on the above selection. Only the Root folder and its contents will be transported. NOTE – all Input Schedules that have passed User Acceptance Testing will be moved under the Input Schedules folder. The same holds true for Reports, which will be moved under the Reports folder.
Oct-13
34
Steps to Create and Release Transport 10. After the all appropriate BPC Objects have been selected the Transport Collection will begin. Average run time should be less than 5 minutes.
11. After the Collection is complete, the system will generate a Transport ID (i.e. WDCXXXXXX) and the Transport will need to be Released (click the “Release Directly” button). After transport is released addition or deletion of object cannot be done , new transport will need to be created for adding new objects
12. Send an email to [email protected] to request the Transport be imported to the target system. Include the ID of the Transport in the Email.
13. Once the transport has been imported, you can set the status of the appset back to “Available” for both the source and target appset.
Oct-13
35
CODE MANAGEMENT GUIDELINES
Philips Healthcare
36
Overview It is recommended that business users be granted the ability to make certain low-risk changes directly in the Production environment. Following this process will result in a system that requires less maintenance from an IT perspective and is more responsive to the changing needs of the Business Users.
For all other updates, a agreed-upon update/regression test/request/transport/restore process will need to be defined.
Oct-13
37
Object How Managed Comments
Security - Teams Directly in Production Best maintained without the use of transports
Security - Members Directly in Production Cannot be transported
Dimension s Directly in Production Manually maintained dimension members (PlanItem) and Properties (Category)
Standard Corp Reports Updated in Dev Transported after testing Ad hoc can be updated Production
Input Schedules Updated in Dev Transported after testing Must follow regression testing guidelines
BPC Logic & Business Rules Updated in Dev Transported after testing Must follow regression testing guidelines
Data Manager Packages & Files Updated in Dev Transported after testing Must follow regression testing guidelines
Updates to Business Process Flows
Update Template in Dev, Test, Transport
BPF Templates can be transported but Instances must be produced in Destination system
Recommended Development/Test/Deploy Guidelines
Initial Transport from Dev to QA
1. For the Initial Transport to populate the QA system, we will transport everything from Dev to QA using the BPC 10.0 Transport process. This includes all finalized Reports and Input Schedules, Dimensions, Security setups, etc.
2. Once this Transport has been created and imported into QA, the following tasks will need to be performed in QA:
a. Add all users to the QA environment through BPC Security
b. Assign the users to the appropriate BPC Teams
c. Load the Actuals and 2012 AOP transactions into QA
3. Prerequisites for Transporting to QA:
a. Creation of user ALEREMOTE using SU01 Transaction
b. Create an RFC destination to allow the import method to be executed in the correct client. Use transaction RSTPRFC to create the destination for this client.
c. The Source AND Destination systems must be offline
4. Items that DO transport across environments:
Oct-13
38
Recommended Development/Test/Deploy Guidelines
Initial Transport from Dev to QA (Cont.)
5. Items that do NOT transport across environments:
• Security rights for individual users
• Work Status Settings
• Business Process Flow Instances
Updates during SIT and UAT
Testing will occur within the QA environment. When issues arise there are two options on how to handle the needed updates:
1. Make the needed updates directly in the QA environment and then move the updates back into Dev by either replicating the adjustments or saving the input schedule/report offline and then saving the updated version back into Dev. These changes would be made exclusively by Macrospect resources.
Advantage – this will allow for MUCH faster turn-around when correcting issues located during SIT/UAT
Disadvantage:
a) This does not follow normal coding develop/test/release standards
b) There does leave room for the possibility of Dev becoming out of sync with QA
2. Making all needed changes in Dev, retesting, and then using a Transport to move the updated report/input schedule/logic script to QA
Advantage – Follows standard develop/test/release standards
Disadvantage:
a) This has the potential to greatly increase response times to getting fixes back in QA for testing
b) This will require that a Philips IT resource be available during all normal testing hours to promote Transports in 90 minutes or less
Oct-13
39
Recommended Development/Test/Deploy Guidelines
Migration to Production
The migration into Prod will follow the same processes defined for Dev to QA.
Once the environment is restored in Prod the following will take place in Prod:
1. The assigning of all users to the correct teams
2. The creation of all required Business Process Flows.
3. Adding users to the QA environment.
4. Run the Data Loads (Actual and 2012 AOP)
Once Production is up and stable for CFP Planning 1. If time permits all Business Process Flows for CFP Planning will be replicated in QA. This will be a manual process. 2. Any issues found in schedules in production will be corrected in Dev and then promoted to QA for additional
testing. Once they have been approved they will be transported to Prod using the BPC Transport process. BPC Transports of schedules/reports will overlay any files with the same name with the new version. However, it will not remove any files in the destination system that are not in the source system.
3. NOTE: Production changes to Input Schedules for material impacts to the planning cycle are allowed on an exception basis with approval of Global Healthcare VP of FP&A.
New development work in Dev 1. Once the first phase is deployed in Prod and work begins on subsequent phases (RDE, Cost Center Planning, etc)
an entirely new Environment (Philips_Planning_Prod) will be created that will retain the same landscape as the Production environment. This will allow for changes to be made and tested in an environment that mirrors Prod even after updates are made to Philips_Planning for subsequent phases.
2. The same will be created in QA.
Oct-13
40
Recommended Development/Test/Deploy Guidelines
Issues to define/discover with Customer
Definition of the process for Business Users to request a Transport from Dev for high-risk updates
Definition of the requirements to prove an update has been thoroughly tested before transport to Production
Defined minimum cycle time for transports to be released and imported
Definition of any known “black-out” periods preventing Transports into Prod
Oct-13
41
ADMINISTRATION & SUSTAINMENT
Business and Technical Roles
42
Business & Technical Roles by Interface
43
The diagram illustrates the typical administrative roles by software application / tool. Generally, business admins manage the day-to-day support of the system, and technical admins ensure system availability.
Business and Technical Roles
BPC support models vary from organization to organization. Generally speaking, some characteristics of the support structure are shared across organizations – notably the separation of functional and technical roles.
Business Admin(s)
Provide day-to-day management of BPC including security, executing data manager packages, reporting and light logic modifications in support of one or more departments / business processes
Typically members of the finance / accounting team(s) using the system
Power User(s)
Provide ongoing report development and analysis in support of one or more departments / business processes
Typically members of the finance / accounting team(s) using the system
44
Business and Technical Roles
Infrastructure / Technical Support
Provide day-to-day management of the underlying infrastructure including data integration, custom process chains and ABAP routines, infrastructure upgrades and related activities
Supports business admin(s) and power user(s) with troubleshooting of technical issues in the system
Typically members of the sustainment / technology team
45
Update Process Flow Diagram
46