結果分析碼( results analysis key )
Use
How the results analysis key is used depends on the nature of the order.
For orders with revenue ( internal orders, sales orders, and projects), the results analysis key determines how results analysis is carried out.
Results analysis is recommended in the following situations:
When you are using a nonvaluated sales order stock or nonvaluated project stock and you want to valuate the inventories at the end of the period
When you are using a valuated sales order stock or valuated project stock and want to valuate goods that have been delivered but not yet invoiced, or when you want to create reserves automatically
For orders without reference to a sales order item or WBS element, the results analysis key determines how the work in process is calculated.
The production type can be make-to-stock or mass production on the basis of sales orders. The work in process is calculated at the level of the production order, process order, or product cost collector.
For capital investment measures, the results analysis key determines how the system calculates the values to be capitalized.
Examples
For orders with revenue, costs may be incurred before any revenue is received. If you are using a nonvaluated sales order stock, results analysis enables you to report the costs as work in process. After the first revenue has been posted, you can calculate the cost of sales. If the calculated cost of sales is greater than the actual costs incurred to date, the system creates reserves for unrealized costs in the amount of the difference.
No revenue is posted in CO for orders without reference to a sales order item. Each goods receipt for these orders is valuated. The work in process for these orders can be calculated with two different methods:
Work in process at actual costs
The actual costs for production orders and process orders for which no delivery has taken place are reported as work in process. After a partial delivery, the difference between the debit of the order with actual costs and the credit of the order from goods receipts is reported as work in process. When the order is complete, this work in process is canceled. The difference between the debit and credit of the order is then interpreted by the system as a variance.
In Product Cost by Order, the work in process is usually valuated at actual costs.
A requirement for the valuation of work in process at actual costs is that the default rule PP1 (full settlement) must be specified in the order.
Work in process at target costs
A confirmation is made for each operation or at certain reporting points. The system uses the confirmations to determine the quantity of work in process. This quantity is valuated using the strategy sequence specified in the valuation variant for work in process and scrap.
In Product Cost by Period, the work in process is always valuated at target costs.
A requirement for the valuation of work in process at target costs is that the default rule PP2 (periodic settlement) must be specified in the order.
See also: Check default values for order types
Dependencies
The control parameters for results analysis, for the calculation of work in process, and for the calculation of the values to be capitalized are selected through the results analysis key in the order and a results analysis version. If you have not specified a results analysis key in the order, the order will not be included in the calculation of work in process during period-end closing.
The control parameters for the valuation of work in process in Product Cost by Period are defined in Customizing for Product Cost by Period.
See also: Define valuation variant for WIP and scrap (target costs)
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/46681/viewspace-791912/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 揭開OKR (Objectives and Key Results) 的面紗OKRObject
- Elasticsearch Analysis 分析器Elasticsearch
- LIRE教程之原始碼分析 | LIRE Tutorial of Analysis of the Source Code原始碼
- 壓測結果分析
- 分析結果,方法傳參
- Linux netstat命令結果分析Linux
- R語言-Survival analysis(生存分析)R語言
- ElasticSearch7.3學習(二十六)----搜尋(Search)引數總結、結果跳躍(bouncing results)問題解析Elasticsearch
- LoadRunner測試結果分析(1)
- 線性判別分析(Linear Discriminant Analysis)NaN
- Go語言之變數逃逸(Escape Analysis)分析Go變數
- 線性判別分析(Linear Discriminant Analysis, LDA)NaNLDA
- SSH key使用總結
- SARIF:靜態分析結果交換格式
- 資料庫中介軟體 Sharding-JDBC 原始碼分析 —— 結果歸併資料庫JDBC原始碼
- iDLHCGP_Numerical_results
- iDLHCG_Numerical_results
- Elasticsearch——Filter search resultsElasticsearchFilter
- Oracle:On ROWNUM and Limiting ResultsOracleMIT
- 【筆記】【THM】Malware Analysis(惡意軟體分析)筆記
- MySQL EXPLAIN結果集分析 - 附帶大量案例MySqlAI
- sp_sysmon效能診斷結果分析(zt)
- 大資料分析筆記 (7) - 時間序列分析(Time Series Analysis)大資料筆記
- Android uncovers master-key 漏洞分析AndroidAST
- Numerical Results of adf-mDFP
- 如何使用GraphPad Prsim 9展示亞組分析結果PHP
- Linux系統下ifconfig命令使用及結果分析Linux
- 需求分析問卷調查及反饋結果
- 程式碼分析工具小結
- RISK ANALYSIS
- SOLIDWORKS Flow Simulation軟體流體分析結果檢視Solid
- jmeter學習指南之結果分析-圖形圖表JMeter
- Python純程式碼 取組合數結果Python
- Android Sensor原始碼分析總結Android原始碼
- 簡單分析MySQL中的primary key功能MySql
- Flutter Analysis OptionsFlutter
- HanLP Analysis for ElasticsearchHanLPElasticsearch
- 再見!onActivityResult!你好,Activity Results API!API
- NFS mount results in "vmount: operation not permitted" errorNFSMITError