sap businessobjects epm rig how-to guide...sheldon is an active contributor to sap developer network...

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 1

SAP BusinessObjects EPM RIG

How-To Guide

Title:

How to Generate product and customer data views using SAP BusinessObjects Planning and Consolidation, SAP BusinessObjects Profitability and Cost Management, and SAP BusinessObjects Financial Information Management

Applies to:

SAP BusinessObjects Planning and Consolidation 7.5, version for Microsoft

SAP BusinessObjects Profitability and Cost Management 7.5

SAP BusinessObjects Financial Information Management 7.5 (SP06 or greater)

Summary

The objective of this study is to understand the mechanisms for transferring transactional data from SAP BusinessObjects Planning and Consolidation (BPC) into SAP BusinessObjects Profitability and Cost Management (PCM) using SAP BusinessObjects Financial Information Management (F.I.M.). Once data is successfully transferred into the PCM application allocations are processed to provide additional Customer and Product data segmentation.

Authors: Sheldon Edelstein, Jeffrey Holdeman, and Sushma Sandepogu

Company: SAP BusinessObjects EPM Regional Implementation Group

Created on: 16th November 2010

SAP BusinessObjects EPM RIG How-To Guide


© 2010 SAP AG 2

Sheldon Edelstein

Sheldon Edelstein is a RIG [Regional Implementation Group] Specialist specializing in SAP BusinessObjects Planning & Consolidations [BPC] and the SAP EPM [Enterprise Performance Management] product suite. Sheldon has ten+ years experience specializing in Planning and Analytic applications for large scale implementations. As a former SAP Platinum consultant, he has implemented planning solutions for over a dozen large scale projects. His current area of

focus is BPC, but has previously specialized in BI-IP [Integrated Planning] and BW-BPS [Business Planning and Simulation]. Sheldon is an active contributor to SAP Developer Network (SDN) responding to EPM forum inquiries, actively blogging on a variety of topics, and publishing “How To Guides” for use by the extended SAP community. Wiki: https://wiki.sdn.sap.com/wiki/display/profile/Sheldon%20Edelstein

Jeffrey Holdeman

Jeffrey Holdeman joined the SAP BusinessObjects Regional Implementation Group (RIG) for Enterprise Performance Management (EPM) in 2007. He works as a Product Specialist for the Profitability and Cost Management and the SAP BusinessObjects Planning and Consolidation solutions. Previously, Jeff worked for 10 years at SAP America, Inc. as a Platinum Principal Applications Consultant where he was a key contributor and impact player in the success of nine customer ERP/BW/SEM go-lives, including all aspects of project lifecycles. He has also

performed spot consulting and SAP Safeguarding services for more than 60 customers requiring in-depth and expert product knowledge of SAP Financials. Jeff is an active contributor to the SAP Developer Network (SDN). Wiki profile: http://wiki.sdn.sap.com/wiki/display/profile/Jeffrey+Holdeman

Sushma Sandepogu

Sushma Sandepogu has joined the SAP BusinessObjects Regional Implementation Group (RIG) in July of 2008 as a Product Specialist in SAP BusinessObjects Planning and Consolidation. She provides the back office support to Ramp-up customers of SAP BO PC, helps the customers in smoother implementation of SAP BO PC. Before joining the Enterprise Performance Management Regional Implementation Group (EPM RIG) she was part of SAP BusinessObjects Planning and Consolidation Product Support group supporting a large number

of customers for over 1 and half year. She also worked on the SAP Visual Composer tool. She joined the SDN communities and is a regular contributor to the forums.

https://wiki.sdn.sap.com/wiki/display/profile/Sheldon%20Edelstein

https://www.sdn.sap.com/irj/sdn/bc?u=ecvUlwHaLy0%3D

http://wiki.sdn.sap.com/wiki/display/profile/Jeffrey+Holdeman



© 2010 SAP AG 3

Table of Contents

1. Scenario ........................................................................................................................................... 4

2. SAP BusinessObjects Planning & Consolidations (BPC) Data Model ................................................ 5

BPC Master Data Detail ............................................................................................................................. 6

3. Profitability Cost Management (PCM) Data Model........................................................................... 10

PCM Master Data Detail .......................................................................................................................... 10

4. SAP BusinessObjects Financial Information Management (F.I.M) ................................................... 14

5. Step by Step Process for Transferring BPC data into PCM ............................................................. 15

5.1 Logging on to F.I.M. ........................................................................................................................ 15

5.2 Create the Planning and Consolidation (BPC) Connection .............................................................. 15

