Run Price Revaluation - Orders
Application component: Overhead Cost Controlling
App type: SAP GUI
Description: Revaluation at actual prices supplements revaluation of activity allocations between cost centers and business processes. It is used to correct activity allocations that occurred previously from cost centers or business processes to other cost accounting objects. You can use revaluation at actual prices for the following objects:Internal orders In Cost Object Controlling: Production ordersProcess ordersProduct cost collectorsSales document item (for example, sales orders) In the Project System: ProjectsWBS elementsNetworksNetwork activities Note Revaluation on cost centers and business process levels takes place within actual price calculation in Cost Center Accounting.For more information, see the SAP Library under Financials  Controlling  Cost Center Accounting  Period-End Closing  Actual Price Calculation If a cost accounting object uses an activity from a cost center or business process, you usually start with a plan price to allocate the activity. This is because the actual price is calculated during period-end closing. In the actual price calculation, the SAP system performs an iterative calculation of the prices for the activity types. To do this, it uses the actual costs that were debited to the cost center or business process, and the activities actually incurred. During this process, the system accounts for all activity relationships between cost centers and business processes. After actual price calculation, you can revaluate the objects at actual prices if they have used the activities from cost centers or business processes. You do this using Revaluation at actual prices (revaluation). The system always determines the variances between the costs posted up to this point and the costs that occur under the new prices. The corresponding sender cost center is credited by the actual price revaluation and the receiver is debited accordingly. 
Key features: Revaluation occurs periodically for individual cost accounting objects or in collective processing for more than one cost accounting object. You start revaluation with your own user-defined transactions after the actual price calculation. Revaluation occurs for all the secondary cost elements affected. Caution After revaluation, it is important that you execute settlement for all of the receivers again. This is an important requirement, as it is the only way that you can pass on revaluation data from a revaluated CO object to further CO objects. See also: Example: Revaluation at Actual Prices With Repeated Settlement You can also start revaluation for test and forecast purposes. In this case, you do not update the revaluations that you calculated. You can run both test and update runs either online or in the background. You can repeat revaluation as often as required. The system only updates the differences that occurred due to price changes. You can create a worklist for objects that could not be revaluated during collective processing. The system uses this worklist to provide you with information about the cause of any incorrect processing. Once you have corrected these error sources, you can restart revaluation for the objects in the worklist. You can find further information on worklist processing in Worklist for Revaluation at Actual Prices. You can completely reverse the revaluations made in the update runs, so long as the status of the relevant CO objects allows this. The original activity allocations remain the same. If you have reversed any activity allocations, you should also reverse the revaluation for the period affected. Note For cumulative prices, you should reverse the revaluations for the higher periods first. Caution After reversing the revaluations, ensure that you perform the settlement again, This is required because such revaluation data, that was transferred from one cost accounting object to other cost accounting objects, is not reversed. See also: Internal Order Settlement