Errors During Multilevel Price Determination
Prerequisites
In order to perform multilevel price determination successfully, the following prerequisites must be satisfied:
- The materials are not locked.
- Single-level price determination was performed.
Errors During Material Price Determination
Even if these prerequisites have been met, you may still experience the following errors during multilevel price determination:
- The cumulated quantity of a material in the period is zero, which prevents an actual price from being calculated.
- The actual BOM contains a cycle that is not converged and therefore does not allow price determination.
- The price for the material is negative.
- The price calculated in multilevel price determination for a material exceeds the threshold you set.
- The sum of the multilevel price differences that would subsequently be debited to the material exceeds the threshold you set.
These errors can be divided into three categories:
- Error 1 is corrected automatically by the system. No action is required on the part of the user. The system calculates with an alternative price that is found through a strategy.
- Errors 2 and 3 can also be corrected through special strategies in order to enable price determination. When you maintain the parameters for multilevel price determination, you can specify the strategy that is to be used under Show Postprocessing Options.
- Errors 4 and 5 occur as a result of the error thresholds you set. These error thresholds must be set to enable the errors to be corrected automatically using strategies under Show Postprocessing Options.
Options for Error Correction
Recommendations for Multilevel Price Determination
Due to the high level of complexity and the wide range of problem situations, there is no single best method of performing multilevel price determination. This section contains information that will assist you in finding a strategy that is suited to your particular situation.
Possible Approaches
Search for the materials whose variances are not acceptable, and decide whether you want to make adjustment postings. If you cannot make any adjustment postings, or if the adjustment postings do not remove the errors, set an error limit and execute the run again for all materials. When you do so, turn on automatic error correction so that the system can remove the errors that are resulting in the threshold values being exceeded.
- Also check whether the warning and error limits you set for single-level price determination were exceeded. If you did not set any limits, or if the set limits were not exceeded, any new errors are due exclusively to multilevel price determination and can be removed with automatic error correction. The worst that can happen is that in the reduced BOM (see
- If there is a large number of materials, you may want to set an error limit right from the start. It is then possible to determine the materials that have errors using the report Materials by Period Status. In some cases this may be easier than searching through the warning messages of multilevel price determination.
- When you process materials that have errors, you always start with the lowest costing level, since errors at this level are reproduced at the higher levels. However, it is possible for variances at different levels to cancel each other out. For example, if a material at the lowest level has large negative variances, such variances may cancel out variances at higher levels. If you remove the variances at the lowest level by means of correction postings or error correction, new errors may appear at the higher levels.
Warnings
If you first execute a costing run and generate warning messages for values that exceed the threshold value, and then set error limits, you must repeat the entire costing run with the error limits for all materials. You should not limit the run to materials for which you have set error limits.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/46681/viewspace-1038724/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- MyEclipse提示Errors occurred during the buildEclipseErrorUI
- ORA-04045: errors during recompilation/revalidation of LBACSYS.LBAC_EVENTSError
- eclipse新建maven專案:'Building' has encountered a problem. Errors occurred during the build.EclipseMavenUIError
- SQL : OM Price ListSQL
- ORB problem determinationORB
- Metric Collection ErrorsError
- oracle之errorsOracleError
- oracle 之errorsOracleError
- Price Tag | INTERVIEW 04 | 獨立開發者 LarryView
- Price Control V or S in material type
- [LeetCode] 430. Flatten a Multilevel Doubly Linked ListLeetCode
- SAP PM入門系列21 - IE07 Equipment List (Multilevel)UI
- Go Errors 詳解GoError
- slave-skip-errorsError
- HIbernate errors...Error
- Set Tolerance Limits for Price Variance(ZZ Kanterwang)MIT
- SAP PM入門系列23 - IL07 Functional Location List (Multilevel)Function
- 從EXCEL導PRICE LIST到OM單價庫Excel
- how to handl price differences in Purchase Order, Goods Receipts and Vendor InvoiceGo
- Working with Errors in Go 1.13ErrorGo
- Errors and Recovery for the Server Parameter FileErrorServer
- mysql slave-skip-errorsMySqlError
- Canvas errors & CORS All In OneCanvasErrorCORS
- React 18 errors All In OneReactError
- SAP Cloud for Customer Price-計價簡介Cloud
- How to recover from USB pipe errorsError
- Two errors after cloning eBSError
- nvm command errors All In OneError
- An error occurred during bosboot verification processingErrorboot
- BestCoder Round #861001Price List(數學)
- oracle software price軟體產品定價--價格資訊Oracle
- 用excel檔把item與price匯入oracle erpExcelOracle
- Paper Reading: Cost-sensitive deep forest for price predictionREST
- MIGO Error:Account determination for entry LGCC WRX not possibleGoErrorGC
- “setting.xml” has syntax errorsXMLError
- 忘不了的 TODOS & FIXMES & ERRORSError
- How to Diagnose and Resolve UNABLE TO EXTEND ErrorsError
- error: Exited sync due to fetch errorsError