Run Actual Indirect Activity Allocation - Profitability Analysis
Application component: Profitability Analysis
App type: SAP GUI
Description:  To transfer cost center costs or process costs to Profitability Analysis at the end of the period, execute assessment, indirect activity allocation or template allocation. 
Key features: Performing Assessment and Indirect Activity Allocation Given that cycles are allocated in assessment and in indirect activity allocation, the same procedure is executed for both. You can allocate cycles online or in the background. Recommendation Assessment cycles that process large amounts of data should always be executed in the background in order to avoid bottlenecks. It is recommended that you do not execute more than one large cycle in the same job step. You can perform cycles sequentially or in parallel. If you want to prevent specific cycles from being performed in parallel (such as ones that are dependent on other ones), you must assign these particular cycles to the same cycle run group (see also Processing Cycle Run Groups). If your controlling area and your operating concern use different currencies, the system translates the values during the transfer. For actual costs, the system uses the mean exchange rate (exchange rate type M). The default setting translates the values using the rate valid on the last day of the period. By choosing Extras  Value Date in assessment, you can also enter a date on which the currency translation should take place.In planning, the exchange rate type is taken from the definition of the plan version. The system always uses the rate valid for the first day of the period. Line items are written, being credited to the cost centers/processes and debited from the profitability segments. To display these line items, use the information system or choose Assessment  Overview or Indirect Activity Allocation  Overview. In costing-based CO-PA, the receiver data is transferred to value fields in CO-PA. Records are also are created in CO-PA with record type D. For the allocation of actual data, the posting date is the last day of the period. For the allocation of planning data, the posting date is the first day of the period. If you repeat a cycle during a period, data already posted is canceled automatically before the cycle is run a second time. Note Along with the cycle name and the initial data, the sender version is also part of the unique key of a plan cycle. This means that you can carry out the same cycle repeatedly with different sender versions. Hence nothing is canceled if you change the sender version in the cycle definition. If you want to manually cancel a cycle, choose Indirect Activity Allocation  Cancel or Assessment  Cancel. Note Cancellation is always carried out at the line item level. Once you have archived your data or have deleted the line items in either Profitability Analysis or Cost Center Accounting, you can no longer reverse the cycles. You can check the allocation results (such as the sender and receiver information) by creating detailed lists (sender and receiver lists as well as journal lists) in which to record the results. To specify which detail lists should be created, select the detail lists indicator and choose List selection. If you perform allocation in the background, the system generates the following spool files:A spool file is generated for the basic list, the segment list, and for the receiver and sender lists if appropriate.If applicable, a separate spool file is generated for the journal list.If applicable, a separate spool file is generated for the expert trace. Moreover, you can display a runtime analysis (expert trace) or any messages while allocation is being executed. See also Results of Periodic Repostings or Periodic Allocations. The message section of the lists also contains information about which summarization levels were read (see also Defining Summarization Levels). You can improve performance significantly by defining suitable summarization levels. You can find more detailed explanations by double-clicking the individual messages. You can make the following settings by choosing Edit  Settings:Enter the display variant for detail listsSpecify the strategy for database selectionEnter the name under which the detail lists are to be stored with the allocation resultsRecord the run log and the runtime analysisDetermine system behavior when an error has occurred during the collective execution of cycles. One main difference with allocating planned overhead is that a cycle cannot be defined by the name and initial date alone. Instead, the sender version is also an essential part of the key for the cycle to run. This allows you to reuse the same cycle for different planned versions. All you need to do is change the sender version, without having to define a completely new cycle for each version.  Performing Template Allocation For information on performing template allocation, see the section on Executing Template Allocations in the online documentation for Activity-Based Costing (CO-OM-ABC).