Ansicht
Dokumentation

CK_SDI_COSTRUN - Manage Order BOM Cost Estimates in Parallel Valuation

CK_SDI_COSTRUN - Manage Order BOM Cost Estimates in Parallel Valuation

rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

Using the mass costing function in parallel valuation, order BOM cost estimates can be created in parallel view in collective processing.

Integration

If parallel valuation approaches are used in the controlling area, sales order stocks can also be valuated differently in parallel views. Using the requirements class, only one cost estimate can be automatically created and marked for the valuation in the leading view (usually the legal valuation). Costing in parallel view can be performed using an order BOM cost estimate. To do this, at least one costing variant must be created for sales order costing per view.

If you want to ensure that goods movements cannot be posted with reference to the valuated sales order stock as long as there is no marked costing in parallel view, you can change message CKBK 048 (No marked sales order costing in valuation view &1) to an error message by means of user-defined error management. To do this, in the Implementation Guide (IMG), choose 'Controlling -> Product Cost Controlling -> Cost Object Controlling -> Product Cost by Sales Order -> Preliminary Costing and Order BOM Costing -> User-Defined Error Management -> Specify User-Defined Message Types for Sales Order Costing and Order BOM Costing'.

Prerequisites

Separate valuation with reference to the sales document/project must be configured for the sales order item using the requirements class ('M' valuation).

At least one costing variant to which a costing type for a parallel valuation view is assigned must be defined for the sales order costing.

Features

The costing cockpit supports the creation and management of order BOM cost estimates using costing runs. The following functions are supported.

·,,Execute: With each execution, the system automatically creates a costing run and the sales documents processed with the execution are saved with reference to the run. The name of the run is assigned automatically by the system. However, the user can assign a descriptive text for each run.

·,,Display: It is possible to navigate to an individual run from the list of costing runs executed. The list of sales order items processed in this run is displayed.

·,,Delete: You can delete one or more costing runs. Only the administration data for the runs and their logs is deleted. Costings are not deleted.

·,,Log display: You can navigate to the detailed view of an individual costing run from the list of all run logs. Besides general messages, only error messages are collected from the costings.

·,,Search: Using the sales order, costing run, material, or plant characteristics, you can search for and display costings from the costing runs executed.

·,,Worklist: Worklists can be created and changed. A worklist can be used as a selection list for future costing runs.

·,,Set controlling area: To execute a costing run, it is compulsory to set a controlling area. This is used to determine which is the leading valuation view and which parallel views are used.

Selection

The sales order items to be processed can be selected using characteristics or a worklist. The selection type is determined using a radio button. Depending on the selection type, the user can either specify a worklist or maintain the selection options available.

The following options are available for execution:

·,,Save selection in worklist: The selected sales order items to be processed can be saved as a worklist for a future costing run.

·,,Test run: Costings are performed based on the selection, but not saved. Therefore, it is not possible to navigate to the costing subsequently. The costing result and the error status are saved with reference to the run.

·,,Recost a marked cost estimate: By selecting this indicator, you can overwrite cost estimates that have already been marked. Note that goods movements that were valuated with the marked cost estimate may have been posted already.

·,,Marking: By activating this indicator, you can mark executed costings for valuation.

·,,Parallel processing: By specifying a number of parallel processes and a suitable server group (maintained in transaction RZ12), you can also execute processing using parallel dialog processes.

Standard Variants

Output

The result of processing is displayed in a list. The information is also saved and can be managed using the functions described above. The costing result is shown in object currency for the most suitable view possible. In the standard system, this would be cost view 02 (cost of goods sold).

Activities

Example






BAL Application Log Documentation   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 5076 Date: 20240520 Time: 065629     sap01-206 ( 103 ms )