5.3 Create the Profitability and Cost Management (PCM) Connection ................................................... 18

5.4 View the F.I.M. Connection Summary ............................................................................................. 19

5.5 Creating a F.I.M. Job ...................................................................................................................... 20

5.6 F.I.M. Job definition: General Properties: ....................................................................................... 20

5.7 F.I.M. Job definition: Source Properties.......................................................................................... 21

5.8 F.I.M. Job definition: Setting up the Target System ........................................................................ 22

5.9 F.I.M. Job definition: Defining Mapping Tables ............................................................................... 23

5.10 F.I.M. Job definition: Creating the Mapping Table........................................................................... 23

5.11 F.I.M. Job definition: define mapping table rules ............................................................................. 26

5.12 F.I.M. Job definition: Job Execution................................................................................................ 30

5.13 F.I.M. Job definition: View Job History............................................................................................ 30

6. Analysis of the results ..................................................................................................................... 31

7. Allocation to Customer and Product in PCM.................................................................................... 35

PCM Allocation Summary:........................................................................................................................... 40

Related Content .......................................................................................................................................... 41

Copyright .................................................................................................................................................... 42



© 2010 SAP AG 4

1. Scenario

Businesses need to efficiently move data between various specialized applications. These data extraction/loads must be able to be automated and controlled to insure that only the required records are transferred at the appropriate time. SAP BusinessObjects Financial Information Management (F.I.M.) achieves this through use of job definition and scheduling, as well as providing a means to efficiently define complex mapping and transformation/conversion of data between differing application data models.

This guide focuses on using the allocation capabilities of SAP BusinessObjects Profitability and Cost Management (PCM) on data sourced from SAP BusinessObjects Planning and Consolidation (BPC). Financial data is extracted from BPC, PCM allocates this data to the customer and product levels allowing customer and/or product based reporting and decision making.



© 2010 SAP AG 5

2. SAP BusinessObjects Planning & Consolidations (BPC) Data Model

The source data for our integration scenario comes from the PLANNING application defined within BPC. We use a copy of the delivered application set, “ApShell”.

The PLANNING application was constructed using seven dimensions:

Category examples: “PLAN”, “ACTUAL”

P_ACCT examples: account numbers

P_Activity examples: “Hours”, “Labor”

P_CC examples: cost center ids

P_DataSrc examples: “Manual”, “Upload”

RptCurrency examples: “LC” (local currency), “USD” (USA dollars)

Time examples: “2011.JAN” for January, 2011



© 2010 SAP AG 6

BPC Master Data Detail

Category

The Category dimension provides an identifier to allow a broad group assignment of data classification

For example, the category “ACTUAL”, refers to data from real transactions.

“PLAN” refers to data that is projected in a planned future scenario

P_ACCT (Planning Account)

P_ACCT provides a dimension identifier of the specific account assignment for the reported transaction.

The P_ACCT dimension was mapped to the equivalent PCM “Line Item” dimension.



© 2010 SAP AG 7

P_Activity: (Planning Activity)

P_Activity provides an additional dimension identifier of the data to indicate specific origins of the record.

For example, “MAINT” is typically used to identify the transaction as having been associated with a maintenance activity

In this study, the BPC P_Activity dimension was not mapped into PCM (PCM has its own concept of Activity which is used to facilitate allocations).



© 2010 SAP AG 8

P_CC (Planning Cost Center)

P_CC indicates the relevant cost center that is associated with the transactional record.

In this integration exercise, P_CC represented “country” and geographic area.

This dimension was mapped to the PCM dimension called “Responsibility Center”.

P_DataSrc (Planning Data Source)

P_DataSrc provides a dimension identifier of how data was delivered into the system.

For example, “MANUAL” is typically used to indicate that a record was entered using a planning input schedule and “UPLOAD” is typically used to indentify records that were loaded using an automated load process.



© 2010 SAP AG 9

RptCurrency (Reporting Currency)

RptCurrency provides a dimension identifier for the currency represented by the amount associated with the record.

LC (Local Currency) is a typical currency designation to indicate the amounts represented in the record are based upon the “local currency” of the entity indentified with the record. The system recognizes what constitutes “local” by the assignment of properties in the entity dimension.

This dimension was mapped to the PCM dimension called “Currency”.

TIME

The Time dimension provides an identifier for the time relevancy for the data. In BPC, Time is typically identified using monthly, quarterly, and annual references. The format of the dimension is YYYY.MMM for monthly Time Ids. This dimension was mapped to the PCM dimension “Periods”



