Simple steps for creating a planning application

Hi all,
     I am trying to create a simple planning application. I need to show the actuals by hierarchies on characteristics and allow the users to plan on various levels of the hierarchy. Then, I have to generate a report comparing the previous year actuals and present plans. Please let me know the simple steps to achieve this.
Thanks.

hi Uma,
  Create planning applications ,Go THru This LInkS .
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/d-f/frequently asked questions - planning with sap netweaver bi.faq#q-6
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/s-u/sap bw business planning and simulation - how to guides list.htm
Hope this links help you to create simple planning applications.
THnaks
Varun CN

Similar Messages

  • Error Trying to create a planning application 9.3.1.2

    Hi,
    I have a problem when I try to create a new application in Planning.
    I re installed a new server from scratch with the lastest version in Oracle eDelivery (9.3.1.2), using DB2 as database.
    All is working fine (shared service, essbase, eas ...) never got an error, but i'm not able to create a planning application, I have an error at the end of the process using: http://server:8300/HyperionPlanning/AppWizard.jsp.
    For information, I have 4 different databases in DB2 (Shared Services, Essbase, Planning and the Planning Instance).
    Here is the error log I have in Tomcat:
    26 févr. 2009 10:52:08 org.apache.coyote.http11.Http11Protocol init
    INFO: Initialisation de Coyote HTTP/1.1 sur http-8300
    26 févr. 2009 10:52:08 org.apache.catalina.startup.Catalina load
    INFO: Initialization processed in 594 ms
    26 févr. 2009 10:52:08 org.apache.catalina.core.StandardService start
    INFO: Démarrage du service Catalina
    26 févr. 2009 10:52:08 org.apache.catalina.core.StandardEngine start
    INFO: Starting Servlet Engine: Apache Tomcat/5.0.28
    26 févr. 2009 10:52:08 org.apache.catalina.core.StandardHost start
    INFO: XML validation disabled
    26 févr. 2009 10:52:08 org.apache.catalina.core.StandardHost getDeployer
    INFO: Create Host deployer for direct deployment ( non-jmx )
    26 févr. 2009 10:52:08 org.apache.catalina.core.StandardHostDeployer install
    INFO: Installation d'une application pour le chemin de contexte /HyperionPlanning depuis l'URL file:C:\Hyperion\deployments\Tomcat5\HyperionPlanning\webapps\HyperionPlanning
    Creating rebind thread to RMI
    Cache Control is :public,max-age=2592000
    26 févr. 2009 10:52:12 org.apache.coyote.http11.Http11Protocol start
    INFO: Démarrage de Coyote HTTP/1.1 sur http-8300
    26 févr. 2009 10:52:13 org.apache.jk.common.ChannelSocket init
    INFO: JK2: ajp13 listening on /0.0.0.0:8302
    26 févr. 2009 10:52:13 org.apache.jk.server.JkMain start
    INFO: Jk running ID=0 time=0/31 config=null
    26 févr. 2009 10:52:13 org.apache.catalina.startup.Catalina start
    INFO: Server startup in 4781 ms
    java.util.MissingResourceException: Can't find bundle for base name HspCustomMsgs, locale fr
    java.util.MissingResourceException: Can't find bundle for base name HspImgs, locale fr
    java.util.MissingResourceException: Can't find bundle for base name HspCustomImgs, locale fr
    java.util.MissingResourceException: Can't find bundle for base name HspImgs, locale fr_FR
    java.util.MissingResourceException: Can't find bundle for base name HspCustomImgs, locale fr_FR
    [INFO] AuthChallengeProcessor - basic authentication scheme selected
    [INFO] AuthChallengeProcessor - basic authentication scheme selected
    Setting Arbor path to: C:\Hyperion\common\EssbaseRTC\9.3.1
    Connection to the datasource created successfully.
    createSchema hyperion.jdbc.base.BaseBatchUpdateException: [Hyperion][DB2 JDBC Driver][DB2]No default primary tablespace exists for the new table.
    hyperion.jdbc.base.BaseBatchUpdateException: [Hyperion][DB2 JDBC Driver][DB2]No default primary tablespace exists for the new table.
         at hyperion.jdbc.db2.DB2ImplStatement.executeBatch(Unknown Source)
         at hyperion.jdbc.base.BaseStatement.commonExecute(Unknown Source)
         at hyperion.jdbc.base.BaseStatement.executeBatch(Unknown Source)
         at com.hyperion.planning.sql.HspSetupSQLImpl.createSchema(Unknown Source)
         at com.hyperion.planning.HspManageApplication.createApp(Unknown Source)
         at com.hyperion.planning.appdeploy.HspManageAppSession.createApplication(Unknown Source)
         at HspCreateApp.Handle(Unknown Source)
         at HspCreateApp.doPost(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
         at java.lang.Thread.run(Unknown Source)
    Unable to create Scehma for application. Exiting Application Creation.
    Exception in Application Creation :Unable to create Scehma for application. Exiting Application Creation.
    java.lang.IllegalStateException: Unable to create Scehma for application. Exiting Application Creation.
         at com.hyperion.planning.HspManageApplication.createApp(Unknown Source)
         at com.hyperion.planning.appdeploy.HspManageAppSession.createApplication(Unknown Source)
         at HspCreateApp.Handle(Unknown Source)
         at HspCreateApp.doPost(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
         at java.lang.Thread.run(Unknown Source)
    java.lang.RuntimeException: Create application failed.
         at com.hyperion.planning.appdeploy.HspManageAppSession.createApplication(Unknown Source)
         at HspCreateApp.Handle(Unknown Source)
         at HspCreateApp.doPost(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
         at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
         at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
         at java.lang.Thread.run(Unknown Source)
    I think it is something related to DB2 (on a different server), but i don't know what...
    Many thanks for any help and kind regards.

    Hi,
    It looks like it is around the DB2 set up.
    In the errors you posted :-
    No default primary tablespace exists for the new table
    Unable to create Scehma for application
    So maybe it is down to tablespace or permissions
    Be sure to see the sections in the installation guide regarding DB2, also any information in the 9.3.1 readme
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Steps for Creating a Report in Oracle Apps

    I need the steps for creating a Report 2.5 in Oracle Apps.
    Please let me know the steps involved in detail
    Regards
    Choudary

    First you create the report using reports 2.5. (You need to refer Application Developer's User Guide to understand Apps standards for customization)
    Then register the report in Apps:
    1) Define the executable
    2) Place the executable in the appropriate directory (You need to refer Apps installation guide to find the directory structure for placing reports)
    3) Define the concurrent program (Pay attention when you define program parameters and value sets associated)
    4) Attach your report to the request group attached to your responsibility
    5) Run the concurrent program using SRS (you will not see the report when you open Submit Requests Form, if you do have permission)
    The above procedure is applicable if you are defining the report directly in your instance. If you are using chain link, then you may have to migrate the objects appropriately.
    Some of the above activities are usually done by System Administrator and users are not given permissions.

  • Unable to create a Planning Application

    Dear All,
    I am not able to create a Planning application. I logged in into the planning using 'admin' user , at the final step I get the error . I checked in the Essbase log file it gives the error as User/group admin already exists.
    I tried with other user also , i get the same error . Please suggest me the remedy . Thank You so much

    Hi John
    When i started the planning service in command propmpt i get the error saying HSP_Action object not found. I checked in the Database and found that this table doesnt exists in the database. Then i reconfigured the database only, from Configuration utility and after that this table appears in the database. I again started the service in commnad it runs fine now. But when I try to login in to the planning , it gives the following error in command propmt.
    java.lang.IllegalStateException: User provisioning requires CSS as the security
    provider.
    at com.hyperion.planning.appdeploy.HspManageAppSession.<init>(Unknown So
    urce)
    at com.hyperion.planning.appdeploy.HspManageAppSession.<init>(Unknown So
    urce)
    at HspCreateApp.Handle(Unknown Source)
    at HspCreateApp.doPost(Unknown Source)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
    icationFilterChain.java:237)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
    ilterChain.java:157)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
    alve.java:214)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
    eContext.java:104)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
    a:520)
    at org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
    ContextValve.java:198)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
    alve.java:152)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
    eContext.java:104)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
    a:520)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
    ava:137)
    at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
    eContext.java:104)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j

  • Steps for creating a new BAPI function module

    Hello experts,
    Can any one send me steps for creating a new BAPI function module , I got a requirement to do like this,but I dont have any clue about how to create.
    Please help !!!

    BAPI stands for Business Application Programming Interface.
    There are 5 different steps in BAPI.
    - Create BAPI Structure  
    - Create BAPI Function Module or API Method.  
    - Create BAPI object  
    - Release BAPI Function Module.  
    - Release BAPI object.
    Step1. Creating BAPI Structure:  
    - Go to <SE11>. 
    - Select Data Type & Enter a name. 
    - Click on Create.
    - Note: Always BAPI should be in a development class with request number (Not Local Object).
    - Select Structure & hit ENTER.
    - Enter the fields from your database. Make sure that the first field is the Primary Key Field.
    - Then SAVE & ACTIVATE.
    Step 2. Creating BAPI module: 
    - Enter TR.CODE <SE37>.
    - Before entering any thing, from the present screen that you are in, select the menu
       Goto -> Function Groups -> Create Group.
       Enter a name (Note: This name Must start with ZBAPI)
       Let this screen be as it is and open another window and there, enter TR.CODE <SE80).
       Click on the Third ICON that says Inactive Objects. 
       Select the group that you just created and click on Activate. 
       Notice that the group you created will disappear from the list of inactive objects.
    - Go back to <SE37> screen and enter a name and hit <ENTER>. Then enter the group name that you just created and activated.
    NOTE: When you release a function module the respective group will be attached to that particular application. It cannot be used for any other application. NEVER include an already existing group that is attached to another module.
    Now click on the first Tab that says [ATTRIBUTES] and select the radio button that says remote-enabled module since we will be accessing this from any external system.
    Then click on the second tab that says [IMPORT].
    Enter a PARAMETER NAME, TYPE and the structure you created in the first step. Also select the check box ‘Pa’. All remotely enabled functional modules MUST be Pa enabled, where Pa means ‘Passed by Value’ and if you don’t select ‘Pa’, then that means it will be passed by reference..
    Then click on tab that says [EXPORT].
    Enter the following as is in the first three fields 
      RETURN        TYPE        BAPIRETURN (These 3 field values are always same)
      Here also select ‘Pa’ meaning Pass by value.
    Note: BAPIRETURN contains structure with message fields.
    Then SAVE and ACTIVATE.
    Step 3. Creating BAPI object: 
    - Enter Tr.Code <SWO1>   (Note. It is letter ‘O’ and not Zero).
    - Enter a name and then click on create. Enter details. 
    NOTE: Make sure that that Object Type and Program name are SAME.   
    - Enter Application ‘M’, if you are using standard table Mara. If you are using your own database then select ‘Z’ at the bottom. 
    - Then hit <ENTER>. 
    - Now we have to add ‘Methods’. High light METHODS and then select the following from the menu: 
    Goto Utilities -> API Methods -> Add Methods.
    - Enter function Module name and hit <ENTER>.
    - Select the second FORWARD ARROW button (>)to go to next step. 
    - Check if every thing looks ok and again click on FORWARD ARROW button (>).
    - Then select ‘YES’ and click on <SAVE>.
    -  Now on a different screen goto TR.CODE <SE37>.  Enter Function Module name and select from the top menu  Function Module -> Release -> Release.
    - Goback to TR.CODE <SWO1>.
    Here select the menu combination shown below in the same order.
    - Edit -> Change Release Status -> Object Type Component -> To Implemented.
    - Edit -> Change Release Status -> Object Type Component -> To Released.
    - Edit -> Change Release Status -> Object Type -> To Implemented.
    - Edit -> Change Release Status -> Object Type -> To Released.
    - Then click on <SAVE>.
    - Then click on Generate Button (4th button from left hand side looks like spinning wheel).
    - Then Click on the button that says ‘PROGRAM’ to see the source code.
    To check if this is present in work flow goto TR.CODE <BAPI>. 
    Here it shows business object repository.
    - First click on the middle button and then select “ALL” and hit ENTER.
    - Goto tab [ALPHABETICAL] and look for the object that you created. This shows that the BAPI object has been created successfully.
    regards,
    aswin

  • What are the basic steps for creating a content repository?

    I am trying to create a document store on a file system (fsdb) that will hold files that are ftp's to that location. Is this possible using KM? If so, what are the basic steps for creating a file system repository and using it through KM? I have found stuff on help.sap.com but that only tells you what each component does not what actual steps need to be taken to setup KM, such as user rights , creating an entry point, so that all of KM is not visible, etc...
    If anyone knows of any guides that show a step by step process that would be great too.
    Thanks
    Paul

    Hi Paul
    First of all you need to create a new repository
    Suppose you want to add all the documents under folder Paul under C: Drive
    (Even you can put whole documents of C: drive into Paul)
    Navigate to System Admin -> System Configuration -> Knowledge management -> Content Management -> Repository Manager -> File System Repository
    There you can create a new directory by clicking on button New
    Give the parameters as follows :-
    Name               :           Anything you like
    Description       :           Anything you want
    Prefix (must start with /)  :  Probably same as your repository name like \Paul
    Lookup mode : caseless
    Root Directory   :  C:\Paul
    NOTE:  This is the trick. You need to give the proper path means folder path which you want use as repository)
    Repository Services  :  Any services you want
    Property Search : Managercom.sapportals.wcm.repository.manager.generic.search.SimplePropertySearchManager
    Security Manager         :           AclSecurityManager
    ACL Manager Cache   :           ca_cm_rep_acl
    The save it
    Now see whether the same repository is coming under KM Content or not, if not may be after restart it will come.
    I think the above information will help you. If still you have problem, please feel free to contect me.
    Regards,
    Chamkaur

  • Steps for creating structural authorization profile using trans. OOSP

    Dears,
    Could someone please guide to the steps for creating a structural authorization profile using transaction OOSP, to authorize on the HR Payroll Area.
    Thanks.
    Reda

    Hi,
    There are comprehensive guidelines on help.sap.com for creation of structural authorizations: http://help.sap.com/saphelp_erp2004/helpdata/en/34/49ba3b3bf00152e10000000a114084/content.htm
    However, please bear in mind that you cannot limit access to certain payroll area with structural authorization. For that you should use standard PA authorization object (you can use field organizational key to store Payroll Area VDSK1 in IT0001):
    P_ORGIN  http://help.sap.com/erp2005_ehp_02/helpdata/en/3e/b8b83b5b831f3be10000000a114084/content.htm
    Cheers

  • More simple way for creating dummy variables

    I am finding for more simple way for creating dummy variables.
    For analyzing by linear regression, logistic regression ... creating dummy variables from categorical data is necessary.
    Most simplest way for creating dummy variables is may be pivot function.
    But I need more simple method.
    Anyone's idea. I welcome.
    Naoya Ikeda

    Hi Naoya. Can you give an example of a sample input and output, with a description of what you'd like to do?
    Thanks,
    Ehren

  • Steps for creating abap query

    hi sap gurus,
    can i steps for creating abap query
    plz help me on this.
    regards,
    balaji.t
    09990019711

    Hi
    Please check this link for a document on ABAP query. It explains the process step by step with screen shots..
    http://www.auditware.co.uk/downloads/SAPQuery_step_thru.pdf
    Thanks,
    Ravi

  • Steps for creating a SAP Remote cube.

    Hello Experts,
    Can you anyone list the steps for creating a SAP Remote cube please?
    Any step by step guide will be of really great help.
    Thanks in advance.
    Regards,
    Kumar.

    Creating VirtualProviders Based on Data Transfer Processes Locate the document in its SAP Library structure
    Prerequisites
    If you are using a DataSource as the source for a VirtualProvider, you have to allow direct access to this DataSource.
    Procedure:
           1.      In the Data Warehousing Workbench under Modeling, choose the InfoProvider tree.
           2.      In the context menu, choose Create VirtualProvider.
           3.      As the type, select VirtualProvider based on data transfer process for direct access.
    In terms of compatibility, a VirtualProvider that is based on a data transfer process with direct access can also be connected to an SAP source system using a 3.x InfoSource.
    The Unique Source System Assignment indicator controls whether this source system assignment needs to be unique. If the indicator is set, you can select a maximum of one source system in the assignment dialog. If the indicator is not set, you can select multiple source systems. In this case, the VirtualProvider acts like a MultiProvider.
    If the indicator is not set, characteristic 0LOGSYS is automatically added to the VirtualProvider when it is created.  In the query, this characteristic allows you to select the source system dynamically: In each navigation step, the system only requests data from the assigned source systems whose logical system name fulfills the selection condition for characteristic 0LOGSYS.
           4.      Define the VirtualProvider by transferring the required InfoObjects. Activate the VirtualProvider.
           5.      In the context menu of the VirtualProvider, select Create Transformation. Define the transformation rules and activate them.
           6.      In the context menu of the VirtualProvider, select Create Data Transfer Process. DTP for Direct Access is the default value for the DTP type. Select the source for the VirtualProvider. Activate the data transfer process. See Structure linkCreating Data Transfer Process for Direct Accesss.
           7.      Activate direct access. In the context menu of the VirtualProvider, select Activate Direct Access. In the dialog box that appears, choose one or more data transfer processes and select This graphic is explained in the accompanying text Save Assignments.
    Check this for little extra info:
    /thread/142088 [original link is broken]

  • Step By Step Procedure to create a Planning Application

    Hi All,
    I am new to BPS, can any one plz provide the document to create a sample Planning Application in Step-By-Step procedure......
    [email protected]
    Thanks in Advance
    Regards
    Ramakrishna Kamurthy

    Hi,
    Pls go to :SDN-> elearning>SAP Business Intelligence->Begineers/Intermediate Courses--> (There are 4 demo's -step by step)1. Planning Modeler -eBook Oct 2007 10 min 
    This eBook Shows the easy of use the planning modeler for the creation of a plannng model with abministration tasks.
    2.Planning: Variable Wizard - eBook Oct 2007 2 min 
    3.Web-based Planning with SAP BW-BPS
    Also Pls chk this links;
    create planning applications,
    http://help.sap.com/saphelp_sem320bw/helpdata/en/05/242537cedf2056e10000009b38f936/frameset.htm
    http://help.sap.com/saphelp_sem350bw/helpdata/en/05/242537cedf2056e10000009b38f936/frameset.htm
    Hope this helps,
    regards
    CSM Reddy

  • STEPS for creating IDOC .

    I need to creat IDOC for whenever  delivery is created .

    Hi
    Take the correct Idoc type and Message Type and process code from EDBAS and EDMSG tables and use
    see the doc
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Steps to migrate Hyperion Planning application from 9.2.0 to new 9.3.1 env

    We currently have 9.2.0 Hyperion planning installed in a windows env. We are planning to setup a new Hyperion planning env on a totally new hardware upgraded env. Would be appreciate if some can outline steps invloved to migrate Hyperion Planning apps, forms, BR ect from 9.2.0 to the newly setip 9.3.1 env. Is there any documentation, URL's to do the above. Any help would be greatly appreciated. Any issue to look out for, setbacks details would be helpful.
    Thanks..

    Hi,
    One way of doing it would be :-
    Create a new database for your planning application 9.3.1
    Create a datasource to the database
    Create a fresh planning application on version 9.3.1 make sure the admin is the same name as your old 9.2 planning app
    Go into the database tables for the planning app and look at table HSP_USERS, store the SID value against user 50001
    Go into the database planning system tables and HSPSYS_APPLICATION, clear out the version field for the application you have created
    Stop Planning
    Restore the 9.2 planning application database over the one created in the first step
    Go into the HSP_USERS table and update the SID for user id 50001
    Start planning
    Go to planning web and you should see your application when you try and log in it should take you to a migrate screen.
    If you are requiring to migrate users as well, you will have to make sure you create them in Shared Services and then use the updateusers utility in the planning bin directory.
    Or you could try using the copy app utility though I don't believe it is the best utility about and not sure how it handles between different versions(http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_hp_admin/ch09s01.html)
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Financial report for essbase and planning application

    Hi,
    Can any one please explain me what is the difference between creating financial report for essbase application and planning application.
    Considering we will have Essbase cube for the planning application
    Thanks in advance

    Correct, the data that is stored in Essbase will be the same regardless of which connection type you use.
    Data that is only stored in Planning can only be retrieved using a Planning connection. This includes Supporting Detail and SmartLists as these are stored in the Planning relational database.
    As a general rule I always use an Essbase connection unless i specifically want to get supporting detail or smartlists but that is just me.
    Hope this helps
    Stuart

  • Error while creating hyperion planning application in 11.1.1.1.0

    Hi All,
    I am using EPM system 11.1.1.1.0 and i get the following error while trying to create a new application using Hyperion Planning:
    Unable to find JDBC_CATALOG key for application: ABC1+
    Connection to the datasource created successfully.+
    in cpp -Created NonUnicode App:ABC1 0+
    Unable to create Analytical application. Exiting Application Creation.+
    Exception in Application Creation :Unable to create Analytical application. Exit+
    ing Application Creation.+
    java.lang.IllegalStateException: Unable to create Analytical application. Exitin+
    g Application Creation.+
    at com.hyperion.planning.HspManageApplication.createApp(Unknown Source)+
    at com.hyperion.planning.appdeploy.HspManageAppSession.createApplication+
    *(Unknown Source)*
    at HspCreateApp.Handle(Unknown Source)+
    at HspCreateApp.doPost(Unknown Source)+
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)+
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)+
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl+
    icationFilterChain.java:252)+
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF+
    ilterChain.java:173)+
    at HspValidationFilter.doFilter(Unknown Source)+
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl+
    icationFilterChain.java:202)+
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF+
    ilterChain.java:173)+
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV+
    alve.java:213)+
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV+
    alve.java:178)+
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j+
    ava:126)+
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j+
    ava:105)+
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal+
    ve.java:107)+
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav+
    a:148)+
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java+
    *:869)*
    at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p+
    rocessConnection(Http11BaseProtocol.java:664)+
    at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo+
    int.java:527)+
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol+
    lowerWorkerThread.java:80)+
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP+
    ool.java:684)+
    at java.lang.Thread.run(Unknown Source)+
    java.lang.RuntimeException: Create application failed.+
    at com.hyperion.planning.appdeploy.HspManageAppSession.createApplication+
    *(Unknown Source)*
    at HspCreateApp.Handle(Unknown Source)+
    at HspCreateApp.doPost(Unknown Source)+
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)+
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)+
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl+
    icationFilterChain.java:252)+
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF+
    ilterChain.java:173)+
    at HspValidationFilter.doFilter(Unknown Source)+
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl+
    icationFilterChain.java:202)+
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF+
    ilterChain.java:173)+
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV+
    alve.java:213)+
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV+
    alve.java:178)+
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j+
    ava:126)+
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j+
    ava:105)+
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal+
    ve.java:107)+
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav+
    a:148)+
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java+
    *:869)*
    at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p+
    rocessConnection(Http11BaseProtocol.java:664)+
    at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo+
    int.java:527)+
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol+
    lowerWorkerThread.java:80)+
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP+
    ool.java:684)+
    at java.lang.Thread.run(Unknown Source)+
    Error terminating Essbase connection: java.lang.NullPointerException+
    If somebody can please help me resolve this issue , it would be great.
    Thanks in Advance.
    Alicia

    I suspect that this is caused by an "incorrect" datasource definition when you create a new one.
    I noticed that when I created an Essbase DB through the Essbase Enterprise Admin Service, it only allowed me to create one for localhost, not my server name EVEN if when the "Manage Data Source" validated the connection.
    This points to one of the myriad of apps inconsistently trying to resolve a server name.
    So, in EAS, see if you can connect to your local Essbase install and if successful, use the exact same params for you Workspace Application.
    Hope that helps.

Maybe you are looking for


HashFlare