Plan/Forecast Scenario in HFM - best practice

Hello all,
We're currently working on adding a Plan and Forecast scenarios to HFM
to incorporate some budgeting, which had previously been done in
Excel/Access. For those of you who do planning in HFM, would you care
to briefly summarize your processes?
1) How do you load the data into your HFM plan/forecast scenario?
Excel spreadsheet? FDM Multi-Load? Webform?
2) If you use Excel, do you just allow the users to submit via the
template using SmartView or formulas? What about audit/controls?
3) Do you let the users consolidate whenever they want?
Any other tips would be greatly appreciated!
Thanks

We've been doing budgeting forecasting for awhile in HFM.... However.... We leaving that and going to Hyperion Planning...
Some things you are going to want to consider:
1) You will probably have more people entering budgets \ forecasting then actuals, so there might be licensing cost.
2) Security will need to be considered, who get's what and where.
3) Budgeting \ Forecasting is usually done at a more granular level then rolled-up. This could make your HFM application much larger or more detailed then necessary.
4) If you re-org, which we do, we have to reconsolidate all the scenarios and all the years. Time consuming.
5) The is one rule file, making divisional or cross-company modeling difficult. For instance, one of our divisions has a very complex allocation model which we could not build in HFM.
6) Its not uncommon for users to ask for a rolling forecast, which can be done in HFM at the cost of more scenarios. Also, versioning is difficult in HFM.
7) Reporting will also need to be considered, who does it, how it looks and who gets what report.
With Planning, we don't have the above issues.
To answer your questions before moving to Planning:
1) How do you load the data into your HFM plan/forecast scenario, Excel spreadsheet, FDM Multi-Load, Webform? 90% use the data grids, 5% FDM (International or not on our GL) 5% SmartView (Powerusers)
2) If you use Excel, do you just allow the users to submit via the template using SmartView or formulas? What about audit/controls? How do you handle that in actuals? Our controls are handled via security
3) Do you let the users consolidate whenever they want? Yes - at the expense of users running consolidations over each-other