© 2010 SAP AG 10

3. Profitability Cost Management (PCM) Data Model

PCM Master Data Detail

Versions

In PCM a common design approach for the Version master data is to combine Category with a Year. For example “PLAN 2010”.

PCM hierarchies and attributes are used to consolidate the versions into logical groupings.



© 2010 SAP AG 11

Periods

In PCM a common design approach for the Period master data is to use the monthly names (for example “January”). PCM attributes are used to consolidate specific periods into logical groupings (for example “Q1”).



© 2010 SAP AG 12

Responsibility Center

In PCM the Responsibility Center is used to represent an organization‟s enterprise structure.

In this demonstration model the Responsibility Center‟s have been defined identically to the BPC Entity dimension members.



© 2010 SAP AG 13

Line Item

In PCM the Line Item is used to represent an organization‟s G/L account structure.

In this demonstration model the Line Item‟s have been defined identically to the BPC Account dimension member ID‟s.

Attributes are used to consolidate the accounts into logical groupings.

A Data Alias called “Reporting Alias” was created to hold the BPC account description which can be used to display the Line Items hierarchy in reporting using the text descriptions instead of the ID‟s.



© 2010 SAP AG 14

4. SAP BusinessObjects Financial Information Management (F.I.M)

F.I.M. is a web-based solution that allows a financial business user to do the following:

Ability to connect to variety of existing EPM solutions

Maintain complex mappings

Define and Launch data movement processes using a single tool

Facilitates data transfers between various databases and applications including: Financial Consolidation, Planning and Consolidation, Strategy Management, and Profitability and Cost Management applications.

The Financial Information Management solution is a tool that combines an easy-to-use web based interface that is connected to SAP BusinessObjects Data Services.

The F.I.M. application allows the user to define “jobs” (collections of activities that include mapping tables and job execution instructions), and system connections.



© 2010 SAP AG 15

5. Step by Step Process for Transferring BPC data into PCM

5.1 Logging on to F.I.M.

