Revenue Planning in APO

What are the possibilities of doing financial revenue forecast in APO along with demand planning?

P134329
We need lot of integration to do this any way financial revenues could easily done in FI Module so why unnecessary complication. I am not sure your requirement I am talking in general.
Thnaks
Sat

Similar Messages

  • Unable to update revenue plan values in Easy Cost Planning

    Hi,
    Business maintains planned costs and revenues on WBS element using Easy Cost Planning tool. But for one of the WBS element system is not allowing to update/add planned revenue line items.User is able to update the planned costs for this WBS element.
    The Legend in Easy Cost Planning screen is Non-Changeable Cost Estimate.
    The status of WBS is REL,ACPT(Order Accepted),NSCH(Not Scheduled - Forecast Dates),RESA(Result Analysis Carried out).
    We have checked all the business process and all the revenue planning is allowed.
    Please guide us on how to resolve this issue.

    This is resolved...Select the WBS and click on CLOSE icon to reset the cost estimate. This allows to plan revenues again.

  • Scheduling agreement planning in APO

    Hi,
      Currently I am planning in APO (SCM 5.1) and have scheduling agreement (type - APO Sch. Agree.)
    Planning run created - Schedule lines and using transaction - /SAPAPO/PWBSCH1, create release.
    Then I went to external procurement master data and clicked on SA release and executed Schedule line.
    I could see it green.
    But if I check ECC, I don't see Schedules lines in agreement.
    Do let me know if I am missing any steps or any configuration which I might have missed.
    In the "Partner" tab within external procurement master data, I changed medium to "XML" and can see one failed IDOC.
    How scheduling lines are released from APO to ECC? is it not standard "pulbication of planning result"
    Thanks
    Sharad

    Hi,
    Thanks for all your replies, mentioned settings are already maintained and I did check all the queques for any error.
    OLTP transfer setting is also maintained as immediate..so I don't need to transfer change pointers through report, as it should immediately be transferred to ECC.
    My question is: We have report - create release (transaction - /SAPAPO/PWBSCH1) to release scheduling agreement, so I believe for scheduling agreement we need to use above transaction.
    It seems to work, as I can see IDOC but its in failed status.
    I have following question:
    - Does scheduling line release work in a different way than purchase req, in APO. I did test with purchase req and it was immediately transferred to ECC.
    Has somebody worked for schedule agreement scenario in APO?
    Any insights would be appreciated.
    Thanks
    Sharad

  • Profit center planning - Revenue planning

    Hi,
    Out client is service provider and all the scale of rates are mapped to pricing proceedure in SD. Now the requirement is for revenue planning. Revenue planning can be done through profit center accounting. But he do not want to enter the values i.e. revenues directly using the planning layouts. Expectation is that he will enter the quantities that he is expected to sale/provide in the next year and the system should generate the revenues based on the SOR (scale of rates )mapped  in Pricing proceedure of SD. How can we achieve this?
    Your immediate help is highly appreciated.
    Regards
    Koteswara Rao

    Valuating planned quantities can be done in CO-PA and than transferd to PCA
    I think in PCA this is not possible
    In PCA you only plan on the account and ProfitCenter (and statistical key figure) and the system doesn't know where to get the prices
    In CO-PA you plan on different characteristics (material, service, customer...) and this can be customized in order to derive prices for planned quantites
    cheers
    matej

  • Revenue Planning to cost elements

    Hi,
    I am Working on Project system object.
    When i am trying  planned revenue is added on the project, I need to find if there is a way to assign the revenue amount on the lowest WBS to a cost element. This is required for revenue amounts to appear in costing reports. CJ42 is used to add planned revenue manually.

    hi anuradha,
    Revenue Planning
    Use
    Revenue planning can be necessary when you perform results analysis on a sales order item and use a results analysis method that uses the planned revenues to calculate the results analysis data.
    Features
    The net value (revenue) for sales-order-related production is determined in pricing in Sales and Distribution (SD). Pricing depends on specific conditions which you maintain in Sales and Distribution.
    A particular customer orders a particular quantity of a product on a particular day. The variable factors – customer, product, quantity ordered, date – determine the final price for the customer.
    The system uses the conditions you specified to calculate the gross price at which the customer is invoiced; any discounts applying to the customer, for example; and other values such as freight charges and tax.
    Pricing is controlled by a pricing procedure which is selected through the sales document type. Price elements such as prices, surcharges and discounts, freight costs and taxes are saved in Sales and Distribution as condition types. The pricing procedure determines which condition types are used and the sequence in which they are calculated in the sales order.
    Condition Types
    The standard system contains the following condition types that can be used in connection with unit costing, product costing, and preliminary order costing in assembly processing:
    Condition Types for Pricing
    Condition Type
    Meaning
    EK01
    Cost of goods manufactured (CGM)
    EK02
    CGM (statistical)
    EK03
    Fixed CGM (statistical)
    Condition type EK01 is mainly used for cost-plus contracts in which the sales price depends on the expected costs.
    Condition type EK02 is mainly used when the sales price is a market price and the expected costs are only used for informational purposes.
    Condition type EK03 offers the capability of transferring the fixed costs of a cost estimate into the conditions.
    The costs are transferred from the cost component view Cost of goods sold into the condition type.
    The above-mentioned condition types must be of category Q. Whether a condition type of category Q is only used in pricing as a statistical value or for price calculation is controlled in the pricing procedure.
    The condition type is created in Customizing for Sales.
    The condition type can be selected as follows:
    Through the sales document type
    Condition types EK01 and EK02 are specified in the CndTypLineItems field in the sales document type.
    Through the requirements class
    This enables you to define different condition types for different sales document items of a sales document.
    Condition types EK01 or EK02 are specified in the CndTypLineItems field in the requirements class.
    Condition type EK03 is specified in the CondTypLinItFix field. You can only use condition type EK03 in conjunction with the requirements class.
    Planned Revenues
    Revenue elements from the SD pricing procedure that are not statistical are updated as planned revenue on the sales order item that carries costs and revenues, and can be viewed in the Product Cost Controlling Information System. Sales deductions can also be assigned to revenue elements through account determination, and updated on the CO object for the sales order item.
    The condition type is selected through the sales document type.
    Condition type EK01 is selected for sales document type TA (standard order). This means that the value from the cost estimate goes directly into pricing. A surcharge is calculated from this value and the net value for the sales order item is calculated.
    Condition type EK02 is selected for sales document type TA (standard order). Pricing is carried out on the basis of condition type PR00. To maintain this price, choose Logistics ® Sales/distribution ® Sales ® Master data ® Prices ® Material prices and enter a material price. The material price is updated under condition type PR00, while the values from the cost estimate are updated under condition type EK02 and can be used for informational purposes.
    Actual Revenue in Product Cost by Sales Order
    Use
    In Product Cost by Sales Order, actual revenues are updated to the sales order item that carries costs and revenues at the time of invoicing.
    Integration
    You can view the actual revenues in comparison with the planned revenues and costs in the Product Cost Controlling Information System at any time.
    You can settle the costs and revenues that are updated to the sales order item to a profitability segment in Profitability Analysis (CO-PA) during period-end closing for Product Cost by Sales Order. When you perform results analysis, the results analysis data are settled to CO-PA.
    The processing in Product Cost by Sales Order therefore differs from the processing in Product Cost by Order or Product Cost by Period (make-to-stock production and with a valuated sales order stock without a sales order item that carries costs and revenues).
    If you perform this type of product cost controlling (such as in addition to Product Cost by Sales Order), then in Product Cost by Order or Product Cost by Period the revenues from invoicing are transferred to CO-PA.
    If you are using the cost-of-sales accounting in Financial Accounting (FI) and are using a valuated sales order stock, you do not need to perform results analysis in order to transfer the cost of sales to FI. The cost of sales is transferred to Financial Accounting at the point of the goods issue posting.
    Prerequisites
    To ensure that the revenues are displayed on the sales order item, you must create revenue accounts and possibly sales deduction accounts as primary cost elements of cost element type 11 (revenues) or 12 (sales deductions). Make the necessary settings in Customizing under Controlling ® Overhead Cost Controlling ® Cost and Revenue Element Accounting ® Master data ® Cost Elements.
    To be able to settle the costs to Profitability Analysis, you must make the necessary settings in Customizing for Profitability Analysis. Make the necessary settings in Customizing under Controlling ® Profitability Analysis.
    Features
    Billing
    Billing invoices the customer for the goods and services delivered for a sales order.
    In Sales and Distribution, you create an invoice (billing document) on the basis of a reference document. In order-related billing, the reference document is the standard order or the delivery document with delivery-related billing.
    The data such as prices and quantities are transferred from the previous documents into the billing documents. The price can be calculated in the following ways:
    Using pricing on the basis of conditions (such as material or customer)
    On the basis of the incurred costs if you want to use resource-related billing
    When you enter a billing document, the system proposes a billing type depending on the reference document.
    The billing type determines the following:
    Which pricing procedure is used for account determination for Financial Accounting
    Whether the invoices are passed immediately to Financial Accounting
    Account assignment is controlled by the following parameters:
    The chart of accounts
    The sales organization
    The account assignment group of the customer (in the Account group field in the Invoicing screen of the customer master record)
    The account assignment group of the material (in the Account assignment group field in the Sales 2 view of the material master record)
    The account key in the pricing procedure
    thanks
    karthik
    <REMOVED BY MODERATOR>
    Edited by: Alvaro Tejada Galindo on Apr 15, 2008 3:10 PM

  • Project Revenue Plan Not Update from Sales Order Item

    I am generating a network and project from the sales order item using Assembly processing. I am using milestone billing on the sales order item and the milestones attached to the project network activities are appearing as billing blocks on the sales order item billing plan. However, the project revenue is not getting updated from the sales order billing plan. Can someone please help?
    I have deleted the billing plan on the billing WBS element and activated revenue planning update from sales order in cusomization for PS. I am looking at CNS41 under the project revenue sched in version 0. Is there a different report I should be looking at?
    Regards,
    Venkat.

    HI Venkat,
    You are looking at the correct report & I believe you have also done the necessary customization. If you create a sales order and reference it to a quotation, the related plan values in the WBS element are refreshed automatically.
    When the payment data is recorded, the terms of payment and the customer payment history are taken into consideration. One of the probable causes could be the credit limit of the customer might have been exceeded. Take help of your SD consultant & increase the credit limit for that customer (from the sales document), t-code FD32 if it is permitted in the business.
    After the new credit limit is set execute the following steps:
    u2022     Go to the t-code Change billing request (VA02)
    u2022     Open the required billing request
    u2022     Remove the account assignment of WBS element from each line item
    u2022     Save the billing request
    u2022     Reopen the billing request in change mode
    u2022     Reassign the WBS elements to all line items
    u2022     Now the changed credit limit will take affect
    u2022     Check the Planned Revenue for the said project in CNS41, it should get updated.
    Rgds
    Deepak

  • BOM explosion for component in ECC which are relevant for planning in APO

    Hi ,
    as we assign materials the MRP type X0 with the MRP procedure X (without MRP, with BOM explosion) which are relevant to APO, so if i have BOM under this item then how this below level Items will be plan in ECC....?
    as we are excluding the component from planning so how the below level will be plan .....?
    Regards

    Dear SCM APO 22 ,
    Answer lies in your question only.
    as the assembly is relevant to be planned in APO but it will be exploded in MRP and the lower level component will be planned in R/3 only if required.
    Only teh assembly which have MRP type X0 will be planned in APO.
    Revert back if you need further clarification.
    Hope it helps you.
    Regards
    Ritesh

  • Diff between Planning in BPS and Planning in APO

    Hello..
    Can any one give me some good insight in to the difference between planning in APO and plannning BW BPS.. In what way is it diff?
    thankyou..
    kishore karnati

    Hi Kishore,
    Not sure about APO but some of the distinct features of BPS planning are:
    Loose integration with the transactional data flow
    Fast and simple adaptation to current and future organizational changes
    Free and unrestricted definition of integrated planning scenarios
    One homogeneous planning environment for the flexible design of various planning steps
    One central data warehouse as basis for all information needed in the decision process
    More simulative planning processes
    Maybe an APO expert could comment on the other side
    Hope it helps...

  • Make to order planning in APO

    Hi guys,
    Can we do the make to order planning in APO ?
    Thanks in advance
    S.Murali

    Hello,
    You can carry out MTO planning in APO.
    But normally we do not recommend since you may not be able to utilize advantages offered by APO.
    With Regards
    Mangesh A. Kulkarni

  • KEPM-   in  revenue planning , quantity  not planned

    Hi 
    In  revenue planning ,  we   plan  for  the  amount and  quantity  of  sales.   Then   we  valuate  the  quantity to get the cost of goods  based on standard cost.     Now   if   only  revenue amount is planned  and   no  quantity is  planned,  then   i  cannot  do  valuation.
    My  question is  where   can  I   manually    enter  the  cost   in  KEPM  and  see the same in report in KE30   . Also  let me know  how  to do  the same.
    Thanks  
    kamala

    Hi Kamala,
    Activating valuation with product cost is an optional step. If you don't want to valuate sales quantity (or you are not planning quantity) with product cost, then you can manually enter the cost in planning. Include the relevant cost value field in the plan layout (using t.code KE15) and then the cost value field will be available in KEPM for you to input the data.
    Hope this helps.

  • Advantages of Implementing Demand Planning in APO

    Hi All:
    One of our company's business units is exploring the possibility of implementing their Demand Planning in APO. Since their business closely resembles retail, they do not run MRP in ECC to replenish.  Instead they do Kanban for replenishment.  Hence they do not need Independent requirement in ECC. 
    The as-is forecast model is a simple spreadsheet that they use that is used for financial forecasting.  They have a lots of SKUs and with spreadsheet aggregation and disaggregation is a night mare.  Hence they have products sitting in their inventory, worth millions of dollars that has not been sold yet for a year.  In essense the top-level forecast data has too many errors.  They also use this to forecast how much of components they have to procure.  Again, they have millions of dollars work of components sitting in our inventory.
    So, they are looking to implement their DP in some other software.  Since we have APO, APO could be a choice.  But we have to justify the cost involved.
    They will not need APO to send back IR back to ECC.
    Followiing are the benefits we see:
    1.  Highly integrated with ECC and hence forecasting will be based on their Sales and invoice history.
    2.  Since their products are seasonal, APO can offer advanced forecast methods to forecast SKUs as accurately as possible.
    3.  Ease of use.
    4.  Right now, the spreadsheet is accessible to one user at a time and been shared thru emails.  This will change with APO
    5.  They could use DP-BOM to forecast component and help reduce components inventory
    6.  An integrated system that will sent forecast to CO-PA on a monthly basis.
    Can you guys help me with anything else that will benefit the business?  Any input will be of great benefit.

    Hi,
    before to begin: I don't really understand what you are saying: you say the forecast is not use for planning, however your think it is the cause of overstock... how can that be?
    I understand the logic for componenents, but not for finish good here
    Anyway, regarding your questions:
    Of course DP will help you too, and the benefits you emntioned are good.
    However I suggest you to do a bigger analysis of your business needs... it looks ot me that you will need more than DP.
    You could use SNP to plan your finish good and components (or use a strategy such as planning at assembly level).
    If your biggest challenges in inventory level then SNP is the tool that will give you a better visibility here.
    I personnally think that DP BOM should be use only is specific cases. You better have to plan your component in SNP, which will be far more flexible.
    In one sentence, I think that if you do decide for a DP implementation now, you biggest benefit should be: later on you will be able to use SNP for planning.
    Well that is what I think....
    Good luck for your challenges!
    Julien

  • Use of ECC planningtime fence when planning with APO SNP

    I am using SAP ECC for execution, and SAP APO SNP heuristics for planning.
    So, for a product planned in APO, the MRP type in ECC is X0.
    So, as there is no MRP planning in ECC for such a product, what is the use of the ECC planning time fence? I think it becomes redundant in ECC - yes? In fact, I do not see it in the stock reqs list (MD04).
    So, in ECC, all that 'planners' can do is to manually reschedule planned/production orders - yes?
    Any shortage alerts will only be visible in APO - yes?
    Thanks for any advice on this...

    Hi
    Please find below the answers from my side.
    Two questions in my mind...
    So, if MRP type = X0 in ECC, the planning time fence is not seen in MD04.
    First of all, we should not have any planning time fence in ECC, as it is not adding any value for products with MRP type X0. Yes in MD04  we can not see it.
    2. How can ECC users easily distinguish between planned orders which are in the 'short term' from those which are beyond the SNP production horizon?
    I think they have to use APO alerts. I think that should be right approach as APO is leading planning tool.
    Thanks
    Amol

  • Change a Material A from Planning at APO( XO ) to MRP (PD)

    Hi,
    if i change a material from planning at APO to R3, what is the impact that i need to prepare ?
    do i need to delete the planned order at APO for the material and set the deletion flag for the material at APO or delete the material.
    Do i need to set a C5 to delete the APO planned order at R/3?
    Regards

    Hi,
           When you change the material MRP type from X0 to PD, the integration model stops integrating the material between R/3 and APO meaning any changes done to the material or the BOM or routing or orders or any where the material is referenced is not integrated any more.
    So, just to be safe, before changing the MRP type, go to transaction WUF ( where used Function) in APO and search for all orders.
    Depending on your configuration, usually PPDS orders are set to immediate transfer to R/3 but SNP orders are set to periodic. So in both the cases, you have to delete the material using program /sapapo/rlcdelete with selection deletion in R/3 and APO or send deletion. If it is SNP order, you need to run the transaction /sapapo/C5 to push the changes/deletion.
    Then you can change the MRP type to PD from X0.
    So after you change the MRP type, create and activate your integration model again. Check in CFM2 to make sure the material is not being picked up any more by the relevant integration models.
    Then it's up to you to keep or delete the APO product master.
    The orders generated for this material are also no longer integrated.

  • PS Revenue Planning ( Tracking History )

    Hi All,
    Kindly advice how can we track the history changes in revenue planning, whether it comes from SD Doc, WBS billing plan or CJ43.
    I tried couple things but it seems that there is no tcode to track the history changes.
    I can track the changes in Planning cost through CJI4.
    Appreciate for the advice.
    Thank you.

    Hi Varun,
    We already activated ' Write plan line items ' in our user status. I think the Business transaction only can capture for Planning cost not for Planning revenue.
    Appreciate for your response.
    Thank you.
    Nies

  • Copying annual revenue planning into a CO version

    Dear All,
    I have condtion where we do planning of revenue on annual basis with GL. And we have overall cost planning. Tcode used was CJ42 and CJ40 respectively. We do not want to plan cost on annual basis.
    Because of above condtion when we copy planning into other co versions revenue planning was not got copied. Tcode used was CJ9FS.
    We have lock year up dation in CO versions because we got wrong values of cost planning into versions. So that yearwise revenue values not got copied into versions.
    Is there any standard way to copy annual revenue plan into co versions with maintaining above conditions or any work arround?
    We are using RA, because of that we have to use annual revenue planning to use GL.
    Regards,
    Nilesh Bagav.

    Dear Hemant,
    Thanks for your reply. IN CJ9BS/selection option/Primary Revenue option works for copying revenue in to initial year of CO version.
    Thanks,
    Nilesh Bagav.

Maybe you are looking for