Similar Messages

  • SOX Compliance in HFM- Best Practice

    Hi guys,
    Is there any "best practice" for SOX compliance in HFM? Can you do it by using Shared Services? Should I work with the .SEC file?
    Have you ever been required to do so? I was asked to do so, but since it's not my field, I'm kind of lost...
    Any advice would be greatly appreciated.
    Thanks!
    Jay

    SOX covers a number of topics. Ask for the request list from the SOX auditors, and then go through each item and determine where in the system is the best source.
    The .sec file is likely not going to work. There is a provisioning report that is more helpful for user access.

  • Scenario runtime parameters best practices

    Hi,
    I have a scenario which uses dynamic input values. Iam trying to understand what is best practice to initialise input configuration values considering the scenario is automatic.
    (something like configuration initialisation parameters)
    Option in my mind
    1. variables (which can be passed at runtime however have to be input manually)
    2. Flexfields (sounds a good idea but not sure if i migrate across environments flexfields will also be migrated?)
    3. Procedure Options ( can the procedure options be changed at runtime?)
    please let me know your suggestions.

    Hi John,
    I think it's best if you use a variable, and refresh that variable from a database query at runtime.
    You can setup a lookup/config table which has key/value pairs, the key being the variable name, the value being the config value you need to use.
    The developers guide has info on refreshing variables.
    You can then change the config in your DB table when you need to.
    Cheers.

  • BI Best Practice for Chemical Industry

    Hello,
    I would like to know if anyone is aware of SAP BI  Best Practice for Chemicals.And if so can anyone please post a link aswell.
    Thanks

    Hi Naser,
    Below information will helps you in detail explanation regarding Chemical industry....
    SAP Best Practices packages support best business practices that quickly turn your SAP ERP application into a valuable tool used by the entire business. You can evaluate and implement specific business processes quickly u2013 without extensive Customization of your SAP software. As a result, you realize the benefits with less Effort and at a lower cost than ever before. This helps you improve operational efficiency while providing the flexibility you need to be successful in highly demanding markets. SAP Best Practices packages can benefit companies of all sizes, including global enterprises creating a corporate template for their subsidiaries.
    Extending beyond the boundaries of conventional corporate divisions and functions, the SAP Best Practices for Chemicals package is based on SAP ERP; the SAP Environment, Health & Safety (SAP EH&S) application; and the SAP Recipe Management application. The business processes supported by SAP Best Practices for Chemicals encompass a wide range of activities typically found in a chemical industry
    Practice:
    u2022 Sales and marketing
    u2013 Sales order processing
    u2013 Presales and contracts
    u2013 Sales and distribution (including returns, returnables, and rebates, with quality management)
    u2013 Inter- and intracompany processes
    u2013 Cross-company sales
    u2013 Third-party processing
    u2013 Samples processing
    u2013 Foreign trade
    u2013 Active-ingredient processing
    u2013 Totes handling
    u2013 Tank-trailer processing
    u2013 Vendor-managed inventory
    u2013 Consignment processing
    u2013 Outbound logistics
    u2022 Supply chain planning and execution Supply and demand planning
    u2022 Manufacturing planning and execution
    u2013 Manufacturing execution (including quality management)
    u2013 Subcontracting
    u2013 Blending
    u2013 Repackaging
    u2013 Relabeling
    u2013 Samples processing
    u2022 Quality management and compliance
    u2013 EH&S dangerous goods management
    u2013 EH&S product safety
    u2013 EH&S business compliance services
    u2013 EH&S industrial hygiene and safety
    u2013 EH&S waste management
    u2022 Research and development Transformation of general recipes
    u2022 Supplier collaboration
    u2013 Procurement of materials and services (Including quality management)
    u2013 Storage tank management
    u2013 E-commerce (Chemical Industry Data Exchange)
    u2022 Enterprise management and support
    u2013 Plant maintenance
    u2013 Investment management
    u2013 Integration of the SAP NetWeaver Portal component
    u2022 Profitability analysis
    More Details
    This section details the most common business scenarios u2013 those that benefit most from the application of best practices.
    Sales and Marketing
    SAP Best Practices for Chemicals supports the following sales and marketingu2013related business processes:
    Sales order processing u2013 In this scenario, SAP Best Practices for Chemicals supports order entry, delivery, and billing. Chemical industry functions include the following:
    u2022 Triggering an available-to-promise (ATP) inventory check on bulk orders after sales order entry and automatically creating a filling order (Note: an ATP check is triggered for packaged material.)
    u2022 Selecting batches according to customer requirements:
    u2022 Processing internal sales activities that involve different organizational units
    Third-party and additional internal processing u2013 In this area, the SAP Best Practices for Chemicals package provides an additional batch production step that can be applied to products previously produced by either continuous or batch processing. The following example is based on further internal processing of plastic granules:
    u2022 Purchase order creation, staging, execution, and completion
    u2022 In-process and post process control
    u2022 Batch assignment from bulk to finished materials
    u2022 Repackaging of bulk material
    SAP Best Practices for Chemicals features several tools that help you take advantage of chemical industry best practices. For example, it provides a fully documented and reusable prototype that you can turn into a productive solution quickly. It also provides a variety of tools, descriptions of business scenarios, and proven configuration of SAP software based on more than 35 years of working with the
    Chemical industry.
    SAP Functions in Detail u2013 SAP Best Practices for Chemicals
    The package can also be used to support external toll processing such as that required for additional treatment or repackaging.
    Tank-trailer processing u2013 In this scenario, SAP Best Practices for Chemicals helps handle the selling of bulk material, liquid or granular. It covers the process that automatically adjusts the differences between the original order quantities and the actual quantities filled in the truck. To determine the quantity actually filled, the tank trailer is weighed before and after loading. The delta weight u2013 or quantity filled u2013 is transmitted to the SAP software via an order confirmation. When the delivery for the sales order is created, the software automatically adjusts the order quantity with the confirmed filling quantity.The customer is invoiced for the precise quantity filled and delivered.
    Supply Chain Planning and Execution
    SAP Best Practices for Chemicals supports supply chain planning as well as supply chain execution processes:
    Supply and demand planning u2013 Via the SAP Best Practices for Chemicals package, SAP enables complete support for commercial and supply-chain processes in the chemical industry, including support for integrated sales and operations planning, planning strategies for bulk material, and a variety of filling processes with corresponding packaging units. The package maps the entire supply chain u2013 from sales planning to material requirements planning to transportation procurement.
    Supplier Collaboration
    In the procurement arena, best practices are most important in the following
    Scenario:
    Procurement of materials and services:
    In this scenario, SAP Best Practices for Chemicals describes a range of purchasing processes, including the following:
    u2022 Selection of delivery schedules by vendor
    u2022 Interplant stock transfer orders
    u2022 Quality inspections for raw materials, including sampling requests triggered
    by goods receipt
    Manufacturing Scenarios
    SAP Best Practices for Chemicals supports the following sales and
    Manufacturingu2013related business processes:
    Continuous production u2013 In a continuous production scenario, SAP Best Practices for Chemicals typifies the practice used by basic or commodity chemical producers. For example, in the continuous production of plastic granules, production order processing is based on run-schedule headers. This best-practice package also describes batch and quality management in continuous production. Other processes it supports include handling of byproducts,co-products, and the blending process.
    Batch production u2013 For batch production,
    SAP Best Practices for Chemicals typifies the best practice used by specialty
    chemical producers. The following example demonstrates batch production
    of paint, which includes the following business processes:
    u2022 Process order creation, execution, and completion
    u2022 In-process and post process control
    u2022 Paperless manufacturing using XMLbased Process integration sheets
    u2022 Alerts and events
    u2022 Batch derivation from bulk to finished materials
    Enterprise Management and Support
    SAP Best Practices for Chemicals also supports a range of scenarios in this
    area:
    Plant maintenance u2013 SAP Best Practices for Chemicals allows for management
    of your technical systems. Once the assets are set up in the system, it focuses on preventive and emergency maintenance. Tools and information support the setup of a production plant with assets and buildings.Revenue and cost controlling u2013 The package supports the functions that help you meet product-costing requirements in the industry. It describes how cost centers can be defined, attached
    to activity types, and then linked to logistics. It also supports costing and settlement of production orders for batch and continuous production. And it includes information and tools that help you analyze sales and actual costs in a margin contribution report.
    The SAP Best Practices for Chemicals package supports numerous integrated
    business processes typical of the chemical industry, including the following:
    u2022 Quality management u2013 Supports integration of quality management concepts across the entire supplychain (procurement, production, and sales), including batch recall and complaint handling
    u2022 Batch management u2013 Helps generate batches based on deliveries from vendors or because of company production or filling, with information and tools for total management of batch production and associated processes including batch  derivation, batch information cockpit, and a batchwhere- used list
    u2022 Warehouse management u2013 Enables you to identify locations where materials
    or batch lots are stored, recording details such as bin location and other storage information on dangerous goods to help capture all information needed to show compliance with legal requirements
    Regards
    Sudheer

  • What is best practices

    hi gurus,
    I would like know what is best practices.  Where we will use this best practices.  What are the benefits we will get through best practices. For whcih industry it is useful.
    If any one help me in this following subject .  I will be value added for me.
    Thanks in advance

    Dear nag
    SAP Best Practices facilitate a speedy and cost-efficient implementation of SAP Software with a minimal need for planning and resources. SAP Best Practices are suited to the enterprise requirements of different industries. They integrate well with varying financial accounting and human resource management systems and can be used by enterprises of any size.
    => SAP Best Practices are a central component of the second phase of ValueSAP (Implementation). The ValueSAP framework guarantees value throughout the entire life cycle of SAP Software.
    => SAP Best Practices are a cornerstone of mySAP.com, since all the key elements of mySAP.com are linked to SAP Best Practices through preconfiguration. Key elements include:
              <> Preconfigured collaborative business scenarios
              <> Preconfigured mySAP.com Workplaces
              <> Preconfigured access to electronic marketplaces
              <> Preconfigured employee self-services
    Features
    SAP Best Practices consist of:
    An industry-specific version of AcceleratedSAP (ASAP) including various tools such as the Implementation Assistant, the Question & Answer database (Q&Adb), detailed documentation of business processes and accelerators:
    The industry-specific version of ASAP provides extensive business knowledge in a clear, structured format, which is geared towards the needs of your enterprise. You can use the reference structures with industry-specific end-to-end business processes, checklists and questions to create a Business Blueprint. This document contains a detailed description of your enterprise requirements and forms the basis for a rapid and efficient implementation of an SAP System.
    Preconfigured systems providing you with the industry-specific and/or country-specific Customizing settings you need to effectively implement business processes relevant to your enterprise
    Key elements include:
    -> Tried and tested configuration settings for the critical processes in your industry including special functions that are standard across all the preconfigured systems
    -> Documentation on configuration, which provides project team members with a comprehensive overview of the system settings
    -> Master data, which you can easily change or extend, for example, organizational structures, job roles, and customer/vendor master records
    -> Test catalogs that can be used to replay test processes in training courses, for example, to help you gain a better understanding of how processes work in the system
    Thanks
    G. Lakshmipathi

  • Information on Best Practice usage of PopulateAttribute

    Using JDeveloper 11.1.1.4.0
    I have a requirement where I use the BC layer as my data service for my UI. But this BC is not connected to the database but rather relying on a WebService.
    Everything is returning well based on NO-DB Transaction and Programmatic Vo's implementation based on SteveMeunch not yet documented, but to further enhance or optimize my implementation, I'm trying to utilize the populateAttribute as in my scenario, I do insert the attribute programmatically thus I also handle the validation before-hand.
    Based on definition populateAttribute allows me to set the value without triggering any validations. So far this is correct as none of my BusinessRules nor any LOVModel accessor validation are getting fired. My question mainly focus on the difference between <b>populateAttribute</b> and <b>populateAttributeAsChanged</b>.
    1. Which of the two methods should be used on certain scenarios (close to best practice :) )?
    2. In the documentation, there is a warning about "Primary key attributes should not be set using populateAttribute apis", in what case will this affect my rows?
    3. In a click-to-edit table, I am able to prepopulate my ViewObject without triggering my accessor (LOVModel) validation, but when I start activating the rows (click), it seems to still be firing the accessor validation. (Which is fairly not expensive calls but uneccessary).
    Thanks.
    -Marvin

    Hi Julian,
    I have struggled with the same questions you are addressing. On a previous project we tried to model based on packages, but during the course of the project we encountered some problems that grew overtime. The main problems were:
    1. It is hard to enforce rules on package assignments
    2. With multiple developers on the project and limited time we didn't have time to review package assignment
    3. Devopelers would click away warnings that an object was already part of another project and just continue
    4. After go-live the maintenance partner didn't care.
    So, my experience is is that it is a nice feature, but only from a high level design point of view. In real life it will get messy and above all, it doesn't add much value to the development. On my neew assignment we are just working with packages based on functional area and that works just fine.
    Roy

  • WCEM Best Practice deployment in a multi CRM Landscape

    Hi SCN
    Im looking for advice in relation to best practice deployment of WCEM. Specifically in a multi CRM landscape scenario.
    Do best practices exist?
    JR

    Look into using NWDI as your source code control (DTR) and transport/migration from dev through to production.  This also will handle the deployment to your dev system (check-in/activate).
    For unit testing and debugging you should be running a local version (NWDW).  This way once the code is ready to be shared with the team, you check it in (makes it visible to other team members) and activate it (deploys it to development server).
    We are currently using a separate server for WD applications rather than running them on the portal server.  However, this does not allow for the WD app to run in the new WD iView.  So it depends on what the WD app needs to do an have access to.  Of course there is always the Federated Portal Network as an option, but that is a whole other topic.
    For JCo connections, WD uses a connection name and this connection can be set up to point to different locations depending on which server it is on.  So on the development server the JCo connection can point to the dev back-end and in prod point to the prod back-end.  The JCo connections are not migrated, but setup in each system.
    I hope this helps.  There is a lot of documentation available for NWDI to get you started.  See:  http://help.sap.com/saphelp_erp2005/helpdata/en/01/9c4940d1ba6913e10000000a1550b0/frameset.htm
    -Cindy

  • Best practices around building reporting relationships in OM

    Hello Experts,
    Would you please let me know the pros and cons of building the following kind of reporting lines in Organizational Management (OM):
    1) Direct line reporting
    2) Travel expense approval manager relationship
    3) Compensation approval reporting lines
    4) Performance and other reporting lines.
    What do you all suggest and what's the best practices in this respect....just build one (the direct reporting) and that's it or you recommend building all kind of reporting relationships. Any thoughts and what you all have done on this!
    Thank you very much.
    saplover

    I learned for Time Management, you need to have Chief not in the same org unit as his employees so he won't have access to approve his own time.  I wondered if same would apply for ESS / MSS?
    Here are two different scenarios of maintaing this.  I learned that Scenario I would not work for Time Management for the reasons I listed above and Scenario II would work.  Can you provide some input?  what's SAP best practices on this? which scenario would be best practice?  Please help!
    Scenario I     
    *HQ Sales (Org Unit 1)     *     
         General Manager (Chief)     
         Sales Rep I     
         Sales Rep II     
         Sales Rep III     
    Scenario II
    *HQ Sales (Org Unit 1)     *     
         General Manager (Chief)     
         *HQ Sales (Org Unit 2)     *     
                    Sales Rep I     
         Sales Rep II     
         Sales Rep III

  • SAP PI conceptual best practice for synchronous scenarios

    Hi,
    <br /><br />Apologies for the length of this post but I'm sure this is an area most of you have thought about in your journey with SAP PI.
    <br /><br />We have recently upgraded our SAP PI system from 7.0 to 7.1 and I'd like to document  best practice guidelines for our internal development team to follow.
    I'd be grateful for any feedback related to my thoughts below which may help to consolidate my knowledge to date.
    <br /><br />Prior to the upgrade we have implemented a number of synchronous and asynchronous scenarios using SAP PI as the hub at runtime using the Integration Directory configuration.
    No interfaces to date are exposes directly from our backend systems using transaction SOAMANAGER.
    <br /><br />Our asynchronous scenarios operate through the SAP PI hub at runtime which builds in resilience and harnesses the benefits of the queue-based approach.
    <br /><br />My queries relate to the implementation of synchronous scenarios where there is no mapping or routing requirement.  Perhaps it's best that I outline my experience/thoughts on the 3 options and summarise my queries/concerns that people may be able to advise upon afterwards.
    <br /><br />1) Use SAP PI Integration Directory.  I appreciate going through SAP PI at runtime is not necessary and adds latency to the process but the monitoring capability in transaction SXMB_MONI provide full access for audit purposes and we have implemented alerting running hourly so all process errors are raised and we handle accordingly.  In our SAP PI Production system we have a full record of sync messages recorded while these don't show in the backend system as we don't have propogation turned on.  When we first looked at this, the reduction in speed seemed to be outweighed by the quality of the monitoring/alerting given none of the processes are particularly intensive and don't require instant responses.  We have some inbound interfaces called by two sender systems so we have the overhead of maintaing the Integration Repository/Directory design/configuration twice for these systems but the nice thing is SXMB_MONI shows which system sent the message.  Extra work but seemingly for improved visibility of the process.  I'm not suggesting this is the correct long term approach but states where we are currently.
    <br /><br />2) Use the Advanced Adapter Engine.  I've heard mixed reviews about this functionaslity, there areh obvious improvements in speed by avoiding the ABAP stack on the SAP PI server at runtime, but some people have complained about the lack of SXMB_MONI support.  I don't know if this is still the case as we're at SAP PI 7.1 EHP1 but I plan to test and evaluate once Basis have set up the pre-requisite RFC etc. 
    <br /><br />3) Use the backend system's SOAP runtime and SOAMANAGER.  Using this option I can still model inbound interfaces in SAP PI but expose these using transaction SOAMANAGER in the backend ABAP system.  [I would have tested out the direct P2P connection option but our backend systems are still at Netweaver 7.0 and this option is not supported until 7.1 so that's out for now.]  The clear benefits of exposing the service directly from the backend system is obviously performance which in some of our planned processes would be desirable.  My understanding is that the logging/tracing options in SOAMANAGER have to be switched on while you investigate so there is no automatic recording of interface detail for retrospective review. 
    <br /><br />Queries:
    <br /><br />I have the feeling that there is no clear cut answer to which of the options you select from above but the decision should be based upon the requirements.
    <br /><br />I'm curious to understand SAPs intention with these options  -
    <br /><br />- For synchronous scenarios is it assumed that the client should always handle errors therefore the lack of monitoring should be less of a concern and option 3 desirable when no mapping/routing is required? 
    <br /><br />- Not only does option 3 offer the best performance, but the generated WSDL is ready once built for any further system to implement thereby offering the maximum benefit of SOA, therefore should we always use option 3 whenever possible?
    <br /><br />- Is it intended that the AAE runtime should be used when available but only for asynchronous scenarios or those requiring SAP PI functionality like mapping/routing otherwise customers should use option 3?  I accept there are some areas of functionality not yet supported with the AAE so that would be another factor.
    <br /><br />Thanks for any advice, it is much appreciated.
    <br /><br />Alan
    Edited by: Alan Cecchini on Aug 19, 2010 11:48 AM
    Edited by: Alan Cecchini on Aug 19, 2010 11:50 AM
    Edited by: Alan Cecchini on Aug 20, 2010 12:11 PM

    Hi Aaron,
    I was hoping for a better more concrete answer to my questions.
    I've had discussion with a number of experienced SAP developers and read many articles.
    There is no definitive paper that sets out the best approach here but I have gleaned the following key points:
    - Make interfaces asynchronous whenever possible to reduce system dependencies and improve the user experience (e.g. by eliminating wait times when they are not essential, such as by sending them an email with confirmation details rather than waiting for the server to respond)
    - It is the responsibility of the client to handle errors in synchronous scenarios hence monitoring lost through P-P services compared to the details information in transaction SXMB_MONI for PI services is not such a big issue.  You can always turn on monitoring in SOAMANAGER to trace errors if need be.
    - Choice of integration technique varies considerably by release level (for PI and Netweaver) so system landscape will be a significant factor.  For example, we have some systems on Netweaver 7.0 and other on 7.1.  As you need 7.1 for direction connection PI services we'd rather wait until all systems are at the higher level than have mixed usage in our landscape - it is already complex enough.
    - We've not tried the AAE option in a Production scenarios yet but this is only really important for high volume interfaces, something that is not a concern at the moment.  Obviously cumulative performance may be an issue in time so we plan to start looking at AAE soon.
    Hope these comments may be useful.
    Alan

  • Best Practice for Plan for Every Part (PFEP) Database/Dashboard?

    Hello All-
    I was wondering if anyone had experience with implementing / developing a Plan for Every Part (PFEP) Database in SAP. My company is looking to migrate its existing PFEP solution (Custom developed Excel/Access system) into SAP. If you are unfamiliar, a PFEP is a dashboard view of a part/material that provides various business groups with dedicated views to data from Material Masters, Info Records, and Vendor Master Records and combines it with historical/forecasting information. The goal is to provide a single source to all the part/material settings for a given part.
    Is there a Best Practice PFEP in SAP? Or if this is something that most companies custom develop in ERP or BI?
    Thanks in advance.
    -Ron

    I think you will likely get a response in SAP ERP - Logistics Materials Management (SAP MM)
    additionally you might want to do some searches based on SAP Lean Inventory, perhaps Kanban. I am assuming you are not using WM or EWM either?
    Where I have seen PFEP incorporated into the supply chain strategy this typically requires not inconsiderable additions to the alternate UoM in MM dropping of automatic replenishment levels (reorder level) and rethinking aspects of the MRP plan so be prepared or significant additional data management work if you haven't already started on that. I believe Ryder logistics uses PFEP and theirSAP infrstructure is managed by IBM; might be an idea to try and find a linkedin  resource from there. You may also find one of the ASUG supply chain,logistics,  MM or WM sigs a good place to also ask questions and look for answers.

  • What is best practice to do APO Demand planning

    Hi,
    My client wants to implement demand planning.
    Client has come up with one scenario like a New Customer is created in ECC, and if I use BI and then APO flow  ( ECC -> BI -> APO-BI) for Demand planning, user will have to wait for another day. (AS BI is always having one day delay).
    For this scenarios user is insisting on ECC and APO-DP interface.
    Will anybody suggest what should be the best practice for Demand planning.
    ECC -> Standalone BI -> Planning area (Planning is done in APO) -> Stand alone BI
    Or ECC -> APO-DP (Planning is done in APO) -> Standalone BI system
    I hope I am able to explain my scenario.
    Regards,
    ST

    Hi Sujoy,
    Thanks for reply.
    (1) I have to get Sales Order data from ECC into BI standalone system Cube.
    (2) Then from this cube same data is sent to SCM APO - BI Cube.
    (3) Planning will be done in SCM APO.
    (4) Planned data is again sent to BI standalone system, Using datamart on Planned area.
    (5) In BI we will have reporting on cube, which has ECC sales order data and APO Planned data.
    But in this case, there is always delay between data loads (firstly ECC -> BI, then BI -> APO, then APO -> BI).
    In this case, if a new customer is created, Client wants to see demand planning in  latest data.
    How do we do APO DP generally?
    Do we follow the route from BI, or directly between ECC and APO..
    Hope I am able to explain the scenario..

  • Best practice for timing of Transfer of forecast to R/3 Demand Management

    Hi All,
    I have APO DP 4.0 with monthly bucket. What is best practice to transfer the planning results to R/3. Meaning how many times we should transfer it?
    And when forecast (PIR) is transfered it replaces the old PIR in demand management for that month. How it will affect the consumption of forecast in R/3? Meaning let us say in same month first time forecast transfered was 100 and by middle of the month 50 has been consumed. Now in same month forecast has been carried out and now 200 has been calculated for the same month and transfered to R/3. Now ideally the remaining quantity to be made should be 150 in R/3. Is it so? Any idea?
    TBR, MM

    Hi Somnath,
    Thanks for the reply. The problem with frequent transfer of forecast to R/3 demand management is that the latest forecast ignores the prior shipments made in that month.
    I will give numeric example:
    Let us say we are in September month and in first week transfered forecast of 100 for one product to demand management. In first two weeks 40 items have been shipped so remaining is 60.
    Now we are in third week and planner realizes that instead of 100 we needed to plan 150 and 150 number is sent to R/3 demand management as a fresh forecast for that month.
    Now for September month we should see net demand as 110 (=150-40). Somehow this is not happening. It shows as a whole 150 net demand. Any idea why it is not happening.
    Thanks and Best Regards, Manoj

  • What is the best practice for APO - Demand planning implementation

    Hi,
    M client wants to implement demand planning.
    Cient has come up with one scenario like a New Customer is created in ECC, and if I use BI and then APO flow for Demand planning, user will have to wait for another day. (AS BI is always having one day delay).
    For this scenarios user is insisting on ECC and APO-DP interface.
    Will anybody suggest what should be the best practice for Demand planning.
    ECC -> Standalone BI -> Planning area (Planning is done in APO) -> Stand alone BI
    Or ECC -> APO-DP (Planning is done in APO) -> Standalone BI system
    I hope I am able to explain my scenario.
    Regards,
    Saurabh

    Any suggestions !!

  • BEST Practice for Balance sheet and Investment Planning

    hi all
       I need the Best Practice guides for Balance sheet and Investment Planning
    where can i get it ?
    if someone has them please could you mail them to [email protected]
       also if someone has documentation regarding these please forward them also
    Points assured
    Thanks in advance
    Nidhi

    Hi Nidhi,
    Refer to the below link for the available scenarios
    http://help.sap.com/bp_biv335/BI_EN/html/Bw.htm

  • Best practices for loading apo planning book data to cube for reporting

    Hi,
    I would like to know whether there are any Best practices for loading apo planning book data to cube for reporting.
    I have seen 2 types of Design:
    1) The Planning Book Extractor data is Loaded first to the APO BW system within a Cube, and then get transferred to the Actual BW system. Reports are run from the Actual BW system cube.
    2) The Planning Book Extractor data is loaded directly to a cube within the Actual BW system.
    We do these data loads during evening hours once in a day.
    Rgds
    Gk

    Hi GK,
    What I have normally seen is:
    1) Data would be extracted from APO Planning Area to APO Cube (FOR BACKUP purpose). Weekly or monthly, depending on how much data change you expect, or how critical it is for business. Backups are mostly monthly for DP.
    2) Data extracted from APO planning area directly to DSO of staging layer in BW, and then to BW cubes, for reporting.
    For DP monthly, SNP daily
    You can also use the option 1 that you mentioned below. In this case, the APO cube is the backup cube, while the BW cube is the one that you could use for reporting, and this BW cube gets data from APO cube.
    Benefit in this case is that we have to extract data from Planning Area only once. So, planning area is available for jobs/users for more time. However, backup and reporting extraction are getting mixed in this case, so issues in the flow could impact both the backup and the reporting. We have used this scenario recently, and yet to see the full impact.
    Thanks - Pawan

Maybe you are looking for