how to use the write back pre- process badia248.g. ??use the write back pre-process badi ... 4.1...

Download How To Use the Write Back Pre- Process BAdIa248.g. ??Use the Write Back Pre-Process BAdI ... 4.1 Create a BAdI Implementation ... Transfer - SAP BusinessObjects EPM Solutions - SAP BO PC 7.5, version for SAP

Post on 11-Feb-2018

221 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

  • SAP BusinessObjects EPMHow-To Guide

    How To... Use the Write Back Pre-Process BAdI

    Applicable Releases:

    SAP BusinessObjects Planning and Consolidation 7.0 , version for SAPNetWeaver, SP04 and higher.

    SAP BusinessObjects Planning and Consolidation 7.5 , version for SAPNetWeaver, SP00 and higher.

    Version 1.0

    May 2010

  • Copyright 2010 SAP AG. All rights reserved.

    No part of this publication may be reproduced ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The information containedherein may be changed without prior notice.

    Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

    Microsoft, Windows, Outlook, and PowerPoint areregistered trademarks of Microsoft Corporation.

    IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,i5/OS, POWER, POWER5, OpenPower and PowerPC aretrademarks or registered trademarks of IBM Corporation.

    Adobe, the Adobe logo, Acrobat, PostScript, and Readerare either trademarks or registered trademarks of AdobeSystems Incorporated in the United States and/or othercountries.

    Oracle is a registered trademark of Oracle Corporation.

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

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

    HTML, XML, XHTML and W3C are trademarks orregistered trademarks of W3C, World Wide WebConsortium, 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 andimplemented by Netscape.

    MaxDB is a trademark of MySQL AB, Sweden.

    SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAPNetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world.All other product and service names mentioned are thetrademarks of their respective companies. Data containedin 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 affiliatedcompanies ("SAP Group") for informational purposes only,without representation or warranty of any kind, and SAPGroup shall not be liable for errors or omissions withrespect to the materials. The only warranties for SAPGroup products and services are those that are set forth inthe express warranty statements accompanying suchproducts and services, if any. Nothing herein should beconstrued as constituting an additional warranty.

    These materials are provided as is without a warranty ofany kind, either express or implied, including but notlimited to, the implied warranties of merchantability,fitness for a particular purpose, or non-infringement.

    SAP shall not be liable for damages of any kind includingwithout limitation direct, special, indirect, or consequentialdamages that may result from the use of these materials.

    SAP does not warrant the accuracy or completeness of theinformation, text, graphics, links or other items containedwithin these materials. SAP has no control over theinformation that you may access through the use of hotlinks contained in these materials and does not endorseyour use of third party web pages nor provide any warrantywhatsoever relating to third party web pages.

    SAP NetWeaver How-to Guides are intended to simplifythe product implementation. While specific productfeatures and procedures typically are explained in apractical business context, it is not implied that thosefeatures and procedures are the only approach in solving aspecific business problem using SAP NetWeaver. Shouldyou wish to receive additional information, clarification orsupport, please refer to SAP Consulting.

    Any software coding and/or code lines / strings (Code)included in this documentation are only examples and arenot intended to be used in a productive systemenvironment. The Code is only intended better explain andvisualize the syntax and phrasing rules of certain coding.SAP does not warrant the correctness and completeness ofthe Code given herein, and SAP shall not be liable forerrors or damages caused by the usage of the Code, exceptif such damages were caused by SAP intentionally orgrossly negligent.

    Disclaimer

    Some components of this product are based on Java. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.

    Any Java Source Code delivered with this product is onlyto be used by SAPs Support Services and may not bemodified or altered in any way.

  • Document HistoryDocument Version Description

    1.00 First official release of this guide

  • Typographic ConventionsType Style Description

    Example Text Words or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.Cross-references to otherdocumentation

    Example text Emphasized words orphrases in body text, graphictitles, and table titles

    Example text File and directory names andtheir paths, messages,names of variables andparameters, source text, andnames of installation,upgrade and database tools.

    Example text User entry texts. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

    Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

    EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

    IconsIcon Description

    Caution

    Note or Important

    Example

    Recommendation or Tip

  • Table of Contents

    1. Business Scenario ..........................................................................................................1

    2. Background Information .................................................................................................1

    3. Prerequisites....................................................................................................................2

    4. Step-by-Step Procedure ..................................................................................................34.1 Create a BAdI Implementation ..................................................................................34.2 Test the BAdI Implementation ................................................................................. 18

    5. Appendix ........................................................................................................................ 245.1 Source Code for BAdI Implementation .................................................................... 24

  • How To... Use the Write Back Pre-Process BAdI

    May 2010 1

    1. Business Scenario

    Note: This guide is intended to demonstrate how to use the Write Back BAdI to implement customcode to fill gap requirements. In this guide, we use the Disaggregation business scenario as anexample only. The code associated with this guide is not supported in any way by SAP, and is notguaranteed to work in all cases. Remember, this guide is to demonstrate the use of the Write BackBAdI only.

    Currently, BPC only supports planning or writing data to base members or leaves of a hierarchy. Oftentimes, the business user wants to plan at a higher level than just the base member level, especiallywhen it comes to what-if analysis. This paper covers the case where a user wants to plan data atthe parent level and distribute the values evenly to the underlying base members. This guide willdemonstrate how you can use the Write Back BAdI to accomplish this task.

    In this example, the end user would like to write enter data at a parent level Entity dimension, using aBPC Input Schedule, and evenly disaggregate or distribute that number across all of the children(base members) of that parent Entity dimension. In this guides example, we are disaggregatingevenly, however, you could perform other types of distribution, such as; based on a percentage value,or distribution based on previous years data, for example.

    The sample BAdI Implementation UJR_BADI_SAMPLE_DISAGGREGATE is shipped as an exampleimplementation for this disaggregation scenario, but this guide will demonstrate how to implement thefunctionality from scratch.

    2. Background Information

    SAP Business Add-Ins (BAdIs) are one of the most important technologies used to adapt SAPsoftware to specific requirements. As of Release 7.0 of the SAP NetWeaver Application Server ABAP,BAdIs are part of the Enhancement Framework, where they represent explicit enhancement options.BAdIs are the basis for Object Plug-Ins that can enhance the functions in ABAP programs withouthaving to make core software modifications. As such, BAdI calls can be integrated into customerapplications (like BusinessObjects Planning and Consolidation, version for SAP NetWeaver) to allowenhanced customization of standard application functionality.

    This How-To Guide (HTG) describes the procedure for implementing a BAdI that allows the end userto write data to a parent level from within the BPC for Excel Front End Client. The Step By Stepsection will outline the steps needed to create the BAdI itself as well as the configuration requiredwithin BPC to actually execute the BAdI. The Appendix s