“Single-Sign On” (SSO) (facilitated by incorporating Business Objects Enterprise's User Management System) provided the capability for F.I.M. to authenticate between all involved applications. Using SSO was a necessary requirement for F.I.M. to access BPC and PCM content.

5.2 Create the Planning and Consolidation (BPC) Connection

Before a F.I.M. business user can create or execute a F.I.M. job, a F.I.M. administrator must create connections to source databases and target applications. Connections are stored in the financial information management repository.

Creating a Planning and Consolidation Connection:

Create the new BPC Connection in F.I.M. by logging in an Administrator role

Click “List of Connections”

Click “New”



© 2010 SAP AG 16

Under “Connection Type” select “SAP BusinessObjects Planning and Consolidation”

In the “Connection Name” box, type a free form unique name to identify the connection.

In the “Web Service URL” box, type the web service deployed in the Planning and Consolidation application. Also make sure to include port information and terminate the web service URL with a back slash (“/”).

Click on “Test Connection” to establish the connection and populate the AppSet selections.



© 2010 SAP AG 17

The AppSet dropdown will populate if the connection tests successfully. Select the target application set (“RIG_LANDSCAPE” in this example) that will be used to extract the source data.

Save the connection definition



© 2010 SAP AG 18

5.3 Create the Profitability and Cost Management (PCM) Connection

Create a NEW connection for target application (PCM)

Enter a Connection Name, the URL for the PCM web service, database type, server, name, and database logon credentials. Test connection. No need to enter Model information.



© 2010 SAP AG 19

5.4 View the F.I.M. Connection Summary

Source and Target Systems Connections are established



© 2010 SAP AG 20

5.5 Creating a F.I.M. Job

The F.I.M. Job:

establishes the source and target for data transfer

defines mapping tables to be used

populates the mapping tables

schedules the job for execution

provides access to execution logs

Create a new Job by clicking on “New”:

5.6 F.I.M. Job definition: General Properties:

Enter a “Name of the Job”, “Job Description” and select the users who would be accessing the job.



© 2010 SAP AG 21

5.7 F.I.M. Job definition: Source Properties

Select the “Connection” radio button and Select the BPC source system set up in section 5.2.

Once the source system is selected, all the Applications within the Appset are displayed. Select the PLANNING Application from the dropdown list:



© 2010 SAP AG 22

5.8 F.I.M. Job definition: Setting up the Target System

On the Target Properties tab select the Target System PCM75 to establish the connection.

Select the Measure value to be used to contain the numeric data in the target system (i.e. “LineItemValue” key figure in PCM) and click Next Button.



© 2010 SAP AG 23

5.9 F.I.M. Job definition: Defining Mapping Tables

Create the mapping table to map the source system fields (BPC) to the target system fields (PCM). Start by creating a Mapping Table:

5.10 F.I.M. Job definition: Creating the Mapping Table

Each time you click on the “Create Mapping Table” button, the system creates a new tab in the mapping table definition. The new tab can be double clicked to change its name. In this example, we defined the first tab in the mapping table as “AMOUNT2VALUE” (BPC record “amount” “to” PCM record “value”). The body of the mapping table presents source and target files. Select one or more source fields that will be mapped into one target field. In this example, the source field “AMOUNT” and the target field “Value”.



© 2010 SAP AG 24

Click on the “Create Mapping Table” button and define the CATEGORY2VERSION mapping table. Map the Source Column “Category” and “Time” to the Target “Version” (Note: “Version” in PCM is typically of the form “ACTUAL 2009”, this requires the mapping of two BPC dimensions, CATEGORY and TIME to properly define PCM “Version”.)

Click on the “Create Mapping Table” button and define the CC2RESPCENTER mapping table. Map the Source Column “P_CC” to the Target “RespCenter”



© 2010 SAP AG 25

Click on the “Create Mapping Table” button and define the PACCT2LINEITEM mapping table. Map the Source Column “P_ACCT” to the Target “LineItem”

Click on the “Create Mapping Table” button and define the RPT2CURRENCY mapping table. Map the Source Column “RptCurrency” to the Target “Currency”



© 2010 SAP AG 26

Click on the “Create Mapping Table” button and define the TIME2PERIODS mapping table. Map the Source Column “Time” to the Target “Period”

5.11 F.I.M. Job definition: define mapping table rules

Each entry in the mapping table requires a transformation rule to be defined. In this case, all BPC values (“*”) will be mapped without modification to the targeted PCM key figure value. The amount to be transferred to the PCM key figure is represented by [AMOUNT].



© 2010 SAP AG 27

“Version” in PCM is typically presented in the form “Version Year”. The mapping of two BPC dimensions, CATEGORY and TIME are therefore required to properly define the target PCM “Version”. This transformation rule selects the value of Category and Time from the BPC record, then selects the appropriate string components from these values and concatenates them into the required PCM format for Version (i.e.: Actual 2009).

Note the use of special F.I.M. editing characters that construct the new target PCM Version from the two BPC dimensions, Category and Time:

“init_cap” capitalizes the first letter in the Category member id and forces the remaining letters into lowercase

“||” concatenates the Category string, Time string, and a space („ „)

“substr” starts from position 1 and then counting 4 positions to the right takes only the remaining characters. Since TIME in BPC is represented as MMM.YYYY this function returns only the YYYY portion.

All BPC cost center values (“*”) will be mapped without modification to the targeted PCM “RespCenter”. The value transferred to the PCM RespCenter dimension is represented by [P_CC].



© 2010 SAP AG 28

Each entry in the mapping table requires a transformation rule to be defined. In this case, all BPC account (P_Acct) values (“*”) will be mapped without modification to the targeted PCM “LineItem”. The value transferred to the PCM LineItem dimension is represented by [P_ACCT].

Only BPC reporting currency (RptCurrency) values equal to “LC” (local currency) will be mapped to the PCM Currency dimension with a value of “NON” (this dimension had only three characters, so “NON” was short for “NONE”).



© 2010 SAP AG 29

Each entry in the mapping table requires a transformation rule to be defined. In this case, all BPC time values (defined in BPC using a MONTH.YEAR format) will be mapped to the PCM Period dimension (defined as only consisting of MONTH).



© 2010 SAP AG 30

5.12 F.I.M. Job definition: Job Execution

Once the mapping table has been constructed the data transfer job can be executed. Click on the “Execute” button to run the job, which will start the process of moving the records from the BPC system to the PCM system.

5.13 F.I.M. Job definition: View Job History

The execution of the F.I.M. job creates a Job History log. In our example job, BPC2PCM, the job ran successfully. A total of 3770 records were imported from the BPC MS system into the PCM system.



© 2010 SAP AG 31

6. Analysis of the results

In BPC 5,589 records exist in the source application (“PLANNING”). Since we are ignoring the P_Activity and P_DataSrc dimensions when loading data into PCM the actual number of records that will be transferred with be less than 5,589 records.



© 2010 SAP AG 32

BPC Transaction Data - Unique Records

The P_Activity and P_DataSrc dimensions from BPC were not mapped into PCM using the F.I.M. mapping tables. As a result, F.I.M. aggregates across all P_Activity and P_DataSrc values and transfers only the unique records from BPC to PCM. Analyses of the BPC transactional Db tables indicate that there are a total of 3,770 unique records in the application.



© 2010 SAP AG 33

PCM Transaction Data Line Item Values

In PCM the LineItemValues table confirms that 3,770 records were loaded by the F.I.M job.



© 2010 SAP AG 34

BPC/PCM Transaction Data

Total Cost for Plan 2008 = $155,805,620 -- both PCM and BPC agree at total and subtotal detail.

PCM total = $155,805,620.45

BPC total = $155,805,620.45



© 2010 SAP AG 35

7. Allocation to Customer and Product in PCM

PCM allocates line item values (represented as resources in the graphic) using a two step process. First PCM allocates each record to an Activity, and then each record is allocated to one or more cost objects (i.e. Customer and Product).

Resource Drivers are assigned to Line Items and used to allocate costs to Activities. Since activity allocation is not the focus of this HTG the Percentage resource driver was used for all line items.

In practice other resource drivers are commonly used, such as:

Headcount

Labor Hours

Machine Time

Utility Usage

Square Meters

Etc.

Resource Driver Values

In PCM the ResourceDriverValues table contains a Resource Driver value for each combination of Responsibility Center, Period, and Version.

Since Activity-based costing is not the focus of this demonstration the value of “1.0000” is assumed for the “Percentage” Resource Driver against all intersections of Version, Period and Responsibility Center:



© 2010 SAP AG 36

Resource Driver Split Values

In PCM the ResourceDriverSplitValues table determines how much of the Resource Driver value is related to an Activity for each Responsibility Center, Period, and Version combination. In this demonstration it is assumed that resources are split 40/60 between Corporate activities and Manufacturing activities:

Resource Driver Percentage Split Values

In PCM the ResourceDriverPctSplit Values table determines how much of the Resource Driver value is related to an Activity for each Responsibility Center, Period, and Version.

In this demonstration it is assumed that resources are split 40/60 between Corporate activities and Manufacturing activities. This value was automatically calculated by the system:



© 2010 SAP AG 37

Activity Values

Activity values are automatically calculated by the system and therefore input values are not allowed, nor can PCM Rules be written against Activities to derive values using formulas.

Activity-based costing is not the purpose of this demonstration so a simplified activity structure and cost flow will be utilized to focus the demo on allocating BPC data onto customers and products.



© 2010 SAP AG 38

Activity Driver Values

The Activity Drivers dimension represents quantitative measures of the processes involved in producing the outputs of your organization. For example, the number of sales is used in this demonstration.

The Activity Driver Values are used to distribute activity costs through to Cost Objects:



© 2010 SAP AG 39

Cost Object Assignment

The Cost Object Assignments function uses Activity Drivers to associate Activity, Line Item, and Responsibility Center costs with specific Cost Object combinations:

Cost Object Values

Cost Object Values are the outputs of a Profitability and Costing model. These costs are generated by the built-in Calculation Engine, but this depends on several factors that include the specification of Cost Object Assignments.

These may be complex combinations of up to five different Cost Object dimensions. In this demonstration just Customers and Products have been utilized:



© 2010 SAP AG 41

Related Content

BPC Master Guides:

http://service.sap.com/~sapidb/012002523100011196792009E/SBOP_PC_75_M_SP04_Master.pdf

http://service.sap.com/~sapidb/011000358700001106942009E/SBOP_PC_75_NW_SP03_Master.pdf

PCM Master Guide:

http://service.sap.com/~sapidb/011000358700000225782009E/FPM75_PCM_Master_en.pdf

F.I.M. Master Guide:

http://service.sap.com/~sapidb/011000358700000289492009E/FPM75_FI_MasterGuide_en.pdf

http://service.sap.com/~sapidb/012002523100011196792009E/SBOP_PC_75_M_SP04_Master.pdf

http://service.sap.com/~sapidb/011000358700001106942009E/SBOP_PC_75_NW_SP03_Master.pdf

http://service.sap.com/~sapidb/011000358700000225782009E/FPM75_PCM_Master_en.pdf

http://service.sap.com/~sapidb/011000358700000289492009E/FPM75_FI_MasterGuide_en.pdf



© 2010 SAP AG 42

Copyright

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,

PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,

BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and

other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP

Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the

express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

sap businessobjects epm rig how-to guide...sheldon is an active contributor to sap developer network...

Documents