Ansicht
Dokumentation
Reorganization of Product Cost Collectors ( RELN46A_COPC_REORGPKOSA )
BAL Application Log Documentation Addresses (Business Address Services)This documentation is copyright by SAP AG.
Short text
Reorganization of Product Cost Collectors
Description
If the customer is using product cost collectors, then logistical orders (such as production orders) are linked to the product cost collectors. This link means that processing differs somewhat when the logistical orders and product cost collectors are archived.
For example, before the logistical orders linked to a product cost collector can be reorganized, you must make sure that all steps in the period-end closing process in the Product Cost by Period component that reference quantity information of that order are:
- Completed
- Cannot be repeated
This is important because the information on the operation quantities and scrap quantities confirmed in the period are stored in files that belong to the logistical orders. If the logistical orders were to be deleted, this information would be lost. This information is needed, however, in the period-end closing process of the Product Cost by Period component to calculate figures such as the work in process (WIP) or the scrap variances. If the quantity information were to be lost, data inconsistencies would result.
The system therefore performs the following checks:
- A manufacturing order can only be flagged for deletion (status DLFL) if archiving it cannot influence the period-end closing data of the product cost collector to which it is linked. The system therefore checks the following:
- Whether the last period in which a confirmation or goods movement took place on the manufacturing order, as well as all periods preceding that period, are locked for WIP calculation and variance calculation. This means that the cutoff period must be set for the relevant periods for WIP calculation and for variance calculation.
- Whether the work in process has been canceled
- Whether the balance of the manufacturing order is zero
- A run schedule header or a production version (in Release 4.6A, products are manufactured with direct reference to the production version; no run schedule header is needed) can only be deleted if:
- The cutoff period for WIP calculation and for variance calculation is set for the period in which the last reporting point backflush took place, as well as for all periods preceding it in which the run schedule header or the production version is valid
- Reporting points are being used and the production line is empty; that is, the work in process has been canceled
- A product cost collector may only be flagged for deletion if the deletion indicator (status DLT) has been set for all logistical orders that are linked to it.
- In addition, before the deletion flag is set, the criteria that are known must be met. This means that:
- The work in process must be canceled
- The balance of the product cost collector must be zero (that is, the product cost collector must be completely settled)
Damage caused to data by errors
Software/hardware requirements
Installation information
Effects on System Administration
Effects on Customizing
Effect on batch input
Changes to the Interface
Changes in procedure
Procedure for removing dataset errors
Dependent functions
Planning
Further notes
For detailed information on reorganizing product cost collectors, and on the requirements for and the results of reorganization, refer to the documentation in the R/3 Library under Controlling -> Product Cost Controlling -> Cost Object Controlling -> Product Cost by Period.
RFUMSV00 - Advance Return for Tax on Sales/Purchases General Material Data
This documentation is copyright by SAP AG.
Length: 5524 Date: 20240427 Time: 000121 sap01-206 ( 150 ms )
